You Walked Into a Finished Vote

You Walked Into a Finished Vote

You know the numbers. You can walk into any room and lay out the projects you've shipped, the revenue you've influenced, the problems you've solved that nobody else would have touched. You've rehearsed the narrative. You believe that if you just tell the story well enough, to the right person, at the right moment, the answer will be yes. And here's the part that stings: in most of the organizations I've walked through, the decision about who's next was made six to nine months before the formal conversation ever happened. Not by a committee. Not by a rubric. By a slow accumulation of who got pulled into certain rooms, who got the stretch assignment, who the VP mentioned by name in a Tuesday sync while the rest of the team just got the link to the deck.

The Allocation You Didn't Ask For

The myth is that influence is a presentation. A deliverable. Something you build, polish, and hand over. It isn't. It's a sequence of small allocations that compound before you ever open your mouth. Who cc'd you on the thread. Who asked for your input on the plan versus who just sent you the finished version for awareness. Whether you were in the room when the problem was still fuzzy, or brought in after the shape was already decided. I've watched people spend three months building a business case for a promotion, present it cleanly, and get a warm "let's revisit next quarter." Not because the case was weak. Because the person making the call had already mentally assigned that seat to someone else four months prior. The room isn't neutral. It's pre-loaded, and you walked in expecting a blank slate.

The Part That Doesn't Resolve Cleanly

Here's where it gets uncomfortable. The people who seem to get ahead aren't the ones with the best slide deck. They're the ones who were already operating at the next level in the small, unglamorous moments. The one who reframed the problem in a two-line email before the meeting. The one who spoke up in the cross-functional sync when nobody else would. But even that doesn't guarantee the seat. Because the allocation isn't purely merit-based. It's proximity-based. And proximity is a function of who the leader already trusts, which is a function of history, not performance. So the question that actually matters isn't how to build a better case. It's who you're in the room with, in what capacity, six months from now. And whether you'll recognize that the window is closing before it actually closes.

The Approval Step Nobody Built

The Approval Step Nobody Built

You're about to ask for another hire. You've got the deck, the business case, the at-capacity language ready to go. But before you send that request, there's a question that's harder to answer than the headcount number. How many steps in your process exist because they were added in 2019 and nobody has questioned them since? I've walked through operations where a $200 vendor invoice went through four approval layers. Four. Each one added a person's name to a document. Each one added a day to the cycle. And when you ask who actually needs to see this before it goes out, the answer, more often than not, is nobody. The step didn't fail. It just never had a job.

The Step Is Not the System

Here's the distinction that changes how you look at your org chart. An approval step is not the same thing as a control. A control exists to prevent a specific, named risk. Finance reviews vendor invoices over $500. That's a control. The VP signs off on all purchase orders regardless of amount. That's a step. One is doing work. The other is a person's name on a form. When I sit down with a leadership team and we go through their order-to-cash process line by line, the pattern is consistent. The steps that survive scrutiny are the ones where you can name the risk they prevent. The ones that don't survive are the ones where the answer to what goes wrong if this person doesn't see this is nothing, we just always did it. That's not a process. It's a tradition, and traditions don't scale. They just get more expensive.

The Headcount Math Changes

Now here's where it gets uncomfortable. When you pull those unnecessary steps out of the equation, the headcount math changes in a way that's hard to argue with. You thought you needed two more accountants because the volume was too high. But the volume wasn't the problem. Every invoice was getting routed through a manager review that added three days of idle time per transaction. Remove the step, and the same two people clear the queue in half the time. You just didn't need to ask for the hire in the first place. And that's the part that stings, because the request for the new person was the easier conversation. Pointing at your own process and saying this step is doing no work is the harder one. It means looking at the org chart and asking the question that makes the room go quiet.

The One That's Still There

But here's the edge case that keeps me up. Sometimes the step isn't decoration. Sometimes it's a person's only reason to feel like their role matters. I've been in the room where a process owner hears this step can go and their face does something complicated. Because for them, that step is the proof they're needed. And now you're asking them to remove their own proof. That's not an operations problem anymore. It's a people problem wearing an operations costume. You can't cut your way through it with a process diagram. You can only walk into that conversation knowing the step is doing no work, and then decide what you owe the person who built their identity around it. That decision doesn't have a clean answer. It just has a cost, and the cost of not having the conversation is the one you're already paying.

Using AI a Lot Is Not the Same as Being Good at It

Using AI a Lot Is Not the Same as Being Good at It

You prompt AI ten, fifteen times a day. You've got it open in a browser tab next to your calendar, your CRM, your email. You're not slacking. You're not the person in the meeting who still copies text between windows. And yet something feels off. You can't explain why the output you get is always the same, why you keep landing in the same shallow loop, why the person who only touches it twice a week somehow gets results that make you look like you're using a calculator. The metric everyone keeps pointing at is frequency. How many prompts a day, they ask. As if volume is the skill. It isn't.

The Distinction Nobody Draws for You

Here's the split that matters. There's a difference between running AI and redesigning with it. One person asks it to summarize a meeting, every day, for three months. They've built a habit. They've got volume. The other person spent an afternoon rethinking how they write a client proposal, found the two or three steps where they were actually doing the thinking, and rebuilt that sequence so AI handles the scaffolding while they handle the judgment. One is volume. The other is fluency. And fluency compounds in ways volume never will, because volume just makes you faster at a task you already knew how to do.

The Person Doing Less Might Be the One Building Something

And here's where it gets uncomfortable. The people who are genuinely good at this don't look like power users. They look like they're doing less. They ask fewer questions. They spend more time before they type, and more time after they get the answer. They're not grinding. They're thinking. Which means the person in your org with the AI usage dashboard glowing green, the one with the highest prompt count, might be the one most at risk of being replaced by the very tool they're logging hours against. And the person using it twice a week, deliberately, might be the one actually building something. You can't tell from the dashboard. That's the problem.

You Designed for the Easy Day

You Designed for the Easy Day

You built the process on a Tuesday. Everyone was in. The tickets were light. No one called in sick. You mapped the workflow, set the escalation path, told yourself this is how it works. Then Thursday hit and the whole thing dissolved. I have seen this pattern across billions of dollars in managed operations, and it is always the same shape. The system works until the first exception. The SOP was written by someone who had never been on the other side of the phone at 2pm when the server is down, the key person is on a flight, and the client is asking for an answer in four minutes. You did not design a system. You documented a memory.

The Calm Version Is a Fiction

You think you are being thorough when you write down the steps for a normal day. You are not. You are writing a script for a play that only gets performed once. The real job is the improvisation. It is the 6pm quick question that is actually a scope change. It is the vendor who says they just need a minute and then needs a week. I watched a team at a 200M company rebuild their onboarding process three times in eight months. Not because the business changed. Because they kept designing for a world where every new hire arrives on schedule, with complete documentation, and without a single question in the first 48 hours. That world is not the world.

What the Worst Day Actually Requires

The worst day is not a failure state. It is the operating state. The difference between a system that survives and one that collapses is whether you built it for the Tuesday or the Thursday, and most people cannot tell which day they are on until it is already Thursday. Here is the thing I still sit with. If you design for the worst day, the easy day starts to feel like overkill, and people push back. They call it paranoid. They say that is not how we operate. And they are right. They operate for the easy day. They just do not have a name for it.

Same Work, Different Outcome

Same Work, Different Outcome

You spent eleven months rebuilding the onboarding system. Fixed the broken handoff between sales and delivery. Wrote the SOPs nobody asked for but everyone needed. Sat in the Tuesday standups, answered the questions, closed the tickets. And at the end of the year, the person who came in three months after you, who did maybe sixty percent of what you did, got the promotion. Not because they were better. Because you were quiet, and they were loud.

The Distinction Nobody Names

Here is the thing that separates those two trajectories, and it is not effort. It is not output volume. It is whether the work was narrated as it happened or discovered after the fact. The person who narrated did not do more work. They did the same work, but they left a trail. A Slack message noting where they got stuck and what they tried. A short update in the channel. A paragraph in the Friday note about what the new process actually changed. That trail is not bragging. It is the difference between your work existing and your work being legible to the person making the decision.

The Part That Sticks

And here is where it gets uncomfortable, because the fix is not just posting more. If you narrate every task, you become noise. If you narrate only the wins, you become a highlight reel and lose the trust of the people who need you to be the person who actually solved the problem. The real question is not whether to narrate. It is what the act of narrating costs you in the moment, and whether that small cost is cheaper than the eleven months of silence that preceded the promotion you did not get. I do not have a clean answer for that. I have watched people solve it and people who never do, and the difference was not confidence. It was whether they treated the telling as part of the doing, or a separate act that required permission they never gave themselves.

You've Been Doing Two Jobs and Only Naming One

You've Been Doing Two Jobs and Only Naming One

You wake up and your day is already three roles deep before your first meeting. You're the one who closes the deal, fixes the process that broke at 2am, and keeps the vendor relationship from quietly imploding. None of those three things are in your job description. You didn't sign up for them. They just... arrived. I've sat across the table from forty-plus operators in the last few years, and the pattern is almost boring in its consistency. People absorb work by default, not by design. They pick up the second function because nobody else will, or because the gap was there and they were standing next to it. And then six months later, the second job is 30% of their week and nobody in the org chart knows it exists.

The Circled List

Here's the part that surprises most people when I ask them to write down everything they did last week, every single task, and then mark the ones that fall outside their actual title. The list is longer than they think. Not by a little. By a lot. I had a VP of Operations tell me she was spending four hours a week writing the content briefs for a marketing team that didn't exist. Another had become the de facto onboarding lead for a team of twelve, a role that had no owner, no budget, and no name. The work was real. The hours were real. The role was not. And because the role was not named, it had no owner, no scope, and no leverage. It just sat there, getting heavier, while the person carrying it told themselves they were "just being helpful."

Why Nobody Names It

The second job stays invisible because naming it costs something. Name it and you're either asking for a title change, a pay adjustment, or a headcount that the budget doesn't cover. Name it and you're admitting the org has a gap, which means someone else's planning was wrong. So the path of least resistance is to keep doing the work and call it "part of the job." The problem is that "part of the job" is a phrase that expands to fill any container you put it in. It will swallow your weekend. It will swallow your promotion case, because the second job never shows up in a review. It will swallow your authority, because you can't delegate a role that technically doesn't exist. And the quietest cost of all: you start to believe the second job is who you are, not something you're doing. That's the part that's hardest to walk back.

Busy Is the Laziest Excuse You Have

Busy Is the Laziest Excuse You Have

You're in the quarterly review and someone asks what moved forward this month. You open your mouth and the words that come out are that you've been so busy. You say it like it explains something, like it's a full answer. In twenty years of running operations across industries, I've heard that phrase in maybe eight out of ten status meetings. And I can tell you, the people who say it most are rarely the ones producing the most. They're the ones who can't point to a specific thing that got built, shipped, or closed. The room hears effort, and the room does not respect effort. It respects output. And you just gave them nothing to point at.

The Word Does Different Work Than You Think

Here's a distinction that most people never sit with. Busy is a process word. It describes motion, duration, the feeling of time passing. It does not describe a result. A developer who has been busy for three weeks might have the same pull request as one who has been busy for four days. A sales rep who has been busy all quarter might have closed two deals or zero. The word absorbs all the ambiguity and lets you hide behind the hours instead of the artifact. I've watched teams log 40 hours a week and produce a single slide deck, and I've watched others work 20 focused hours and ship a product update that moved revenue. The hours were never the variable. The output was. And busy is the one word that keeps you from having to name it.

Where the Real Problem Actually Lives

And here's the part that makes it worse than a simple bad habit. Sometimes the person is genuinely overloaded, but the system that created that overload is the same system that rewards the phrase because it's the only answer that doesn't expose a gap in planning, delegation, or scope. The excuse isn't just lazy in the moment. It's lazy across quarters. It keeps the real structural problem invisible, and the person saying it knows that. That's why the phrase comes out so fast, so automatic, before they have to think about what actually got done. Here's the edge case that keeps me up at night. What if the person who's genuinely doing the most work is the one who says it least? What if the quiet operator who shipped three things this quarter never opens their mouth in the meeting, and the one who did nothing but schedule calls gets the nod? The system rewards the performance of effort, and the person who actually produced is the one who looks most replaceable in the room.