Almost everyone who has spent enough time in expert organizations knows at least one exceptionally competent professional who is also exceptionally aware of their own competence.
You probably know the type. They have an answer to almost everything, interrupt others, show little patience for beginners, and are quick to explain why someone else’s idea is unlikely to work. Sometimes they make their colleagues feel rather stupid. And quite often, annoyingly enough, they are right.
I have met people like this during my career consulting and academia. Some are genuinely brilliant at what they do. They can solve complex problems, recognize patterns that others miss, and produce results that would be difficult to achieve without them. But working with them can also be exhausting.
In one of my books on IT consulting, I actually suggested that if you are very good at what you do, you can afford to be a little arrogant. I still think there is some truth to that. Exceptional competence does buy you a certain amount of tolerance. But my thinking has evolved since then. Just because you can afford to be arrogant does not necessarily mean you should.
I do not consider myself particularly arrogant. Of course, this assessment comes from a highly reliable source: myself. I certainly know my professional worth, and I think that is a good thing. Whether everyone else always agrees with my self-assessment is another question.
All of this raises an interesting issue. How arrogant can you afford to be when you are genuinely very good at your job?
Expertise Buys You Some Privileges
Let’s start with an uncomfortable observation: highly competent people can often get away with behavior that would cause serious problems for someone less capable.
A senior expert may possess rare technical knowledge, understand complicated systems better than anyone else, or have relationships with important clients. They might be the person everyone calls when a critical project runs into trouble. Replacing them could be expensive, time-consuming, or practically impossible in the short term.
Under these circumstances, a certain amount of arrogance may be tolerated for years.
Managers might explain that the person is simply demanding, exceptionally intelligent, or perhaps not very interested in social conventions. Colleagues learn to deal with the occasional unpleasant remark. Junior employees learn to prepare their questions carefully, preferably after first consulting someone more approachable. The expert gets to continue doing things their own way.
And from a purely practical perspective, this tolerance is understandable. If someone repeatedly delivers exceptional results, an organization may be willing to accept a few unpleasant characteristics.
However, there is a difference between what an organization is willing to tolerate and what actually helps an expert succeed. The better you are, the more arrogance people may tolerate. But that does not mean it is a good career strategy.
There is also a distinction worth making between arrogance and plain bad behavior. Having a high opinion of yourself, perhaps even an excessively high one, is one thing. Treating colleagues disrespectfully, humiliating others, or making their working lives miserable is another. The two can certainly go together, but they are not quite the same thing. And exceptional competence is hardly an excuse for treating people badly.
But Are You Actually That Good?
There is another problem with arrogance: the person displaying it may not be nearly as competent as they think.
Some professionals have a remarkably high opinion of their own abilities. But confidence is not particularly reliable evidence of competence.
I have not encountered this combination particularly often in my professional work. As a customer, however, I sometimes get the impression that the least competent people are also the most arrogant. Sometimes this even seems to be a characteristic of the entire organization. Of course, this is based on my assessment of their competence, which may not be entirely objective either.
Experience does not automatically make someone an exceptional expert, either. You can spend twenty years doing something without becoming particularly good at it. You might simply have twenty years of experience doing things more or less the same way.
And even genuinely excellent experts tend to have their blind spots. Being exceptionally good at software architecture, for example, does not automatically make you an authority on business strategy, organizational change, or managing people. Still, some experienced professionals seem to believe their expertise extends to almost everything.
I suppose most of us have at least some tendency to overestimate our abilities. Also this makes arrogance a rather risky strategy. You may believe your exceptional competence gives you the right to behave as you please. But what if other people consider you merely average, or perhaps just reasonably good at a rather narrow set of tasks?
In that case, you are asking people to tolerate unpleasant behavior without offering much in return. And even if you really are exceptionally good at what you do, it might be worth remembering that you are probably not quite as exceptional as you think.
Being Right Is Only Part of the Job
One of the privileges of seniority is the ability to recognize problems quickly. After working in a particular field for many years, you have probably seen the same mistakes several times.
Consider an experienced IT architect reviewing a proposed solution. Within minutes, they recognize that the approach will create serious maintenance problems. Perhaps they have seen something very similar fail before.
They could say:
“I have seen this approach before, and I think it will cause problems. Let me explain why.”
Or:
“Anyone competent should immediately understand why this is a bad idea.”
The underlying technical assessment might be exactly the same. The difference is in how the expertise is delivered.
The first response makes the expert’s knowledge available to others. The second also communicates something about the other person’s competence, whether intentionally or not. And that additional message has consequences.
People gradually become more careful about what they bring to an arrogant expert. They might avoid discussing early ideas, asking basic questions, or admitting uncertainty. Instead, they consult someone who is perhaps less experienced but easier to approach.
This can become a surprisingly serious problem. In most senior expert roles, your value comes from much more than the quality of your personal work. You are also expected to advise others, influence decisions, help less experienced colleagues develop, and contribute to the organization’s collective competence.
If people avoid involving you, much of that potential remains unused.
Competence can buy you tolerance, but it does not necessarily buy you influence. You might still be the person who gets called when everything has already gone wrong. But you may be absent from the conversations where those problems could have been prevented.
Confidence and Arrogance Are Different Things
Clients and colleagues expect experienced professionals to have opinions. Sometimes they expect quite strong ones. If I would hire a senior consultant, I certainly do not want to hear that every possible approach is equally good and that we should perhaps organize another workshop to explore the options.
I want the consultant to tell me what they think, based on their experience and expertise.
Sometimes that means disagreeing with the client, challenging management, or telling an enthusiastic project team that their brilliant idea has some rather obvious weaknesses.
There is nothing inherently arrogant about that. That is just confidence.
In fact, excessive caution can make an expert almost as frustrating as excessive arrogance. If someone has the knowledge and experience to recognize a serious problem, I would expect them to speak up.
The important distinction is between being confident in your professional judgment and assuming that your judgment makes you superior to others.
You can be very certain about an analysis while remaining open to additional information. You can disagree strongly without questioning another person’s intelligence. And you can acknowledge that someone with less experience might still understand something you have overlooked.
Seniority should make these things easier, rather than more difficult.
How to Be Very Good Without Becoming Unbearable
I would suggest three practical principles for experienced professionals.
Be Certain About the Work, Not About Your Superiority
If you know that a proposed solution is problematic, explain the reasons. Refer to previous experience, identify risks, and suggest alternatives. People are more likely to appreciate your competence when they can understand the thinking behind your conclusions.
Being able to explain something clearly is also a useful test of whether you understand it as well as you think you do.
Earn the Right to Be Direct
Experienced experts usually have more freedom to communicate directly because their opinions are supported by a history of good work. They have earned credibility.
Use that freedom. There is little reason to hide an important point behind unnecessarily diplomatic language. But remember that being direct and being disrespectful are two different things.
A straightforward explanation of why an idea is bad is often much more useful than a polite but vague response. Adding a personal insult rarely improves the analysis.
Remember That Expertise Has Diminishing Returns If Nobody Wants to Involve You
This is particularly important for consultants, architects, technical specialists, and other professionals whose work depends on influencing decisions made by other people.
You can be the smartest person in the room and still have surprisingly little impact on what the organization actually does.
If colleagues hesitate to involve you, clients avoid difficult conversations, and junior experts stop asking for advice, your expertise is becoming less useful than it could be.
That is a considerable waste of competence, especially if you have spent years developing it.
So, How Much Arrogance Can You Afford?
Probably quite a lot, if you are exceptionally good at something that other people really need.
Some experts seem to build entire careers around this arrangement. Their competence makes them valuable enough that others simply accept the difficulties of working with them.
And perhaps they are perfectly happy with that. Not everyone wants to become a mentor, leader, or universally appreciated colleague. There is certainly room for highly specialized individual contributors who prefer to concentrate on their work.
Still, even the most independent expert depends on other people to some extent. Someone needs to recognize the problem, ask for help, provide relevant information, and eventually make use of the solution. Arrogance can make every one of those steps unnecessarily difficult.
I also think there is something slightly contradictory about an experienced expert who constantly needs to demonstrate their superiority. After years of successful work, professional competence should be rather well established. There is little need to turn every meeting into another opportunity to prove it.
Of course, recognizing your own tendency toward arrogance is easier said than done. Particularly when you are convinced that your self-awareness is also above average.
Maybe the real privilege of being very good is not that you can afford to be arrogant. It is that you no longer need to prove that you are.
📚 Related Reads from Expert Work by Design
If you found this useful, you might also enjoy the following articles:
👨💻About the Author
Eetu Niemi is an enterprise architect, consultant, and author.
Follow him elsewhere: Homepage | LinkedIn | Substack (enterprise architecture ) | Medium (writing) | Homepage (FI)
Books: Enterprise Architecture | The Senior Expert Career Playbook | Technology Consultant Fast Track | Successful Technology Consulting | Kokonaisarkkitehtuuri (FI) | Pohjoisen tie (FI) | Little Cthulhu’s Breakfast Time
Web resources: Enterprise Architecture Info Package (FI)





