Practical guide · recurring problems

Where is progress actually getting stuck?

Start with the result that is not improving, then trace one real flow. Avoid choosing a cause just because it is familiar.

The complete loop

Leave with a specific evidence request and a date to return.

RouteMapCommitReturn
01

1. Describe the recurring result.

Choose one outcome: profitable completed orders, collected payment, reliable delivery or another result that fits your business. Record the period and the gap between the intended and observed result. “The team is too slow” is too broad to investigate. “Quotes wait several days before customers receive them” names a place to begin, but not yet the main constraint. Keep the customer or business consequence in view.

02

2. Follow work through the handoffs.

Sketch how a recent enquiry becomes a quote, an order, delivery and payment. For each step, ask who owns it, what input it needs and where it waits or returns for correction. Use actual cases rather than everyone’s average impression. In the fictional demo, approval records are available while specification-start dates are not. That gap limits what the team can conclude about specifications; it must not be silently filled.

03

3. Compare explanations that imply different actions.

The owner might see insufficient sales capacity. The manager might see approval delay. A coordinator might see incomplete specifications. List what each explanation predicts: more unanswered enquiries, a queue awaiting signatures, or work restarting after clarification. Ask which records would distinguish these patterns. Several constraints may coexist or move after a change; do not force every observation into one cause.

04

4. Choose the next useful evidence request.

Ask for a defined set of recent cases, timestamps, margin or payment records only where they matter to the decision. Name the source, responsible person and review date. In the prepared example, twelve of twenty quotes await owner approval; that supports examining approvals without proving hiring is unnecessary. If the records are missing, choose a feasible observation period or collection method and explain what remains unknown.

05

5. Test the constraint against the outcome.

Choose a bounded change that targets the suspected limit. Write the expected intermediate signal and the business result you will check. The fictional approval test shortens quote turnaround from four days to two while profitable completed orders remain eight, below the expected ten. The team has learned something about speed but cannot claim growth. Return to the flow and ask what now limits completed work. The useful conclusion may be a better next question.

Your first company decision

Choose your next useful check.

See how the owner delegates preparation, the team contributes independent evidence, and a recorded result informs the next move. Then review the self-service paid company trial. No founder meeting is required.

Explore the team demo