DocsUse CasesPlaybooks: Persona Guides

Playbooks: Persona Guides

Use Cases by Department · Beginner Friendly

Decision Velocity, Narrative, and Strategic Focus

Run in Prompt Architect
personafounderceostrategytutorial

Objective: give founders fast, structured clarity for weekly priorities and decision tradeoffs.

1

Weekly Executive Brief

Generate one-page summary of growth, delivery, risk, and burn signals.

2

Top 3 Decisions

Surface only decisions requiring CEO intervention with owner and deadline.

3

Narrative Alignment

Create internal narrative for teams and external narrative for board/investors.

4

Execution Lock

Publish explicit next-week priorities and success criteria.

Best Practices

Start decision velocity, narrative, and strategic focus with a small live pilot and one owner per review lane.

Track decision lead time and initiative velocity from day one.

Bake this control into your checklist: scenario assumptions are visible

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: single-scenario plans presented as certainty.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Decision Velocity, Narrative, and Strategic Focus Owner: Strategy and Transformation Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Put decision deadline and decision owner at top of every strategic draft.

Cross-Functional Throughput and SLA Control

Run in Prompt Architect
personacoooperationsexecutiontutorial

Objective: improve execution reliability across departments with shared workflow contracts.

1

Process Inventory

Map top 10 cross-team workflows with owners and SLA targets.

2

Handoff Contracts

Standardize required fields at each handoff to reduce rework.

3

Exception Routing

Auto-route broken handoffs with severity and owner assignment.

4

Weekly Ops Review

Publish throughput, SLA misses, and corrective actions.

Best Practices

Start cross-functional throughput and sla control with a small live pilot and one owner per review lane.

Track rework rate and cycle time from day one.

Bake this control into your checklist: fallback path exists for common failure states

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: SOP text that reads well but cannot be executed.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Cross-Functional Throughput and SLA Control Owner: Operations Excellence Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Document what to do when data arrives late, not just when it is clean.

Pipeline Integrity, Win Rate, and Commercial Discipline

Run in Prompt Architect
personacrorevenuesalestutorial

Objective: improve forecast confidence while raising win rate on strategic deals.

1

Deal Hygiene

Run weekly deal audits for MEDDIC completeness and stage validity.

2

Forecast Bands

Publish best/base/worst bands with confidence notes and assumptions.

3

Deal Desk Support

Auto-generate negotiation briefs and concession guardrails.

4

Loss Intelligence

Summarize loss drivers and feed into enablement and messaging updates.

Best Practices

Start pipeline integrity, win rate, and commercial discipline with a small live pilot and one owner per review lane.

Track rerun rate per opportunity and stage conversion from day one.

Bake this control into your checklist: claims and numbers are source-backed

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: outreach that sounds polished but could apply to any account.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Pipeline Integrity, Win Rate, and Commercial Discipline Owner: Revenue Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Track where reps overwrite generated messaging and turn that into new constraints.

Message Coherence and Demand Performance at Scale

Run in Prompt Architect
personacmomarketingbrandtutorial

Objective: keep brand consistency while scaling multi-channel campaigns and content velocity.

1

Core Message Map

Create single source message architecture by persona and funnel stage.

2

Channel Adaptation

Generate compliant variants for email, social, paid, and sales enablement.

3

Claim Validation

Require proof-linked claims before publication.

4

Performance Loop

Feed best-performing motifs back into the template library weekly.

Best Practices

Start message coherence and demand performance at scale with a small live pilot and one owner per review lane.

Track CTR and CVR trend and organic movement by cluster from day one.

Bake this control into your checklist: format aligns with channel constraints

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: single creative angle reused across all segments.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Message Coherence and Demand Performance at Scale Owner: Growth Marketing Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Separate top-funnel education from bottom-funnel conversion copy.

Forecast Credibility, Cash Discipline, and Variance Clarity

Run in Prompt Architect
personacfofinanceforecasttutorial

Objective: improve planning accuracy and decision confidence through transparent assumptions.

1

Close Summary

Generate monthly close narrative with material variance highlights.

2

Assumption Register

Track assumptions, owner, confidence, and evidence for each forecast driver.

3

Scenario Pack

Publish base/bear/bull outlook with trigger points.

4

Decision Memo

Convert forecast deltas into explicit budget and hiring decisions.

Best Practices

Start forecast credibility, cash discipline, and variance clarity with a small live pilot and one owner per review lane.

Track close cycle duration and forecast error from day one.

Bake this control into your checklist: assumptions are visible and quantifiable

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: ignoring materiality because edge case is rare.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Forecast Credibility, Cash Discipline, and Variance Clarity Owner: Finance Systems Controller Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Use scenario labels that executives can compare at a glance.

People Health, Capability Growth, and Retention Signals

Run in Prompt Architect
personahrbppeopleretentiontutorial

Objective: standardize manager support, review quality, and growth planning across teams.

1

Manager Support Kits

Generate coaching prompts, 1:1 agendas, and development plan templates.

2

Review Quality

Draft structured feedback with bias checks and measurable actions.

3

Retention Watch

Summarize attrition risk signals and intervention options.

4

Capability Plans

Create role-specific skill growth plans tied to business priorities.

Best Practices

Start people health, capability growth, and retention signals with a small live pilot and one owner per review lane.

Track manual rewrite rate and policy adherence rate from day one.

Bake this control into your checklist: jurisdiction and policy effective date are explicitly referenced

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: generic templates that ignore role or location context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: People Health, Capability Growth, and Retention Signals Owner: People Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Treat every first month rollout as calibration, not final process design.

Resolution Quality, Escalation Readiness, and Deflection

Run in Prompt Architect
personasupportserviceoperationstutorial

Objective: improve first-contact resolution while reducing low-value ticket volume.

1

Ticket Structuring

Normalize intake fields for priority, impact, and reproduction quality.

2

Response Assist

Generate clear customer responses with policy-safe language and next steps.

3

Escalation Pack

Build engineering-ready escalation packets with technical context.

4

KB Automation

Turn resolved issues into reusable knowledge articles.

Best Practices

Start resolution quality, escalation readiness, and deflection with a small live pilot and one owner per review lane.

Track throughput stability and SLA adherence from day one.

Bake this control into your checklist: every step has an owner and SLA

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: local optimizations that break downstream teams.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Resolution Quality, Escalation Readiness, and Deflection Owner: Operations Excellence Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Write one ‘stop and escalate’ condition for each critical step.

Discovery Discipline, PRD Quality, and Outcome Tracking

Run in Prompt Architect
personaproductdiscoveryroadmaptutorial

Objective: increase roadmap quality by connecting evidence, decisions, and delivery outcomes.

1

Problem Intake

Aggregate user research, ticket themes, and analytics anomalies.

2

Opportunity Framing

Generate measurable problem statements and target outcomes.

3

PRD Drafting

Produce PRD skeleton with constraints, dependencies, and rollout plan.

4

Outcome Review

Compare projected vs realized impact after launch.

Best Practices

Start discovery discipline, prd quality, and outcome tracking with a small live pilot and one owner per review lane.

Track activation lift and escaped defects from day one.

Bake this control into your checklist: evidence links are attached to conclusions

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: prioritization by loudest request.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Discovery Discipline, PRD Quality, and Outcome Tracking Owner: Product Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Use a fixed template for experiment readouts to improve cross-team comparison.

Delivery Predictability, Quality, and Team Enablement

Run in Prompt Architect
personaengineering-managerdeliveryqualitytutorial

Objective: improve sprint predictability and reduce quality regressions across squads.

1

Sprint Planning Assist

Generate risk-aware sprint plans from backlog + capacity inputs.

2

PR Quality Prompts

Use standardized review prompts for reliability, security, and maintainability checks.

3

Incident Feedback

Convert incidents into backlog improvements and runbook updates.

4

Team Health Review

Summarize blockers, context-switch load, and coaching opportunities.

Best Practices

Start delivery predictability, quality, and team enablement with a small live pilot and one owner per review lane.

Track SLA adherence and throughput stability from day one.

Bake this control into your checklist: every step has an owner and SLA

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: SOP text that reads well but cannot be executed.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Delivery Predictability, Quality, and Team Enablement Owner: Operations Excellence Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Measure handoff quality with downstream rework, not internal completion stats.

Academy v4.0 · Interactive Documentation · Beginner Mode