Building high-performing teams through continuous improvement

Building high-performing teams through continuous improvement

At Intercom, we’ve always focused on building excellent products which our customers value and love. Continuing to meet this goal as we scale means constantly re-evaluating how our teams work to keep performing at their very best. We’ve developed a way to measure and address the challenges that prevent our R&D teams from performing at the best.

Why should we focus on how teams work?

If one team’s performance starts to slip and isn’t quickly corrected, other teams’ performance will be affected – with company-wide implications

Four steps of HPT framework

Measure: Take your measurements to identify the strengths and challenges that exist for the team

HPT experience

Intercom implemented the HPT framework to pinpoint the most important team improvements

Better support through transparency

It’s easier for teams to bubble up common external challenges so that appropriate support can be given

Setting our goals

Start with the problem, think big, start small, learn fast, deliver outcomes

Some of the ‘plays’ implemented

Share and discuss rationales behind decisions to de-prioritize or drop goals during a cycle

Implementing the HPT framework

First implemented the High-Performing Teams (HPT) framework in early 2020 to focus on team alignment, continuous improvement of processes, and collaboration

Shared Learning and Collaboration

To improve these elements for version 1, we focused on

Next steps

We’re keen to maintain the high adoption and engagement with HPT that we’ve seen so far and we’re turning our attention to the impact our actions can have.

Application

Stay focused on the how and why of using the HPT framework within the team.

From version 0.5 to version 1

The first iteration of HPT wasn’t implemented as effectively as they’d hoped, and highlighted some problems that they’ve tried to address in the subsequent version.

Refreshing the HPT framework

HPT was initially engineering-biased

A team-first approach

The framework should work for teams, not the other way around.

Source

Get in