Latest / The Office Politics Podcast with Fexingo: Workplace Dynamics, Influence, and Getting Things Done / The Silent Killer Of Career Momentum
Transcript
- Lucas: Let's talk about the thing nobody puts on their LinkedIn profile but everyone feels every single day: the administrative tax. It's not the big strategic decisions or the client pitches. It's the twenty minutes spent waiting for a link to a document that hasn't been shared yet. It's the three emails back and forth clarifying a meeting agenda that should have been one calendar invite. Luna: Right. And the worst part is that it doesn't feel like 'work,' so we never track it. It just eats the space where actual thinking was supposed to happen. Lucas: Exactly. And looking at the broader landscape as of September fifteenth, two thousand twenty-six, this friction has only gotten worse despite the return to office mandates from companies like Amazon. They are pushing for five days a week, arguing that physical proximity solves communication gaps. But if you look at the internal metrics from several major tech firms, the number of cross-departmental meetings has actually increased by nearly thirty percent since those policies rolled out. Luna: That seems counterintuitive. If you're sitting next to someone, shouldn't you be able to solve things faster over a desk chat instead of scheduling a call? Lucas: It should, but the culture of visibility has shifted. When you're remote, you protect your calendar because you don't want to appear unproductive. In the office, there's this implicit pressure to be seen as available. So people fill their days with check-ins, sync-ups, and stand-ups that add no new information. You end up with what I call the 'visibility trap.' You're busy, but you're not moving the needle. Luna: I see that all the time with my engineering leads. They spend forty percent of their week in meetings that could have been an email, and then they complain they can't find time to code. Lucas: That is the classic symptom. The problem isn't laziness. It's fragmentation. Cognitive science tells us that when you switch tasks, your brain takes about twenty-three minutes to fully refocus on the original task. If you have a meeting every hour, you never get into that flow state where the heavy lifting happens. You're just skimming the surface of ten different problems all day long. Luna: So the solution isn't really about going back to the office or staying home. It's about restructuring how we allocate our attention blocks. Lucas: Precisely. And this brings me to a specific example that illustrates this perfectly. There was a mid-sized software firm called DevStream Solutions—they aren't household names, but their approach is replicable anywhere. Last year, they realized their project delivery times were slipping. Leadership assumed it was a talent issue, so they started recruiting harder. But when they audited the workflow, they found that developers were losing roughly eight hours a week to unnecessary status updates. Luna: Eight hours? That's basically two full working days lost every single week to just talking about work? Lucas: Two full days. So they made a radical decision. They abolished the weekly team status meeting entirely. Instead, they implemented a silent Friday afternoon report. Everyone submitted a brief written update on progress, blockers, and next steps. No discussion allowed during submission. Then, the following Monday morning, they only met if there was a blocker that required group input. If no one flagged an issue, the meeting didn't happen. Luna: Wait, so if everything is fine, nobody talks? That feels risky. How do they stay aligned? Lucas: It feels risky because we're conditioned to believe that alignment requires constant conversation. But in practice, most alignment comes from shared documentation, not shared screens. What happened after they made this change is what I'd consider a landmark case in modern productivity. Within six months, their average project delivery speed jumped by fifteen percent. Not ten percent. Fifteen. Because the developers finally had four-hour blocks of uninterrupted time to tackle complex architecture problems. Luna: That is a massive lift. But it requires a lot of trust, right? Leaders have to let go of the need to hear people's voices daily. Lucas: It does require trust, but more importantly, it requires discipline in writing. The silent report forces clarity. You can't hide vague progress behind a rambling verbal explanation. You have to write down exactly what you did and what you're stuck on. For managers, it becomes a filtering tool. They only engage when there's a real problem. It shifts the dynamic from performance monitoring to problem solving. Luna: I think that's the missing piece for a lot of professionals. We treat our calendar like a to-do list, but we rarely audit whether those calendar events are actually generating value. Lucas: Spot on. And here is the hard truth that many people resist: if you are invited to a meeting and you are not a decision-maker, you are likely the wrong person to be there. Or at least, you are being asked to do something inefficient. The best career movers I know are ruthless about declining meetings that don't have a clear objective and a defined outcome. They protect their deep work windows like they would protect a revenue-generating client call. Luna: That's a tough sell in a collaborative culture though. If you keep saying no, won't people think you're not a team player? Lucas: They might initially. But within a quarter, your output speaks for itself. People start realizing that when you are in a meeting with them, you are fully present and prepared, rather than distracted by the last three calls. You become known as someone who delivers high-quality work, not just someone who shows up. That reputation is worth infinitely more than attendance points. Luna: Yeah, quality over quantity. It reminds me of how some top-tier law firms handle billable hours. They don't reward you for sitting in the chair longer; they reward you for resolving the case faster. Lucas: Exactly. Legal is one of the few industries that still respects the concept of efficient resolution. Most corporate jobs still conflate motion with progress. You're running around the track, sweating, exhausted, but you haven't crossed the finish line. The goal is to stop running and just walk across the line efficiently. Luna: So, how do we start doing this? Is it okay to just cancel recurring meetings without asking permission? Lucas: Don't just cancel them silently. Frame it as an experiment. Say, 'Hey team, I've noticed we spend two hours every Tuesday reviewing updates that are already documented. I'd like to try replacing that with async notes for four weeks and see if we can free up that time for deeper project work. If it doesn't work, we'll bring the meeting back.' Most reasonable managers will agree because it saves budgeted hours. Luna: That's smart. It positions you as trying to improve efficiency, not just avoiding work. It makes you look proactive. Lucas: It does. And it gives you data. If the team thrives without the meeting, you've made a permanent improvement. If they struggle, you have evidence of where the gap actually is—usually it's not the meeting, it's the lack of good documentation. Either way, you've moved the needle. Luna: I love that framework. Data-driven changes are always easier to defend than subjective preferences. Lucas: Always. Now, before we wrap up this angle on protecting your focus, I want to mention something quick. A couple of dollars a month is genuinely what keeps these episodes coming out every day. If you've gotten something useful out of our breakdowns, support us at buy me a coffee dot com slash fexingo. It helps us keep the research sharp and the ads off. Luna: Yeah, even small contributions make a huge difference for independent creators like us. Thanks for listening. Lucas: Appreciate it. Let's circle back to the practical side of this. Once you've cleared the noise, what does a truly optimized week look like for a knowledge worker in twenty twenty-six? Luna: It probably starts with blocking out two mornings a week as sacred. No meetings, no Slack, just execution. Lucas: Two mornings. That's four hours. In that time, you could draft a proposal, analyze a dataset, or design a system component that would take a week of fragmented effort otherwise. It's not about working harder. It's about working in larger, cleaner chunks. Luna: And communicating that boundary clearly. If people know those blocks are non-negotiable, they'll learn to batch their questions for the open windows. Lucas: Exactly. You train your environment to respect your attention span. It takes a few weeks of consistency, but once it sticks, your career trajectory shifts because you're producing distinct, high-value work instead of just maintaining presence. Luna: It's a subtle shift, but it changes everything about how you're perceived. Less busy, more capable. Lucas: Right. The goal isn't to be the busiest person in the room. It's to be the one who gets the hardest problems solved while everyone else is drowning in logistics. That's where the real influence lives. Luna: So, next time you get invited to a meeting that feels like a catch-up, ask yourself: does this require my brain, or just my ears? Lucas: If it's just your ears, send a delegate or decline with the async summary. Save your brain for the problems that actually need you. What do you think? Is that a realistic standard for most offices right now?