Attending time: That’s just a myth

If “being present” were the same thing as “being productive,” your calendar would be a Nobel Prize factory and your status light would deserve a raise.

But you already know the uncomfortable truth: a day packed with meetings, messages, and “quick check-ins” can leave you exhausted… and mysteriously lacking anything you can point to besides a slightly haunted look. This is the myth of attending timethe idea that time spent showing up, staying visible, and being constantly available is inherently valuable work.

Spoiler: it’s not. Or at least, it’s not the way most modern knowledge work actually creates value. And once you see the difference between attendance and output, you’ll stop confusing motion with progressand start protecting the kind of time that produces real results.

What “attending time” actually means (and why it feels so convincing)

“Attending time” is time spent performing presencein meetings, in inboxes, in chat threads, and in the never-ending theater of “Just circling back…”

It feels like work because it uses your brain. It creates friction. It fills the day. It can even generate short-term relief (“I answered everything!”) and social rewards (“Wow, you’re always responsive!”). Unfortunately, it also fragments attention, inflates busywork, and can quietly sabotage the deeper thinking that most roles actually pay for.

Presenteeism, upgraded: from office chairs to digital availability

Classic presenteeism was about being physically seen at a desk. Today it’s often digital: instant replies, constant pings, a calendar that looks like a tiled bathroom wall. The medium changed; the incentive didn’t. When visibility becomes the scoreboard, people optimize for being seen working instead of shipping outcomes.

The problem isn’t meetings or messages themselves. The problem is treating them as a proxy for value and then wondering why the work that matters keeps getting postponed to “after hours.”

Myth #1: More hours automatically means more output

In industrial work, hours can correlate with output because the work is often linear and observable. In knowledge work, the most valuable moments are often invisible: designing, deciding, writing, debugging, planning, analyzing, revising, and thinking through tradeoffs.

That kind of progress doesn’t scale neatly with hours. In fact, longer hours can backfire by increasing errors, reducing creativity, and driving burnoutthe productivity-killer that shows up wearing your badge and smiling politely.

So when someone says, “We just need to put in more time,” ask: More time doing whatdeep work, or more attending? Because those are not interchangeable. One builds value; the other often builds a museum of half-finished tasks.

Myth #2: Meetings are work (and the calendar is the truth)

Meetings can be powerful: alignment, decisions, conflict resolution, planning, mentoring. But meetings can also become the default coping mechanism for uncertainty: “Let’s set up time.” Translation: “I’m uncomfortable making a call, so let’s talk until the discomfort moves to someone else.”

Here’s the awkward part: many organizations have an invisible belief that a full calendar signals importance. It doesn’t. It signals interruption density.

The hidden tax: context switching, follow-ups, and “meeting hangover”

The time cost of a meeting isn’t just the meeting. It’s the ramp-up, the mental reset, the notes, the follow-ups, and the cognitive residue of unresolved tension (“Wait, did we agree on anything?”). That residue steals from the next block of work, which then gets chopped up again by the next meeting.

A day with scattered meetings often produces a very specific output: a person who feels busy and accomplished, paired with a to-do list that somehow got longer.

A quick test: is this meeting replacing a decision?

If a meeting doesn’t have a decision, a deliverable, or a clearly defined output, it’s often a conversation pretending to be progress. Before you accept, ask:

• What will be different after this meeting? (A decision? A plan? A draft?)
• Who is the decider? (If nobody is, you’re attending a circle.)
• What must be prepared beforehand? (If “nothing,” expect wandering.)
• Can this be done asynchronously? (If yes, reclaim your brain.)

Meetings aren’t evil. But “meeting as default” turns your schedule into a suggestion and your focus into a rumor.

Myth #3: Multitasking makes you efficient

Multitasking is usually just fast task-switchingjumping between contexts and paying a mental switching fee each time. The fee isn’t always obvious, which is why the myth survives. You feel productive because you’re moving. But you’re also constantly reloading the same mental files like a laptop with 73 tabs open.

Research on task switching consistently shows performance costs: slower completion, more errors, reduced quality, and higher stress. You don’t become “good at multitasking.” You become good at recovering from self-inflicted interruption. That is not the same skill.

Attention residue: why “quick” context switches aren’t actually quick

When you leave one task and jump to another, part of your attention often stays behind still chewing on the previous problem, still emotionally attached to it, still thinking about what you meant to say. That leftover attention is residue, and it reduces performance on the next task.

This is why “I’ll just answer this message real quick” can turn into 45 minutes of scattered re-entry. The message took 30 seconds. The recovery took the rest of your life. (Okay, not your life. But definitely your afternoon.)

So what’s real? Focus time is the unit of value

If attending time is the myth, focus time is the reality: uninterrupted blocks where you can think, build, write, solve, and finish. The work that creates outsized results usually requires continuitytime long enough to move past “getting started” and into “actually making something.”

This doesn’t mean you vanish into a cabin with no Wi-Fi and emerge only when you’ve invented a new element. It means you intentionally design the day so your brain is not constantly yanked between micro-demands.

Try the “two-lane day”: attending lane vs producing lane

A simple framework:

• Attending lane: messages, coordination, admin, quick decisions, lightweight meetings.
• Producing lane: deep work, writing, analysis, design, strategy, building, creative problem-solving.

The goal isn’t to eliminate the attending laneit’s to contain it so it doesn’t swallow the producing lane. When the attending lane expands without boundaries, it consumes the day and leaves only scraps for meaningful output.

How leaders accidentally reward the myth

Even smart teams fall into attending-time culture when measurement is fuzzy. When outcomes are hard to evaluate, organizations start measuring what’s easiest to see: responsiveness, meeting attendance, visible activity, late-night replies, and “always on” behavior.

The result is a system where people learn that availability is safer than impact. You can be wrong in a meeting with everyone else. You can’t be wrong alone shipping something.

Shift the scoreboard: from visibility to outcomes

Teams that escape attending-time culture do a few things differently:

• They define outputs clearly: what “done” looks like, not how busy it feels.
• They make decisions explicit: who decides, by when, using what inputs.
• They standardize async updates: fewer status meetings, more written clarity.
• They protect maker time: uninterrupted blocks are treated like infrastructure.

Ironically, this often makes teams more responsive where it countsbecause fewer interruptions means faster, higher-quality delivery.

A practical toolkit: 9 ways to stop worshipping attending time

1) Schedule focus like it’s a meeting with your future self

If you don’t reserve producing time, attending time will take itpolitely, continuously, and without remorse. Put focus blocks on the calendar, and treat them as real.

2) Batch communication windows

Instead of checking messages constantly, use set windows (for example, late morning and late afternoon). This reduces the “always reloading” effect that drains cognitive energy.

3) Replace status meetings with written updates

A short written update forces clarity, creates a record, and often surfaces blockers faster than a meeting. Then hold meetings only when discussion or a decision is truly needed.

4) Add an agenda or decline by default

No agenda, no meeting. Or at least: no agenda, no guaranteed attendance. Agendas aren’t bureaucracy; they’re a signal that the meeting has a job to do.

5) Shorten meeting defaults

If your calendar tool offers it, set default meetings to 25 or 50 minutes. You’ll be amazed how quickly “we should wrap” produces actual conclusions.

6) Build “decision packets”

For complex choices, write a one-page decision packet: context, options, recommendation, risks. Share it before any meeting. Most “decision meetings” become 10 minutes of real decision-making instead of 45 minutes of wandering.

7) Stack meetings (so they stop attacking your day in random places)

If your role allows it, group meetings into blocks or specific days. This reduces fragmentation and creates protected stretches for producing work.

8) Track outcomes, not activity

Make output visible: drafts shipped, decisions made, bugs resolved, clients helped, pages written, experiments run. When outcomes are visible, attending-time theater becomes less necessary.

9) Normalize “slow replies” during focus windows

Teams that respect focus time agree on response expectations. Not every message is an emergency. If everything is urgent, nothing is.

Conclusion: be less present, be more valuable

The myth of attending time survives because it’s comfortable. It’s measurable. It’s social. It’s busy. And it gives the illusion of progress without forcing the harder questions: What matters? What are we building? What are we deciding? What can we stop doing?

But value comes from outcomes, not attendance. If you want better workmore creative work, more meaningful work, more high-impact workyou don’t need more time “showing up.” You need more time actually doing the thing.

Reclaim your focus. Contain your meetings. Stop mistaking availability for achievement. Your calendar doesn’t deserve to be the main character.

Experiences you’ll recognize: five “attending time” stories (and the escape hatch)

To make this painfully real, here are five scenarios that show up in offices, remote teams, and hybrid setups everywhere. They’re not about any one personthey’re the kind of patterns that happen when the myth becomes culture.

1) The Calendar Tetris Champion

This person’s day is a flawless mosaic of back-to-back meetings. They are admired. They are booked. They are also quietly suffering. By 3 p.m., their brain is running on fumes and polite nods. Work that requires thinkingwriting, planning, solvinggets pushed to “later,” which becomes 9 p.m., which becomes resentment, which becomes burnout.

Escape hatch: stack meetings into tighter blocks, insist on agendas, and create two protected focus windows a week. Even small boundaries expose how many meetings never needed to exist.

2) The Instant-Replier Hero

They respond to messages in seconds. People love them. They feel essential. They are also constantly interrupted, constantly restarting, and constantly behind on their actual deliverables. They confuse responsiveness with reliability. The irony is that the team’s “go-to person” becomes the one person who can’t finish anything uninterrupted.

Escape hatch: set communication windows, update your status during focus blocks, and move repeat questions into a living doc. The team will survive a 90-minute delay. Your work might even improve.

3) The “Quick Sync” Collector

They don’t schedule “meetings.” They schedule “quick chats.” Ten minutes here, fifteen there, a “fast alignment” in between. Individually, each seems harmless. Together, they destroy continuity. The day becomes a series of restarts: open the file, remember where you were, get interrupted, reopen, re-remember, repeat until retirement.

Escape hatch: replace quick syncs with short written updates unless discussion is truly required. If it must be live, batch them. Quick isn’t quick when it’s everywhere.

4) The Manager Who Measures Green Dots

They don’t say they measure presence. They just ask, “Were you online?” and “Why didn’t you respond?” People adapt by staying visibly activemore replies, more meetings, more digital noise. Output quietly declines. Everyone becomes “busy,” and nobody is sure what’s moving forward.

Escape hatch: shift to output-based check-ins. Ask for progress artifacts: drafts, decisions, metrics, next steps. When outcomes are visible, the obsession with presence fades.

5) The Team That Finally Tried Boundaries

They experimented: no-meeting mornings twice a week, agendas required, written status updates, and meeting stacking on two afternoons. The first week felt weirdlike leaving the house without your phone. Then something happened: work started finishing. Not just “starting,” not just “discussing,” but finishing. People felt calmer. The team got faster. And the funniest part? They became more responsive, because fewer interruptions meant fewer self-created emergencies.

Escape hatch: start small, measure what changes, and keep what works. You’re not removing collaborationyou’re rescuing it from becoming performative.

SEO Tags