{"site":{"name":"Koji","description":"AI-native customer research platform that helps teams conduct, analyze, and synthesize customer interviews at scale.","url":"https://www.koji.so","contentTypes":["blog","documentation"],"lastUpdated":"2026-11-06T17:03:51.108Z"},"content":[{"type":"blog","id":"2c61a3d3-edda-4090-9910-196a0509a6a0","slug":"manager-span-of-control-interviews-hr-playbook","title":"Wider Spans, Fewer Managers: An HR Playbook for Checking Whether Teams Still Get Managed After a Delayering","url":"https://www.koji.so/blog/manager-span-of-control-interviews-hr-playbook","summary":"A playbook for HR teams on running a span check: AI-moderated interviews with teams whose manager now has more direct reports, and with those managers, 30 to 90 days after a delayering. It cites Gartner (July 2026, 297 CHROs: 67% face higher productivity expectations while removing middle management layers), Gallup (average span 10.9 in 2024 to 12.1 in 2025; manager engagement 31% in 2022, 27% in 2024, 22% in 2025) and Gartner (April 2026: 47% of managers work harder than a year ago). It gives a flag rule for which teams to check, a sampling rule (8 finished interviews per cohort plus a comparison cohort), a seven-step 30-day method, a full interview guide for teams and managers, setup steps in Koji using the Manager Effectiveness Feedback template and the Remove personal details setting, and a list of capacity fixes.","content":"A span check is a short round of interviews with the teams whose manager now looks after more people, and with those managers, run 30 to 90 days after a delayering or reorg. It tells you which teams still get 1:1s, clear priorities and help when they are stuck, and which managers are quietly drowning. Running it with AI-moderated interviews means every team gets the same questions, nobody has to criticise their boss to their boss's boss, and you get counts and quotes by cohort instead of anecdotes. By the end of this playbook you will have a flag rule for which teams to check, a sampling rule, a full interview guide for teams and managers, and a readout that ends in capacity decisions.\n\n## Why the span check matters now\n\nThe middle of the org chart is getting thinner. In a [July 2026 Gartner survey of 297 CHROs](https://www.gartner.com/en/newsroom/press-releases/2026-10-6-gartner-says-chros-top-priorities-for-2027-focus-on-meeting-ceos-expectations-while-minimizing-organizational-risk), 67% reported higher expectations for employee productivity, while their organisations were removing some middle management layers and hiring fewer entry-level staff. The same survey found only 24% of leadership teams agree on who should be accountable for AI agents. More output, fewer managers, and new kinds of work to supervise.\n\nThe teams are already bigger. Gallup reports that the [average number of direct reports per manager rose from 10.9 in 2024 to 12.1 in 2025](https://www.gallup.com/workplace/700718/managers-teams-getting-bigger.aspx), nearly 50% higher than when it first measured in 2013. An average hides the extremes: the manager who went from 7 people to 19 in one reorg is the one you need to hear from.\n\nThe managers taking on those teams are not in good shape. Gallup's [State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) puts manager engagement at 22% in 2025, down from 27% in 2024 and 31% in 2022, and says the fall in manager engagement accounts for most of the recent decline in global engagement, which stands at 20%.\n\n![Column chart of the share of managers engaged at work worldwide: 31% in 2022, 27% in 2024 and 22% in 2025](/visuals/gallup-manager-engagement-2022-2025/gallup-manager-engagement-2022-2025.png \"Manager engagement has fallen nine points in three years, as spans widen · Source: Gallup, State of the Global Workplace 2026 report, 2026\")\n\nManagers say the same thing about their own week. In an [April 2026 Gartner survey](https://www.gartner.com/en/newsroom/press-releases/2026-04-29-gartner-hr-survey-finds-47-percent-of-managers-say-they-are-working-harder-than-1-year-ago), 47% of managers said more is expected of them and they must work harder than a year ago. They spend an average of nine hours a week, more than 20% of their time, on their employees' personal and emotional concerns. HR saw it coming: in Gartner's [July 2024 survey of 1,403 HR leaders](https://www.gartner.com/en/newsroom/press-releases/2024-10-15-gartner-survey-finds-leader-and-manager-development-tops-hrleaders-list), three-quarters said their managers were overwhelmed by the expansion of their responsibilities.\n\nWhy this lands on HR: Gallup estimates that managers account for [at least 70% of the variance in employee engagement scores](https://news.gallup.com/businessjournal/182792/managers-account-variance-employee-engagement.aspx) across business units (Beck and Harter, State of the American Manager). When a manager's span doubles, every one of their reports feels it, and your engagement, regretted attrition and manager effectiveness numbers move months later. The cost of not checking is that you find out from exit interviews, after the delayering business case has already been declared a success.\n\n## What good looks like\n\nTreat the span check as a check on the system, not a grade for each manager. The question is not \"is this person a good manager?\" It is \"can anyone manage 17 people, a quota of their own and two time zones at once, and what has to change so they can?\" Say that to managers before you start, and mean it. It is the difference between a study people help with and one they quietly sabotage.\n\n![A manager and a team member talking one to one at a table, the kind of time that gets squeezed when spans widen](https://images.unsplash.com/photo-1568992687947-868a62a9f521?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3w5NDUzMDN8MHwxfHNlYXJjaHwyfHxtYW5hZ2VyJTIwb25lJTIwb24lMjBvbmUlMjBtZWV0aW5nJTIwb2ZmaWNlfGVufDF8MHx8fDE3OTM5NTE0MTB8MA&ixlib=rb-4.1.0&q=80&w=1080)\n\n_Photo by [Redd Francisco](https://unsplash.com/@reddfrancisco?utm_source=koji&utm_medium=referral) on [Unsplash](https://unsplash.com/?utm_source=koji&utm_medium=referral)_\n\n**Ask about four things: access, clarity, growth and the gap.** Access: can people get time and decisions from their manager? Clarity: do they know what is expected this month? Growth: has anyone talked to them about their development since the change? The gap: who is filling in when the manager can't, and is that person burning out too? Every question in the guide serves one of the four.\n\n**Use this flag rule to pick teams.** It is Koji's recommendation, not a statistical cut-off. Include a manager's team first if any one of these is true since the change:\n\n- Their span grew by four or more people, or by 50% or more.\n- They also carry individual work: a quota, a ticket queue, projects of their own.\n- They inherited a team or function they did not hire or have never run.\n- Their team spans three or more time zones.\n\n**Use this sampling rule.** Invite every direct report in each flagged cohort and aim for at least 8 finished interviews per cohort before you report it. Add one comparison cohort of unflagged teams, so you can tell span effects from company-wide mood. Interview every flagged manager in a separate, shorter round.\n\n**Report by cohort, never by named manager.** Cohorts are span bands (under 8, 8 to 12, 13 to 20, over 20) and \"carries individual work: yes or no\". If an HRBP wants to help a specific manager, that is a separate, opted-in development conversation, not this study.\n\n**Ask for the last event, not a rating.** \"How supported do you feel?\" gets a polite 7. \"Think about the last time you needed a decision from your manager. What happened?\" gets a story with a wait time in it.\n\n**Common mistakes**\n\n- Calling it a manager review. Managers hear \"we're checking whether to cut you next\" and brief their teams accordingly.\n- Asking for team name and tenure together. In small teams that identifies people, and answers go short and safe.\n- Skipping the managers. Their week explains half of what their teams say.\n- Interviewing only the flagged teams. Without a comparison cohort you can't separate the span from the season.\n- Running it at day 10. In the first weeks people are still sorting out who reports to whom. Wait at least 30 days so the new rhythm has had time to fail.\n- Ending with \"managers need training\". Training does not give anyone back nine hours a week. The readout should end in capacity decisions.\n\n## The 30-day span check, step by step\n\nThis is the sequence we recommend, counted from the day you decide to run it, about 30 days after the reorg took effect.\n\n![Process of the 30-day span check: flag teams, brief managers, interview teams and managers, read by cohort, decide fixes, repeat at day 90](/visuals/span-check-30-day-process/span-check-30-day-process.png \"Seven steps from flagging teams to capacity decisions, then a repeat at day 90 · Koji\")\n\n1. **Flag the teams (week 0).** Pull spans before and after the change from your HRIS and apply the flag rule.\n2. **Brief the managers (week 0).** Tell flagged managers what the study is for, that results come back by cohort, and that they will be interviewed too.\n3. **Open the team interviews (week 1).** Send one link from the CHRO or HR director and keep it open for ten days.\n4. **Run the manager round (week 1).** A shorter guide, open at the same time.\n5. **Read by cohort (week 3).** Compare span bands and the comparison cohort side by side.\n6. **Decide the fixes (week 4).** For each cohort, choose a capacity fix and an owner.\n7. **Repeat at day 90.** Same guide, same cohorts, so you can see whether the fixes worked.\n\nThe fixes come from a short menu: move reports to rebalance spans, name a team lead or deputy for day-to-day questions, take work off the manager (approvals, reporting, recruiting admin), change the rhythm (fortnightly 1:1s plus open office hours), or, only when the rest is in place, coaching.\n\n## How to set up a span check in Koji\n\nStart from the **Manager Effectiveness Feedback** template in the dashboard's template gallery. It is built for confidential interviews with direct reports, with a brief, question patterns and probes you can keep. Replace the questions with the guide below. Text interviews are available on every plan, including Free, and a new account starts with 10 free credits, enough to preview the study and run a small first cohort. A text interview uses 1 credit and a voice interview uses 3, and only interviews with a quality score of 3 or more use credits. Check the pricing page for which plans include voice.\n\n![Koji template library with filters by role and cards for research templates](/email/shots/shot-templates.jpg \"Start from the Manager Effectiveness Feedback template and swap in the span check guide\")\n\n1. **Create the team study from the template** or paste the brief from the guide below into \"What do you want to research?\". Koji drafts a research brief you can edit.\n2. **Add the questions and set their types.** Use single choice for the cohort questions (team change, span band), a 1 to 10 scale for clarity, and open questions for everything else. The [structured questions guide](/docs/structured-questions-guide) lists the types.\n3. **Turn on Remove personal details.** In Branding & Settings, open Privacy and switch on Remove personal details (PII). People will name their manager and colleagues in their own words. With the setting on, Koji replaces names, email addresses, phone numbers, addresses and the companies people work for with labels such as [NAME] when each interview finishes, and the original text is not kept. Products and tools stay. It applies to interviews that finish after you switch it on, it leaves pre-interview form answers as they are, and it can miss details, so read quotes before you share them.\n4. **Collect nothing that identifies people.** Switch off the pre-interview form, share one generic link and use the Anonymous badge with your own wording. The badge is a label on the welcome page; what makes the study anonymous is that you collect no identifiers. The [anonymous employee research guide](/docs/anonymous-employee-research-ai-interviews) walks through it.\n5. **Add guardrails.** Tell the interviewer not to ask people to name or rate individuals, and not to discuss pay, performance ratings or who might be moved. See the [guardrails guide](/docs/setting-interview-guardrails).\n6. **Duplicate the setup for managers.** Create a second study with the manager guide, so manager answers never mix with their teams' answers.\n7. **Choose text, voice or both, then preview.** Take each interview yourself on the Preview tab, which does not count as a response. Set a response limit, send the link, and close it after ten days.\n8. **In Europe, bring your works council in first.** See [works councils and employee research](/docs/works-council-employee-research).\n\n## Copy this interview guide\n\nPaste this into any tool. Each question has a type and one follow-up probe.\n\n**Brief to paste into Koji's \"What do you want to research?\" box:** \"After our reorg widened managers' spans, can people on those teams still get time, clear priorities and development from their manager, and what do the managers need to make it work?\"\n\n**Opening line for teams:** \"Thanks for doing this. We are talking to people across the company about how teams have been working since the reorg. This is about how work is set up, not about rating anyone. Nobody will see your name.\"\n\n1. **Cohort (single choice).** \"Which best describes your team since the reorg? Same manager, more people / New manager / Merged with another team / No real change.\" Probe: \"What changed first in your week?\"\n2. **Cohort (single choice).** \"About how many people report to your manager now? Under 8 / 8 to 12 / 13 to 20 / More than 20 / Not sure.\"\n3. **Access (open).** \"Think about the last time you needed a decision or help from your manager. Walk me through what happened.\" Probe: \"How long did you wait, and what did you do in the meantime?\"\n4. **Access (single choice).** \"In the last two weeks, how many 1:1s did you have with your manager? None / One / Two / More than two / We don't have 1:1s.\"\n5. **Clarity (1 to 10 scale).** \"How clear are you about what your manager expects from you this month?\" Probe: \"What would move that up by two points?\"\n6. **Growth (open).** \"When did your manager last talk with you about your own development? What was said?\" Probe: \"What would you have wanted to talk about?\"\n7. **The gap (open).** \"When your manager isn't available, who do you go to?\" Probe: \"Does that person have the time for it?\"\n\n**Closing:** \"If one thing changed about how your team is managed in the next 30 days, what should it be?\"\n\n**For managers:**\n\n1. **Load (open).** \"Walk me through last week. Where did your time go?\" Probe: \"What didn't you get to?\"\n2. **Load (single choice).** \"Do you also carry individual work, like a quota, tickets or projects of your own? Yes / Partly / No.\"\n3. **Access (open).** \"What kind of support are people on your team not getting from you right now?\" Probe: \"What happens to that work instead?\"\n4. **Load (1 to 10 scale).** \"How sustainable is your current workload for the next six months?\" Probe: \"What made you pick that number?\"\n5. **The fix (open).** \"What would give you back five hours a week?\"\n\n![Question bank for a span check after a delayering, with seven questions for team members and five for managers](/visuals/span-check-interview-questions/span-check-interview-questions.png \"The full span check guide on one page, for teams and for their managers · Koji\")\n\n## What you get\n\nKoji's report builds as interviews arrive, and every finding opens to the quotes behind it.\n\n![Koji high-impact finding card backed by a share of participants with a link to supporting responses](/email/shots/shot-finding.jpg \"Each finding shows how many people said it, with the quotes one click away\")\n\n- **An access map by span band.** The share of each cohort with no 1:1 in two weeks, next to the stories of how long decisions take. This is the slide that changes the delayering conversation.\n- **Clarity scores by cohort.** Question 5 by span band and by \"manager carries individual work\", against the comparison cohort.\n- **The hidden deputies.** The people teams go to when the manager is away. They are your retention risk and your obvious team leads.\n- **The manager's week.** Where managers' time goes, how sustainable they rate it and what would give them five hours back. This is your list of work to take off them.\n- **A day-90 comparison.** Run the same guides again. The report history keeps each version.\n\nA usable sequence: a one-page readout to the CHRO and the business leaders who signed off the reorg at week 3, capacity decisions with owners at week 4, a short note back to everyone who took part saying what will change, and the repeat at day 90.\n\n## The same playbook elsewhere\n\nThe span check is one version of a pattern: when one person's load jumps, ask the people downstream. Customer success leaders run it when a CSM's book of business grows, through [renewal risk interviews](/blog/renewal-risk-interviews-customer-success-playbook) with the accounts that just changed hands. Private equity operating partners use the same timing in the [100-day customer baseline](/blog/100-day-customer-baseline-pe-playbook). Inside HR, a delayering often follows a layoff, so pair this with [layoff survivor interviews](/blog/layoff-survivor-interviews-hr-playbook) if both happened in the same quarter. For upward feedback questions to use in a regular cycle, see the [manager feedback survey guide](/docs/manager-feedback-survey-guide).\n\n## Why Koji for a span check\n\nYour realistic options are a pulse from the engagement platform you already own, skip-level meetings, a 360 or upward feedback survey, or a short round of interviews. Each has a place. A pulse is quick and good for a trend line. Skip-levels build trust when it already exists, but a few conversations per leader is all most leaders can fit in. Upward surveys such as Culture Amp's [Manager Effectiveness survey](https://support.cultureamp.com/hc/en-us/articles/360001144745), a 29-question template, or upward reviews inside Lattice's [review cycles](https://lattice.com/fr/blog/february-2025-product-updates-ai-summaries-in-calibrations-shareable-survey-links-grow-ui-improvements-and-more) give comparable ratings, but they are built to rate a manager, and the span check is asking something else: what is the setup doing to the team?\n\n![Table comparing an engagement pulse, skip-level meetings, an upward feedback survey and Koji for checking teams after a delayering](/visuals/span-check-research-methods-compared/span-check-research-methods-compared.png \"How the realistic options compare on what HR needs after spans widen · Koji\")\n\n- **It asks why, every time.** When someone says they had no 1:1 in two weeks, the interviewer asks what happened instead. A pulse records the number and moves on.\n- **Nobody in the chain is asking.** People talk to an AI moderator with no say in their job, so \"my manager has no time for me\" is easier to say than in a skip-level.\n- **Names come out of the quotes.** With Remove personal details on, the quotes leadership reads say [NAME], not the manager's name.\n- **Same questions everywhere.** Differences between cohorts come from the teams, not from who ran the session.\n- **Numbers and quotes together, with quality control.** Single choice and scale questions give counts by cohort next to the stories, and each interview gets a quality score from 1 to 5, so thin conversations don't use credits.\n\nIf you already run a survey platform, see [Culture Amp alternatives](/blog/culture-amp-alternatives-2026) and [Lattice alternatives](/blog/lattice-alternatives-2026).\n\n## Questions you might have about AI interviews\n\n**People will name their manager. Can we still promise confidentiality?** Promise only what the setup delivers. Collect no identifiers, share one generic link, turn on Remove personal details so names in the text become [NAME], and never report a cohort with fewer than 8 finished interviews (the [k-anonymity guide](/docs/k-anonymity-segment-reporting-minimum-base-size) explains why small groups give people away). The removal is automatic and can miss details, so someone in HR reads quotes before they go into a deck.\n\n**Will managers see who said what?** Not unless you give them the study. Use Share on the study card to give Viewer, Editor or Full access to named people or a group, such as the HR team running it, and send line managers the cohort readout instead. The [access controls guide](/docs/research-data-access-controls-audit-trail) covers who sees what.\n\n**Will an AI feel cold for something this close to home?** Participants choose text or voice, the welcome page says what is and isn't collected, and you can take the interview yourself in Preview first. Many people find it easier to be blunt about their boss with a moderator who can't repeat it in the corridor.\n\n## When Koji may not be the right fit\n\nIf you want a formal performance assessment of individual managers, use a consented 360 process, not an anonymous span check. If a cohort will never reach 8 finished interviews, talk to those people in person. If the reorg is still being negotiated with employee representatives, wait until consultation is done and take advice on what you can ask. And if leadership has already decided that spans and support will not change whatever you hear, don't run it: asking and then doing nothing teaches people not to answer next time.\n\n## Metrics to track\n\n- Completion rate and quality scores by cohort.\n- Share with no 1:1 in the last two weeks (team question 4), by span band.\n- Clarity score (team question 5), flagged cohorts against the comparison cohort.\n- Manager workload sustainability (manager question 4).\n- Regretted attrition at 90 and 180 days in flagged cohorts.\n- Capacity fixes decided, with owners, within 30 days of the readout.\n- The same measures at day 90.\n\n## FAQ\n\n**What is a healthy span of control?**\nThere is no single right number. Gallup's average was 12.1 direct reports in 2025, and its own reading is that the manager's talent matters more than team size. What a manager can carry depends on their individual workload, how routine the team's work is and how spread out the team is. That is why the flag rule looks at change and load, not a fixed cap.\n\n**How many interviews do I need?**\nAt least 8 finished interviews per cohort before you report it, plus one comparison cohort of unflagged teams. Interview every flagged manager in a separate round.\n\n**When should I run a span check?**\nAbout 30 days after the reorg takes effect, with a ten-day field window, then again at day 90 with the same guide.\n\n**Should the report name managers?**\nNo. Report by span band and by whether the manager carries individual work. Support for a specific manager belongs in a separate, opted-in development conversation.\n\n**Which Koji plan do I need?**\nText interviews work on every plan, including Free, and new accounts start with 10 free credits. Check the pricing page for voice and for team seats.\n\n## Start your span check\n\nOpen the dashboard, start from the Manager Effectiveness Feedback template or paste the brief above, and have the team round live within a week. See how [HR and People teams use Koji](/for/hr), or browse every playbook in the [HR use-case library](/use-cases/hr).\n","category":"Use Cases","lastModified":"2026-11-06T07:50:10.716291+00:00","metaTitle":"Span of Control Interviews After a Delayering: HR Playbook","metaDescription":"Spans are widening as middle layers go. A 30-day HR playbook to interview teams and managers, spot overload and fix capacity before people leave.","keywords":["span of control","delayering","manager span of control interviews","flattening middle management","manager overload","HR playbook","employee listening after reorg"],"aiSummary":"A playbook for HR teams on running a span check: AI-moderated interviews with teams whose manager now has more direct reports, and with those managers, 30 to 90 days after a delayering. It cites Gartner (July 2026, 297 CHROs: 67% face higher productivity expectations while removing middle management layers), Gallup (average span 10.9 in 2024 to 12.1 in 2025; manager engagement 31% in 2022, 27% in 2024, 22% in 2025) and Gartner (April 2026: 47% of managers work harder than a year ago). It gives a flag rule for which teams to check, a sampling rule (8 finished interviews per cohort plus a comparison cohort), a seven-step 30-day method, a full interview guide for teams and managers, setup steps in Koji using the Manager Effectiveness Feedback template and the Remove personal details setting, and a list of capacity fixes.","aiKeywords":["span of control","delayering","span check","manager capacity","middle management","manager effectiveness interviews","HR employee listening","Gallup manager engagement","Gartner CHRO priorities 2027"],"aiContentType":"guide","faqItems":[{"answer":"There is no single right number. Gallup's average was 12.1 direct reports in 2025, and its own reading is that the manager's talent matters more than team size. What a manager can carry depends on their individual workload, how routine the team's work is and how spread out the team is. That is why the flag rule looks at change and load, not a fixed cap.","question":"What is a healthy span of control?"},{"answer":"At least 8 finished interviews per cohort before you report it, plus one comparison cohort of unflagged teams. Interview every flagged manager in a separate round.","question":"How many interviews do I need?"},{"answer":"About 30 days after the reorg takes effect, with a ten-day field window, then again at day 90 with the same guide.","question":"When should I run a span check?"},{"answer":"No. Report by span band and by whether the manager carries individual work. Support for a specific manager belongs in a separate, opted-in development conversation.","question":"Should the report name managers?"},{"answer":"Text interviews work on every plan, including Free, and new accounts start with 10 free credits. Check the pricing page for voice and for team seats.","question":"Which Koji plan do I need?"}],"relatedTopics":["span of control","delayering","manager effectiveness","employee listening","anonymous employee research","layoff survivors"]}],"pagination":{"total":1,"returned":1,"offset":0}}