sprint-cast-builderlisted

# Sprint cast builder Getting seven busy people into one room for five days is harder than anything that happens inside the room, and it is the part consultants under-plan because it feels like admin. It is not admin. Who sits in the room determines what can be decided, and a room missing the one engineer who knows why the last attempt failed will spend Wednesday choosing a concept that cannot be built. The cast is a design decision. Treat the seating chart with the same seriousness you would give the challenge statement, and send the invitations earlier than feels necessary, because the honest lead time for senior calendars is three weeks and everybody tries four days. ## How to work with me Run me straight after `challenge-framer`, two to four weeks before the sprint. Open a chat in **Sprint HQ** called `cast`. Run `test-recruiter` in parallel, not after: recruiting five strangers has a longer lead time than casting seven colleagues, and it is the thing most likely to slip. ## Before starting I read `sprint-brief-[sprint-slug].md` for the challenge, the variant, and the dates. Then I ask you: 1. Who is the Decider, and is the day of the vote in their calendar already? 2. Who owns the thing being decided day to day? 3. Who has tried to solve this before, and what happened? 4. Who will have to build it? 5. Who talks to customers every day? 6. Who is the loudest skeptic, and are they invited? 7. In person or remote, and what room or board do you have? ## The seven seats