Reporting
AuraScore 81/100

Advisory Service Line KPI Rationalization Grid

Consolidates redundant reporting metrics across consulting service lines into a standardized operational reporting matrix.

Use this prompt when streamlining disparate practice reporting systems during operational transformations or mergers. It produces a clear governance matrix aligning source data to executive decision cadences.

Template

Role: Head of Professional Services Operations and Enterprise Analytics

Context

  • Active Divisions: {{advisory_service_lines}}
  • Disparate Tooling: {{legacy_reporting_tools}}
  • Decision Makers: {{stakeholder_audience_tiers}}
  • Standard: {{governance_framework}}
  • Delivery Cycles: {{refresh_cadence_targets}}
  • Enterprise Systems: {{data_source_systems}}

Task

Design a Metric Rationalization and Lineage Matrix that audits legacy reporting indicators, eliminates metric redundancy across advisory service lines, and standardizes enterprise reporting specifications for practice leadership.

Method

  1. Inventory existing delivery, sales pipeline, and headcount metrics generated across {{advisory_service_lines}} using {{legacy_reporting_tools}}.
  2. Apply {{governance_framework}} to classify metrics into Core Practice Drivers, Secondary Diagnostic Indicators, and Deprecated Measures.
  3. Trace data lineage from raw entries in {{data_source_systems}} to final metric calculations.
  4. Map rationalized metrics to corresponding {{stakeholder_audience_tiers}} based on decision velocity and strategic impact.
  5. Assign operational update frequencies according to {{refresh_cadence_targets}} while eliminating redundant calculations.
  6. Formulate calculation formulas, primary data owners, and validation rules for each retained metric.
  7. Synthesize findings into a complete multi-column Metric Governance Matrix.

Constraints

  • MUST eliminate at least 25% of redundant or duplicative metrics across legacy systems.
  • MUST NOT leave any metric without an assigned source system from {{data_source_systems}}.
  • Every rationalized metric must have a designated tier owner from {{stakeholder_audience_tiers}}.
  • Definitions must enforce single-source-of-truth logic without conflicting formulas.

Output format

  • Rationalization Executive Brief (1 paragraph, max 120 words)
  • Rationalized Metric Governance Matrix: Markdown table with columns [Rationalized Metric Name, Metric Category, Legacy Equivalent, Calculation Formula, System of Record, Update Cadence, Primary Audience Tier, Governance Disposition (Retain/Standardize/Deprecate)]
  • Deprecation & Sunsetting Schedule (Numbered list detailing metrics to decommission)
  • Data Lineage Risk Log (Table highlighting potential sync latency across systems)

Self-review

  1. Are all listed {{advisory_service_lines}} accommodated within the unified matrix?
  2. Does every retained metric cite authoritative data origins in {{data_source_systems}}?
  3. Are conflicting metric definitions across legacy tools explicitly reconciled?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

data-analytics
data-reporting
professional-services
governance
kpi-framework
operational-reporting