Manager conversation scripts

“What happens to my career?”

Private one-to-one, 45 minutes, before the restructuring announcement.

1. Open honestly: “I want to be straight with you. This restructuring is going to change your role. Your span of control will shrink. Some managers see that as a demotion. I want you to see it as an upgrade. Can I walk you through how?”
2. Show the three new roles: Pod coach, guild steward, career growth partner.
3. Ask: “Which of these three new roles excites you most? And which one scares you?”
4. Listen: Do not interrupt. Let them vent if needed.
5. If they fear losing authority: “In the old model, your authority was about approval. In the new model, it is about influence: coaching engineers, shaping standards across the guild, and growing people's careers. Which one actually matters more to you?”
6. Close the loop: “I'm not asking you to accept this blindly. I'm asking you to help design how the guilds run. I'd rather have you as a co-architect than a passenger. Will you join me in designing this?”

Their answers: write them somewhere private. The studio keeps no notes about people.

“We can't afford a QA on every pod”

Group meeting with functional managers.

1. Draw the value stream map: On the whiteboard: the lead time and the touch time.
2. Run the numbers: “Sharing QA across three teams saves us $____ a month in QA salary. But waiting for QA delays our features by ____ days on average, at $____ a week in Cost of Delay. We're losing $____ a month to save $____.”
   QA salary saved a month Days waiting for QA Cost of Delay a week Features waiting for QA a month

   Type the four numbers and the line fills itself in. Get the Cost of Delay from Card 2.

3. Make the ask: “I'm not asking you to hire more QA. I'm asking you to let QA sit inside the pods, teaching developers to write better tests. Same headcount; a much shorter queue.”
4. Offer a trial: One pod with dedicated QA, one shared. Measure DORA metrics and Cost of Delay for 30 days, and let the numbers decide.