How PXF™ Works
Advance on evidence. Never on the calendar.
PXF™ moves through five phases. A phase ends when its exit test is met — which sometimes means a phase takes longer than anyone hoped, and sometimes means it ends early.
- 01
Prepare
Before the clock startsName the end state, name the owners, and agree what evidence will count. Nothing is installed yet.
Exit test
The end state is written in one sentence, and every outcome under it has one name against it.
- 02
Crawl
Install, earlyThe Five Tools go in on real work — not a pilot, not a sandbox. The advisor is in the room.
Exit test
Two consecutive Weeklies run to standard and every closure that week carried a proof line.
- 03
Walk
Install, middleThe team runs the rhythm. The advisor watches, corrects, and steps back further each week.
Exit test
The rhythm holds through a disrupted week, and flags cleared inside the escalation window.
- 04
Run
Install, lateThe team runs it without prompting, including when the founder is absent.
Exit test
A full cycle runs to standard with no advisor intervention and no founder unblocking.
- 05
Certify & Adapt
After the installThe system is demonstrated, verified against a second source, and adapted to how the business actually changes.
Exit test
A witnessed, dated demonstration on the record.
The Four Rules of the Install
Short, unpopular, and non-negotiable.
These are the rules that make the rest of it work. They are also the rules a business is most tempted to bend in week three.
One owner per outcome
Shared ownership is not ownership. If two names appear, the outcome is split until one name remains.
Proof before closure
A commitment does not close on a verbal assurance. It closes against evidence. Overrides are allowed — and recorded.
Escalation on a clock
A flag that is not cleared inside the agreed window escalates automatically. Silence is not a resolution.
Advance on evidence, not on the calendar
A phase ends when its exit test is met. Time passing is not an exit test.
Why execution, not strategy
The honest hours price
Under five person-hours a week.
That is the whole operating cost of PXF™ once it is in: the Weekly, keeping the Common Operating Picture current, and the small amount of writing it takes to close work against evidence.
If it is costing your team meaningfully more than that, the configuration is wrong and we fix the configuration. We do not ask people to absorb it.
The charter
What we commit to, on our side.
We will not add a meeting you do not need
The Weekly usually replaces something. If the calendar gets heavier, the configuration is wrong.
We will tell you what we actually found
Including the parts that are uncomfortable, and including when the constraint is the owner.
We will build ourselves out of the job
Every phase transfers more of the running to your team. Dependency is a failure mode, not a business model.