We are moving into the AI era before we have settled the bill for the smartphone era. This may explain why some of the pushback against AI is less about robots or job losses and more about a sense of repetition. The promises are familiar: save time, remove routine, connect everyone, create more freedom. On paper, much of this happened. We can reach anyone, work from anywhere, and access information instantly. We can also receive seventeen urgent messages before breakfast. Progress delivered what it promised. It just left out the part about operating costs.

The invoice from the last technology wave is still open. It appears as permanent availability, fragmented attention, and the expectation that people can monitor multiple channels, join meetings, and still deliver focused work. We call this productivity, mostly because ‘continuous cognitive assault’ does not fit in a quarterly report. Now AI arrives with a new offer: it can write, summarize, analyze, generate options, and clear hours of routine work. The real question is what organizations will actually do with those saved hours.

The optimistic version is that people will use the freed-up time for deeper thinking, creativity, and recovery. The more common pattern is that saved capacity becomes the new baseline. If someone can now produce twice as much, the organization expects twice as much, usually by next quarter and ideally without a bigger budget. This is how efficiency tends to work in real systems. A tool saves thirty minutes, so another task appears. Automation removes a process, so management adds three new reporting requirements. AI drafts something in seconds, but someone still needs to review, verify, adjust, compare, and take responsibility when the confident output turns out to be wrong.

Work rarely disappears. It shifts from creation to supervision, and supervision can be just as draining. Take a product manager before AI: review research, prepare a proposal, discuss with the team, make a decision, explain it to stakeholders. Now add five AI tools: one for customer feedback, one for roadmaps, another for requirements, another for competitor analysis, and one more for meeting notes. On paper, this looks like a workload reduction. In practice, the manager now inspects five streams of output, spots contradictions, questions assumptions, checks sources, decides what matters, and explains why the AI-generated strategy is not automatically the company strategy. The job has not shrunk. It has become a control tower, and the planes keep coming.

This is where the conversation about technology gets selective. We measure what machines produce, but rarely what humans have to absorb. Drafts created, tickets resolved, reports generated, minutes saved: all easy to count. The extra verification, monitoring, switching, interpretation, and decision-making? Not so much. The system sees output. The nervous system sees Tuesday.

This pattern is not new. Social networks promised connection and monetized attention. Smartphones promised mobility and turned every location into a potential workplace. Collaboration platforms promised transparency and delivered environments where key information hides in emails, chats, boards, comments, or meetings that could have been emails but, in a strategic twist, became both. The tools are not the problem. The issue is that every benefit creates new costs, and those costs rarely land in the same place as the benefits.

Companies get growth, data, speed, scale, and higher output. Individuals pay with attention, recovery, sleep, and the ability to stay with a hard problem long enough to solve it. When people struggle, organizations offer help: time-management training, resilience workshops, meditation apps, and a digital wellbeing webinar scheduled during lunch because calendars are full. The message is polite but clear: the system is fine; the employee needs an upgrade.

We keep repairing people and returning them to the same environment that exhausted them. Personal habits do matter. People can disable notifications, protect focus time, improve boundaries, and use technology more consciously. But individual discipline cannot fully compensate for a system designed around constant responsiveness, excessive information, and permanent task switching. You can practise digital hygiene. You cannot personally redesign your company’s operating model.

This is why cognitive overload should not be discussed only as an individual weakness. In many workplaces, it is an expected result of how work is structured. If a role requires someone to monitor several platforms, react continuously, make decisions under time pressure, and switch between strategic and operational questions every few minutes, exhaustion is not surprising. It is not a mysterious failure of resilience. It is the output of the system.

The uncomfortable reality is that companies have little incentive to look too closely. Organizations measure what supports investment decisions: revenue, engagement, adoption, throughput, utilization, conversion, growth. The cost to human attention is harder to quantify and less convenient to discuss. A company rolling out AI wants to show time saved, not that the saved time is now filled with more supervision, more parallel work, and higher expectations. A platform wants to show engagement, not whether users can still read ten pages without checking their phones.

The side creating the effect rarely wants to measure the harm. The side experiencing it rarely has the data or power to do so. The cost disappears into the gap between what is profitable and what is measurable.

This is not an argument against AI. AI may be one of the most valuable tools in decades. It can remove meaningless work, expand access to expertise, improve decisions, and give small teams capabilities that used to require large organizations. But none of this is automatic. AI can reduce cognitive load, or multiply it. It can protect time for deeper work, or create more streams to monitor. It can give people more autonomy, or just increase the volume they are expected to handle.

Technology does not make that decision. Management does.

The real question is not whether AI makes people more productive. It is what happens to the capacity AI creates. Does the organization return some of it as time to think, recover, learn, and improve decisions? Or does it immediately convert every saved minute into another task, another target, and another dashboard to prove the transformation worked?

Progress always comes with a price. Industrial growth cost bodies, cities, and safety before rules caught up. The digital economy cost attention, privacy, boundaries, and recovery. AI will have a price too. The goal is not to stop progress or pretend the past was better. It is to stop treating the human cost as a personal problem discovered after the rollout.

Responsible progress means measuring not just what technology lets people produce, but what people have to carry to produce it. When every new tool promises to save time, but nobody has any time left, maybe the tool is not the only part of the system that needs a closer look.

“We don’t have the budget for salary increases this year. How do we keep people motivated?”

It is one of the most common management questions I hear. Usually, it comes from good managers who genuinely care about their teams and want to do the right thing. They are hoping there is a clever replacement for money — some management trick, a better recognition program, a team-building event, or perhaps another inspirational speech. The assumption is understandable. If you cannot change salaries, surely you need to find another way to motivate people.

I think the assumption itself is wrong.

If money were the main driver of performance, the world’s highest-paying companies would automatically have the highest-performing teams. Every employee who received a raise would become noticeably more productive. Every generous bonus program would produce exceptional results year after year. We all know that is not how organizations work. Some highly paid companies are incredibly innovative. Others are painfully bureaucratic. Some underpay people and somehow still manage to build remarkable cultures. Others offer excellent compensation and struggle with disengaged employees who are counting the days until Friday.

That does not mean money is unimportant. Quite the opposite.

Pay people below market, and eventually their attention shifts away from customers, products, and colleagues toward recruiters, salary surveys, and job boards. It is difficult to expect someone to focus on solving business problems while they are worried about paying their own bills. Fair compensation is not a luxury, and it is certainly not something organizations can ignore. Nobody should be expected to sacrifice their financial well-being simply because management believes people should work for “the mission.”

But something interesting happens once salaries become fair.

People receive a raise. They feel appreciated. They celebrate with their family, buy something they have wanted for a while, or simply enjoy seeing a larger number on their next paycheck. A few months later, life quietly adjusts. The higher salary no longer feels like a reward. It becomes normal. Expenses grow to match income. Expectations reset. The company has permanently increased its payroll, while the motivational effect that justified the increase has largely disappeared.

This is not a criticism of employees. It is simply how people work. We become accustomed to better circumstances surprisingly quickly. Companies often assume motivation grows in a straight line with compensation, while human psychology insists on treating salary increases as temporary emotional events and permanent financial baselines.

This is why I believe compensation and motivation are often confused.

Fair pay removes dissatisfaction. It creates trust. It reduces the temptation to leave. It allows people to focus on work instead of worrying about whether they are being treated fairly. In other words, it creates the conditions in which good work becomes possible. But creating the conditions for performance is not the same thing as creating performance itself. Fair compensation is not a competitive advantage. It is the admission ticket that allows the real management work to begin.

Unfortunately, this is exactly where many organizations stop. Budgets are approved. Salaries are reviewed. Annual bonuses are distributed. Leadership proudly announces another investment in people. Six months later, everyone is asking the same question again because productivity, collaboration, innovation, and execution have barely changed.

That is hardly surprising. Knowledge workers are not vending machines, where inserting another dollar reliably produces another unit of output. Their performance depends on dozens of factors that have very little to do with compensation once basic fairness has been established.

The first of those factors is clarity. People cannot consistently perform well if success itself remains vague. Surprisingly often, employees are not struggling because they lack motivation but because they are trying to satisfy five different priorities at the same time. They receive conflicting messages from different managers, shifting business priorities, and objectives that sound impressive but provide very little practical guidance. Clear goals do not simply improve focus. They reduce stress, improve decision-making, and allow people to spend their energy solving problems instead of guessing which problem deserves attention today.

The second factor is feedback, and not the kind delivered once a year during a performance review that feels more like an archaeological excavation than a management conversation. Feedback only creates value while people still have an opportunity to improve their work. The best managers are remarkably consistent about explaining what should continue, what should change, and how those changes can be made. Employees rarely become frustrated because they receive honest feedback. They become frustrated because they receive none until it is too late to be useful.

The third factor is meaning. I have never met anyone who became excited because another task moved from “In Progress” to “Done.” People become engaged when they understand why that task matters, who benefits from it, and how it contributes to something larger than their individual workload. Most professionals are perfectly capable of handling difficult work, tight deadlines, and ambitious goals. What gradually drains motivation is spending months working on activities that appear disconnected from any meaningful outcome.

Autonomy matters just as much. Organizations spend months recruiting intelligent, experienced professionals and then surround them with approval chains, mandatory meetings, reporting structures, committees, governance boards, and endless requests for alignment. Eventually, every decision becomes somebody else’s responsibility. A few months later, leadership announces a company-wide initiative to improve innovation. The irony is difficult to miss. Innovation rarely disappears because employees suddenly become less creative. More often, it disappears because organizations become remarkably efficient at preventing creativity from turning into action.

There is another responsibility that receives far less attention because it is neither glamorous nor inspirational. Managers often spend enormous amounts of time searching for new ways to motivate people while accepting broken processes, conflicting priorities, unnecessary meetings, technical debt, poor communication, and organizational politics as unavoidable parts of corporate life. Yet these obstacles quietly consume far more energy than any motivational speech could ever restore. Sometimes the highest-performing manager is not the one who inspires the team the most. It is the one who systematically removes the obstacles that prevent talented people from doing the work they were hired to do.

Money still has an important role. It attracts talented people. It helps retain them. It can reward exceptional achievements, especially when results are measurable and directly connected to individual effort. But in product management, software development, design, research, leadership, and most other forms of knowledge work, compensation becomes progressively less effective as a performance tool once it reaches a level employees perceive as fair.

Which brings me back to the original question: “How do you improve performance if you cannot increase salaries?”

Perhaps the better question is not how to motivate people at all.

Perhaps it is this: “What is preventing already motivated professionals from doing their best work?”

The difference between those two questions may look small. In reality, it separates managers who try to energize people from managers who build environments where people no longer need constant motivation to perform well.

A manager is exhausted. They can barely concentrate. Their calendar looks like a game of Tetris designed by someone with a personal grudge. Every meeting feels heavier than the previous one. Deadlines keep moving closer, decisions take longer, and even simple conversations require more effort than they used to.

What do many companies do next? They sign the manager up for a resilience workshop.

It is a fascinating solution. Almost like trying to extinguish a fire by giving the building a course on fire safety.

The more I think about burnout, the more convinced I become that one of the biggest management mistakes is treating it as a knowledge problem. Somewhere along the way, many organizations started believing that every human problem has an educational solution. If someone is overwhelmed, teach them time management. If they are emotionally drained, teach resilience. If they struggle with priorities, send them to another workshop. The assumption is always the same: if people knew more, they would cope better.

The irony is that learning itself is demanding work. It requires attention, energy, memory, curiosity, and the ability to absorb new ideas. Those are exactly the resources that severe burnout gradually takes away. Asking someone in that condition to attend another training course is a bit like asking a marathon runner who has collapsed after kilometer 40 to spend an afternoon improving their running technique before offering them water. Nobody would seriously suggest that in sports. Yet in management, we often call it employee development.

The research I recently read makes a distinction that deserves much more attention. Burnout is not simply an individual psychological problem. It develops when there is a long-term mismatch between the person and the way work is organized. Chronic overload, endless context switching, poorly designed roles, lack of control, conflicting priorities, or promotions into levels of complexity people were never truly prepared for all contribute to the problem. None of these can be solved by adding another course to someone’s calendar.

That does not mean individuals have no responsibility. They absolutely do. Good managers learn to delegate, protect their calendars, challenge unnecessary meetings, escalate issues early, and admit when they have reached their limits. But personal responsibility should never become an excuse for organizational irresponsibility. If the environment keeps producing the same pressure every day, teaching people to breathe differently does not remove the weight sitting on their shoulders. It simply makes them carry it a little more quietly.

Interestingly, we already know this principle from product management. When a product repeatedly fails, experienced teams rarely conclude that users need another training session. They investigate the system. Was the product designed correctly? Were the incentives wrong? Did we create unnecessary friction? Did our assumptions turn out to be false? Somehow, when the subject changes from products to people, many organizations completely reverse the logic. The system remains untouched, while the human being becomes the object that needs fixing.

Another observation from the paper is equally important. Severe burnout can eventually resemble clinical depression so closely that distinguishing between the two requires proper medical assessment. Medication may become necessary if clinical depression develops, but medication alone cannot remove excessive workload, poor leadership, impossible expectations, or dysfunctional organizational design. Treating only the symptoms while leaving the environment unchanged is unlikely to produce lasting recovery.

Perhaps this explains why burnout remains so difficult to address. Organizations naturally prefer solutions that fit existing processes. Buying a training program is straightforward. Adding another position to the team is expensive. Redesigning responsibilities is politically complicated. Admitting that someone was promoted without enough support is uncomfortable. Canceling half the recurring meetings may feel almost revolutionary. One option ends with certificates and smiling photos. The other requires leaders to admit that the system itself needs to change.

What strikes me most is that prevention receives remarkably little attention because it is almost invisible. Nobody celebrates the manager who never burned out because their workload was realistic, priorities were clear, and they had enough authority to match their responsibility. There are no awards for crises that never happened. We tend to notice burnout only after someone collapses, not when good management quietly prevents it from happening in the first place.

Maybe that is why we continue investing so much effort in making people stronger instead of making organizations healthier.

The uncomfortable question for leaders is not, “How do we make burned-out managers more resilient?”

It is, “What have we built that requires so much resilience just to survive another week?”

For years, the IT world had a simple mantra: Move fast and break things. Today, we’ve replaced it with another one that sounds much more responsible: Just build an MVP. Somewhere along the way, “start small” stopped being one useful tool among many and became almost a moral principle. Suggest spending six months building something before showing it to users, and someone will inevitably remind you that “this isn’t very Lean.” It’s an interesting shift. The same people who insist that every product should be an MVP would probably think twice before boarding an aircraft whose navigation system was developed the same way.

The problem is not the idea of an MVP itself. Quite the opposite. Some of the best products I’ve worked on started exactly that way. We had a hypothesis, we knew we didn’t have all the answers, and the fastest way to learn was to put something useful in front of real users. They surprised us, challenged our assumptions, and often took the product in directions we hadn’t anticipated. That is exactly what an MVP is supposed to do.

But over time, many organizations quietly stopped asking why they were building an MVP. It became the default answer rather than a conscious decision. Every project, regardless of its nature, was expected to follow the same playbook. New recommendation engine? MVP. Internal workflow? MVP. Authentication platform? MVP. Core publishing infrastructure? Also MVP. At that point, we’ve stopped applying a methodology and started following an ideology.

The mistake is subtle but important. We tend to think that every project carries the same kind of uncertainty, when in reality they don’t. Sometimes the biggest unknown is whether users actually want what we’re building. Sometimes the real challenge is whether the technology will work reliably under real conditions, whether it can scale, whether it can survive failures, or whether it can be trusted at all. Those are fundamentally different problems, yet we often reach for exactly the same delivery approach.

Take something as simple as a new dashboard. If users don’t understand it or don’t find it useful, the consequences are relatively small. You learn something, improve it, and release another version. The cost of being wrong is low, while the value of learning quickly is extremely high. That is exactly the environment where iterative development shines. The product becomes better because people use it before it’s finished.

Now compare that with replacing your authentication system, your payment platform, or the infrastructure that allows journalists to publish safely in heavily censored countries. Here, a partially working solution doesn’t create partial value. It creates partial trust. And trust is remarkably difficult to recover once you’ve lost it. A bridge that reaches halfway across the river isn’t an MVP. It’s simply an unfinished bridge. Some systems become valuable only when they work as a complete system.

I think this is why experienced product leaders often sound more cautious than people early in their careers. It’s not because they’ve become less Agile or less innovative. They’ve simply learned that not every uncertainty should be exposed to customers. Sometimes the smartest iteration happens long before the first public release. Technical prototypes, architecture experiments, internal pilots, migration rehearsals, dark launches, and parallel systems. These are all forms of iteration as well. Users may not see them, but the organization is constantly learning.

There is also an irony that doesn’t get discussed often enough. The companies we admire for moving incredibly fast are frequently the same companies that spend years investing in things nobody outside the organization will ever notice. We see the new feature appear overnight and assume it was built overnight. What we don’t see are the years spent building internal platforms, deployment pipelines, observability, testing frameworks, migration tools, and engineering practices that make those rapid releases possible. To outsiders, it looks like speed. Inside the company, it often looks like patience.

Over the years, I’ve found that one question has become much more useful than asking whether something deserves an MVP. Instead, I ask what we’re actually trying to learn. If the biggest uncertainty is about people — their needs, habits, priorities, or willingness to adopt something — then expose the product early and learn from reality. But if the biggest uncertainty lies in technology, resilience, security, compliance, or trust, then exposing customers to that uncertainty may be exactly the wrong thing to do. Learn internally first.

Perhaps that’s the distinction we should be making more often. The goal is not to release everything as quickly as possible, nor is it to hide in development for years chasing perfection. The goal is to expose uncertainty to the right audience at the right moment. Users should help us discover whether we’re solving the right problem. Engineers should help us discover whether we’ve built the solution correctly. Mixing those two kinds of learning is where many expensive mistakes begin.

Maybe the real lesson is that there is no universally “Agile” way to build products. There is only a disciplined way to manage uncertainty. The best product organizations aren’t the ones that always ship first or always polish everything before launch. They’re the ones that know which risks can safely be explored in public. And which ones absolutely should not.

Every organization eventually starts looking for a “strong leader.”

A stronger Head of Product. A stronger Operations Director. A stronger Engineering Manager. Sometimes even a stronger CEO. The assumption is almost always the same: somewhere out there is a person whose leadership is an intrinsic quality, like intelligence or height. Bring that person into the company, and performance will improve almost automatically. If things later go wrong, the explanation is equally simple: we hired the wrong person.

It is an attractive belief because it turns a complex organizational problem into a recruitment problem. Finding the right leader feels much easier than changing an organization. It also creates compelling business stories. We love reading that someone “transformed the company” or “rebuilt the culture.” We rarely hear the less glamorous version: the company happened to reach the right stage of growth, the market shifted in its favor, the team around the leader complemented their weaknesses, and the organization was finally ready for changes that had previously failed. The second explanation is usually much closer to reality. It is simply much harder to fit into a headline.

Interestingly, management science has spent nearly a century trying to identify the characteristics of universally effective leaders. Researchers searched for the perfect combination of intelligence, confidence, charisma, determination, and dozens of other traits. The result was surprisingly disappointing. There are qualities that certainly help someone become a leader, but no combination consistently predicts success across different organizations, teams, and situations. Over time, researchers from organizational psychology, leadership studies, and business management all arrived at a remarkably similar conclusion: leadership effectiveness is not a property of a person. It is a property of the relationship between a person and their environment.

Once you start looking through that lens, many familiar business stories suddenly make much more sense. A Head of Product who built an outstanding startup may struggle inside a heavily regulated enterprise. An operations leader praised for introducing discipline into a global corporation may become a serious obstacle in a young company that survives through speed and experimentation. A manager who earns promotion by personally solving every difficult problem often becomes the bottleneck once the organization grows to a size where delegation matters more than individual heroics. The person did not necessarily change. The context did.

This is why I have become increasingly skeptical whenever someone tells me they are looking for a “strong leader.” My first question is always: strong for what? Strong for building something new, or for making an existing organization more predictable? Strong for rapid growth, or for operational excellence? Strong for leading experts who value autonomy, or for stabilizing a fragmented organization that needs structure? Without understanding the context, the word “strong” tells us remarkably little.

There is, however, one place where I think many academic models stop a little too early. They often describe leadership as finding the right match between a person and a situation. In reality, organizations never stop changing. Markets evolve. Teams grow. Products mature. Technologies reshape entire industries. A leader who is perfectly suited to today’s challenges may become tomorrow’s constraint. The real question, therefore, is not whether someone fits the current context, but whether they can evolve as quickly as the context itself.

Perhaps that is the rarest leadership capability of all: not charisma, not confidence, not decisiveness. The ability to recognize that the game has changed before everyone else does, and to change yourself before the organization starts looking for someone else.

Maybe that is why I no longer believe in strong leaders as permanent categories. I believe in strong matches between people and situations. Some of those matches last for years. Others last for only a single stage in an organization’s life. The best leaders are not those who remain unchanged while the world moves around them. They are the ones who keep becoming the right leader for the next chapter.

There is a strange corporate belief that if something is important enough, it must fit into a quarterly KPI. Leadership development? Measure it. Learning culture? Measure it. Managerial maturity? Ideally, convert it into revenue impact by the end of the year, add a decimal point, and put it in a slide deck. Because nothing says “we understand human development” quite like asking a feedback training to prove its contribution to annual revenue.

This is where the current disappointment with Learning and Development (L&D) often begins. Companies invest in corporate universities, leadership programs, business schools, coaching sessions, online academies, feedback workshops, resilience trainings, strategic thinking modules, and many other carefully branded efforts to make adults behave slightly better at work. Yet after all of this, a senior manager still cannot give normal feedback, delegate without anxiety, make a decision without forming a committee, or have a difficult conversation without turning it into either silence or theater. So the question appears, quite naturally: what exactly did we pay for?

Some of this criticism is fair. Many L&D functions helped create their own trap. Too often, learning became an activity factory, with success measured by completed courses, training hours, attendance, satisfaction scores, internal NPS, and the famous “participants found the session useful.” Useful for what, exactly, is sometimes left for future historians to investigate. When a function reports primarily on activity, it should not be surprised when the business asks whether that activity has any real value.

But when companies face a complex problem, they often simplify it until it becomes wrong. The new demand becomes: prove business impact. Not through changed behavior, better management practices, stronger succession pipelines, or lower avoidable attrition. No, show us the effect on revenue. Directly. Preferably this quarter. On paper, the impulse is healthy. Nobody wants L&D to be a black hole of budget, reporting “insights” and “engagement” while the organization keeps producing the same weak managers with better certificates. It is reasonable to ask whether learning changes anything.

The problem is that revenue is not a clean metric. Revenue reflects the market, the product, the price, the sales team, the brand, the economy, competitors, timing, luck, and sometimes the mysterious corporate force known as “we have no idea why this worked, but please build a framework around it.” Trying to isolate the exact revenue contribution of feedback training is not measurement. It is performance art with spreadsheets. The result is fake precision: a model appears, a number appears, someone writes that the program contributed 2.8% to revenue growth, nobody truly believes it, and everyone still copies it into the report. And the machine continues.

The irony is that this pressure pushes L&D in exactly the wrong direction. If you ask learning teams to prove immediate financial impact, they will optimize for what can be attributed quickly: short-term skills, visible activity, easy before-and-after metrics, and programs that produce numbers fast enough to survive the reporting cycle. But adult development does not work that way. A person does not become a mature leader because they attended a workshop on Tuesday and received a PDF on Wednesday. A manager may know how to give feedback yet still avoid it. They may understand delegation yet still micromanage. They may repeat the word “strategy” while spending every week in operational panic.

The problem is often not a lack of information. It is habits, fear, status, incentives, organizational politics, avoidance, culture, and the hidden reward system that says one thing in leadership principles and another in promotion decisions. This is why leadership development is slow, distributed, and inconvenient. It appears in different conversations, better decisions, fewer unnecessary escalations, stronger teams, more capable successors, and managers who can finally hold complexity without immediately turning it into a dashboard. Naturally, this makes it difficult to report in a neat quarterly table.

We demand that L&D speak the language of the execution machine. Then we complain that it no longer develops people but produces learning theater. The medicine is judged by the metric of the disease. Here is the larger problem: for years, many companies avoided the hard work of developing leaders internally because there was always a convenient alternative. Hire someone from the market. Did not grow your own? Buy someone else’s. This worked for a while, or at least it looked like it worked. But everyone was buying from the same limited pool. One company’s “great external hire” was often another company’s “we failed to retain this person.” The total supply of mature leaders did not magically expand. It just moved between LinkedIn announcements.

At some point, the market stops solving for what the organization refuses to build. This is already evident. Companies complain that strong leaders are hard to find. Candidates complain that companies want impossible combinations of maturity, speed, loyalty, transformation experience, political sensitivity, technical literacy, emotional intelligence, and low compensation expectations. Both sides are disappointed, which usually means the system is working exactly as designed, just no longer in our favor.

So no, the real issue is not whether L&D has the right KPI. The real issue is whether companies still know how to create the conditions in which adults can grow into better leaders. That requires more than courses. It requires serious managers above them, real feedback, space to think, consequences for poor leadership behavior, promotion criteria that reward maturity rather than visibility alone, and an organization that does not outsource every uncomfortable developmental task to the training department.

L&D should absolutely be accountable, but not for pretending a workshop directly drove revenue. It should be accountable for building organizational capability: better managers, stronger decision-making, healthier leadership pipelines, and fewer costly failures caused by promoting people faster than they developed. The problem is not that development cannot be measured. The problem is that we often measure it in ways that destroy the very thing we claim to value. And then, with impressive seriousness, we call it management.

There is a comforting dream behind most goal-setting exercises. We sit in a room, open a document, and write down what we want to achieve. Then we break it into priorities, initiatives, milestones, owners, dependencies, risks, mitigation plans, and, if the organization is mature enough, at least three tables that say roughly the same thing in different formats.

For a brief moment, it feels like control. Do A, get B. Do B, get C. If the result does not happen, the explanation is ready: the goal was not clear enough, ownership was not strong enough, the roadmap was not detailed enough, or the alignment meeting did not produce enough alignment. So naturally, we add another layer of detail, because apparently the only thing standing between us and a predictable universe is a better spreadsheet.

I have been thinking about this through the work of Ilya Prigogine, the Nobel Prize-winning chemist and physicist who studied complex systems far from equilibrium. His work on dissipative structures showed something deeply uncomfortable for anyone who enjoys clean planning: in complex systems, order does not simply defeat chaos. Order often emerges from chaos. These systems are not merely complicated machines with missing documentation. They are unstable, adaptive, and open to several possible futures.

At certain points, a small fluctuation can change the system’s overall direction. The past does not mechanically produce the future. The system answers back. This is not a perfect metaphor for business, of course. Organizations are not chemical reactions. Product teams are not molecules, although on some days the difference is less obvious than we would like. But as a way of thinking, it is useful.

Many organizations still set goals as if they operate in a stable, obedient environment. As if the market will politely stay still while the annual plan is executed. As if the user behavior we observed last year will remain largely valid this year. As if the competitive landscape will wait for Q4, when we planned to review the strategy.

Reality is rarely that well-mannered. A competitor appears from a direction no one had on the slide. A technology that was supposed to be “interesting in three years” becomes normal in eight months. A stakeholder changes. A team loses key people. A regulatory risk appears. A user behavior we thought was marginal suddenly becomes mainstream. Or, more quietly, an unexpected conversation opens a much better path than the one we spent months planning.

This is the part where traditional goal-setting often goes wrong. Not because goals are useless. They are not. The problem is not a lack of goals. The problem is pretending that goals give us control over things we can only influence.

A good goal creates direction. It helps people choose. It gives teams a shared language for trade-offs. It says: this is what matters, this is what we are trying to change, and this is the effect we believe is worth pursuing. A bad goal pretends to be a contract with the future. And the future, as usual, did not sign it.

In product work, this distinction matters a lot. A roadmap is often treated as a delivery promise, but in a complex environment it should be closer to a structured hypothesis. We believe these problems are important. We believe these solutions may work. We believe this sequence makes sense based on what we know now. The key phrase is “based on what we know now,” not “based on what we hope will remain true forever.”

The greater the uncertainty, the less useful it is to worship the original plan. Yet this is exactly what many organizations do. When reality becomes less predictable, they respond by demanding more precision from the plan: more milestones, more reporting, more governance, and more status updates explaining why the world has failed to comply with the roadmap. This is not management. This is administrative weather control.

The better question is not “How do we remove uncertainty?” We cannot. The better question is: “Which parts of this system can we influence, and where do we need to stay alert enough to adapt?” That requires a different kind of discipline. Less theatrical certainty and more honest observation. Less obsession with predicting the exact output and more attention to signals. Less punishment for changing course when the evidence changes, and more ability to distinguish between abandoning a goal and updating a hypothesis. This is where many teams struggle. Not because they lack ambition, but because they confuse flexibility with weakness. They think adaptation means giving up. But in reality, adaptation is often the only serious form of execution. Rigid plans look strong in presentations. Adaptive systems survive outside them.

The irony is that the best outcomes in our lives and work often come from things we did not fully plan. A meeting that was not supposed to matter. A side conversation after the official discussion ended. A small experiment no one expected much from. A person who entered the picture late and changed the whole direction. A constraint that forced a better idea. But these outcomes are not pure luck.

Chance opens the door. Preparedness notices it. Competence uses it. This is why the next evolution of goal-setting should not be about abandoning goals and becoming passive observers of chaos. That would be just another fashionable excuse, and we already have enough of them.

The evolution should be about intellectual honesty. We need goals, but we should stop pretending that all goals are control mechanisms. Some are direction markers. Some are bets. Some are learning tools. Some are useful only until the system gives us a better answer.

The mature approach is not to say: “Here is the plan, and reality must follow.” The mature approach is to say: “Here is our direction, our current hypothesis, what we can influence, what we need to watch, and how we will know that the system is telling us something important.” It is less comforting than a beautiful annual plan, but it has one advantage. It is closer to how reality actually works.

A few weeks ago, I attended a workshop on Belbin’s Team Roles. You probably know the concept, or at least the general idea behind it. Every effective team needs different types of contributions. Some people generate ideas, some turn ideas into practical plans, some challenge inertia, some analyze risks, some maintain relationships, some bring deep expertise, and some make sure the work is actually finished rather than becoming another beautifully designed slide in the corporate museum of unfinished intentions.

So far, so good.

Then we came to the part where the idea of a team without a leader appeared. This is where my inner corporate heretic politely raised his hand.

Not because I believe every team needs a boss. Quite the opposite. The best leaders are not always the loudest in the room, and they are definitely not the ones who measure leadership by how many follow-up messages they send after every meeting. A leader is not someone whose main function is to ask, “Any updates?” across five different communication channels. That is not leadership. That is calendar-based anxiety with admin permissions.

But I do believe every serious team needs leadership. There is a difference. A boss controls; a leader enables. A boss wants to be at the center; a leader creates conditions in which other people can do their work. A boss treats the team as a delivery machine; a leader understands that the team is a system of people, roles, expectations, conflicts, priorities, constraints, external pressure, unclear requirements, and the occasional stakeholder who enters the room carrying a “small request” that somehow requires three months of engineering work.

Belbin’s model is useful because it reminds us that teams need different types of contributions. A team made only of idea generators may produce an impressive number of concepts and almost no output. A team made only of implementers may deliver efficiently in the wrong direction. A team made only of evaluators may analyze the project to death. A team made only of relationship-builders may create a safe and friendly environment where nobody wants to ask why the deadline was missed. Balance matters, and the model clearly shows why.

But balance does not eliminate the need for responsibility.

This is where I struggle with the romantic idea of leaderless teams. It often sounds appealing in workshops, especially when everything is theoretical, the coffee is still hot, and no real stakeholder is waiting for an answer by the end of the day. In theory, the team self-organizes. In theory, decisions emerge naturally. In theory, people align around the best argument. In theory, everyone owns the result. Then reality arrives, usually without reading the workshop handout first.

A deadline slips. Two departments want opposite things. A senior stakeholder pushes for a shortcut. A technical risk is discovered late. A conflict within the team stops being a “healthy disagreement” and becomes a polite civil war waged through Jira comments. Suddenly, “shared ownership” starts to look suspiciously like “nobody is actually responsible.”

This is the moment when teams need more than roles. They need someone who can say: “Here is the decision. Here is why. Here is what we will do next. And I own the consequences.” That person does not need to dominate the team. They do not need to have all the answers. In fact, if they think they have all the answers, they are likely the problem. But someone must own the frame.

Someone must protect the team from noise, represent the team to the outside, resolve conflicts when good intentions fall short, and connect internal work to external reality. Someone must ensure that autonomy does not become isolation and that collaboration does not become permanent consensus-seeking. This, to me, is leadership. Not command and control. Not corporate theater. Not “let’s circle back” as a lifestyle. Leadership is the function that enables all other functions to work.

A strong leader enables the Plant to bring ideas without letting the team lose itself in abstract creativity. They help the Implementer turn plans into action without reducing every discussion to a checklist. They let the Monitor Evaluator challenge assumptions without creating a culture of permanent skepticism. They support the Teamworker without making harmony more important than truth. They value the Specialist without allowing expertise to become a private kingdom. Good leadership does not replace team roles. It makes them usable.

This is why the phrase “leaderless team” often feels misleading to me. Many teams that call themselves leaderless still have leadership. They just do not call it that. Someone coordinates. Someone facilitates. Someone exerts influence. Someone breaks deadlocks. Someone represents the group. Someone becomes the person others look to when things get difficult. The title may disappear, but the function remains.

And when the function disappears, the consequences are usually not very modern or progressive. They are just messy.

The strongest teams I have seen do not rely on a leader for every small decision. That would be slow, exhausting, and frankly insulting to capable professionals. Strong teams make many decisions themselves. They challenge each other. They draw on expertise. They do not wait for permission to breathe. But they also know where accountability lies. They know who protects the mission when priorities collide. They know who owns escalation. They know who can make the unpopular decision when all available options are imperfect. They know who carries the responsibility when the beautifully balanced team roles are not enough.

So maybe the real question is not whether teams need a leader. The better question is what kind of leader the team needs. If the answer is “someone who controls every step,” the team is probably not mature enough, or the leader is not. If the answer is “nobody, because we are all adults here,” that may work for a while, especially while things are calm. But when pressure comes, leadership stops being a job title and becomes infrastructure.

And like most infrastructure, nobody appreciates it when it works. They only notice when it is missing.

These days, when a new project lands on our desk, a stakeholder arrives with a difficult question, or a strategy discussion starts going in circles, many of us have developed the same reflex.

Before we call a colleague, before we challenge our own assumptions, and sometimes even before we spend five minutes thinking about the problem ourselves, we open ChatGPT.

• “Can you research this?”

• “Can you validate this idea?”

• “What am I missing?”

• “How would you approach this?”

Sound familiar? It certainly does to me.

To be clear, this is not a criticism. In many ways, it is perfectly rational behavior. We have access to a tool that can summarize information, compare alternatives, challenge assumptions, and produce a reasonably intelligent response in seconds. Refusing to use it would be as strange as refusing to use Google twenty years ago.

What interests me is not the tool itself. It is what this new habit reveals about how our relationship with research, analysis, and decision-making has been changing for years, long before AI arrived.

For most of my career, research was expensive. If you wanted to understand a market, a product, a competitor, or an audience, you had to work for it. You collected reports, interviewed users, studied competitors, reviewed data, argued with colleagues, and slowly pieced together a picture from incomplete information. The challenge was not interpretation. The challenge was access. There were always more questions than answers.

Today, the situation is almost the reverse. Search engines have dramatically lowered the cost of finding information. Social media has multiplied the number of available signals. Analytics platforms have given us dashboards for everything. And now artificial intelligence can summarize, compare, analyze, and explain in seconds what once took hours or days. Access is no longer the bottleneck. Information is no longer scarce. Answers have become abundant.

That sounds like progress, and in many ways it is. We can learn faster, validate assumptions more quickly, and explore topics that would have required enormous effort just a decade ago. Yet abundance creates a different problem. When answers become cheap, we begin to confuse collecting information with understanding it. The ability to retrieve knowledge starts to replace the harder task of deciding what that knowledge actually means.

This distinction matters more than many people realize. Research and thinking are related activities, but they are not the same. Research gathers evidence. Thinking evaluates it. Research identifies patterns. Thinking questions whether those patterns are real. Research helps us understand what happened. Thinking tries to understand why it happened and what might happen next. One produces information. The other produces judgment.

In product management, leadership, consulting, journalism, and strategy, judgment has always been the scarce resource. Information was never the final product. Insight was. Two people can look at the same data and reach completely different conclusions. One sees a trend. The other sees noise. One sees a user problem. The other sees a measurement issue. One discovers an opportunity. The other discovers a risk. The difference is rarely access to information. The difference is interpretation.

The irony is that artificial intelligence did not create this challenge. It merely accelerated a trend already well underway. Long before large language models appeared, many organizations had quietly begun rewarding certainty over curiosity. Executives wanted forecasts. Managers wanted metrics. Recruiters wanted keywords. Schools wanted correct answers. PowerPoint presentations wanted conclusions. Very few systems rewarded anyone for saying, “I don’t know yet, but I think we’re asking the wrong question.”

Over time, uncertainty became something to eliminate as quickly as possible. Open questions were treated as problems waiting to be closed. The professional who sounded certain often appeared more competent than the one still exploring possibilities. Artificial intelligence happens to be exceptionally good at operating in such an environment. It produces answers instantly, presents them confidently, and never hesitates. Most importantly, it never appears uncomfortable with ambiguity.

That is precisely why it is so useful and why it warrants a certain amount of caution. The danger is not that AI makes people less intelligent. The danger is that it can create the impression that analysis has occurred when only information gathering has taken place. A beautifully structured answer can feel like understanding. A polished summary can feel like expertise. A generated recommendation can feel like strategic thinking. Sometimes it is. Sometimes it is simply a very convincing starting point.

Anyone who has spent enough time in large organizations has seen this phenomenon before AI arrived. We have all read reports filled with data yet lacking insight. We have all attended meetings where everyone discussed metrics while no one challenged assumptions. We have all seen strategy decks that answered dozens of questions except the one that actually mattered. The technology changed. Human behavior did not.

This is why I suspect some of the most valuable professional skills are becoming more important, not less. The ability to formulate a good question. The ability to identify hidden assumptions. The ability to recognize contradictions. The ability to sit with uncertainty long enough for a deeper understanding to emerge. These skills become more valuable when answers are abundant, not less.

The future probably belongs neither to those who reject AI nor to those who outsource their thinking to it. It belongs to those who learn to use it without surrendering their judgment. The best professionals will use artificial intelligence the same way previous generations used search engines, calculators, spreadsheets, and databases, as a tool that extends capability, not as a substitute for reasoning.

What remains uniquely valuable is not access to information. Machines are already better at that. It is the ability to decide what deserves attention, what deserves skepticism, and what deserves belief. It is the ability to recognize when a seemingly perfect answer is addressing the wrong question. It is the ability to connect ideas across domains and create something genuinely new.

Ironically, these are not new skills. They were valuable before Google, remained valuable during the age of dashboards and analytics, and will remain valuable long after today’s AI tools are replaced by something faster, smarter, and more impressive.

Technology keeps lowering the cost of finding answers. Human value increasingly comes from knowing which answers matter.

And perhaps even more importantly, from knowing which questions are still worth asking.

That pause between receiving an answer and accepting it as truth may become one of the most valuable professional skills we have left.

Let’s start with a confession.

Most of us have taken part in a strange corporate ritual. Every year, managers and employees gather in meeting rooms or on video calls to set goals. Those goals are carefully aligned with department objectives, which are aligned with company objectives, which are aligned with strategic priorities, which are aligned with another presentation created somewhere several organizational layers above reality. Everyone nods. Everyone agrees. Everyone enters the goals into the system. The process looks rational, structured, and professional. Then the meeting ends, people return to their desks, and something interesting happens: most of them go back to pursuing their own goals.

Not because people are lazy. Not because they are disloyal. Not because they secretly want the company to fail. They do it because they are human. The uncomfortable truth behind many performance management systems is that they rest on an assumption that sounds reasonable but rarely holds up to reality. The assumption is that if company goals are communicated clearly, measured carefully, and tied to incentives strongly, employees will naturally adopt them as their own. In practice, people do not set aside personal ambitions, interests, concerns, and priorities simply because a new quarterly objective appears in a slide deck.

For decades, companies have treated motivation as a relatively simple engineering problem. Increase compensation, improve benefits, add recognition programs, introduce employee-of-the-month awards, and organize team-building activities, and motivation should increase accordingly. The model is attractive because it is easy to understand and even easier to measure. It allows organizations to think about people the same way they think about budgets, processes, and operational metrics. The difficulty is that human beings are considerably more complicated than spreadsheets.

Money matters, of course. Anyone claiming otherwise is usually either very wealthy or trying to persuade someone else to work for less. But money explains far less than organizations often assume. A salary increase can mean security to one employee, status to another, independence to a third, and recognition to a fourth. Meanwhile, a highly curious engineer may value learning opportunities more than a larger bonus. An ambitious product manager may care more about influence and ownership than about another corporate benefit. A senior specialist may willingly sacrifice compensation growth in exchange for greater autonomy. The company believes it is sending a clear motivational signal. The employee receives a message in a language they do not particularly care about.

This is where many performance management systems begin to struggle. The problem is not that employees reject company goals. Rather, employees filter every company goal through a personal lens before deciding how much effort to invest. When leadership announces a strategic initiative, people do not immediately think about shareholder value, organizational efficiency, or market positioning. They ask different questions. Will this help me grow? Will it make my work more interesting? Will it increase my influence? Will it improve my reputation? Will it create opportunities for me? These questions are not selfish. They are completely rational. Every employee, from an intern to a senior executive, translates organizational priorities into personal meaning before deciding how much energy to commit.

What makes this particularly relevant today is the changing nature of work. Many traditional management approaches were developed when organizations primarily coordinated large numbers of people performing standardized tasks. Modern organizations increasingly depend on knowledge workers whose primary tools are judgment, expertise, creativity, and problem-solving. These people often have strong opinions, strong professional identities, and a reasonably accurate understanding of their market value. They have access to remote opportunities, international employers, consulting work, startups, and professional networks that barely existed a generation ago. They are not trapped in a single organization. They choose to remain there.

That shift changes the entire management equation. In the past, companies often relied on compliance. Today, they increasingly depend on commitment. Compliance can be enforced through rules, reporting structures, and oversight. Commitment is different. It appears when people see a meaningful connection between what the organization wants and what they personally want. It cannot be demanded. It cannot be purchased directly. It has to be created.

This is why I have become increasingly skeptical whenever I hear discussions focused exclusively on company goals. The question is not whether company goals matter. Of course they do. The question is whether leaders understand that those goals compete for attention with dozens of other motivations already present in every employee’s mind. Career ambitions, intellectual curiosity, desire for recognition, financial security, family responsibilities, personal values, and simple quality of life all sit at the same table. Company objectives are merely another participant in that conversation.

The irony is that the strongest organizations are often not the ones that demand the highest level of commitment to corporate goals. They are the ones that invest the most effort in understanding what their people actually want. Instead of trying to convince employees to care about business objectives for their own sake, they find ways to align business success with personal success. They create environments where professional growth supports organizational growth, ownership supports accountability, learning supports innovation, and individual ambition contributes to collective outcomes.

That approach sounds almost obvious once stated aloud. Yet many organizations continue to act as though employees should naturally prioritize corporate objectives over their own interests. The reality is exactly the opposite. People will always pursue what matters to them personally. The real challenge of leadership is not fighting that fact. It is ensuring that when people move toward their own goals, they help move the organization forward as well.

Because in the end, people do not come to work every morning to achieve company goals. They come to achieve their own. The best companies simply make those two journeys look like the same road.

A few weeks ago, I caught myself doing something ridiculous.

I was waiting for a meeting to start, casually scrolling through LinkedIn. One person had just become a VP. Another had joined a well-known technology company. Someone else was announcing a successful startup exit. A familiar face was sharing photos from a London conference. Another was celebrating ten years in leadership. Amid all the promotions, milestones, keynote speeches, and carefully written reflections on success, I suddenly felt oddly behind.

The funny part was that nothing in my real life had changed.

I was still the same person I had been fifteen minutes earlier. My experience had not disappeared. My accomplishments had not become any less valuable. My team had not suddenly stopped delivering results. Objectively, everything was exactly the same as it had been before I opened the app. Yet subjectively, something had shifted. The moment I immersed myself in a stream of other people’s achievements, my own career began to feel smaller. Not unsuccessful. Not disappointing. Just somehow less impressive than it had felt before.

That reaction is surprisingly common, and psychology offers a straightforward explanation. More than seventy years ago, psychologist Leon Festinger described social comparison as a fundamental way people evaluate themselves. We rarely assess our success in absolute terms. We assess it relative to others. The challenge is that our brains evolved in environments where “other people” meant family members, neighbors, coworkers, classmates, and a handful of local success stories. Human beings were not designed to compare themselves against thousands of highly curated examples of achievement before their first cup of coffee.

For most of history, comparison occurred within relatively small, stable communities. You knew the successful people around you, and you knew their struggles. You knew who got promoted after years of hard work. You knew who lost a job before finding a better one. You knew who looked successful yet was constantly stressed, and who seemed ordinary yet was quietly thriving. Real life provided context. Success and failure coexisted in the same picture.

Social media has changed the picture entirely.

Instagram is often criticized for fostering unrealistic expectations about beauty, lifestyle, travel, and relationships. LinkedIn does something remarkably similar, but in a professional context. Instead of showcasing perfect vacations and flawless bodies, it highlights promotions, awards, keynote speeches, funding announcements, successful launches, prestigious new jobs, and carefully packaged lessons from triumphant career journeys. The content may look more professional, but the psychological mechanism is almost identical.

What makes LinkedIn particularly effective is that it feels objective. Instagram users generally understand that they are looking at a highlight reel. The platform has become synonymous with curation. LinkedIn, however, presents itself as a professional environment. The stories feel credible, useful, and relevant. We tell ourselves that we are learning about the market, staying informed, or building our network. Yet beneath that rational explanation, our brains are still processing a continuous stream of social status signals.

And status signals are powerful.

When someone your age becomes a Vice President, joins a prestigious company, launches a successful business, or speaks at a major conference, your brain rarely pauses to analyze the full context. It does not calculate the probability of that outcome. It does not consider how many candidates were rejected, how many failures preceded the success, how much luck was involved, or what sacrifices were made along the way. Instead, it performs a much simpler calculation. It notices that someone seems to be moving faster than you and immediately starts measuring the distance between their position and yours.

The irony is that this phenomenon often intensifies rather than diminishes as careers advance. Early in their careers, people compare themselves to colleagues or classmates. Later, they compare themselves to directors, vice presidents, founders, and industry thought leaders. Every promotion resolves one comparison problem and creates another. The benchmark keeps moving. What felt like an ambitious career goal five years ago becomes merely the starting point for the next round of comparison.

I have seen this repeatedly among experienced leaders. People running large teams, managing significant budgets, and shaping important products sometimes feel strangely unsuccessful. Not because they are unsuccessful, but because they spend too much time observing exceptional careers. When your daily feed is filled with executives from Google, Meta, OpenAI, Stripe, or the latest unicorn startup, your sense of what counts as a “normal” career gradually becomes distorted. Statistically rare outcomes start to feel commonplace. Exceptional success begins to look ordinary. Once that happens, perfectly respectable achievements can start to feel inadequate.

The more I think about it, the more I believe social media is changing not only how we evaluate careers but also how we define them.

Many professionals unconsciously design careers that look impressive when summarized in a LinkedIn post. Visibility competes with impact. Public recognition competes with expertise. Activities that attract attention often seem more valuable than those that deliver long-term results. A conference keynote looks more impressive online than two years spent improving an organization’s culture. A startup launch creates a better headline than a decade of patient operational excellence. A personal brand is easier to showcase than deep expertise.

The problem is not that visibility, speaking engagements, or personal branding are bad. They can all be useful and valuable. The problem arises when visibility becomes the scorecard itself. At that point, we stop measuring success by the quality of our work and start measuring it by the quality of the story we tell about our work.

Some of the most effective leaders I have met would barely show up on LinkedIn. They rarely post, do not speak at conferences, and have no interest in building a personal brand. Yet they consistently build strong teams, develop future leaders, solve difficult organizational problems, and deliver meaningful results. Their organizations value them immensely. The algorithm simply does not.

That distinction matters because LinkedIn is not the labor market. It is the showroom of the labor market. It contains valuable information, useful connections, and genuine opportunities, but it also systematically overrepresents success and underrepresents struggle. We see promotions but not disappointments. We see outcomes but not uncertainty. We see victories but rarely the years of ambiguity that preceded them.

Perhaps the healthiest response is not to reject professional social media but to understand what it actually is. A showcase is useful as long as we remember it is just a showcase. The moment we mistake it for reality, comparison becomes inevitable, and dissatisfaction follows close behind.

Careers are lived in the messy, uncertain, unglamorous world of everyday work. They are built on difficult decisions, failed projects, uncomfortable conversations, occasional luck, and long stretches of persistence. None of that makes for particularly engaging content. Most of it never appears in a LinkedIn post.

Yet those invisible parts are where careers are truly made. The algorithm edits them out. Reality does not.

There are two management philosophies that sound absolutely brilliant on LinkedIn: “The manager should not constantly ask when the task will be done” and “The manager has three duties: explain the task, provide resources, and shut up.”

People love these quotes because almost everyone who has worked in a large organization has experienced the opposite. Endless status meetings. Daily “quick syncs” that somehow stretch to an hour. Managers who believe productivity only exists if they can visibly observe it in real time. Entire departments operating like anxious airport security, repeatedly asking whether everyone still has their boarding pass.

So naturally, the fantasy is appealing. Hire smart adults, explain the objective clearly, give them resources, stop interfering, and let competent people do their jobs. In theory, this sounds not only efficient but also civilized. And to be fair, in strong teams with experienced specialists, it often works surprisingly well. Engineers, designers, editors, product people, analysts — most professionals genuinely do better work when they have enough trust, enough context, and enough uninterrupted time to think.

The problem is that these elegant management quotes quietly assume an environment that rarely lasts long. They imagine organizations as calm, rational systems where priorities are stable, communication is clear, dependencies are visible, and everyone shares the same understanding of urgency and success.

Reality is usually less cinematic. Real organizations are noisy systems filled with conflicting incentives, shifting priorities, half-finished transformations, unclear ownership, overloaded specialists, political sensitivities, budget pressures, legacy processes, and stakeholders who confidently approve one direction, only to change their minds three weeks later after a conference, a board meeting, or a conversation with another executive.

And this is exactly where simplistic anti-management philosophy begins to collide with operational reality.

The uncomfortable truth is that organizations do not become chaotic because managers exist. Managers exist because organizations naturally drift toward chaos if no one actively aligns them. The larger and more interconnected the system becomes, the more invisible coordination work is required simply to prevent collisions among teams, priorities, technologies, and people. A surprising amount of management is not about telling people what to do. It is about constantly reducing friction before it becomes visible to everyone else.

The irony is that the best managers often seem “hands-off” precisely because they are quietly intervening behind the scenes. They notice that two departments are heading toward incompatible deadlines long before the conflict erupts publicly. They realize that a “small technical dependency” will eventually delay five projects. They sense when leadership expectations no longer align with delivery reality, even as everyone continues to smile politely in meetings. They absorb pressure, negotiate compromises, clarify ambiguity, and translate vague executive ambition into something an exhausted team can execute without collapsing.

Most of this work is deeply unglamorous, which is probably why online management discussions favor inspirational mythology instead. The internet loves the image of the enlightened leader who empowers everyone through trust, vision, and radical autonomy. It sounds elegant. It also sounds much better than admitting that real management often involves uncomfortable follow-ups, conflict resolution, operational escalation, resource negotiations, damage control, and conversations that nobody wants to have.

Meanwhile, actual management often looks less like philosophy and more like: “Can somebody please confirm which system is considered the source of truth before three teams implement different versions of the same feature?”

Not exactly the kind of sentence people print on conference banners.

At the same time, criticism of micromanagement is completely valid. If a manager spends most of the day asking whether tasks are done, something deeper is usually broken. Either priorities are unclear, ownership is weak, communication is fragmented, the process lacks transparency, or the organization itself operates in a permanent reactive mode. Strong teams should not require constant supervision to function. Mature professionals generally do not need someone metaphorically standing behind them with a stopwatch and a clipboard.

But this is where many fashionable management quotes become misleading. The absence of micromanagement is not the same as the absence of management. A healthy organization does not emerge automatically just because intelligent people were hired. Independence without alignment eventually leads to fragmentation. Total freedom without coordination slowly produces duplicated work, incompatible decisions, missed dependencies, and strategic drift. People start optimizing locally while the organization quietly loses coherence globally.

The real role of management lies somewhere in the uncomfortable middle between control and absence. Good managers are not dictators obsessively monitoring every move. But they are also not passive motivational figures whose entire contribution ends after assigning tasks and distributing inspirational energy. Their job is to build an environment where people can operate independently most of the time while ensuring the broader system still functions coherently under stress, uncertainty, and constant change.

And perhaps the greatest irony of management is this: when it works exceptionally well, people often conclude that management was unnecessary.

Which, from a manager’s perspective, is simultaneously the highest compliment and the most dangerous illusion.

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.