DocsUse CasesPlaybooks: Role Day Walkthroughs

Playbooks: Role Day Walkthroughs

Use Cases by Department · Beginner Friendly

Run Founder Cadence with Clear Strategic Loops

Run in Prompt Architect
role-walkthroughfounderceodailyweeklymonthly
1

Daily: 20-Min Signal Scan

Review top growth, delivery, people, and risk metrics in one brief.

2

Daily: Top 3 Decisions

Lock only high-impact decisions; delegate everything else with explicit owners.

3

Weekly: Priority Reset

Publish one page: wins, misses, top bets, and cross-functional blockers.

4

Monthly: Strategic Review

Compare strategic bets vs outcomes and reallocate resources.

Best Practices

Start run founder cadence with clear strategic loops with a small live pilot and one owner per review lane.

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

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

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

Common Mistakes

Avoid this pattern: overwriting prior decisions with no changelog.

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: Run Founder Cadence with Clear Strategic Loops 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.

Operational Cadence for Throughput and Reliability

Run in Prompt Architect
role-walkthroughcoooperationsdailyweeklymonthly
1

Daily: SLA Dashboard

Check missed handoffs, blocked workflows, and aging queues.

2

Daily: Exception Routing

Assign clear owners for every severe workflow exception.

3

Weekly: Cross-Team Ops Review

Review SLA trends, rejection causes, and process fixes.

4

Monthly: Capacity Rebalance

Shift staffing and process capacity to top bottlenecks.

Best Practices

Start operational cadence for throughput and reliability with a small live pilot and one owner per review lane.

Track policy adherence rate and manager clarity score from day one.

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

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: Operational Cadence for Throughput and Reliability 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.

Commercial Rhythm for Forecast and Win Rate

Run in Prompt Architect
role-walkthroughcrosalesforecastdailyweeklymonthly
1

Daily: Commit Risk Watch

Review top commit deals with objective evidence checks.

2

Daily: Escalation Coaching

Resolve stalled enterprise deals with deal-desk intervention.

3

Weekly: Forecast Review

Publish confidence-banded forecast with assumption changes.

4

Monthly: Commercial Postmortem

Analyze wins/losses and recalibrate messaging + pricing playbooks.

Best Practices

Start commercial rhythm for forecast and win rate with a small live pilot and one owner per review lane.

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

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

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: Commercial Rhythm for Forecast and Win Rate 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

Use manager-facing language in a separate section from legal-facing rationale.

Content and Demand Cadence for Brand-Safe Growth

Run in Prompt Architect
role-walkthroughcmomarketingdailyweeklymonthly
1

Daily: Campaign Pulse

Track spend, CTR, conversion, and CPA anomalies.

2

Daily: Message QA

Review claim safety and tone consistency before publication.

3

Weekly: Content Planning

Publish channel plan mapped to persona and funnel stage.

4

Monthly: Creative ROI Review

Retire low-yield patterns and scale winning narratives.

Best Practices

Start content and demand cadence for brand-safe growth 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: approval path to HRBP or legal is visible for escalations

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: Content and Demand Cadence for Brand-Safe Growth 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

Use manager-facing language in a separate section from legal-facing rationale.

Finance Cadence for Confidence and Control

Run in Prompt Architect
role-walkthroughcfofinancedailyweeklymonthly
1

Daily: Cash + Variance Monitor

Review cash movement, major spend anomalies, and revenue variance signals.

2

Daily: Decision Notes

Generate short finance decisions memo with owner and impact.

3

Weekly: Forecast Delta

Publish assumption changes and confidence adjustments.

4

Monthly: Board Finance Narrative

Synthesize actuals vs plan with forward risk and action plan.

Best Practices

Start finance cadence for confidence and control with a small live pilot and one owner per review lane.

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

Bake this control into your checklist: language is bias-checked before publishing to managers or employees

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

Common Mistakes

Avoid this pattern: publishing drafts without naming accountable reviewer.

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: Finance Cadence for Confidence and Control 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.

People Partner Cadence for Team Health and Development

Run in Prompt Architect
role-walkthroughhrbppeopledailyweeklymonthly
1

Daily: People Signal Review

Scan attrition risks, manager support requests, and workload hotspots.

2

Daily: Manager Enablement

Draft coaching prompts and communication support for people managers.

3

Weekly: Talent Health Sync

Review hiring, onboarding, performance, and retention actions.

4

Monthly: Capability Plan

Publish skill-growth and succession readiness updates.

Best Practices

Start people partner cadence for team health and development with a small live pilot and one owner per review lane.

Track manager clarity score and policy adherence rate from day one.

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

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 Partner Cadence for Team Health and Development 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

Use manager-facing language in a separate section from legal-facing rationale.

Legal Service Cadence for Risk and Throughput

Run in Prompt Architect
role-walkthroughgeneral-counsellegaldailyweeklymonthly
1

Daily: Matter Triage

Classify incoming legal requests by risk and urgency.

2

Daily: Clause Guardrails

Use approved fallback language for routine contract cycles.

3

Weekly: High-Risk Review

Review material exposures and escalation decisions.

4

Monthly: Policy Refresh

Update legal templates from observed negotiation and dispute trends.

Best Practices

Start legal service cadence for risk and throughput with a small live pilot and one owner per review lane.

Track manual rewrite rate and cycle time per case from day one.

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

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: Legal Service Cadence for Risk and Throughput 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.

Support Cadence for Resolution Quality and Deflection

Run in Prompt Architect
role-walkthroughsupportdailyweeklymonthly
1

Daily: Queue Health

Check backlog aging, severe tickets, and SLA risk.

2

Daily: Escalation Quality

Validate escalation packets before engineering handoff.

3

Weekly: Deflection Review

Identify repeat tickets and create/update knowledge articles.

4

Monthly: Quality Coaching

Generate coaching plans by resolution pattern and CSAT trends.

Best Practices

Start support cadence for resolution quality and deflection with a small live pilot and one owner per review lane.

Track manager clarity score and cycle time per case from day one.

Bake this control into your checklist: language is bias-checked before publishing to managers or employees

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: Support Cadence for Resolution Quality and Deflection 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

Store one approved ‘golden’ output per workflow and compare every new draft against it.

Product Cadence for Discovery, Spec Quality, and Outcomes

Run in Prompt Architect
role-walkthroughproductdailyweeklymonthly
1

Daily: Signal Intake

Review user feedback, funnel anomalies, and incident insights.

2

Daily: Problem Framing

Turn raw signals into structured problem statements.

3

Weekly: PRD Pipeline

Progress high-confidence opportunities into clear PRDs with constraints.

4

Monthly: Outcome Review

Compare launched feature outcomes against expected impact.

Best Practices

Start product cadence for discovery, spec quality, and outcomes with a small live pilot and one owner per review lane.

Track cycle time per case and manager clarity score 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: Product Cadence for Discovery, Spec Quality, and Outcomes 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

Store one approved ‘golden’ output per workflow and compare every new draft against it.

Engineering Cadence for Predictability and Quality

Run in Prompt Architect
role-walkthroughengineering-managerdailyweeklymonthly
1

Daily: Delivery Signal Scan

Track blocked work, PR queue health, and incident impact.

2

Daily: Risk Notes

Capture scope and dependency risks for active sprint work.

3

Weekly: Sprint Health

Review commitment risk, quality regressions, and capacity fit.

4

Monthly: Reliability + Throughput Review

Balance delivery speed with incident and rework trends.

Best Practices

Start engineering cadence for predictability and quality with a small live pilot and one owner per review lane.

Track manager clarity score and cycle time per case from day one.

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

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

Common Mistakes

Avoid this pattern: publishing drafts without naming accountable reviewer.

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: Engineering Cadence for Predictability and Quality 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.

Academy v4.0 · Interactive Documentation · Beginner Mode