Managing A Career

Hosted by Layne Robinson

Business

Website RSS feed

Episodes

168

Latest episode

Oct 2026

Language

About the show

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.

Listen to episodes

60 recent

November 3, 202624 min

Hope Is Not A Strategy - MAC165

When people called Terry Rice lucky, he had an answer: luck is when preparation and opportunity are met with action. In Luck When Preparation and Opportunity Meet Action (MAC-162) we covered the action. Five words, Hey, I like your podcast , said at a free kids' gymnastics class in Brooklyn, turned a chance meeting with Jason Feifer, the editor in chief of Entrepreneur, into a working relationship and eventually real money. This is that method. Two Rooms, One Method Terry is a consultant. Everyone he wants to reach lives outside his company, mostly on social media, so the method he described on the Help Wanted episode where he told this story is built for the outside world. Most of us work in two rooms: the company we work for now, and everything outside it. The four moves work in both, but they build two different things, and if you don't know which one you're building, you'll aim them at the wrong people. Inside your company, you're building a network . Outside it, you're building a reputation . A network is the people who know you : your manager's boss, the leads of the teams next to yours, the person who runs the talent review. They decide your next role here, and what you need from them is access and trust. A reputation is the people who know what you're known for : peers at other companies, people who write and speak in your field, recruiters. Most will never meet you. What you need is an accurate sense of what you're good at, so your name comes up when a door opens elsewhere. Inside, you want to be known. Outside, you want to be known for something. The research lines up with the split. Herminia Ibarra and Mark Hunter studied thirty managers stepping into leadership and described three kinds of networks : operational, personal and strategic. Almost everyone neglected the strategic one. Your internal network covers the operational and strategic kinds; your external reputation lives mostly in the personal one. Move One: The List of Forty Terry keeps a list of about forty people he wants to be known by, and they have to be active : people who post, reply and show up. A famous name who hasn't answered a comment in three years doesn't belong on it. Why forty? Three is a bet that one of them has a need at the exact moment you're paying attention. Four hundred is too many to pay real attention to. Forty is the size where you can keep up with what each person is working on, and that's the point, because you can't offer specific help to someone whose work you don't know. It's the idea from Building a Network (MAC-029) with a number attached: depth beats count. There's also a research reason not to fill the list with close friends. Randomized experiments on LinkedIn across roughly twenty million people found that moderately weak ties, people you know but not well, produced the most job moves. Inside the company , much of the list comes from the org chart: your manager's boss, the leaders of teams your work depends on, someone who sees across the business, a person who has run the project you want next. The trap is an internal list made entirely of peers. Peers don't decide your next role, and, the person you report to often can't move your career alone. Put some names a level or two above you. Outside the company , the list skews toward people who publish, speak, organize or host something in your field: the person who runs a regional user group, a writer whose newsletter your industry reads, a hiring manager who posts about their team. Active beats famous here too. Split the list roughly half and half, leaning internal if you want to grow where you are and external if you're planning a move soon. Write it down. A list you keep in your head is a wish. Move Two: Comments Before Connections Terry's rule: connections are made in the comment section, not by sending a connection request. A request asks a busy person to accept a stranger on faith. A comment asks for nothing, shows up where they already are, and lets them decide whether you're worth knowing. Terry spent about a year commenting on Jason's posts before that gymnastics class. A comment worth answering carries one of three things: a specific detail from your own experience, a real question they could answer, or a useful addition they didn't include. "Great post" carries none of them. After the comment comes a direct message once they know your name, then a call or coffee. Inside the company , picture your skip-level posting an update about a cost problem their organization is chasing. You've seen the same problem in your own team's numbers, so you reply in the thread with one line on what you saw and one question about whether it matches what they're seeing. You didn't ask for a meeting. You added something to their problem, where their peers could see it. Internally, the comment section is the meeting thread, the shared channel and the question you ask out loud in a review. That's the advice from Visibility (MAC-081) , that a well-timed question is one of the cheapest ways to be seen, now aimed at someone on your list. Outside the company , the comment section is literal, and the stakes are higher. A thoughtful reply is visible to their whole audience, so it starts a relationship and builds your reputation at once. Write it as if it might be quoted: specific, generous, and with no links to your own work. If the posting episodes left you stuck, a comment is your on-ramp: the smallest possible post. The rule from "What If My Boss Sees This?" (MAC-164) applies: talk about the pattern, and keep the situation inside the building. Move Three: Name the Help Terry never asks "how can I help?" He shows up with the help already named. "Let me know if there's anything I can do" sounds generous, but it hands the work of figuring out what you could do back to the busiest person in the conversation, so the offer sits there, unanswered. After the coffee with Jason, Terry recorded a short, unrequested video walking through three or four specific ways to improve a page Entrepreneur was using to sell a new product. It was small, usable immediately, and easy to forward to the people who owned that page. Days later, Jason was in a meeting where nobody had the marketing background they needed, and he said, I know a guy. A specific offer shows your thinking instead of describing it. This is also the move most likely to backfire. An unsolicited offer is only as good as your read on what the other person actually needs. If it fixes a problem they don't think they have, it's noise. If it says "here's what you got wrong," it reads as "I'm smarter than you." If it's really about showing off, it's a pitch. Terry's video could easily have gone that way. My read is that it worked because a year of following Jason's work told him what Jason cared about and how he'd take outside input. So this is not an invitation to sell yourself. It's a legitimate offer to help with a problem they're facing right now. If you can't name that problem from something they've said or done, go back to commenting. Help solves their problem. A pitch solves yours. Inside the company , this is the most powerful of the four moves, and the safest. Your manager's boss mentions in a staff meeting that they're preparing a quarterly review and the numbers are a mess. You say, "I pulled something similar for our team last quarter. I could put together a one-page summary of the trend by Thursday if that would help." They said the problem out loud first, so you're not guessing. If that sounds like Busy Is Not Visible (MAC-161) , it should: the forwardable update is a specific offer you make to your manager every month. Outside the company , the offer looks like Terry's video: a short teardown of something they've published, a written answer to a question they asked publicly, or an introduction to someone they'd want to meet. As Building Someone Else's Network (MAC-079) showed, an introduction is one of the most valuable offers there is, and it costs you one email. There's a line here: generosity is a strategy, unlimited generosity is free labor. Keep the offer small, finishable in about an hour, and inside the company, work you're allowed to do. Give once, then let them decide what comes next. Move Four: Send It Before It's Perfect The last move is the one Terry was most honest about. He wrote his early messages to Jason in Microsoft Word, then pasted them into Instagram, where the spacing fell apart. At the coffee, he talked, in his words, fifty miles a minute. He was sure he'd blown it both times. Jason doesn't remember either one. People don't grade you like a...

October 27, 202618 min

“What If My Boss Sees This?” — Posting Publicly While You Still Have a Job - MAC164

You've written the post. It's good. It's a real lesson from a real project, and you know it would help somebody. Your thumb is over the button, and a second voice shows up that has nothing to do with whether the post is any good: what if my boss sees this? I've spent a run of episodes on public posting. In You Need to Be Posting Publicly (MAC-144) I made the case for why. In What to Post When You Think You Have Nothing to Say (MAC-153) I gave you the catalog of what to post. And in The Empty Result (MAC-154) we looked at whether anyone can actually find it. This episode is the objection I never fully answered in any of them. How do you build a public body of work while you still have a job, without leaking anything confidential, without badmouthing the place that pays you, and without your manager quietly concluding that you're halfway out the door? The Fear Is Reasonable Most advice on this topic treats hesitation as imposter syndrome. Just be confident, just share your journey, just hit publish. That isn't what's going on for most of the people I talk to. They aren't worried that they have nothing to say. They're worried that they'll say the wrong thing. They signed an NDA they haven't read since their first week. They work somewhere with a social media policy they've never opened. And at some point they watched a colleague post something that seemed harmless and then get a call from HR. That isn't insecurity. It's pattern recognition. So I'm not going to tell you the fear is wrong. I'm going to tell you it's aimed at the wrong target. When you unpack it, it's two fears tangled together. The first is the fear of leaking: saying something about a client, a number, a project, or a person that isn't yours to say. The second is the fear of signaling: posting in a way that makes your manager wonder whether you're looking. Those are different problems with different fixes, and the reason most people stay frozen is that they never separate them. Visibility vs. Exposure Here's the distinction I want you to carry out of this episode. Visibility means people can see how you think: your judgment, your expertise, the way you approach a problem, the lessons you've drawn from the work. Visibility is about you . Exposure means people can see things that aren't yours to show: your employer's clients, numbers, internal decisions, a colleague's mistake. There is a second kind of exposure too, which is your own plans. Anything that tells the world, and your manager, that you're looking for the exit is exposure. Exposure is about them , or about your next move. Most people treat these as the same thing. They assume any public presence carries exposure risk, so the safe choice is silence. But silence isn't safe. It's just invisible. As we covered in the Empty Result episode, when someone with the power to change your career goes looking for you and finds nothing, they don't conclude "no data." They draw a conclusion about you. And the people searching aren't only recruiters. Managers look you up. Skip-levels look you up. The VP deciding who gets the new initiative looks you up. The goal isn't to avoid being seen. The goal is to be visible without being exposed. Now the signaling fear, which is the one people talk about least and feel most. What actually makes a manager wonder if you're leaving? It's mostly not posts about your field. People who study the mechanics of quiet job searches point out that the clearest signals are statements about your plans : a headline announcing you're seeking a new position, membership in job-hunting groups. Regular posts about your profession read as what they are, a professional who's engaged in their field. A post about how you think through a vendor negotiation says I'm good at my job . A headline that says open to new opportunities says I'm leaving my job . One is visibility. The other is exposure. A strong public presence, done well, also does something for your current employer. It makes them look like a place with thoughtful people in it. Not because you're writing press releases, because you shouldn't be a corporate mouthpiece, but because a smart practitioner who happens to work there is good for everyone. Engaged reads very differently from disloyal. The Abstraction Ladder That handles the signaling fear. The leaking fear needs a tool rather than a reframe, and the tool is what I call the Abstraction Ladder. Every piece of work you do can be described at three levels, three rungs on a ladder. The bottom rung is the situation : the specific thing that happened. Who, what, when, how much. Names, numbers, the client, the internal fight. The bottom rung belongs to your employer. The middle rung is the pattern : what tends to happen in situations like this one, anywhere. The specifics are stripped out but the shape remains. The top rung is the principle : the lesson that would hold in any company, in any industry, in any year. The rule is simple. You post from the middle rung or the top rung. The bottom rung stays inside the building. Let me walk one example all the way up. Imagine you just finished a project consolidating three regional vendor contracts into one. It took six months and it saved real money. The hardest part wasn't the negotiation with the vendor. It was the regional team in one office who'd had a relationship with their old supplier for a decade and fought the change at every step. On the bottom rung, that story sounds like this: "We consolidated our three regional freight vendors into a single contract, saved one-point-two million dollars, and the Midwest team fought us the whole way." Every word belongs to your employer: the vendor, the savings figure, the team that resisted. You don't post that. Climb one rung and you get the pattern: "When you consolidate vendors across regions, the negotiation is rarely the hard part. The hard part is the local team that's losing a relationship they built, and nobody budgets time for that." Same story, nothing identifiable, and still specific enough to help someone about to run the same kind of project. Climb one more and you get the principle: "Every consolidation project is a change-management project wearing a procurement badge." That one you could put on a slide at a conference. This works far beyond procurement. A marketing manager who just ran a rebrand has a bottom rung of agency, budget and an executive who hated the new logo, and a middle rung that rebrands stall in the approval chain far more often than in the creative work. A software team that just finished a painful migration has the same three rungs. The ladder doesn't care what department you're in. Here's what surprises people: the middle and top rungs are the parts readers actually want. Nobody outside your company cares which vendor you picked. They care what you learned that they can use on Monday. Consultants who think carefully about sharing expertise without giving away their intellectual property make exactly this move. They turn detailed execution into principles, frameworks and diagnostic questions, and keep the templates, workflows and internal decision logic private. You're doing the same thing as an employee rather than a firm. Two Tests Before You Post The ladder tells you where to post from. You still need a way to check that you actually climbed. I run two tests on anything before it goes out. The first is the recognition test . Practitioners who write case studies about client work covered by an NDA use a version of it: could the client read this and recognize themselves? I'd widen it. Could your client, your colleague, your competitor or your CEO read this and identify the company, the project or the person? If yes, you're still on the bottom rung. Replace names with generic descriptors, "a regional distributor" instead of the company's name. Turn exact figures into approximations or drop them. Remove the one detail that makes the story unique. The second is the any-employer test . Would this post still be true if you worked somewhere else? If the lesson only makes sense inside your company, it's probably a situation, not a pattern. And one more thing, because it's where good people slip: tell the story without a villain. The regional team that fought the vendor change isn't the bad guy in your post. They were losing something real, and the system hadn't given anyone time to manage that. That's not just safer. It's more accurate, and it's the more useful lesson. If your post needs someone to be the idiot for the point to land, you haven't found the point yet. In plain terms: safe to share are how you think, the frameworks you use, the questions you ask at the start of a project, lessons with the specifics stripped out, and opinions on your field. Not safe to share are screenshots, internal numbers, client and vendor names, org charts, anything about a specific colleague, and...

October 20, 202620 min

The Strategic Audition - MAC163

You have fifteen minutes on the calendar with a vice president who oversees two hundred people. She's been friendly from the first second. She leans forward, smiles, and asks the easiest question in the world: "So, what's your team working on right now?" And you answer it. Of course you do. The vendor migration. The new intake form. The quarter-end reconciliation. About three projects in, you notice she's nodding the way people nod at a weather report. You've just spent the most valuable fifteen minutes of your quarter taking an exam nobody asked you to take. This is a sequel. In Skip Level 1x1 (MAC-064) , I made the case for asking for a skip-level at all, since most people never request one, and I gave three goals for it: build the relationship, highlight your contributions, and learn where your leader is taking the organization. All of that still holds. What that episode didn't give you was the words. This one is the script. The oral exam versus the strategic audition Most people prepare for an oral exam. They assume the leader is checking whether they know their stuff (what the team is doing, what's on schedule, what's late), so they rehearse the status. But a vice president with two hundred people doesn't need your project list. Somebody already put it in a deck. What the deck can't tell them is how you think. Can this person see past their own desk? Do they understand what I'm actually worried about? When something breaks, do they bring me a complaint or a choice? Those are the questions a senior leader is quietly answering in fifteen minutes. That isn't an exam. It's an audition, and it assesses judgment. An exam looks backward. An audition looks forward. The standard advice doesn't get you very far here. Search for skip-level questions and you'll find long lists of perfectly reasonable ones : what do you hope our department achieves this quarter, where is the company going, what feedback do you have for me. Good questions. They're also the questions everyone else on that leader's calendar is asking this month. They get you an answer. They don't get you remembered. So instead of thirty questions, here are three moves and a way to fit them into fifteen minutes. They only work after one piece of homework. Look up before you walk in Your team has a scoreboard: deadlines hit, requests closed, campaigns launched, the month-end close finished on time. You know it cold, because it's the one you're measured on. Your skip-level leader has a different one, measuring outcomes, risk, and a much longer time horizon. Most people walk in knowing every number on their own scoreboard and none on the leader's, then wonder why the conversation felt polite and flat. So before the meeting, build the Leader's Scoreboard : a three-line page with your best guess at what this leader is measured on this year. Not what they care about in general. What their boss will ask them about. Look in places you've already been: the all-hands slides, the goals your organization published at the start of the year, earnings calls or annual reports if you work somewhere public, and the requests that keep reaching your own team from that leader's office. Whatever gets asked for over and over is on the scoreboard. One guardrail: this is homework, not espionage. You read what's been shared openly. You don't interview your manager for gossip or poll colleagues for what they've heard. If you wouldn't be comfortable saying where you read it, it doesn't go on the page. Then translate. Rewrite each of your current projects the way the leader would describe it. A practitioner piece on speaking to senior leaders puts the principle plainly: drop the internal vocabulary and talk about the business outcomes they actually track . "The vendor migration" becomes "we're taking about four days out of the month-end close." Same work, different scoreboard. And your page will be partly wrong. That's the point. It's a guess you bring into the room to be corrected, and being corrected by a vice president in the first five minutes is about the best thing that can happen to you. Move one: the Strategic Horizon The first move is a question: "What's the metric leadership is watching most closely this quarter that you think our team isn't paying enough attention to?" It doesn't ask the leader to summarize strategy, which they've done at every all-hands. It asks them to name a blind spot, and specifically yours, which tells them you're willing to hear it. With your homework done, sharpen it: "My read is that what you're watching hardest this year is the cost per order in the new region. Is that right, or is it something else?" Now you've handed them a draft to edit, and people love editing a draft. That same Learning Guild piece recommends simply asking executives which results they expect. This is that question, aimed one level past the obvious. Then stop talking and write down whatever they say, because there's a decent chance your own manager doesn't know it yet either. In Are You Asking the Right Questions? (MAC-150) , we talked about how a good question can signal more than a good answer. This is that idea at the highest altitude you'll get all year. Move two: the Tradeoff Test The second move is how you bring up a problem. Consider a finance team where the month-end close drags because three regions submit numbers in three formats. "Our close process is broken" is true, and it's also a grievance: it hands the leader a feeling and no decision, and in a skip-level it can sound like a complaint about your manager. The Tradeoff Test turns the same problem into a choice, in three parts: the choice the organization is currently making, what each side costs, and what you'd recommend. "Right now we're letting each region keep its own format, which saves them rework. The cost is about four days of reconciliation every month on our side. If we standardized, they'd take a one-time hit and we'd get most of those days back. I'd standardize, starting with the two largest regions." Now it's a decision about a system instead of a person, and you've shown judgment at the level above yours because you weighed somebody else's cost. It works in any function: in marketing, "We're choosing a full brand review on every asset, which costs about a week per campaign. I'd move low-risk formats to spot checks." If that sounds familiar, it should. In Own the Problem, Bring Solutions (MAC-084) , we talked about taking a problem to your manager when you already have a plan and need approval to run it. The Tradeoff Test is that habit one level up. Your manager needs to know you can own a problem. Their boss needs to see that you understand what the fix costs somebody else. Worried about a recommendation that turns out to be wrong? A piece from Arizona State on what makes someone start to sound like an executive argues that having a perspective, even one that isn't guaranteed to be right, is what signals confidence and leadership. A leader can disagree with your recommendation. They can't do anything with your frustration. One rule: the tradeoff is never about your manager. In Your Manager Is Not Your Career Sponsor (MAC-139) , we talked about how your manager is constrained by the same system you are. Describe the system. Leave the people out. A grievance asks them to feel what you feel. A tradeoff asks them to decide. Move three: the Memory Anchor Some weeks after your skip-level, your name will come up in a room you're not in: a talent review, a calibration meeting, a conversation about who leads the new initiative. Somebody will ask that leader, "Do you know this person?" and they'll have about one sentence to answer with. The Memory Anchor is you writing that sentence for them, said near the end of the meeting. Something done, what changed, and what it was up against: "The short version of my year is that I took the close from nine days to five, while the regions were changing systems underneath us." No adjectives about yourself, no list, nothing a stranger would need context to repeat. If the leader could say it to a peer next month without getting it wrong, it's done. If you heard Busy Is Not Visible (MAC-161) , this may sound like the Forwardable Update. It's a cousin, not a twin. The Forwardable Update is written, goes out monthly, and travels through your manager. The Memory Anchor is spoken, once, and placed directly with the person above them. One reaches the leader secondhand. The other reaches them in your voice. You won't be in the room when they decide. Your sentence can be. The fifteen-minute run of show Before the meeting, send a one-line agenda ("I'd love to hear what you're watching most closely this quarter, and share a little about...

October 13, 202618 min

Luck Needs a Verb - MAC162

Five words. Hey, I like your podcast. That's what a man said to a stranger at a free kids' gymnastics class in Brooklyn. A few years later those five words were worth, in his own estimate, hundreds of thousands of dollars. And when people hear that story, almost all of them reach for the same explanation: he got lucky. This week on Managing A Career I want to fix something I've been saying on the show for years. The line wasn't wrong. It was missing a piece, and the missing piece turns out to be the one that does the work. The Line I Keep Coming Back To Luck is what happens when preparation meets opportunity. I built one of the earliest episodes of this show around it, A Little Bit of Luck (MAC-013) . I came back to it in Riding the Coattails of Others (MAC-117) , then Manufacturing Serendipity (MAC-147) , and most recently Intelligent Failure (MAC-158) , where the opportunity was the ambiguous project everyone else was avoiding. Every one of those episodes is about one of the two ingredients. Get prepared. Then find the opportunity, or build it, or notice it's already in front of you. And every one of them quietly assumed that once you had both, the rest would take care of itself. It doesn't. Terry's Version The missing piece came from an episode of Help Wanted , the podcast Jason Feifer hosts with Nicole Lapin. Jason is the editor in chief of Entrepreneur magazine, and if his name sounds familiar, it's because I've referenced him before. His posts and podcasts have sparked several episodes of this show, including Owning Your Mistakes (MAC-055) , Taking Action (MAC-098) , A Keg of Ketchup Will Make You Rethink Your Career (MAC-126) , and Are You Asking the Right Questions? (MAC-150) . On that episode he sat down with Terry Rice , a business development consultant who writes for the magazine. Jason raises the obvious objection, the same one I just put in your mouth: wasn't that just luck? And Terry answers with a version of my line, with one ingredient added. Luck is when preparation and opportunity are met with action. Then he maps his own story onto all three, and it is much less magical than "he got lucky." The preparation was about a year of following Jason's work. Terry listened to the podcast. He read the posts. He commented on as many of them as he could, with real comments. That year is the only reason he recognized the man across the room at a gymnastics class. The opportunity was the class itself. A free session, and the editor in chief of the magazine Terry had publicly said he wanted to write for was standing there on the phone. The action was a sequence of small, slightly awkward steps. He walked over, apologized for interrupting, and said those five words. He followed up with a direct message that named specific ways he could help. That became a coffee. That became a short video, recorded unasked, pointing out three or four ways to improve a page Entrepreneur was using to sell a new product. A few days after the coffee, Jason was in a meeting about a launch where nobody had the marketing background the team needed. Jason said, I know a guy. That's the whole break. Jason tells his side of it in his newsletter , and his read is fair to both of them: part of it was luck, but Terry had built every possible way for that luck to break in his direction. There's a whole method underneath that story, and it gets its own episode. Terry keeps a list of people he wants to be known by, around forty of them. Connections are made in the comment section, not by sending a connection request. He never asks "how can I help?" He shows up with the help already named. And he is ruthless about not waiting for things to be perfect. Those come later. Today I want to stay with the bigger point: out of the three ingredients, the third is the only one anybody else could see. Ready vs. Moving Think about everything Terry did in that year of preparation. Almost all of it happened inside his own head and his own feed. If he had stopped there, he would have been extremely well prepared and completely unknown. The year was real. From Jason's side of the room it was invisible. There is being ready , and there is moving , and most of us treat the second as something that happens automatically once we've finished the first. Ready is a property of you. Moving is a property of what other people can see. In thirty years I've watched a lot of genuinely prepared people stay exactly where they were. They'd done the course. They'd noticed the opening, the role next door or the director short on people for a new initiative. They were qualified to walk through the door. Three weeks later it had closed, and from the outside it looked like they'd never been interested. Nobody saw the preparation. Everybody saw the silence. A formula that circulates in startup circles makes the same point with a little math: luck equals doing times telling . What you actually do, multiplied by how many people effectively know about it. It's multiplication, not addition, so you can be a ten on doing, and if you're a zero on telling, the answer is still zero. It's the same reason I keep pushing you to post publicly, which we covered in You Need to Be Posting Publicly (MAC-144) . The posting was never the point. It's a way of moving work you've already done into a place where someone else can see it. The Smallest Visible Move "Take action" is advice you've heard a thousand times and it's never once gotten anybody off the bench. So here is something more concrete. The smallest visible move is the smallest step toward an opportunity that another person could actually notice. Not the biggest step you can imagine. The smallest one that leaves a mark on somebody else. It comes with a test, which is the whole reason it's useful: if nobody else could know you did it, it was preparation, not action. Run your last month through that. Researching the team you'd like to join? Preparation. Updating your résumé? Preparation. Rehearsing what you'd say to that director if you ever got the chance? Preparation. All of it might be necessary, and none of it has moved you an inch, because none of it has reached another human being. Now look at what passes. A thoughtful comment on something that director posted. A two-line message to the person running the new initiative. A question asked out loud in the meeting that shows you've been paying attention to their problem. An offer of help that names the help. Terry's first move was five words long. That's the size I'm talking about. Preparation happens in private. Action happens in front of somebody. Where Preparation Hides If the move can be that small, what stops us? Preparation itself. It's the most respectable place there is to hide, because from the inside it feels exactly like progress. I see it take three shapes. One more course. You've seen the opening and decide you need one more credential before you're allowed to raise your hand. Sometimes that's true. Much more often the people already doing the job don't have it either, and the course is a way of feeling busy while you postpone the moment someone might say no. One more draft. The message to the hiring manager or the note to the person you met at the conference sits in your drafts for nine days, and each time you open it you improve one sentence and close it again. One more month. Things will be calmer after the quarter closes, after the reorg settles. This is the most dangerous of the three, because it never feels like a decision. It feels like patience. It's a close cousin of Analysis Paralysis Is Just Fear Wearing a Lab Coat (MAC-160) . That episode was about one decision you keep researching instead of making. This is the broader version: a whole posture of getting ready that never quite turns into going. And while you're getting ready, the window is closing. Terry tells two stories about his own imperfect action, and I love both. He wrote his messages to Jason in...

October 6, 202616 min

Busy is what you are. Visible is what they remember. - MAC161

It's Friday afternoon, and you've just sent the weekly update. Eleven bullet points, every one of them true. Met with the vendor. Reviewed the draft. Followed up on open items. Closed out the quarter-end checklist. Eleven bullets that cost you something like fifty hours. Your manager skims them on the way to another meeting. Your manager's boss never sees them at all. By Monday morning, the most important thing you did all week exists in exactly one place: your own memory. This episode is for the person who hears "be more visible to senior leaders" and thinks, I would love to, and I don't have a single free hour to do it. If you're fully allocated, buried in delivery, and quietly suspicious that the people two levels up have no idea what you do, you're right to be suspicious, and there's a fix that doesn't ask you to work more. Busy Is Not Visible Let me start with the distinction the whole episode hangs on, because most of us blur it without noticing. Busy and visible are not the same thing, and they aren't even measured in the same place. Busy is a property of your calendar. Visible is a property of somebody else's memory. We've talked about visibility before, in Visibility (MAC-081) and again in Your Manager Is Not Your Career Sponsor (MAC-139) . Every time, I get the same fair reply: Layne, I hear you, but I'm already at capacity. You're asking me to take on a second job. I'm not. Think about how a senior leader actually encounters you. It's in fragments: a line in your manager's monthly report, thirty seconds of a project mentioned at an all-hands, your name on slide nine of somebody else's deck. They don't see the fifty hours. They see whatever compressed version of those fifty hours happens to reach them, and that version is almost always written by someone who wasn't doing the work. That isn't carelessness. It's the shape of the job. A director with a hundred and twenty people in their organization makes decisions about budget, projects, and promotions for people they have spoken to three times. They have to decide on partial information, and the only open question is whose information it is. A group of executive coaches writing for Forbes put the hard version plainly: the belief that your work should speak for itself is outdated thinking . I'd go one step further. Work doesn't speak. It gets spoken about , usually by someone else, usually in a room you're not in. Busy is what you are. Visible is what they remember. Promoting Clarity, Not Yourself Before the mechanics, a word to everyone who flinched when I said visibility. Some of you find self-promotion genuinely distasteful. You'd rather do the work than talk about the work, and announcing your own wins in the team channel makes your skin crawl. I respect that. Over thirty years I've managed a lot of people like that, and they are very often the best people on the team. But let me reframe who visibility is for. It isn't for you. It's for the person making the decision. When a senior leader is deciding who gets the stretch assignment, which team gets the headcount, or whose name comes up in the talent review, they need clarity to decide well. If you leave them guessing, you aren't being humble. You're making their job harder, and you're letting the guess be made by whoever happened to talk loudest that quarter. A piece on building strategic visibility without self-promotion contains a line I've more or less adopted as my own: visibility is not about promoting yourself; it's about promoting clarity. One framing is about you. The other is about the person on the other end, who has forty decisions to make this week and would love one of them to be easy. If you're one of the quiet ones, two habits will carry you a surprisingly long way. The first: give credit out loud, and own accountability in private. When the work goes well, name the people who made it go well, specifically and publicly. When it goes badly, take that conversation into a one-on-one. It sounds like the opposite of a visibility strategy, but the person who reliably makes other people look good becomes someone senior leaders trust with more people. The second habit is restraint. You don't need to speak in every meeting. You need to speak at the pivotal moment and say one precise thing. The person who delivers one sharp sentence in the quarterly review is remembered over the person who talked every five minutes. You're not promoting yourself. You're reducing their guesswork. The Forwardable Update So what does promoting clarity look like on a Tuesday when you have no time to spare? One short document, once a month. I call it the Forwardable Update: a short monthly note to your manager, written so they could forward it to their boss without changing a single word. That last part is the whole design. In MAC-139 we talked about why your manager usually isn't positioned to advocate for you the way a sponsor would. That's still true. But your manager is something else that matters enormously: the channel. Most of what a senior leader knows about you travels through your manager's upward reporting, and your manager is writing that reporting at nine o'clock at night, trying to compress eight people's work into something their boss will actually read. Picture two people on that team. One sends a list of activities. The other sends four tight lines already written for the next level up. Which one gets quoted? Structurally, the person whose update is ready to forward is the person whose work travels. So here's the test, and it's the only one that matters: could your manager forward this note, unedited, to the person above them? If they'd need to rewrite it, it won't travel, and if it doesn't travel, then above your manager it effectively didn't happen. The update has four parts. What moved. Not what you did, but what changed because you did it. "Met with finance four times" is activity. "Finance and operations are now working from the same forecast, so the March number no longer needs a footnote" is an outcome. Same four meetings, completely different sentence. The coaches I mentioned frame each item the same way: what changed, why it matters, and what comes next. If a line doesn't answer the first of those, it isn't ready. What I learned. One or two sentences. This is where your judgment becomes visible, and judgment is what senior leaders are really assessing when they think about who's ready for more. What's at risk. The thing you can see coming that they can't yet. Nothing builds trust faster than being the person who flagged it early. What I need. A decision, a resource, an introduction. Specific and small. Four parts, under two hundred words. If you've been keeping the running record from The Brag Document (MAC-141) , you already have the raw material; this is the month's version of it, shaped for an audience. Twenty minutes a month, less once it's a habit. Notice what this is not. In Reporting Status (MAC-044) we covered the weekly status that keeps your manager informed, and that's still worth doing. But the weekly status is written for your manager. The Forwardable Update is written through them. A status report tells your manager you were busy. A Forwardable Update tells their boss what changed. Borrow the Room The update gets your work into rooms you'll never be in. Now let's get you into a few of those rooms yourself, without adding a single new project to your plate. Most of your best work happens in rooms senior leaders never enter: the working session where the problem actually got solved, the whiteboard, the spreadsheet at eleven at night. By the time that work reaches a senior audience, someone else is usually presenting it. But the rooms where senior leaders are already exist: the quarterly business review, the monthly operating review, the all-hands, the steering committee for the initiative you're three layers deep in. Nobody needs to invent a forum for you. The question is simply which recurring rooms senior leaders sit in where your work is already on the agenda , presented by someone else. Picture an analyst who builds the same recurring report every month. Her director presents it at the monthly operations review, reads the numbers aloud, and moves on. One month she asks a small question: Could I take five minutes at the next review to walk through what the numbers are actually telling us? Same report, same meeting, new narrator. Within a quarter, the VP running that review is asking for "her read" before the meeting starts. She didn't take on a project. She borrowed a room her work was already in. That's the first move: ask to present one slice of existing work. Not the whole initiative, just

September 29, 202619 min

Analysis Paralysis Is Just Fear Wearing a Lab Coat - MAC160

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...

September 22, 202621 min

Are Your Emotions Holding You Back - MAC159

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....

September 15, 202618 min

Not Every Failure Counts Against You - MAC158

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...

September 8, 202615 min

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

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...

September 1, 202616 min

Measuring Invisible Work - MAC156

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,...