12. The Implementation Playbook

This chapter is how to actually stand up an organisation that runs in perpetual beta. One caveat first, carried from Chapter 2 — this is a playbook, not a recipe. The work is complex, not complicated, so treat what follows as a starting structure you adapt as you learn, not a sequence you execute on faith.¹

Start with an honest assessment

Before you change anything, map how innovation actually happens in your organisation today — or fails to. Assess the three dimensions candidly: the people (skills, culture, willingness to collaborate), the process (how an idea travels from conception to production, and what it is measured by), and the technology (the tools and data that enable or block the work). Surveys, interviews, and a plain audit will surface the real pain points, and they are usually specific: ideas from frontline engineers rarely reach anyone who can fund them; development is slow and siloed; nobody can say whether a given project ties to the strategy. Give the assessment a fixed shape and a clock — roughly three months: form the team and the stakeholder map, audit capability across people, process, and technology, then run vision workshops to turn the findings into a direction leaders will own. And read readiness at three levels, because they fail differently. At the micro level: do individual teams actually have permission to experiment, or only the language of it? At the meso level: are code reviews and sign-offs enabling the work or blocking it? At the macro level: is there a tech radar, a way the organisation notices what is coming at all? A blockage at any one level will stall the others, and naming which level is broken tells you where to start. You cannot plan a route without knowing where you are standing, and most organisations are standing somewhere less flattering than their slides suggest.