Skip to main content

Performance broken down by skills

How to build a playbook's Performance score from skills with their own weight, to see what explains the score and focus coaching on something concrete.

By default, playbooks use simplified performance: a single score from 0 to 10 that evaluates how the conversation was conducted. With Performance Broken Down by Skills, that score is built from the skills your team needs to measure, each with its own relative weight. In diio, each skill is set up as a dimension.

diio evaluates each skill in every conversation and calculates Performance as the weighted average of all of them, on a 0 to 10 scale. The score still exists, but now you can see which skill raises it and which one lowers it.

What it's for

  • Know what explains the score. A 5/10 can come from very different things. With the breakdown you know whether the problem is understanding the other person's need, explaining clearly or closing with a next step.

  • Coach on something concrete. Instead of "you need to improve your conversations", the leader and the executive can agree to work on a single skill and measure whether it improves.

  • Measure what your team values. The weights reflect what matters most in that type of conversation.

In the Executive's Bitácora, playbooks with broken-down performance show the skills profile against the team median, and diio can suggest coaching focuses on a specific skill.

Who can set it up

The account Admin or an administrator of the team the playbook is assigned to.

How to turn it on

  1. Go to diio settings → Playbooks and open the use case and conversation type you want to edit.

  2. Edit the playbook and expand the General Performance field.

  3. Switch to Performance Broken Down by Skills. You'll know it's on because you'll see the message "You're using Performance Broken Down by Skills", with a link to go back to simplified performance if you need to.

  4. Click Add dimension for each skill you want to measure. Name it with the pencil icon and fill in:

    • Skill to evaluate and its description: what diio should evaluate and in what context. It's required; you can't save without it.

    • What bad practices should be avoided in this skill?: the behaviors that should lower the score.

    • What good practices are you looking for in this skill?: the behaviors that should raise it.

    • Strictness level: High, Medium or Low. Defines how strict the evaluation is. It's set to Medium by default.

    • Relative weight: how much this skill contributes to the score compared with the others. diio turns it into a percentage and shows it at the top right of each dimension. For example, a skill with weight 2 counts twice as much as one with weight 1.

  5. Save your changes.

How to choose good skills

  • Between 3 and 6 per playbook. With fewer, the breakdown says little. With more, the profile gets hard to read and each skill weighs too little to move the score.

  • One behavior per skill. "Asks about the need and its impact" can be evaluated. "Has a good conversation" can't.

  • Make sure they don't overlap. If two skills measure almost the same thing, the same mistake is counted twice.

  • Let the weight reflect the priority. Give more weight to what most defines success in that type of conversation. If they all matter equally, use the same relative weight for all.

  • Give context in the description. Explain what type of conversation it is and what's expected in it. For example: "first 45-minute interview with a candidate, before the technical test".

  • Write observable practices. In good and bad practices, describe behaviors that can be heard in the conversation, one per line. The more concrete they are, the more consistent the score.

  • If you use example phrases, make clear they're just a guide. Add something like "example phrases should be read as 'or similar': evaluate the intent, not the exact wording". That way diio doesn't penalize someone who says the same thing in other words.

Examples of skills by conversation type

Discovery meeting (sales): digging into the need and its impact · qualifying budget, decision process and timelines · identifying who decides and who influences · closing with a next step with a date and an owner.

Recruiting interview: exploring concrete experiences with examples · assessing the role's competencies · clearly explaining the role and the process · closing with next steps for the candidate.

Account review (customer success): reviewing results against the customer's goals · detecting risks or dissatisfaction · identifying new needs · agreeing on actions with an owner and a date.

What a complete dimension looks like

Example for a recruiting interview:

  • Name: Experience exploration

  • Skill to evaluate and its description: First interview with a candidate. Evaluates the interviewer's ability to get concrete examples of past experience, with situation, action and result.

  • Bad practices: Accepting general answers without asking for an example. Asking yes-or-no questions. Moving to the next question without digging deeper.

  • Good practices: Asks for a concrete case ("can you tell me about a time when…?"). Asks what the person did specifically, not the team. Asks about the result and what they learned.

  • Strictness level: Medium · Relative weight: 2

What happens after you save

  • The breakdown applies to new conversations. Conversations already analyzed keep their score without a breakdown.

  • If you need an earlier conversation to have the breakdown, reassign the playbook from its detail view so it's processed again.

  • If you change the skills later, the Bitácora shows the current ones. Each skill is averaged only over the conversations that evaluated it.

  • If you go back to simplified performance, the playbook stops showing the skills profile in the Bitácora for new conversations.

Did this answer your question?