The Owner Bottleneck · Chapter 2
How to choose the first workflow to improve
A list of recurring problems is not yet a roadmap. Compare operational impact with readiness, choose one bounded workflow, and test an improvement before selecting technology.
Use the priority scorecard← Chapter 1: When the Owner Becomes the Operating System
A list of problems is not a roadmap
After observing owner-dependent work, you may find several bottlenecks: quotes need follow-up, employees search for material, customer decisions stay in messages, and completed work waits for invoice information.
The first workflow should be important enough that improving it creates visible value, but contained enough that the business can understand it, test a change, and learn from the result.
Do not automatically choose the loudest problem, the easiest automation, or the largest department.
Choose a workflow—not a department or product
A useful starting workflow has a starting event and a completed operating outcome.
Customer flow
Customer request received → quote sent with an assigned follow-up date
Material flow
Material received → quantity, location, and intended job visible
Completion flow
Work marked complete → office has invoice-ready information
The objective is the smallest boundary that still produces a meaningful business outcome.
Compare impact and readiness separately
A painful workflow may not be clear enough to automate. An easy automation may not create enough value to deserve attention.
Impact
Will the difference matter?
- Frequency
- Waiting and delay
- Rework or repeated entry
- Owner dependence
- Customer or financial consequence
Readiness
Can a better process be tested safely?
- Boundary clarity
- Predictable next actions
- Participation
- Small-test feasibility
Workflow Priority Scorecard
Compare two to four candidates
Use recent observations when possible. Score each criterion from zero to three, then keep the impact and readiness subtotals separate.
Scoring scale
Not present, not understood, or no evidence
Occasional, limited, or low consequence
Recurring or meaningful
Frequent, persistent, or high consequence
Impact score
| Criterion | Question | Score 0–3 |
|---|---|---|
| Frequency | How often does this workflow or problem occur? | |
| Waiting and delay | How much does work, a customer, material, an invoice, or an employee wait? | |
| Rework or repeated entry | How often is information reconstructed, corrected, entered again, or chased? | |
| Owner dependence | How often must the owner provide routine status, information, approval, or reconnection? | |
| Customer or financial consequence | Can this affect commitments, trust, revenue, cash timing, cost, or financial handoff? | |
| Impact subtotal | / 15 | |
Readiness score
For readiness: 0 means unknown; 1 means unclear or dependent on major prerequisites; 2 means mostly clear with some preparation needed; and 3 means clear enough for a contained operating test.
| Criterion | Question | Score 0–3 |
|---|---|---|
| Boundary clarity | Can the starting event and completed outcome be described clearly? | |
| Predictable next actions | Are the normal steps and decisions understood well enough to test a better process? | |
| Participation | Are the people involved available and willing to describe and test the workflow? | |
| Small-test feasibility | Can one useful change be tested during a few operating cycles without replacing everything? | |
| Readiness subtotal | / 12 | |
Candidate comparison
Score one candidate at a time, then carry both subtotals into this table.
| Candidate workflow | Impact / 15 | Readiness / 12 | Priority override? | Decision or preparation needed |
|---|---|---|---|---|
Keep the two subtotals separate
The numbers help compare candidates. They are not universal pass/fail grades, and a combined total can hide the difference between an important workflow and an easy one.
Interpret the result
Higher impact · Higher readiness
Strong starting candidate
Important enough to matter and clear enough to test.
Higher impact · Lower readiness
Prepare it
Clarify the boundary, information, responsibility, or normal path before automating.
Lower impact · Higher readiness
Validate its value
It may be a quick improvement, but convenience should still produce a meaningful result.
Lower impact · Lower readiness
Usually defer it
Keep observing unless an important risk or obligation changes the priority.
Important priority override
A rare problem can still require immediate attention
Safety risk, legal or regulatory obligations, serious financial exposure, security or privacy risk, and materially broken customer commitments may deserve attention regardless of frequency or score.
This scorecard is not a safety, legal, accounting, security, or compliance assessment. It should not postpone help from the appropriate responsible professional or authority.
What a hypothetical comparison can reveal
These examples illustrate the method rather than diagnose a particular company.
Quote follow-up
Meaningful impact and higher readiness when the request, quote, responsible person, and desired follow-up are already understood.
Material receiving and location
Potentially high impact but lower readiness when no consistent receiving step, location convention, or job association exists.
Completion to invoice readiness
Strong customer and financial consequences, and a viable candidate when completion outcomes and required handoffs can be defined.
The scorecard informs contextual judgment; it does not declare one universal winner.
One result to produce
Write the decision before naming the software
We will improve the workflow from __________ to __________ because it repeatedly creates __________. We will first test __________ during __________ operating cycles.
That statement defines a business experiment rather than a product installation.
Technology in its proper role
A first improvement may be a checklist, shared status, required field, assigned responsibility, or operating rule. Technology becomes valuable when it makes the agreed flow easier to follow, reduces repeated work, preserves a reliable record, and exposes exceptions early.
Technology must remove more effort, delay, risk, or uncertainty than it adds.
Previous chapter
When the Owner Becomes the Operating System
Next chapter
Measure Before You Automate
Once a workflow is selected, establish a small baseline before changing it.
Choose one. Measure it before changing it.
A focused first workflow gives the business a practical place to learn. The next step is to capture a small baseline so the result can be compared with what happens after the change.
Talk through one workflow