Some management books age badly. You open them 30 years later and find advice that sounds like it was written for a factory overseen by a man smoking next to a forklift.

Philip Crosby’s Quality Is Free, first published in the late 1970s, is strange because half of it feels completely outdated — and the other half feels uncomfortably modern.

The title itself sounds almost absurd today. “Quality is free.” Right. Tell that to a product team drowning in technical debt, a newsroom fixing broken embeds at midnight, or an engineering manager negotiating cloud costs after another emergency rollback.

But Crosby’s point was never that quality costs nothing. His point was that the absence of quality is catastrophically expensive.

That idea has survived surprisingly well.

For years, I have had a slightly provocative theory about work: lazy people often produce higher-quality work on the first attempt.

Not always. There is obviously the destructive kind of laziness too. But experienced, intelligent laziness is different. It hates repetition. It hates fixing the same thing twice. It hates unnecessary motion, unnecessary meetings, unnecessary debugging, unnecessary explanations, unnecessary support tickets.

So these people quietly optimize for permanence.

They write the cleaner process because they do not want to answer the same question fifteen times. They automate the workflow because manual repetition irritates them. They document things because they do not want late-night calls. They think through architecture because they do not want emergency rewrites six months later.

Meanwhile, organizations often reward the opposite behavior: visible urgency, heroic recovery, chaotic multitasking, dramatic late-night fixes, endless firefighting. Entire careers are sometimes built on solving problems that should never have existed in the first place.

Crosby would probably appreciate the irony.

Back in the 1970s, he was mostly talking about manufacturing defects, production lines, warranties, scrap, inspections, and rework. The world was industrial, hierarchical, and obsessed with process control. The enemy was the defective physical product.

Half a century later, the factories became platforms, APIs, apps, recommendation engines, analytics pipelines, AI systems, and distributed cloud infrastructure. But the defects never disappeared. They just changed shape.

Today’s “scrap” is not metal in a warehouse. It is engineering time lost to regressions. It is product managers holding alignment meetings about problems that should never have existed. It is support teams manually correcting workflows. It is editors working around broken CMS logic. It is developers fixing rushed integrations at 2 a.m. because “we’ll clean it up later” somehow became an operating model.

And just like in Crosby’s time, organizations still underestimate the cost of all this invisible chaos.

One of Crosby’s most controversial ideas was “Zero Defects.” Modern people instinctively dislike the phrase because it sounds unrealistic, authoritarian, or detached from reality. In software, especially, people love saying that “bugs are inevitable,” which is true. But Crosby was not really arguing for perfection. He was arguing against normalization.

That distinction matters.

Many organizations quietly build cultures where recurring problems become folklore rather than priorities. Everyone knows the broken workflow. Everyone knows the unreliable report. Everyone knows the feature that randomly fails under load. Entire teams adapt to dysfunction, like people in an old apartment building learning which stair steps creak.

Eventually the workaround becomes more stable than the actual system.

Crosby would probably hate modern startup culture. Not because of technology, but because of the mythology of speed. “Move fast and break things” sounds exciting until you realize someone has to maintain the broken things. Usually, with half the original team gone and the documentation written by archaeologists.

At the same time, some things have changed dramatically since the late 1970s.

Back then, quality management was deeply centralized. Committees, formal programs, structured initiatives, quality departments, slogans on walls. Today, quality is far more embedded in operational systems. CI/CD pipelines, observability, automated testing, SRE practices, feature flags, incident management, telemetry, DevOps culture — much of modern engineering is essentially automated quality management wearing a hoodie instead of a necktie.

Even Crosby’s famous idea that “quality must start at the top” has evolved. Modern organizations increasingly understand that quality is systemic. Leadership still matters enormously, but quality now emerges from incentives, architecture, tooling, communication patterns, deployment practices, staffing realities, and organizational trust.

Ironically, AI is making Crosby’s arguments even more relevant today.

AI dramatically lowers the cost of producing things quickly. But it also lowers the cost of producing bad things quickly. Hallucinated summaries, unreliable automations, synthetic content errors, broken AI workflows, low-quality code generation — the scale of potential rework is becoming enormous.

The old industrial defect is becoming a probabilistic defect.

Which brings us back to Crosby’s original argument from the late 1970s: prevention is cheaper than correction.

Still true.

Not because humans became smarter. Not because technology solved complexity. But because organizations still pay for every shortcut, eventually. The invoice simply arrives later, in a different department, under a different budget line, in a different quarter, explained by a different PowerPoint presentation.

Half a century later, that part aged perfectly.

There is a French expression: esprit de l’escalier — the wit of the staircase.

It captures that deeply annoying moment when you finally think of the perfect response after the conversation is already over. After the meeting ended. After the argument moved on. After you already nodded politely, left the room, entered the elevator, and replayed the entire discussion in your head, like Lt. Columbo quietly returning to the room with “just one more thing.”

Only then does the right answer arrive.

Modern management culture quietly treats this as a weakness. We admire people who respond instantly, speak confidently, dominate discussions, and always appear intellectually armed. The ideal leader in many organizations is someone who can offer immediate opinions on strategy, budgets, hiring, restructuring, AI, cybersecurity, market shifts, and organizational politics. Preferably within the same thirty-minute meeting and without showing visible signs of human cognition.

But after years in product leadership, I increasingly suspect we misunderstand what is actually happening in those moments.

The person with the fastest answer is not necessarily the one doing the best thinking. Very often, they are simply the person most comfortable performing certainty in public.

Organizations inadvertently train people to optimize for reaction speed rather than judgment quality. Meetings become strange little performance arenas where timing matters more than depth. Whoever speaks first often controls the framing of the problem. Whoever sounds most confident creates gravity around their interpretation. Because corporate environments reward momentum, the room starts moving before anyone fully understands whether the direction even makes sense.

Then comes the staircase moment.

You leave the room, and your brain finally exits survival mode. The pressure lifts. You are no longer trying to sound diplomatic, protect relationships, avoid escalation, respect hierarchy, defend your department, manage optics, and simultaneously interpret three contradictory stakeholder expectations disguised as “alignment.” The nervous system calms, and suddenly the real thought appears.

Not the clever comeback. Not the movie-style one-liner everyone imagines afterward. The real insight.

“The roadmap itself is internally contradictory.”

“We are discussing delivery problems because nobody wants to discuss prioritization failures.”

“This initiative was approved because challenging it politically costs more than implementing it poorly.”

“The KPI exists mainly to comfort management, not to measure customer value.”

By then, of course, the meeting is already over. Someone has already summarized the discussion in Teams. Someone else has written “great progress, everyone.” The slide deck has become organizational reality simply because enough people stopped resisting it for forty-five minutes.

Large organizations are full of decisions made just minutes before the smartest idea entered the room.

Ironically, this becomes even more apparent at senior levels. The more political the environment, the less cognitive bandwidth people have for pure thinking. A significant portion of executive communication is emotional risk management disguised as strategic discussion. People constantly calculate consequences: Who supports whom? Which conflict is safe? Which truth is dangerous? Which topic will cause unnecessary escalation? Which sentence may resurface six months later during budgeting season?

No wonder the best insights often arrive later, when the meeting is finally over and the brain can process the conversation without social threat detection running at full capacity.

That is also why some executives suddenly seem remarkably intelligent in follow-up emails sent at 11:43 PM. The staircase finally gave them processing power.

Over time, it became clear that healthier organizations intentionally build mechanisms for delayed thinking. They understand that complex environments rarely yield their best decisions instantly. They allow people to revisit assumptions, clarify concerns, or challenge conclusions after reflection, rather than treating every meeting like a live television debate where hesitation equals incompetence.

Weak organizations interpret this as indecisiveness. Strong organizations recognize it as cognitive maturity.

This matters even more now because AI is making fast answers unbelievably cheap. We are entering a period when immediate responses, summaries, opinions, presentations, and strategic language can be generated almost infinitely. This means the value of leadership shifts elsewhere. The scarce skill is no longer producing quick reactions. The scarce skill is knowing which reactions deserve skepticism, which conclusions were reached too quickly, and which decisions require uncomfortable additional thinking before the organization commits itself to a confident mistake at scale.

Maybe esprit de l’escalier is not really a personal flaw after all.

Maybe it is a warning sign that modern organizations increasingly mistake intellectual theater for actual thought.

And maybe the most dangerous person in the room is not the one who speaks first, but the one whose mind keeps working after everyone else believes the meeting is already over.

There is a famous psychological phenomenon known as King Solomon’s paradox. It captures something both amusing and deeply uncomfortable: people are often remarkably good at giving wise advice to others while being completely unable to apply the same logic to their own lives.

Which, if we are honest, also explains a very large part of modern product management.

Take almost any experienced product leader and place them in another company for half a day. Within minutes, they will identify the core problems with almost surgical precision. They will notice the overloaded roadmap, chaotic prioritization, unclear ownership, endless operational interruptions, a reactive culture disguised as agility, and the complete absence of strategic focus, hidden under layers of dashboards and planning rituals. They will calmly explain that the organization keeps confusing movement with progress. Everyone around the table will nod thoughtfully because the diagnosis sounds intelligent, mature, and painfully accurate. A few hours later, the workshop ends successfully. Someone posts a photo of sticky notes on LinkedIn, and the consultant leaves looking very wise.

Then that same person returns to their own organization and spends the next three months trapped in meetings where seventeen parallel priorities somehow all remain “critical,” even though basic math strongly suggests otherwise.

This is the fascinating part. Most organizational dysfunction is not actually hidden. Mature organizations are often perfectly capable of describing their own problems in extraordinary detail. Everyone already knows that technical debt is growing, priorities shift every week, analytics are incomplete, ownership is unclear, and stakeholders bypass processes whenever pressure mounts. Entire companies openly admit they have too many meetings, too many projects, and too little focus. Yet somehow the organization continues operating in exactly the same way, quarter after quarter, almost like a person repeatedly reading books about healthy sleep at two o’clock in the morning while answering Slack messages.

And this is where Solomon’s paradox becomes highly relevant to product leadership and organizational strategy. Companies are not purely rational systems. They are social systems filled with emotions, politics, insecurities, historical tensions, survival instincts, and power structures — all carefully masked by strategic presentations and modern corporate vocabulary. Outside the organization, product people think analytically. Inside the organization, they think relationally. These are very different modes of thinking, even if we prefer to pretend otherwise.

A product manager advising another company can confidently say that stronger prioritization discipline is needed. That sounds simple, reasonable, and professionally correct. But within their own company, saying “no” to the wrong stakeholder may quietly erode trust, political capital, budget access, visibility, or future career opportunities for years. Suddenly, the obvious strategic decision no longer feels so obvious. The problem is no longer theoretical. It becomes personal.

This is also why consultants often appear smarter than internal leaders. It is not necessarily because they possess deeper wisdom. Distance creates clarity. External advisors are not trapped in the system’s emotional gravity. They do not carry years of unresolved tensions, organizational trauma, reporting-line conflicts, budget fights, executive sensitivities, or memories of failed initiatives that still haunt meeting rooms long after everyone pretends to have moved on. Consultants see systems. Internal leaders experience consequences. These are completely different psychological conditions.

The same paradox becomes visible whenever organizations talk about innovation. Almost every company claims to value experimentation. Innovation sounds exciting in presentations because it conjures an image of a modern, adaptive, forward-looking organization. But the moment experimentation threatens existing ownership structures, established expertise, or comfortable routines, the organization’s enthusiasm shifts dramatically. Suddenly, the “small experiment” requires alignment meetings, business justifications, risk assessments, ROI projections, communication plans, stakeholder reviews, and governance approvals. At some point, the experiment becomes so operationally burdensome that the original purpose quietly disappears beneath the process designed to protect the organization from uncertainty.

AI is making this contradiction even more visible. Nearly every company now says it needs an AI strategy, which often means adding AI-generated summaries to meetings, placing “AI-powered” somewhere on the website, or demonstrating cheerful prototypes during executive presentations. But far fewer organizations are seriously asking the dangerous question beneath all this enthusiasm: what happens if AI actually works? If it truly works, many long-standing organizational assumptions become unstable very quickly. Information flows differently. Expertise is distributed differently. Decision-making speed changes. Entire coordination layers may become unnecessary. Some forms of management become less valuable, while others become critically important.

And organizations instinctively resist changes that redistribute influence or reduce control, even when those changes are strategically logical. So instead of operational transformation, many companies drift toward ceremonial transformation. They adopt the language of change while preserving the structure of the old system almost untouched. Which, honestly, may be one of the most corporate behaviors humanity has ever invented.

The uncomfortable truth behind Solomon’s paradox is that many organizations are not optimized to identify the best decision. They are optimized to maintain stability, preserve relationships, reduce political risk, and avoid internal conflict. The safest roadmap often wins over the smartest. The least controversial initiative often wins over the most strategically important one. Organizations publicly celebrate focus while privately rewarding responsiveness. They praise innovation while quietly punishing visible failure. They speak passionately about long-term strategy and then schedule thirty-minute meetings to discuss transformational change between two operational escalations.

And product managers sit right in the middle of all this, trying to act like rational system designers in environments that are often driven by human psychology, institutional inertia, and low-grade organizational anxiety.

Perhaps this is why experienced product leaders become less ideological over time. Junior PMs often believe every problem has a single correct answer waiting to be uncovered through frameworks and analysis. Senior leaders eventually realize that many organizational decisions cannot be solved mathematically. They are negotiated compromises among incentives, personalities, fears, timing, politics, operational pressure, and the simple reality that companies are made of humans, not diagrams.

That realization does not necessarily make people cynical.

But it usually makes them noticeably quieter when someone confidently says, “We just need better prioritization.”

This episode is a companion to my LinkedIn article.

This podcast is generated using an AI version of my voice from a script written and edited by me.

For years, managers across the technology industry lived with the same permanent anxiety: “We simply do not have enough resources.”

Not enough developers. Not enough designers. Not enough analysts. Not enough time. Not enough budget. Most product managers built their careers negotiating this triangle of constraint, usually with a new spreadsheet template every year.

Then AI arrived and quietly introduced a different question: What if resource constraints were never really the main issue?

Inside organizations, something odd is happening. Teams are producing more output than ever. Prototypes appear overnight. Marketing copy is generated in seconds. Research summaries arrive instantly. Roadmaps are assembled at a pace that would have seemed impossible a year ago. Everyone feels faster, more modern, more efficient, more ‘AI-enabled.’

And yet, many companies still somehow feel strategically stuck.

The uncomfortable part is that AI is making execution dramatically easier, but it is also exposing how weak prioritization was all along.

For decades, most organizations relied on a familiar tool: the four-quadrant prioritization matrix. Quick Wins in one corner: high value, low effort. Big Bets in another: expensive, potentially transformative. Fillers: small, low-impact tasks that keep people busy but rarely move the needle. And then the most dangerous quadrant: Time Wasters: initiatives that consume resources with little to show for it.

Traditionally, this model was mostly about tasks.

But AI changes something fundamental: the matrix is no longer only about tasks. It is now also about human behavior.

Because AI shifts the cost of execution so aggressively that entire categories of work begin moving between quadrants.

Quick Wins get even quicker. And more tempting. A UX tweak that once took weeks of coordination, design, copy, translation, and testing now happens almost instantly. Teams rack up small victories. Metrics nudge upward. Dashboards look healthier. Slack fills with launch announcements. Leadership sees movement and feels reassured.

But there is a subtle trap hidden inside this acceleration.

Organizations can become addicted to visible momentum instead of meaningful progress.

The company starts optimizing dozens of tiny things simply because they are now cheap to optimize. Everyone feels productive as the machine keeps generating visible output. Meanwhile, the harder strategic questions sit quietly in the background, like gym equipment people keep meaning to use.

Big Bets move in the opposite direction. AI lowers the barrier to entry for strategic thinking. Now, every team can generate polished concepts, vision decks, market analyses, technical architectures, customer personas, and future-state scenarios in hours. What once took weeks and real expertise now appears after a single workshop and a few prompts.

This creates a familiar illusion: organizations start confusing the ability to describe strategy with the ability to execute it.

And these are very different skills.

AI is good at helping people imagine futures. It is much less useful for navigating organizational politics, aligning stakeholders, rewriting processes, migrating legacy systems, changing company culture, or surviving budget reviews with finance teams who still expect innovation to be free.

So companies enter a period of strategic inflation. More Big Bets. More transformation initiatives. More AI-first roadmaps. More platform reinventions. More innovative language. More rockets on slides.

Not necessarily more outcomes.

Then there is the evolution of filler work. Historically, these were harmless activities: easy, safe, politically neutral. Small updates. Minor documentation changes. Cosmetic improvements. Tasks that created the feeling of progress without changing much.

AI has turned this category into something almost surreal.

Now organizations can generate filler work at industrial scale.

Summaries of meetings become summaries of summaries. Brainstorms produce AI-generated follow-up brainstorms. Documents generate more documents. Teams create entire ecosystems of polished output with no clear connection to business impact. Somewhere in the system, there is probably already an AI writing weekly reports that are read only by another AI generating executive summaries.

And somehow this does not even sound unrealistic anymore.

But the most dangerous transformation happens in the Time Wasters quadrant.

Historically, bad ideas at least faced natural friction. Terrible projects moved slowly because execution was expensive. Organizations had built-in protection: limited staff, limited time, limited coordination, human exhaustion, technical bottlenecks. Bad initiatives often collapsed under their own weight before they could do real damage.

AI quietly removes many of those friction points.

Now, companies can move in the wrong direction faster, longer, and with more confidence than before.

This is the truly uncomfortable part of the AI conversation that receives far less attention than prompts, copilots, and productivity gains.

AI does not improve judgment. It just amplifies it.

Good prioritization gets more powerful. Bad prioritization gets more expensive.

This leads to a familiar paradox: the teams that look most productive are not always the ones creating the most value. Some teams are becoming very efficient at producing motion without progress. Dashboards look fantastic. Velocity increases. Output explodes. Internal excitement grows.

Meanwhile, the company may be driving straight into a wall at full speed, with beautifully formatted AI-generated documentation explaining why the wall is a growth opportunity.

This is why the real bottleneck in the AI era is not execution capacity. It is the quality of prioritization.

The most valuable people are not the ones producing the most content, writing the most tickets, generating the most slides, or shipping the most visible activity. AI is handling more of that output every day.

The valuable people are the ones who can still calmly ask uncomfortable questions. Why are we doing this? What problem does it actually solve? Does this initiative deserve to exist at all?

And perhaps most importantly: Are we mistaking acceleration for direction?

Ironically, these are not futuristic skills. They are old-fashioned ones: judgment, taste, restraint, strategic clarity. The ability to say no before execution begins, not after resources disappear.

Unfortunately, these skills are much harder to showcase in a LinkedIn post than with screenshots of AI dashboards and words like “transformation”.

But beneath all the excitement, the reality is becoming surprisingly simple: AI boosts execution while humans still choose direction.

And choosing direction was always the hardest part.

There is a familiar contradiction in how we talk about politeness. We grow up hearing that nothing costs so little and is valued so much as politeness. It sounds elegant, civilized, almost universally true. Then people enter actual organizations and discover a different operating system running beneath the official story.

“If you are too polite, people will see you as weak.”

Many professionals do not just believe this as a theory; they have lived it. They have seen polite managers ignored while louder colleagues take over meetings with more confidence than competence. They have watched respectful people get overloaded simply because they are easier to pressure. In meetings, the calmest person is often treated as the least authoritative, while the most reactive is somehow promoted as a strong leader. For all its innovations, corporate life still struggles to distinguish between confidence and aggression.

Politeness does not have a fixed meaning. In stable organizations, it signals professionalism and respect for people’s time. In more political or insecure environments, the same politeness is read as negotiability. A calm manager saying, “Please try to deliver this by Friday,” may be understood by one team as respectful leadership and by another as evidence that deadlines are optional and reality itself remains open for discussion. The sentence does not change. The culture does.

This is how cynicism about politeness takes root. After enough exposure to aggressive systems, people stop trusting that politeness offers any protection. Worse, they start to confuse weak boundaries with politeness itself. These are not the same. The issue is rarely that someone is calm or respectful. The issue is that they cannot hold the line when pressure comes. Being polite is not the same as being unable to say no. One is a skill. The other is surrender dressed up as teamwork.

The strongest leaders I have seen are often quietly polite. Not the scripted politeness of training videos, but a genuine calm and respect. They do not raise their voices or manufacture urgency. They do not dominate meetings just to be seen. Yet they move organizations. They can reject ideas, block projects, and redirect strategy without turning every conversation into a contest. Real authority is quieter than most people expect. The people with the most power are usually the least interested in proving it.

People remain highly sensitive to dominance signals, even in organizations that claim to value collaboration above all else. Underneath the language of agile, psychological safety, and alignment, status displays still drive reactions. Interrupting, speaking with certainty, creating pressure, responding slowly, escalating conflicts. These behaviors still trigger associations with power. The result is one of the ongoing absurdities of modern work: the person with the least emotional control is often seen, at least for a while, as the strongest in the room.

Once you notice this pattern, you’ll see it everywhere. The executive who sends midnight emails is called passionate. The manager who lives in crisis mode is labeled high-performance. The stakeholder who escalates every disagreement is seen as strategic. Meanwhile, the calm person who pauses before speaking risks being seen as lacking urgency or ambition. Especially in places where stress has become a status symbol.

There is a cultural layer here that rarely gets discussed. Some societies link politeness to education and status. Others see toughness as a survival skill. In competitive or unstable environments, people learn early that visible softness attracts pressure. The polite child is interrupted. The polite employee gets extra work. The polite manager is bypassed by louder voices. Over time, people build protective identities around sharpness and controlled aggression. Not because they enjoy it, but because emotional hardness feels safer.

This is how defensive abrasiveness takes hold. After enough time in chaotic systems, people become colder, shorter, more impatient, and a bit hostile just to avoid being seen as weak. You can see this especially in tech, where communication sometimes starts to sound like tired airport security announcements on Slack. Somewhere along the way, professionalism got confused with emotional frostbite.

The irony is that genuinely confident people have little need to perform power. The insecure manager dominates meetings because silence feels risky. The secure manager can sit quietly and still shape the outcome. That is a different kind of authority, and usually a more durable one.

This may be the real lesson behind the contradiction. Politeness without boundaries invites exploitation. Aggression without competence destroys trust. Calm firmness — the ability to stay respectful while holding the line — remains one of the most underestimated forms of authority in professional life.

It is also much harder than just sounding intimidating on Slack.

Most software companies reach a point where everything starts to feel reactive. Tickets accumulate, users get louder, teams get busier. Dashboards show activity. Everyone is busy, but the system is not improving.

And yet, somehow, nothing feels under control.

This is when it becomes clear: what you have is not a support function. It is an Emergency Room. Not as a metaphor, but as an operating model.

Once you recognize the pattern, it is difficult to ignore.

Intake and triage: where everything already starts going wrong

In an actual Emergency Room, nobody treats patients in the order they walked in. A broken finger does not go ahead of a heart attack. That sounds obvious. Until you look at many Customer Care queues.

Tickets come in through forms, email, chat, Slack, and sometimes a phone call from someone senior. Without real triage, everything merges into one stream. The loudest or most recent issue gets attention, or the one with the most senior escalation.

A mature support team behaves more like medical triage than inbox management. It classifies issues by severity, impact, and urgency within minutes. It routes them intentionally. It accepts that some cases will wait. And that this is not negligence, but prioritization.

Most teams do not have a capacity problem. They have a triage problem.

Decisions under uncertainty: guessing, but professionally

In Emergency Rooms, doctors rarely have perfect information. They work with symptoms, fragments, probabilities. They make a call, act, and adjust.

Customer Care operates in the same fog. “The CMS is slow.” Which part? For whom? Since when? No one knows yet. But the clock is already ticking.

Good support agents develop clinical instincts. Pattern recognition. A sense of “this smells like a caching issue” or “this is probably a permissions edge case.” They don’t wait for perfect clarity. They move the case forward while gathering evidence.

Bad systems, on the other hand, demand complete information upfront. They stall. They bounce tickets back to users: “Please provide more details.” Meanwhile, the incident grows quietly in the background.

Hesitation is costly in both settings. In software, we often act as if it is not.

Resource constraints: you don’t have enough, you never will

Emergency Rooms are always constrained — beds, staff, equipment. When a surge hits, something has to give.

Customer Care teams face the same constraints. Agent capacity is limited. Engineering attention is even more limited. When the CMS fails during a peak publishing window, every ticket becomes urgent.

This is when the system shows its actual design. Are there clear incident modes? Can you reassign resources? Do you ignore non-critical requests, or try to handle everything and end up failing across the board?

Most organizations say they have priorities. Few enforce them when it matters.

Escalation pathways: where time is usually lost

In an Emergency Room, escalation is not a failure. It’s the system working as intended. A generalist stabilizes, a specialist intervenes, the case moves forward.

In Customer Care, escalation often becomes a bureaucratic process. Tickets move with missing context. Engineers repeat the same questions. Product teams join too late or too early. Many people are involved, but ownership is unclear.

The difference between a functional and dysfunctional system is not escalation itself, but how it operates. Good escalation brings structure, ownership, and clear expectations. Bad escalation brings frustration.

And frustration, unlike tickets, does not close.

Time sensitivity: SLAs are just a polite version of urgency

In medicine, urgency is obvious. In software, we hide it behind SLAs. “Response within 4 hours.” “Resolution within 24 hours.”

But when your CMS goes down during a major news event, nobody is thinking in SLA language. That is not a “P1 ticket.” That is an emergency.

The issue is not the existence of SLAs. The issue is treating them as a replacement for judgment. Teams optimize for compliance, not for impact. They respond within the window, but do not always solve the problem.

In an Emergency Room, stabilizing the patient matters more than updating the chart. The same principle applies more often than we admit.

Emotional load: you’re not just solving problems

Emergency Room staff deal with fear, panic, and occasionally anger. The technical problem is only part of the job. The emotional state of the patient is the rest.

Customer Care agents live in a softer version of the same reality. Users are frustrated. Editors are blocked. Stakeholders are anxious. And the tone of communication can escalate faster than the issue itself.

Here is the nuance many teams miss: communication is not a wrapper around the solution. It is part of the solution.

A well-timed message can prevent escalation. A poorly handled one can turn a minor issue into a major conflict. The system can be fixed, but the user can still be lost.

Feedback loops: treating symptoms vs fixing the disease

Every Emergency Room generates data. Patterns emerge. Certain injuries spike at certain times. Certain conditions repeat. This informs prevention, staffing, public health.

Customer Care should do the same. Recurring tickets are not “business as usual.” They are signals. Poor UX, fragile features, unclear workflows. They all surface through support long before they appear in product metrics.

Many organizations treat support as an endpoint. Tickets arrive and are resolved, but there is no structured feedback into product. No prioritization based on support data. The same issues quietly return each week.

At that stage, the work is not solving problems. It is managing their recurrence.

From emergency response to preventive care

Here is where the analogy becomes uncomfortable.

A hospital that invests only in its Emergency Room is not a good hospital. It is an overwhelmed one. Real healthcare systems invest heavily in prevention: primary care, early diagnosis, reducing the need for emergencies in the first place.

The same is true for software.

A Customer Care team that is always busy is not a sign of success. It is often a sign that the product is generating problems faster than they can be addressed. Onboarding is unclear, workflows are fragile, and edge cases are now common cases.

Preventive care in a CMS environment looks less dramatic, but more valuable. It is better defaults. Clearer interfaces. Fewer clicks to publish. Smarter error messages. More resilient infrastructure. Thoughtful constraints that prevent users from getting into broken states.

It also means taking support data seriously. Not as anecdotes, but as input into roadmap decisions. If 30% of your tickets come from one feature, that is not a support issue. That is a product decision waiting to happen.

This work is less visible. There is no late-night incident, no dramatic recovery. There are simply fewer emergencies.

Which, ironically, is the real goal.

Most software companies eventually build an Emergency Room. They don’t always admit it. They call it Customer Care, Support, Helpdesk. But the dynamics are the same.

The more interesting question is what happens next.

Do you keep optimizing the Emergency Room for faster triage, better escalation, tighter SLAs? Or do you start asking why so many patients keep showing up in the first place?

When media still had edges

There is a shift in media that most people sense but rarely name. We still talk about reaching audiences, building products, growing traffic, increasing engagement. As if we are still at the center. But if you watch how content actually moves now, the story changes. We are no longer the main interface between information and the user. We are just one layer in a stack, and not the one that matters most.

It was not always this abstract. Media used to have edges. Literal ones. A newspaper stopped at page 32. The news ended at 7:30, whether you were done or not. You bought the whole thing, not a slice. Consumption was limited by design, not just by bandwidth. If someone started reading, they usually finished. Editorial choices shaped the entire experience. Distribution was something you owned and could predict.

Infinite content, finite attention

Then the internet erased those edges. At first, it felt like freedom. No limits on length, frequency, or format. But the trade was clear: infinite content, finite attention. Suddenly, attention, not distribution, became the bottleneck. The rules shifted.

Media stopped competing with other media and started competing with anything that could steal a few seconds of attention. Analytics made this obvious. People did not read the way we hoped. They skimmed, dropped off, clicked away. Audiences did not vanish, but their behavior became fragmented and unpredictable. Control over consumption disappeared, along with the idea that good content would naturally hold attention.

Platforms moved the front door

Platforms did not just speed up the shift. They locked it in. Once users stopped visiting websites and started scrolling feeds, the center of gravity moved. Facebook, YouTube, TikTok did not kill media companies. They just changed their job description. Media stopped being the destination and became a supplier. Distribution was no longer built; it was bargained for.

At first, this looked like a win: massive reach, global audiences, almost no friction. Over time, it turned into dependency. Traffic could spike or vanish for reasons you could not see, because the system was not yours. You were optimizing for a platform that could change the rules overnight. And often did.

Trust shifts from brands to people

Meanwhile, trust was quietly moving. It shifted from institutions to individuals. Audiences responded to a recognizable voice, not a carefully managed brand. One person could build a direct relationship with millions. Something traditional media could rarely match.

Figures like Joe Rogan or Tucker Carlson are not just examples of scale. They show a different kind of connection. Less formal, less filtered, more direct. Media brands did not vanish, but they stopped being the default. They became just another option.

We already adapted. And then the ground shifted again

By the time this shift was clear, the industry had already adapted. It learned to work with algorithms, optimize packaging, and think in terms of channels instead of owned audiences. It accepted that control over distribution was now limited.

And just as that started to feel stable, the ground shifted again.

AI is not just another channel. It is a new kind of interface. It does not deliver your content; it processes, compresses, and rebuilds it. The user does not need to visit your site, scroll a feed, or even pick a source. They ask a question and get an answer. That answer might use your work, but it will not keep your structure, your tone, or your priorities. Tools like NotebookLM show this in a controlled way. Large-scale AI systems take it much further.

From distribution to interpretation

This is where the shift gets deeper. Platforms changed distribution. AI changes interpretation. In the platform era, you could assume that if your content reached the user, it would look the way you made it. In the AI era, that assumption is gone.

Your work becomes input for a system that produces something new. The user interacts with that, not with your original. The relationship is now so indirect it is almost invisible. The pattern is clear: control moves away from the creator, first over distribution, then attention, now meaning.

The paradox of modern media

And yet, one thing has not changed. High-quality journalism still does something none of these layers can replace. It captures reality. It gathers facts, checks them, and builds a coherent account of what happened. Even the best AI systems depend on that layer. They do not create new knowledge. They just reorganize what already exists.

This is the paradox. Media creates the most essential part of the value chain: the raw understanding of reality. But other layers capture more and more of the visibility and value. The better the system gets at repackaging and redistributing, the less visible the original source becomes. Even as it stays essential.

What we are actually building now

In practice, media is not disappearing. Its role is just being rewritten. It is no longer enough to design products for direct consumption. Content now has to survive multiple transformations. It has to move through platforms, adapt to new formats, and be legible to systems that will reinterpret it.

The challenge is not just to make content, but to keep its meaning and integrity as it passes through layers built for other goals. Content is no longer a finished product. It is a component in a system you do not control, for an audience you do not reach, through interfaces you did not choose.

No way back, only forward

It is tempting to think this is a cycle, that media will someday regain control over distribution or rebuild direct relationships at scale. But the direction of change does not support that hope. Each new layer adds abstraction and moves the user further from the source. The original content stays necessary, but it becomes less visible as its own thing.

Journalism will not vanish. The need to understand and explain reality is not going anywhere. But the idea that journalism naturally becomes stable, self-contained media products is already gone. What remains is the core function and the need to make it survive in a system built to reshape and reinterpret everything it touches.

Recently, I heard something that sounded like a punchline. It wasn’t.

In some software companies, developer performance is now measured not just by delivery or quality, but by how many AI tokens they burn each month. The more you prompt, the better your KPI. Tokens as progress.

The first reaction is obvious: why reward people for spending more? Tokens are not free. On the surface, this looks like incentivizing waste.

But look closer, and it gets more interesting. Not more correct, just more revealing. This is less a KPI than a lever to force a behavioral shift.

Activity Is Not Outcome. Even If It’s Measurable

As a KPI, token usage is a clean example of measuring activity instead of outcome. The distinction is not subtle. Tie evaluation to tokens, and you get more prompting, more interaction, more output. What you do not get is better software, faster delivery, or higher quality.

This is the familiar pattern: once a metric becomes a target, it loses its value as a signal. The system optimizes for the number, not the impact. From a distance, it looks like progress. Up close, it is mostly motion.

You are Not Buying Tokens. You are Buying Behavior

Yet companies persist. Which suggests the real goal is elsewhere.

What is really being purchased is not tokens, but a shift in behavior. The aim is to make AI interaction default, not optional. Left alone, most people stick to what they know, underestimate new tools, and avoid the friction of learning something that does not yet feel essential.

So the organization reaches for a blunt tool: remove the choice. Use AI, or fall behind. Eventually, enough people adapt, and the system shifts from experimentation to habit. It is not elegant, but it works. Until it doesn’t.

The Productivity Paradox Nobody Likes to Mention

The catch is that more output does not guarantee better outcomes. Developers can generate more code, product managers more documents, designers more options, journalists more content. At the organizational level, speed and quality do not always improve. Sometimes, they slip.

Output is not outcome. More code means more to review, test, and maintain. More content means more noise. More options mean more decisions. AI rarely removes work; it just moves it, often from creation to validation and correction.

There is also the perception gap. People often feel faster with AI, even when they are not. The interaction creates a sense of acceleration, while hidden costs pile up. This is typical of transition phases: the shape of work changes before the results do.

From Doing the Work to Supervising It

Underneath all this, the roles themselves are shifting. Developers move from writing code to orchestrating it, from direct problem-solving to supervising machine-generated solutions. Product managers shape and evaluate AI outputs. Designers explore wider spaces before narrowing in. Customer care agents supervise more than they compose. Even journalists, in organizations that limit AI in reporting, use it for distribution, summarization, and research.

The pattern is not replacement, but reallocation. New habits, new judgment, and new definitions of good work follow.

Where Forced Adoption Actually Creates Leverage

Forced adoption sometimes creates leverage, but only in the right places. Where work is repetitive, structured, and easy to check, and where mistakes are cheap, AI speeds up iteration. Product managers draft faster, designers explore more options, customer care teams respond more consistently, journalists repackage content across formats. The value is in acceleration, not in replacing judgment.

In these cases, the gain is speed and breadth of exploration, not the outsourcing of decisions. The path to better choices gets shorter, but the choices remain yours.

Where It Quietly Breaks Things

The same approach breaks down in areas that depend on judgment, context, or accountability. Decision-making, prioritization, editorial voice, and complex reasoning do not improve when forced through AI. Here, the tool adds friction. People game the metric, offload thinking they should keep, or spend more time fixing AI output than doing the work themselves.

This is where the original instinct holds: the KPI is wrong. In these areas, mistakes are expensive and quality is hard to measure.

What a More Mature Approach Looks Like

More mature organizations move on. The question shifts from ‘did you use AI’ to ‘did it matter.’ Activity gives way to outcomes, volume to impact. AI becomes just another tool, visible in the workflow only when it adds value.

Judgment returns, including the choice not to use AI when it adds nothing. Experimentation is separated from production. Over time, the organization builds capability, not just usage. The goal shifts from forcing adoption to making effective use unavoidable.

It’s Not Just About Developers

This pattern is not limited to software. The same dynamic plays out in product management, design, customer care, journalism, marketing, analytics. Forced usage speeds adoption where work is structured and execution-heavy. It quietly erodes quality where judgment and context matter.

The real mistake is not force, but lack of precision. Treat every task as equally automatable, and the results will be equally mediocre.

So Was the KPI Stupid?

As a long-term measure, it is hard to defend. As a temporary lever to break inertia, it sometimes works. The problem is when organizations stop at the metric and keep optimizing for tokens, long after the real goal — changing how people work — should have taken over.

In the end, this is not about tokens or even productivity. It is about reshaping habits. And that is always more complex, and more fragile, than any KPI can capture.

For years, product managers have relied on a comforting story. You are the glue. The mini-CEO. The person at the intersection of business, technology, and design. You orchestrate complexity. You make things happen. It sounds important, vaguely strategic, and above all, safe. Safe from reorgs, safe from outsourcing, and certainly safe from automation.

Then AI arrives. No drama, just quiet competence. It writes specs that are good enough. It summarizes research faster than any analyst. It generates ideas on demand. It builds prototypes in hours, not weeks. Suddenly, much of what once justified the role starts to look negotiable.

This is where the discomfort sets in. Not because product management is vanishing, but because some parts were never as essential as we liked to think.

Execution Is Collapsing. Judgment Is Not

One of the more obvious shifts is that execution costs are collapsing. You do not need a full team or multiple cycles to validate a simple idea. A prompt, a tool, and some patience are often enough. The barrier to building has dropped so far that ‘we do not have resources’ is starting to sound less convincing.

Cheaper execution does not make the job simpler. It just changes where the difficulty sits. When it is easy to build ten versions, the real work is deciding which one should exist. When iteration is fast, hesitation is harder to hide. When delivery is not the bottleneck, thinking is.

This is where many product managers start to struggle. Execution was always easier to measure. Judgment is not. You cannot hide behind velocity charts when the real question is whether you are even moving in the right direction.

The Myth of “Human Skills”

The response to this shift is predictable. The industry leans on a familiar story: human skills will save us. Empathy, intuition, emotional intelligence, internal authority. These are framed as the last defense against AI, the things only humans can do.

There is some truth here, but also a fair amount of wishful thinking. Most product roles were not built on deep empathy or rare intuition. They were built on coordination, communication, and structured thinking. Useful, but not uniquely human. And increasingly, not out of reach for machines.

Even intuition, often treated as something mystical, is usually just compressed experience. Pattern recognition built up over time. AI is already good at that. The gap is not as wide as we would like.

The real differentiator is less romantic. It is the willingness to take responsibility for a decision when the data is incomplete, the signals are mixed, and the outcome is uncertain. AI can suggest, simulate, and optimize. It does not carry consequences. Humans still do.

Organizations Are Not Getting Simpler

Another assumption does not survive contact with reality: that AI will make organizations simpler. Fewer people, flatter structures, less friction. It sounds logical. It is mostly wrong.

As execution gets easier, alignment gets harder. More ideas, more experiments, more people who want to contribute. The result is not clarity, but noise. Competing directions, overlapping initiatives, and a growing need to decide what not to pursue.

Stakeholder management does not go away. It gets louder. People still want ownership, recognition, influence. They still bring their biases and ambitions. Faster cycles only amplify this, because there is less time to build consensus and more pressure to commit.

This is where ‘internal authority’ starts to matter, but not in a therapeutic way. It is not about self-reflection for its own sake. It is about being able to hold a position, make a call, and move forward without hiding behind endless validation.

More Tools, More Work, Less Excuses

One thing that gets less attention: AI does not reduce workload. It just moves it around. When writing, analysis, and prototyping get easier, expectations do not stay flat. They expand. You are expected to explore more options, run more experiments, consider more variables, and do it all faster.

The work becomes cognitively lighter at the surface level, but strategically heavier underneath. You are no longer limited by what you can produce, but by what you can meaningfully evaluate. The constraint shifts from output to attention. This creates a different kind of pressure. Not the pressure of scarce resources, but the pressure of too many possibilities. When almost anything can be built, the real skill is deciding what should not be built.lt.

And that is not something you can outsource to a model.

What the Role Actually Becomes

If you strip away the mythology, the future product manager looks less like a mini-CEO and more like something less glamorous and more demanding: a professional decision-maker working under constant uncertainty.

You are not there to produce documents. AI does that faster. You are not there to gather information. AI does that at scale. You are not even there to generate ideas. AI has an endless supply.

You are there to define what matters in a sea of options, to ignore what does not, to make a decision before it feels fully justified, and to change course before failure is obvious. You are there to create direction where none is visible.

That requires clarity of thought, some product taste, and enough psychological stability to operate without constant reassurance. Not because therapy is the future of product management, but because the buffers that once absorbed uncertainty are disappearing.

The Uncomfortable Conclusion

AI will not replace product managers. That is the comforting part.

The less comforting part is what comes next. AI will remove the scaffolding that made many product roles feel more substantial than they were. It will expose who was relying on process rather than thinking, who was coordinating rather than deciding, and who was optimizing for agreement rather than outcomes.

In that sense, AI is not a threat to the role. It is a stress test for it.

If your value was tied to execution, you would feel the pressure. If your value is tied to judgment, you may find yourself with more leverage than before. For the first time in a while, the role starts to look like what it always claimed to be.

Not managing products. But making decisions that shape them.

Most organizations are not struggling with strategy itself. They are struggling with what they think strategy is.

Strategy gets treated as a fixed plan: define it once, align everyone, put it in a deck, and execute. The more stable it looks, the more strategic it feels. Predictability becomes a proxy for rigor.

And then reality happens.

New technologies emerge. User behavior shifts in ways no research predicted. Stakeholders change priorities mid-cycle. Budgets shrink without warning. Entire markets become harder (or suddenly easier) to reach. And quietly, almost politely, the plan stops making sense.

But no one wants to say it out loud.

So the organization keeps moving. Teams deliver against assumptions that no longer hold. Leaders make small adjustments, but the strategy deck stays the same. Roadmaps change, the story does not. The result is not failed execution. It is something quieter: the gap between what the organization says and what it actually does keeps widening.

We call this drift. More often, it is just denial with better branding.

The uncomfortable part is not that the environment moves too fast. It is that we expect strategy to behave like a plan, even when plans expire quickly.

If you treat strategy as something that must remain stable in its details, you are guaranteed to be wrong. The only question is how long it takes you to notice.

A more useful way to think about strategy is to separate two things that are usually mixed together: direction and decisions.

Direction is the part that should remain relatively stable. It is your sense of where you are going and why. It includes your mission, your target audience, your positioning, and the constraints you are not willing to violate. In many cases, these constraints matter more than your ambitions. They define the space within which you are allowed to operate.

Decisions are everything else. What you build, how you distribute it, which technologies you adopt, what you prioritize this quarter, what you drop, what you postpone, what you experiment with. This layer should not be stable. It should change constantly, because it is your interface with reality.

Most organizations blur these layers. They try to make decisions as stable as direction, then wonder why everything gets slower, more rigid, and less connected to reality.

The answer is not to give up on long-term thinking. It is to swap detailed planning for something more resilient: a system that adapts within clear boundaries.

Instead of betting on a detailed future, you set a clear direction, a few guardrails, and a way to judge new opportunities. You do not try to predict what you will build in two years. You define which moves fit, and which do not.

When a new opportunity appears (and it always does), you don’t ask whether it was in the plan. You ask whether it fits the system.

Does it serve the audience we care about? Does it strengthen our positioning or dilute it? Does it respect the constraints we’ve set for ourselves? Does it connect to something we are already trying to achieve, or does it require us to quietly change direction without admitting it?

If it fits, you adapt. If it doesn’t, you say no.

This sounds simple. In practice, it is where most organizations stumble. Not for lack of ideas, but for lack of discipline to say no — especially when the idea is shiny, well-funded, or politically convenient.

Ironically, adapting within boundaries is harder than planning. Planning offers the illusion of control. Adaptation means making uncomfortable choices, over and over.

At this point, someone usually says: “But isn’t this just another way of describing strategy drift?” Not quite.

There are two types of drift. One is unconscious and dangerous. It happens when small decisions accumulate without anyone checking whether they still connect to the original direction. Over time, execution and strategy diverge, and the organization keeps moving — just not in a meaningful direction.

The other type is adaptive. It happens when reality changes, and the organization responds. This is not failure. This is survival.

The difference is not in the movement. It is in the acknowledgment.

If your organization has changed direction but the strategy still claims otherwise, you do not have adaptability. You have fragmentation. Teams work from different assumptions, leaders say something else, and alignment becomes theater.

The fix is not to stop change. It is to make change visible. Even small shifts need to be named and reflected in the story everyone shares. Otherwise, you are running parallel strategies and pretending it is one.

This is where cadence becomes critical.

Not everything moves at the same speed. Direction should be stable, checked now and then. Objectives shift more often. Execution is always in motion. But the real discipline is this: review your assumptions more often than you rewrite them.

A lightweight question is usually enough: has anything changed that would make this no longer true?

If the answer is no, you move on. If the answer is yes, you’ve caught something early — before it turns into months of misaligned work.

And yet, even with all of this in place, many organizations still struggle. Not because the model is wrong, but because something more fundamental is misaligned.

Teams get rewarded for output, not outcomes. Leaders get attention for launching things, not for keeping the system coherent. Stakeholders push for more, rarely for less. In this setup, drift is not a bug. It is the system working as designed.

You can roll out any framework you like. If the incentives stay the same, so will the behavior.

In complex environments — especially those shaped by external constraints, multiple markets, and competing priorities — perfect alignment is not a realistic goal. Trying to achieve it often leads to over-centralization and loss of responsiveness.

A more honest goal is not perfect alignment. It is controlled divergence.

Different teams will optimize for different realities. Different markets will require different tactics. Different constraints will force different trade-offs. That is not a failure of strategy. That is the reality of operating at scale.

What matters is that all of this happens within a shared directional frame. The same “why,” even if the “how” varies significantly.

Strategy, in this sense, is not a plan to execute. It is a system to maintain. Constantly.

It does not eliminate tension between long-term intent and short-term reality. It makes that tension visible, manageable, and, if you are disciplined enough, productive.

The alternative is simpler.

Keep the plan. Ignore the changes. Call the misalignment “execution issues.”

And hope no one notices how far you’ve drifted.

There is a product principle that gets repeated, usually with a half-smile: no one reads anything. Not documentation, not emails, not UI copy, and definitely not news past the headline. It sounds like a joke, but it is really a design constraint. The uncomfortable part is not that it is wrong. It is that it is just accurate enough to shape how we build.

Somewhere along the way, we accepted a contradiction. We produce more content than ever — articles, explainers, threads, summaries — while knowing most of it will not be read. Not in any meaningful way. At best, it gets scanned, skimmed, reduced to a headline and a vague sense of what happened. At worst, it is replaced by a two-line AI summary that sounds confident enough to pass for understanding.

Yet in newsrooms and product meetings, we still talk as if depth is the default. As if the average user is moving patiently from paragraph one to paragraph twelve, collecting nuance, context, and background along the way. It is a comforting fiction. Operationally, it does not hold up.

The so-called Miller Principle, or at least its modern version, forces a different perspective. If no one reads anything, every extra sentence is not just ignored. It becomes a liability. It is a bet that the user will invest attention they do not have. Most of the time, they do not.

Now, place this reality inside news consumption.

We expect users to understand geopolitical nuance, historical context, and conflicting narratives. We expect them to distinguish signal from noise, fact from framing, reporting from opinion. And we package all of this inside a structure that assumes time, focus, and patience. Then we act surprised when the headline becomes the story.

This is not a failure of the audience. It is a mismatch between product design and human behavior.

The uncomfortable implication is that the headline is not just an entry point. For many users, it is the whole experience. Any nuance not present there is not just hidden or delayed. It is lost.

This leaves us with a quiet editorial dilemma. Do we optimize for accuracy or for attention? The industry has been trying to do both and often ends up with neither: headlines too vague to inform, articles too long to be consumed.

Now add AI, and the problem shifts. It is no longer just about attention. It becomes a question of what users actually know.

AI does not just shorten content. It rewrites it into something that feels finished. A clean paragraph, a few confident statements, sometimes even a tidy conclusion. Ambiguity disappears. The user gets an answer, no effort required.

And that is precisely the problem.

When AI simplifies, it does not just remove words. It removes tension and uncertainty. It smooths out the messy edges where real understanding usually lives. What remains is a version of reality that is easier to process, and therefore easier to trust.

We are entering a phase where users are not just skipping the article. They are skipping the existence of the article altogether.

In this world, the role of a news product shifts. It is no longer just about publishing content. It becomes about managing how much of reality survives the process of compression.

This is where things get uncomfortable for product leaders. The trade-offs become harder to ignore.

If you take the ‘no one reads anything’ principle seriously, the answer is not to simplify everything. It is to design for selective depth. Accept that most users will stay at the surface, but make sure the surface is not misleading, and that moving deeper does not feel like a penalty.

Right now, depth often feels like a penalty. Long articles, dense paragraphs, context buried out of sight. The product signals: if you want nuance, you pay with your time. Most users do not take the deal.

The real challenge is not to make users read more. It is to make every extra second of attention disproportionately valuable. The goal is a system where understanding is layered, not hidden behind a wall of text.

But here is the tension. The more efficient the experience, the easier it is to consume a simplified version and move on. Efficiency and understanding do not always align. Sometimes they work against each other.

This leads to a slightly uncomfortable question.

If no one reads anything and AI explains everything, what are we actually optimizing for?

If the answer is speed, we are doing well. If the answer is understanding, we may be designing ourselves into a corner where users feel informed without actually being informed.

That is a much harder problem than low engagement or high bounce rates.

It is a product problem. It is an editorial problem. And increasingly, it is a trust problem.

Jogging did not become mainstream because people suddenly discovered discipline. It became normal because the cost of ignoring physical health became visible, then hard to ignore. Now, not caring about your fitness is the exception, not the rule.

We could see the same shift with mental discipline. The ability to focus, to read deeply, to think without interruption might stop being assumed and start being recognized as rare. And as with physical fitness, what is rare tends to become valuable. The metric just changes from steps to minutes of undistracted attention.

The analogy is not perfect, but it is close enough to make people uneasy. We spent decades learning how to train the body. The brain, meanwhile, was left to fend for itself. Now, as our environment quietly shifts to make focus harder, we are only just noticing the side effects.

We Fixed the Body. We Outsourced the Brain.

Physical fitness did not become a movement because people woke up one day with more willpower. It happened because the downsides of ignoring the body became obvious, then embarrassing. Sedentary living and bad diets stopped being invisible. They became problems with names, metrics, and solutions.

With mental focus, we are still pretending nothing has changed. We act as if attention and depth are default settings, immune to environment. Meanwhile, we keep redesigning our world to make sustained thinking less likely, not more.

Focus did not vanish. We traded it away, bit by bit, for convenience.

Your Brain Eats What You Feed It

Modern content is not just available. It is engineered for frictionless, repeat consumption. Short loops, emotional nudges, infinite feeds. These are not bugs. They are the product.

At this point, the food analogy stops being cute and starts being literal. Ultra-processed food is built to be irresistible. Digital content is built to remove every barrier to consumption. The issue is not occasional indulgence. The issue is what becomes normal.

When most inputs require little effort, the brain adapts. It gets better at skimming, reacting, and switching. It gets worse at staying put, analyzing, or handling complexity. This does not feel like loss. It just feels like the new baseline.

Which is exactly how most long-term shifts begin.

AI as the Perfect Convenience Layer

If that were the whole story, it would be enough. But AI adds a new twist. It does not just distract. It substitutes.

For the first time, we have tools that can handle parts of thinking for us. Structuring ideas, summarizing, drafting, exploring options. These are no longer reserved for people.

This does not make us less capable by itself. It just makes effort optional.

And when effort becomes optional, it usually disappears unless someone chooses to keep it.

The pattern is familiar. First, friction goes away. Then effort. Then the skill itself fades, not because it is lost, but because it is no longer needed.

The Predictable Turn to Regulation

At this stage, the usual response is to look for bigger levers. If the environment is working against us, maybe the answer is to regulate platforms, restrict algorithms, or protect users.

This is a familiar cycle. When a behavior becomes common and starts to hurt, we reach for external controls. Sometimes, especially for younger people, this makes sense.

But attention does not become discipline by decree. You cannot outsource the hard part. No policy will make people pick complexity over convenience every day.

Environment shapes behavior. It does not erase choice.

From Capability to Signal

The next shift is not in policy. It is in what people notice.

Physical fitness used to be a signal. Then it became a baseline. Now, it is often just for show. The skill did not change as much as the story around it.

Mental discipline may take the same path, but in reverse. As distraction becomes standard, focus and deep thinking start to look strange.

And what stands out tends to become valuable. Not because it is new, but because it is rare.

A Different Kind of Cardio

The analogy is not perfect, but the mechanism is simple. Systems adapt to use. Skills that get exercised improve. Skills that do not, fade.

There is no single breaking point. Just a slow change in what feels easy, what feels hard, and what feels worth the effort.

It is not hard to picture a quiet room where people who once tracked steps now sit without devices, working on something slow and difficult. Not out of nostalgia, but out of necessity.

From running clubs to chess clubs. A different kind of cardio.

Most IT organizations have a pattern that is obvious if you look for it, but almost no one says it out loud.

The underdog who improves in public gets the praise, the promotion, the story. The steady high performer, the one who delivers without drama, fades into the background. Trusted, relied on, and eventually taken for granted.

It sounds fair enough. Growth deserves recognition. Effort should matter. Everyone likes a story with an arc. But look closer and it is less about fairness, more about how the system chooses what counts as performance.

Performance systems are not built to weigh underdogs against high performers. They are built to flatten messy, conflicting signals into a single story. And then reward whatever is most visible at the time.

Why this is not a people problem but a system problem

The real issue is not bias in the usual sense. It is structural confusion.

We ask one system to judge output and effort, consistency and improvement, visibility and impact, short-term delivery and long-term thinking. Each pair is a real trade-off. None of them can be averaged away, but most organizations act as if they can be compressed into a single number or a tidy conversation.

In practice, the system just grabs whatever signal is easiest to see at review time. In knowledge work, that signal is almost never the most accurate one.

This is how performance management quietly becomes a storytelling exercise.

Output vs effort: why activity wins over impact

Take output versus effort. In theory, results matter more than activity. In practice, results in software are hard to pin down. Work is collaborative, dependencies are everywhere, and some of the best contributions are the ones you never see: problems that never happen, incidents that never escalate, systems that quietly get more stable.

Faced with all this ambiguity, managers reach for proxies. Responsiveness, visible urgency, number of tickets touched, presence in meetings. These signals are not useless, but they are much easier to spot than the real impact.

So the person who quietly removes a whole class of production issues goes unnoticed, while the person who fights incidents in public channels becomes a hero. The system does not reward chaos on purpose, but it reliably rewards the attention chaos creates.

Consistency vs improvement: why stability becomes invisible

The same distortion shows up with consistency versus improvement. High, stable performance has a strange weakness: it becomes the baseline. Once something is seen as normal, it stops drawing attention. No one tells a story about the thing that just works, every time.

Improvement, on the other hand, is always visible. It has direction, contrast, and emotional pull. Someone who moves from average to good creates a story that is easy to tell and easy to remember.

Over time, this shifts the balance. Organizations start to overweight trajectories and underweight reliability. High performers are not punished, but they stop standing out. Their contribution is assumed, not examined.

Assumption is a fragile kind of recognition.

Visibility vs impact: when performance becomes influence

Visibility versus impact is where the system quietly turns political. Every organization says it values impact, but few invest in making it measurable. What is left is visibility: who speaks, who presents, who shows up at the right moments, who can explain their work well.

Communication matters. But when it replaces evidence, the rules change. Performance reviews become contests of influence, where a clear story can outweigh real contribution.

This is how glue work — mentorship, documentation, reliability, cross-team coordination — either disappears or gets misread. It is critical to the system, but unless someone tracks it on purpose, it loses out to more visible output.

Short-term vs long-term: the trade-off nobody tracks

Short-term delivery versus long-term capability is the tension that usually causes damage later. Shipping features and hitting deadlines create immediate, measurable results. Investing in architecture, reducing technical debt, or mentoring juniors pays off slowly and rarely fits into a single review cycle.

So the system does what it is built to do: it prioritizes what it can measure right now.

Teams get efficient in the short term and fragile in the long term. Learning slows, complexity grows, and eventually delivery starts to slip. When that happens, the usual response is more pressure on delivery, which just repeats the cycle.

Why adding more metrics usually makes it worse

At this point, the instinct is to fix performance by adding more metrics, more dashboards, more reviews. In reality, this usually makes the problem louder, not smaller.

The real issue is that performance systems are asked to do two incompatible jobs at once. They are used for administrative decisions — compensation, promotions, rankings — and at the same time for development, coaching, and growth.

These jobs need different signals and different interpretations. Admin decisions want stability and comparability. Development needs trends, potential, and context. When both are forced into the same box, the system gets inconsistent and easier to game.

Why high performers burn out in “fair” systems

There is another, less comfortable pattern here. High performers get more demand because they are trusted. At the same time, their output becomes the new normal, and recognition fails to keep pace with expectations.

This creates a familiar imbalance: high effort, high responsibility, low visible reward. Over time, this is a reliable path to burnout. Not because people are weak or overcommitted, but because the system slowly disconnects effort from recognition.

What a more coherent system actually looks like

A better approach does not start with new metrics or frameworks. It starts by admitting that performance is multi-dimensional, and that different dimensions belong at different levels.

Some signals make sense at the team or system level: delivery speed, reliability, stability. Others belong to the individual: decision quality, ownership, ability to simplify, contribution to team capability.

Once you separate these, evaluation stops being about squeezing everything into one score. It becomes about building a coherent, evidence-based view of contribution. Invisible work is made visible on purpose. Context is documented, not assumed. Sustainability is treated as part of performance, not an afterthought.

Back to underdogs vs high performers

The tension between underdogs and high performers does not disappear in this kind of system. But it becomes explicit, manageable, and less about who tells the better story.

And that is usually the difference between a performance system that feels political and one that feels fair.

Explaining your product to everyone at once feels efficient and transparent. In practice, it is one of the fastest ways to make sure no one actually understands what you mean.

We like the idea of a single story that works for everyone — users, stakeholders, engineers, leadership, partners. It sounds clean and professional. It rarely survives contact with reality.

These groups are not just different people. They think in different systems. Each listens for something else, filters information differently, and decides based on different signals. When you give them the same message, they do not align. They reinterpret.

That reinterpretation is where most product communication quietly breaks.

You launch a feature and write a careful explanation. You cover the user problem, business value, technical constraints, and some vision. It feels complete, so you share it widely.

Users ignore most of it. They want to know what changes for them right now. Stakeholders ask follow-up questions to assess risk and defend the decision. The team starts building but interprets the goal differently. Management scans, jumps to conclusions, and moves on. Partners miss how this connects to their systems.

Nothing dramatic happens. Alignment is lost.

The usual reaction is to say we need to communicate better. In practice, the problem is not clarity. It is targeting.

Good product storytelling is not about simplifying one message for everyone. It is about shaping different versions so each audience gets what they need.

Users are not interested in your reasoning. They want to see their situation reflected and understand how the product changes it. The moment you move from showing value to explaining context, you lose them. They are not judging your thinking. They are judging whether this makes their life easier, faster, or safer.

Stakeholders are not trying to use the product. They are trying to justify decisions. They need a story that holds up under pressure and can be repeated when challenged. Timing, alternatives, and evidence matter. If your story cannot be defended in a budget or prioritization discussion, it does not work for them.

Inside the team, the problem changes. Storytelling is not about persuasion. It is about precision. Vague goals create expensive misunderstandings. Phrases like ‘improve engagement’ or ‘enhance user experience’ do not align a team. They create space for multiple interpretations. A strong internal story removes ambiguity and makes success observable. If people describe the goal differently, the story has already failed.

Management looks for something else. Features matter less than the quality of decisions. They are evaluating how you handle trade-offs, assess risk, and prioritize under constraints. A story that only talks about opportunity and ignores what you are not doing or what could go wrong sounds incomplete. Clarity about limits builds more trust than optimism.

With partners, the gap is operational. They do not need your intent or reasoning. They need to know how things connect: what goes in, what comes out, who is responsible, and where the boundaries are. If that is not clear, they fill the gaps with their own assumptions. What you later call integration complexity is often just unclear communication.

Most teams ignore one audience: the future version of the organization. Months later, people change, context disappears, and decisions that once felt obvious become opaque. Someone asks why a certain approach was chosen, and the only answer is ‘it made sense at the time.’ At that point, the story was never told. What is missing is not the record of what was done, but the reasoning behind it — the constraints, alternatives, and trade-offs that shaped the decision.

Step back and a pattern appears. The product does not change. The facts stay the same. What changes is the question each audience is trying to answer. Users ask what this does for them. Stakeholders ask if it is worth it. The team asks what needs to be built. Management asks if this is the right call in context. Partners ask how to connect to it. The future organization asks why it ended up this way.

Trying to answer all these questions at once leads to messages that feel complete but land nowhere. They contain everything and emphasize nothing.

A more effective approach is less elegant and more precise. Before communicating, decide which audience you are addressing and what decision you expect from them. Shape the story around that decision, even if it means leaving other aspects aside.

This is where product communication gets uncomfortable. It stops being about covering everything and starts being about being selective.

You do not need a better, more polished, or more inspiring story. You need to aim it.

At this point, the “remote vs. office” debate feels less like a strategy discussion and more like a ritual. Leaders defend office presence as discipline. Employees defend remote work as freedom. Both sides are convinced they are protecting productivity.

In reality, most are protecting something else: their own comfort with how work used to be.

If a company needs people in the office to feel in control, the issue is not remote work. It is a lack of trust, clarity, and measurable outcomes. Office attendance does not solve that.

The myths we keep repeating

Let’s start with a few ideas that sound reasonable but don’t hold up well under scrutiny.

Remote work is often framed as a reward you earn. In practice, flexible work reduces attrition but leaves performance mostly unchanged. So remote work is less a perk, more a retention tool.

Presence is often equated with productivity. It is not. Presence gives visibility, and visibility is easier to measure than output.

There is also the claim that the office is only for brainstorming. That is only part of the story. In-person work also builds informal networks, speeds up onboarding, and supports mentorship. These are the invisible systems that keep organizations running.

Where remote work actually breaks

Remote work does not fail randomly. It fails predictably.

Remote work struggles when tasks are ambiguous, when tight coordination is needed, when knowledge is informal, or when fast feedback is required. It also fails where learning depends on observation instead of clear instruction.

You see this in collaboration patterns. Remote teams become more siloed. Cross-team interactions drop. People work more with their immediate group and less across the company.

Innovation drops when coordination is weak. Not because people are less creative at home, but because spontaneous exchange is less likely.

But when work is structured, measurable, and needs long focus, remote often matches or beats the office. Fewer interruptions. More control. Less performance theater.

The hidden costs of hybrid

Hybrid is sold as a compromise. In reality, it often combines the downsides of both models.

Uncoordinated office days mean empty offices or people commuting just to join video calls. Communication overhead grows. Meetings multiply. Calendars fragment.

Mentorship suffers quietly. Seniors spend less time transferring knowledge. Juniors lose informal learning. The cost shows up later.

Decision-making also suffers. Without clear rules, frustration grows. People see decisions as arbitrary.

Stop choosing. Start designing.

The more useful framing is simple: work is not one thing. It is a set of activities with different requirements.

Some tasks need deep focus and independence. Others need high-bandwidth interaction. Treating them the same, and putting them in the same environment, is where most organizations fail.

A more effective model looks like this:

• Remote is the default for execution. Clear tasks, defined outputs, measurable outcomes.

• Office presence is triggered by the work, not mandated. You come together when needed: ambiguity, cross-team alignment, onboarding, complex feedback.

When you come together, it is intentional and synchronized. Not optional attendance scattered through the week.

Replace presence with evidence

The final shift is uncomfortable but necessary.

Modern work cannot be managed by observation. It needs to be managed by signals.

Cycle time. Decision speed. Error rates. Time to onboard new hires. Retention.

These are harder to measure than attendance. But they are also harder to fake.

Once leaders trust these signals, the urge to see people working fades. So does much of the anxiety behind return-to-office mandates.

The actual deal

Remote work is not a privilege. It is also not a free-for-all.

The workable model is a simple trade:

• Freedom by default.

• Structure by necessity.

Not ideology. Not control. Design. And not the idea that a chair in an office is a performance system.

Every few weeks, a new wave of headlines arrives with a familiar message: AI is taking over journalism. Somewhere between conference slides, LinkedIn posts, and media think pieces, a number appears — 5%, 10%, sometimes much higher — suggesting that a growing share of news content is now written “by AI” or “with AI.”

It sounds dramatic. It is meant to sound dramatic.

The implied image is almost cinematic: invisible systems drafting articles at scale, quietly replacing human writers, reshaping the very idea of journalism. A reader scrolling through news feeds might reasonably assume that somewhere along the line, the byline has become… optional.

And yet, if you step inside an actual newsroom, the picture looks very different. Not less interesting — just less theatrical.

AI is indeed entering editorial processes at speed. But it is not marching through the front door, announcing itself as the new author of record. It is slipping in through side entrances — tools, assistants, small utilities — embedding itself into workflows in ways that are often invisible both to readers and, sometimes, even to the people describing them publicly.

Which raises a more precise question: when we say “AI is used in the newsroom,” what are we actually talking about?

What “using AI in the newsroom” actually means

The phrase AI-generated journalism suggests a binary reality: either a human wrote the article, or a machine did. In practice, the situation is far more nuanced and far more layered.

At one extreme, there are fully automated articles. These exist, but they tend to live in highly structured environments: sports results, financial earnings, weather updates, or election data. In these cases, the “article” is essentially a transformation of structured data into readable text. This is not new — variations of this have existed for years, long before the current generation of large language models.

At the other end of the spectrum is something much more common, but much harder to label.

A journalist writes a story, but uses AI to generate five headline options and selects one. Another journalist feeds a long interview transcript into a tool to extract key quotes. An editor asks AI to shorten a paragraph, adjust tone, or produce a summary for social media. A producer uses it to translate material or suggest alternative framing for a lead.

None of these scenarios fit neatly into “AI wrote the article.” Yet all of them are part of the editorial process.

This creates a wide, almost elastic definition of AI usage. The same newsroom might claim both “we don’t use AI to write articles” and “AI is deeply integrated into our workflow” — and both statements would be true.

Which is why the discussion about percentages often feels misleading. It compresses a spectrum into a single number.

To understand what is actually changing, it is more useful to look not at how much content AI writes, but at where in the process AI is most effective.

The tasks AI automates first — and why

AI does not begin by taking over the most visible or prestigious parts of journalism. It begins with the work that journalists themselves would gladly spend less time doing.

Transcribing interviews that stretch over hours. Translating material from one language to another. Condensing long reports into usable summaries. Generating multiple headline options under time pressure. Cleaning up grammar, tightening structure, shortening text without losing meaning.

These tasks are not trivial, but they are procedural. They require effort, time, and attention — but not necessarily deep editorial judgment.

And that distinction matters.

AI performs best where the output can be quickly evaluated by a human. A headline can be judged in seconds. A summary can be compared to the source. A transcript can be verified against audio. The human remains firmly in control, but the machine accelerates the process.

By contrast, tasks that require interpretation, contextual understanding, and accountability — deciding what the story is, which facts matter, how they should be framed — remain much more resistant to automation.

AI enters the newsroom not by replacing judgment, but by reducing friction. It removes the small delays that accumulate across the workflow — the minutes that become hours, the hours that become days.

And once those delays begin to disappear, something else happens. AI starts to spread into places where its presence is less obvious.

Where AI is used quietly

The most interesting part of AI adoption in journalism is not where it is visible. It is where it is not.

Public discussions tend to focus on the idea of AI writing articles. Inside newsrooms, much of the real impact happens earlier (and later) in the process.

Before a single line is written, AI may already be involved. It can help navigate large document sets, extract key points from reports, identify patterns across sources, or surface relevant material from archives. For investigative work, this is particularly valuable: not as a source of truth, but as a way to reduce the time needed to find where truth might be hiding.

None of this appears in the final publication. The reader never sees the hours saved. After the article is written, another layer of quiet activity begins.

A single piece of journalism rarely lives as a single piece anymore. It needs to be adapted — for search, for mobile, for social media, for newsletters, for different audience segments. Each of these requires slightly different wording, structure, or emphasis.

This is where AI is extremely efficient.

It can generate variations quickly, test different angles, produce summaries of different lengths, and adapt tone depending on the channel. Again, the journalist remains responsible for the content — but the distribution layer becomes increasingly assisted.

In effect, AI is not just participating in journalism. It is participating in how journalism moves.

What the real AI workflow in major newsrooms looks like

If you strip away the narratives and look at how large news organizations actually operate today, the workflow is less revolutionary than evolutionary.

The core remains intact. A journalist investigates, interviews, verifies, and writes. An editor reviews, challenges, refines. Accountability sits with people, not systems.

Around this core, however, a new layer has formed.

During research, AI may assist in processing documents or transcripts. During writing, it may offer structural suggestions or alternative phrasings. After writing, it contributes to headlines, summaries, and distribution formats. Throughout the process, it acts as a tool — sometimes helpful, sometimes ignored, occasionally wrong.

Importantly, it is rarely autonomous.

The idea that AI writes an article and a human simply approves it is not how most serious newsrooms operate. The direction is usually the opposite: a human creates the material, and AI supports specific steps around it.

This distinction may seem subtle, but it is fundamental. It defines whether AI is an author or an instrument.

For now, in most traditional news organizations, it is very clearly the latter.

A few conclusions

So how deeply is AI embedded in journalism?

Deep enough to matter. Not deep enough to replace it.

The more accurate picture is not one of sudden disruption, but of gradual integration. AI is becoming part of the infrastructure of news production: accelerating research, simplifying editing, enabling faster and more flexible distribution.

At the same time, the boundaries are holding. The closer we get to the core of journalism — facts, interpretation, accountability — the more cautious newsrooms remain.

This creates an interesting tension.

From the outside, it looks like AI is writing the news. From the inside, it feels more like AI is reorganizing the work around the news.

And perhaps that is the more useful way to think about it.

Journalism is not being replaced. It is being restructured — one quiet workflow improvement at a time.

Most product and engineering teams have people who fall into one of two groups.

The first group treats every stakeholder request as an order. A new feature? Yes. A last-minute change? Yes. Another urgent request from another department? Yes again. Calendars fill up, roadmaps get longer, and teams quietly work evenings and weekends to keep all the promises. The Yes-Man seems helpful and flexible, but eventually, deadlines slip, the team burns out, and everyone wonders who approved it all.

The second group is the opposite. Every request gets pushback. “Not in the roadmap.” “No resources.” “Come back next quarter.” Sometimes it’s just a polite no. Mister No protects the team from overload, but over time, stakeholders stop sharing ideas, innovation slows, and the product team starts to seem more like a gatekeeper than a partner.

Both attitudes make sense. One focuses on keeping stakeholders happy. The other focuses on stability and control. But both avoid the same uncomfortable task: negotiation.

The real job of product leadership isn’t just saying yes or no. It’s turning requests into priority decisions.

When someone asks for a new feature, the honest answer is rarely just yes or no. It’s usually something like, “Yes, if we move something else out of the plan,” or, “Yes, but that will push the analytics work back by three weeks.” The conversation shifts from approval to discussing trade-offs.

This is when priorities become real. When requests are considered alone, everything seems important. Every idea feels urgent by itself. But once you compare it to other planned work, the question changes from “Is this useful?” to “Is this more important than what we’re already doing?”

And that’s a much harder question to answer.

In practice, good teams make trade-offs clear as soon as possible. They show the roadmap, the backlog, and what the team is working on, along with available capacity. Instead of saying, “we’ll try to fit it in,” they explain each request in terms of time, effort, and impact. This isn’t to block ideas, but to bring clarity to the conversation.

At this point, something interesting often happens. Many requests get smaller. A “must-have feature” becomes “maybe a smaller version would work.” An urgent request turns into “maybe next quarter is fine.” Sometimes, two stakeholders realize they’re competing for the same resources and start negotiating with each other instead of pushing the team.

In other words, being transparent does half the negotiating for you.

Another key point is to separate ideas from commitments. Product teams should welcome ideas, but making commitments should be much harder. Anyone can suggest something new, but deciding to build it should follow the same prioritization process as everything else. This keeps the team from making accidental promises that turn into obligations.

This approach also takes much of the emotion out of these conversations. If a team just says “no,” the discussion feels personal and stakeholders feel rejected. If a team says “yes” but sacrifices its own capacity, resentment builds within the team.

But when the answer is, “here are the trade-offs,” the decision is no longer personal. It becomes about structure. The conversation shifts from asking for permission to discussing how to allocate resources.

Interestingly, many requests disappear once trade-offs are clear. When stakeholders see that their urgent feature would delay something else they care about, priorities become clear much faster.

Good product teams work differently. Instead of making promises or refusing requests, they set conditions. Every request goes through the same process: what’s the impact, what’s the effort, and what needs to be postponed to make room for it.

This approach has an unexpected benefit. Stakeholders start negotiating with each other instead of with the team, which is usually a much healthier dynamic.

So next time someone asks your team for something new, try not to be a Yes-Man. Also, avoid becoming Mister No.

Try something a bit more uncomfortable. Say, “Yes, we can do this. Let’s decide together what will no longer be a priority.”

At some point in every leadership role, you realize that your job is not to produce results. It is to translate reality.

Roadmaps, OKRs, and delivery plans are just tools. The real work often happens in more personal moments, like when you stand in front of your team, open a Zoom call, or write a Slack message and decide how to share the news:

• We won

• We lost

• We don’t know yet

How well you communicate shapes more than just morale. It affects trust, alignment, and long-term results. I have seen strong strategies fail because of poor communication, and average strategies succeed when the message was clear and consistent.

Most teams do not fail because of poor strategy. They fall apart because of mixed messages, such as excessive optimism, delayed candor, or silence when people need clarity.

Let’s talk about the good, the bad, and the ugly.

The Good

Good news looks easy. It rarely is.

A feature performs better than expected. Traffic grows. Leadership approves budget. A difficult project lands well with users. The numbers look good. The mood lifts.

The risk here is subtle.

Some leaders minimize success in the name of discipline: “Great, but let’s not celebrate too much.” The intention is focus. The effect is emotional flatness. Over time, people stop feeling that their work matters.

Some leaders exaggerate success. Every small win is called “a game changer.” Every milestone is “transformational.” This can feel exciting at first, but when reality sets in, people lose trust.

Good news is not about excitement. It is about pattern recognition.

If you share success without explaining why it happened, you are not leading. You are just reporting. And reporting is neutral. Leadership is interpretive.

• What exactly worked?

• Was it timing?

• Was it positioning?

• Was it cross-functional collaboration?

• Was it a risky decision that paid off?

Good news should make it clear which actions are worth repeating. It should help the team understand what success looks like. Credit should be given specifically, not just with a vague “great job, everyone.” Clear recognition builds pride and sets standards.

Celebration is useful. But reinforcement is strategic. Good news can boost energy if you handle it with discipline.

The Bad

Bad news is where leadership maturity becomes visible.

A deadline slips. A release underperforms. A budget is reduced. A strategic direction changes. A restructuring is announced.

There are predictable failure modes.

The first problem is the delay. Leaders hope the issue will go away or become less important, but that rarely happens. In the meantime, uncertainty spreads through the team.

The second problem is dilution. Leaders use soft language like “some challenges,” “temporary adjustments,” or “minor recalibration.” People pick up on the tone and sense something is wrong, but they cannot see the real problem. This makes anxiety grow.

The third problem is delegation. Leaders pass difficult messages down the chain. A manager might ask a team lead to share news that really came from above. The information may be accurate, but it does not feel like the right person is taking responsibility.

Bad news does not require drama. It requires structure.

• Here are the facts.

• Here are the constraints.

• Here is what we are doing.

• Here is what this means for you.

• Here is what remains uncertain.

Clarity reduces anxiety. Vagueness amplifies it.

Teams are surprisingly resilient when reality is explicit. What they struggle with is ambiguity disguised as comfort.

I have learned that the sooner you share bad news with context, the sooner your team can regain stability. If you stay silent, people create their own stories, and those stories are rarely positive.

Bad news, handled properly, builds credibility. It signals that you are not curating reality. You are sharing it.

The Ugly

The most complex category is neither success nor failure.

It is uncertainty.

Funding is under review. Strategic options are being considered. There are outside pressures that might affect your department. The market may be shifting, but it is not clear yet. A product experiment could change priorities or simply fade away.

This is where many leaders freeze.

Leaders worry about saying too much and being wrong later, so they say nothing. Sometimes they try to reassure the team too soon by saying, “Everything is fine.” But teams notice when something is off. They pick up on tension, see the signs, and read between the lines.

Uncertainty does not scare professionals. Lack of framing does.

The discipline here is subtle.

• Define what is known.

• Define what is not known.

• Set the next checkpoint, which is when you expect to have more clarity.

You do not need certainty. You need boundaries.

Sometimes the most powerful thing a leader can say is: “I don’t know yet. Here is what we are monitoring. Here is when we will revisit this.”

Authority is not built on omniscience. It is built on composure in ambiguity.

When uncertainty is acknowledged, teams can calibrate emotionally. When it is hidden, it grows in the shadows and turns into a rumor.

In my experience, unclear situations are when trust is either built or lost for good. In these moments, people pay more attention to what you do than what you say.

Sharing news is not a soft skill. It is a strategic one.

• Good news should reinforce what works.

• Bad news should clarify direction.

• Unclear news should define reality.

If you reflect honestly on your own leadership, which category do you handle worst?

• Is it the good news, because you move on too quickly?

• Is it the bad news, because you put it off?

• Or is it the ugly news, because uncertainty makes you uneasy?

The answer is usually personal. And rarely visible in a dashboard.

But your team always knows.

I believe in sticking to a clear work routine. Arrive on time, leave on time, respect weekends, and take your vacations. People with families, hobbies, and health concerns need this kind of structure.

But even so, I constantly catch myself checking email in the evening. Replying on Saturday. Clarifying something small during vacation. Not because someone demands it. Not because management pressures me. But because of a quiet internal calculation: “It is easier to fix this now than to deal with the consequences on Monday.”

Spending five minutes today can save two hours of trouble tomorrow. A quick answer can stop misunderstandings, and a fast decision can help others move forward. Operationally, this logic makes sense.

But this is where the trap starts.

When a few people keep acting this way, they slowly change what’s normal. Management notices quick responses, deadlines met, and problems avoided. The system looks efficient. But the hidden cost — personal time used to cover planning gaps — goes unnoticed.

Soon, weekend replies stop being rare and just become part of the routine. Someone who waits until Monday to respond might seem “less engaged.” The person who says, “I will finalize this over the weekend (despite a sick child at home),” starts to look like a quiet hero. It’s not officially required, but it’s quietly admired.

Hero culture is tempting. It feels productive, responsible, and grown-up. But often, it hides bigger problems like unrealistic planning, unclear priorities, not enough staff, poor delegation, or indecision from managers.

If deadlines are always saved by late-night work, the organization never learns to plan well. If getting things done depends on extra hours, the system doesn’t have enough resources. It just hasn’t realized it yet.

The hard truth is that many of us choose to take part in this cycle. It’s not because we’re afraid, but because we want to be efficient, professional, and believe that small actions now will stop bigger problems later.

And often, that’s true.

But lasting success doesn’t come from good intentions. It comes from setting clear boundaries.

I’m not saying we should become strict clock-watchers. Emergencies will happen. Product launches need extra effort. Sometimes, big problems mean late nights. Taking ownership is part of being a leader.

The real question is: are we just handling exceptions, or are we making them the new normal?

• If working on weekends is rare, it shows something urgent is happening.

• If weekend work becomes routine, it’s a sign that something is wrong.

Leaving the office on time isn’t lazy. It forces the organization to set better priorities, plan more realistically, and make real trade-offs instead of quietly taking up your personal time.

Still, next Saturday, I’ll probably check my inbox again.

This tension is real. The system rewards quick responses. I know that spending five minutes now can prevent a bigger mess later. But I also know that every small fix makes it more likely people will expect me to always step in.

Leadership isn’t just about fixing problems. It’s also about knowing which ones can wait.

The toughest boundary to set is the one with yourself.