协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
qbr-deck【开发与工程】Build a Quarterly Business Review (QBR) deck structure and narrative for a customer account. Use when asked to prepare a QBR, business review meeting, executive review, or quarterly check-in with a customer. Produces a slide-by-slide QBR structure with talking points, metrics review, value narrative, and mutual next steps.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Produce a complete Quarterly Business Review deck — structured, data-backed, and customer-focused. A good QBR demonstrates value delivered, aligns on goals for the next quarter, and strengthens the executive relationship. It should never feel like a product demo or a vendor update.
Ask for these if not already provided:
[Quarter] [Year] Business Review
Date: [Date] | Location / Call link: [TBC] Customer attendees: [Names and roles] [Your company] attendees: [Names and roles]
| Time | Topic | Owner |
|---|---|---|
| 0:00 | Welcome and introductions | CSM |
| 0:05 | [Last quarter] — how did we do? | CSM + Customer |
| 0:20 | Value delivered — business impact | CSM |
| 0:35 | What's coming — roadmap preview | CSM / Product |
| 0:45 | [Next quarter] — goals and priorities | Customer |
| 0:55 | Actions and mutual commitments | CSM |
| 1:00 | Close |
Talking point: "We've kept today to 60 minutes. We want as much of this to be a conversation as possible — please push back, redirect, and ask questions throughout."
Partnership snapshot:
Talking point: "Before we dive in — a quick picture of where we are. [X] months in, [Y] active users, and this is our [Nth] QBR together."
| Goal | Set in [Last QBR / Kickoff] | Status |
|---|---|---|
| [Goal 1] | [What we committed to] | ✅ Achieved / ⚠️ Partial / ❌ Missed |
| [Goal 2] | [What we committed to] | ✅ Achieved / ⚠️ Partial / ❌ Missed |
| [Goal 3] | [What we committed to] | ✅ Achieved / ⚠️ Partial / ❌ Missed |
For any partial or missed goal: state what happened and what changes next quarter.
Talking point: "Let's start with accountability. Here's what we said we'd achieve last quarter — let's be honest about where we landed."
Quarter-over-quarter trend:
| Metric | [Q-1] | [Q] | Change |
|---|---|---|---|
| Monthly active users | [N] | [N] | +/-X% |
| Sessions per user per week | [N] | [N] | +/-X% |
| [Key feature 1] adoption | [X]% | [X]% | +/-X% |
| [Key feature 2] adoption | [X]% | [X]% | +/-X% |
Highlights:
Opportunity:
Talking point: "Usage is [up / stable / something we want to talk about]. The area I'd like to focus on is [feature] — we're not seeing the adoption we'd expect given [their goal], and I want to understand why."
Lead with outcomes, not activity.
[Outcome 1: customer's primary success metric]
[Outcome 2]
[Outcome 3]
Customer evidence (use if available):
"[Quote from champion or user about value experienced]"
Talking point: "This is the section I most want your input on. Are these the outcomes that matter to your business? Are there other ways you're measuring success that we should be tracking?"
| Metric | This quarter | Last quarter | Trend |
|---|---|---|---|
| Tickets raised | [N] | [N] | ↑ / → / ↓ |
| Average resolution time | [X hrs] | [X hrs] | ↑ / → / ↓ |
| P1 / critical issues | [N] | [N] | ↑ / → / ↓ |
| CSAT score | [X/10] | [X/10] | ↑ / → / ↓ |
Notable issues this quarter:
What we're doing differently:
Focus only on what's relevant to this customer's goals. Do not dump the full roadmap.
| Feature / Improvement | Expected | Why it matters to [Account Name] |
|---|---|---|
| [Feature 1] | [Q+1] | [Direct link to their goal or pain point] |
| [Feature 2] | [Q+1 / Q+2] | [Direct link] |
| [Feature 3] | [H2] | [Direct link] |
Talking point: "I've filtered the roadmap to what I think matters most to your team. I'd love your reaction — are these the right priorities from your perspective?"
Customer input section — facilitate, don't present.
Prompt questions:
Capture live:
| Goal for next quarter | Owner (customer) | How we'll support it | How we'll measure it |
|---|---|---|---|
| [Goal 1] | [Name] | [CSM / product action] | [Metric] |
| [Goal 2] | [Name] | [CSM / product action] | [Metric] |
[Your company] commits to:
[Account Name] commits to:
Next touchpoint: [Date of next check-in or mid-quarter review]
This skill ships with support files — use them when they are available:
references/value-narrative.md — The QBR Value Narrative: Their Numbers, Not Your Features. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.templates/qbr-outline.md — a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.Score any output of this skill before handing it over; 32+ is ship-quality.
| Dimension | 0 | 5 | 10 |
|---|---|---|---|
| Outcome framing | Value slide is product activity (logins, sessions, features shipped) dressed as impact | Business outcomes present but unquantified, or quantified in vendor units rather than the customer's own metrics and currency | Every value claim is a before/after in the customer's units (hours, spend, attrition, £/$), and shaky attribution is disclosed rather than claimed |
| Accountability honesty | Last quarter's goals missing, or every goal quietly marked achieved; problems and escalations omitted | Goals graded but misses lack a cause and a changed plan; support issues mentioned only in passing | Every goal graded ✅/⚠️/❌ with cause and corrective plan for misses, and the quarter's worst moment (outage, escalation, disputed number) gets its own airtime with what changes next |
| Customer airtime & facilitation | Deck is a one-way vendor presentation; no customer input sections | Agenda nominally includes customer slots but talking points don't actually hand over the floor, or airtime totals under 20 minutes | Customer holds 20+ minutes by the agenda, the goals slide is pure facilitation with prompts and a live-capture table, and multiple talking points explicitly invite pushback |
| Commitments & relevance | No mutual commitments; roadmap is a full product dump | Commitments exist but are vendor-only or undated; some roadmap items lack a link to this customer's goals | Both sides own named, dated commitments, every roadmap row states why it matters to this account, and a next touchpoint is booked before the deck ends |