#509 – Team Health Champagne

This week we took Team Health to production for the first time.

Our upcoming Team Health activity went live on prod behind a feature flag for internal testing. Team Health is a lightweight way for a team to rate how they’re doing across a set of categories.

On Wednesday we opened the very first company-wide Team Health activity. We ran the whole team through it to shake out the flow before we widen access. Our Team Health Activity won’t just be for the market, it’s for us to. Being avid consumers of our own product is something we’ve call Drinking Our Own Champagne:

Lead developers at Parabol often start a thread in Slack to collect feedback on a new feature. People report their findings as people interact with it. Here’s a sampling of the kind of things our team generates thier first run through:

Collecting and making changes on the things we can spot pre-launch shaves a good amount of friction off for our users and customers. However, using a feature week in and week out and making making improvements based on the frictions that only appear after a good amount of time is what really makes our product sing.

As if on cue, our metrics mostly show green this week as our seasonal August slowdown ends and we roll into September. Will this turn around into a growth trend? Stay tuned and let’s find out together!

…polished the Team Health onboarding and permissions. We added a new animation to the Activity Library that walks people through the Team Health flow, and reworked the trickier permission questions around who can start and end a health check (a CEO kicking one off across every team vs. a single team lead closing out their own).

…continued the standup templates work moving. Structured responses and templates for Stand-Ups continued firming up in design and dev off, heading toward the same production-testing bar we just cleared with Team Health. Hopefully, we’ll have this feature in production in the next week or two.

…spoke to customers to get more feedback on our upcoming Enterprise reporting features.

…widen access to Team Health. We’ll move from internal prod testing to real teams, finish the permissions UX, and close out rough edges the our internal dry run surfaced.
…push standup templates toward an internally testable deployment. We’ll get structured responses in front of the team the way we did with Team Health.