Managing A Career

I help you navigate the path to professional success. Whether you're a recent graduate still searching for your place or a seasoned professional with years of experience, the knowledge and insights I share can show you how to position yourself for growth and career advancement.

Managing A Career is a business podcast hosted by Unknown Host, with 164 episodes on record and a Required Pod Score of 83.

Unknown Host hosts Managing A Career, a business show with 164 episodes published.

Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.

• 

  Episode #160

  Analysis Paralysis Is Just Fear Wearing a Lab Coat - MAC160

  Sep 29, 202620 min

  Nobody has ever been written up for doing too much research. That's what makes it such a good place to hide. In the biggest calls a career throws at you — the job, the promotion ask, the pivot you've been circling for two years. Research looks like diligence, and it feels like diligence the whole time. But past a certain point, it stops being research and starts being a well-dressed way of not deciding. The Spreadsheet With Fourteen Columns A recruiter reaches out about a role one level up, better pay, better title. You say you'll think about it, and because you're responsible, you build a spreadsheet. Salary, commute, benefits — sensible columns, all of them. By week two there's a column for the company's review-site scores, one tracking how long the team has stayed, one for a parental leave policy you may never use, one for something the CFO said on an earnings call. By week five you're at fourteen columns, you've reread the same three reviews, and when someone asks where you landed, you say the thing we all say: "I'm still doing my homework." That spreadsheet feels like the most responsible thing you've done all month. That's the problem. Think about what got you here. Every organization you've worked in has rewarded you for looking one more time. So when fear shows up around a decision this size, it doesn't show up as fear. It puts on the most respectable costume in your closet. Fear in a hoodie, you'd spot immediately. Fear in a lab coat looks exactly like thoroughness. A career counselor who specializes in this exact problem, LaRae Jome , makes a point worth sitting with: most people already know the steps of a good career decision — narrow your options, explore them properly, choose based on what you value. They still can't finish those steps, not from lack of knowledge but because finishing means feeling the uncertainty they've been avoiding. So they find another step. That's a different animal than the fear I described in Just Because You're Scared, Doesn't Mean You Do NOTHING . That fear freezes you. This one keeps you extremely, productively busy. The Association for Psychological Science names it as one of the clearest signs of overthinking: you've researched your options to death, and you're still not moving. To be clear, I'm not telling you to stop doing homework — even Jome tells her clients to explore thoroughly. I'm telling you there's a point where the homework is actually finished, and most of us blow straight past it without noticing. Research vs. Reassurance Here's the question I want you to ask at the end of every hour you spend on a decision like this: what do I know now that I didn't know an hour ago, and would it change my answer? That's the whole test. If you can answer it, you were doing research. If you can't, you were doing something else. Amanda Nimon-Peters , writing in Psychology Today, describes how your brain treats deliberation as a cost you pay to buy confidence. Normally you think until you're confident enough, then stop. But when no new information is actually arriving — you're just re-reading the same reviews, the same posting — you keep paying, and the confidence never shows up. It drops. That's the strangest part of analysis paralysis: the longer you research, the less sure you feel. So here's the distinction to carry out of this: research versus reassurance. Research changes what you know. Reassurance changes how you feel, for about an hour, then wears off and you need another dose. That's why the spreadsheet keeps growing. Research ends. Reassurance has to be refilled. There are three tells that you've crossed from one into the other. The questions repeat: a fourth set of reviews answering the question the first three already answered. The source changed. The information didn't. The criteria move. Every time one option starts to win, a new column appears — it was salary, then the commute, then the culture. When your criteria keep shifting, you're not refining the decision, you're protecting yourself from making it. And the hardest one to admit: you're researching after you already know. Somewhere in week two you knew what you wanted, and every hour since has been a search for permission, or for the one piece of evidence that would let you off the hook. You're not looking for information anymore. You're looking for an exit. The Research Receipt Noticing these tells in the moment is hard, so here's a tool. I call it the Research Receipt. At the end of every session you spend on a decision you write one line: the new fact you bought, and whether it moved your decision. You paid for that session with your time. The receipt tells you what you actually got for it. When you can fill in the line, that session was research. When you can't, it was reassurance — and you just learned that too. Three blank receipts in a row means your homework is finished, whether it feels finished or not. A blank receipt isn't a failure. It's a finding. When you get that blank receipt, there's a second question worth asking — the same one from the Control Filter episode : what is the research protecting me from? Almost always it's one of a handful of things: being told no, being wrong where others can see it, wanting something out loud and not getting it, or plain regret — the fear that a better option existed and you took the wrong one. That last one deserves a minute. Career advisors at the National Institutes of Health , applying Barry Schwartz's paradox-of-choice research to careers, describe the maximizer haunted by the possibility that something better existed — a pattern that curdles into chronic restlessness with jobs that are actually good. No amount of research closes that gap, because the better option doesn't exist yet. Finish Lines "Stop researching" is useless advice unless you know what done looks like, so here are the finish lines for the three decisions people stall on most. For a job change, you're done when you know four things: the actual scope of the role (not the posting), who you'd report to, because you've talked to them, the compensation in writing, and one real conversation with someone who's done the job or recently left it. Past that point, the review sites and earnings calls are noise for your decision. They're about the company. Your decision is about the job. For a promotion ask, you're done when you know what the next level requires, you have your evidence gathered — if you've kept a brag document , that's already sitting there — and you know when those calls get made. You will never feel ready enough to ask. The ask itself is the research: whatever your manager says back tells you something you couldn't have found out any other way. For a pivot, you're done when you've talked to three people who do the work and done one small, real piece of it yourself: a side project, a stretch assignment, a few hours helping the team you're circling. Reading about a field and trying it are different kinds of information, and only one tells you whether you'll like it on a Wednesday. Notice what those finish lines share. Almost every one ends in a conversation or an action, not another article. Past a certain point, the only new information left comes from doing something. The last piece of research is almost always a move. Most Career Doors Swing Both Ways Back in Fast to Decide, Slow to Act , I borrowed Jeff Bezos's idea of one-way doors and two-way doors: a one-way door is hard or impossible to reverse, a two-way door you can walk back out of. I said a one-way door deserves a slower process, and I stand by that. What I didn't talk about then is how often we mislabel the door — and which direction we get it wrong in. Fear makes every door look one-way. Take the promotion ask at two in the morning. It feels final — if they say no, everyone knows it. Now walk it forward in daylight. The worst realistic outcome is "not yet," and now you know exactly what the gap is, which you didn't before you asked. That's not a one-way door. That's a two-way door with a prize behind it. Sort a few decisions you might be sitting on. Asking for the promotion: two-way door. Interviewing for a role: two-way door, and you can walk away right up until you sign. An internal transfer: mostly two-way, because people move back, or move again a year later. Leaving for another company is heavier, but more reversible than it feels — people go back to former employers constantly. I know this personally: I'm on my second stint with my current company, having left for a better opportunity...

  ListenShow Notes
• 

  Episode #159

  Are Your Emotions Holding You Back - MAC159

  Sep 22, 202621 min

  It's 11:40 on a Tuesday night, and you are not asleep. You're replaying a sentence. Your skip-level said it around two-fifteen that afternoon, in a meeting with five other people in it: "Let's make sure we're being realistic about that timeline." You've run it back maybe forty times since. Tried it with the emphasis on realistic . Tried it on that . Drafted three replies you're never going to send. Somewhere around the thirtieth replay, you picked up your phone, which is how it got to be 11:40. So here's a question worth sitting with: in the nine and a half hours since that sentence was said, what has the worry actually done for you? That's the question underneath this episode. Not how to get rid of the worry, the fear, the anxiety, the flash of jealousy that shows up when somebody else gets the promotion. Not a case for toughening up, and not permission to leave your feelings at the door. What follows is a sort — a way to run any of those feelings through two questions and come out the other side knowing whether it's something to act on or something you can honestly put down. Feeling It vs. Carrying It Start with what this isn't. It isn't an argument for becoming a cold, unfeeling operator at work. In years of managing people, the ones who insisted they didn't feel anything about their jobs were usually the ones feeling the most — just quietly, and at their own expense. Emotions at work are normal, and they're useful. Stress As A Signal, Not A Symptom (MAC-146) made the case that stress is information before it's a problem; the same holds for the rest of the list. Worry, fear, anxiety, jealousy — every one of them is pointing at something. The trouble starts when you don't follow where it points. Alice Boyes, a former clinical psychologist, wrote a piece for Harvard Business Review on what anxiety does to us at work , and the list is specific: it makes you misjudge what other people think of you, it makes you defensive about feedback, it makes you see the risk in a new idea before you see anything else, and it makes you avoid the situations that would actually move your work forward. Notice that none of those is the feeling itself — every one is a behavior. The anxiety doesn't cost you the stretch assignment. Avoiding the stretch assignment does. So here's the distinction worth carrying forward: there's feeling an emotion, and there's carrying one. Feeling it is the part that happens to you — the jolt in the meeting, the sting when you read the email. It's fast, it's human, and you don't get a vote. Carrying it is everything after that — the replays, the unsent drafts, the version of the conversation you keep having with yourself in the car. That part, you do get a vote on. Feeling is the immediate reaction. Carrying it takes the rest of the week. One caveat before the framework: this is about the ordinary emotional weather of a working life — the worry after a meeting, the sting of somebody else's promotion, the dread before a review. If the worry doesn't lift, if it's following you everywhere and not just to work, if it's taking your sleep for weeks rather than a night, that's not something a sorting exercise fixes, and it's not something a career podcast should try to fix. Mental Health and You (MAC-042) covers this directly: put your own oxygen mask on first. If stress has become overwhelming, reaching out to a professional or an Employee Assistance Program is the right move, and there's nothing weak about that conversation. The Control Filter So how do you tell which feelings to act on and which to put down? There's a prayer a lot of people already know, even without ever being near a twelve-step meeting. Usually credited to the theologian Reinhold Niebuhr: God, grant me the serenity to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference. That last line is doing all the work. Psychologists have taken it seriously enough to study — the Association for Psychological Science has written about the science behind the Serenity Prayer — and the tension it names sits underneath an enormous amount of what people struggle with at work. Knowing the difference isn't a trait you're born with. It's a sort, and a sort is something you can practice. Most people already run a version of it. They just run it on the wrong thing. They ask, "can I change what caused this?" — and they ask it about the trigger. The sentence the skip-level said. The promotion announcement. The reorg rumor. The answer is almost always no, so they conclude it's one of the things they cannot change and tell themselves to accept it — and then carry it anyway, because "accept it" is easy to say and nearly impossible to do when you haven't figured out what "it" is. Here's the sort to run instead. Call it the control filter, and it's two questions. Question one: what is this actually about? Not what set it off — what it's about. The trigger is the event; the source is the thing inside you that the event landed on. The skip-level's sentence is the trigger. The source is not knowing whether she thinks the estimate is wrong — and underneath that, a worry about being quietly filed as someone whose timelines can't be trusted. Question two: is there a move? One thing, inside your control, that you could do this week — not something that requires somebody else to change first, but something you can do. If there's a move, the feeling just became a to-do. Do the move, and the feeling has finished its job — it got your attention, pointed you somewhere, and you went. If there's no move, the feeling is weight. It can't tell you anything more, and carrying it won't change the outcome. So you name it, and you set it down on purpose. Run it on the 11:40 sentence. The trigger isn't yours. But the source — I don't know what she meant, and I'm afraid of what it might mean — has an obvious move: you ask. Something like, "You mentioned being realistic about the timeline — is there a risk you're seeing that I should be building in?" That's the whole move. The feedback episode on why that kind of question works (MAC-148) covers this in depth — the person giving you feedback is a witness to how something landed, not a judge handing down a verdict, and the most useful thing you can do with a witness is ask what they actually saw. Once that message is sitting in your drafts for nine a.m., the worry has nothing left to do. The trigger is rarely yours. The source usually is. Try it once more on something bigger. Picture a reorg rumor — two weeks of closed-door meetings, nobody saying anything. The trigger is about as far outside your control as anything at work ever gets. But what's the source? For most people it's something like: the person drawing the new boxes doesn't know what I do. And that has a move — you can make what you do legible. If you've been keeping the Brag Document (MAC-141) , this is the week it pays for itself; if you haven't, this is the week you start one, with a short note to your manager on what you've delivered this quarter, while there's still a conversation to be part of. And then some of it really is no-move: whether the reorg happens, where your team lands, who your next manager is. Those go on the other pile, and that's fine. The filter isn't a promise that everything is secretly in your control — it's a way to stop treating the controllable parts as if they weren't. Have To vs. Get To (MAC-140) talked about locus of control — whether your default is to believe your outcomes are driven by you or by the world around you. The more useful way to hold that now: you choose it one feeling at a time. Every time you run the filter on the source instead of the trigger, you're moving the locus back inside — not by pretending the reorg is yours, but by finding the part of the problem that is. Setting It Down Is Not Pushing It Down About that second pile: "set it down" does not mean "push it down." The two phrases sound almost identical and do opposite things. Pushing it down is suppression — gritting your teeth through the rest of the meeting, telling yourself you're fine, scrolling your phone until the feeling goes quiet. It looks and feels like control for about an hour, and it's the move most professionals were trained to make, because the workplace rewards the person who looks unbothered. The problem is that it doesn't work. Pushing a feeling down turns out to be counterproductive in most cases — the feeling doesn't leave, it relocates. It shows up in your sleep, in your body, in how short you are with somebody who had nothing to do with it, and in the quality of your work the next day. You don't get out of feeling it — you just move the bill....

  ListenShow Notes
• 

  Episode #158

  Not Every Failure Counts Against You - MAC158

  Sep 15, 202618 min

  Two people walk out of two different meetings having heard the same sentence: it didn't work . One of them skipped a step in a process the company has run four hundred times. The other tried something the company has never tried. Same sentence, same tone in the room, same quiet adjustment in how each of them gets described in the next talent review. That's the problem underneath this whole piece: your organization almost certainly cannot tell those two people apart. Not because anyone up the chain is cruel — because sorting the difference is genuinely hard and the meeting has twenty minutes. That failure to sort is expensive in a very specific, very avoidable way, and there's a fix that costs about ninety seconds and changes the entire conversation. Three kinds of wrong Before any of this is useful, the terminology has to be exact. Amy Edmondson, a Harvard Business School researcher who has spent a career studying how organizations handle things going wrong, lays out three distinct kinds of failure, and argues they need opposite responses . A basic failure has one cause, is usually preventable, and happens in territory that is completely known — the invoice with last quarter's numbers, the wrong client name in the deck, the checklist step skipped because the day ran long. There's no mystery and no glory here. A basic failure needs a system, not a lesson. A complex failure happens when several things go wrong at once and no single one of them would have caused the problem alone — the vendor slips a week, the reviewer is on leave, the requirements quietly changed in a meeting nobody wrote down. You don't eliminate complex failures. You build slack and make the pieces visible to each other. And an intelligent failure is the one nobody teaches. Edmondson sets four conditions for it : it happens in genuinely new territory where no playbook exists; it's a credible route toward something that matters; it's informed by what you already know, not a wild swing; and it's kept as small as possible while still teaching you something. An intelligent failure isn't a mistake. It's the price of information you couldn't have bought any other way. I want to sharpen something I said in an earlier episode, Own Your Mistakes, Deliver Results (MAC-149) . I stand behind most of it, but I treated "your mistake" as one category — a thing you step toward, own cleanly, and move past. What I missed is that a good chunk of what gets called your mistake was never a mistake at all. It was a bet. And owning a bet the way you'd own an error isn't integrity — it's a filing error, and you're the one who filed it. Here's the distinction: a mistake is something you should have known. A bet is something nobody knew. Notice that has nothing to do with the outcome — both end in it didn't work . The difference sits entirely in what was knowable beforehand, which is exactly the information that disappears the moment the result is on the table. The lane nobody is driving in Most organizations respond to all three kinds of failure identically — not from cruelty, but because sorting them is slow and the meeting is short. So the org reacts to the outcome, the one piece of information everybody already has. Basic, complex, intelligent — same flinch, same footnote in the calibration room. I covered where that instinct goes once it's left alone in The Blame Game (MAC-099) ; what's happening here sits one step upstream of blame, in the sorting that never occurs in the first place. People learn fast, and what they learn isn't "don't be careless." It's "don't be the person standing next to the uncertain thing." They stop volunteering for the ambiguous project. They stop floating the idea that would need a real test. I've watched this happen to people who were, on paper, the strongest performers in the room. None of them decided to become conservative — they just took the only signal the system was actually giving them: unpredictability is expensive . That produces an empty lane. Almost everyone in your organization competes in the same place — flawless execution on known work — because that's where the incentives point. Meanwhile the genuinely ambiguous projects go undersubscribed year after year, carrying a risk everyone has correctly identified and nobody has learned to manage. Everyone wants the person who takes smart risks. Almost nobody wants to be the person mid-risk. That gap is the opportunity, and it's not because risk-taking is inherently virtuous — plenty of people have torched a career on a wild swing they couldn't explain afterward. It's that the skill of running a bet well is rare, visible when present, and almost never taught. Being the person who can take the ambiguous project and give leadership a clean account of it either way is a method, not a personality trait — and the method is learnable. There's a line I keep returning to on the show, from Seneca: luck is what happens when preparation meets opportunity. I built an early episode around it in A Little Bit of Luck (MAC-013) , and returned to it in Posting Publicly (MAC-144) and Manufacturing Serendipity (MAC-147) . In those episodes, the missing half was almost always opportunity — people preparing in private and waiting for a door to appear. Here the equation inverts. The opportunity is already staring you in the face: the empty, ambiguous project everyone else is avoiding. Standing next to it without the right preparation doesn't make you lucky — it makes you exposed. The preparation that matters here isn't another title or another hour of overtime. It's learning to run a bet cleanly, so that what looks like a lucky break to everyone else in the room is just preparation meeting the door nobody else opened. There's a habit worth building alongside this. A Princeton professor once published what he called a CV of failures — the grants he didn't get, the papers rejected, the jobs he didn't land — and it traveled further than his actual research. The venture firm Bessemer keeps a public version, an "anti-portfolio" of the enormous companies they had a chance to invest in and passed on. Keep your own private version. If you already keep the brag document from MAC-141 or the prevention ledger from MAC-155 , this is one more column in the same file: what you bet, why it was reasonable at the time, what it cost, and what you now know that you couldn't have known any other way. The brag document records what worked. The prevention ledger records what never broke. This one records what you were willing to find out. The stated bet None of the above protects you on its own. Here's the mechanism, and it's smaller than you'd expect: the reason a bet gets processed as a mistake has almost nothing to do with the bet. It has to do with when you described it . Picture the version most people run. You believe something will work, you spend six weeks on it, it doesn't work. Now you're standing in front of your manager explaining that this was always exploratory, that the outcome was uncertain, that you learned a lot. Every word might be true. It doesn't matter — you're saying it after the result, so it arrives as a defense, and a defense carries the smell of the thing it's defending against. Run the same six weeks with one difference. Before you start, on the record, out loud, to whoever would have to approve it, you say: here's what I think is true that nobody here has tested, here's what result would tell me I'm wrong, here's when I stop. Six weeks later, the identical failure — but what you're delivering is not a defense. It's the answer to a question you both agreed to ask. That's the whole move. I call it the stated bet , and the entire mechanism is sequence. Said afterward, it's an excuse. Said beforehand, it's a method. Two pieces go into it. The claim : what you believe that isn't currently known, stated plainly enough that it could turn out to be wrong. "I think we're losing most of these renewals in the first two weeks, not at the contract date" is a claim. "I'd like to explore the renewal process" is not — it can't fail, which means it also can't teach you anything, and your manager can feel that even without naming it. The stop is the piece people skip: what result, or what date, ends this. A stop condition feels like planning to lose, but it's what makes the whole thing affordable. Edmondson's fourth...

  ListenShow Notes
• 

  Episode #157

  It's Easier to Disappoint Yourself Than Someone Else - MAC157

  Sep 8, 202615 min

  Two things went on your calendar this quarter. The first was a commitment to someone else. That meeting, you have never moved it once. When it landed on top of your own doctor's appointment, the doctor got rescheduled. The second was an hour you blocked for yourself — the certification, the analysis you keep meaning to start, the conversation you keep meaning to have. You have quietly moved it four times, and not one person has mentioned it. Same calendar. Same you. The only difference is who was standing on the other side of it. I heard a line on a podcast a while back that I have not been able to put down. It came from Jam Gamble, a speaking coach, on an episode of Amy Porterfield's show , and it was this: it's easier to disappoint ourselves than someone else. Nine words. And they explain more about stalled careers than most of the advice I've given on this show. The Two Debts When you let another person down, the cost arrives immediately and it has a face attached. You watch it land. There's a pause on the call, a shorter reply than usual, a follow-up question with a little edge on it. Even when the other person is completely gracious about it, you carry it around for a day. Psychologists who study this have a clean explanation for why it stings as much as it does: letting someone else down disappoints them and disappoints you in the same moment. You pay both bills at once. Now run the other one. You told yourself you were going to finish the certification. You told yourself you were going to have the compensation conversation before the cycle closed. You told yourself this was the quarter you'd stop being the person who does the recurring report and start being the person who does the analysis on top of it. You didn't. And nothing happened. No pause on the call, no edge in the reply, no follow-up. One debt has a creditor standing in the lobby. The other one has nobody, so it never gets collected. Here's what that does over a career. Therapists who work with chronic people-pleasers describe the same workplace pattern over and over — the extra work absorbed without recognition, the compensation conversation that never gets scheduled, the feedback that never gets asked for. Every one of those is a decision to protect somebody else's afternoon at the expense of your own year. I want to be precise here, because this is where most advice on this topic goes wrong: that is not a character flaw. Reading the room, absorbing the load, being the person who doesn't let people down — those are the exact behaviors that got you hired and got you trusted. Nobody needs to become less reliable. The actual problem is that you're running the calculation with one of the two costs set to zero. And the zero compounds in a way the other cost never does. Miss a deadline for your manager and the bill arrives once, gets paid, and closes. Defer the certification, the compensation conversation, or the pitch you keep meaning to make, and the bill doesn't arrive at all — which means it never gets paid, which means it's still sitting there next quarter, plus whatever the market did to the value of that move in the meantime. A missed external deadline is a bad week. A promise to yourself that never gets collected on is a bad decade, made one invisible quarter at a time. Why the Promise to Yourself Breaks It isn't willpower, and I want to get that off the table early. Think about any commitment you made to another person this month that you actually kept. Trace what came attached to it. It had a date — a real one, on a shared calendar, that someone else could see. It had a witness — at least one person who knew about it and would notice its absence. And it had a cost — something that visibly happens if it doesn't happen: a slipped release, an unhappy stakeholder, a number that doesn't get reported on Friday. Date, witness, cost. You didn't install any of those. They arrived pre-attached, because the organization attaches them automatically to anything the organization needs. Now trace the promise you made to yourself. The date is "this quarter," which isn't a date. The witness is you, and you are extremely understanding. The cost is a vague sense that you're behind, which is a feeling, not a consequence. A promise to someone else arrives with a date, a witness, and a cost already attached. A promise to yourself arrives naked. This is also why "just be more disciplined" is such useless advice. The coaching literature backs this up: the gap between knowing what to do and doing it is almost never a knowledge problem or a willpower problem. Sometimes it's fear wearing the costume of caution — I'll start the certification when this project calms down. Sometimes it's an identity that hasn't caught up yet — the actions you'll take are bounded by who you currently think you are. And frequently it's just that you're empty at 6pm. I've talked about the fear half of this before, in Just Because You're Scared, Doesn't Mean You Do NOTHING (MAC-123) . What I didn't say clearly enough in that episode is that fear rarely stops the action by itself. Fear is what makes you want a reason to defer. The missing structure is what lets you. You didn't lack the will. You lacked a witness. Nobody Was Ever Assigned to You Pull up your org chart. Every function on it has an owner. Revenue has an owner. Delivery has an owner. Quality, headcount, the budget, the roadmap, the incident queue — every one of those has a name next to it and a person whose performance review depends on it. Now find the box that says responsible for this person's growth. It isn't there. Not because your company is careless, and not because your manager doesn't care about you. I said this back in Your Manager Is Not Your Career Sponsor (MAC-139) and it holds here: your manager is measured on delivery, on retention, on the operating plan. If they invest in your growth, they're doing it out of the margins of a job that is fully spoken for. The good ones do it anyway. It still isn't what the system pays them for. The system isn't ignoring you. It was never pointed at you. Which means every mechanism that makes other commitments stick — the shared calendar, the status update, the person who will ask about it Thursday — exists because the org needed those commitments kept. It built the machinery for its own priorities. It didn't build any for yours, and it isn't going to. This is the part of Who is driving your career? (MAC-025) I'd sharpen today. Owning your career isn't a posture or an attitude. Coaches who work with senior professionals frame it as running your career the way a founder runs a business — you invest, you experiment, you act before it's perfect. I like that framing, but a founder doesn't just feel responsible. A founder builds the operating system: the deadlines, the reviews, the board that asks uncomfortable questions on a schedule. You already know how to build that machinery. You build it every week. You've just never built it for yourself. Borrowed Urgency Here's the move, and I'm giving it a name so you can reach for it later: borrowed urgency . It's taking the three things that make someone else's commitment stick — a date, a witness, and a cost — and installing them on one of your own, deliberately, because nobody is going to install them for you. A date means not "this quarter." It means a specific hour, on your actual calendar, in the same system where your other meetings live — the Protecting Time In Chaos (MAC-137) discipline pointed inward. The hour is only real if it can collide with something; if it never collides with anything, you didn't schedule it, you hoped for it. A witness is one person who knows the date and will ask about it. This is the single highest-leverage piece of the three, and it's the one everybody skips, because it feels like making a big deal out of something small. Tell your manager you're finishing the certification by a specific date. Tell a peer you're sending the analysis to the ops lead by Friday. You've just converted a private intention into a promise to another person — and you already know, from decades of evidence about yourself, that you keep those. Pick the witness the way you'd pick anything else that has to actually work. A witness who's too polite to follow up is decoration, not structure — you've told them, but you haven't given them permission to ask. A witness who's too busy to remember has the same problem as no witness...

  ListenShow Notes
• 

  Episode #156

  Measuring Invisible Work - MAC156

  Sep 1, 202617 min

  here is a specific moment this episode is built around, and you have almost certainly lived it. You are writing up your contribution — for a review, a self-assessment, a conversation you are trying to prepare for. You know what happened. You know it mattered. You get to the word saved — "which saved us about" — and you stop. Because the next word is supposed to be a figure, and you do not have one. So you write "a lot of time" instead, and the sentence quietly dies. That is the failure point. And it is not a laziness problem. It is a permission problem. You believe that to put a dollar figure on your own work, you would need the real number — HR's actual turnover model, finance's actual cost-per-incident, something audited and defensible that lives in a system you do not have access to. Since you cannot get it, you conclude you are not entitled to a number at all. And so you arrive at every performance conversation armed with adjectives while the organization around you runs entirely on estimates. The revenue forecast in that room is an estimate. The headcount plan is an estimate. The projected savings from the reorg somebody presented last quarter was, structurally, a guess with a confidence level and a name attached to it. Nobody in that room is working from audited truth. They are working from numbers somebody was willing to own. You are not missing the data. You are missing permission to estimate. There is a second thing working against you: you will aim low. Most people place their own contribution below where outside evidence puts it, and the error runs in that direction far more often than the other. The career self-diagnostic episode (MAC-152 at managingacareer.com/152) covered this in detail — the calibration gap is real, it is directional, and knowing about it does not automatically fix it. So when you finally do reach for a number, your instinct will be to shave it. Know that going in. Where the numbers actually live. There are three sources, and you probably have access to all three right now. The first is public. There is a whole industry of aggregated employer data sitting in the open, and it covers exactly the metrics leadership already watches. On turnover, for instance, the pooled employer numbers put the cost of replacing someone at roughly 40 percent of their salary for a frontline role, around 80 percent for a mid-level professional, and north of 200 percent for a leader. That is not your company's model. It is a range your company's model almost certainly falls inside. The second place is your own organization's ordinary paperwork — the one people never think to check. The job posting for the role you helped fill has a salary band printed on it. Your recruiting team's open requisitions tell you how long a seat stays empty. Your own calendar tells you how many hours a month go into the meeting you eliminated. None of that is confidential. It is just sitting there, un-mined, because you have never thought of a job posting as a pricing document. The third place is a person. Somebody in finance, HR, or ops owns the cost you are trying to estimate, and they will usually answer one specific question if you ask it as a specific question. Not "what does turnover cost us." That gets you nothing. Try: "When we backfill an analyst on my team, roughly how long does the seat sit empty?" That is answerable in one line, and it is the only piece you were missing. The anchor number. The thing you build out of those three sources has a name, and naming it is what makes it usable. Call it an anchor number: a public or borrowed figure you pick up on purpose, label out loud as borrowed, and use as the starting point of an estimate rather than the end of one. Forty percent of salary is not what your company pays to replace somebody. It is the number you multiply against until somebody hands you a better one. An anchor number is not your company's number. It is a number you can defend while you wait for a better one. The one rule that matters: say where it came from. The whole thing works if you say "using the industry benchmark of roughly 40 percent of salary" and it collapses the instant you say "our turnover cost is." One of those is an estimate with its sources showing. The other is a claim you cannot back, and the moment somebody checks, every other number you have ever given them gets re-examined too. The repricing pass — four moves. Take one entry and walk it all the way from a note to a sentence. Move one: name the metric. Which of the four does this touch — turnover, ramp time, rework, or escalation? Pick one. Most entries touch two, and you will be tempted to claim both. Do not. Two half-credible numbers read worse than one solid one. Move two: find the unit. Every metric has a thing you count. Turnover counts people. Ramp counts weeks. Rework counts hours. Escalation counts incidents. Figure out what you actually moved and how many of them. Move three: attach the anchor. Price the unit using one of your three sources. Move four: put the assumption inside the sentence. Not in a footnote. In the sentence, out loud, where the person hearing it can see exactly what they would have to disagree with. Here is what that looks like, fully worked. The entry: I cut the new analyst's ramp from six weeks to three. Metric: ramp time. Unit: weeks of one person's capacity. Anchor: the salary band on that role's own job posting — say it topped out around ninety-five thousand. Fully loaded, with benefits and payroll tax, that is conventionally somewhere around a quarter to a third above base, so call it one hundred and twenty-three thousand a year, or roughly twenty-four hundred dollars a week. A person still ramping is not producing nothing — call it a third of full output early on. So each week you removed is worth about two-thirds of twenty-four hundred. Sixteen hundred dollars. Three weeks, call it five thousand. And the sentence: "I cut the new analyst's ramp from six weeks to three. Using the posted band for that role and assuming a new hire runs at about a third of output in month one, that's somewhere around five thousand dollars of recovered capacity — and I'd expect the same on the next two hires, because the onboarding doc is reusable." Five thousand dollars is not an impressive number. That is the point. It is a number that survives a follow-up question, and every step of it can be walked backward in front of a skeptic. A number you can walk backward beats a bigger number you cannot. The discipline the whole episode rests on: show the arithmetic instead of presenting the total. Label how confident you are in each input — you can be highly confident about a posted salary band and only medium confident about the output assumption, and saying so makes you more credible, not less. And when you are choosing between the modest figure you can defend and the impressive figure you would have to defend with adjectives, take the modest one. Always. Two more examples across different work: Rework. Entry: I rewrote the recurring report so people stopped guessing at it. Metric: rework. Unit: hours. Four people were spending about ninety minutes a month each re-deriving what the report meant — that is six hours a month, seventy-two hours a year, call it two working weeks the department stops burning. High confidence on the hours, because you can ask the four people. Medium confidence on whether every one of them actually reinvests it. Escalation. Entry: I caught the client discrepancy on Friday before it reached their finance team. Metric: escalation. Unit: incidents. You do not have to model this one — go find the last time it was not caught. "The last time this got through, it took four people two days and a written apology." That is your anchor. It happened at your own company, and it costs you one search to find. One number vs. a track record. This is where the episode turns on itself, and on purpose. Because the natural response to a framework this clean is to use it once — the week before your review, on three entries — and then never again. That version mostly does not work. Not because the numbers are wrong, but because of what one number sounds like when it arrives alone. One number that appears the week before performance conversations reads as advocacy. It reads as somebody who went looking for ammunition, and the person hearing it discounts it accordingly. Ten numbers, produced steadily over two quarters, read as something else entirely. They read as a person who tracks their own work, which is a character claim you cannot make about yourself and can only demonstrate. Nobody has to believe you about it. They just look at the record. One number is a claim. A quarter of them is a track record. This also matters because of where those numbers have to travel. Your manager is not your career sponsor (MAC-139) — the decisions that move you happen in rooms you are not in, made by people who have never watched you work. What crosses into those rooms is whatever your advocate can repeat from memory. "She's great with the new people" does not survive that trip. "She cut analyst ramp by half and the onboarding doc is reusable" does,...

  ListenShow Notes

Recent guests on Managing A Career. Study who booked and why before you pitch.

Based on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:

Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.