You know you should stop thinking about work but work doesn’t end when you close the laptop, it just changes location. It moves into the shower, the commute, the moment right before sleep.

Most people believe they just need more discipline - turn work thoughts off, compartmentalize better. But many also know it doesn’t work, no matter how strong the willpower.

Why your brain won’t let go

In 2011, researchers Masicampo and Baumeister ran a study on something called the Zeigarnik effect - the tendency for unfinished tasks to intrude on our thoughts far more than finished ones. They wanted to know what actually makes the intrusion stop.

The obvious answer is complete the task and your mind lets it go.

But they found more - finishing the task worked but so did something much smaller, writing a specific plan for when and how the task would get done. Participants who made a concrete plan showed the same drop in intrusive thoughts as participants who actually completed the task.

The brain doesn’t need to work to be completely done but it demands a plan. An open loop with a plan reads as handled, even though nothing has actually happened yet. That’s why the unfinished email lingers at the back of your mind but the meeting you’ve already scheduled to deal with it doesn’t. Same task, same amount of undone work, but completely different mental weight.

Close the loop

The best option is always to finish the thing. Send the email, have the conversation. Nothing beats actual completion for getting it out of your head.

But most days, you can’t finish everything, so the next best move is to close the loop some other way.

Write the plan down. Not the incomplete task at a high level but something specific like scheduling a meeting with a stakeholder to clarify assumptions as the first concrete step.

Journal it. If a conversation is replaying in your head, write out what happened and what you’d want to say or do next. The point isn’t to solve it on the page but to give your brain proof that the loop has a next step. Write down the difficult conversation you plan to have with your colleague and see what happens to your thoughts after. You might not even need to talk to that colleague after.

Say it out loud. Tell a colleague or your partner what’s unresolved and what you’re going to do about it. Speaking the plan externalizes it the same way writing does. And that’s why therapy also helps.

None of this requires the problem to be resolved. It just requires your brain to stop treating it like an emergency with no plan attached. The conversation that keeps replaying, the task sitting half-done - your mind isn’t asking you to fix it tonight.

It’s asking you to tell it what happens next.

Sources:

Consider it done! Plan making can eliminate the cognitive effects of unfulfilled goals

Ghost jobs are postings for roles a company has no real intention of filling right now. Some are placeholders for a “talent pipeline.” Some are already filled internally and nobody took the listing down. Some exist purely to make a company look like it’s growing. Either way, you’re applying to a black hole.

The numbers are worse than they feel

Estimates on how common this is vary, but they all land in the same uncomfortable range. Clarify Capital’s 2025 survey of 1,000 employers found nearly one in three admitted to posting jobs with no real intent to hire. Other analyses of active listings put the share of ghost jobs between 20% and 35%, depending on sector. Wholesale and senior-level roles run higher than average.

It’s not just the postings. It’s the silence afterward. Fortune reported in March 2026 that 53% of job seekers said they’d been ghosted by an employer in the past year, a three-year high, up from 48% in 2025 and 38% in 2024. That climb tracks with the rise of one-click apply tools and AI screening, which let companies collect resumes at scale without the staffing to respond to any of them.

The law is starting to catch up

Ontario moved first. Under the province’s Working for Workers Seven Act, effective January 1, 2026, employers with 25 or more staff must disclose whether a public job posting is for a current vacancy, state if AI is used in screening, and notify any interviewed candidate of the outcome within 45 days, win or lose. Fines run up to $100,000 CAD per violation.

New York followed. Bill S8877 cleared both the Senate and Assembly in June 2026 and is now with Governor Hochul for signature. It would require employers with 100 or more employees, and third-party job boards, to state whether a posting is an active vacancy and give an expected hiring timeframe.

California’s version, AB 1251, passed the Assembly in a 62-9 vote but has been sitting in the Senate Appropriations Committee since last August. New Jersey, Pennsylvania, and Kentucky all have similar bills moving through their own legislatures. None of this helps you today. But it tells you the problem is big enough that lawmakers in four states and one Canadian province decided it needed a statute.

What to check before you apply

You don’t need a law to protect your own time. A few checks will do most of the work:

• Compare the aggregator to the company’s own careers page. If a role has been live on LinkedIn or Indeed for weeks but doesn’t appear on the employer’s site, that’s a signal. Aggregators pull listings automatically and rarely verify them.

• Look at posting age. Anything sitting active past 30 days without edits is worth a second look. Real urgency doesn’t usually last a month.

• Check for a salary range. Pay transparency laws are spreading. A listing that dodges compensation entirely, especially where disclosure is required, is often not a serious one.

• Watch for vague or duplicated postings. Identical listings reposted every few weeks, or ones with no named hiring manager or team, are common patterns behind evergreen “pipeline” roles.

• Connect with someone from the company. “Ask if the company have a referral bonus and if they are willing to refer you for the role”.

None of this guarantees a real job on the other end. But it will save you from spending nine hours on a posting that was never going anywhere.

Further reading

• Clarify Capital, Ghost Jobs Study (2025)

• Fortune, “Job seekers aren’t imagining things” (March 2026)

• CNBC, Lawmakers want to end HR ghosting during the interview process (Aug 2025)

• Bloomberg Law, New York Targets Use of “Ghost Job” Ads in Bill Headed to Hochul (June 2026)

• Staffing Industry Analysts, Lawmakers target “ghost jobs” in next hiring fight

• Fisher Phillips, California Lawmakers Want to Ban “Ghost” Job Postings

Strip away the branding and most of these documents are saying five things.

Obsess over the user. Amazon calls it Customer Obsession. Stripe calls it Users First. Anthropic calls it Be Good to Our Users. Apple never named it, but “best user experience” has been the whole company for a decade. Different words, same instruction: start with the person on the other end, not the org chart.

Move with urgency. Amazon: Bias for Action. Meta: Move Fast. Stripe: Move with Urgency and Focus. OpenAI, in its leanest current form: Intense and scrappy. Every one of these companies is telling employees the same thing: don’t wait for permission, don’t wait for consensus, don’t wait until next week.

Hold a high bar. Insist on the Highest Standards. Be Meticulous in Your Craft. Great and Always Better. Apple’s whole design culture runs on this without ever printing it on a wall.

Own the outcome. Amazon’s Ownership. Netflix’s “use good judgment” as its literal core precept. Apple’s DRI model, where one person is directly responsible for every feature and has to defend it in review. Different mechanisms, same bet: trust people to decide rather than build process to control them.

Stay humble, keep learning. Learn and Be Curious. Intellectual humility. Act with humility. Curious. This is the one value that shows up almost word-for-word across every list, which tells you something about what actually breaks teams at scale. Not laziness. Certainty.

That’s the shared spine. Five behaviors, worded eight different ways, because “be humble” doesn’t sound proprietary enough to put in an S-1.

What’s not shared is more interesting than what is.

Amazon turns its principles into a literal interview rubric. Each interviewer gets assigned two or three, grades you against them, and a Bar Raiser can veto the hire regardless of how the rest of the loop felt. Netflix built a “keeper test” and describes itself as a pro sports team, not a family, on purpose. Google scores “Googleyness” as a fourth hiring signal alongside raw cognitive ability. None of these are decorations. They’re enforcement mechanisms.

Then there’s the one nobody copies: Anthropic is the only company on this list whose stated values include the option to slow itself down. Its Responsible Scaling Policy can pause a launch for safety reasons, which means “move fast” isn’t even in its top six. Every other company on this list treats speed as close to sacred. Anthropic wrote a values document with an explicit off-switch.

OpenAI’s list, meanwhile, has changed more than once in the last few years. It went from six values (Audacious, Thoughtful, Unpretentious, Impact-driven, Collaborative, Growth-oriented) to a leaner set built around AGI focus, with a line on the careers page that reads almost like a warning: anything that doesn’t help with that is out of scope.

And Apple just didn’t write one down. No single “Apple Values” document exists. Instead you get secrecy treated as a craft, need-to-know compartmentalization built into how teams talk to each other, and a design obsession that functions like a value system without ever being formalized as one.

Here’s the pattern underneath the pattern. A values document isn’t a description of the company. It’s a description of the failure mode the company is most afraid of. Amazon is afraid of slow decisions, so it built 16 checks against slowness. Netflix is afraid of mediocrity tolerated out of politeness, so it built a test to remove people. Anthropic is afraid of moving too fast toward something dangerous, so its values include a brake. Apple is afraid of leaks, so its culture is quiet by design.

If you’re building your own version of this for a company, team, or even just yourself, that’s the actual exercise. Not “what do we value.” Everyone values the same five things. The real question is: what’s the one failure you’re most scared of, and does your list actually defend against it?

Appendix: full lists and sources

Amazon - 16 Leadership Principles
Customer Obsession, Ownership, Invent and Simplify, Are Right, A Lot, Learn and Be Curious, Hire and Develop the Best, Insist on the Highest Standards, Think Big, Bias for Action, Frugality, Earn Trust, Dive Deep, Have Backbone; Disagree and Commit, Deliver Results, Strive to be Earth’s Best Employer, Success and Scale Bring Broad Responsibility
Source: amazon.jobs/en/principles

Anthropic - Core Values
Act for the Global Good, Hold Light and Shade, Be Good to Our Users, Ignite a Race to the Top on Safety, Do the Simple Thing That Works, Be Helpful and Honest.
Source: anthropic.com/careers

Apple - no single published document
Working culture principles compiled from public reporting: DRI (Directly Responsible Individual) ownership model, need-to-know secrecy, design and craft perfectionism, privacy as a design constraint. Separately, Apple’s official investor-facing values: accessibility, education, environment, inclusion and diversity, privacy, racial equity and justice, supplier responsibility.
Source: builtin.com/company/apple/faq/culture-values

Google - Googleyness
Intellectual humility, comfort with ambiguity, conscientiousness/bias to action, collaboration, user focus, enjoying fun, courageous/interesting life paths. Grouped into six interview areas: thriving in ambiguity, valuing feedback, challenging the status quo, putting the user first, doing the right thing, caring about the team.
Source: resumeadapter.com/companies/google/googleyness

Meta - Core Values
Move Fast, Focus on Long-Term Impact, Build Awesome Things, Live in the Future, Be Direct and Respect Your Colleagues, Meta, Metamates, Me.
Source: resumeadapter.com/companies/meta/values

Netflix - Culture Memo
Four principles: The Dream Team, People over Process, Uncomfortably Exciting, Great and Always Better. Eight Dream Team behaviors: Judgment, Communication, Curiosity, Innovation, Courage, Passion, Candor, Selflessness (Netflix’s own materials list eight or nine depending on version).
Source: jobs.netflix.com/culture

OpenAI - Charter and current careers values
Charter (2018): broadly distributed benefits, long-term safety, technical leadership, cooperative orientation. Careers page (2026): AGI focus, Act with humility, Feel the AGI, Ship joy, Intense and scrappy.
Source: openai.com/charter and openai.com/careers

Stripe - Operating Principles
Users First, Move with Urgency and Focus, Be Meticulous in Your Craft, Seek Feedback, Curious, Macro-optimistic.
Source: stripe.com/jobs/culture

People don’t follow advice because it’s rational. They follow it because they trust the person giving it. A mediocre plan from someone you trust beats a brilliant plan from someone you don’t. This is true at work and it’s true at home.

How trust gets built

Minimize the gap between what you say and what you do. That’s the whole game. Every promise you keep narrows the gap. Every promise you break widens it. People aren’t tracking your intentions. They’re tracking your track record.

Say “I don’t know” out loud. A hiring manager I know used to tell his team: uncertainty isn’t the problem, hiding it is. If you’re not sure, say so, and give a caveat. “I think X, but I haven’t checked Y” builds more trust than a confident answer that turns out wrong. People forgive uncertainty. They don’t forgive being misled.

Never lie, even small. Small lies feel harmless because they’re small. But trust isn’t measured by the size of the lie. It’s measured by whether one was told at all.

Have you ever caught a whiff that someone was lying, even a little, and said nothing? You probably didn’t call it out. Most people don’t. But your brain quietly logged it. It adjusted that person’s trust score down a notch, without your permission and without a conversation. You just started weighing their next claim a little more carefully.

Other people are running the same silent calculation on you. Every small lie, even the ones nobody confronts you on, still gets scored. That’s what makes lying so costly. The damage happens whether or not anyone says a word.

Show up the same way twice. Consistency is underrated because it’s boring. But a person who behaves the same way in a crisis as they do on a normal Tuesday is a person others can plan around. That predictability is trust.

At work

Your team trusts you based on whether your calendar matches your words. If you say a project is the priority and then miss its standups, the team notices before you do. If you tell a report they’re doing well and then pass them over for the promotion without explanation, that gap becomes the story people tell about you.

Trust at work is built in unglamorous moments: giving credit accurately, delivering hard feedback directly instead of through gossip, and admitting when a call you made was wrong.

At home

Same mechanics, higher stakes. Kids don’t trust parents because parents are always right. They trust parents who are consistent, who follow through on small promises, and who admit mistakes instead of covering for them.

Why trust is asymmetric

Trust takes years to build and seconds to lose. Worse, it’s not lost proportionally to the actual risk.

AI agents are, by the numbers, often more consistent than the humans doing the same task. But let an AI agent make one bad call, send one wrong email, book one wrong meeting, and it gets remembered longer than a thousand identical mistakes made by people. One error and the whole category gets labeled unreliable. We hold new or unfamiliar trust to a stricter standard than the trust we’ve already extended out of habit.

This means one visible break can undo years of consistency, especially with people who were still deciding whether to trust you in the first place. The people who trust you most will give you room to recover. The people who don’t yet will use the first crack as proof they were right not to.

That’s not a reason to be paralyzed. It’s a reason to be deliberate. Say less than you’re sure of. Do more than you promised. Let the track record speak.

This worksheet helps you separate the two. Work through it before you make a move. It takes about ten minutes.

Download the free worksheet here.

What the worksheet covers

What’s actually broken. Name the real problem. Is it the role, the manager, the company, or the system around you? You can’t fix what you can’t name.

What you’d lose and what you’d gain. Map the tradeoffs of leaving versus staying, without the emotion clouding it.

The fixes you haven’t tried yet. Most people quit before using the leverage they already have. This section finds it.

Your walk-away number and terms. Decide your real conditions before you’re in a heated moment.

The 30-day test. One concrete experiment to run before you decide anything.

How to use it

Print it or fill it in on screen. Be honest. The worksheet only works if you tell it the truth.

Two questions, and I read every reply: What’s your biggest career challenge right now? What made you subscribe?

Hit reply and tell me. It shapes what I write next.

You’ve probably also watched someone less capable get promoted ahead of you. Not because their work was better. Because they spoke up more in meetings, or maybe they’re just more charismatic.

Doing good work isn’t the mistake. Sometimes it’s just not enough.

Find a sponsor

The most effective sponsor you can find is usually your manager. They sit in the room where staffing and promotion decisions actually happen, and they can make the case for you when you’re not there. Give them two things to work with - a record of what you’ve shipped, and clarity on where you’re headed.

Keep a brag doc. Add a line every 1:1: “Here’s what I shipped and why it mattered.” That’s not bragging, it’s documentation aimed at a human instead of a compiler, and it means neither of you is reconstructing your last two quarters from memory at review time.

Share your career aspirations every 1-2 months. Ask your manager directly what concrete things you can learn and act on to get to the next level by the next promotion cycle. Most people never ask, then wonder why the path never appears.

Treat any friction here like a bad requirement, a misalignment to clear up, not a fight to win. Ask for the same clarity your manager should already be setting on what great actually looks like.

In some organizations, your manager isn’t positioned to sponsor you. If that’s the case, look outside the reporting line. Check whether your company runs a formal mentorship program and find a mentor there instead. The goal doesn’t change: someone senior enough to speak for you in rooms you’re not in.

Show up in team meetings

Sponsorship covers your manager. The rest gets built in the room with everyone else, in team meetings and cross-functional syncs. Three things matter there.

1. Guide instead of correcting. If someone’s take is wrong, the goal isn’t to be right in front of the room, it’s to get the group to a better answer. Ask the question that surfaces the gap and let them find it, or lay out your read and invite pushback: “Tell me if I’m missing context” or “here’s my read, tell me where I’m wrong.” Either turns a correction into a conversation instead of a verdict.

2. Do the research first when you can. Quiet contributors do their best work with time to think, so take it when it’s available. Read the doc, form a view, before you’re in the room. When you don’t have that runway, think out loud instead of staying silent: say what you know, flag that it’s based on limited context so far, and name what you still need to find out and where. That reads as engaged. Silence reads as absent.

3. Give before you get. Collaborate on other people’s work, not just your own. Give credit loudly and specifically when someone helps you. Take the unglamorous task the team needs done. This is how you build the credibility and reputation that makes people comfortable vouching for you when you’re not in the room. Sometimes you give for months before anything comes back. That’s not a bad trade, just not an instant one.

This will make your manager’s job to advocate for you easier. The unspoken reality is, most people prefer someone easier to work with, not simply the smartest.

Figure out what your company actually rewards

Not every company rewards the same behavior. Not every manager inside the same company does either. Some reward visible ownership, some technical depth, some whoever the loudest voice in the room trusts.

Stop guessing. Ask people who got promoted recently what actually moved the needle. Ask your manager directly what they look for when they advocate for someone. You’re not asking for a shortcut, you’re asking for the rules of the game you’re already playing.

It’s fine to just do the quiet work

You don’t have to do any of this. If visibility work feels exhausting and the promotion isn’t worth the discomfort, that’s a legitimate choice, not a failure of ambition. Plenty of people build good, stable careers doing excellent quiet work at a steady level. That’s a real tradeoff, not a consolation prize.

What Quiet actually argues

Susan Cain’s Quiet gets read as permission to stay hidden. That’s a misread. Her real claim: introverts contribute differently, not less, and organizations that only recognize the loudest people waste most of their talent.

If you manage people, build the habit of asking quiet contributors directly what they’re working on instead of waiting for them to perform it. The healthiest teams reward delivered value, not volume, and that’s a leadership choice as much as an individual one.

But it cuts both ways. The world won’t notice on its own. Cain’s point isn’t that patience gets rewarded. It’s that quiet excellence is real, and worth a small, deliberate effort to make sure someone with influence actually sees it.

The usual failure mode is picking the wrong kind of story. A program that ran smoothly has no risk to talk about. A program that was chaotic has no evidence you controlled anything. The interviewer wants a program where real things could have gone wrong, and didn’t, because of decisions you made on purpose.

What they’re actually testing

Four things, roughly in order of weight:

• Did you own the program end-to-end, not just your slice of it.

• Did you name the risks before they hit, not after.

• Did you keep exec, product, and eng aligned as things moved.

• Did you close with a number that proves impact.

A great technical story with no stakeholder thread reads as narrow. A great alignment story with no metric reads as fluff. You need both.

The structure: STAR, weighted toward Action

Situation and Task should take a few sentences combined: scope, stakeholders, environment, your specific role. Don’t linger. The interviewer is listening for Action, the part where you show how you spotted risk and moved on it, and Result, the part where you prove it mattered. Aim for two to three minutes spoken.

Picking your example

Before you draft anything, list every program you’ve run that had real scope - multiple teams, a hard deadline, a dependency you didn’t control. For each one, write down the top two or three risks it carried. Use a simple taxonomy so you don’t miss one: technical debt, resource constraints, vendor dependencies, compliance. Then map what you actually did about each risk, in order - assess, communicate, mitigate. Finally, attach the number.

Prep one story per level you might actually interview at. A staff engineer and a senior manager get asked the same question and should not give the same answer.

Three examples

L5, Senior SWE. I led the migration of our monolith to microservices across three regions, and the risk that kept me up at night was doing it without downtime. We put circuit breakers in front of every new service boundary, ran dark launches so real traffic hit the new code path before we cut over, and ran disaster recovery drills until the on-call team could fail over in their sleep. We hit zero downtime, held error rates under 0.5%, improved latency by 30%, and avoided roughly $200K in projected incident cost.

L6, Staff Engineer or Manager. I owned a global customer analytics platform spanning five business units on a ten-month timeline. The risks weren’t just technical. Schema versioning could break five teams at once if we got it wrong, GDPR meant every field needed a masking strategy before it shipped, and one vendor’s SLA didn’t match our uptime target until we renegotiated it. We hit 99.95% uptime, ingested 2TB a day, cut pipeline incidents by 60%, and the cleaner data lifted marketing effectiveness by 15%.

L7, Principal or Senior Manager. I ran a multi-year ERP-to-cloud transformation with over 150 engineers and a $20M budget. At that scale the biggest risk is losing the room, so I stood up an executive steering committee and ran the program against a COSO risk framework from day one. We built active/active failover and a DevSecOps pipeline so security wasn’t a phase, it was the default. Wave one landed 8% under budget, cut downtime by 75%, and cut executive escalations in half.

Notice the shape repeats: a real risk with teeth, a specific action taken before the risk landed, and a number. The scale changes. The shape doesn’t.

Before you walk in

Write your version of this in the same shape, out loud, timed. Match the level of the story to the level of the room you’re walking into. Practice until you can deliver the Action and Result without checking notes.

Ready to ace your next tech interview? Subscribe to Kaizen Coach for more in-depth guides or book a one-on-one strategy session today!

Here’s how to write the second one.

1. Own the verb, not the proximity. Responsible for, helped with, and worked closely with describe nearness to a result, not ownership of it. A recruiter scanning for impact skips past these on sight. Use the verb for what you actually did: built, cut, closed, shipped, negotiated.

2. Structure every bullet as Problem, Action, Result. Not a sentence, a compressed slide. “Checkout drop-off was costing 8% of monthly signups. Redesigned the flow from 5 steps to 2. Drop-off fell to 3% within one quarter.” Three clauses, one number, and the reader knows exactly what you’re capable of repeating for them.

3. Lead the effort, don’t just join it. Most candidates for a given role have similar peer resumes: same tools, same functions, similar bullet phrasing. What separates one page from the stack is evidence of ownership. If you drove the initiative, say so directly. “Led the migration” and “contributed to the migration” describe two very different hires, even if the work looked the same day to day.

4. Let the resume show growth, not just a list of jobs. A hiring manager reading top to bottom is checking for a trajectory: did scope, budget, or team size expand from one role to the next, or does every bullet read the same regardless of seniority? A resume that shows a widening circle of responsibility argues for promotion. A flat one argues for staying put.

5. Give context for any company the reader won’t recognize. If your employer isn’t a household name, don’t make the recruiter guess at scale or stakes. Anchor it: “aligned cross-functional teams across a Fortune 500 manufacturer” or “took the product from 0 to 1, first paying customer in month four.” One clause of context does the work that brand recognition would otherwise do for free.

6. Cap it at three bullets per role. Recruiters and hiring managers work through volume, often dozens of resumes a day. Guy Kawasaki’s 10/20/30 rule for pitch decks (10 slides, 20 minutes, 30-point font) holds for the same reason: constraint forces you to keep only what earns its place. If your resume is already longer than a page, a fourth bullet rarely adds proof. It mostly adds scanning time the reader doesn’t have.

7. Name your working style, because not every manager is looking for the same thing. Some hiring managers want someone careful and thoughtful, who de-risks decisions before committing. Others want someone who biases for action, ships fast, and iterates in public. Both are legitimate operating modes, but they read as opposite strengths. Don’t add a section to spell this out. Signal it in the two places that already carry weight: the summary line and the verbs inside your bullets. Bias for action shows up as “Launched MVP in 3 weeks, iterated through 4 releases based on user feedback.” Careful and thoughtful shows up as “Ran a 6-week pilot across 2 markets before full rollout, catching a pricing flaw that would have cost $200K.” Same underlying skill set, opposite framing, and each one pulls the right manager toward you instead of making them guess.

8. Replace your summary with a one-line pitch that also carries your working style. “Passionate product leader who loves solving problems” is unfalsifiable and says nothing about how you operate. “Product leader who ships fast and iterates based on live user data, taking three B2B tools from zero to $1M ARR” is a specific, checkable claim that also tells the reader what kind of hire they’re getting, the kind they can ask you to defend in the first five minutes of a call.

Pick one bullet on your current resume and run it through steps 1 and 2 right now. If it doesn’t survive as a Problem, Action, Result with a number attached, it wasn’t ready to be read in 6 seconds.

Push hard for what you believe, then once the decision is made, commit fully even if you disagree. It sounds mature. In practice it quietly answers a much harder question while pretending not to.

Who pays when the decision turns out wrong?

Should we let people make mistakes?

There’s a real argument for letting people fail. Mistakes teach faster than warnings do. A person who pushes a bad architecture into production and watches it buckle under load learns something a code review comment never delivers. If you intervene every time you smell a bad decision, you raise people who can’t smell anything themselves.

But that argument only holds when the cost of the mistake lands on the person who made it. Most of the time it doesn’t.

The senior engineer who says “I told you so” six months later isn’t the one who stayed until midnight migrating off the system that got rushed to production. The product manager who insisted on the feature isn’t the one fielding support tickets two quarters later. The mistake teaches a lesson, just rarely to the person who needed to learn it.

So the question isn’t really “should people be allowed to fail.” It’s “who is the textbook in this story, and who is the lab subject.”

Having backbone

This is where backbone earns its name. Speaking up before the decision, clearly and on the record, is the only leverage you have to stop being the lab subject in someone else’s lesson. Not because you’re certain you’re right. Most disagreements aren’t about certainty, they’re about risk you can see and the other person can’t.

If you’re not 100% sure, say so anyway. Certainty was never the bar. The bar is, did you say enough that, when it goes wrong, the failure mode was visible in advance.

What happens after

Decisions get made. Some of them are bad. Then someone has to clean up.

Cleanup is never evenly distributed. It falls on whoever is closest to the system, which is usually the person who raised the concern in the first place, now doing unpaid penance for someone else’s confidence.

This is the part the leadership principle conveniently skips. “Disagree and commit” describes the meeting. It says nothing about the three months after, spent paying down debt that someone else borrowed against your time.

Dealing with stubborn, uninformed people

The hardest version of this isn’t disagreeing with a sharp person who happens to be wrong. That’s normal work. It’s disagreeing with someone who is both confident and uninformed, and who outranks the argument by sheer force of will.

It is psychologically draining in a specific way. You’re not just losing an argument. You’re pre-living the cleanup before it happens, doing the math on hours you haven’t lost yet.

You can let them make the mistake. That part is easy, you just stop pushing. The actual question is narrower and uglier: will you be the one who works the extra hours to fix it? Will you be the one who carries the technical debt nobody else remembers borrowing?

If the answer is yes, “letting them learn” isn’t a development strategy. It’s you volunteering to be collateral.

What I see at work

Here’s the part that should bother people more than it does. Stubborn people get ahead. Not the people who are right, the people who refuse to budge regardless of whether they’re right.

Confidence reads as competence to anyone who isn’t close enough to check the work. A person who never says “I’m not sure” looks more promotable than a person who flags risk honestly, even when the second person’s track record is better. Organizations reward the appearance of conviction because it’s legible. They rarely audit whether the conviction was earned.

So the stubborn survive and the careful absorb the cost of their mistakes quietly, which teaches the organization exactly the wrong lesson: stubbornness works.

What to do instead

Don’t confuse “disagree and commit” with “go silent and absorb.” The principle works when disagreement is genuinely heard and the commitment is a real choice, not a forced one.

A few things that actually help:

• Put your disagreement in writing before the decision, not after. Memory is a terrible witness, and an email is not.

• Ask for the specific failure condition. “What would have to be true for this to go wrong?” forces the stubborn person to engage with the mechanism, not just the outcome.

• Refuse to be the default owner of someone else’s bad call. If you didn’t make the decision, say clearly who is accountable for the outcome before you start fixing it.

• Pick your battles by blast radius, not by how annoying it is to be ignored. Save backbone for decisions that are expensive to reverse.

• If the pattern repeats, that’s not a decision problem anymore. That’s a person or a structure problem, and no amount of better disagreeing fixes it.

Disagree and commit is a fine principle for a single decision made in good faith by people who will actually update when they’re wrong. It is a terrible substitute for a culture that lets the same people make the same expensive mistakes, on someone else’s time, again and again.

It’s not laziness. It’s not weakness. It’s your system telling you the math stopped working.

What’s Actually Happening

Burnout is three things collapsing simultaneously: energy, engagement, and belief in your own effectiveness.

The World Health Organization classifies it as a syndrome from chronic workplace stress that was never dealt with. The clinical definition captures the mechanics, but not the feeling. The feeling is that you used to care, and now you don’t, and you don’t have the energy to care about not caring.

Research points to six root causes:

1. Overwork - sustained output without recovery

2. Lack of control - doing work you can’t influence or redirect

3. Insufficient reward - effort that doesn’t register as valuable

4. Weak community - no one to absorb the friction with you

5. Unfairness - effort not matching recognition

6. Values conflict - your work asks you to be someone you’re not

None of these require a toxic job. They can accumulate inside a good job over time, invisibly.

Why It Gets Worse As You Age

This is the part most people don’t talk about.

Early career, you’re running on novelty and ambition. The dopamine from learning new things covers a lot of structural problems. You’re still building, still proving, still discovering what you’re capable of. The fuel is intrinsic.

By midlife, that fuel shifts. You’ve hit the milestones. You’ve earned the title, the income, the reputation. And instead of satisfaction, many people find a strange flatness.

The achievements don’t land the way you expected.

At the same time, the load has compounded. More responsibility. Less tolerance for inefficiency. Probably a family, aging parents, or both. The “sandwich generation” is real: about 47% of adults in their 40s and 50s are simultaneously raising children and caring for aging parents. That’s two full emotional jobs running alongside the work one.

The other factor is identity. Younger workers burn out from overload. Older workers often burn out from misalignment. After 15 or 20 years, your values have evolved. What mattered at 28 doesn’t necessarily matter at 42. But the career you built reflects the old values, and dismantling it feels like admitting something.

The result: you stay in a role that no longer fits, and the friction accumulates until there’s nothing left to give.

What Comes Next

The worst move after burnout is trying to productivity-hack your way out of it. More systems, better morning routines, aggressive recovery plans. These treat the symptom, not the cause.

Real recovery has a sequence.

Name it without negotiating with it.

Most high-performers resist the label. They call it stress, a rough quarter, a bad month. Recognition isn’t weakness. It’s the precondition for changing anything. Your prefrontal cortex, the part of the brain that actually solves problems, can’t engage while you’re in denial.

Create separation from the stressor.

Not forever. Not necessarily at all. But enough to interrupt the loop. Time off, a reduced load, a hard stop at a specific hour. Your nervous system cannot reset while it’s still receiving the same inputs. This is physiological, not philosophical.

Audit the cause, not the symptoms.

Most people treat burnout like a sleep deficit and try to rest their way out. Rest helps, but if you return to the same misalignment, you’ll be back in six months. The real question is: which of the six causes was at work here? Overload? Misalignment? No agency? The answer shapes what needs to change.

Rebuild identity separate from output.

Burnout is often tied to the belief that your worth is a function of your productivity. The recovery requires breaking that equation. Not permanently abandoning ambition. But finding proof that you exist and matter outside of what you produce. For builders and operators, this is often the hardest step.

Redesign the conditions, not just the habits.

Boundaries, recovery rituals, exercise, sleep. All valid. All insufficient on their own. The deeper work is structural: renegotiating what you take on, who you work with, and whether the role still reflects what you actually want from the next decade.

You used to hold five things in your head at once. Now you write everything down or you lose it. That’s not burnout. That’s a measurable change in your brain’s hardware.

Psychologists split intelligence into two types. Fluid intelligence is your ability to reason through new problems, hold information in mind, and adapt on the fly. Crystallized intelligence is everything you’ve banked: vocabulary, expertise, pattern recognition built over years.

Fluid intelligence peaks in your late 20s and declines slowly from there. Working memory, one of its core components, often starts slipping as early as your 30s and 40s. Crystallized intelligence does the opposite. It keeps climbing into your 50s and beyond, because experience compounds.

This is why you feel sharper in judgment but slower in raw processing. You’re not getting dumber. You’re trading horsepower for range.

The catch: most 40-something burnout isn’t really about workload. It’s the gap between what your fluid intelligence can hold and what modern life demands of it: kids’ schedules, work decisions, group chats, fifteen open tabs. Cognitive overload, not task count, drains people. Chronic stress raises cortisol, and elevated cortisol degrades working memory further. Stress shrinks your fluid capacity, the shrinking capacity makes everything feel harder, and that creates more stress.

What actually helps:

• Sleep first. Sleep deprivation measurably impairs working memory and spikes cortisol. Highest-leverage lever you have.

• Lower baseline stress. Chronic cortisol elevation is the mechanism behind a lot of the “brain fog” people report in their 40s.

• Hydrate. Mild dehydration alone measurably dings cognitive performance.

• Train working memory directly. Dual n-back has real evidence behind it, especially with consistent daily sessions over several weeks. Not magic, but one of the few interventions with documented transfer effects.

• Externalize aggressively. Don’t trust your working memory to hold things it wasn’t built to hold anymore. Notes, lists, calendars. Offload ruthlessly. The fluid system is for processing, not storage.

• Teach what you learn. Explaining something forces you to reorganize it, which converts fresh, fragile fluid-intelligence material into durable crystallized knowledge. People retain dramatically more of what they teach than what they merely read.

None of this reverses the curve. Fluid intelligence declines no matter what you do. But you can slow it, protect what’s left, and lean harder into the system that’s actually getting stronger: the crystallized one. That’s the real 40s unlock. Stop trying to out-process younger versions of yourself. Start out-pattern-matching them.

This post was inspired by ‘s note on “Life happens in transitions”, but reminded of my skillset as I get older…

I’ve sat on both sides of that table, as an engineer and later building and running product teams.

Here’s the sequence I’d follow.

1. Figure out the manager’s real intent first. Two very different things produce a bad review: a manager who wants you to succeed and is frustrated you haven’t, and a manager who’s already decided you’re leaving and is building the paper trail to make it stick. Don’t assume it’s the first one just because that’s the more comfortable read.

Some tells of a managed exit: the feedback is vague and trait-based (”not strategic enough”) rather than tied to specific decisions. The timeline for improvement is short and unrealistic. The manager won’t commit to clear, measurable criteria for success. You’re suddenly being CC’d to HR or skip-level on routine things. None of these prove it on their own, but a cluster of them is a pattern, not bad luck.

2. Ask for concrete, actionable items, not adjectives. Whatever the intent, push for specifics: “What exactly would ‘meeting expectations’ look like by next quarter? Give me two or three concrete things.” A manager who genuinely wants you to succeed will usually engage with this. A manager who’s already decided will deflect, stay vague, or hand you a list that quietly keeps moving. That response is itself useful data, going back to point one.

3. Decide if it’s a fixable problem or a fit problem. If it’s fixable, fix it. If it’s not, figure out where the mismatch actually lives. Is it this manager, this team, or this company? That distinction matters because your options shrink fast once you’re formally on a PIP. Plenty of companies won’t let you transfer teams once you’re flagged, even if the problem was clearly about your specific manager and not your work. If a lateral move is on the table, it’s usually only available before the PIP starts, not after.

4. Check whether this is a visibility problem or an alignment problem. These look identical from the outside but need opposite responses. A visibility problem means the work is good but invisible: nobody above your manager knows what you actually did. An alignment problem means the work itself doesn’t match what the team or company needs right now, regardless of how visible it is.

If it’s visibility, the fix is making your work legible: documenting impact, presenting in the right rooms, and yes, seeing if a peer or skip-level will vouch for you with specifics. A peer saying “actually, I saw them solve X” carries more weight than anything you say about yourself. If it’s alignment, no amount of visibility fixes it. You need a different role, team, or company where the work that comes naturally to you is the work that’s valued.

5. Skip the “document everything and challenge your manager through HR” advice. This gets repeated everywhere, and I think it’s mostly wrong. HR exists to manage company risk, not to act as your advocate. They report up through the same leadership your manager answers to. If your manager has been asked to hit an unregretted attrition number, which happens more often than companies admit, HR isn’t a neutral referee. They’re often the mechanism executing that plan.

Building a detailed paper trail to dispute a review can occasionally help if you’re aiming for a severance negotiation or you have a genuinely strong legal claim. As a strategy to keep your job or change your manager’s mind, it rarely works and it burns time you could spend on your next move. Decide which game you’re actually playing before you invest in documentation.

A bad review is one of the few moments someone is forced to tell you, in some form, where they think you stand. Spend your energy figuring out what’s really happening, not on convincing them they’re wrong.

Your brain can hold about 4-7 things at once. That’s it. Every unfinished task, every deferred decision, every open loop competes for that space.

Engineers call this a stack overflow. HBS researchers now call it brain fry.

AI agents made it worse. You’re now managing your own work plus a dozen parallel threads you’ve delegated: a Claude writing a draft, a Cursor fixing a bug, an agent researching a market. Each one needs a context switch to check in. Each switch costs stack space. The productivity gain is real, but so is the overhead of orchestrating it.

Most people respond by trying to hold more. Better apps, more tabs, tighter schedules. But the problem isn’t your system. It’s the volume.

Every possession you own, every commitment you haven’t resolved, every agent thread you’re half-tracking is running in the background. The more you pile on, the less you can do with any of it.

A few things actually help:

Write things down before you delegate. Externalizing a task clears it from your stack. If you’re spinning up an AI agent, write the brief, then let it go. Don’t half-hold it.

Batch your check-ins. Treat agent outputs like email. Check them at set times, not continuously. Constant monitoring is just a new form of multitasking.

Limit active threads. Three parallel workstreams is about the limit before you’re spending more energy tracking than doing. More agents doesn’t mean more output.

Resolve open loops daily. Anything you’re “meaning to get back to” is occupying space. Decide, delegate, or delete it before it becomes background noise.

The stack is limited. AI gives you more horsepower, but the cockpit is still the same size. The people who benefit most aren’t the ones running the most agents. They’re the ones who stay clear on what they’re actually trying to get done.

We build the same way. Validate everything. Reject anything that doesn’t match the schema. Force users into rigid flows so the data stays clean. It works, until reality shows up.

Reality is messy. Customers fat-finger their email. Names have unicode characters your regex didn’t anticipate. A user clicks back mid-flow and your state machine has no idea what to do. A system that can’t tolerate any of this isn’t robust. It’s brittle wearing a robust costume.

Good systems absorb noise. They have a default path when the expected path breaks. They log the weird case and keep moving instead of throwing a 500. The best support teams I’ve worked with weren’t the ones who never saw edge cases. They were the ones who had a playbook for “I don’t know what just happened, but here’s what we do.”

This is part of why AI is eating rule based systems for breakfast. A rule based parser sees “jhon@gmial.com” and either rejects it or silently fails. An LLM sees it and goes “that’s probably john@gmail.com” and moves on.

The rules system is technically correct and practically useless. The model is technically uncertain and practically right.

The counter case

Tolerance has a cost, and it’s not always worth paying.

If you’re moving money, you don’t want a system that guesses what the user “probably meant.” A typo in a wire transfer amount or account number is not a nuance to smooth over, it’s a reason to stop and ask. The same goes for anything with legal, medical, or safety consequences. There, rigidity isn’t a flaw, it’s the point.

There’s also a quieter cost: tolerant systems can train people to be sloppy. If your form auto-corrects every bad input, nobody learns to fill it out right, and the errors just move downstream to where they’re harder to catch.

The real skill isn’t picking error tolerant over rigid. It’s knowing which parts of your system are pipes and which are valves. Pipes should flex. Valves should hold the line. Most failures I’ve seen come from treating a valve like a pipe, or a pipe like a valve.

That reframe is the whole game. When you ask permission, you are asking another person to put their name on an outcome they can’t control and don’t fully understand. Of course they hesitate. Of course they ask for more data, another meeting, a smaller scope. They aren’t being slow. They are being rational. The default answer to “can I?” is “let me think about it,” and “let me think about it” is where good ideas go to get old.

So builders learn a different move. Do the thing. Show the result. Apologize if it broke something. This works more often than the cautious would like to admit, and it fails in ways that can end a career. The skill isn’t picking a side. It’s knowing which situation you’re in.

When forgiveness wins

The bias toward action pays off when three things are true at once:

1. The downside is reversible. You can roll it back, delete it, undo it, or quietly fix it before it matters. A feature flag, a draft, a test in a sandbox. If the worst case is “we revert the commit,” go.

2. The cost of asking exceeds the cost of being wrong. Some approvals take two weeks and three stakeholders to bless a change you could ship and measure in an afternoon. The meeting is more expensive than the mistake.

3. You’d be told no for the wrong reasons. Not because the idea is bad, but because no one wants to own the yes. This is the real reason “ask forgiveness” exists. It routes around people who are optimizing for their own safety, not the project’s success.

When those hold, asking permission is just volunteering for delay. You already know the answer is yes on the merits. You’re only missing a signature.

When it backfires

The same move that makes you look decisive can make you look reckless. Forgiveness is the wrong play when:

• The blast radius is bigger than you. Anything touching money, customer data, security, legal exposure, or another team’s roadmap. If your mistake lands on someone else’s desk, you don’t get to skip their input.

• It can’t be undone. Sending the email to the whole company. Deleting the production table. Telling the customer something you can’t walk back. Irreversibility removes the entire premise. There is no forgiveness, only consequence.

• Trust is the thing you’re spending. The first time you act without asking and it works, you’re bold. The fifth time, especially if one of them went sideways, you’re the person who can’t be trusted in the room. You spend trust faster than you think, and it doesn’t refill on the same schedule.

The pattern people miss: the move scales badly. It’s a tool for the occasional high-conviction call, not an operating system. Use it on everything and you’ve just told your team that process is optional, which is a great way to find out how much process was actually load-bearing.

How to tell the difference

I run a fast version of this before acting:

• Can I undo this in under a day? If no, ask.

• If I’m wrong, who pays? If it’s not me, ask.

• Am I skipping permission because it’s slow, or because I suspect the answer is no? If it’s the second one, that “no” is information. Don’t route around it. Go find out why.

That last one is the trap. “Easier to ask forgiveness” quietly becomes “easier to avoid hearing no.” Those are different.

The first is a judgment about process being too slow for a decision you’re confident in. The second is you overriding a constraint you haven’t bothered to understand. One is leadership. The other is how you blow up a project and call it initiative.

The honest version of this principle isn’t “don’t ask.” It’s “ask when the answer matters, act when the asking is the only thing in the way.” Most of the speed people admire in good operators comes from telling those two apart in about four seconds.

The cautious ask permission for everything and ship nothing. The reckless ask forgiveness for everything and eventually run out of it. The job is to spend your forgiveness deliberately, on the calls where being right and being fast are worth more than being safe.

Watch a team protect a lead by keeping the ball. They pass sideways, backward, anywhere but forward. The clock runs. No risk, no shot, no chance of a mistake. It looks like soccer. It is mostly clock management.

A lot of office work is the same move. The meeting that schedules the next meeting. The doc that summarizes the other docs. The review that asks for another review. The ball never goes near the goal.

Motion without direction.

People do this because solving a problem requires a position. A position can be wrong. Once you commit to a fix, you own the outcome, and the outcome might fail in front of everyone. Keeping the ball avoids all of that. You cannot lose possession if you never drive at the net.

And it works, partly. You stay busy. You stay employed. Your calendar is full, your updates are long, and nobody can say you did nothing.

But possession is not a score. The match ends 0-0, and 0-0 does not get you promoted.

Promotion is the reward for scoring. For taking the shot, owning the result, and being right often enough that people hand you bigger shots. The person who passed the ball around for two years did not lose. They also did not move. There is no column in the table for keeping the ball nicely.

The safe game has a hidden cost. Every season you play for the draw is a season someone else spent learning to score. They missed sometimes. They also got better at it, and the misses are forgotten while the goals are remembered.

So check the direction of the ball. If your work never points at the goal, you are not avoiding a loss. You are choosing a slow one.

The founder is running on deferred reward. They took a pay cut, bet their reputation, and internalized the company’s survival as their own. Slow weeks feel dangerous. Speed isn’t a preference; it’s the whole thesis.

The employee made a different calculation. Maybe they left a stable job for equity and an interesting problem. But they didn’t sign up for the founder’s anxiety. They have a life. Friday evening is theirs.

Neither is wrong. But the gap is real.

The founder treats lack of urgency as underperformance. The employee reads the founder’s intensity as poor management. Both are partially right.

The fix isn’t squeezing more out of employees or asking founders to calm down. It’s three things:

1. Be explicit about the deal upfront. This is a high-urgency environment. Here’s what that looks like. Here’s what you get in return.

2. Separate urgency from hours. A startup needs fast decisions and tight feedback loops, not 60-hour weeks. Define what “moving fast” actually means in practice.

3. Make the mission visceral. Employees move faster when they feel the stakes, not just hear about them. Share the numbers. Share the pressure. Treat them like owners.

Most startups skip all three. They pay for it in resentment, bad hires, and quiet departures.

The hunger gap doesn’t close on its own. Name it early, and build around it.

Most candidates treat “do you have any questions?” as a formality. That’s a mistake.

Your questions reveal how you think. They show whether you’re evaluating the company as seriously as they’re evaluating you. Come with real questions, not softballs.

On Culture

“How does the team handle disagreement with a decision from above?”

You’ll learn more from how they pause before answering than what they actually say.

“Can you give me an example of a recent cross-functional project that went badly, and what changed because of it?”

Every company claims to learn from failure. This question finds out whether that’s true.

On the Role

“What would a strong first 90 days look like?”

Vague answers are a red flag. A good manager knows exactly what early success looks like.

“What’s the most common reason someone in this role struggles?”

More useful than asking what the job entails. You get the real picture.

“How does career growth actually work here, outside of the official ladder?”

Because the official ladder is often not how it works.

On the Company’s Direction

“What’s the biggest thing the company is trying to figure out right now?”

This surfaces whether leadership has honest answers or just talking points.

“What made you stay?”

Ask the interviewer directly. Their answer tells you more about the company than any pitch will.

The goal isn’t to impress. It’s to walk out knowing whether this place is worth your time

The difference between these experiences offers a powerful metaphor for how we approach work.

Beyond the Buffet Mentality

In the workplace, the "buffet mentality" translates to the belief that working longer hours automatically equals better performance. It's the corporate equivalent of piling your plate high—more meetings, more emails, more late nights. But just as a buffet prioritizes quantity over culinary excellence, this approach often sacrifices quality for the illusion of productivity.

Fine dining, on the other hand, is about curation. Each element serves a purpose. The portions are deliberate, the timing is precise, and the overall experience leaves you satisfied rather than uncomfortably full. When we apply this philosophy to work, we shift from asking "How many hours can I put in?" to "What value am I creating in the time I have?"

The Art of Professional Curation

A skilled chef doesn't throw every ingredient into a dish. Similarly, effective professionals don't say yes to every request or work themselves into exhaustion. They understand that sustainable excellence requires boundaries—not the rigid walls that some workplace communities advocate for, but thoughtful limits that protect both quality and well-being.

This isn't about becoming calculative or transactional. When you're constantly measuring your effort against potential rewards, you create a dynamic where both you and your manager are playing a zero-sum game. Your manager, being human, will have biases. They may not be able to protect you from broader economic forces. And if they sense you're holding back or keeping score, you might find yourself first in line when difficult decisions need to be made.

The Compound Effect of Excellence

But here's the paradox: when you focus on delivering exceptional value—when you approach your work like a master chef approaches a tasting menu—you often create something more powerful than individual job security. You build teams that deliver results customers actually want. You contribute to organizations that thrive rather than just survive.

Companies with teams focused on genuine value creation rarely need to make the kinds of cuts that keep employees awake at night. When your collective work creates real impact, layoffs become a last resort rather than a regular business cycle event.

Finding Your Recipe

The goal isn't to work yourself to exhaustion or to do the bare minimum. It's to find that sweet spot where you can take pride in your contribution while maintaining the energy and perspective needed for sustained performance. Like a perfectly balanced dish, great work requires both passion and restraint, both creativity and discipline.

The next time you're tempted to pile on another commitment or stay late just for the sake of being busy, ask yourself: Am I creating a buffet plate or a carefully crafted experience? The difference might just determine not only the quality of your work, but the sustainability of your career.

What does your work "tasting menu" look like? What would you remove, and what would you perfect?

The difference isn’t the event. It’s what follows.

Excuse: “The customer didn’t reply, so I couldn’t finish.” Reason: “The customer didn’t reply. I sent reminders and drafted a fallback plan.”

Same situation. Completely different signal.

Excuses stop at why it failed. Reasons add what you did and what changes next time.

One test cuts through it: does this explanation help prevent the same problem next time? Yes = reason. No = excuse.

Leaders don’t judge by incident. They judge by pattern. One missed deadline is noise. A consistent stream of closed-door explanations becomes a reputation.

Everyone hits blockers. People who earn trust stay in the problem even after they’ve named it.

Ownership plus next step. That’s the line.