#510 – Team Health Activity Released

This week we shipped Team Health into production.

After last week’s internal dry run, we opened Team Health up to every organization with the feature turned on. Over the course of the week, teams outside Parabol started and completed their first health checks on production.

For me, it first felt real during last week’s QA, when we tested the build that has now shipped. That pass caught one significant bug late in the process: team leads couldn’t close a health check early to reveal its results before its scheduled end.

We’ve also started reaching out to a handful of current and prospective customers to let them know Team Health is here. One organizational leader wrote back almost immediately:

It’s too early to say much more than that. But it was a sweet moment.

Back when we were getting Parabol off the ground, I was still working as an organizational design consultant. I had a reputation for helping turn around teams and departments with high attrition and low engagement. One client shared their team’s engagement survey data with me, and the written comments were oozing with the organization’s issues. When I asked the executive team whether they had read them, or put together plans to address them, the answer was simply: “No, that would be too much work.”

That answer stuck with me. In Friday Ship #497 we asked the same question another way: if a team member pours their heart out in a survey, then what? Our answer is to build the moment to act right into the product, at every level of the organization. A Team Health check runs as its own recurring meeting or as a phase inside a retrospective. When the results are revealed, the team can discuss them and turn what they find into a task, synced to wherever the team tracks its work.

Team Health now has its own category in the Activity Library. Pick a question pack: Parabol’s balanced default (we call it the Everything Bagel), a research-backed instrument like the Gallup Q12 or Spotify’s Squad Health Check, or your own questions. Every check asks one question from each of the five categories Google’s Project Aristotle found in its most effective teams: Psychological Safety, Dependability, Structure & Clarity, Meaning, and Impact. The questions rotate from check to check, so your team isn’t answering the same survey every time.

When the check closes, each category shows its score, how it changed since the last check, and its trend over time.

We did a lot of research and stakeholder interviews while designing Team Health. Many of the people we spoke with were used to survey-style products that never give team members a moment to actually talk about the health of their team. And they worried a lot about feedback being traced back to whoever wrote it. So anonymity is built into every step:

Parabol is popular with product and engineering teams, and much less known outside of them. So alongside the feature, we rebuilt how Team Health shows up on our website. We wrote these pages so the people championing Parabol inside their companies have something to share with colleagues in HR, people operations, and leadership.

Nine pages changed this week. Two of them are new:

And seven were updated:

We also built these pages to be read by AI assistants, not just people. Back in #497 we noted our web traffic shifting as more people search with chatbots. So every fact on these pages is written out in text (not only shown in a screenshot), the FAQs carry structured data, and the details match from page to page. When someone asks an assistant about Parabol’s Team Health, it has consistent answers to work from.

Organization-wide Team Health reporting is coming soon for Enterprise. Leaders responsible for many teams will see participation, category scores, and change since the last check for every team in one report, with the same anonymity floor the meeting enforces.

If you run a health check with your team, we’d love to hear how it goes: parabol.co/contact

Signups were up week over week nearly 25% so it is a bit surprising that platform activity was lower. We’ll be watching this carefully next week.

…ran Team Health with real teams for the first time. Health checks were started and completed on production all week, the first real usage to feed back into the flow before we widen access further.

…got structured Stand-Up templates within striking distance. Close enough that when a customer asked again for a date, we promised to beat two weeks. The last thing holding it up is simplifying how Inspirations make their way into a drafted answer.

…cracked the Inspirations design open. A deep pass on the AI drafting controls showed most of their complexity doesn’t earn its keep. The bigger idea that emerged: Parabol as one window across GitHub, your calendar, Jira and Notion that tells the story of your work. For now we’ll ship the minimum good version and build toward that.

…ship structured Stand-Up templates.

…keep learning from Team Health in the wild, smoothing the rough edges teams run into on the way to more awareness.