Pulse

A team update tool that uses AI to draft updates for people to review and publish.

Role
Sole product designer
Project
Independent product · 2023–25

The monthly leadership update was a scramble.

Michael saw directors and VPs piece together a slide deck at the last minute. Details and contributions were left out, and blocked work could look settled in the summary.

Leaders heard much of this for the first time in the meeting, with little time to reflect or follow an issue back to the people doing the work. We wanted them to have that context beforehand and a way to reach the work behind it.

Walkthrough · Updates and sources

From Stacks to Pulse

I interviewed people in different roles about how they kept their teams informed. Managers chased updates, people copied information between tools, and meetings filled the gaps. Each team organized its work differently.

Our first concept, Stacks, mapped how work on one project affected another, so someone could trace a delay to its source. We took it through a design sprint, made a Figma prototype, and tested it with people.

People saw value in the updates, but struggled with the stack hierarchy, labels, and status colors. One tester preferred the update view to the stack view. Another understood the update history and liked being able to comment inline.

Teams already had tools for managing projects. Stacks would have given them another map to keep up to date. We changed direction together: start with updates from the people doing the work, then bring those updates together for their teams.

Stacks · Projects
Stacks · Projects
Pulse · People
Pulse · People

A draft to build on

Pulse used AI to take the first pass. A draft drew on a person’s last update and work their team had shared that week. They could edit it, add what was missing, or start from scratch. They decided what to publish.

AI draft · Review and publish
AI draft · Review and publish

A clear view at every level

Once people published their updates, Pulse prepared a draft team update for their manager to review and publish. The same pattern continued up the company. Readers could follow a summary back to individual updates, see who said what, and open the supporting links.

The aim was to give leaders time to read before a meeting and a way to dig into the details that mattered to them.

Sources · Linked work
Sources · Linked work
Exploration · Source links
Exploration · Source links

Why we stopped building Pulse

We used Pulse with our own team. The drafts saved time when there was enough context, but filling in the gaps still took effort. It never became a consistent habit.

Other teams saw the value, but adopting it meant getting everyone to participate before the benefit was clear to each person. We stopped building when we could not resolve that problem.

Pulse needed to be useful to one person before asking them to bring in a whole team. A better draft alone was not enough to make it a habit.

My role

I was the sole product designer on a three-person team with two technical partners, Michael Ashley and Musa Kahya. Michael brought the idea and led the early research. I led interviews and the design sprint, then designed the interactions and prototypes. We decided together to move from Stacks to Pulse.

When we built Pulse in 2024, I worked in Figma while Michael and Musa built the product in code. Musa took on much of the implementation and helped shape product decisions. Our shared shadcn/ui and Tailwind patterns let us try ideas in both places and decide together what to keep.

Team · Design sprint
Team · Design sprint