Improve operations by fixing flow, standards, and decisions

Choose a problem you can follow

I look at operational effectiveness through three connected elements: how work moves, what the team agrees good work requires, and how decisions get made. Together, flow, standards, and governance help explain why committed people can still spend so much effort compensating for the way work is organized.

Select a recurring item the team recognizes: a request, an approval, a report, or a delivery commitment. Define where it begins and where the receiving person considers it finished. Keep the first review narrow enough to complete with the people involved.

Trace where the work waits

Take a few recent examples and reconstruct their journey. Use records and conversations to distinguish time spent doing the work from time spent waiting. For each pause, record what had to happen before progress could resume.

• Was information missing or unclear?
• Was a person waiting for permission to proceed?
• Was the work ready but capacity unavailable?
• Had the item reached a handoff that nobody was watching?

Keep the conditions separate. An information problem needs a different response from a capacity problem. If the cause is uncertain, assign a small investigation instead of turning an assumption into the improvement plan.

Illustrative example: a weekly request review

Illustrative example: A team reviews the same unresolved requests every week. Each meeting produces reminders, but the next meeting starts with much of the same list.

Looking at the records reveals several different conditions: some requests lack an answer from the sender, some need a priority decision, and some are approved but waiting for available capacity. One undifferentiated list hides the decisions required.

The team could separate those conditions and assign a response to each. The sender clarifies incomplete requests. An accountable leader resolves competing priorities. The delivery owner reviews ready work against capacity. The meeting can then focus on changes and decisions that remain unresolved.

Set one useful standard

Choose a recurring point of confusion and write the minimum agreement needed to resolve it. A practical standard should answer:

1. What must be present? Define the information or evidence needed for the next step.
2. Who checks it? Assign responsibility for confirming that the work is ready.
3. What happens when it is incomplete? Give the sender and receiver a clear way to resolve the gap.
4. Who can approve an exception? Make the decision route visible so people can handle unusual circumstances consistently.

Test the standard against ordinary work and an awkward example. Ask someone who did not help write it to explain how they would use it. Revise the parts that require an unwritten explanation.

Give decisions a reliable rhythm

An operating rhythm should match when the team needs to act. Define the purpose of each review, the decisions it can make, and what participants need to bring. Avoid carrying an unresolved item forward without identifying what will change before the next review.

• Before the review: prepare the relevant exceptions and state the decision needed.
• During the review: agree the response, accountable owner, and next review point.
• After the review: record the commitment where the people doing the work can find it.

If a decision exceeds the group’s authority, send it through an agreed escalation route with the question and supporting context intact.

Change one part, then examine the effects

Give the team time to use the change, then return to the original problem. Has the waiting condition changed? Are requests easier to accept? Are decisions being resolved at the intended review? Has the change created extra work elsewhere?

Use the answers to retain, revise, or remove the change. Keep the measures understandable and close to the work. A small improvement that people can maintain provides a stronger foundation for the next decision than a broad redesign nobody has put into practice.