Effort became performance, and motion became the evidence of value — even when nothing meaningful was happening.
There was a time when work felt like forward motion — that sense of doing something that actually changed something. You could feel it in the way a task completed opened space for the next one, or how solving a problem made the next question clearer rather than fuzzier. But over time that experience shifted into something subtler and more confusing: the distinction between actual progress and the *appearance* of work started to blur.
It didn’t start with a crisis. It didn’t happen in one meeting or one comment. It arrived quietly, like a background pattern that only becomes visible when you step back and notice how people are moving through the day. Suddenly it felt like everyone was performing busyness rather than engaging with the work itself.
In meetings, there was a rhythm of talking *about* work more than doing it — long conversations about plans that never landed on actions, restatements of problems without resolution, questions repeated without synthesis. It reminded me of what I wrote in why I struggle with being interrupted all day and still expected to focus: a cadence of motion that never quite translated into clarity or completion.
But this was different. This was about how effort and presence came to feel like performance in themselves. The goal no longer seemed to be finishing something. It was being seen doing something. And because almost everything that technically counted as *doing* was observable — a chat message, a revision in a document, being in a meeting — there was a kind of internal incentive to fill every moment with visible activity.
So everyone stayed busy. Very busy. But the shape of that busyness felt hollow rather than grounded.
It showed up in simple ways. Someone would send a message halfway through a meeting. Someone else would update a shared doc with small, incremental changes that didn’t actually move the work forward. Calendar after calendar would be filled with check‑in meetings, status syncs, “just touching base” calls — all with that familiar language of collaboration, but rarely with outcomes that made the next steps clearer.
And because this pattern had become normalized, it rarely got questioned. People weren’t slacking off. Quite the opposite. They were often responding quickly, contributing earnestly in threads, attending meticulously scheduled sessions. The busyness was real on the surface. It was the *meaning* beneath it that felt thin.
There was a moment I noticed this most clearly. I closed my laptop at the end of a day full of activity — messages sent, meetings attended, revisions made — and realized I couldn’t point to a single thing that felt finished in a way that landed as *done* rather than *paused.* It wasn’t that nothing got done. It was that the work that got done didn’t feel resolute. It felt like *activity* without *arrival.*
That’s when I began to see the difference between busyness as motion and work as progression.
There’s a performance aspect to busyness that’s hard to articulate because it doesn’t come from laziness or avoidance. It comes from the subtle pressure to look productive at all times. In environments where responsiveness is a valued signal, people begin to equate visible engagement with meaningful engagement.
When everyone is trying to look busy, motion becomes the measure of value — even when meaning slips quietly out of view.
One of the confusions in all of this is that busyness does *feel* like work. Typing a reply feels like effort. Sitting in a meeting feels like involvement. Updating a spreadsheet feels like forward motion. But effort isn’t the same as progress. It’s the difference between *moving* and *arriving.* And the more time I spent in environments where busyness was the visible currency of work, the more I began to notice how easy it is to mistake motion for meaning.
Some days, I found myself doing things not because they needed to be done, but because doing them would signal something: “I’m here. I’m engaged. I’m on top of this.” I would draft messages in Slack not because they clarified anything, but because silence felt like absence. I would show up in meetings not because there was an agenda that felt purposeful, but because dropping off the calendar felt like disengagement — even when the meeting itself didn’t land on conclusions.
This isn’t about external evaluation. It’s about internal experience. The rhythm of being *seen* doing work started to shape how I judged my own presence. I began to equate visibility with contribution, even when the two didn’t truly align.
There were conversations where I could feel this happening in real time. Someone would share a long paragraph in chat that didn’t change anything. Someone else would comment “Thanks!” and then add another thought that only served to extend the thread rather than conclude it. These weren’t unhelpful gestures. They were simply part of a pattern where activity became the default measure of engagement.
And because everyone was participating in this pattern, it rarely got questioned. No one said, *Why are we doing this, exactly?* Instead, people said, *Thank you for the update,* *Let’s keep each other posted,* *Feel free to add more.* Polite language. Warm intentions. But no sense of *closure.*
I began to recognize how this affected how I felt at the end of the day. It wasn’t a sense of accomplishment. It was a sense of motion without arrival. Like I had been moving, but not necessarily in directions that felt purposeful. Like I had been present, but not necessarily *engaged* in the work that mattered most to me.
Over time, this pattern reshaped how I approached my own tasks. I’d find myself organizing work in ways that made it visible rather than in ways that made it meaningful. I’d respond to threads with immediate replies not because they needed them, but because there was a subtle sense that not responding quickly might look like absence of care.
And that’s where busyness stops being a sign of engagement and starts being a signal of insecurity. Not insecurity in ability, but insecurity in presence. A worry that if you aren’t visibly moving, you aren’t actually part of what’s happening.
There’s a difference between showing up to contribute and showing up to prove you’re present. And in environments where busyness is equated with participation, that difference gets blurred until it’s hard to see where contribution ends and performance begins.
So you keep moving. You respond. You attend. You revise. You dash off quick messages. You stay visible. And day after day, you accumulate activity that feels like work but rarely lands as *progress.*
It’s not that nothing gets done. It’s that nothing ever feels like it *arrived.*
And that’s what happens when everyone’s just trying to look busy: motion expands to fill all available space, and meaning quietly recedes.
When everyone’s trying to look busy, the work doesn’t stop — but the sense of arrival does.

Leave a Reply