Process Management: From Opportunity to Measurable Outcome

What is process management?

Process management is the discipline of carrying an approved opportunity through implementation without losing the business reason for the work.

It connects five things:

1. the evidence that revealed the issue
2. the economic case that justified action
3. the workstreams and actions that create the change
4. the measures that show whether the change is occurring
5. the governance decisions that keep, adapt, accelerate, or stop the work

This is more than task tracking. A list of completed activities cannot show whether the expected business effect occurred.

Begin with an owned decision

Implementation begins when the team owns a clear decision.

Record:

• what was approved
• the scope and affected population
• the expected economic effect and timing
• the leader accountable for the intended outcome
• the owner responsible for delivery
• important constraints, risks, and dependencies
• the next decision gate

The accountable leader and delivery owner may be the same person. The scale of the work may justify additional governance roles, but the operating requirement is clear accountability rather than a fixed role structure.

If the approved scope differs from the sized opportunity, revise the case before creating the plan. Otherwise, the team will be measured against economics that no longer match the work.

Translate the case into owned work

The economic bridge describes why value should change. The implementation structure describes how the organization will make that change happen.

Use the lightest structure the work requires:

Element	Purpose	Example content
Opportunity / owned decision	The approved business change, scope, and intended economic outcome	Simplify the low-volume product portfolio
Initiative or workstream	A coherent body of work needed to deliver part of the decision	Define disposition rules and transition plans
Action	A specific next step with an owner and date	Validate contractual obligations for selected SKUs
Measure + review	Evidence that implementation and the intended outcome are occurring	Track product exits and review margin or capacity movement

Terminology can vary with the implementation method. In COMPASS, workstreams and actions are the common execution structure, while Grow can add an initiative layer when it is useful. Milestones can mark meaningful states or decisions inside the work, but they are planning markers rather than a required structural level.

Avoid turning every task into a workstream or initiative. Each should represent a distinct body of work with an owner, outcome, and reviewable progress.

Make ownership unambiguous

Every active body of work and action needs one accountable owner. Critical measures need a defined source and owner. Teams and functions can contribute, but shared accountability often becomes no accountability.

At minimum, make four kinds of ownership clear:

• Outcome ownership: one accountable leader owns the intended business result and the major tradeoffs required to pursue it
• Workstream or initiative ownership: one owner coordinates and delivers a coherent body of work
• Action ownership: one owner completes a specific next step by a date
• Measure ownership: one owner maintains the definition and source of a critical measure

The same person may hold more than one of these responsibilities. Larger or more cross-functional efforts may add a sponsor, executive lead, integration lead, or other governance roles when the scale of the work requires them. Those are governance choices, not mandatory layers in the operating model.

Document who recommends, decides, executes, and must be consulted when those rights are not obvious.

Connect actions to measures

Use both implementation and outcome measures.

Implementation measures

These show whether the planned change is being put in place. Examples include decisions completed, customers transitioned, products dispositioned, policies activated, or employees trained.

Outcome measures

These show whether the expected business effect is occurring. Examples include realized price, margin, order frequency, changeovers, inventory, service cost, capacity, or EBITDA contribution.

Each measure should have:

• a precise definition
• a source system and owner
• a baseline and reporting period
• an expected direction or target
• a refresh cadence
• known limitations

Do not use a leading implementation measure as proof of the final economic result. It is evidence that the mechanism is progressing, not that value has been realized.

Design the review cadence

Different questions move at different speeds. Use only the review layers appropriate to the scale of the work rather than forcing every topic into one meeting.

• Action review: frequent, focused on next steps, dates, and immediate barriers
• Workstream or initiative review: focused on progress, meaningful milestones or decision points, dependencies, risks, and decisions
• Outcome review: timed to when operational or financial measures can meaningfully change
• Portfolio review: when multiple opportunities compete for attention or capacity, compare expected value, strategic priority, and resource demands

Every review should end with recorded decisions, changes, owners, and dates. A status conversation without a decision or next action is not governance.

Review the business case, not just the plan

Bring the original opportunity case into the review. Ask:

• Is the affected population still the same?
• Is the value mechanism behaving as expected?
• Have assumptions changed?
• Is timing ahead or behind the case?
• Are implementation costs different?
• Is the opportunity still material?
• What evidence supports continuing, adapting, accelerating, or stopping?

Update the forecast when facts change. Preserve the original case as a baseline, but do not protect an outdated estimate merely because it was approved.

Use exception-based governance

Management attention is limited. Focus reviews on material exceptions and decisions.

Define escalation rules for conditions such as:

• a critical decision, date, or milestone is missed
• expected value falls outside the agreed range
• a dependency threatens timing or scope
• risk exceeds the owner’s authority
• a measure cannot be produced reliably
• the mechanism is not responding as expected
• the work requires capacity not included in the plan

Clear rules allow routine progress to continue while bringing the critical few issues to the right level quickly.

Manage changes to scope and value

Implementation plans will change. Treat scope, timing, cost, and expected value as connected.

When scope changes:

1. record the reason
2. update the affected population and actions
3. revise the economic bridge and timing
4. identify new risks or dependencies
5. obtain the appropriate decision
6. preserve a traceable history of the change

This prevents the team from quietly delivering a smaller result while continuing to report the original opportunity value.

Close the loop

Implementation is not complete when the final action is checked. Close the work when the organization has made an explicit decision about the outcome.

At closeout, document:

• what changed
• what value was observed and over what period
• which assumptions were supported or disproven
• any remaining actions or controls
• who owns the process after implementation activity ends
• what should be repeated, adjusted, or avoided next time

Some outcomes require continued measurement after implementation activity ends. Assign that ownership before closing the work.

Common process-management mistakes

Tracking activity without the case

Completed tasks do not prove economic impact. Review actions and outcome measures together.

Too many priorities

If every analytical insight becomes a workstream or initiative, leadership attention and delivery capacity are diluted. Return to the critical few.

Ambiguous ownership

Name one accountable owner for each outcome, active workstream or initiative, action, and critical measure.

Static plans

Plans should change when evidence changes. Use controlled revisions rather than ignoring new facts or continually resetting the baseline.

Meetings without decisions

Design governance around exceptions, choices, and owner commitments—not presentation volume.

The minimum operating system

A practical management process can begin with a small set of connected records:

1. the approved opportunity size and owned decision
2. the active workstreams or initiatives and actions
3. owners and decision rights
4. implementation and outcome measures
5. risks and dependencies
6. review cadence and escalation rules
7. decisions and revisions
8. closeout and learning

Use milestones where they help the team recognize a meaningful state or decision, but do not require them as a separate management layer.

The purpose is not to create administration. It is to keep attention on the few changes that matter and make their progress, economics, and ownership visible.

Frequently asked questions

What is process management in an 80/20 implementation?

It is the operating discipline that connects an approved economic case to workstreams, actions, owners, measures, governance, and review decisions. It keeps implementation activity tied to the intended business outcome.

What should an implementation review cover?

Review the original case, workstream and action status, leading indicators, business outcome measures, risks, dependencies, decisions required, and any change to the expected value or timing.

How often should workstreams be reviewed?

Use a cadence that matches the speed of the work and the measure. Actions may need weekly review, while operational or financial outcomes may be meaningful monthly or quarterly. Define the cadence before execution begins.

When should a workstream be stopped?

Stop, redesign, or rescope when the mechanism is disproven, expected value is no longer material, risk becomes unacceptable, required capacity is unavailable, or repeated evidence shows the current approach will not deliver the case.