← All field notes
Adoption
Three things that drift after go-live
A system that fitted the business on launch day rarely fits it a year later. The drift is predictable, and so are the fixes.
Rygnite team
3 min read
Nobody decides to let a system drift. It happens one sensible workaround at a time, until the workarounds are how the business runs. These are the three we see most often.
1. Fields nobody fills in
Fields added for a report that nobody reads any more, or for a process that changed, stay on the form. People learn to skip them, and then they skip the ones that matter too. Once a quarter, list every field that is empty on most records and ask who needs it.
2. Rules nobody owns
Automations are built by whoever needed them at the time. A year later nobody knows why an email goes out or a status changes, so nobody dares switch it off. Give every rule an owner and a one-line reason, and review the list when a process changes.
3. Access copied from a colleague
New starters are often set up by copying a colleague, so permissions spread further than anyone intended. Check roles against the access model you agreed at design, and remove admin rights that were only needed during the build.
What to do about it
A short monthly review catches all three before they become policy. That review is Stage 6 of how we work, and it is where most of the value of a system is kept or lost.