Overview
The association lacked a consistent way to track and communicate product outcomes, with teams focusing on outputs and activity rather than measurable impact.
I led the design of a weekly reporting framework that reframed how teams defined, tracked, and communicated success—enabling more outcome-driven decision-making across product and leadership.
Impact
Improved alignment between the Technology team workloads and business goals
Estimated time savings of ~4 hours per user across a user base of ~600
Shifted team behavior toward outcome-oriented thinking
My Role
Led the design of an outcome-focused reporting system used across Technology teams
Partnered with leadership to redefine success metrics and reporting expectations
Translated abstract goals (e.g. "better write-ups") into structured, repeatable reporting formats
Context & Challenge
As the association matured in its product operating model, leadership needed clearer visibility into progress and impact. Existing reporting was:
Inconsistent across teams
Focused on activity rather than outcomes
Difficult to synthesize at a leadership level
The challenge was not just creating a report—but changing how teams think about and communicate success.
Key Insights
Teams defaulted to reporting outputs due to a lack of clear outcome definitions
Leadership needed concise, comparable reporting across teams
Overly detailed reporting reduced clarity instead of improving it
Design Approach
Reframed reporting around outcomes, not activity
Standardized structure while allowing flexibility across teams
Optimized for quick scanning by leadership
Solution
A weekly outcome reporting system that:
Highlights key outcomes and progress against goals
Surfaces risks and blockers clearly
Enables consistent communication across teams
