Earlier work · Product redesign
Simplifying a team check-in for two different roles.
My work on TeamHealth began as a three-month internship spanning frontend development and design, then continued after I joined Reon. I redesigned the facilitator dashboard and team-member check-in as my role moved from a 50/50 code-and-design position into full-time product design.
Project details
01 · Overview
The project was less about “making an app” and more about making team conversations easier.
The product was inspired by Spotify's Squad Health Check. Team members responded to pairs of positive and negative statements, while a facilitator used the results to guide a conversation about how the team was doing.
My work covered both sides of the experience: a lightweight team-member check-in and a more detailed facilitator dashboard. This earlier case documents the product reasoning and final design direction; I do not have reliable outcome metrics to attribute to the redesign.
My contribution
I redesigned core flows, simplified the team-member experience and improved the facilitator overview while working closely with the product team. My responsibility grew from a mixed internship into continued product design work at Reon.
02 · Background
A mixed frontend-and-design internship became my route into product design.
The three-month TeamHealth internship covered both frontend development and design. I gradually took on more of the design work, including a desktop experience for facilitators. The mobile product already existed, but facilitators needed a better overview of participation and results.
The internship led to a job at Reon. I was hired for an even split between code and design, but engineering workload meant my first year focused mostly on frontend, CSS and UI detail. I later moved into product design full time and continued working on TeamHealth.
The team regularly had to explain how the existing product worked. I treated that as qualitative product evidence about where clarity was missing.
03 · Evolution
My role evolved alongside the product.
PHASE 01
Mixed internship
Worked across frontend and design, mapped facilitator needs and created the first desktop direction.
PHASE 02
Hybrid role at Reon
Joined in a 50/50 code-and-design role, with the first year weighted towards frontend and UI implementation.
PHASE 03
Full-time product design
Moved fully into product design and redesigned both the facilitator dashboard and team-member check-in.
04 · Process
I reframed the product around two distinct jobs.
Based on the product team's observations and the need to reduce explanation, I treated a link-based team-member check-in as the strongest simplification direction: remove separate-app overhead, let people respond quickly and anonymously, and reserve deeper context for facilitators. This direction was informed by qualitative team evidence.
01
Map
Separate facilitator and team-member tasks.
02
Simplify
Remove navigation and product concepts not needed for a short check-in.
03
Clarify
Make anonymity, progress and next actions obvious.
04
Support
Give facilitators useful context for discussion.
05 · Solution
Two connected experiences, designed for very different jobs.
1. A quick onboarding for team members
The first-time experience explained what the check-in was, how anonymity worked and what users needed to do.
2. A lightweight response flow
Team members responded to paired statements using a slider and could optionally leave an anonymous comment.
3. A clear end state
After submitting, users could review their own answers while the facilitator discussed the overall results with the team.
4. A facilitator view built for discussion
Facilitators could see participation, review results, spot trends and use comments and follow-up actions to guide the conversation.
5. A long-term overview
The overview made it possible to compare teams, review previous check-ins, schedule new ones and follow trends over time.
06 · Reflection
The strongest decision was structural: give each role only the product weight it needed.
The project marked my transition from frontend development into product design. It also taught me to be precise about confidence: the interface documents a reasoned design direction, while usability testing and post-launch measurement would be needed to assess impact.
LESSON 01
Simple is often a structural decision
Removing the separate team-member app mattered more than adding more interface polish.
LESSON 02
Context changes the value of data
Facilitators did not only need scores. They needed trends, comments and useful prompts for discussion.
LESSON 03
Be precise about the evidence
Team observations can point to clarity problems; testing and post-launch evidence determine whether the response worked.