Scope & gate decisions
Is the project ready to advance?
Make evidence sufficiency, assumptions, unresolved contradictions, decision authority, and conditions of advancement visible.
Circular Deduction™ · Project & Program Decision Review
Govern the consequential decisions inside projects and programs.
Project systems manage plans, schedules, costs, risks, deliverables, and reporting. Circular Deduction governs the consequential decisions made with that information.
It is most relevant when capital, vendor commitments, risk acceptance, operational readiness, or hard-to-reverse change are at stake.
Initial fit is infrastructure-heavy and high-consequence work. Circular Deduction supplements—not replaces—project-management frameworks, PMOs, stage gates, risk registers, or accountable governance bodies.
WHERE PROJECT INFORMATION BECOMES COMMITMENT
Schedule
Risk
Technical evidence
Commercial evidence
Governance context
Consequential decision
Commit / Condition / Withhold / Reconsider
Project systems manage the work. Circular Deduction governs the consequential decisions inside it.
The gap
Project controls produce information. Decisions still need governance.
Project information does not authorize action by itself. A material decision still needs an inspectable basis: what evidence supports the action, what contradicts it, which assumptions remain open, who has authority, what is being committed, and what would require reconsideration.
Use Circular Deduction when:
- multiple functions hold different parts of the evidence;
- the recommendation depends on assumptions that are not visible;
- approval authority, execution authority, and risk acceptance are not the same;
- the decision must remain explainable after the meeting is over;
- new evidence may require the organization to reopen the decision.
Decision moments
Apply the method where project information becomes organizational commitment.
The method is most useful before a team spends capital, binds a vendor, accepts residual risk, enters service, approves material change, or closes an incident whose consequences may persist.
Vendor & procurement
What are we actually buying—and why?
Separate scoring, technical evidence, commercial pressure, risk allocation, exceptions, and accountable selection authority.
Who is accepting which residual risk?
Distinguish recommendation from authorization, and make residual risk, owner, conditions, and escalation explicit.
Change decisions
Does the change preserve the original decision basis?
Expose cumulative scope, cost, schedule, technical, and authority effects before incremental approvals become unexamined drift.
Readiness & transition
Is completion evidenced—or merely reported?
Connect commitment to observed state, verification, residual gaps, closure authority, and conditions that prevent premature acceptance.
Incident & recovery
What changed, what held, and what must reopen?
Preserve changing evidence, bounded actions, corrective commitments, verification, and recurrence triggers without treating task completion as proof of resolution.
One method underneath
Frame → Derive → Contradict → Reconcile → Commit → Extract | +1 Reinsert
The 6+1 governed state architecture does not change for project work. The project context changes the evidence, stakeholders, authority, and consequence—not the method. Existing delivery systems continue to manage the work; Circular Deduction governs the consequential decision inside them.
Project management asks whether the work is being managed. Circular Deduction asks whether the consequential decision is sufficiently evidenced, challenged, authorized, committed, and reconstructable.
Bounded entry point
Test the operating value on one consequential decision.
A Consequential Decision Review reconstructs one bounded decision, tests the evidence and authority boundary, and produces a decision package that can be challenged and revisited. It is a contained review step—not a commitment to replace the project system or adopt broader software.
01Decision Reconstruction
What is being decided, by whom, under what constraints, and on what horizon.
02Evidence & Contradiction Map
What supports the recommendation, what conflicts, what is assumed, and what remains materially unresolved.
03Authority & Risk Boundary
Who may recommend, approve, execute, verify, accept risk, and authorize closure.
04Reconciled Recommendation
What still holds after contradiction, including conditions, limitations, and what would change the recommendation.
05Decision Basis Record
A Decision Basis Record connecting evidence, authority, commitments, verification, residual risk, and disposition.
06Reconsideration Triggers
Defined evidence, thresholds, recurrence, or changed conditions that require the decision to be reopened.
Who this is for
Practitioners
Project and program managers, technical leads, procurement teams, operational leaders, and other practitioners who assemble the evidence but should not be forced to carry authority they do not own.
Bring the decision
Start before the next irreversible commitment.
Bring one material decision, why it matters, what is known, where the evidence conflicts, and what a useful decision package must clarify. Sensitive information should wait for an authorized channel.
