When Role Design Fails, Everything Else Breaks
The Painkiller That Masks Everything
A talented operator joins a startup early. The role is undefined on purpose. They wear every hat, learn constantly, build from scratch, and care about the outcome. It feels like a dream job. They tell their friends about it. They stay late. They solve problems no job description has caught up to yet.
The company grows. Processes appear. Roles narrow. What felt like relief at first (finally, some focus and some help with the workload) slowly turns into something else. The operator ends up doing the work that's most valuable to the company and least interesting to them: spreadsheets, logistics, tracking. The creative work that brought them in goes to someone new.
They stay for a while and try to stay motivated. Their manager's people skills and the company's stated values aren't the issue. The role itself is.
When the right role exists, it masks everything else. When the role disappears, every other flaw comes into focus at once.
What Makes Work Actually Meaningful
Hackman and Oldham's Job Characteristics Model identified five elements that make work feel meaningful: doing different kinds of things, seeing how your piece fits the whole, knowing it matters, having some say in how you do it, and knowing how you're actually performing.
The Cost of Stripping Them Away
Strip enough of those away and the work stops feeling meaningful, however much someone loved it before. The early-stage startup delivered all five by accident. The growth phase removed most of them by accident.
The manager, the pay, and the culture in the usual sense can all be fine. The failure is in organizational design.
So the operator leaves. They walk away from equity that might have been worth something, and from relationships and context that took years to build. They leave because nobody designed the system to keep them engaged as the organization changed shape. (If you want a rough number for what that costs, try our turnover calculator.)
Leaders often assume retention problems point to bad management, bad culture, or low pay. Sometimes they do. Organizational structure does its damage more quietly. When roles aren't shaped on purpose, when scope collapses with nothing to replace it, when feedback loops disappear, and when autonomy shrinks without anyone saying so, talented people start noticing everything else they used to be too busy to care about. We trace the same pattern in when the wrong role becomes your biggest problem.
Spreadsheets don't feel better because your boss runs better one-on-ones. A role doesn't become meaningful because the culture deck says it should be.
Designing for Retention Requires Structure
Organizational design has to be revisited as the company grows. Roles need to be shaped on purpose to deliver meaning, or scaling will hollow them out. That's why organizational design can matter more than leadership style.
For leaders, the lesson is direct: if you want to keep good people, examine the role before you examine everything else. Make sure the work delivers autonomy, variety, purpose, feedback, and impact. If it doesn't, leadership development and cultural messaging won't fix it. Get the management fundamentals and the role design right first, and the rest has something to stand on.
Retention problems are often role design problems in disguise. See how we work at Kestryl Edge.
Dan Korus, Kestryl Edge founder, publishes The Updraft, a weekly newsletter on leadership, trust, and how teams actually perform. Subscribe here.