THE GROWTH EDGE
The Leadership Edge
Development Insights for Leaders Who Do the Work
October 2026 • Issue #7
Most of the leaders I work with are already doing the thing that would develop their people. They hand off work constantly. What they’re not doing is the fifteen minutes on either side of the handoff — the framing beforehand that tells someone why this task and why them, and the debrief afterward that turns a completed assignment into a processed experience. Those thirty minutes are the entire difference between a team that executes and a team that grows, and they’re the first thing to get cut on a busy week.
I keep coming back to this because it’s one of the rare places where the highest-leverage move costs almost nothing. You’re already delegating. The work is already getting done. The only variable is whether anyone learns anything from it. And the leaders who build that habit end up, two years later, with a bench of people who can handle things they couldn’t have handled before — which is the only sustainable answer to the workload problem that prompted the delegation in the first place.
Last month’s posts covered the mechanics of that (a four-step delegation framework) and the organizational context around it (what changes about culture as a company scales, and what that means for you as the person your team actually experiences as the company). The research this month suggests the gap between development intent and development effect is wider than most organizations realize — which makes what you do inside your own team disproportionately important.
What We Published Last Month
Delegation as Development: Stop Doing, Start Growing Your People
“When I hand something off and it comes back at 70% of what I would have done, I fix it myself. And then I’m working until 8 PM again.” This post reframes delegation from a workload problem to a development one, and gives you the four-step framework that makes the difference: choose the task for the person rather than the person for the task, frame it as development rather than delivery, define guardrails rather than process, and debrief the learning rather than the outcome. About 25 minutes of added effort per cycle, for a direct report who’s measurably more capable afterward.
Read it: Delegation as Development →
Scaling Culture: What Changes When You Go From 50 to 200 Employees
Written for organizational leaders, but worth reading as an individual contributor to your own team’s culture. The post’s central point is that past about 100 people, employees stop experiencing “the company’s culture” and start experiencing their manager’s. If you lead a team inside a growing organization, you are the culture for the people who report to you — the norms they learn about feedback, risk, conflict, and what gets rewarded come from watching you, not from the values page. Useful for understanding why your team’s experience may differ sharply from the one described at the all-hands.
Read it: Scaling Culture: What Changes From 50 to 200 →
Worth Knowing: What the Research Is Saying
LEADx, 2026 Global Leadership Development Study. Benchmark data from leadership development professionals found that nearly 75% estimate less than half of trained content is ever applied on the job. The study’s diagnosis is a design failure rather than a content failure: generic programs that aren’t connected to real role context or reinforced by ongoing coaching rarely transfer. The same body of research identifies emotional intelligence as the most in-demand leadership skill heading into 2026, and finds that organizations developing leaders at every level — not just the top — are substantially more likely to rank in the top tier of their industry’s financial performance.
That 75% figure is the strongest argument I know for the approach in last month’s delegation post. If most formal training doesn’t survive contact with the actual job, then the development that counts is happening in the work itself — and the person who determines whether that work develops anyone is the direct manager. Not L&D. Not the program. You. Which is either a burden or an unusual amount of leverage over your team’s growth, depending on how you look at it.
O.C. Tanner, 2027 Global Culture Report (released September 23). Based on more than 25,000 workers across 23 countries, the report draws a distinction worth sitting with: employees increasingly experience learning as transactional — a one-sided push for more output dressed up as development. What the researchers call a growth culture is different, built on six elements (empathy, communication, community, support, opportunity, and balance) that together create a partnership rather than an extraction. Where all six are present, organizations showed 48x higher odds of what the report terms cultural elasticity: the capacity to build new skills and stay adaptable when conditions change.
The transactional-learning problem is one I see constantly in coaching, usually described by the person on the receiving end. “They want me to develop so I can take on more” is a very different experience from “they want me to develop because they’re invested in where I’m going.” The tell is almost always the framing at handoff. Step 2 of last month’s delegation framework — telling someone why you chose them and what capability this is meant to build — is precisely what separates the two. Same task, opposite signal.
Thirst & Totara, 2026 State of L&D Research. In a survey of more than 3,000 L&D professionals, 64% said leadership now expects proof of learning impact and 72% report being asked to justify development spend more rigorously than in prior years, against largely flat budgets. Totara’s companion research found a specific mechanism behind the problem: when employees overestimate their own skills, skills gaps widen for 36% of organizations, productivity drops for 34%, and manager stress rises for 31%. Self-assessment, in other words, is an unreliable input to a development plan.
For an individual leader, that last finding has a practical edge. If your direct report’s view of their own capability is the primary input to their development plan, the plan is probably aimed at the wrong target — and you’ll feel the cost as the manager absorbing the gap. This is where external data earns its place: a 360, an assessment debrief, or even a structured debrief after a stretch assignment gives both of you something more reliable than self-report to work from. It’s also why the debrief questions in last month’s post are framed around what the person learned about themselves, not whether the work went well.
Resource Spotlight
Eisenhower Matrix Implementation Checklist. A practical tool for sorting what’s actually on your plate into do, schedule, delegate, and drop — with the implementation detail most versions skip. Pairs directly with this month’s delegation theme, because the hardest part of developmental delegation isn’t the framing or the debrief. It’s being clear-eyed about which work should leave your hands in the first place, and resisting the pull to keep the things you’re best at.
Get the Eisenhower Matrix Implementation Checklist →
Curious what assessment-driven development would look like for you?
Discovery calls are free, 30 minutes, and there’s no pitch — just an honest conversation about where you are, what you’re working on, and whether structured coaching or assessment work would help you get there.