Skill: Data Storytelling and Dashboard Design

Capability Domain: Analytics Communication
Technology Stack: Narrative structure

Purpose

Plan the story. Do not pick a BI product here. Interpret proven findings — do not re-extract. Do not re-classify Action Register cause tags.

Template

Fill docs/analysis/narrative-outline.md. YAML numbers live in streamlit/data/.

Recipe

1. Big-picture first: reconstructed delivery cycle (effort, wall-clock, impact on every stage) before any stage section. Renderer: streamlit/pages/0_Delivery_Cycle.py / cycle_figure.
2. Then the opportunity quadrant (1_Opportunity_Quadrant.py). Opportunity names, not agents.
3. Then the deficiency register (2_Deficiency_Register.py): finding + eliminate/automate/delegate + dE/dK/dI + receiving playbook. Copy CAS. Do not invent tags.
   - dE + automate/delegate → AI SDLC as receiver.
   - Other dE → process/tooling owners (not AI SDLC).
   - dK → Team Upskill Engine as receiver of candidates (stage, clock, unit, n, role). Do not outline modules.
   - dI → staffing / selection.
4. Then one section per stage in flow order. Promoted EDA ids from promoted_eda.yaml or none.
5. Cap visuals at one per finding.
6. Name which presentation skill Present Findings will use. Jupyter = notebooks/published-findings.ipynb.
7. If Streamlit or Jupyter: list starter mart tabs (Commits, Work items, Changes, Pipelines, Load, Defects, Sprints) as drill-down. Skip missing views. Formulas: skill Present Findings with Streamlit → Starter mart tabs.

Clocks (never equate)

• Issue lead / cycle (if Jira views exist): business days. Skill Jira Flow Extract.
• MR / PR cycle: wall-clock hours, created → merged.
• Label the unit. Do not plot both clocks on one unlabeled axis.

KPI aggregation

Prefer per-item median + n. A mean of daily averages is unweighted by volume.

Three lenses

Flow, speed, people — in stage detail and tabs, not as the opening slide.

Contributors

commit author ≠ work-item author ≠ integrator ≠ assigned reviewer. Reviewer counts are assignments, not approvals. Load signals are risk, not a score.

Pitfalls

• A finding without its Action Register decision is trivia.
• Opening with a starter tab or Feature Cycle Time.
• Re-tagging dE/dK/dI, or presenting dK rows as a curriculum.