Andrew Luxem

Project Reviews: Unstick a project by exposing the real decision

A project is stuck, but the review repeats status instead of identifying the unresolved decision, root cause, dependency, or recovery path. This brief shows the mechanism, failure check, and adoption test.

Andrew Luxem
Andrew Luxem
CRM, Lifecycle & AI Strategy

2 min read
The argument
A project is stuck, but the review repeats status instead of identifying the unresolved decision, root cause, dependency, or recovery path.
The skill should unstick a project by exposing the real decision.
Use the format on one at-risk project. Track time to decision, forecast change, and closure of recovery actions.

A project is stuck, but the review repeats status instead of identifying the unresolved decision, root cause, dependency, or recovery path.

The useful response is not another status layer. It is a mechanism that can unstick a project by exposing the real decision.

What the skill produces

The Project Reviews skill turns supplied context into a decision-focused project review with evidence, options, trade-offs, risks, recommendation, owners, and dates. It should expose missing evidence instead of inventing it. The free skill packages this mechanism for explicit use. It does not fetch remote instructions, and the practitioner remains responsible for the facts and final decision.

Run the mechanism

  1. State result versus plan and the material variance.
  2. Trace the root cause and unresolved dependencies.
  3. Present options, recommendation, decision needed, and recovery owners.

The accountable owner reviews the output against the source evidence before it is used. Material unknowns remain labeled and receive an owner and date when they affect the decision.

Failure check

The review fails when it hides the request behind background or assigns a working group instead of one accountable owner.

Adoption test

Use the format on one at-risk project. Track time to decision, forecast change, and closure of recovery actions.

Keep the skill only if the result improves against that baseline. Revise the playbook when the same operating failure survives more than one review cycle.

Infographic

STATUS IS NOT A PROJECT REVIEW infographic
Andrew Luxem
20 years building CRM and lifecycle programs at Amazon, Ancestry, and Stanley Black & Decker.
Next up

One argument like this, in your inbox, on a schedule that respects your time.

Subscribe on Substack