1. Bound the flow
Agree the start, the end, and what is deliberately out of scope. A bound keeps the work finishable. “Improve operations” is not a bound. “Client onboarding from verbal yes to first delivery” is.
The practice
A practice for the operating side of strategy
ANDRIAN PRONIN is an independent business process strategy practice based at Mihai Eminescu Street 74 in Chișinău. The work sits between a leadership intention and the daily line of tasks: who owns the next step, what “done” means at a handoff, and how the team will notice if the line slips.
Strategy documents often describe markets, offers, and goals. They say less about the path a piece of work takes once someone has said yes. That path is the subject of this practice. It is practical, bounded, and written so the people who run the work can use it.
Clients are usually founders, chief operating officers, operations managers, and heads of delivery or client service. They come when growth has made the old informal system heavy: more people, more exceptions, and more time spent asking where something went.
Principles
How the work is held
The case comes before the framework. A recent order, client, claim, or internal request is the evidence. Frameworks are used only if they explain that case.
Ownership is a design choice. If two roles can both claim a step, the process will wait. The work names a single accountable owner for each stage.
Exceptions belong on the map. The smooth path is rarely where time is lost. Rework, missing inputs, and escalations are designed on purpose.
Discretion is part of the method. Internal process detail is treated as the client’s operating information. It is not reused as a public example.
The engagement is meant to end. Advice that only works while the advisor remains in the meetings has not finished. Deliverables are written for the team that stays.
Methodology
Line of Work
Line of Work is the practice method. It keeps every engagement inside five moves, even when the subject is an operating model rather than a single procedure. The same sequence appears, in client language, on the journey page.
2. Walk the real work
Follow one or two recent cases with the people who touched them. The aim is the path that happened, including delays and informal fixes, not the path in the old procedure.
3. Name the breaks
Separate symptoms from breaks in the line: unclear ownership, a handoff with no ready-standard, a decision with no authority, or a review that never occurs.
4. Redesign the line
Draw the future path, the roles, the handoff rules, and the exception routes. The design is small enough to pilot. It is not a rewrite of the whole company.
5. Set the cadence
Choose a few measures and a review rhythm. Without this step, the map is a document. With it, the team has a way to see whether the line is holding.