A practical guide / Engineering leadership

Help the team ship with a clearer direction.

Connect daily engineering habits to the decisions around them: what to build, how to coordinate, and where a technical leader can remove friction.

Follow the reading path ↓

Start here

Three useful places to begin.

Read in order, or choose the problem closest to your own.

  1. 01

    See the operating workflow

    A documented account of coordinating engineering work with an AI-assisted brief, PR triage, and recurring checks.

    How I Run 3 Engineering Teams with 1 AI Brain ↗
  2. 02

    Make decisions easier to revisit

    Capture the context and tradeoffs around an architectural choice, so the team can understand it after the meeting ends.

    I Taught My AI Agent How to Write Architecture Decision Records ↗
  3. 03

    Protect the space to execute

    Examine the cost of coordination and decide which conversations help the work move forward.

    The hidden costs of meetings ↗

The working principles

Start with the decision that needs to be made

A technical leader helps a team choose what to do next and understand why. Name the constraint before choosing the tool: an unclear product goal, a system boundary that no longer fits, or a delivery process that hides risk until late in the work.

The architecture decision record guide offers a way to keep that context with the decision. The useful output is not a document for its own sake; it is an explanation the next person can inspect and revisit.

Build a view of the work you can act on

A list of activity is different from an account of what needs attention. Look for work that is blocked, changes that need a decision, and operational problems that keep recurring. Make the ownership and next step clear enough that someone can act.

How I Run Three Engineering Teams with One AI Brain describes a specific operating workflow, including its limitations. I Built a Brain with Claude Code explores the coordination layer in more detail.

Keep coordination connected to execution

A recurring meeting should earn its place by helping people make a decision or move work forward. Inspect the cost of interruptions alongside the value of the conversation. Written context can make the discussion more useful, but it does not replace difficult conversations or clear ownership.

The Hidden Costs of Meetings looks at that tradeoff. Pair it with The 200-Line Rule for a smaller, reviewable unit of engineering progress.

From the idea to the work

Give the team a clearer way forward.

Work through architecture, delivery habits, and the engineering decisions that are slowing your team down.

Read the engineering workflow →

Go further

More notes on engineering leadership.

Further experiments, implementation details, and lessons from the work.

Browse all writing →