You know your operations are inefficient. You do not yet know which part is actually costing you, and in operations that is the difference between a fix that pays and a fix that backfires.
The temptation is to grab the loudest pain, the crisis this week or the tool someone is lobbying for, and react to it, while the real constraint sits somewhere else. A business buys software to fix a process it never mapped. A business standardizes a process whose root problems it never solved, and standardizes the dysfunction. This diagnostic replaces the guessing with an honest, scored read of where your operations actually break, and it hands you a plan telling you which guides to work and in what order.
This is a routing instrument, not a fix. It will not map your processes or build your standards. It tells you where to start and what order to work in. It takes about thirty to forty five minutes and a willingness to look honestly at how your operations really run, not how the org chart says they should. If you have any operational numbers, cycle times, error or rework rates, volumes, bring them. If you have none, that absence is itself a finding.
Every judgment below rests on reality rather than impression only if you first write down how your operations actually run today. Two facts matter most: whether your core work would run the same if a key person were out for a month, and how much of your week goes to firefighting recurring issues. Both are direct reads on where you stand.
Open the Operations Baseline Snapshot first →Answer each the way it really is, not the way you wish it were. Each link maps to one guide in this pathway.
You can state your single binding constraint in one sentence. You hold an ordered list of guides, not a vague sense that operations need work. And your first guide has a real start date. Write the finding into your action plan and give the first move a date this week, because operational improvement is uniquely easy to defer when the firefighting always feels more urgent than the system building that would end the fires.
If you could not score the links because the weakness lives in one function rather than in operations generally, the real work may be elsewhere. The sales system is sales systems, client delivery is delivery and client experience, and individual and team workflow is productivity and workflow.