Operator
Executive Operator.
This page is the working interface: how I show up, how decisions get made, and how work gets shipped without noise.
The promise
- • I run situation assessment fast, align the room, then ship a plan that survives contact with reality.
- • Top-down clarity, bottom-up execution. Hands-on where it matters.
How I operate
A simple loop. Repeated until the week stops breaking.
Diagnose
Reality check: constraints, where truth is hiding, what’s breaking the week.
Align
Priorities, decision rights, cadence, and the smallest set of outcomes that matter.
Design
System shape + team shape: measures, gates, and kill criteria before build starts.
Ship
Timeboxed sprints, artifacts, ownership, unblockers. No delegation of ambiguity.
Compound
Retros, playbooks, automation, handover. Improvement is logged, not implied.
What you get (exec-coded)
Week 1
- • Situation map (one screen) + primary constraint
- • Risk register + failure modes
- • First 10 moves (sequenced, owned, timeboxed)
Weeks 2–4
- • Operating plan + cadence that actually runs
- • KPI stack (few metrics, real ownership)
- • Delivery rhythm + proof posture (what gets logged, where)
Month 2+
- • Team enablement + decision hygiene
- • Systemisation (templates, playbooks, automation boundaries)
- • Scale posture: fewer unknowns, faster recovery when things break
Note: details vary by stack and team. The loop stays constant.
How I work with teams
- • I coach leads, not just tasks.
- • Cross-functional alignment is a product.
- • I push decisions to the edge, but I’m accountable for outcomes.
- • Cadence is governance: what gets reviewed weekly becomes real.
Where I go hands-on
- • I’ll write, model, prototype, and QA when speed matters.
- • I don’t delegate ambiguity.
- • If it can’t be logged, it can’t be trusted.
Fit
For
- Founders and operators who need clarity, cadence, and execution discipline
- Retail and commerce teams with leaks (stock, data, handoffs, decision drift)
- Creator-led businesses needing repeatable release systems and retention loops
- Platforms needing deterministic rails (events → comms → audit) with guardrails
Not for
- Deck-only strategy with no build follow-through
- “Autonomous AI” theatre without logs, observability, or rollback posture
- Teams without decision-maker access (no owner, no outcome)
- Vendor sprawl as status (new tools with no ROI case)
Working principles
- • Truth over comfort.
- • Constraints are strategy.
- • Systems beat heroics.
- • Velocity with auditability.
- • Clear owner, clear outcome.
Engagement modes
Three ways to start. All timeboxed. All end in something real.
Operator Diagnostic (timeboxed)
Fast clarity. Ends in a plan you can run.
- Situation map + constraints
- Risk register + failure modes
- First 10 moves (sequenced, owned, gated)
Advisory Sprint (2–4 weeks)
A small number of high-leverage changes shipped with proof.
- Cadence + decision rights installed
- One or two modules shipped (e.g. Cadence + Proof)
- Handoff notes + operating discipline
Fractional Operator (ongoing)
When the system needs to stay tight and compounding.
- Weekly cadence + accountability loop
- Incremental hardening + guardrails
- Proof logging + iteration discipline
Start
If you want a calm operator who can also build: send a short note with current stack, primary constraint, and what must be true in 30 days.
Proof over promises. Timeboxed by default.