When Role Design Fails, Everything Else Breaks
The Painkiller That Masks Everything
A talented operator joins a startup at the early stage. The role is undefined by design. They wear every hat, learn constantly, build from scratch, and feel genuinely invested in the outcome. It feels like a dream job. They tell their friends about it. They stay late. They solve problems that don't exist in a job description yet.
The company grows. Processes emerge. Roles narrow. What felt like relief at first (finally, some focus, some help with the workload) slowly transforms into something else entirely. The operator starts doing the most valuable work for the company and the least interesting work for them. Spreadsheets. Logistics. Tracking. The creative work that brought them in gets handed off to someone new.
They stay for a while. They try to stay motivated. But the fundamental problem has nothing to do with their manager's emotional intelligence or the company's stated values. The problem is the role itself.
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 these away and the work stops feeling meaningful, regardless of how much someone loved it before. The early-stage startup accidentally delivered all five. The growth phase accidentally removed most of them.
This is not a failure of the manager. It is not a failure of compensation. It is not a failure of company culture in the way we usually talk about culture. It is a failure of organizational design.
The operator leaves. They leave behind equity that might have been worth something. They leave behind relationships and context that took years to build. They leave because the system was not designed to keep them engaged as the organization changed shape.
Leaders often assume that retention problems point to bad management, bad culture, or insufficient pay. Sometimes they do. But organizational structure itself is a silent killer. When roles are not designed with intention, when scope collapses without replacement, when feedback loops disappear, when autonomy shrinks without acknowledgment, talented people start noticing everything else they were too busy to care about before.
The spreadsheets don't feel better if your boss gives better one-on-ones. The role doesn't become meaningful if the culture deck says it should be.
Designing for Retention Requires Structure
Organizational design is not something that happens once and then stays fixed. It is a living system that needs to be revisited as the company grows. Roles need to be intentionally shaped to deliver meaning, not accidentally hollowed out as the company scales.
The lesson for leaders is straightforward: if you want to keep good people, examine the role itself before you examine everything else. Make sure work delivers autonomy, variety, purpose, feedback, and impact. If it doesn't, no amount of leadership development or cultural messaging will fix it.
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, emotional intelligence, and organizational performance. Subscribe here.