Execution playbook

Q1-Q2 2026 / Founder operating system

Founder OS

Move uncertainty out of your head and into the world. Produce evidence, protect the system, and restart quickly.

Jump to the daily sheet See the Q2 reset
Buckets remove pressure. Goals create evidence.
Habits stabilize the system. Tasks serve the week.
Section 01
01

Operating doctrine

Founder OS measures progress by evidence, not effort. These commitments are enforcement mechanisms, not aspirations.

Commitments

  • Optimize for external signal, not internal clarity.
  • Plan at two levels only: quarter and week.
  • Do not judge a week by hours, mood, or task count.
  • Protect the system before you push output.
  • Explicitly end goals, buckets, and experiments.
  • Allow ambition without pressure through a parking lot.
  • Never confuse movement with progress.

Non-negotiables

  • Maximum three weekly objectives.
  • Maximum one outreach-heavy objective each week.
  • At least one stabilizing habit lands four or more days per week.
  • The weekly review happens even during bad weeks.

Default question

"What evidence will exist by Sunday night that did not exist last Sunday?"
Evidence definition Valid evidence: user response, usage, payment attempt, shipped artifact, documented decision.
Not evidence: planning, reading, thinking, feeling productive.
Disconfirming evidence still counts. If something fails fast, the system is working.
Section 02
02

Core vocabulary

Each term below has a strict meaning. Do not let the words drift.

Goal
A 13-week outcome that must produce external evidence and end in a keep, reframe, or kill decision.
Weekly objective
A one-week outcome that creates evidence toward a goal. Write it as outcome plus constraint.
Evidence
An external, observable signal that reduces uncertainty. Planning and thinking do not count.
Bucket
A finite experience that supports the quarter without defining success. It is allowed to remain unfinished.
Habit
A repeatable stabilizer that can survive bad weeks. It cannot be aspirational theater.
Target
An action that directly causes today's goal. Critical targets must make the goal 80 percent or more likely. If they do not, they are noise.
Task
A discrete action in service of a weekly objective or a bucket. Tasks are not meaningful on their own.
Parking lot
A safe container for ideas that are not active. Nothing there affects weekly success or self-worth.
Day type
A declared mode of operation. A good day obeys its rule instead of maximizing volume.
Stabilizer
Anything that prevents system degradation: sleep, admin closure, recovery, or environment reset.
Noise
Activity that feels productive but produces no evidence. The system is designed to filter it out.
Section 03
03

Q1 2026 goals

Three goals. Each ends in a decision. No goal continues without evidence.

1
Startup / venture building

Venture exploration

End state
Keep / reframe / kill

Milestones

  • Weeks 1-3: lock ICP and problem framing, then run 10-15 conversations.
  • Weeks 4-8: get a narrow product into the hands of 10 or more real users.
  • Weeks 9-13: synthesize the signal and write the decision memo.

Anti-goals

  • No scope creep to make the thing look impressive.
  • No continuing without evidence.
  • No redefining success after the results come in.

Valid evidence

  • Three to five real discovery conversations completed.
  • One synthesized insight document exists.
  • An MVP is used by at least one external user.
  • A clear keep, reframe, or kill decision is written down.

Not evidence

  • Feature planning or refactoring.
  • Reading about product-market fit.
  • Internal confidence.
2
Systems / founder OS

Sustainable daily operating rhythm

Target
30 consecutive days

Milestones

  • Weeks 1-2: define the rhythm and minimum viable day.
  • Weeks 3-6: stabilize the rhythm with only minor weekly adjustments.
  • Weeks 7-13: complete a 30-day streak without burnout.

Anti-goals

  • No all-or-nothing thinking.
  • No punishing low-output days.
  • No endless system redesign.

Valid evidence

  • Thirty consecutive days using the system.
  • 80 percent or better tier-one habit adherence.
  • Weekly reviews completed, even during dips.
  • Fewer system-avoidance days over time.

Not evidence

  • Feeling motivated.
  • Perfect routines or ideal mornings.
3
Income / leverage / optionality

High-leverage income asset

Constraint
<= 10 hours / week

Milestones

  • Weeks 1-3: define asset type, buyer, and core promise.
  • Weeks 4-8: build it, price it, and make it public.
  • Weeks 9-13: evaluate demand and decide what continues.

Anti-goals

  • No synchronous delivery or disguised hourly work.
  • No expanding scope to justify weak demand.
  • No continuing if it consumes more than 10 hours per week.

Valid evidence

  • A scoped offer exists publicly.
  • At least one pitch is sent.
  • At least one payment attempt happens.
  • A reusable artifact is created.

Not evidence

  • Polishing or waiting for inbound.
  • Over-customization.
Section 04
04

The bucket list

The bucket list is not a productivity tool. It is a psychological load balancer that reduces ambient anxiety and allows non-optimized human experiences during intense execution cycles.

If goals answer "What must move?" and habits answer "What must repeat?", the bucket list answers "What must be allowed?"
Closure
Closure

Remove invisible mental tabs. These are releases, not improvements.

  • Close one unresolved financial uncertainty.
  • End one ambiguous obligation with explicit closure.
  • Make one final decision on a deferred option.
Test: Will this stop quietly draining me once it is done?
Energy
Energy

Restore nervous system capacity. These are non-instrumental experiences.

  • A full day where nothing is optimized or recorded.
  • Time in a space without an agenda.
  • Sleep and meals without structure.
If it becomes useful, it no longer qualifies.
Identity
Identity

Rebuild self-trust through one irreversible signal.

  • Kill a project decisively without reopening the loop.
  • Deliver something small without over-polishing it.
  • Hold a boundary that costs short-term optionality.
Identity is not repetition. Identity is a clear signal.
Optional
Optional

Preserve curiosity without pressure and keep an anti-burnout buffer.

  • Sample something without declaring intent.
  • Learn just enough to satisfy interest.
  • Create without publishing it.
Never scheduled, never reviewed for completion.

Bucket misclassification detector

Run this test on every addition. If an item fails twice, delete it instead of reclassifying it.

1
Does the language include ship, launch, build, grow, numbers, streaks, maximize, or systematize?
Yes -> not a bucket
2
If this does not happen, do I feel behind?
Yes -> goal
3
Will I check this for completion or progress?
Yes -> goal or habit
4
Does this restore energy or demand energy?
Demand -> goal
5
Does it require scheduling or calendar protection?
Yes -> goal or habit
6
Am I hoping this proves something about me?
Yes -> identity, not bucket
7
Kill question: If I were exhausted and behind, would this still be allowed?
Yes -> bucket
One-line test If it creates pressure, proves something, or needs tracking, it is not a bucket. Buckets are permission, not a progress list.
Section 05
05

Day types

Global rule Zero-energy > recovery > execution > peak. You may always downgrade a day. Never push through a lower type. A peak day that breaks tomorrow failed.
Peak execution
Max 2 / week
High energy + clear next step

Three to five focused hours. One objective only. No context switching. Produce one externally legible artifact.

Win: something exists today that did not exist yesterday.
Execution / validation
Moderate energy, partial clarity

Iterate, test assumptions, send follow-ups, refine docs, or review feedback. Progress matters more than polish.

Win: uncertainty is reduced.
Recovery / transition
After peak or mental fatigue

Stabilize momentum and make tomorrow easier. Journaling, review, cleanup, and integration are fine. No new big initiative starts here.

Win: tomorrow is clearer and easier.
Zero-energy / depression-safe
Low mood, fog, avoidance

Prevent spirals. Preserve identity. Walk, shower, eat, clean one small surface, or write one grounding sentence. No catching up.

Win: you did not quit or make tomorrow worse.
Light execution
Low-stakes day

Admin, scheduling, notes cleanup, and prep for the next week. No heavy thinking and no new complexity.

Win: loose ends are closed.
Creative / exploration
Spacious time

Learn, write, read, or explore with no deliverable pressure. Feed curiosity without forcing monetization.

Win: a new insight or renewed interest.
Full recovery
At least once / week

System-level reset. Rest, presence, and non-instrumental time. No planning and no justification required.

Win: energy is replenished.
Section 06
06

Daily execution sheet

This is how a day gets planned and closed. Every field has a rule. Every rule has a purpose.

Day header Declare before you begin
Day type
Peak Standard Low-energy Admin
Energy
___ / 5
Cognitive clarity
Low / Med / High
Gratitude Concrete and present tense only
Good: "A quiet morning with no meetings." "Enough runway to think clearly."
Bad: abstract virtues, future hopes, or performative gratitude.
What would make today great One sentence and within today's control
Good: "Finish my primary block without avoidance." "Get one honest signal from a real user."
Bad: stretch fantasies such as "Ship everything" or "Feel amazing all day."
Today's focus How you work, not what you do

Examples: "Ship over polish." "Evidence over narrative." "Energy protection over output."

Rule: if you have two focus lines, you have none.

Core principle Goal = evidence created. Targets = actions that force that evidence.
If no evidence is produced, the day did not move forward. If targets do not causally produce the goal, they are noise.
Today's goal — outcome layer One goal only. Non-negotiable.

Outcome: _________________________

Why it matters: _________________________

Link to weekly objective or 13-week goal.

Done when: _________________________

Binary completion condition.

Constraint: _________________________

Time, scope, or energy guardrail.

Rules

  • One goal only.
  • Must be externally verifiable.
  • Must produce evidence, not effort.
  • If completed, the day is a win.

Litmus test

"If this is done, can I forgive the rest of the day?"

If no, the goal is too weak or unclear.

Today's targets — execution layer Minimum actions that cause the goal
Critical (1–3 max)
1. ___________________________________________
2. ___________________________________________
3. ___________________________________________
Support (0–2)
4. ___________________________________________
5. ___________________________________________
Closure / recovery (0–1)
6. ___________________________________________
Alignment rule (non-negotiable) If all critical targets are completed, the goal should be 80 percent or more likely to be achieved.
If not, your targets are invalid. Rewrite them.
Goal and target anti-patterns If you see these, start over
Bad goal: "Work on product."
Bad targets: "Research ideas." "Refactor code." "Think about direction."

No outcome, no evidence, no causal chain. Easy to complete without progress.

Valid goal: "Get 3 users to try Mainta CLI and submit feedback."
Valid targets: "Identify 10 target users." "Send outreach messages." "Run 1 onboarding session."

Clear outcome, clear evidence, each target directly causes the goal.

Daily diagnostic Run every day before you start
1Does my goal produce real-world evidence?
2Do my targets directly cause that outcome?
3Can I complete this with my current energy level?
4Am I hiding behind extra targets?
"I do not complete tasks. I create evidence."
Time blocks Primary block first, then support and closure
__:__ - __:__ Primary outcome work
__:__ - __:__ Secondary / support
__:__ - __:__ Admin / closure
Anti-goals Protect execution from disguised avoidance
No rewriting scope after starting.
No consuming content before the primary block.
No adding new ideas to the backlog mid-day.
Belief under test Optional, but useful when you feel noise creeping in

I believe: ________________________________

If this happens, I will reconsider: ________________________________

End-of-day close Facts only. No storytelling.
Priority outcome
Achieved Partial Missed

What moved forward: ________________________________

Energy change: + / 0 / -

Carryover (max 1): ________________________________

Scoring bands
Plan to reality score (0-5)
5
Planned blocks executed and adjustments were conscious.
4
Minor deviations, but the structure held.
3
Partial adherence and the plan was optimistic.
1-2
Significant drift or early abandon.
Win the day score (0-10)
Priority progress (0-4) + plan-reality (0-3) + energy integrity (0-3)
9-10
Model day and sustainable.
7-8
Strong execution with minor leaks.
5-6
Acceptable but needs correction.
0-4
Recovery signal or system breach.
Aligned
Goals map to 13-week outcomes.
Aligned
One true priority exists.
Aligned
Anti-goals are enforced.
Aligned
Energy reality was respected.

Execution quality matters less than system integrity.

Section 07
07

Eisenhower -> Founder OS

The classic matrix assumes stable roles, external deadlines, and clear task ownership. Founder reality needs a different translation.

Old label Founder interpretation Where it routes
Important and urgent
Stabilizers		 Anything that stops bleed or unblocks execution: admin confirmations, health coverage, payment rails. Bucket -> closure or This week's top 3
Important and not urgent
Foundations		 Systems, strategy, identity, and capability. These become goals, habits, or decisions rather than loose tasks. Goal or Habit
Not important and urgent
Noise that feels productive		 The main danger zone. It only survives if it clearly creates evidence for a goal this week. Weekly objective or Delete
Not important and not urgent
Parking lot		 Someday items and soft curiosity. Healthy by design, but irrelevant to weekly self-evaluation. Parking lot

Task -> bucket -> goal -> habit

1
Is this finite and stress-reducing?
Yes -> bucket
2
Does it restore energy or perspective?
Yes -> bucket
3
Does it produce evidence toward a quarterly goal?
Yes -> goal
4
Does it need to happen repeatedly?
Yes -> habit
5
Is it aspirational or just interesting?
Yes -> parking lot
6
None of the above apply.
Delete
Weekly objective formula Weekly objective = outcome + constraint.
Bad: "Reach out to 50 engineers."
Good: "Generate 3 qualified discovery conversations without exceeding 5 hours total."
Eisenhower matrix

Decides what gets done in the short term: triage, noise removal, and daily prioritization.

Founder OS

Decides who you are becoming: quarterly direction, identity alignment, and energy protection.

Founder OS v2
Q2 2026
Survivable system
You are not trying to be consistent for 13 weeks. You are designing a system that survives 13 weeks of inconsistency.
Primary KPI: re-entry speed. Restart within 24 hours.
Q2 / Section 01
D

System diagnosis

The Q1 failure pattern was structural, not moral. The system worked when energy was high and collapsed everywhere else.

Failure mode 1

Over-indexed on ideal execution

Miss one or two days, backlog appears, shame appears, and disengagement follows. The system was too fragile.

Failure mode 2

No degraded mode

There was no clear answer to the question: "I fell off for five days. How do I re-enter in ten minutes?"

Failure mode 3

Journal debt

Catch-up pages turned the journal from a tool into an obligation. Obligation became avoidance.

Core reframe Old: "I need to be consistent for 13 weeks."
New: "I am designing a system that survives 13 weeks of inconsistency."
Inconsistency is not failure. It is the environment your system must handle.
Q2 / Section 02
02

Minimum viable day and system modes

Minimum viable day

A day is a win if all three are completed. Anything extra is a bonus.

1
Output / work
One outreach, one prototype change, or one logged insight.
2
Body / health
Walk, gym, or eat clean.
3
Control / system
Define tomorrow or review the current goal.
MVD complete = day is a win

System modes

You are always in one mode. If you are unsure, default to recovery first.

Peak mode
Max 2 / week

Full journaling, deep work, time blocks, and focused artifact output.

Standard mode

MVD plus one or two additional actions. Keep moving without pushing.

Recovery mode
Default fallback

MVD only. No journaling required. No planning required. No guilt allowed.

When uncertain, always default here first.
Q2 / Section 03
03

Hard rules and execution log

The three hard rules

Rule 1 - no journal debt

If you miss a day, it does not exist. No catch-up and no reopen.

Rule 2 - no backlog thinking

Only operate inside today and this week. The backlog is outside the system.

Rule 3 - act, then write

Execution comes first. Writing is secondary and optional.

Execution log

One line per day. No narrative, no catch-up, no pressure.

Valid formats "Spoke to X -> learned Y"
"Shipped feature Z"
"No progress, but walked and reset"
Recovery days can simply say: "MVD only (reset day)"

Weekly system

Q1What am I testing this week?
Q2What counts as evidence?
Q3What is the smallest version of success?
Q2 / Section 04
04

Q2 goals, reframed

Same three goals, but cognitively lighter. Measurement is evidence-only and perfection is not required.

Goal 1 / venture

Product validation

Ship something and get real user signal.

Measure: weekly evidence from conversations, usage, or value exchange.

Goal 2 / rhythm

Operating rhythm

Maintain an MVD streak instead of chasing perfection.

Target: 70 percent or better of days with MVD complete.

Goal 3 / income

Income asset

Build one low-maintenance income path.

Constraint: must stay under 10 hours per week and show real demand.

Anti-shame protocol

This is not motivation advice. It is an operating protocol for the moment you fall off.

Do not
  • Reflect deeply on why you fell off.
  • Analyze the failure in place of action.
  • Catch up journals or missed days.
  • Redesign the system mid-emotion.
Do immediately
  • Complete the smallest possible MVD right now.
  • Write one execution-log line.
  • Continue forward with no backfill.
Identity shift Old identity: "I am someone trying to be consistent."
New identity: "I am someone who restarts quickly."
Missing days is expected. Restarting is the only requirement.
Q2 / Section 05
05

Comparison framework

Comparing your worst internal moments to someone else's mythologized peak identity produces net-negative execution. The comparison model is broken.

You are comparing your worst moments against their polished peak identity. That guarantees perceived inadequacy and system disengagement.

The core error

Them
You right now
Decades of compounding
Early or transition phase
Teams, leverage, capital
Solo execution
Refined operating systems
Still building the system
Survivorship bias
Real-time struggle

Tier separation model

Tier 1 / legends

Do not compare daily

Use famous operators for long-horizon inspiration or system extraction only.

Tier 2 / your phase

Correct comparison

Your benchmark is MVD consistency, weekly evidence, and re-entry speed.

Tier 3 / daily execution

The only thing that matters

Did I complete MVD today? Did I generate evidence this week?

Comparison interruption protocol

Step 1 / interrupt
Say: "Different stage. Different constraints. Irrelevant comparison."
Step 2 / reality check
  • I am in a system-building phase.
  • They are in a different game or timeline.
  • Comparison is not a useful signal by itself.
Step 3 / extract

Ask: what specific behavior or system can I observe, and what is the smallest version I can apply today?

Step 4 / action
  • Do MVD now.
  • Log one line.
  • Continue.

Peer comparison filter

They are playing: the optimization game of promotion, comp growth, and incremental upside.
You are playing: the exploration and asymmetric-upside game of ownership, leverage, and uncertainty.
1
Is this person actually in the same game?
If not, discard it
2
What specific observable behavior exists?
Name it
3
What is the smallest version I can do today?
Scope it
4
Can I execute it right now inside today's MVD?
Do it now
Anchor statement Old: "I need to perform like them."
New: "I am building a system that compounds like theirs over time."
Q2 / Section 06
06

Daily sheet add-ons

Two additions take under a minute and keep the system from collapsing.

Five-second check The only daily success metric

Did I complete my MVD today?

Yes -> win No -> do it now

The smallest valid version still counts.

Comparison check Ten seconds maximum

Did comparison show up today? Mark yes or no, then force it into an action.

Trigger: ____________________________
Extract: ____________________________
Action today: _______________________
No comparison without a concrete action
Q2 2026 system summary
Upgraded from Q1
  • Primary KPI -> re-entry speed instead of consistency.
  • Journaling -> execution log.
  • Full planning -> three weekly questions.
  • Day types -> explicit system modes.
  • Goal metrics -> MVD percentage and restart quality.
Permanently added
  • Anti-shame protocol.
  • No journal debt rule.
  • Tier separation for comparison.
  • Comparison interruption protocol.
  • Peer comparison filter.
"The system must work on your worst days, not your best days."

Buckets remove pressure. Goals create evidence. Habits stabilize the system. Tasks serve the week.

Missing days is expected. Restarting is the only requirement.