The how-to library, answered in full.

No to either. There is no sign-up, no gate and no fee. All seventeen guides are published in full, with 142 steps written out rather than summarised, and each one carries a worked example, the failure modes and a definition of done. You can copy them, adapt them and rename them to fit the words your organisation already uses, and you owe us nothing for doing it. Publishing the method free is deliberate. Our engagements are built to leave, and a method a team can only run while it is paying for it is not one they can be left with.

The person running a quarter: the product manager, delivery lead or engineer doing the work the operating model asks for, from pricing an outcome to running a team health check. They are operating instructions, not a sales case. If you are evaluating Tenhaw as a buyer, the how-to library is the wrong place to start: read the five priced engagements or the case studies instead, because that is where the agentic work and the evidence for it live.

The full life of a quarter, in five stages that follow the order work moves through the model. Setting up the work covers pricing outcomes, building a quarterly roadmap, writing value-carrying epics, breaking them into stories and running discovery. Writing the work covers stories, chapters, bug reports and the RAID log. Shipping and supporting covers release notes, the first week after a release and root cause analysis. Measuring and managing covers value validation, running delivery day to day and delivering on time. Forecasting and team health covers confidence-interval forecasting and the monthly team health check.

The Tenhaw Way is the operating model in one read: four values, two delivery modes, a quarterly timebox and seven rituals. The how-to guides are the manual underneath it: the seventeen moves the model asks you to make, each written out with the steps, a worked example and the ways it goes wrong. Read the model to decide whether you want to run this way. Open a guide when it is Monday morning and you actually have to make one of the moves.

Because delivery is the method underneath the agentic work, not a separate business. The guides document the operating model Tenhaw engagements install alongside client teams: priced outcomes, quarterly roadmaps and monthly value validation are what turn an agentic build into money the business can see arriving. An agentic system with no loop between built and worked never shows up in the accounts. The agentic work itself lives in the engagements and the case studies; this library is the discipline that makes it pay.

No. The library is written as a manual, not a framework: take what you need. Each guide stands alone with its own steps, worked example, failure modes and definition of done, so a team can adopt the bug report format or the release notes structure without touching anything else. The guides do share a spine: everything traces to a priced outcome, so the further up the stack you go, the more the pieces reinforce each other. Start with the one your week actually needs and let the rest earn their way in.

Yes, they are free to copy, adapt and rename. If your organisation says initiative instead of outcome, or workstream instead of epic, keep your words and take the mechanics: the priced target, the visible arithmetic, the named owner, the monthly validation. What matters is the discipline each guide encodes, not the vocabulary it happens to use. The one renaming worth resisting is any that quietly removes the number, because a level of work that no longer carries currency has stopped being the same thing.

Two of the seventeen: how to measure the value a project delivered, and how to forecast delivery with confidence intervals. The other fifteen change how the work is written. These two change what leaves the delivery organisation: whether the money arrived, and when the rest of it will land. Value validation runs monthly on every live outcome, and it is the ritual most organisations skip, which is why so few can answer what the quarter actually produced. If your board is asking either question, start with those two.

Every guide carries an AI-native note saying exactly what changes, and the arithmetic never does: outcome pricing, epic value shares and the capacity maths read the same in both modes. What changes sits below the epic. AI-native teams stop there, so the outcome ticket itself carries the currency share, the key user journeys and the test requirements, and the three guides on stories and chapters do not apply at all. Gating and forecasting shift with it: an epic is approved on journeys and test requirements rather than an attached story, and throughput is sampled over fewer, larger items.

Operators who install the model alongside your teams and stay until it sticks. Reading a guide and running a quarter on it are different work: an engagement brings people who have run these rituals before, pairs them with your team, and leaves capability behind rather than dependency. The prices are published, from a four-week AI Readiness Audit at £44,000 fixed to a two-person Agentic Design Team at £35k–£55k a month. The same operating model sits underneath the agentic engagements, where it is what turns a build into validated value. The guides stay free either way.

Both. Every guide sets its steps out in full, then works the same move through end to end on a named example. Eighteen examples sit across the seventeen guides, because pricing an outcome carries two: one on a revenue line at an invented retailer, one on an operational cost base at an invented insurer, since a conversion rate teaches you nothing about a claims operation. Each one runs the arithmetic from the baseline and the date it was read through to the condition that would make you call the outcome not realised. The organisations and their figures are invented so the shape can be shown in full. What we have delivered for real sits in the case studies.

Each guide prints its own run time on the index, next to the number of steps, so you can see the cost before you open it. They range from about ninety minutes to raise and triage a bug, through six hours to price an outcome across a few sittings, to about two days for a quarterly roadmap written two or three weeks before the quarter starts. The recurring rituals are lighter than teams expect: value validation is about three hours a month and the team health check about two, each built round a forty-five minute session. Discovery is capped at two weeks, and the default post-release monitoring window is seven days.

No, that is the other half of the method. This library is the delivery side: how work gets priced, planned, written, shipped, measured and forecast. The engineering side lives on Building with AI, which covers treating requirements as the source code and finding the gaps in them before any code is written. The two meet at the ticket. These seventeen guides take a business result down to an approved epic and back up to whether the money arrived, and Building with AI takes that epic into the codebase. Both are published in full, and the two pages sit one link apart at the foot of this index.

For some of them, yes, and not many people beyond that. Pricing an outcome needs whoever owns the reporting system sitting with you while the baseline is pulled, finance's own margin and lifetime value figures rather than your estimate of them, and one named owner senior enough to carry the number in next year's plan. Getting an epic into the quarter needs a product approval and an engineering approval, which is why that guide runs to half a day rather than an hour. The monthly health check needs the whole team scoring privately, and management reading the card unedited the same day.

Partly, and it is worth knowing what you lose. The spine of the library is that everything traces to a priced outcome, so the setup and measurement guides go quiet without one, while root cause analysis and the ticket craft below the epic run exactly as written, since a chapter carries no currency figure by design. Before accepting the position, run the pricing guide once: a baseline pulled from the system that already records it and re-run a week later to prove it reproduces, then one visible line of volume, change, value per unit, margin and period, with margin taken from finance rather than estimated. Often the block is a missing baseline, and then your first epic is instrumenting it.