Overview
Perdoo helps teams execute strategy using OKRs and KPIs. This project focused on improving how companies track KPI progress across teams - making it easier to bring the right metrics into one place, set targets with the right cadence, and run weekly reviews without leaving Perdoo.
Discovery
We saw a recurring pattern: teams tracked KPIs in multiple places (spreadsheets, BI dashboards, Slack updates) and struggled to keep a single, shared view inside Perdoo. Managers wanted to review KPI progress across teams quickly, while individual contributors needed a simple way to maintain targets over time (monthly, quarterly, yearly) without rebuilding dashboards.
Problem statement
Users couldn’t easily consolidate KPIs across teams in one place, which made reviews slow and fragmented. Target setting was also too rigid, forcing workarounds for monthly vs. quarterly vs. yearly goals. We needed a lightweight way to curate KPI views and make target management flexible - without turning Perdoo into a complex BI tool.
Solution design
We explored multiple structures for representing KPIs over time (rows vs. cards, time as columns vs. filters) and tested which model was fastest to scan during weekly reviews. The MVP focused on two core jobs: (1) create a curated KPI board that can be shared across a team, and (2) set and maintain targets across different cadences without friction.
To keep scope tight, we prioritized features using RICE and validated each assumption with quick user feedback. We shipped the smallest version that delivered value on day one, while leaving a clear path for iteration (filters, permissions, and richer rollups) without redesigning the core model.
Prototyping
Using Figma, I developed a working prototype for user testing on volunteered participants. The high-fidelity version incorporates existing components and introduces new ones as necessary.
Validation
We conducted a series of user tests on the prototype, gathering valuable feedback to improve its usability. Based on the feedback received, we made necessary changes to achieve the most user-friendly and effective result.
In addition, we conducted internal design review meetings to gather technical and UX input from our team members. These collaborative sessions allowed us to leverage their expertise and insights to further enhance the design of our solution.
Outcomes
After launch, Boards became the default weekly review surface for many teams - with 3.1k Boards used in recurring reviews and 62% reused across multiple weeks. We also saw an 18% increase in weekly KPI updates, and Board users showed a 6% higher 90-day retention, suggesting the feature improved stickiness beyond initial setup.
Qualitative feedback confirmed the core value: Boards reduced context switching during reviews and made KPI ownership clearer. The most successful teams treated the Board as a shared “source of truth” - and we used those patterns to inform the next iteration (permissions, templates, and richer rollups).
