Issue Tree: Why Is Our Employee Turnover So High?

A ready-made issue tree. Open it in Razn and fill it with your numbers.

Open this tree in Razn

Free during beta · no card needed

Raising salaries across the board is the most common response to turnover, and often the most expensive guess. This issue tree breaks the problem into who leaves, what pushes them out and what pulls them elsewhere. Cut your exit data by team, manager, tenure and role, and you'll usually see turnover concentrate in a few places. That tells you whether the fix is pay, management, workload or hiring the wrong people.

Why is our employee turnover so high?

  1. Who is leaving?

    • Is turnover concentrated in specific teams, managers or roles?
    • Do people leave in their first six months or after several years?
  2. What pushes them out?

    • Is workload or scheduling unsustainable?
    • Are managers or culture driving people away?
    • Do people see no path to grow?
  3. What pulls them elsewhere?

    • Is our pay below market for these roles?
    • Are competitors offering flexibility we don't?
  4. Are we hiring the right people?

    • Do job descriptions match the real job?
    • Are new hires onboarded well?

How to use this tree

  1. Confirm the root question and who makes the call. If they would phrase it differently, rewrite it first.
  2. Put a number on each branch with data you already have. A rough figure beats a long debate.
  3. Cut the branches that explain little, so the effort goes where the gap is.
  4. Write the answer first: one sentence with the main driver and what you will do about it.

Going further

Your problem is a bit different? Describe it and Razn builds the tree for you.

Structured with Razn → try free