Mission Precedes Operations
Alex de Verteuil ·
Before we optimize a process, we should ask what it must accomplish.
Consider two organizations with the same five-step approval process.
In one, the approval chain delays a routine purchasing decision. Each handoff adds waiting time, but little information or accountability that the next person needs.
In another, those five steps provide necessary controls within a regulated manufacturing process. Each review serves a distinct purpose: verifying evidence, confirming specifications, or authorizing release.
The workflows may look identical. Their value is not.
Removing steps from the first process might eliminate waste. Removing them from the second could weaken the controls that make its output trustworthy. In either case, counting steps or measuring elapsed time tells us very little until we understand what the process must accomplish.
This is the foundational premise of the A. de Verteuil Framework:
Mission precedes operations.
Purpose gives performance meaning
Every institution exists to accomplish something. Its operations should make that mission possible, and its measures should help establish whether it is succeeding.
Yet operational conversations often begin further downstream: a queue is growing, an approval takes too long, a team is missing its targets. The immediate question becomes how to improve the number.
Before changing the workflow, we need to establish what that number represents.
A shorter turnaround time may improve access to a diagnostic result. It may also be achieved by moving verification work to another team. Increased throughput may reflect a stronger process, or it may depend on people absorbing more work than they can sustain.
The metric records a change. Understanding its value requires examining what changed around it.
Efficiency cannot be evaluated independently of purpose.
Understand what the process enables and protects
In life sciences and diagnostics, operational decisions sit at the intersection of quality, scientific capability, regulatory requirements, access, and time to market.
Applying Lean well requires understanding those relationships. Reducing delay matters. So does identifying which activities establish confidence in the result, which preserve essential knowledge, and which exist because the surrounding system has never been redesigned.
A familiar step deserves examination. A required control deserves a clear purpose. Neither familiarity nor the language of compliance should end the discussion.
The task is to understand the function well enough to improve how it is delivered.
Could a control be built into the workflow earlier? Could clearer decision rights remove repeated approvals? Could better information prevent the rework that makes a review necessary in the first place?
These questions open possibilities that simply asking people to work faster will miss.
Look beyond the immediate improvement
Processes connect. Changing one can alter the demands placed on several others.
A team may accelerate its output while creating a backlog downstream. A simplified intake process may leave specialists reconstructing missing information. A local productivity target may encourage work that consumes capacity elsewhere without improving the institution’s ability to fulfill its mission.
The improvement is incomplete if its benefits depend on costs that remain outside the measurement.
This is also why meeting a target does not, by itself, establish that a system is healthy. Performance may depend on extraordinary individual effort, informal coordination, or hidden rework.
Those contributions can keep an organization functioning. They can also conceal where its structure needs attention.
A faster process isn’t necessarily a healthier one.
Begin with intentional architecture
I believe operational excellence begins with intentional architecture: designing the conditions, responsibilities, information flows, and feedback mechanisms that allow an institution to deliver value reliably.
That work starts with a few questions:
- What mission justifies this work?
- What must the system enable, and what must it protect?
- How does each major activity contribute to that purpose?
- Where does performance depend on effort or capacity we have not accounted for?
- What would demonstrate that a change improved the system as a whole?
Making mission explicit does not remove difficult tradeoffs. It gives us a basis for evaluating them.
It also gives the five axioms of the A. de Verteuil Framework a reference point. Environment, system expression, structural integrity, measurement, and incentive drift can be examined in relation to the mission they are meant to support.
Over the coming weeks, I will explore each axiom and how it informs my thinking about Lean, organizational health, and sustainable innovation.
The starting question is:
What must this system accomplish, and how do we design it to do so reliably?
Explore the premise and five axioms of the A. de Verteuil Framework →
If you lead a workflow that meets its targets but is hard to sustain, I would like to hear about it. Get in touch.