Level 3 to Level 4: The Optimization Window Doesn't Stay Open Forever
Updated: Sep 9
What happens to your change request list when nobody's looking at it anymore.
Six to nine months after go-live, something predictable happens. Teams start noticing what they would do differently now. A change request list forms, and people start saying things like "now that we have been using this a while, I would set this part up differently."
That is Level 3 on the Services Operations Maturity Model, the Optimization Window. It is a good problem to have, because it means your organization has finally lived in the system long enough to know what works and what does not.
That window closes, though. And it tends to close without anyone deciding to shut it.
Most change request lists do not get killed by a bad decision. They get killed by nothing at all.
Where the list goes to die
The list sits in a shared doc, or a project board nobody opens anymore. A few items get knocked out. The rest stay there, untouched, month after month.
Around the twelve month mark something shifts. The system is running, reports are flowing, and people have adapted to the workarounds that used to feel temporary and now just feel normal. That is Level 4, Operational Maturity. Things work, and that is exactly the problem.
I do not get pulled into a ton of organizations already sitting at Level 4. Most of my work happens earlier, in implementation or in that Level 3 stretch. But when I do end up in a Level 4 environment, the pattern looks the same. Something feels off even though nothing is technically broken. Once we dig in, the change request list from eighteen months ago is still sitting there, mostly untouched. Half the items are still relevant. Nobody quite remembers why the other half seemed important at the time.
Why the window closes
It is not that Level 4 organizations stop caring. It is that operational maturity has a way of lowering the pressure to act. When the system is stable, "later" stops feeling urgent, and the change list stops being a plan and starts being a graveyard.
Meanwhile the configuration that made sense at go-live keeps aging. The organization has changed since then. New service lines, new reporting needs, new headcount, sometimes a new leadership team with different questions. The system has not moved with any of it, because nobody circled back to make it.
The signals your window is closing
You will not get a notification. But there are tells, and they show up in how people talk rather than in anything the system reports.
Nobody has opened the list in a quarter. If you cannot remember the last time it was reviewed, it is not a plan anymore.
Your team has stopped asking for changes. This reads as a good sign and usually is not. It normally means people gave up asking and built a workaround instead. Requests stopping is different from requests being resolved.
New hires are being trained on the workarounds. This is the one to watch for. The moment a workaround gets taught to someone as "how we do it here," it has stopped being a temporary fix and become policy. Undoing it later is a change management project, not a configuration change.
Someone is maintaining a shadow spreadsheet. If a person is exporting data to do their real work, the system is not doing that part of the job, and nobody has raised it in a while.
What actually keeps the window open
The organizations that get real value out of Level 3 do one specific thing differently. They treat the optimization window as a scheduled checkpoint rather than an open-ended someday. A defined window, usually somewhere in that six to nine month range, where the list gets triaged on purpose instead of accumulating by accident.
That does not mean building everything on the list. It means deciding, deliberately, what is worth doing now and what is genuinely fine to let go.
How to triage the list
When I work through a change request list with a client, every item gets sorted into one of three buckets. It is a blunt method and it works because it is blunt.
Does it change a decision? If fixing this item would change something leadership decides, or lets someone answer a question they currently cannot answer, it goes to the top. This is where your budget belongs. A report that changes how you staff next quarter is worth more than any amount of interface polish.
Does it change a habit? Items in this bucket make daily work meaningfully easier for a group of people. Timesheet friction, approval routing, anything that people work around every single week. These are worth doing, and they are usually cheaper than they look, because the friction has been priced in for so long that nobody remembers it is optional.
Does it change a screen? Cosmetic, preference-driven, or one person's strong opinion about a field label. Some of these are worth doing when they are nearly free. Most are not. Be honest about which is which.
Anything that does not land in the first two buckets is a candidate for closing out. Not deferring, closing. A deferred item comes back in six months looking exactly as important as it does today. A closed one stops taking up room.
A list that has been triaged is a plan. A list that has been collecting dust is a liability waiting to surface.
That liability tends to surface at the worst possible moment, usually when leadership asks why the system is not doing something it was supposed to do eighteen months ago.
If you’re staring at your own list right now
Pull it up and really look at it. Some of it is still relevant. Some of it is not anymore, and that is fine, priorities shift. The goal is not to build everything on the list. It is to stop letting the list decide for you by default.
If your window is still open, use it on purpose. If it has already closed, it can be reopened, and the reopening is usually less work than people fear. What it takes is someone deciding the list matters again and putting a date on it.
Not sure whether you are at Level 3 or already past it?
The SOMM self-assessment places you in under five minutes and shows you what the next level takes.
Want to go deeper?
The SOMM Level-Up Roadmaps cover the Level 3 to 4 move in detail: a structured walkthrough of the triage above, and what changes as organizations settle into Operational Maturity. All five levels in one guide, $49, one time.
Want a second set of eyes on the list?
Triaging a change request list is most of what a Level 3 optimization engagement actually is. If you want help deciding what is worth your budget, let's talk.
Get the next one in your inbox.
PS Playbook is a weekly(ish) read for Professional Services teams who want their operations to actually work.
