Skip to main content
The Hard Parts.dev
RF-33 Leadership · Delivery RF Red Flags
Severity high Freq common

Risks are acknowledged but never priced into plans

People discuss risks intelligently, but schedules, scope, staffing, and commitments do not change to reflect them.

Severity
high
Frequency
common
First noticed by
delivery leads · senior engineers · honest managers
Detectability
subtle
Confidence
high
At a glanceRF-33
Where you see this

portfolio planningprogram deliveryexecutive steering

Not necessarily a problem when
a risk is low probability and a deliberate conscious decision is documented
Often mistaken for
we have identified the risk, so we are managing it
Time horizon
medium-term
Best placed to act

sponsordirectorportfolio owner

The signal

What you would actually notice

The organization performs awareness without absorbing consequence.

Field observation

Risks appear in logs, updates, and caveats, but commitments remain unchanged as if those risks were free.

Also observed

  • Yes, that is a major risk, but the timeline is unchanged.
  • We are tracking the risk closely.

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.

  • status culture
  • leadership optimism bias
  • fear of explicit trade-offs

Stakes

Why it matters

The organization performs awareness without absorbing consequence.

Inspection

What to check next

Deliberate steps to confirm or disconfirm the primary reading above. Not a checklist. An order of inspection.

  1. risk logs
  2. capacity plans
  3. timeline adjustments
  4. mitigation ownership

Diagnostic questions

Questions to ask the team, or yourself, before concluding anything.

  1. What changed in the plan because of this risk?
  2. What budget, time, or scope was reserved for it?
  3. Who accepted the cost if the risk lands?

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.

  • risks are repeated every update
  • plans stay constant despite worsening evidence
  • mitigations are shallow or symbolic

Common root causes

What is usually sitting under the signal.

  • leadership denial
  • political pressure
  • portfolio overcommitment

Likely consequences

What happens if nothing changes.

  • surprise delays
  • burnout
  • quality compromises

Look-alikes

Not what it looks like

Patterns that can be mistaken for this signal, and 'fix' attempts that make it worse.

False friends Things the signal is often confused with, but isn't.
  • we have identified the risk, so we are managing it

Anti-patterns when responding

Responses that feel sensible and usually make the underlying pattern worse.

  • treating risk discussion as mitigation
  • keeping risk registers detached from resource planning

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.

Common contexts

Where it shows up

  • portfolio planning
  • program delivery
  • executive steering
Most likely to notice

Who sees it first

Before it escalates.

  • delivery leads
  • senior engineers
  • honest managers
Best placed to act

Who can move on it

Not always the same as who notices it.

  • sponsor
  • director
  • portfolio owner
Time horizon

medium-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 generate higher-quality risk summaries that still do nothing to force real trade-offs.

AI masks

Ways AI tooling tends to hide this signal, so it keeps growing under the surface.

  • More articulate risk reporting can create false comfort.

Relationships

Connected signals

Related failure modes, decisions behind the signal, response playbooks, and neighboring red flags.