What is an operating brief and why does one document generate all the others?

The one genuinely new role. When every document is generated from a single operating brief that a model reads, the owner's job stops being to produce documents and becomes to maintain the context that produces them. Write the brief as if it will be read by something that knows nothing and forgets nothing. Then keep it true. Knowing what to leave out of the context is the same skill the whole collection is about.

How does a product owner's job change when documents are generated?

The one genuinely new role. When every document is generated from a single operating brief that a model reads, the owner's job stops being to produce documents and becomes to maintain the context that produces them. Write the brief as if it will be read by something that knows nothing and forgets nothing. Then keep it true. Knowing what to leave out of the context is the same skill the whole collection is about.

What is context engineering in product work?

The one genuinely new role. When every document is generated from a single operating brief that a model reads, the owner's job stops being to produce documents and becomes to maintain the context that produces them. Write the brief as if it will be read by something that knows nothing and forgets nothing. Then keep it true. Knowing what to leave out of the context is the same skill the whole collection is about.

The owner as context engineer · AI-Driven Product

§Most of what AI changed was a rebalancing: the same work, weighted differently. One change is genuinely new, and it is a change in what the owner's job is. This chapter is about it.

§ 6.1One brief, every document#

§In the field engagement, every document came from the same place. Session agendas, field guides, the prototyping brief, the ladder, the interview synthesis templates, the two-act memo, the value proposition canvases, the business model, the monetization sheet. All of them were generated from a single operating brief that the facilitator maintained and a model read.

§The brief held the cast, the calendar, the deliverables, the voice, the visual identity, the decisions made and the rules. When the calendar changed, the brief changed first and the artifacts were regenerated. When a role changed hands, the brief changed first. When the team decided a business rule, it went into the brief, and every later document already knew it.

§ 6.2What changed in the job#

§For the person who owns , the shift is real and easy to underestimate.

§The old job was producing documents. A field guide took a morning. A strategy deck took two days. A synthesis template was reused from the last engagement and lightly edited. The quality of the work was, in large part, the quality and speed of the writing, which is why the bottleneck sat where the first chapter said it did.

§The new job is maintaining context. The field guide takes a minute to generate and is only as good as the brief behind it. If the brief has the wrong interviewee roles, every guide is wrong. If the brief does not know the team decided tiers are built on visits rather than tokens, the next document will contradict the last one, confidently, in a partner meeting.

§ 6.3The rule that matters most#

§One operational rule from the build days generalizes further than any other, and it is the sharpest lesson about context in the whole collection: upload only the brief, never the guide.

§When the team uploaded both the requirements document and the instructions for how to prompt, the tool treated the prompt instructions as product requirements. It built screens for the process instead of the product. The fix was to give it the requirements alone.

§The lesson generalizes past prototyping tools. Context is not everything you have. Context is the smallest set of true things the next step needs. A 's skill is knowing what to leave out, which is the same skill as strategy's exclusions, the first version's scope, and the experiment chosen from the backlog. The whole collection has been teaching subtraction under different names, and context engineering is subtraction applied to what a machine reads.

§ 6.4Why this is the new craft#

§The previous chapter said generation is additive and product is subtraction. Context engineering is where the owner performs the subtraction that the tool cannot. Feeding a model everything produces a plausible, fluent, wrong output, because the model will honor every stray instruction and fill every gap with an invention. Feeding it the smallest true brief produces output the team can trust, because there is nothing in it to misread and nothing missing for it to invent.

6. The owner as context engineer