Both – but in different ways. Juniors get structure and guardrails. Seniors get a fast alignment tool: checklists and frameworks that prevent re-learning the same lessons under pressure.

Start with your current pain. Pick one problem (scope creep, milestone slipping, messy handoffs, unclear Definition of Done), fill one spread, and use it in your next meeting. The pages are written so you can apply them without needing a sample answer.

No. It’s useful for individual contributors too – designers, programmers, artists, QA, and anyone who wants clearer scope, cleaner handoffs, and fewer “what did we decide?” moments. You can use it to prepare for meetings, surface risks early, and document decisions in a way that makes collaboration easier.

No. Jump to the page you need for the problem you’re solving today.

No. It complements them by helping you make better decisions before you create tasks – so what you put into your tools is clearer and easier to execute.

It’s written for gamedev, but it also fits software and product teams working cross-functionally – especially where scope, milestones, risks, and alignment matter.

Execution-first. Store pages, messaging basics, launch/post-launch hygiene, and practical checklists. It’s not an advanced UA/retention or analytics handbook – the focus is on what many teams skip and later pay for.

Because it’s meant to be a desk tool. Physical use is the point: open it, write, flip pages, and keep it present during planning and meetings. A digital version would become just another file.

Paperback is lighter and cheaper. Hardcover is sturdier for daily desk use.