Delivery Reset Workshop
See exactly where your delivery breaks — flow, not story points — and leave with the two or three changes that fix it, sequenced. One facilitated session with your engineering leaders, run by the operators who stood up DORA inside AB InBev's global transformation.
A facilitated working session · modular (a core day, with optional pre-work and follow-up) · on-site or remote · run personally by Bernhard & Adrianna — the operators who instrumented delivery at AB InBev (DORA, ~30% analyst productivity uplift) and mentored engineering managers to run the rollout once we left.
What you walk out with
- An honest read on where delivery actually breaks. Where work stalls between commit and production — handoffs, review queues, environments, unplanned work — not a velocity chart.
- The two or three changes that move it, sequenced. Not a 30-item backlog of "agile best practices" — the few interventions that actually shorten lead time, in order.
- A one-page reset plan with named owners. Who changes what, by when, so the session ends in commitment rather than a retro board.
- Your engineering leaders sharing one picture of the problem. Often the first time the whole leadership group agrees on what's actually wrong — which is half the fix.
How the session runs
- A facilitated core day. The anchor: your engineering leaders in one room (or one call), both principals facilitating, walking out with the reset plan.
- Optional pre-work. A light DORA / flow data pull or short team interviews, so the day starts from evidence instead of opinion.
- Optional follow-up. A second session a few weeks later to check the changes are landing and adjust as the numbers move.
- Both principals, personally. Bernhard and Adrianna run it — two senior operators who have held the seats, not a junior agile-coaching team.
The lens: flow over activity
Most delivery problems are diagnosed by counting activity — story points, velocity, how busy everyone looks. We look at the opposite: where the work actually stops moving on its way to production, and how long it waits there. Measure what ships, not what's busy. That's the same discipline behind our delivery-layer work underneath AI and digital programmes — applied to your delivery in a single room.
Ideal for
- A CTO or VP Engineering whose delivery keeps slipping and who needs to know which layer the problem actually lives in.
- A Head of Delivery being pushed to commit to dates they don't trust, who wants a defensible read before they sign up.
- An engineering leadership team that disagrees on what's wrong — and needs to get aligned before spending on a fix.
- A team about to scale, who wants the delivery basics to hold before adding people and surface area.
Where this comes from
This is the delivery-diagnosis discipline we've run inside real mandates, productised into a session. We instrumented delivery and stood up DORA as the engineering scorecard inside AB InBev's global transformation (~30% analyst productivity uplift), then mentored the engineering managers to keep it running after we left. See four engagements with real numbers →
Workshop, diagnostic, or full engagement?
Three doors, depending on what you need. This workshop is the fastest: a facilitated session that gets your leaders aligned and produces a sequenced reset. The Delivery & AI-Readiness Diagnostic is a two-week, evidence-based read when you want the numbers audited before you act. Agile Engineering & Delivery Performance is the full engagement when you've decided to fix it — DORA baseline, a pilot squad, and engineering managers mentored to run the rollout. The workshop is a clean way to start; nothing locks you into the rest. Setting AI direction instead of fixing delivery? That's the AI Strategy Workshop.
Common questions
What is the Delivery Reset Workshop?
A facilitated working session for engineering leaders that finds where your delivery actually breaks — where work stalls on its way to production — and produces a sequenced plan of the two or three changes that fix it, with named owners. A reset your leadership team agrees on, in a day, not a quarter.
What's the format, and how long is it?
Modular. The anchor is a single facilitated core day, on-site or remote, with optional pre-work (a light DORA / flow data pull or short team interviews) and an optional follow-up session a few weeks later. We scope it to your situation on a short call first.
Do we need DORA data or metrics in place first?
No. If you already track DORA or flow metrics, we'll use them. If you don't, the optional pre-work can pull a quick baseline, and the session works from your team's own account of where things stall. You don't need a measurement stack to start.
What do we actually walk out with?
An honest read on where delivery breaks, the two or three highest-leverage changes sequenced, a one-page reset plan with named owners, and an engineering leadership team that finally shares one picture of the problem. A decision and a plan, not a retro board.
How is this different from the diagnostic and the full engagement?
The workshop is the fast, facilitated start — alignment and a reset plan in a day. The diagnostic is a two-week, evidence-based audit of delivery and AI-readiness. The full Agile Engineering engagement is the build: DORA baseline, a pilot squad, and engineering managers mentored to run the rollout. Many teams start with the workshop and only go deeper if the reset warrants it.
What does it cost?
It's scoped to the format you need — a core day, with or without pre-work and a follow-up — so we price it on a short call once we know the shape. Send a line on your situation and we'll come back with a fixed number, not an open-ended day rate.