# Exec dashboard blueprint Human Guide

## What This Is For
When to Use Preparing ELT/board-ready snapshots of marketing performance. It gives the agent a clearer input/output frame for marketing analytics: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Exec dashboard blueprint agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for exec dashboard blueprint.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Exec dashboard blueprint guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Preparing ELT/board-ready snapshots of marketing performance.
- Standardizing dashboard layout across BI, RevOps, and marketing teams.
- Packaging insights from `/marketing-analytics` commands into clear narratives.
- **Story Arc** – headline → KPI spine → risks/opps → actions.
- **KPI Tiles** – awareness, demand, pipeline, revenue, efficiency metrics with traffic lights.
- **Drill Cards** – channel, campaign, and audience breakouts linking to deeper views.
- **Insight Callouts** – annotate anomalies, root causes, and required decisions.
- **Action Register** – owners, due dates, and follow-ups surfaced alongside metrics.
- 3-slide deck structure (headline, KPIs, actions).
- Dashboard wireframe with recommended chart types + layout.
- Annotation checklist ensuring context + next steps accompany data.
- **GTM Agents KPI Guardrail Sheet** – baseline vs target vs alert ranges for reach, pipeline, win rate, CAC payback @puerto/README.md#214-241.

## Decision Points And Nuance
The original skill emphasizes: When to Use, Framework, Templates, Tips, GTM Agents Dashboard Governance Overlay, KPI Guardrails (GTM Agents Reference), Weekly Exec Packet Outline, Tool Hooks.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- **Insight Callouts** – annotate anomalies, root causes, and required decisions.
- Limit each dashboard view to one primary objective to avoid overload.
- **Narrative Structure** – use Story Arc to link KPI shifts to drivers and required decisions.
- **Action Register** – every dashboard delivery must include owner, due date, and status for prescribed actions.
- Required Decisions – what leadership must approve/block

## Copy-And-Paste Prompt
```text
Use the Exec dashboard blueprint human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the gtmagents/gtm-agents skill entry for `exec-dashboard-blueprint`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Executive Dashboard Blueprint Skill

## When to Use
- Preparing ELT/board-ready snapshots of marketing performance.
- Standardizing dashboard layout across BI, RevOps, and marketing teams.
- Packaging insights from `/marketing-analytics` commands into clear narratives.

## Framework
1. **Story Arc** – headline → KPI spine → risks/opps → actions.
2. **KPI Tiles** – awareness, demand, pipeline, revenue, efficiency metrics with traffic lights.
3. **Drill Cards** – channel, campaign, and audience breakouts linking to deeper views.
4. **Insight Callouts** – annotate anomalies, root causes, and required decisions.
5. **Action Register** – owners, due dates, and follow-ups surfaced alongside metrics.

## Templates
- 3-slide deck structure (headline, KPIs, actions).
- Dashboard wireframe with recommended chart types + layout.
- Annotation checklist ensuring context + next steps accompany data.
- **GTM Agents KPI Guardrail Sheet** – baseline vs target vs alert ranges for reach, pipeline, win rate, CAC payback @puerto/README.md#214-241.
- **Measurement Spec** – metric definitions, filters, refresh cadence, owner column.
- **Weekly Exec Packet** – combines dashboard screenshots, narrative summary, decision log (mirrors GTM Agents Data Analyst deliverable).

## Tips
- Limit each dashboard view to one primary objective to avoid overload.
- Embed links back to commands (`produce-campaign-report`, `monitor-channel-pacing`) for drilldowns.
- Archive monthly snapshots for trend storytelling.
- Adopt GTM Agents cadence: Monday data QA, Tuesday ELT preview, Thursday exec meeting, Friday retro + action register updates.
- Highlight which KPIs are within guardrail, trending to alert, or breaching (RAG) so leadership can react quickly.
- Pair with `docs/gtm-essentials.md` tools: Context7 for latest GA4 docs, Serena for patching data models, Sequential Thinking for retro facilitation.

## GTM Agents Dashboard Governance Overlay
1. **Data QA Loop** – run freshness + anomaly checks before distributing (log results in audit trail).
2. **Narrative Structure** – use Story Arc to link KPI shifts to drivers and required decisions.
3. **Action Register** – every dashboard delivery must include owner, due date, and status for prescribed actions.
4. **Escalation** – if guardrail breach persists >2 weeks, escalate to Chief Product Officer / Sales Director per GTM Agents governance.

## KPI Guardrails (GTM Agents Reference)
- Awareness (reach/impressions) ±8% window before alerting; >12% triggers campaign review.
- Pipeline add ≥3x quota per quarter; warn at 2.5x.
- Win rate ≥25% for in-quarter commit; escalate if <20%.
- CAC payback ≤14 months; escalate if >16 months.

## Weekly Exec Packet Outline
```
1. Headline + KPI spine (traffic lights per guardrail)
2. Insights & Drivers – 3 bullets tying KPI movement to channels/programs
3. Required Decisions – what leadership must approve/block
4. Action Register – owner, due date, status
5. Appendix – detailed drill cards + methodology
```

## Tool Hooks
- **Context7** – fetch current platform docs (GA4, Salesforce) referenced in measurement specs.
- **Serena** – update BI repo SQL notebooks or dbt models safely.
- **Sequential Thinking** – facilitate monthly retros and architecture of dashboard iterations.
- **Playwright** – capture dashboard screenshots or verify embedded web components before distribution.

---