How to use this guide

This guide is for people doing project work — contributors, leads, engineers — not just those managing it formally. You can read it from start to finish, or jump to whatever feels most relevant right now.

It's a way of thinking, not a methodology. It won't tell you to use Scrum or Kanban or any specific methodology. The ideas in this guide work alongside whatever process your team already uses — they're meant to complement it, not replace it.

Some chapters will make more sense when you need them. The first read plants the seed. When a situation at work calls for it, come back to the relevant chapter — that's usually when things click.

The examples are tech scenarios, not tech tutorials. The technical details are kept intentionally light, because they'd date quickly. The thinking behind them won't. Don't get too caught up in the technical setup  — concentrate on the project thinking part instead.