Werk 13 — who carries it
Most product failures are not decision failures — the bet was reasonable and it never arrived intact. This werk owns the distance between a decision and a shipped, instrumented increment.
The offer
Product decisions that survive contact with delivery — teams organised around outcomes rather than projects, a release rhythm the business can plan against, and instrumentation that closes the loop from bet to result.
Squads shaped around product outcomes, dependencies made visible, and a release rhythm with a definition of done that includes accessibility, performance and telemetry.
The path from a validated bet to shipped increment, with the artefacts that survive the handover and the rituals that stop discovery becoming a separate department.
Event taxonomy, funnel and cohort reporting wired at build time, so the result of a release is readable within the sprint that follows it.
Internal platforms treated as products with users, adoption metrics and a roadmap, rather than as a mandated toolchain teams route around.
Delivery diagnostic, topology proposal, instrumentation gap list.
Cadence and topology arbitration, coaching on discovery-to-delivery.
The operating model stood up and shipping, with the metric moved.
State of the proof
Experiences that prove it
Sub-capabilities and evidence
Questions
- How is this different from Product & design?
- Product & design decides what is worth building — discovery, research, experience and the design system. This werk is accountable for whether it ships: team shape, cadence, instrumentation and the platform the teams build on. They are usually bought together and they answer to different questions.
- Is this agile coaching?
- No. A cadence is an output, not the point. The point is that a validated bet reaches production with its telemetry attached, and that the team that built it can read the result. Ceremony without that loop is theatre.
- What is honestly not proven here?
- The internal-platform-as-product discipline. It is held by named operators inside platform mandates; no published case is sold on the adoption work in its own right.
- Who should not hire this werk?
- An organization that wants throughput without changing who decides. If the roadmap is set outside the teams that deliver it, a new cadence just makes the queue faster to observe.