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
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.
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
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.