Before starting a project, cross-reference your success pattern and engineer the conditions in
Cross-reference your success pattern elements against your upcoming project plan before starting work, building in the overlapping conditions deliberately rather than hoping they emerge, as replication requires engineering.
Why This Is a Rule
Having a documented success pattern (Extract your replicable success pattern from 5 fields across your last genuine wins) is valuable only if you use it proactively. Most people extract their success pattern and then hope the conditions happen to be present in their next project. Hope is not a strategy. Replication requires engineering — deliberately building the success conditions into the project from day one.
The cross-reference converts a passive insight ("I succeed when these conditions are present") into an active design step ("I will engineer these conditions into the project plan"). If your success pattern includes "clear first milestone within 48 hours" and "one accountability partner," the project plan must explicitly include both before work begins.
Conditions that can't be engineered (luck, timing, market conditions) are noted as risks. Conditions that can be engineered (team composition, schedule structure, communication cadence) are built into the plan. The cross-reference makes the distinction visible and actionable.
When This Fires
- Before starting any new project, initiative, or significant work effort
- During project kickoff when establishing structure and cadence
- When reviewing a plan and wanting to maximize success probability
- After extracting your success pattern and wanting to apply it forward
Common Failure Mode
Extracting success patterns but never consulting them before new work. The pattern lives in a document you wrote six months ago and haven't opened since. The cross-reference must be an explicit step in your project-start protocol — not optional self-improvement, but mandatory pre-work like budgeting or scoping.
The Protocol
Before starting a new project: (1) Open your documented success pattern (Extract your replicable success pattern from 5 fields across your last genuine wins). (2) List each element. (3) For each: can this condition be built into the project plan? If yes → add it explicitly. If no → note it as a risk factor. (4) Compare: how many success-pattern elements does this project plan include? If fewer than half → redesign the plan to include more. The plan is not just what you'll do — it's the environment you'll engineer to maximize the probability of success.