Nobody can say what the company will stop doing
Priorities accumulate, but explicit stopping decisions are rare or absent.
- Where you see this
rapid growthtransformation programslarge portfolios
- Not necessarily a problem when
- the organization is in a short-term expansion phase and has explicitly funded the extra load
- Often mistaken for
- we can just work smarter across all priorities
- Time horizon
- medium-to-long-term
- Best placed to act
executive leadershipportfolio owners
The signal
What you would actually notice
Strategic focus degrades, teams overcommit, and every new priority becomes somebody’s invisible burden.
Field observation
New initiatives, expectations, and standards appear, but old ones rarely leave formally.
Also observed
- We need to do all of this.
- Nothing is coming off the list.
Primary reading
What it usually indicates
Most likely underlying patterns when this signal shows up. Not a diagnosis, a starting hypothesis.
Usually indicates
Most likely underlying patterns when this signal shows up.
- strategy sprawl
- avoidance of trade-offs
- leadership discomfort with stopping
Not necessarily a problem when
Contexts where this signal is expected and does not indicate a deeper issue.
- the organization is in a short-term expansion phase and has explicitly funded the extra load
Stakes
Why it matters
Strategic focus degrades, teams overcommit, and every new priority becomes somebody’s invisible burden.
Heuristic
An organization that only adds priorities is usually hiding its real trade-offs in people’s capacity and burnout.
Inspection
What to check next
Deliberate steps to confirm or disconfirm the primary reading above. Not a checklist. An order of inspection.
- portfolio changes
- sunset decisions
- capacity versus initiative count
Diagnostic questions
Questions to ask the team, or yourself, before concluding anything.
- What work was intentionally stopped this quarter?
- What priorities displaced which other priorities?
- Where is the cost of not stopping absorbed?
Progression
Under the signal
Where this pattern tends to come from, what's holding it up, and where it goes if nothing changes.
Leading indicators
What tends to show up first.
- teams inherit more priorities than capacity
- everything remains important quarter after quarter
- sunset conversations rarely happen
Common root causes
What is usually sitting under the signal.
- strategy avoidance
- political sponsorship of too many initiatives
- weak portfolio discipline
Likely consequences
What happens if nothing changes.
- overload
- thin execution
- priority cynicism
Look-alikes
Not what it looks like
Patterns that can be mistaken for this signal, and 'fix' attempts that make it worse.
- we can just work smarter across all priorities
Anti-patterns when responding
Responses that feel sensible and usually make the underlying pattern worse.
- adding 'focus' language without removing commitments
- treating stopping as failure rather than portfolio hygiene
Context
Context and ownership
Where this signal surfaces, who sees it first, who can actually act, and how much runway there usually is before escalation.
Where it shows up
- rapid growth
- transformation programs
- large portfolios
Who sees it first
Before it escalates.
- engineering managers
- portfolio leads
- teams on the receiving end
Who can move on it
Not always the same as who notices it.
- executive leadership
- portfolio owners
medium-to-long-term
How much runway there usually is before the signal hardens into the underlying pattern.
AI impact
AI effects on this signal
How AI-assisted and AI-driven workflows tend to amplify or hide this signal.
AI amplifies
Ways AI tooling tends to make this signal louder or more common.
- AI can make expansion look more manageable by increasing artifact and planning throughput without increasing actual human capacity.
AI masks
Ways AI tooling tends to hide this signal, so it keeps growing under the surface.
- Better summaries and plans can hide strategic overcommitment.
AI synthesis
AI adoption becomes one more priority layer without retiring anything else.
Relationships
Connected signals
Related failure modes, decisions behind the signal, response playbooks, and neighboring red flags.