THE OPERATING SYSTEM
Ambition needs an architecture strong enough to carry it.
This is the evolving system behind Project 63 and my wider work: how priorities become sessions, sessions become evidence, and evidence changes the next plan.
Direction
Start with the mission, current season and the small number of outcomes that deserve protected time.
Allocation
Translate priorities into 90-minute focused sessions so ambition becomes a finite, visible commitment.
Execution
Define the exact output before starting, remove distractions and protect one demanding block at a time.
Documentation
Capture decisions, lessons, evidence and unfinished questions while they are still useful.
Measurement
Track behaviours and outputs separately. Effort matters, but it is not automatically a result.
Review
Compare plan against reality, diagnose the constraint and change the system without lowering the truth standard.
Recovery
Sleep, food, movement and margin are part of performance. A plan that destroys recovery is not premium execution.
Publishing
Turn useful lessons into videos, writing, graphics, newsletters and resources without pretending to know more than the evidence supports.
Compounding
Choose work that strengthens reusable capabilities: research, sales, communication, product, software and leadership.
THE SYSTEM EXPLAINED
Project 63: Goals and Non-Negotiables
The complete explanation of the goals, standards and daily non-negotiables behind Project 63.
Ambition becomes useful only when it is translated into visible standards and repeatable actions.Watch directly on YouTube
THE INTERNAL CODE
Twelve principles inside the system they control.
The separate Principles page has been consolidated into the Operating System so each decision rule sits beside the architecture that applies it.
Start before certainty
Action reveals information preparation cannot. Begin with a serious first version, then let reality improve the plan.
Standards over moods
A system must work on ordinary days. Motivation can help, but it cannot be the operating model.
Evidence over claims
Finished work, customer feedback, measurable learning and honest results matter more than sounding ambitious.
Research before noise
Understand the audience, problem, context and constraints before producing more content, software or strategy.
Useful work earns attention
Attention should be a consequence of value, clarity and proof—not the main objective.
Long-term, today
Think in decades, but convert the mission into one clear action that can be completed now.
Review without ego
Separate identity from results. Missed targets are information when examined honestly.
Build connected capabilities
Sales, writing, design, technology, health and leadership should compound into one stronger system.
Technology should remove friction
A feature is valuable only when it makes an important outcome easier, clearer or more reliable.
Character is infrastructure
Truthfulness, courage, humility, discipline and service determine what can be sustained under pressure.
Share the real lesson
Document the decision, mistake and adjustment—not only the polished result.
Leave the system better
Every project should improve the process, knowledge or tools available to the next project.
THE FOUR-QUESTION TEST
Before a major decision, ask:
Does this create real value?
What evidence will prove it?
Which capability will it develop?
Does it move the long horizon forward?
