Most job descriptions are built the same way: a list of duties, a few qualifications, maybe a reporting line at the bottom. That format works fine for roles built around a repeatable set of tasks. It works a lot less well for roles built around judgment calls, relationships, and outcomes that shift depending on what the business needs that quarter. Think of a chief of staff, a program lead stitching together three departments, or anyone whose actual job is “figure out what’s falling through the cracks and go fix it.” Try to write that as a bulleted task list and you’ll either leave things out or write something so broad it stops being useful.
This isn’t a new problem for organizational psychology. Research on role ambiguity, dating back to foundational work by Kahn and colleagues in the 1960s, consistently links unclear role expectations to higher stress and lower job satisfaction, regardless of how capable the person in the role actually is. The issue usually isn’t that people can’t handle ambiguity. It’s that they’re left to interpret it alone, without knowing whether their read on the job matches what leadership actually expects.
That gap shows up in familiar ways. An employee in an adaptable role can feel like they’re perpetually auditioning, unsure whether taking initiative on something outside their written duties will be seen as valuable or as overstepping. Performance conversations get harder too, since it’s tough to evaluate someone against a job description that never really described the job. And when two flexible roles sit near each other on an org chart, the ambiguity compounds: without a clear line between them, disagreements over who owns what tend to surface at the worst possible time, usually mid-project.
None of this means every role can or should be pinned down with the same precision as a task-based job. Some roles are adaptable by design, and trying to force them into a rigid description just trades one problem for another, an org chart that’s accurate on paper and useless in practice. The more realistic goal is to give people clarity on the things that can be defined, even when the day-to-day can’t be.
A few ways organizations do this well: define the role around decision rights and outcomes instead of tasks, so the person knows what they’re accountable for even when the path there changes week to week. Say the ambiguity out loud, in onboarding and in ongoing check-ins, rather than letting someone discover the gray areas on their own through trial and error. Revisit the definition on a real cadence, quarterly rather than annually, since adaptable roles drift as the organization changes and a description that was accurate in January can be stale by summer. And where a role sits close to others, spell out the edges, even if the middle stays flexible, so two people with overlapping scope aren’t left to negotiate boundaries in the moment.
The goal isn’t to eliminate the gray area. For a lot of roles, that flexibility is exactly what makes them valuable. The goal is making sure the people operating in it aren’t doing so without a map.


