When Nobody Can Tell You Exactly What Your Job Actually Is
A job with genuinely unclear expectations creates a specific, well documented kind of exhaustion, distinct from simply having too much to do.
A specific and quietly exhausting kind of workplace stress comes not from having too much to do, but from never being entirely sure what is actually expected, or from being pulled in genuinely contradictory directions by different people who each have a legitimate claim on the same hours. Organizational researchers distinguish these as role ambiguity and role conflict, and both function as distinct, well documented drivers of burnout, separate from raw workload entirely.
Role ambiguity describes a lack of clarity about what a job actually requires: unclear priorities, poorly defined success criteria, a job description that bears little resemblance to what actually gets asked of a person day to day. Role conflict describes a different but related problem: genuinely incompatible expectations from different sources, a manager wanting one thing, a client wanting another, company policy implying a third, with no clear resolution mechanism for the conflict between them. Both have been studied extensively since early organizational behavior research in the 1960s and consistently correlate with elevated stress and burnout, independent of how much actual work is involved.
What makes both patterns specifically exhausting, rather than merely irritating, is the constant low grade decision making they require. A role with clear expectations lets a person act with some confidence once the actual work begins. A role riddled with ambiguity or conflict requires continuously guessing which interpretation is correct, or continuously renegotiating which competing demand takes priority in a given moment, which consumes real cognitive and emotional resources before any of the actual work has even started.
This connects directly to the decision fatigue research discussed elsewhere on this site in a different context: role ambiguity effectively multiplies the number of decisions embedded in a job, since every ambiguous task requires an additional judgment call about what is actually being asked before the task itself can even begin. A job that looks moderate in raw workload can still produce high strain if a meaningful share of that workload arrives wrapped in genuine uncertainty about what success actually looks like.
Role ambiguity often takes root earliest during onboarding, when a genuinely thorough explanation of what a job actually requires gets sacrificed to the pressure of getting a new hire productive quickly. A rushed or superficial onboarding process can leave a role vaguely defined for months or years afterward, since the assumptions formed in the first few weeks tend to calcify into an unspoken understanding that rarely gets revisited once the initial adjustment period has passed, even when that early understanding was never actually accurate to begin with.
A particularly corrosive version of this shows up when the ambiguity is not accidental but structural, in organizations that deliberately leave roles loosely defined to preserve flexibility for management, without recognizing the cost this imposes on the people actually filling those roles. Flexibility that benefits an organization's ability to reassign work can directly increase the burnout risk of the people whose roles are being kept intentionally undefined to enable it.
Addressing this does not always require a full organizational redesign, though that would be the most complete fix. A direct conversation asking a manager to specify, in writing, the actual priority order among competing demands, converts an ongoing, silent source of ambiguity into an explicit, resolved decision that no longer needs to be silently renegotiated each time it comes up. Asking directly what success in a role specifically looks like, rather than assuming a shared understanding exists, often reveals a surprising and clarifying gap between what a person believes is expected and what a manager actually intended.
Feeling exhausted by a job that does not look, on paper, particularly demanding is not a sign of low tolerance for stress. It is frequently a sign that a meaningful share of the actual burden is coming from ambiguity and conflict embedded in the role itself, a specific and well documented burnout driver that workload alone completely fails to capture.