She was talking about how doing business had changed.

Modern organizations have become extraordinarily good at standardization. Calls are routed efficiently, transactions follow defined workflows, decisions are documented, and service levels can be measured across thousands of interactions. There are good reasons for this. In regulated industries like mine, consistency is not simply about efficiency. Clients should be treated fairly, records should be accurate, and important processes should not depend entirely on which employee happens to answer the phone.

Scale requires systems. The problem is that customers do not experience our organizations as systems. They experience moments.

A billing issue. A confusing letter. A claim. An unexpected change. A telephone call made because something simply does not make sense.

Those moments are often exceptions, and exceptions are precisely where highly standardized organizations can struggle. The system sees a transaction. The customer may see twenty years of history. The system sees the next available representative. The customer remembers the person who knew their family. The system asks whether the correct process was followed. The customer wants to know whether anyone understands why they are frustrated.

Neither perspective is necessarily wrong.

The answer is not to abandon standardization. Personalized service without adequate systems quickly becomes inconsistency, inefficiency and, in some industries, genuine risk. The more important question is deciding what should be standardized and what should remain stubbornly human.

Technology should remember details so people do not have to. It should automate repetitive administration, move information efficiently, identify errors, and make routine transactions easier. But perhaps the value of those efficiencies is not that they allow us to remove people from the relationship. Perhaps they should create more room for people to handle the moments where judgment, empathy, context, and trust actually matter.

That is particularly important in professional services. Clients rarely remember how efficiently the system operated when something went wrong. They remember whether someone took ownership of the problem.

That conversation did not make me nostalgic for inefficient processes. It made me think more carefully about what efficiency is supposed to accomplish. If every improvement makes an organization easier to operate while gradually making the customer feel less known, we should at least be willing to ask whether we are measuring the entire cost.

Sometimes the first warning will not appear on a dashboard.

It will simply be a longtime client saying, “This doesn’t feel the way it used to.”

Leaders should pay attention when they hear that.

Standardize the process where you must. Never standardize away the relationship.

Our instinct when something goes wrong is usually to establish fault. We reconstruct events, identify contributing circumstances, and determine who did or did not do what they were expected to do. There are legitimate reasons for this. Organizations need accountability, particularly when failures expose weaknesses in process, judgment, or oversight. Understanding what happened is necessary if we intend to prevent it from happening again.

The difficulty begins when explaining the failure becomes more important than taking responsibility for what follows.

Fault and responsibility are related, but they are not the same thing. Fault is principally concerned with causation. Responsibility is concerned with ownership. The first asks, “How did we get here?” The second asks, “What am I going to do about it?”

That distinction becomes particularly important in leadership because managers are rarely responsible only for things they personally execute. They inherit systems, delegate work, depend on other people, and operate within circumstances they do not completely control. It is entirely possible for an outcome to occur on a leader’s watch without every contributing factor being that leader’s fault.

Leadership does not eliminate that distinction. It makes the response to it more important.

One of the strongest demonstrations of professional maturity is the ability to say, “This happened on my watch. It is not acceptable. Here is what I am doing to put it right.” That statement does not require someone to accept blame for circumstances they did not create. It requires them to accept responsibility for the part of the outcome they were entrusted to manage.

There is a psychological reason this can be difficult. When our competence or integrity feels questioned, explanation becomes a form of self defence. We provide context, identify competing priorities, describe the actions of other people, and demonstrate why the outcome should not be interpreted as evidence of our own shortcomings. Some of that context may be completely legitimate. Yet there is a point at which an explanation stops providing useful information and begins protecting identity.

That is often the point where trust stops recovering.

When trust has been damaged, the person on the other side is rarely looking for a more sophisticated explanation of the past. They are looking for evidence about the future. Will the problem be acknowledged? Will behaviour change? Will commitments now be honoured? Will the same conversation need to happen again?

This is why ownership is so powerful. It moves the conversation from intention to action.

Importantly, ownership is not the same as shame. Shame tends to turn inward and ask what a failure says about us as people. Ownership looks outward and asks what the situation now requires from us. One can become paralysing. The other creates agency.

I have also learned that trust rarely returns because of a single conversation. Words can reopen the door, but behaviour determines whether anyone walks through it. A missed commitment followed by an excellent explanation remains a missed commitment. A missed commitment followed by months of reliable execution begins to become something else: evidence that the failure was an event rather than a pattern.

That is particularly important for leaders. Authority may be granted by an organization, but trust is continually earned through behaviour. Titles can establish decision rights. They cannot compel confidence. Once confidence has been damaged, demanding that people trust us again is largely meaningless. The only credible argument is consistent execution over time.

Perhaps that is why ownership can feel so uncomfortable. It removes many of the protections we instinctively reach for when something goes wrong. There is no elaborate defence, no search for the perfect explanation, and no attempt to negotiate how disappointed someone else is entitled to be. There is simply an acknowledgment of reality followed by action.

We cannot always control whether something goes wrong. We can control what we do once we know that it has.

And when trust has been damaged, that may be the distinction that matters most.

Explanations can clarify the past. Ownership is what earns the future.

It was a small moment, and ultimately an inconsequential one. I was asked about a capability that I do not consider one of my professional strengths. I said as much. I also believed, quite genuinely, that if circumstances ever required me to develop it, I probably could. Somewhere in the conversation, however, those two ideas moved a little too close together.

People who have experienced some measure of professional success are often rewarded for believing they can figure things out. Entrepreneurs in particular spend years operating beyond the boundaries of what they already know. You encounter a problem, learn enough to understand it, find the right people, develop the necessary skills, and move forward. Over time, “I can figure this out” becomes part of your professional identity.

For the most part, that confidence is an asset. I am not sure I would have built much of anything without it.

But there is an important distinction between believing you can develop a capability and accurately representing the capability you possess today.

Potential is forward looking. Competence is present tense.

The distance between those two things is where calibration matters.

I have become increasingly interested in calibration as a leadership skill because confidence receives considerably more attention. We admire leaders who make decisions, enter unfamiliar situations, and believe they can solve difficult problems. Those qualities matter. Yet confidence without calibration can become surprisingly dangerous because the person expressing it may not even believe they are overstating anything.

They are simply describing tomorrow’s potential as though it were today’s capability.

That distinction becomes more consequential as responsibility increases. An executive who believes a struggling division can be repaired may be demonstrating vision. An executive who represents that division as healthy because they are confident they can repair it is doing something entirely different. A leader may reasonably believe a team can deliver an ambitious project, but that belief should not become a statement that the necessary capabilities already exist. The same principle applies to forecasts, acquisitions, technology implementations, hiring decisions, and almost every other area where optimism and execution intersect.

There is another psychological problem. Once we state something confidently, correcting ourselves can feel more uncomfortable than continuing.

The first overstatement may be innocent. Perhaps we understood the question differently. Perhaps we genuinely believed our capability was stronger than it was. Perhaps we simply reached a little too far in the moment. The more important test of credibility is what happens when reality provides better information.

Can we say, “Let me qualify what I just said”?

That sentence requires surprisingly little effort and, occasionally, a surprising amount of maturity.

Leadership culture is shaped by these moments. When senior people can acknowledge uncertainty, specialists become more comfortable challenging assumptions. Managers surface problems earlier. Forecasts become more useful because people are not protecting previous predictions. An organization becomes less interested in appearing correct and more interested in becoming correct.

None of this means leaders should become timid about their potential. I still believe there is enormous value in looking at something you cannot do today and thinking, “I can learn that.” Much of human progress depends on precisely that kind of confidence.

The discipline is keeping the tense correct.

“I can learn this” is ambition.

“I can do this” is a statement of present capability.

Strong leaders should be comfortable saying both, but they should know which one is true.

A recent conversation reminded me that even after years of leading businesses, building teams, and making consequential decisions, that distinction still requires attention. I am glad it did. Small moments have a useful way of exposing larger principles if we are willing to examine them rather than defend them.

Perhaps that is ultimately what credibility requires. Not perfection, and certainly not knowing everything. It requires enough confidence to believe in what we can become, while remaining honest about where we are today.

Potential has no fixed boundary. Competence does. Credibility is knowing the difference.

This can be difficult to accept because our popular understanding of negotiation is heavily influenced by visible displays of strength. We associate victory with extracting concessions, imposing terms, or demonstrating that the other side needed the agreement more. Those outcomes are satisfying when leverage permits them. When it does not, behaving as though the imbalance does not exist is not strength. It is a failure to understand the negotiating environment.

A smaller party cannot manufacture leverage simply by becoming louder. What it can do is understand its leverage more precisely. Even highly asymmetric relationships usually contain dependencies in both directions. A large customer may account for a disproportionate share of a supplier’s revenue, but replacing a reliable supplier may carry switching costs, operational disruption, reputational consequences, or execution risk. An employer may possess considerably more institutional power than an individual executive, while still placing substantial value on that person’s relationships, knowledge, or ability to execute. Scale changes the negotiating position, but it rarely eliminates interdependence entirely.

This is where preparation becomes more important than posture. The weaker party needs an unusually clear understanding of its alternatives, its non-negotiable interests, the other side’s incentives, and the consequences of failing to reach an agreement. It also needs the discipline to distinguish between concessions that are uncomfortable and concessions that fundamentally damage the value of the relationship. Treating every concession as defeat can be just as dangerous as accepting every demand.

The more difficult insight is that success in an asymmetric negotiation should be measured against the realistic alternatives available, not against the outcome we would have preferred under equal bargaining power. If the credible alternatives are materially worse, preserving the most important economic or strategic interests while conceding elsewhere may represent an excellent result. It may not look impressive from the outside, but negotiation is not theatre. The objective is not to produce the appearance of strength. It is to improve your position relative to what would otherwise have occurred.

That does not mean weaker parties should become passive. Quite the opposite. Limited leverage makes judgment more important. Patience can create options. Information can reveal dependencies that were not initially obvious. Coalitions can alter bargaining power. Time can change incentives. Credible alternatives can be developed rather than merely wished into existence. Even the more powerful party has constraints, and understanding those constraints is often where negotiating leverage begins.

There is also a reputational dimension that aggressive negotiators sometimes underestimate. Power can extract concessions in a particular negotiation, but relationships exist beyond a single transaction. If counterparties begin to view commitments as unreliable or negotiations as unnecessarily punitive, they adapt. They diversify, demand protections, develop alternatives, or eventually leave. Exercising leverage and preserving leverage are not always the same thing.

For leaders, this creates an important distinction between symbolic victory and substantive success. Symbolic victory is visible. It produces headlines, applause, or the satisfaction of having refused to yield. Substantive success is often quieter. It protects the interests that matter most, preserves optionality, limits unnecessary damage, and leaves the organization stronger than the alternatives would have.

Sometimes the best negotiator does not leave the room having won everything.

Sometimes they leave having understood exactly what could be won, what had to be protected, and what was never worth fighting over in the first place.

For a long time, being able to fix almost anything is an enormous advantage. Then the business grows. More people arrive, responsibilities get divided, managers emerge, and processes become more sophisticated. Yet something strange can happen to the person who built the organization. Everyone still knows you can fix things.

I have seen versions of this in my own business. Someone comes into my office with a problem and, quite often, I know what I would do. Sometimes I know within thirty seconds. There is an enormous temptation to simply give them the answer. It is faster, the problem disappears, I get to feel useful, and everyone moves on with their day. Except something else just happened. The person who brought me the problem learned that bringing it to me works.

Do that often enough and competence starts creating its own gravitational pull. Difficult decisions find their way to the same desk. People who are perfectly capable of exercising judgment begin second guessing themselves. Managers become messengers. Small problems wait for the person everyone trusts to solve the big ones. Eventually, the most capable person in the organization can become the reason the organization cannot move any faster.

That is an uncomfortable possibility for leaders because being needed feels remarkably similar to being effective. They are not necessarily the same thing.

There is also an ego component that I do not think leaders discuss enough. It feels good to be the person with the answer. There is reassurance in knowing that when something becomes sufficiently difficult, everyone eventually turns to you. You become indispensable, and we tend to describe indispensability as a compliment. I am no longer convinced it always is.

If twenty people need your judgment before they can exercise theirs, you have not necessarily demonstrated how valuable you are. You may have demonstrated how much capability the organization has failed to develop around you. At some point, that changes the job of leadership. The question stops being whether you can solve the problem. Of course you can. That is probably part of the reason you are sitting in the chair. The better question becomes whether you should.

Sometimes the answer is absolutely yes. There are decisions where authority, experience, risk, or consequences require the leader to intervene. Delegation is not abdication, and allowing people to learn does not mean allowing preventable disasters for the sake of personal development. But many of the problems that make their way to a leader’s desk do not meet that threshold.

Sometimes the better response to “What should I do?” is simply, “What do you think we should do?” Then listen. They may arrive at exactly the answer you would have given them. They may arrive at a better one. They may also get it slightly wrong, and that last possibility is where leadership becomes difficult.

Capability requires repetition. Judgment develops through making decisions, living with consequences, receiving feedback, and adjusting. If the leader constantly interrupts that process by supplying the correct answer, the team can become remarkably good at one thing: asking the leader. You can accidentally build dependency while believing you are building excellence.

There is a more practical business risk here as well. An organization concentrated around one person’s judgment has key person risk, whether anyone calls it that or not. Decisions slow when that person is unavailable. Institutional knowledge remains trapped in one head. People escalate instead of deciding. Growth eventually encounters a mathematical constraint because even the most capable leader still has only so many hours in a day. The founder who once accelerated everything can eventually become the bottleneck.

I think one of the harder transitions in leadership is learning to measure your contribution differently. Early in a business, your value is highly visible. You closed the account, solved the problem, saved the client, or fixed the process. Later, some of your best work becomes almost invisible. Someone else makes the right decision without calling you. A manager handles a difficult conversation before you even know there was one. The business encounters a problem you would once have personally solved, and the system absorbs it without you.

Nobody applauds when that happens. Nothing dramatic happens at all. That is precisely the point.

I have increasingly come to believe that leadership maturity involves becoming less impressed by how many things require you and more interested in how many things can function properly without you. That does not make the leader irrelevant. It makes the organization resilient.

Competence gets many of us far enough to build something worth leading. The danger comes when we become so accustomed to demonstrating that competence that nobody around us gets enough room to develop their own. There will always be moments when a leader needs to step in, but if every difficult road eventually leads back to your office, the problem may no longer be the capability of the people around you.

It may be the dependency you unintentionally taught them to have.

If everything works only when you are there, you have not built an organization. You have built a dependency with your name at the centre of it.

As I have gotten older, I have come to appreciate the value of that combination. Honest criticism is useful when it comes from people who are genuinely invested in your development. They are not criticizing you because they need to justify a decision or manage an uncomfortable conversation. They are telling you something because they want you to become better. That distinction becomes much harder to recognize in professional life, where feedback and rejection are often packaged together.

Rejection is unavoidable in business. A proposal is declined, a client chooses a competitor, an application goes nowhere, or an opportunity you believed was a natural fit simply disappears. For ambitious people, the instinct is usually to understand why. We examine the explanation, replay the conversation, and search for the variable that could have changed the outcome. There is nothing inherently wrong with that. Reflection is one of the ways experience becomes judgment.

The problem begins when we assume every explanation accompanying a rejection is an accurate diagnosis of what went wrong.

Professional communication is rarely that precise. People have legitimate reasons for being diplomatic. A hiring manager may not want to explain every consideration behind a decision. A prospective client may simply feel more comfortable with someone else. An executive may have internal political considerations that would be inappropriate to disclose. Sometimes the person making the decision cannot even articulate precisely why one option felt preferable to another. Human decisions are influenced by experience, incentives, relationships, timing, emotion, and bias, much of which never appears in the carefully worded explanation that follows.

This becomes obvious when enough feedback accumulates. One person thinks an idea is too ambitious while another thinks it is too conservative. One client wants more detail while another finds the same level of detail overwhelming. One organization considers your experience unconventional while another sees precisely that difference as an advantage. If every rejection becomes an instruction to change direction, eventually you are no longer improving. You are simply reacting.

That does not mean feedback should be ignored. Quite the opposite. Good feedback is extraordinarily valuable, but it has to be weighted rather than merely collected. I pay particular attention when the same observation comes from several credible sources, when it comes from someone with relevant expertise, or when it comes from people who have demonstrated that they are invested enough in me to tell me something I may not want to hear. A pattern deserves investigation. A single polite explanation may not.

There is also an opportunity cost to endlessly decoding rejection. Time spent constructing elaborate theories about why someone said no is time that cannot be invested in the next client, proposal, relationship, or idea. At some point, reflection stops producing insight and becomes rumination. Knowing when that line has been crossed is an important form of professional judgment.

Perhaps that is what my sisters taught me without either of us realizing it. The objective was never to become immune to criticism. It was to develop enough confidence and self-awareness to know which criticism deserved my attention.

Some feedback should change you. Some should challenge you. Some should confirm something you already suspected.

And sometimes, a no is simply a no.

Wisdom is knowing the difference.

Someone presents an idea. There is some discussion, a few questions are asked, and eventually the person leading the meeting looks around the room and asks if anyone has any concerns. Nobody does.

The meeting ends, people walk out, and suddenly everyone has concerns.

It is easy to look at that behaviour and conclude that people should simply have the courage to speak their minds. Sometimes that criticism is probably deserved. But I think there is a more interesting question for anyone leading a business or a team.

Why didn’t they?

Economist Timur Kuran has written extensively about something called preference falsification. Put simply, people don’t always publicly express what they privately believe. We adjust what we say based on the social consequences of saying it.

That sounds like dishonesty, but it can also be perfectly rational behaviour.

Most people become quite good at reading a room. We learn which opinions are welcomed, which ones create friction, and which disagreements simply aren’t worth having. The dynamic can exist in a ten-person business just as easily as it can in a corporate boardroom.

Over time, every organization teaches its people what honesty costs.

If challenging an idea produces curiosity and discussion, people learn that disagreement is useful. If it produces defensiveness, embarrassment, exclusion, or a reputation for being difficult, people learn something else. Eventually nobody needs to tell them to stay quiet. They do the calculation themselves.

That creates an interesting problem for leadership because leaders depend on observable information to understand their organizations. We watch how people react, listen to what managers tell us, look at employee feedback and performance reports, and pay attention to what happens in meetings. Then we make decisions based on what we see.

But what happens when our position changes what we are able to see?

Imagine ten people sitting around a table discussing a proposal. Seven privately think it is a bad idea, but nobody wants to be the first person to challenge it. One person stays quiet because everyone else appears supportive. Someone across the table notices that person’s silence and makes exactly the same calculation.

Suddenly seven people can privately disagree while each believes they may be one of the only people who does. From the leader’s chair, the observable evidence is compelling. Nobody objected.

The problem is that silence and agreement can look remarkably similar.

I think this becomes even more important as someone gains authority. A colleague may tell you directly that your idea won’t work. An employee might say they have “some concerns.” By the time the same information travels several levels upward, a serious operational problem can arrive in an executive meeting as an “implementation challenge.”

Power doesn’t necessarily stop information from moving. It can change the information while it moves.

That creates a strange paradox of leadership. The more senior you become, the more consequential your decisions are and therefore the more accurate your information needs to be. Yet the authority attached to your position can make people increasingly careful about what they tell you.

This is why I am skeptical when organizations describe themselves as having an “open culture.” An open-door policy tells me very little. I am much more interested in what happens when someone walks through that door and tells the person on the other side something they don’t want to hear.

Does the disagreement become a discussion about the employee’s attitude or commitment? Does nothing happen until people eventually conclude that raising concerns is pointless? Or can someone disagree, be heard, lose the argument, and walk away without having damaged the relationship?

That last part matters.

Creating space for disagreement does not mean leadership becomes a democracy. Employees can be wrong. Teams can resist necessary change. Leaders still have to make difficult decisions, including decisions people dislike.

The objective isn’t agreement. It is access to unfiltered information.

Because when something eventually goes badly, leaders often ask the same question: “Why didn’t anyone tell me?”

Sometimes nobody did. But before asking why people stayed silent, it may be worth asking what happened the last time someone spoke.

Organizations are constantly teaching people which behaviours are rewarded, tolerated and punished. Eventually those lessons become culture, whether leadership intended them or not.

So a room full of people nodding along should not always make a leader comfortable. Agreement is useful when it is genuine. When it isn’t, the appearance of consensus can actually deprive leadership of the information it needs most.

A leader’s job isn’t to create a room where everyone agrees. It’s to create a room where disagreement is cheap enough that the truth can afford to show up.

Curiosity got the better of me, so I asked what the staff thought about it.

He smiled, shook his head, and replied, “We hate it. But we have no choice. We never do.”

It was a brief conversation, but it stayed with me long after I walked back to my car because it raised a question that extends far beyond retail. As artificial intelligence becomes embedded in everyday business, we are spending enormous amounts of time asking what technology can do. I am not convinced we are spending enough time asking what it should do.

Organizations across virtually every industry are investing heavily in automation, artificial intelligence, and data driven decision making. Much of that investment is entirely justified. Technology can process extraordinary amounts of information, recognize patterns humans might overlook, eliminate repetitive work, and improve operational efficiency in ways that would have been unimaginable only a few years ago. Used wisely, it has the potential to become one of the most valuable business tools ever created.

The challenge is that efficiency is not the same thing as judgment.

Scheduling, for example, appears to be a relatively straightforward optimization problem. An algorithm can predict customer traffic, recommend staffing levels, and minimize labour costs with remarkable precision. What it cannot fully appreciate are the realities that rarely appear in a dataset. It cannot understand the employee caring for an aging parent, the single parent trying to coordinate childcare, or the team member who has quietly carried the heaviest workload for months without complaint. Those factors may not influence a mathematical model, yet they often determine whether an employee remains engaged, loyal, and productive over the long term.

This is where leadership becomes irreplaceable. Technology excels at identifying patterns. Leaders must interpret people. The two capabilities complement one another, but they are not interchangeable. An algorithm can recommend a decision. It cannot carry the responsibility, empathy, or accountability required to make one.

Perhaps this is the more important conversation organizations should be having.

For decades, many businesses have measured success by asking, “How can we accomplish more with fewer people?” Increasingly, I wonder whether a better question is, “How can technology help our people create more value?” Those two questions may sound similar, but they lead organizations in very different directions.

One treats people primarily as a cost to optimize. The other recognizes that people are the organization’s greatest source of adaptability, creativity, judgment, and long term competitive advantage. Technology should reduce unnecessary work so that human beings can spend more time doing what only human beings can do.

As artificial intelligence continues to reshape the workplace, I suspect the organizations that distinguish themselves will not simply be those that automate the fastest. They will be those that exercise the wisdom to recognize where automation creates value and where human judgment remains indispensable.

Technology should make better leaders possible.

It should never make leadership optional.

In the early stages of a business, they often appear inseparable. The people producing the strongest results naturally become candidates for greater responsibility because they have demonstrated competence, discipline, and consistency. Promoting them seems like the logical next step. Sometimes it is. Other times, it quietly exposes a distinction that many organizations overlook.

Throughout my career, I have worked with people whose personal production was exceptional. They consistently exceeded expectations, earned the respect of clients, and delivered results that spoke for themselves. Yet when opportunities arose to coach a colleague, share knowledge, or help elevate the broader team, the enthusiasm often disappeared. Their responsibility, in their minds, ended where their own performance metrics ended.

From an organizational perspective, that is a problem.

Leadership begins at the point where your success is no longer measured primarily by what you accomplish yourself, but by what you enable others to accomplish. A high performer creates value through personal execution. A leader creates value by multiplying the capabilities of those around them. The distinction may appear subtle, but it fundamentally changes how an organization grows.

This requires a deliberate shift in mindset. Many professionals understandably invest years mastering their craft. That expertise deserves recognition. However, if knowledge becomes something to protect rather than something to develop in others, the organization inevitably reaches a ceiling. Growth becomes dependent upon a handful of individuals instead of a system capable of producing excellence repeatedly.

That does not mean leadership is simply delegation or inspiration. Effective leaders must retain deep operational credibility. It is difficult to coach people through challenges you do not understand yourself. The strongest leaders I have known were first capable practitioners. The difference was that, over time, they redirected more of their energy toward building people than proving themselves.

Organizations also bear responsibility for creating this transition. If compensation, recognition, and advancement are tied exclusively to individual performance, then individual performance is exactly what people will optimize. If leadership is genuinely valued, then developing talent, strengthening collaboration, and improving the performance of the wider team must become visible measures of success as well.

Ultimately, every organization reaches a point where its future depends less on producing another exceptional employee and more on producing exceptional leaders.

Individual performance builds successful careers.

Leaders build organizations that continue succeeding long after their own numbers no longer matter.

“Do your best, and let your character do the talking.”

At the time, it sounded like simple guidance about personal responsibility. As the years have passed, I have come to appreciate that it was also remarkably practical business advice.

One of the first lessons you learn as an entrepreneur is that competence does not guarantee acceptance. You can invest years developing expertise, work tirelessly for your clients, and build a reputation for integrity, yet still encounter people who decide they have already formed an opinion before you have spoken a single sentence. Throughout my career, I have experienced this in different ways. Sometimes it has been because of how I sound. Sometimes because of how I look. Occasionally, it has simply been because I came from somewhere else.

Earlier in my career, I spent far too much time trying to understand those reactions. Like many business owners, I believed that every point of friction represented a problem to solve. If someone misunderstood me, perhaps I needed to explain myself more clearly. If someone held an unfavourable opinion, perhaps I simply had to work harder to change it.

Experience has taught me otherwise.

Business is ultimately an exercise in allocating finite resources. Time, attention, capital, and emotional energy are all limited. Every hour spent trying to convince someone who has already decided against you is an hour not invested in serving people who genuinely value what you bring to the table. That is not simply inefficient. It is strategically unsound.

This principle extends far beyond personal experience. Every organization faces the temptation to broaden its appeal in the hope of satisfying everyone. Products become overloaded with features that few customers requested. Marketing messages become increasingly generic in an attempt to offend no one. Policies multiply because every exception creates another rule. In trying to accommodate every possible preference, organizations often lose the clarity that made them valuable in the first place.

Strong businesses make difficult choices.

They decide who they serve exceptionally well. They accept that not every customer is the right customer. They recognize that attempting to eliminate every source of criticism is neither realistic nor desirable because doing so often requires compromising the very qualities that distinguish them in the marketplace.

The same principle applies to individuals.

If someone chooses to judge me because of my background or my appearance, that is ultimately a decision I cannot control. What I can control is the quality of my advice, the consistency of my work, and the integrity with which I serve my clients. Those are investments that compound over time. The others rarely produce a meaningful return.

My mother never suggested that character would convince everyone.

She simply understood that, in the long run, it would attract the people who mattered most.

Looking back, I think that was less a lesson about character than it was a lesson about strategy.