Skip to content

Weekly KPI Reporting Cadence #45

Description

@thalescb

Context

GoodDollar currently lacks a predictable, repeatable data review cadence. Stakeholders request ad-hoc data pulls, which creates interrupt-driven work and inconsistent reporting. A weekly KPI review posted to #data would give everyone a current read on the numbers without asking.

Goal

Establish a weekly reporting ritual that stakeholders can rely on -- reducing ad-hoc requests and providing consistent visibility into protocol health.

Scope

  • Define the core KPI set (onchain + Amplitude + supply metrics)
  • Manual weekly review format and delivery (posted to #data)
  • Explore Amplitude automation for streamlining data collection
  • Full automation once onchain pipeline is scheduled and reliable

Current Status

First manual iteration planned for next week (covering 15 days to align with the community call cadence). Exploring Amplitude's built-in reporting for partial automation.

Value

Predictable cadence = fewer "can you pull this" interruptions. The team always has a current, consistent read on the numbers. Builds trust in the data function as proactive, not reactive.

Metadata

Metadata

Assignees

Labels

analyticsDashboards, insights, and reportingepicInitiative-level tracking issuerecurringOngoing cadence, not a one-shot deliverablescopingResearch and planning phase

Type

No type

Projects

Status
Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions