C

Values only count when they change the work

The Captain’s Code.

These are the standards for how I build, sell, serve, and lead. They are also the filter for clients, teammates, partners, products, and decisions.

Start here

Origin

A code for the moment the playbook runs out.

The work has always centered on one question: are we building a system that creates freedom, or a job that needs constant rescue?

Tactics change. Tools change. AI changes what can be automated. The standard underneath the work still has to hold when pressure rises, the answer is unclear, or nobody is watching.

The code turns that standard into behavior you can see, expect, and use.

01 / 06

Build Engines, Not Cages

A business should create freedom, not make the owner the permanent bottleneck. We build clear systems that keep working without constant rescue.

Required behavior

  • Design the repeatable process before adding more effort.
  • Document decisions so the work can move without one person in every loop.
  • Use automation to remove friction while keeping a human accountable.

Violates the standard

  • Celebrating busyness while the same problem keeps returning.
  • Building dependencies that trap clients, teammates, or founders.
  • Automating work nobody has understood or approved.

02 / 06

Own the Outcome

Responsibility starts with us. We tell the truth about what happened, take the next useful action, and do not wait to be rescued.

Required behavior

  • Name your part before pointing at circumstances.
  • Raise risks early, with facts and a proposed response.
  • Close the loop and confirm the result.

Violates the standard

  • Blame, excuses, or strategic silence.
  • Waiting for permission to fix an obvious problem.
  • Reporting activity as if it were an outcome.

03 / 06

Stay Curious. Give First

Better questions beat quick assumptions. We share what works, teach what we know, and help before keeping score.

Required behavior

  • Ask enough questions to understand the real constraint.
  • Share useful context, methods, and lessons without making people chase them.
  • Respect the knowledge and contribution of every person in the room.

Violates the standard

  • Pretending certainty when the facts are incomplete.
  • Withholding useful information to protect status.
  • Treating questions as weakness or contribution as rank.

04 / 06

Go All In or Let It Go

A clean no is better than a distracted yes. Once we decide, we bring focused effort and finish what matters.

Required behavior

  • Choose deliberately, then protect the commitment.
  • Give important work the concentration it deserves.
  • Stop, hand off, or remove work that no longer earns commitment.

Violates the standard

  • Keeping half commitments alive out of guilt or habit.
  • Starting new work to avoid finishing the current work.
  • Confusing long hours with focused effort.

05 / 06

Be the Client You Want

Good work is a two way standard. Pay on time. Show up prepared. Do the work. Treat other people’s expertise the way you want yours treated.

Required behavior

  • Arrive prepared and make decisions when decisions are due.
  • Honor agreements, timelines, invoices, and other people’s time.
  • Give direct feedback and do the work you agreed to own.

Violates the standard

  • Moving the target after the work is done.
  • Ghosting hard conversations or making urgency someone else’s problem.
  • Demanding trust while withholding respect.

06 / 06

Bring Solution Energy

Name the problem once. Spend the rest of the conversation finding the move. Optimism matters when it produces clear action.

Required behavior

  • Bring options, tradeoffs, and a recommendation.
  • Use language that keeps the team clear and moving.
  • Stay composed enough to make a good decision under pressure.

Violates the standard

  • Repeating the problem without advancing the conversation.
  • Performing frustration instead of asking for what is needed.
  • False positivity that hides risk or avoids a hard fact.

The daily practice

The Captain’s Standard of Performance

Inspired by Bill Walsh’s Standard of Performance in The Score Takes Care of Itself. These are paraphrased operating expectations, grouped under the six values so they can guide the work instead of living as a disconnected list.

01

Build Engines, Not Cages

  1. 01Pursue constant improvement with an intense, intelligent work ethic.
  2. 02Treat attention to detail as a path to better work.
  3. 03Go the extra distance when the organization needs it.

02

Own the Outcome

  1. 01Let character guide the choice when nobody is watching.
  2. 02Keep self-control, especially when the pressure rises.
  3. 03Take pride in the quality of the effort, regardless of the result.

03

Stay Curious. Give First

  1. 01Respect every person and the value of their contribution.
  2. 02Keep learning, teach what you know, and build real expertise.
  3. 03Act fairly, even when the easier move is not the fair one.

04

Go All In or Let It Go

  1. 01Protect an unusually high level of focus and concentration.
  2. 02Make sacrifice and commitment signatures of the organization.
  3. 03Handle wins, losses, praise, and embarrassment with perspective.

05

Be the Client You Want

  1. 01Make loyalty visible through your actions.
  2. 02Communicate openly and with substance, especially under stress.
  3. 03Put the welfare of the team ahead of personal advantage.

06

Bring Solution Energy

  1. 01Use constructive language and protect a useful attitude.
  2. 02Bring poise, and expect it from the people around you.

Decision filter

Six questions before the move.

When the choice is messy, run it through the code. A strong decision should survive all six questions.

  1. 01

    Build Engines, Not Cages

    Does this create lasting leverage, or another job someone has to carry?

  2. 02

    Own the Outcome

    Am I taking responsibility for the result, including the next move?

  3. 03

    Stay Curious. Give First

    What do I still need to learn, and what can I give before I ask?

  4. 04

    Go All In or Let It Go

    Is this worth full commitment? If not, what should be released?

  5. 05

    Be the Client You Want

    Am I showing up the way I want a client, teammate, or partner to show up?

  6. 06

    Bring Solution Energy

    After naming the problem, what is the most useful move available now?

How we work

The code in practice.

01

Client expectations

We agree on the outcome, owners, decision points, and communication rhythm. Preparation and follow through go both ways.

02

Team standards

Raise the issue early. Own your part. Ask for context. Bring a recommendation. Finish the loop without drama.

03

Product decisions

Choose durable usefulness over feature volume. A product should remove a real constraint and make the next action clearer.

04

Partnerships

Work with people who keep agreements, share credit, speak plainly, and care about the long game more than the quick win.

05

AI approval rules

AI can draft, organize, analyze, and automate. A named human still approves consequential claims, decisions, messages, and actions.

The approval rule is simple: automation can accelerate judgment, but it cannot hide ownership. If the action affects a client, a person, money, access, reputation, or a public claim, a named human owns the final call.

The fit is the filter

If this is how you operate too, we should probably work together.

Bring the real problem, the willingness to do the work, and a commitment to a clear outcome.

Start the conversation