EPIC Goal

The current Scorecard feature, when displaying aggregated KPIs (Key Performance Indicators) for managers, lacks the necessary transparency to identify the individual components that contribute to the overall score. This "black box" effect prevents managers from efficiently understanding the health score's underlying data, diagnosing issues, and taking immediate action, leading to increased manual effort and delayed response times.

This Epic aims to improve the homepage aggregated Scorecard to implement drill-down functionality and ensuring visible data freshness for aggregated KPIs.

Background/Feature Origin

The need for this feature arises directly form expanding aggregated scorecard logic which can help Engineering Managers and Platform Engineers essential for validating the accuracy of the data and ensuring that pinpoint exactly where interventions are needed to improve organizational performance.

Why is this important?

Implementing a drill-down capability and visible data freshness is crucial because it will:

1. Improve Operational Efficiency: Managers can instantly connect high-level metrics to individual contributors, drastically reducing the time spent on manual diagnosis.
2. Enable Actionable Insights: The Scorecard becomes a diagnostic tool, allowing leadership to pinpoint exactly where interventions are needed to improve organizational performance.
3. Ensure Data Trust and Validation: Providing a visible timestamp for data generation and a path to view underlying entities ensures stakeholders can validate the data's accuracy.

User Scenarios

• Drill-Down Capability: As a Manager, I want to be able to click on an Aggregated KPI to see a list of the individual components that contributed to the value, so I can identify the underlying services impacting the overall score. (Figma)
• Visible Data Freshness: To help provide users with sufficient context, each scorecard should include a timestamp showing when its displayed data was generated (if it's pulled from cached data)

Dependencies (internal and external)

• Internal:
  • Requires changes to the underlying data service to support querying and surfacing individual component data upon request.
  • Requires UI/UX development to implement the drill-down visual interface as per the Figma design.

Acceptance Criteria

FEATURE - Drill-Down Capability: Managers must be able to click on an Aggregated KPI and see a list of the individual components that contributed to the value.

FEATURE - Visible Data Freshness: Each aggregated scorecard view must include a visible timestamp showing when the displayed data was generated.

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>