UX case study

Redesigning the Team Page for Dobee

How I improved collaboration, clarity, and team identity in a complex OKR environment.

My role

Head UX Designer

Scope

Full end-to-end UX

Duration

Two weeks

Case study in progress..

Product overview

Dobee is an OKR platform designed to make goal management engaging, lightweight, and transparent across organizations.

The problem

The existing team page in Dobee did not fully support collaborative goal ownership or provide a clear, intuitive way for team members to work together towards common goals

The goal

A space where teams can easily work together, manage goals, track progress, and build a shared identity.

Process

An iterative approach from discovery to final prototype over 2 weeks.

Discovery

The project began with a series of conversations with Dobee’s product owners based on feedback and needs from the costumers.

Key discovery activities included:

  • Reviewing existing platform patterns

  • Mapping product owners expectations

  • Identifying constraints in the current data model

  • Discussing how Radical Focus could be integrated

  • Clarifying which actions should happen on the Team Page versus elsewhere in the platform

  • Competitive audits

The excisting team page:

Outcome:
A set of core use cases—centered around team-owned goals, weekly reflection, and lightweight team identity—and a shared understanding that version 1 needed clarity, not complexity.

Requirements

Prioritized features based on user needs and business constraints

Must have

To explore

Iteration & Redesign

Layout option 1

Layout option 2

Product owner feedback

  1. Need for intuitive goal previews and ability to see that you can click on a goal on the timeline

  2. A push to surface team summaries high and center

  3. A desire for stronger team identity (theme/skin/color).

  4. Request for a scrollable list of extended goal and result information where teammates can update and contribute

  5. Uncertainty about goal categories and long-term ownership model

Outcome: clear iteration tasks and reframed scope.

  • Clickable goals on a goal preview timeline - ensuring all interactions mirrored existing familiar patterns

  • Also making sure the team can look back on earlier summaries and scores.

  • Highlight week summaries and week score earlier on the page.

  • Introducing a stronger team identity:

    • Change color

    • Large changeable team picture

    • Team avatar, slogan and name

  • Designing a space for team members to work on results

    • Overview of results and progress

    • easily make updates, highlights and change confidence score

    • add contributions and see contributions from other teammates

Research - Usability study

Research study plan

Objective

The goal of this usability study was to evaluate the early prototype of the new Team Page in Dobee. We wanted to understand how users navigated the page, how they completed core tasks, and where the design caused confusion or friction. The study focused on validating the value of new features and identifying usability issues early.

Research Questions

We aimed to answer the following questions:

  1. How do users update result confidence scores?

  2. What motivates users to customize the team’s theme, and how intuitive is this action?

  3. How should goals and results be structured to feel clear and navigable?

  4. Can users locate and use result functions for goals the team does not own?

  5. Does the Team Page feel simple or difficult to navigate?

  6. Are there features users want added or removed?

  7. Which elements create the strongest sense of “team identity”?

KPIs

To measure usability, we tracked:

  • User error rate: When users got stuck completing tasks

  • Assistance rate: How often facilitation was required

  • Perceived ease of use: User-rated difficulty on a 1–3 scale

Logistics

  • Location: Remote

  • Date: 17.06.2025

  • Session length: 30 minutes per participant

  • Participants: 3 users familiar with OKRs or team goal-setting

  • Constraints: Timeframe of the project and resources

My Role

As Head UX Designer, I planned and conducted the study, moderated the interviews, observed task completion, documented behaviors, and synthesized insights.

Method

Users were asked to complete three core tasks in a clickable Figma prototype:

  • Update the confidence score of a result (“Get 12 new customers”)

  • Contribute to a result belonging to a goal the team is invited to

    Change the color theme to explore team identity customization

For each task, I asked follow-up questions about ease of use, expectations, and feature relevance.
The session concluded with a discussion of alternative layouts, clarity of tabs, and expectations for features like weekly resets and result history.

Key Findings

1. Users updated confidence scores in different ways

One user clicked Update directly from the goal line. Two users entered through the Results list and clicked the flag icon

Insight:
Users have different mental models and are accustomed to multiple paths. Offering more than one entry point is beneficial.

2. Confusion between “Results” and “Goals”

⅓ of participants struggled to understand what was a goal vs. a result when using the “Results” list.

Insight:
The list must prioritize clarity: Results should be visually dominant and the layout of Goals and result list should be consistent to similar views in other parts of the product. The list should function primarily as a workspace, not a goal browser

3. Users want to see their contributions immediately

All participants wanted to review the contribution they just added, regardless of who owns the goal.

Insight:
Every result should be openable to view contributions without too many clicks.
Contribution activity is critical for understanding progress.

4. Progress graphs under each result were not seen as necessary

Users preferred focusing on contributions and concrete activity.
Graphs felt redundant because they already appear on the Goal Page.

Insight:
Simplify the results list and remove unnecessary visual noise.

5. Tabs were not recognized as tabs

One user felt unsure whether the tabs were clickable; they didn’t resemble traditional tab patterns.

Insight:
Tabs must use a more recognizable design, with active/inactive states and clear affordances.

6. Radical Focus board should be customizable

One participant wanted to rename the cards to better reflect their team’s workflow.

Insight:
Customizable card labels (e.g., “This week’s focus” → “This week’s contributions”) can increase usefulness across teams.

7. Users want past health metrics

One participant wanted to revisit metrics from earlier weeks.

Insight:
Historical views matter for teams that track trends over time.

8. Color theme customization was not essential but still useful

One user found it unnecessary. Others viewed it as helpful for context when scrolling. Avatar and team photo were considered more important

Insight:
Theme customization is nice-to-have, not essential, but still reinforces team identity—especially when navigating across multiple teams. ⅔ participants had trouble finding the “Change theme” button.

9. Users prefer starting a new week with empty cards

Both users asked preferred to start fresh, with optional access to last week’s content.

Insight:
Starting clean supports a weekly planning ritual.
Offer a “Start new week” modal allowing users to import previous content or start empty.

Design Implications

Based on these findings, several clear UX improvements emerged:

The Goals and results workspace:

  • Use clearer hierarchy and familiar icons to differentiate goals from results. Keep consistency in goals and results layout throughout the platform.

  • Simplify visual noise by removing redundant graphs, that is also shown in each goal page.

  • Ensure contributions are always visible when a result is opened

  • Improve tab design

Team identity and costomization

  • Make team theme editing easier to locate by having an easy to find team settings where you can change team name, slogan and team avatar.

  • Add the option to turn on and off functionality in the team settings module

  • Allow renaming Radical Focus cards and other sections and terms by having “custom terms”

  • Make past health metrics accessible

  • Keep theme customization optional

  • Prioritize the avatar and team photo as primary identity markers.

Overall improvements:

  • Provide multiple entry paths for updating results

  • Support week resets with a simple modal choice.