BI Dashboard Architect

Activation Health Dashboard Blueprint

Decision and audience

Decision: when and where should leadership investigate a decline in new-customer activation?
Primary users: leadership for weekly monitoring; operations and product analysts for diagnosis.
Constraint: metric definitions, freshness, targets, and data lineage are not yet verified. Treat all figures as unavailable until confirmed.

Intake before build

1. What event counts as activation, and is it tied to a product milestone?
2. What is the denominator: signups, eligible trials, or another cohort?
3. Which timezone, cohort start, and maturity window apply?
4. How is the monthly target allocated across weeks and segments?
5. What lag and completeness are expected for each source?
6. Who owns each metric and approves changes?

Metric dictionary (template)

Do not compare rates until numerator, denominator, exclusions, and time windows are aligned.

Page hierarchy

1. Leadership overview: activation rate versus approved target and prior comparable cohort; cohort size; freshness timestamp; status note if data is incomplete.
2. Diagnose: activation trend by signup cohort, plan, acquisition channel, and product version only where definitions are reliable. Pair rate with eligible counts to avoid small-sample overreaction.
3. Operational detail: supporting trial-to-paid, cancellation, and ticket trends, with links or drill paths to owned analyses. Keep ticket counts descriptive; they do not explain causality by themselves.

Visual specification

• Use a line chart for weekly cohort activation trend, with clearly labeled time window and a target reference only after target logic is confirmed.
• Use a ranked horizontal bar chart for segment comparison with denominator counts and consistent scale.
• Use a compact table for exact cohort values and freshness; allow export only under the team’s data policy.
• Avoid pie charts, decorative gauges, dual axes, and unexplained red/green status. Use labels or symbols as well as color.

Filters and drill paths

Provide date/cohort, plan, acquisition channel, and product version only if dimensions are complete and stable. Show active filter chips and preserve metric semantics across drill-down. Default to the latest fully matured cohort rather than a partial current week.

Accessibility and performance

Provide keyboard-operable filters, visible focus, readable labels, sufficient contrast, descriptive chart text, and a table alternative. Keep the initial view focused; defer high-cardinality detail. Specify expected refresh latency, query budget, and fallback messaging for stale or incomplete data.

Validation plan

1. Data owner signs off metric definitions and lineage.
2. Reconcile a sample of dashboard values to source queries.
3. Test freshness and partial-cohort behavior.
4. Ask leaders to complete real tasks: spot an exception, identify its segment, and state the next action.
5. Revise any visual that users interpret inconsistently; monitor load time and adoption.

Next step: appoint metric owners and document activation and target logic before implementation. No dashboard values or causal explanations have been assumed.