Product & Engineering Assignment: Escalation mitigator

We have a robust understanding of the current state of escalations and prioritize the best ways to reduce them.


Expectations / Description

Description

Escalations are necessary, but expensive.

  • Expensive because of the negative impact on Experience of Lessonly’s Customer Service teams
    • Anytime a customer-facing rep cannot answer a question, resolve a problem, or make a change that enhances the value of our offering to the customer in question, it reduces the overall experience.
  • Expensive because escalations are unplanned work for those that could be otherwise improving the system
    • Every moment that is spent NOT making improvements to the system by someone with the skill, access, and knowledge to make enhancements is less than ideal.

Key Result(s) / Outcomes

  • Observability
    • Stakeholders strongly agree or agree when asked “I know what the escalation trends are, and understand what we are doing to reduce them (so that we don’t have the same ones that are bugging us today be the same ones we are bugged by 6 months from now)”.
  • Outcomes
    • If the above is true, then we can/will have a quarter-over-quarter reduction in known escalations (as defined by any escalation type that occurs more than once per month for at least 3 contiguous months and/or takes more than a day of any tier-2+ person).
      • There will always be new escalation-needs being added, such is the physics of creating software. The purpose of this goal is that the known escalation-needs are consistently being eliminated.
    • Customer-facing team members strongly agree or agree when asked “I am continuously given ever-improving tools, knowledge, or skills from the Empower Squad and/or the other product squads that help me serve customers directly without needing to ask for help”.

Requirements

Configuration Health

  • ✅ Has 6 Abilities
  • ✅ Is a part of 11 Positions
  • ✅ Has been referenced in 3 pieces of public recognition
  • ℹ️ Fewer than five people (1) have reacted to this Assignment. To ensure anonymity, analysis will only appear after at least five people have reacted.
  • ℹ️ No one has an official rating on this Assignment
  • ⛔️ Last updated: over 3 years ago
  • ℹ️ Never conversed about

Examples / Observations

  Observation created over 6 years ago

I ❤️ this message that is hidden away in a CH story. It tells the full tale of what I'm spotlighting: https://app.clubhouse.io/lessonly/story/26584/understand-escalations#activity-26619

However, the thing that I appreciate about this, was Rick's conclusions that he put at the end of each question he referenced. That made it so I didn't have to guess at anything nor did I have to try and interpret the intent behind sharing the reports.

Overall this was excellent.

The only thing I was left wanting was clear next steps. But even with that need still existing I felt this was more than worthy of highlighting!

Official Escalation Mitigators

Manager Details:
This section is for Lessonly folks only. Sign your team up to find your Gruuv!

Teams needing an Escalation Mitigator

This section is for Lessonly folks only. Sign your team up to find your Gruuv!

Positions that reference being an Escalation Mitigator

This section is for Lessonly folks only. Sign your team up to find your Gruuv!

Conversations about Escalation mitigator

This section is for Lessonly folks only. Sign your team up to find your Gruuv!

Embed code

<iframe src="http://ourgruuv.com/our/roles/11?embed=true&name=escalation_mitigator&organization=lessonly"></iframe>