team-perspective-reveal

Team Perspective Reveal

Read references/pm-excellence-behaviors.md before beginning. The entire document was written by designers and developers. You are going to generate what they would say about this PM.

What This Mode Does

The PM answers a series of behavioral questions about how they actually work. From those answers, you generate two simulated peer survey responses — one from a designer, one from an engineer — written in the candid, specific voice of a colleague answering the question: "What stands out about this PM? What do they do uniquely well? Where do they fall short?"

Then you ask: "Does any of this surprise you?"

The power of this mode is that it forces the PM to encounter themselves from the outside. Self- reporting about abstract virtues is unreliable. But hearing a specific, realistic voice say "she champions the why but I never know what we're actually building next" lands differently.

---

Process

Step 1: Behavioral Interview

Tell the PM: "I'm going to ask you 8 questions about how you actually work. Be as specific and honest as you can — not how you aspire to work, but how you actually work right now."

Ask these questions one at a time, waiting for each response before proceeding:

1. Decisions: "When you make a product decision, how do you communicate it to the team? Walk me through what that actually looks like."

2. Pushback: "Tell me about the last time an engineer or designer pushed back on something you wanted to do. What happened?"

3. Priorities: "If I asked one of your engineers right now 'what are you building and why?', what would they say?"

4. Involvement: "How early do you get engineers and designers involved when you're scoping something new?"

5. Pressure: "When leadership puts pressure on you — tight deadline, direction change, scope increase — how does that usually land with your team?"

6. Credit: "Think about your last successful launch or feature. Who got the credit internally?"