Part III

Building the Product

You are accountable for what the team ships and when. Not what gets built — that's Product's call — but who builds it, how, and when it lands.

Building the product is the part of the job that’s most visible to everyone outside engineering. It’s also the part that new managers are most likely to over-index on, because the signals are clear and the feedback is fast. Don’t let the visibility mislead you: the work in Part II — People & Teams is the one that determines whether this part succeeds.

What this part covers

Five chapters, each one carved out of the old monolithic “Product” chapter:

  1. Product and Roadmap Management — the Onion Model, the Who/How/When framework, roadmap levels, and the PM/Engineering/Sales triangle.

  2. Project Execution — estimation, tools and repositories, tech debt management, postmortems, decision logs.

  3. Engineering Operations — releases, feature flags, on-call, quality and testing strategy, agile methodology.

  4. Communication and Delegation — meetings, upward/sideways/downward communication, managing up, delegation levels, decision-making.

  5. Managing in the AI Era — what coding agents have changed about staffing, performance evaluation, onboarding, and the junior engineer pipeline. Written for where the industry actually is in 2026, not where it was in 2022.

Build the product your customers need, not the product you want to build. Stay close to customers, ship frequently, and iterate based on feedback. Perfect is the enemy of shipped.

Table of contents