And why that’s harder to make peace with than we admit
Recently, while preparing for my year end performance review, I took more time to prepare than usual.
This year had been very busy. I had delivered more than what was expected.
But when I tried to put it down on paper, it felt harder than it should have. Not because I hadn’t done the work. And not because it didn’t matter.
It just didn’t come out clearly.
When I started my career, I liked clear job descriptions.
I liked knowing where my responsibility started and where it ended. I liked being able to say, this is my job, do it well, and trust that the system would take care of the rest. There was comfort in that clarity. Effort had boundaries. Performance had logic. Do X, get Y.
For a long time, that model worked. And for many people, it still feels like the right way to think about work.
But somewhere along the way, work stopped fitting neatly into the boxes we built for it.
What the Job description doesn’t prepare you for
Today, most of the work that actually matters doesn’t arrive with clear boundaries. It shows up as a problem that cuts across functions. A decision that needs context more than approval. A situation where waiting for the right owner would mean letting momentum die.
And if no one steps in, things simply get stuck.
Not because it’s written anywhere. But because leaving it untouched feels irresponsible. Because the work needs to move, even when ownership isn’t clear.
Over time, this becomes normal. Going beyond the JD stops feeling like an initiative and starts feeling like part of the job. You’re still evaluated within a role, but you’re expected to operate beyond it.
Your JD explains your position. It doesn’t explain the effort.
That’s the mismatch I find hardest to articulate.
When alignment becomes the work
A surprising amount of my time now goes into aligning with stakeholders who don’t share similar priorities. Translating across functions. Carrying context from one conversation to the next so others can move faster. Making sure that we do not drop the ball, even when nothing visible gets built.
This work takes judgement. It takes emotional energy. It takes patience. And it rarely produces a clean artefact you can point to at the end of the day.
When performance conversations happen, this effort is difficult to communicate. This effort is valuable, but because it doesn’t fit into the language, we still use to describe work.
Much of this work is meant to disappear once it’s done.
Leadership, without accounting for it
We often say leadership is everyone’s responsibility. And that’s true.
A lot of my day goes into conversations where I can’t direct, can’t demand, and can’t walk away either. It’s not directional authority. It’s influence, restraint and active listening.
This kind of leadership consumes time in ways that invisible in the calendars. It doesn’t translate cleanly into milestones or metrics. It leaves no formal trace. They are meant to unblock, align, listen or simply keep things moving.
And when at the end of the week, I look back trying to make sense of what I actually achieved, I often struggle to explain where the time went.
Over time, a pattern becomes hard to ignore.
When work is spread across people, functions, and conversations, visibility starts replacing contribution. The things that are easiest to see are also the easiest to reward. People who speak confidently, present often, or package their work well are easier to recognise.
Those who carry complexity quietly are harder to read.
It isn’t about intent. It’s about what gets noticed.
And when effort no longer fits cleanly into a JD, it doesn’t always show up clearly either.
How to live with this shift
Many of us were trained to value depth and to become a specialist in something specific.
That instinct is still valid. Depth still matters. What has changed is what depth alone can carry.
The work now often asks for something broader – the ability to hold context, sit with ambiguity, and keep things moving long enough for others to act.
I didn’t plan for this shift. It happened gradually. My work moved from doing one thing end to end, to holding many things together.
This is what people now loosely call being a generalist. Not someone who knows a little of everything, but someone whose effort sits between clear roles and keeps work from stalling.
Over time, the work spread out. Depth didn’t disappear, but it became harder to point to because it no longer sat in one place
Roles are becoming anchors, not containers. Starting points, not boundaries. They tell you where you begin, not where your contribution must end.
The work still gets done. It always does.
What’s changed is that explaining it now takes more effort than before.
What I’m still trying to make peace with
Job description is not obsolete and, I don’t think clarity is overrated.
But I no longer believe that JDs alone can explain effort, ownership, or impact.
For people early in their careers, this can feel deeply unsettling, especially if you’re looking for clean boundaries, clear timelines, and a predictable equation between effort and reward. That model isn’t wrong. It’s just incomplete.
At some point, growth asks for a broader mindset. One that accepts that some of the most important work won’t fit neatly anywhere. That responsibility often shows up before authority. And that progress sometimes looks like things not going wrong, rather than something visibly going right.
I still like clarity. I just don’t expect the Job description to give it all to me anymore.
Some days, this feels like freedom.
Some days, it feels like friction.
Both seem to be part of work now.
Written by Vibhor Jain © 2026 | Originally published at mindspringlife.com