Welcome to Successteam's Help Center 👋

How is the Score calculated?

A short explanation of the calculation behind the indicators.
Written by Nadia
Updated 1 year ago

In Successteam, we measure team members' perceptions within 4 core areas. All team members receive an email asking for their feedback on a selection of randomized statements on a weekly/monthly basis. 

The statements are all correlated to one of the 12 Indicators we measure on. All team members answer from 0 (Totally disagree) to 6 (Totally agree).

Each statement has its own normal distribution, but as one statement is not sufficient to give a meaningful indication (i.e., Stress in the Culture), we collect data from many statements' normal distributions and merge them. 

In Short, a normal distribution is used as a "model" of how a large number of statistical elements are distributed around their average. Simplified, if you measure the height or weight of a large number of apples, most will be around a certain average, while very large or tiny apples are rarer.

An indicator's normal distribution is shown as the average percent of all answers in a given period (default is a month back). Then we display your team status and score in colors to provide you with a simple and straightforward overview of a pretty complex algorithm based on a normal distribution.

The colors indicate if a team has challenges or is excelling within the 4 main indicators. The meaning of the different colors is explained, in short, below.

Below you have the distribution broken down in percentages. It is intentionally a bit more challenging to reach GREEN (6), as our focus is on where teams can improve and become even more motivated, happy, and high-performing. 

The point is to give you, as a leader, the most manageable and easy-to-understand overview when it comes to your team score and status. That is also why we have the "Successteam Score". With this score, you can quickly see how high your team's average of all 12 indicators is, making it easy to understand if you are on track.

Did this answer your question?