Sure, they can be demanding, impatient, unclear, and sometimes visibly frustrated. But usually there is a fairly understandable reason behind it. They have a problem to solve, a project to deliver, a budget to explain, and someone above them asking why everything is still “in progress.” As a consultant, you are often simply close enough to receive some of that pressure.

With colleagues and consultants from other companies, I have needed thick skin a little more often.

Not because people are generally terrible. Most people are quite decent, at least on a good day and before the afternoon’s last meeting. But expert work creates situations where ego, insecurity, competition, unclear roles, and time pressure all sit around the same table.

This is where thick skin becomes useful. Not as a way to stop caring, but as a way to keep your judgment when the situation gets unnecessarily personal, political, or just a bit stupid. The trick is to build enough distance to stay calm without turning into the kind of person who expects the worst from everyone and calls it realism.

Why Thick Skin Is Needed

Thick skin does not mean that nothing feels bad. That would probably require a medical condition, or a very successful career in law.

It means that you can continue functioning when something feels uncomfortable for a moment. Someone questions your work. Someone ignores your idea and presents almost the same idea two weeks later as their own. Someone uses a meeting mainly to prove that they are the smartest person in the virtual room. Someone is cold or dismissive, and you have no idea why.

The first reaction is often personal.

Did I do something wrong? Why is this person behaving like this toward me? Should I defend myself? Should I write a very long message that I will later regret but briefly enjoy while writing?

Sometimes you should respond firmly. But often the more useful interpretation is simpler: it is probably not about you.

People carry their own pressures, fears, ambitions, and internal politics. Difficult behavior is often a symptom of something else. This does not make it acceptable, but it makes it easier to handle. You do not have to take every sharp comment home with you like a small, unpleasant souvenir.'

The Problem Is Often the Story We Add

In difficult situations, the problem is rarely the feeling itself. Irritation, disappointment, and insecurity are normal reactions. They mostly prove that you are still human and have not yet become a completely emotionless work robot.

The bigger issue is the story we build on top of the feeling.

If every critical comment becomes a personal attack, work gets heavy very quickly. Or if every case of poor behavior is explained away with “this is just how things are,” you slowly become cynical. Then you stop expecting anything sensible from people. It is one way to protect yourself, but not a very useful way to work with others.

The better option is somewhere in the middle. You can notice that a situation felt unpleasant and still analyze it calmly. Was there something useful in the criticism? Was the style bad, but the content valid? Was there a real issue, or was someone just trying to look important in front of an audience?

It is not always easy. But it is useful.

A surprising amount of professional maturity is just the ability to separate the message from the noise around it. Even when the noise has a job title.

Practical Ways to Build Thick Skin

The first habit is to create a delay. You do not have to answer everything immediately, even if Teams, Slack, email, and your inner defense lawyer all suggest otherwise. When a message irritates you, write the response, leave it for a moment, and then remove the most emotional half. Usually that deleted half is exactly the part that would have turned a small issue into a workshop series.

The second habit is to separate feedback, status, and personal value from each other. If someone dislikes your proposal, it does not mean you are bad at your work. If someone behaves rudely, it does not mean you are weak if you do not answer in the same style. Professionalism is not submission. Often it is simply choosing which battles deserve your energy.

The third habit is to keep a basically positive view of people, but without becoming naive. Most people try to do their work reasonably well. Some do it clumsily. Some behave badly under pressure. And a small minority are genuinely difficult cases. With them, it is better to agree clear boundaries, document important points, keep the discussion concrete, and escalate through the right channels if needed. That is not drama. It is just handling the problem at the right level before it quietly poisons your work.

It also helps to get perspective outside the project bubble. When one comment, meeting, or email starts to feel too big, talk about it with a trusted colleague. Not to build a small support group around your own excellence, but to check the proportions. Many dramatic work situations become smaller when you explain them out loud to a normal person. Preferably someone who is not also in the same steering group.

AI can also be surprisingly useful here. Not as a therapist, career coach, or replacement for judgment. But it is good at analyzing the situation more neutrally when you are too close to it, and at turning an irritated draft into something calm and usable. It can help separate the actual message from the emotional packaging, remove the sharp edges, and produce a version that sounds like a professional wrote it before opening the email became a small personal crisis.

Thick Skin With a Soft Core

The best kind of thick skin does not make a person hard. It makes a person more flexible. Or resilient, if we want to use the official word.

You can receive criticism, deal with difficult people, and work under pressure without letting every unpleasant moment make you a little more bitter. That is the part worth protecting. Not your ego, but your ability to stay constructive.

Cynicism sometimes looks like experience. Often it is just tiredness wearing business casual.

An experienced person knows that people can be difficult, projects can be messy, and organizations can behave in ways that make very little sense. Still, they can stay practical. They can ask what needs to happen next. They can decide whether the issue is worth addressing, ignoring, escalating, or simply surviving until Friday.

Developing thick skin means that you do not let other people’s temporary bad behavior define your own way of working. It is a practical skill, not a personality transplant.

And like most practical skills, it develops slowly, usually through exactly those situations where it would have been nice to already have it.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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 | The Senior Expert Pay 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)

There is no clear end of shift in many roles. The laptop can be closed, but the work may still continue in messages, thoughts, calendar invites, half-decisions, and small things that “would be good to handle today”.

This is not always caused by a bad workplace or unreasonable people. Often it is just how modern work is built. Communication is fast, calendars are shared, tools are always available, and many tasks do not have a clean natural ending. There is always something that could be clarified, improved, answered, checked, prepared, or moved forward.

So work creeps.

It creeps into the evening through one quick reply. It creeps into lunch through a meeting that had no other slot. It creeps into a weekend through unfinished tasks that did not fit anywhere else. It creeps into your head when you are technically not working, but still mentally running the next decision.

Nobody usually decides to give away their free time. It happens in smaller pieces.

One exception. One fast answer. One “I’ll just check this quickly”. One task that should not take long.

After a while, the working model has changed without anyone saying it out loud.

The problem is not that every small exception is wrong. Sometimes they are needed. The problem is when these small exceptions become the default way of working.

At that point, it is worth asking a practical question: are you protecting your free time with actual structures, or are you just hoping work will stop at the right moment by itself?

It usually will not. Work is not that polite.

Why Free Time Needs Structure

Free time is easy to treat as a personal matter.

You can decide that evenings are free. You can decide not to work on Fridays. You can decide that at least weekends are protected. These are good decisions, and sometimes they help.

But personal decisions are often too weak if the surrounding work system says something else.

If your calendar is open, people will book it. If you answer messages quickly in the evening, people may learn that evening is a possible response time. If every new request is added without removing anything, the extra work has to go somewhere. Usually it goes into the edges of the day.

This is why free time does not protect itself. It needs a working model that other people can see.

There is also a strange habit in working life where free time becomes more acceptable if you can attach a socially approved reason to it. Family situation. Children. Health. Care responsibilities. Some serious hobby with equipment expensive enough to look like a second job.

All of these can be real and important reasons. But they should not be required.

Free time should not need a defence case. You do not need to prove that your evening is valuable enough to be protected. The default should be that time outside work is not available, unless something else has been clearly agreed.

The point is not to make collaboration difficult. The point is to make expectations clear before they become a problem.

Practical Ways To Protect Free Time

The practical answer is not to become more strict about everything. That usually does not work, makes normal collaboration annoying, and is not great for your career.

The better answer is to make the default way of working clearer. When the default is visible, people know what to expect, and exceptions are easier to handle without turning them into the new normal.

Make The Working Model Concrete

The first step is to move from intentions to visible rules.

“Trying to be better with time” is not a working model. “No meetings after 15:00 on Fridays” is.

“Need to focus more” is not a working model. “Mornings are blocked for deep work” is.

“Let’s reduce unnecessary meetings” is not a working model. “Every meeting needs a clear purpose, decision, or reason for me to be there” is.

These rules do not need to be dramatic. They are not personal manifestos. They are just information about how work gets done.

For example, you can define that non-urgent messages are answered during working hours. You can keep one afternoon meeting-free. You can block focused work time before the week fills up. You can agree with your team that urgent topics go through a specific channel, while everything else can wait.

The more concrete the rule is, the easier it is for others to respect it. Vague boundaries create vague behavior. Clear boundaries create less guessing.

Slightly boring, yes. But boring is often where the useful stuff lives.

Choose What You Participate In

A lot of time disappears through participation that was never really questioned.

A meeting appears in the calendar, so you join. A message thread includes your name, so you follow it. A discussion is happening, so you feel you should have an opinion. A working group is created, and suddenly your calendar has a new recurring meeting that may live longer than some software products.

Not all participation is useful participation.

Before joining something, it helps to ask a few basic questions. Am I needed here, or just included? Is there a decision to make? Do I have information that others do not have? Will this discussion change what I do next? Could I contribute better by writing a short comment instead of attending the whole meeting?

This is not about being passive or avoiding responsibility. It is about using attention where it actually creates value.

A useful habit is to clarify your role before accepting the time cost:

“Do you need me for the whole meeting, or just one topic?”
“Is there a specific decision where you need my input?”
“I can comment async, but I probably do not need to join the full session.”
“Please include me in the summary, unless there is something I need to decide.”

This protects time in a very practical way. You are not saying that the topic is unimportant. You are saying that your participation should have a purpose. Because being included is not the same as being needed.

Prioritize With Trade-Offs

A lot of free time disappears because new work is added without changing the old plan.

A request arrives, and instead of deciding whether it is more important than the current work, it is simply added to the pile. Everyone stays polite, the plan becomes unrealistic, and the calendar quietly absorbs the problem.

This is where prioritization needs to become practical.

A useful rule is simple: if something new becomes important, something else should become less important.

That can sound like:

“Yes, we can do this, but then something else moves.”
“Yes, but not this week.”
“Yes, if we reduce the scope.”
“No, unless this is more important than the current priority.”

This is not negative. It is just honest.

Time and attention are real constraints. If those constraints are not discussed, they still exist. They just show up later as overtime, rushed work, or tired decision-making.

Otherwise the priority list is not a priority list. It is just a polite collection of wishes.

Make Exceptions Explicit

Prioritization is about what fits into the plan. Exceptions are about what happens outside the normal plan.

Every working model needs some flexibility. Sometimes something genuinely important happens at a bad time. A deadline is close. A colleague needs help. A customer issue appears. Normal work has these moments, and pretending otherwise would be very cute but not very useful.

The problem is not the occasional exception. The problem is when the exception quietly becomes the new agreement.

One evening reply becomes normal evening availability. One Friday task becomes regular Friday work. One “just this once” becomes a pattern with no name.

For most people, the answer is not to negotiate every exception like a contract lawyer with a calendar. Often it is enough to make the situation visible:

“I can help with this today because it is important, but let’s treat it as an exception.”
“I can do this on Friday this time, but Fridays are not normally available.”
“I can answer this now so we can keep things moving, but I do not want evening replies to become the expected pattern.”
“If this keeps happening, we should change the working model.”

The goal is not to be difficult. The goal is to prevent silent drift.

Silent drift is when the working model changes without any real discussion. Nobody decides that evenings are now working time. Nobody announces that Fridays are now overflow days. It just becomes normal because it happened a few times and nobody named it.

That is how free time disappears in a very polite and professional way.

What a 4-Day Week Actually Changes

A 4-day workweek is useful mainly because it makes the shape of work visible.

It does not need to be a lifestyle statement. It does not need to come with a podcast, a personal brand, or a dramatic post about walking in nature on Fridays.

At its simplest, it means that the main work happens from Monday to Thursday, and Friday is not treated as normal delivery time.

That already changes the conversation. If something new appears on Wednesday, the question is no longer “can you just fit this in by Friday?” The better question is “what should move?”

Friday can have a purpose, but it should not become a disguised fifth workday. It can be genuinely free, or it can be intentionally reserved for something specific like learning or a side project.

The mistake is to call it a 4-day week while using Friday as hidden overflow. If Friday is always available when things get messy, then the model is not really a 4-day week. It is a normal 5-day week with worse calendar hygiene and more self-deception. Which is also a model, just not a very good one.

Of course, a 4-day week is not possible or useful for everyone. The broader point is not the number of days. The point is that working time should have a shape. It should not be an open container where everything eventually lands.

Recovery Is Part of the Work

Free time is often discussed as a wellbeing topic. That is valid, but it is not the whole picture.

In expert work, recovery also affects the quality of the work.

Tired people make worse decisions. They avoid difficult conversations. They accept unclear priorities. They create more complicated solutions because they do not have the energy to simplify. They say yes when they should slow the discussion down.

A lot of expert work depends on judgment. What matters? What should wait? Where is the risk? What should be simplified? What needs to be challenged? What is actually worth doing?

That kind of work needs attention. And attention does not survive very well if every week is filled to the edges.

So protecting free time is not separate from doing good work. It is one of the things that makes good work possible.

This is also why the topic should not be reduced to personal comfort. It is not only about wanting easier days, although wanting easier days is not a crime against humanity either. It is about sustainability, clarity, and better work.

A Working Model Beats Willpower

Most people do not lose their free time because of one bad decision. They lose it because the normal way of working slowly expands.

Messages, meetings, small tasks, urgent requests, and harmless-looking exceptions start to fill the space that was never clearly protected.

That is why the solution needs to be practical, not heroic. Free time is protected by defaults: when you are available, how meetings are handled, how priorities change, what counts as urgent, and what happens when something falls outside the normal pattern.

The exact model can vary. A 4-day week can work. So can protected mornings, a meeting-free afternoon, fixed response times, or a clear rule that new work requires trade-offs.

The important part is that there is a model.

Because if you do not define how your time is used, the work will define it for you. Usually through the next calendar invite.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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 | The Senior Expert Pay 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)

In my first consulting job, I acted as a team lead in two of my last projects. The role itself was somewhat artificial, mostly used by my manager and me as a way to justify a promotion to a manager title. Without that framing, the promotion—and the corresponding salary increase—would have been difficult to push through. I did not stay in that company long enough for this to become a major career phase, but the logic was clear enough.

Later, I have seen a similar pattern from the other side. In some recruiting discussions, team lead responsibility has been positioned almost as a prerequisite for meeting a certain salary expectation. The message is not always explicit, but the implication is usually clear: higher compensation is easier to justify if it comes with a role that looks like management.

This question tends to appear in fairly predictable situations. Annual discussions, promotion cycles, or job changes often create a moment where the next logical step is presented as some version of team leadership.

These experiences frame the question in a particular way. If higher salary is tied to a team lead role, does it make sense to take the role mainly for that reason?

From a distance, the answer might look obvious. In practice, it is usually not.

The Role Change Is Larger Than It Looks

The team lead role often appears to be a natural continuation of senior expert work.

You already understand the domain. You already contribute to decisions. You are already involved in complex situations and helping other people solve problems. The next step can look incremental from the outside.

Usually it is not. The center of gravity changes. Instead of solving problems directly, you start managing how problems are solved. Instead of focusing mainly on content, you spend more time on coordination, communication, prioritization, staffing concerns, and alignment between people with different expectations.

A larger part of the work moves into conversations that are not really about the solution itself.

Some people enjoy this shift immediately. Others gradually notice that the part of the work they originally found most interesting becomes smaller over time.

Neither reaction is wrong. But the distinction matters more than people sometimes expect.

Why The Decision Is More Complex Than It Looks

Higher salary is often the most visible part of the role change. It is also the simplest part to understand.

The increase reflects broader organizational responsibility, not necessarily a direct continuation of the work you have been doing so far. The organization is paying for a somewhat different type of contribution: coordination, accountability, people management, and operational stability at the team level.

That distinction becomes important surprisingly quickly.

If the motivation is mainly financial, the decision can feel reasonable in the short term. Over time, however, the daily structure of the work tends to dominate the experience. If the role itself does not fit particularly well, the salary increase rarely compensates for the mismatch indefinitely.

The decision also influences longer-term direction. Team lead roles often move people gradually toward management tracks where success is measured less through direct expert contribution and more through organizational coordination and responsibility. Returning fully to expert-focused work later is possible, but usually less straightforward than people assume.

At the same time, many experts quietly assume that compensation growth more or less requires moving into management. That is not always true either.

In many environments, senior expert roles can eventually reach comparable compensation levels. The mechanism is simply different. Instead of formal managerial responsibility, compensation tends to follow positioning, visibility, trusted judgment, client impact, and involvement in situations that matter commercially or strategically.

That path is usually less explicit and less structured than the management path, which is partly why people underestimate it.

Looking only at the immediate salary difference hides most of these trade-offs.

When the Role Actually Fits

There are also many situations where taking a team lead role makes complete sense.

Some people are already operating that way informally before the title changes. They coordinate work, support less experienced colleagues, help resolve conflicts, and naturally become central points of responsibility inside projects or teams. In those cases, formalizing the role often changes less than expected.

The role also fits people who genuinely enjoy helping teams function better. Some experts eventually realize that they are more interested in enabling other people’s work than maximizing their own technical depth. Others discover that broader organizational influence feels more meaningful than individual problem-solving.

It can also be a good long-term step for people who want to move further into leadership positions later in their careers.

In these situations, the role aligns relatively naturally with both the person’s strengths and the direction they already want to move toward.

The Alternative Expert Path

One reason team lead roles create pressure is that many organizations make management progression highly visible while expert progression remains less clearly defined.

The management ladder is easier to explain. Titles change predictably, responsibility expands visibly, and compensation bands are often clearer. Expert careers tend to evolve more indirectly.

Still, alternative paths do exist. Senior experts often create substantial organizational value without formal people management responsibility. For example in consulting, this may involve shaping major client decisions, structuring ambiguous situations, supporting strategic initiatives, improving delivery quality across teams, or becoming trusted in commercially important contexts.

The work may look less impressive organizationally because it does not involve direct managerial authority. Economically, however, the impact can still become very significant over time.

The challenge is that this path usually requires stronger positioning and clearer visibility than management roles do. The contribution needs to become understandable in contexts where compensation decisions are made. That tends to happen more gradually.

A Better Question to Ask

Instead of asking whether the salary increase justifies the move, a more useful question is often simpler:

Do you actually want the work that comes with the role?

That includes the parts that are less visible in the job description: coordination, performance discussions, difficult people situations, competing priorities, organizational friction, and less uninterrupted expert work.

In expert careers, many decisions look like compensation decisions on the surface. In practice, they are often decisions about the type of work you want to spend the next few years doing.

Salary follows that choice more often than it defines it.

Choosing a role mainly for the compensation can work reasonably well for a while. Over time, however, the actual nature of the work tends to dominate the experience. And that is usually what determines whether the decision was ultimately a good one.

📘 Explore the Topic Further

If this perspective resonates, I explore the same theme in more detail in my Senior Expert Playbook series.

The Senior Expert Career Playbook looks at how expert careers actually develop in practice—covering positioning, visibility, and how contribution becomes understood inside organizations.

The Senior Expert Pay Playbook builds on that and explains how compensation typically forms through perceived impact, trust, and structural alignment, not just performance reviews or negotiation.

Together, the books focus on a simple idea: your work matters, but how it is interpreted often matters just as much.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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)

Once a year, you sit down with your manager. Goals are discussed and written down. They often sound reasonable, but also slightly abstract. Things like client value, leadership, development. At that point, it is not always entirely clear what is expected of you in practice.

Then you work, more or less like before. Projects move forward, problems get solved, clients are kept reasonably satisfied, and some things quietly improve without much visibility. If the goals happen to include something concrete, you may try to align with it. But in most cases, the work is still driven by the situation rather than the wording of the targets.

Toward the end of the cycle, you are asked to summarize what you did. You write a structured description of how your work aligns with the goals. If you have done this a few times, you know how to make it sound coherent.

After that, the process moves somewhere else. A group of managers compares people, discusses outcomes, and decides who gets promoted, who receives a salary increase, and who continues more or less as before. The criteria are visible, but the actual decision-making is usually a black box for anyone not in the room.

At this point, it is reasonable to ask what the process is actually optimizing for.

My own experience with this has been somewhat mixed. A significant part of my career has happened without formal performance targets beyond basic things like client work and utilization. At other times, I have had clearly defined but fairly abstract goals similar to most large consulting organizations. Looking at both sides, the difference in how the work itself felt was not particularly large. The difference was mainly in how that work was later described and interpreted.

This raises a few practical questions. Do performance reviews actually measure the right things, or mainly what is easiest to describe? Do they meaningfully influence how people work, or do most experienced professionals continue to focus on what the situation requires?

And how much do they really matter for promotions and salary decisions? In many cases, the outcome seems to reflect a broader view that has already formed over time.

More broadly, who is the process actually for? Does it genuinely help anyone, or is it mainly a structured way to make the outcome look consistent?

Why Performance Reviews Need Structure

Organizations are not running performance reviews because they enjoy them.

They need a way to make decisions about people that can be explained and defended. Promotions, salary increases, and role changes create expectations and comparisons. Without some structure, decisions would feel arbitrary, even when they are reasonable.

So frameworks are introduced. Competencies are defined. Evaluation criteria are linked to strategy. The intention is straightforward: create a common language that connects individual contribution to organizational goals.

In smaller organizations, this often remains relatively informal. Decisions are based on direct knowledge of people’s work. In larger organizations, distance increases. Not everyone sees everyone else’s contribution in detail, and decisions need to be aligned across teams.

There is a clear logic behind this. When work becomes complex and distributed, structure is introduced to make it more manageable. The result is a system that is less about precise measurement and more about creating a shared interpretation that holds together across the organization.

The question is how well that structure actually captures what is happening in practice.

Why It Can Feel Like Theater

The intention behind performance reviews is reasonable, but the experience can feel different.

On paper, the process looks structured and consistent. In practice, it often feels slightly detached from how work actually happens. Not completely wrong, but not quite aligned either.

The gap comes from a few recurring challenges.

The first is the level of abstraction. The metrics exist, but they are often too high-level to capture how value is created in practice. Different types of contribution can end up competing inside the same category, even though they are not directly comparable.

The second is behavioral. In theory, performance frameworks should guide how people work. In practice, most experienced consultants focus on what the situation requires. Client needs, project constraints, and real-world problems tend to override abstract targets. The evaluation system follows the work, not the other way around.

The third is the link to decisions. Performance reviews are formally tied to promotions and salary changes, but the actual decisions often reflect a broader view: accumulated contribution, reputation, role evolution, and perceived potential. The review summarizes that view, but rarely creates it.

In situations where many people are performing well, the distinction becomes even less precise. When several candidates could reasonably be considered strong performers, the outcome is shaped through discussion rather than measurement. The ability to explain and advocate for a person’s contribution starts to matter. Visibility, credibility, and influence inside the organization can tilt the outcome, even when the formal criteria are the same.

This is where the process can start to feel like theater.

The structure is formal, the criteria are defined, and the outcome is presented as if it follows directly from the inputs. But in reality, much of the decision has already taken shape before the formal evaluation. The review becomes a way to describe and justify that outcome in a consistent format.

Nothing in the process is fake. The work is real, and the decisions are real. But the connection between the two is not always as direct as it appears.

How to Work With the System

Trying to optimize the performance review itself usually has limited effect. By the time the discussion happens, most of the interpretation has already formed.

What tends to matter more is how easy your contribution is to interpret during the year.

This does not require gaming the system. In practice, it often means making the work visible in concrete terms. Not just what was done, but what changed because of it. Connecting your work to outcomes that others recognize, and making sure the right people understand why it mattered.

Some types of work need more translation than others. If the value is indirect, it helps to make the reasoning visible while the work is happening, not only at the end of the year. Short summaries, clear explanations, and shared material tend to travel better than the original work itself.

It also helps to accept the limits of the system. Not everything valuable will be captured perfectly, and not every evaluation will feel precise.

Over time, many experienced professionals adjust their perspective. The performance review becomes less of a measurement and more of a summary of how their contribution has been understood inside the organization.

A More Useful Way to Look at Performance Reviews

Seen this way, performance reviews are not purely theater, but they are also not precise instruments.

They are a structured way to make sense of something that is inherently difficult to measure. They create a narrative that connects individual work to organizational logic, even if the connection is sometimes imperfect.

So performance reviews are not meaningless, but they describe reality rather than measure it.

And in most cases, the underlying pattern remains simple. Contribution that is easier to interpret is also easier to reward.

It does not mean the system needs to be taken too seriously, but it usually makes sense to understand how it works—and make sure your contribution can be understood within it.

📘 Explore the Topic Further

If this perspective resonates, I explore the same theme in more detail in my Senior Expert Playbook series.

The Senior Expert Career Playbook looks at how expert careers actually develop in practice—covering positioning, visibility, and how contribution becomes understood inside organizations.

The Senior Expert Pay Playbook builds on that and explains how compensation typically forms through perceived impact, trust, and structural alignment, not just performance reviews or negotiation.

Together, the books focus on a simple idea: your work matters, but how it is interpreted often matters just as much.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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)

That was a slightly optimistic assumption.

In practice, trust sometimes has to be built in situations where the client is not yet convinced. The logo on the slide deck helps a little, but only a little. After that, it is still your own thinking on the table.

For me, this has happened surprisingly rarely. Most client situations have been very reasonable. But one early experience stayed in mind because it made the dynamic unusually visible.

I joined an identity and access management related assignment for a new client. It involved solution design, that would later lead to implementation. The topic itself was new to me, and I joined the team after the work had already started. That already made life a bit more entertaining. Internally, the situation was not entirely simple either. Some colleagues were unsure whether my background was strong enough for the assignment.

During one workshop, I presented a work plan for my part of the assignment. A client representative reacted quite directly and asked something along the lines of whether those words had been “put in my mouth” by someone else.

Not exactly the warmest possible welcome.

It was never fully clear whether the comment was aimed at me personally, the team, or the proposed approach. But it did not matter that much. The point was clear enough: confidence had not yet been granted.

Situations like that are uncomfortable in the moment, but they are also informative. They show fairly quickly how trust is actually built in consulting work. Usually not through titles, and not by sounding offended, but by making the work hold together under scrutiny.

I no longer remember what I answered in that moment. But I do remember how I continued. I treated the situation as a signal that the topic required deeper grounding from my side. I went through the available material, read relevant standards, familiarized myself with the terminology, and worked through the typical solution structures in that area. I also discussed the topic with more experienced colleagues who had worked with similar solutions before. Nothing particularly dramatic, just careful homework.

At the same time, I started putting more effort into making the material as clear and usable as possible. I prepared structured slides and used regular checkpoints with the client to review progress and direction.

The assignment itself was not unusually heavy, which made this possible without wrecking the rest of life in the process.

Over time, the discussions became easier. The structure became clearer. The conversation moved from whether the approach made sense to how it should be implemented. That is usually a good sign. People stop testing whether you know what you are doing and start using the work.

Later in my career, some of the same client stakeholders purchased additional consulting from me several times.

The initial skepticism did not disappear because I argued better. It disappeared because the work became clearer, more concrete, and consistently usable over time.

That is also the broader point of this article. When clients challenge your expertise, the situation may feel personal, but usually it is more structural than that. They are not only reacting to you. They are trying to reduce uncertainty.

Challenge Is Often Part Of The Role

Clients rarely challenge expertise because they want conflict. Usually they are trying to reduce risk.

Consulting work often takes place in situations where the client has to make decisions under uncertainty. They may be investing money, changing processes, choosing technology, or committing to a direction that will be annoying to reverse later. Accepting an external recommendation means accepting some responsibility for its consequences as well.

Testing the consultant’s reasoning is one way to reduce that uncertainty.

The questions may sound blunt. Are we sure this works in practice? Why is this approach better than the alternatives? Have you actually done this before? Why is this necessary? None of these are especially poetic, but all of them are normal.

Behind the questions is usually a practical concern: what happens if this turns out to be wrong?

Seen from that angle, challenge becomes easier to interpret. It is not necessarily resistance, hostility, or some deep philosophical disagreement. Quite often it is just part of how the decision gets made.

Being Credible Includes Being Questioned

Technical knowledge alone rarely resolves these situations.

Clients are often evaluating more than the proposal itself. They are also looking at how the consultant handles uncertainty, disagreement, incomplete information, and a bit of pressure. In other words, they are evaluating judgment, not only content.

Senior experts are not expected to know everything immediately. That fantasy belongs more to PowerPoint than real life. What they are expected to do is remain reasonably stable when the situation is unclear.

Calm reasoning tends to signal credibility more effectively than defensive argumentation. If the consultant gets irritated every time a proposal is challenged, that becomes part of the message too, and not usually the helpful part.

In many cases, the objective is not to win the discussion. It is to help the client understand the structure of the decision. That may mean clarifying assumptions, making trade-offs visible, acknowledging uncertainty honestly, showing how risks can be managed, and explaining why some options are more robust than others.

Trust often grows when the reasoning becomes visible enough that others can work with it.

Credibility Develops Through Interaction

Credibility rarely appears fully formed at the start of an assignment.

It develops through repeated interactions where the consultant’s thinking proves useful. Clear explanations help. Structured material helps. Consistency helps. Prior reputation may reduce initial skepticism, but credibility is still mostly built through usable thinking in the current context.

None of this is glamorous, which is probably why it works.

Over time, the client starts to understand how the consultant approaches problems and what kind of judgment they can expect. Once that understanding forms, the tone of discussion often changes.

Questions become more collaborative. The client stops mainly testing the expert and starts using the expert. That is a much nicer place to work from.

Internal Skepticism Exists Too

Challenge does not always come only from the client.

Consulting firms do their own quiet evaluation all the time. Is this person the right fit for the assignment? Can they handle the topic? Will the client trust them? Will this become a delivery problem three weeks from now? None of this is especially dramatic. It is simply how commercial organizations try to manage risk.

Sometimes the skepticism stays implicit. Sometimes it is expressed a bit more directly. Either way, the mechanism is usually the same as on the client side: credibility develops through visible contribution.

Support from colleagues matters a lot here as well. A consultant does not build credibility only alone in front of the client. Internal trust, backing, and a few sensible people around you help more than people sometimes admit.

Once colleagues see how someone structures a difficult topic, how they communicate under pressure, and whether the work actually lands, skepticism tends to decrease naturally.

Preparation Usually Reduces Tension

Many difficult client situations become easier once the structure of the topic is clear enough.

Preparation does not always mean knowing every detail. More often it means understanding the landscape well enough to explain what is stable, what varies, what depends on context, what usually works, and what tends to go wrong.

Clients rarely expect perfection. They usually expect clarity.

When the reasoning is visible, disagreement often becomes more constructive. People may still disagree, but now they are disagreeing about something concrete rather than reacting to uncertainty in the abstract. That is already progress.

Disagreement Does Not Mean You Are Losing

One common concern among consultants is that disagreement automatically reduces credibility. In practice, respectful disagreement often increases it.

Clients are rarely looking for agreement for its own sake. They are looking for judgment they can rely on when decisions are difficult. If the consultant agrees immediately with everything, the interaction may feel smooth, but not necessarily useful. There is not much value in a very expensive nodding service.

A consultant who can explain why a certain direction may create risk, or why a tempting shortcut may backfire later, can become a valuable counterweight inside the decision process. That is often part of the role.

Trust grows when the client sees that the consultant is able to think independently while still supporting the shared objective.

What Usually Helps In The Moment

When your expertise is challenged, a few practical patterns tend to help:

• Slow the conversation down. When discussions speed up, misunderstandings multiply. A calmer structure often helps more than a faster reply.

• Make assumptions explicit. A surprising amount of disagreement comes from different starting assumptions rather than different goals.

• Separate the proposal from the person. Critique usually concerns the idea, the model, or the plan. It does not have to become a small identity crisis.

• Acknowledge uncertainty openly. Confidence does not require pretending that uncertainty does not exist. Quite the opposite, usually.

• Show the reasoning path. People often resist conclusions less when they can see how those conclusions were reached.

• Do the homework when needed. Sometimes the correct response is simply to learn the topic better and come back stronger.

• Avoid escalation too early. Most situations improve through clarification, not through hierarchy, sharpness, or theatrical firmness.

Credibility Compounds Over Time

Most consulting careers include a few moments where expertise is questioned more directly than expected.

These situations usually feel larger in the moment than they look afterwards. At the time, it can feel like everything depends on one difficult conversation. Later, it usually looks more like one small but useful part of a longer process.

Over time, repeated experience changes the perspective. Challenge becomes part of normal consultant-client interaction rather than some alarming exception. Trust develops gradually, and one conversation rarely determines the long-term outcome on its own.

Still, each conversation contributes something. It shapes how the expert is perceived the next time, and the next time after that. Credibility accumulates through consistent clarity across multiple situations.

And quite often, the strongest signal is simply this: the work holds up when examined closely.

📕Further Reading: My Books on IT Consulting in Discount

Before you go, a small and fairly intentional promotion: the themes I cover in this Substack originally grew into a pair of books on IT consulting.

Technology Consultant Fast Track focuses on getting into the field: choosing the right companies, preparing for interviews, and understanding what kind of career IT consulting can actually offer.

Successful Technology Consulting is about what happens after that: how to earn trust, act like a professional, keep developing, and build a consulting career that is both successful and sustainable.

In that sense, these books are where much of this topic started for me. And despite not being brand new anymore, they are still very relevant.

Both are now available at $0.99 + tax:

Technology Consultant Fast Track
https://www.amazon.com/dp/B0918JB48D

Successful Technology Consulting
https://www.amazon.com/dp/B0B379SWDR

If you have found this Substack useful, there is a good chance you will find something useful in the books too.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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)

In theory it should. Senior experts have more experience, more judgment, and often more autonomy than earlier in their careers. But in practice, their calendars often become more fragmented and reactive rather than less.

A typical day has been filled before it even begins. The calendar runs the schedule. One meeting ends, another begins, and the short gaps in between disappear into quick messages, Slack questions, or “just a small thing” someone wants to check.

I see this pattern constantly among colleagues and also on the client side. Some experts seem to be involved in almost everything, all the time. Their names appear in meeting invitations across projects and departments.

The reason is simple. As expertise becomes trusted, demand increases. People start routing more questions, decisions, and problems through you.

The challenge is that it can slowly undermine the core of the expert role.

Trust Creates Traffic

Early in a career, most tasks are clearly defined. Someone assigns work, deadlines are explicit, and the scope is usually limited. The calendar reflects this structure. Meetings exist, but much of the time is still reserved for doing the work itself.

If you work as a consultant, you are often allocated a clear percentage to a specific project. You show up in the project meetings, do the deliverables, and move on.

Later, as expertise deepens, the nature of the requests changes. Instead of tasks, you receive questions. Instead of assignments, you receive invitations. Instead of clear deliverables, people ask for opinions.

You may also accumulate formal or informal areas of responsibility along the way. An application portfolio, a capability area, a technology stack, an architectural domain. Things that suddenly need oversight.

The requests usually sound harmless:

“Could you take a quick look at this?”
“Do you have five minutes to comment on this design?”
“Would it help if you joined this meeting?”

Individually, none of these requests are unreasonable. In fact, they are often a sign that your judgment is valued.

But collectively they create a new pattern. Your time becomes a shared resource.

The Calendar Fills From the Edges

Senior experts rarely lose control of their calendars in a single moment. It happens gradually.

One meeting becomes two. A project discussion turns into a recurring session. A quick review expands into a regular checkpoint. A design discussion turns into a steering group. Over time, small fragments accumulate until the day is divided into narrow pieces of time.

This fragmentation changes the nature of the work.

Expert work often depends on concentration. Preparing extensive offers, designing complex solutions, or framing a difficult client problem all require time to think things through properly. When the calendar is full of interruptions, that thinking becomes harder to sustain.

The expert stays busy, but the work slowly becomes reactive.

When Expertise Becomes a Bottleneck

Another pattern appears as senior experts become more central to important decisions.

Projects begin to depend on their presence. Teams feel safer when the expert is involved. Meetings are scheduled around their availability because the discussion might require their input. Without anyone intending it, the expert becomes a bottleneck.

This is rarely a deliberate design. It is simply what happens when the organization learns that certain problems are easier to solve when a particular person is present.

The result is predictable: more meetings, more requests, and less uninterrupted time.

The Structural Reason

This dynamic is not primarily about poor time management. It is structural.

Organizations rely on trusted experts to reduce uncertainty. When something looks ambiguous, inviting a senior expert to the conversation feels like a safe decision. It increases the probability that the discussion leads to a reasonable outcome.

From the organization’s perspective, it makes perfect sense. From the expert’s perspective, it can slowly erode the conditions required for deep work.

The more valuable your judgment becomes, the more often it gets requested.

Why Control Becomes a Skill

Senior experts who manage to protect their calendars don’t simply refuse work. Instead, they shape how their expertise is used.

It usually starts with understanding where their expertise actually creates the most value—and making that visible to others. If everything looks equally important, everything will eventually end up on the calendar.

In practice, it can take several forms.

Sometimes it means participating in fewer meetings and asking others to formulate their questions more clearly before involving you.

Sometimes it means creating structures—documents, models, guidelines, architecture principles—that allow others to move forward without constant supervision or sparring.

Another approach is to change how people access your expertise. Instead of ad-hoc meetings, you might schedule fixed office hours where teams can bring questions. In other cases, you can ask people to send material in advance and give feedback asynchronously.

It also helps to make decisions visible. When architectural principles, solution patterns, or decision records are documented and shared, teams can move forward without repeatedly asking the same questions.

Some experts also protect a few uninterrupted thinking blocks in their calendar each week. Not as a luxury, but as a condition for doing the kind of work their role actually requires.

Delegation also becomes essential. Many senior experts struggle with it. They are used to solving problems themselves and often remain the fastest person in the room. But if everything still flows through them, the calendar eventually collapses under its own weight.

Over time, managing this dynamic becomes part of senior expertise itself: not only solving problems, but shaping how and when your expertise enters the system.

A Different Definition of Control

Control over a calendar rarely means empty space. In expert roles, demand is usually a sign that the work matters.

The real question is whether the expert is shaping that demand or merely responding to it.

Senior expertise often means becoming a scarce resource in the organization. When that happens, time stops behaving like a private asset and starts behaving more like shared infrastructure.

Understanding this shift is often the first step toward managing it deliberately. Senior expertise is not only about solving difficult problems, but also about shaping how your time and judgment are used inside the organization.

Personally, I have rarely felt overwhelmed by calendar invitations. When my calendar is full, the meetings are usually intentional and necessary. In many consulting roles, discussions with clients and project teams are not a distraction from the work—they are the work itself. Reducing meetings for the sake of reducing meetings rarely improves expert productivity. The real question is whether the right conversations are happening with the right people.

But the same structural dynamic still exists: once people trust your judgment, more questions and decisions start flowing your way. Managing how that demand enters your calendar becomes part of the job.

This is one of the structural challenges I explore in my book The Senior Expert Career Playbook. The book looks at why expert careers often become heavier without becoming clearer—and how experienced professionals can build influence, visibility, and sustainable working conditions without drifting into management roles.

If the topic resonates, you can get the book together with the new The Senior Expert Pay Playbook with launch discount. The bundle combines career positioning and compensation positioning into one practical model for senior specialists. Launch price available via my Gumroad store until April 15.

Launch discount codes:

PAYSTRUCTURE22 – The Senior Expert Pay Playbook
EXPERTMODEL22 – Bundle including both books

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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)

In most consulting situations, the setup is quite simple: the consultant recommends, the client decides. Formal authority over the outcome is close to zero. Still, consultants are often involved in discussions where important directions are being set.

That raises a more practical question: why do some experts consistently shape those directions, while others don’t—even when their expertise is similar?

The issue is that the concept gives a slightly misleading picture of when influence actually happens. It suggests that influence takes place during the discussion itself. In practice, most of it happens before that.

Where Decisions Actually Take Shape

Organizations tend to assume that decisions are made in meetings. In reality, the meeting is often just the final step.

Before that, someone has usually already defined what the problem actually is, narrowed down the options, and suggested a first plausible direction. By the time the discussion starts, the room for movement is often smaller than it appears.

That explains a lot. Many experts assume they need to “earn a seat at the table” before they can influence anything. But by the time they are invited in, they are often too late. The role becomes reactive rather than formative.

More senior experts tend to operate earlier. They step in before the situation is fully defined. They don’t wait to be asked what should be done. They propose how the situation should be understood.

In consulting, a practical example is influencing how the client frames the problem before a formal request for proposal is written. Once requirements are fixed, the solution space is already constrained. Earlier involvement often means more opportunity to shape both the direction and the criteria by which alternatives are evaluated.

Influence often begins before the visible decision process starts.

Influence Rarely Looks Formal

A lot of this early influence doesn’t happen in official settings. It happens in short conversations before meetings, quick Slack messages, or someone asking “what do you think about this” in passing. These moments can look informal, even accidental.

In practice, they are often where the direction starts to form.

This is sometimes described as “politics,” but that framing is not particularly helpful. The more practical way to look at it is simple: people align their thinking in small steps, before anything is written down or formally decided.

If you’re only present when the formal discussion starts, you’re already working inside someone else’s framework.

More experienced experts don’t necessarily “play politics.” They just engage earlier, in whatever setting the conversation happens to take place.

Structure Carries More Weight Than Opinion

This leads to another common misunderstanding: influence is not mainly about having stronger opinions.

Opinions are easy to ignore. Another opinion can always be added next to them.

Structure is harder to ignore. When someone lays out the situation clearly—what the actual problem is, what the realistic options are, and what each option implies—the conversation starts to converge. This often begins before anything formal, through early drafts, rough visuals, or initial thinking shared with others.

As a result, people begin discussing the same things in the same terms.

It also signals something else: that the person has thought the situation through. That alone makes it easier for others to rely on it. In practice, clarity tends to be taken as competence.

People rarely push back against clarity. They build on it. And at that point, direction starts to form without much visible effort.

Why the Concept Breaks Down

This is where influence without authority starts to fall apart as a concept.

It suggests that influence happens within an already defined situation. That first there is a situation, and then you influence it. In practice, the biggest leverage comes from defining the situation in the first place.

By the time options are formally discussed, they have often already been tested, clarified, and narrowed down informally.

If you find yourself working hard to influence a decision, it often means someone else has already done that work—they’ve shaped the options and framed the discussion.

What Actually Changes Over Time

Being able to influence without authority is often described as “seniority,” but that word hides more than it explains. The real shift is not about title or years of experience. It’s about when and where you engage.

Early in your career, you are usually brought in to comment on options someone else has defined. Later, you start shaping them. Eventually, you define the frame in which options even exist.

In consulting work, this shows up in fairly concrete ways. Early on, you might be asked to review a proposed solution or give input on a draft. Later, you start outlining what a reasonable solution could look like. At some point, you are no longer reacting to a request—you are helping define the approach, the structure of the solution, and even what the client should be asking for in the first place. The change is subtle but very real.

Over time, it creates a slightly strange effect. By the time a decision is made, it often feels obvious. The options are clear, the trade-offs understood, and the direction almost self-evident.

The influence is real, but it doesn’t look like influence.

Practical Ways to Influence Earlier

If most influence happens before the decision, the question becomes quite concrete: what do you actually do differently?

Here are a few patterns that tend to work in practice:

• Write the first version of the problem statement. Even a rough version shifts the conversation. Others will refine it, but rarely replace it completely.

• Frame 2–3 realistic options early. Not ten. Not one. A small, credible set that people can react to.

• Make trade-offs visible. Cost, complexity, risk, time. Put them on the table early so they become part of the shared language.

• Use simple visuals. A clear diagram beats a long explanation. It also tends to stick.

• Send material before the meeting. Many people form their view in advance. The meeting then confirms it.

• Document decisions immediately after. A short memo often becomes the “official version” of what was decided and why.

• Use informal moments deliberately. A quick chat before the meeting, a short message, or a “sanity check” with the right person can shape how others see the situation. These are not separate from the work—they are often where the initial alignment happens.

• Step in slightly earlier than feels comfortable. If the situation already looks fully defined, it usually is.

None of this requires formal authority. But it does require taking some ownership of the direction earlier than most people do.

In Closing

The idea of influence without authority can be misleading. It’s not really about influencing without power. It’s about where and when that power is applied—and that is usually earlier than it seems.

The influence is real, but it doesn’t look like influence. It mostly looks like clarity at the right moment.

I explore these structural patterns of expert influence in more detail in The Senior Expert Career Playbook, focusing on how expert work actually connects to real decisions inside organizations.

📘Book Bundle for Senior Experts

If the topic resonates, I have written two short books that explore the same theme from a practical perspective:

The Senior Expert Career Playbook, focuses on how expert careers develop without moving into management, including positioning, credibility, and long-term professional direction.

The Senior Expert Pay Playbook continues from there and examines how expert compensation typically forms inside organizations through visibility, perceived impact, trust, and structural alignment.

Together, the books describe how expert value becomes easier for organizations to interpret—and therefore easier to reward.

You can still grab both books as an Expert bundle at the launch price.

Launch discount codes (valid until April 15):

PAYSTRUCTURE22 – The Senior Expert Pay Playbook
EXPERTMODEL22 – Bundle including both books

Available now via my Gumroad store.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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 | The Senior Expert Pay 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)

It did not work that way in practice.

Over time, the work became more complex. Responsibilities expanded, expectations increased, and I was trusted to structure ambiguous situations, support senior stakeholders, and contribute to decisions with wider organizational impact. Compensation adjusted more slowly than the work itself, which made the relationship between effort and reward feel less predictable than expected.

Only later did I realize that the issue was not primarily negotiation technique. Nor does compensation automatically adjust as seniority increases. By the time salary discussions happen, most of the structural perception of value has already formed, often months or years earlier through everyday work and collaboration.

Negotiation often confirms structure more than creates it.

Many senior specialists recognize this pattern. Responsibility grows continuously, while positioning evolves in visible steps that may lag behind the competence development. The gap between the two can last surprisingly long.

What Organizations Actually Evaluate

Organizations rarely compensate effort directly. They compensate contribution that can be explained in terms decision-makers recognize as meaningful.

Managers must justify compensation decisions internally, often across several layers of management. The logic does not need to be mathematically precise, but it must be understandable: this person enables something important to happen faster, with less risk, or with better outcomes.

When the connection between work and outcomes is easy to describe, alignment becomes easier. When the connection requires long explanation chains or depends on several indirect effects, decisions tend to move more slowly.

In my own career, noticeable compensation increases often followed situations where my contribution became easier to interpret in terms of revenue, client value, or business impact. A typical step was working in client situations where judgment had visible consequences for scope, direction, or risk.

The competence had been developing for years, but its relevance had simply become easier to communicate. Clarity tends to move through organizations more easily than effort.

Why Expert Contribution Is Often Hard To See

Many senior specialist roles create value by improving the quality of decisions made by others. This includes structuring ambiguous problem areas, identifying dependencies, clarifying risks early, and helping stakeholders align faster around realistic options.

A solution architect may prevent expensive redesign months later. A consultant may structure a proposal that allows an organization to commit to a direction. A senior expert may help colleagues improve delivery quality across several teams.

The economic impact is real, but the causal chain is long. The value materializes through improved actions by others rather than immediately visible output.

Without explanation, the effect spreads into surrounding work and becomes difficult to isolate. The contribution exists, but it may not appear clearly inside the organization’s decision logic.

Distance from decision-making does not reduce value, but it increases the number of interpretation steps required before the value becomes visible. Each additional step introduces friction.

Why Seniority Alone Does Not Change Position

Competence typically develops continuously through experience, repetition, and exposure to increasingly complex situations.

Still, positioning tends to change more discretely.

In my own career, there were long periods when the nature of the work had already evolved, even though the formal role description had not. The outputs were similar—presentations, models, documents—but the level of judgment required had changed substantially.

Questions gradually shifted from producing individual deliverables toward clarifying direction, dependencies, and risks across a broader landscape of stakeholders and constraints.

Only when this shift became visible in contexts connected to revenue, major proposals, client responsibility, or senior decision-making did compensation begin to adjust.

The competence did not suddenly improve, but the perceived relevance of the competence changed.

How Thinking Becomes Visible Inside Organizations

Visibility is often misunderstood as self-promotion. In practice, the most durable visibility usually emerges from making thinking usable beyond the original context.

Clear deliverables, concise syntheses, and structured reasoning tend to travel further inside organizations than the meetings that produced them. When decision-makers can quickly understand the situation, the contribution becomes easier to recognize and easier to remember later.

Over time, colleagues begin to associate a person with clarity and reliability in complex situations. That association gradually becomes part of how their role is described internally. External visibility can reinforce the same effect. Articles, presentations, and professional discussion often increase perceived credibility internally as well. Recognizable expertise can also create indirect value for the organization, as well-known experts tend to increase trust in sales situations and reduce perceived risk for clients.

In my case, writing has consistently extended the reach of my own thinking. Structured explanations often continue influencing decisions long after the original interaction. Durable thinking creates durable positioning.

Proximity To Decisions Changes Interpretation

Some expert roles operate closer to economic outcomes than others. Work that influences investment decisions, revenue opportunities, or major risk exposure tends to produce clearer signals about its importance. When the connection between expert input and organizational consequences is visible, interpretation becomes easier.

In practice, proximity to decisions often means working relatively close to leadership, either within your own organization or on the client side. Participation in discussions closer to strategic decision-making tend to make the relevance of expert work easier to understand. Typical examples include major initiatives, significant proposals, client responsibility, or strategic prioritization discussions where direction is still open and judgment matters.

Consulting roles illustrate this dynamic particularly well. Consultants often operate near situations where organizations are deciding how to proceed, what to invest in, or how to reduce uncertainty.

In these contexts, the value of structured thinking tends to be more visible, even when the exact financial impact cannot be calculated precisely. Decision-makers can usually recognize when clarity improves confidence, reduces risk, or prevents expensive mistakes. Visibility accelerates recognition.

Practical Ways To Influence Positioning

Positioning rarely changes overnight, but it is not fixed either. Small shifts accumulate when your contribution becomes easier to interpret in situations where decisions are made. In practice, this usually means helping others understand choices more clearly, reducing uncertainty in ambiguous situations, and making the consequences of decisions more visible.

The objective is simple: reduce the effort required for others to understand what kind of problems you help solve and why that matters.

Concrete patterns that tend to help:

• Write short decision-oriented syntheses. Summarize options, trade-offs, and implications so that stakeholders can quickly understand what is at stake.

• Work close to decision situations. Contribute to initiatives where priorities, investments, scope, or risks are actively discussed.

• Structure ambiguous problem spaces. Make alternatives visible when direction is still unclear. Clarity reduces decision friction.

• Make impact visible in practical terms. Connect the work to speed, cost, risk, or delivery confidence, even when exact numbers are not available.

• Support significant initiatives and proposals. Work that influences direction tends to be easier to interpret than work that only documents outcomes.

• Build reliability over time. Consistency creates trust, and trusted judgment carries more weight in uncertain situations.

• Develop internal visibility. Share useful thinking inside the organization through short write-ups, internal presentations, or reusable material that helps others make progress.

• Develop external visibility. Articles, talks, and professional discussion can strengthen perceived credibility internally as well, even when they are not directly linked to a specific client case.

• Let visibility emerge from useful work. Visibility that follows actual contribution tends to feel natural and sustainable.

None of these actions guarantees higher compensation. They simply make contribution easier to recognize and easier to justify. And justification is what organizations ultimately rely on when adjusting compensation.

The Discussion Usually Reflects Earlier Development

Compensation discussions often feel personal, but many of the underlying drivers are structural.

When contribution becomes easier to describe in terms that matter to decision-makers, alignment becomes easier. But when structural position remains unclear, even strong performance may not translate into proportional compensation.

Over time, compensation starts to look less like the result of individual negotiation moments and more like the outcome of accumulated positioning.

A useful question is often not what to say in the meeting. It is rather what needs to be true before the meeting begins.

I explore this perspective further in The Senior Expert Pay Playbook, which examines how compensation forms through structural positioning, perceived impact, and visible contribution rather than negotiation tactics alone. The book focuses on making expert value easier for organizations to interpret and justify, especially in roles where impact is often indirect. Many of the same structural mechanisms discussed here shape both career opportunities and compensation over time.

📘New Book: The Architecture of Expert Compensation

I recently wrote a short book, The Senior Expert Pay Playbook, which looks at how expert compensation actually develops in practice inside organizations.

Instead of focusing on negotiation tactics, the book takes a structural perspective: how role scope, expertise, responsibility, positioning, and organizational context shape long-term compensation.

In other words, it examines the architecture behind expert compensation.

The book includes my salary graph together with a structural analysis of how expert pay can evolve over time.

Recommended reading for IT consultants and other experts interested in understanding how compensation develops beyond individual career moves.

Available now via my Gumroad store.

Launch discount codes (valid until April 15):
PAYSTRUCTURE22 (The Senior Expert Pay Playbook)
EXPERTMODEL22 (bundle with The Senior Expert Career Playbook)

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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 | The Senior Expert Pay 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)

Flexibility.

If I had to point out one of the main reasons things have worked out reasonably well in my consulting career, this would be somewhere near the top of the list. Not the only thing, but one of the few that seems to matter in almost every situation.

What made it interesting in that moment was how easily it gets overlooked. We tend to talk about other things instead.

Traditionally, when discussing what makes a good consultant, the focus is on expertise, structured thinking, communication skills, and familiarity with methods and frameworks. All of these matter, and in many cases they are the entry ticket to the profession. Without them, things become difficult quite quickly.

But they are not what carries you through the day-to-day reality of consulting work. For that, you need something else.

What Flexibility Actually Means in Practice

Flexibility is often interpreted in a fairly narrow way. Plans change, priorities shift, scope evolves, and the consultant is expected to adjust.

That is certainly part of the picture, but it is also the most visible and easiest form of flexibility. It usually comes with a clear signal: something has changed, and you react.

In practice, the more relevant situations are less explicit.

You walk into a meeting expecting to present a well-prepared solution, but quickly realize that the client team is not aligned at all. The discussion you had planned does not really make sense in that context. Or you prepare a structured workshop, only to notice that the participants are more interested in debating basic assumptions than following your agenda.

Nothing has officially changed. There is no new scope or revised timeline.

But the situation itself is different from what you expected.

Flexibility, in this sense, is the ability to notice that difference early enough and adjust your approach without making a big deal out of it. You quietly shift from presenting to facilitating, from leading to listening, or from abstract thinking to something more concrete.

The work continues, but in a slightly different form.

Adaptability as a Core Working Mode

This is where flexibility becomes more concrete. In practice, it shows up as adaptability—the ability to shift your role and way of working depending on the situation. In reality, it is closer to a default mode of operation than an occasional skill.

A consultant rarely operates in a single, stable role. During a single day, you may move from being an expert presenting recommendations, to facilitating a discussion, to structuring messy input into something usable, to doing fairly operational tasks just to keep things moving.

And if your job description looks anything like mine, you are not only shifting between roles, but also between different projects and clients—sometimes several times within the same day. Each of these contexts comes with its own expectations, dynamics, people, tools, and ways of working, and the transition between them needs to happen quickly and without much ceremony.

The value comes from switching between roles and contexts without friction and without making it look like a struggle.

The client does not necessarily notice that you changed your approach. They just experience that something tangible comes out of it. And that is usually enough.

Resilience as Continuous Adjustment

One aspect of flexibility that is easy to overlook is resilience. It is not only about dramatic situations or extraordinary endurance. More often, it is about the ability to continue working effectively when things are slightly off.

Plans change, sometimes repeatedly. The client may not be entirely sure what they want, or their internal alignment may shift during the project. The work itself may not be as clean or well-defined as you would prefer. Despite all this, progress still needs to be made.

Resilience, in this context, is the ability to absorb these small disruptions without losing momentum. You adjust, recalibrate, and continue. There is no need for visible effort or emphasis.

Over time, this quiet persistence tends to matter more than any individual insight or particularly successful meeting.

Managing Your Own Persona

This is where flexibility becomes slightly more personal and, perhaps, a bit uncomfortable to discuss openly.

A good consultant does not bring their personality into every situation in the same way. There is a certain amount of regulation involved.

It does not mean acting or pretending. But it does mean that you are aware of how you come across and what the situation requires.

There are moments where being direct and assertive is useful, especially when decisions need to be made or when the discussion lacks direction. There are also situations where a softer, more neutral approach works better, particularly when the client needs space to think or align internally.

And sometimes, the most effective contribution is surprisingly small. You ask a question, summarize a point, or simply help the group stay on track.

At the same time, there is a boundary that is worth stating quite plainly: consulting is a service profession. The client is paying for a service. That is the starting point.

From that perspective, your personal challenges, frustrations, or moods are not particularly relevant in the situation. They may be completely valid, but they are not what the client is there for. Similarly, your personality should not make the work harder. If your way of interacting creates friction, it reduces your effectiveness regardless of how strong your expertise is.

That said, the opposite extreme is not desirable either. No one enjoys working with someone who feels like a generic, personality-less operator. A certain level of authenticity and natural presence is still important. People trust people, not roles.

The balance is somewhere in between. You remain yourself, but you make sure that the way you show up supports the situation rather than dominates it.

What Flexibility Is Not

At this point, it is worth making one thing explicit, because this is where the idea of flexibility often gets misunderstood.

Flexibility does not mean that you agree to everything or that you simply go along with whatever the client suggests. It is not about being a yes-man, and it certainly does not mean giving up your professional judgment. In fact, that is usually where problems start.

A consultant who adapts to every situation without any internal anchor quickly becomes ineffective. If you do not have a clear view of what makes sense and what does not, there is nothing to adapt in the first place. You are just reacting.

Real flexibility works differently. You keep your direction, your standards, and your understanding of what should be done. What changes is how you get there. Sometimes you push more directly, sometimes you slow down and build alignment, and sometimes you take a step sideways to move things forward indirectly.

In that sense, flexibility is less about bending and more about controlled adjustment. You are not drifting with the situation. You are working with it, without losing your footing.

Why This Matters More Than It Seems

Looking back at different consulting situations over the years, many of the challenging ones were not primarily about complexity or lack of knowledge. They were about applying the wrong approach to the situation at hand.

Pushing too hard when alignment was missing. Holding back when direction was needed. Presenting a solution when the problem was still unclear.

These are not failures of expertise. They are mismatches between the situation and the way you respond to it.

Once you start to see that pattern, the role of flexibility becomes much more visible.

Not as a secondary skill or a nice-to-have quality, but as something that quietly enables everything else to work as intended.

📘 New Book: Why Good Consultants Often Stay Underpaid

I have recently written a short book called The Senior Expert Pay Playbook.

It continues the same structural perspective as The Senior Expert Career Playbook, but focuses specifically on how compensation actually forms in expert roles—especially in consulting environments where contribution is often indirect and distributed across projects, clients, and teams.

Many experienced consultants deliver strong work, build trust, and take on increasing responsibility, yet compensation develops more slowly than expected. Often the issue is not performance or negotiation skill, but structural positioning: how visible the contribution is, how close the role is to value creation, and how clearly the impact can be articulated.

The book looks at these questions from a practical perspective and describes how expert roles can gradually develop stronger economic leverage without requiring a move into management or sales.

The book will be published in early April, but it is already available in my Gumroad store.

A small launch discount is available with the code PAYSTRUCTURE22 (for The Senior Expert Pay Playbook) and EXPERTMODEL22 (for the bundle including both books).

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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)

Over time you begin to understand the organization properly. Decisions stop being abstract. Problems gain context. Instead of just a short diagnostic, you start working on things that actually matter.

Inside the consulting firm, however, the same situation can look quite different. The longer you remain embedded in a client environment, the easier it becomes for your work to fade into the background internally. From the firm’s point of view the engagement is simply running. The client is satisfied, the work continues, and nothing appears to require attention.

For the consultant this can have quiet consequences. When promotion discussions happen, the people making those decisions may have only a vague picture of what you have actually been doing. Salary reviews, role changes, and new opportunities tend to revolve around the work that leadership can easily see and explain. If your most demanding work has been happening deep inside a single client engagement, it may barely appear in those conversations.

I have encountered this dynamic several times in my own career. Early on, I spent two shorter periods—roughly six months each—embedded in client organizations. Later, I had two longer engagements: one lasting about two years and another a little over a year. In all of these cases, I worked closely with client teams and spent most of the time physically in their offices.

From the client’s side, this worked very well. The work required continuity and a deep understanding of the organization, and being present made it easier to support decisions and keep projects moving. Inside my own firm, however, it mostly meant I became the consultant no one needed to worry about.

When the Client Sees You More Than Your Manager

Long client engagements create a particular kind of visibility pattern.

The longer you stay embedded in a client organization, the more people there begin to rely on you. You learn how the tools are actually used, who the key people are, and how work really moves through the organization. Over time you start to understand how decisions happen in practice and where the real risks sit. Gradually you stop being an external advisor and become part of the operating structure around a project or program.

From the client’s point of view, this is exactly what they want. Continuity builds trust. Work becomes easier because fewer things need to be explained and fewer misunderstandings occur.

From the perspective of your own consulting firm, however, something else happens at the same time. You slowly disappear from view.

Not intentionally. Not because anyone is neglecting you. It simply happens because most of your work is happening somewhere else. The client sees you every day, but your colleagues and leadership inside the consulting firm often do not.

Good Work That No One Sees

Consulting firms are structured around a few core mechanisms: sales, staffing, and delivery. These systems work well when projects are visible and moving through the organization regularly.

Shorter assignments naturally create visibility. You meet new colleagues. Different partners and managers see your work. Your name appears more often in staffing discussions—especially if the work involves a new client or an opportunity to expand the engagement.

Longer client engagements behave differently. If you are embedded in a single project for a year or two, the firm’s internal system simply stops interacting with you very often. Staffing becomes automatic. Your utilization looks stable. From the perspective of management dashboards, everything appears to be working perfectly.

You are allocated. The client is satisfied. Revenue flows. There is no problem to solve. Which also means there is little reason for anyone inside the firm to look closely at your role.

Why the System Works This Way

This dynamic is not usually the result of bad management. It’s mostly structural.

Consulting firms optimize for growth through sales and delivery. They pay close attention to things that change: new deals, staffing needs, major client escalations, and expanding accounts. A stable long-running engagement generates fewer internal signals.

If you are doing your work well, the project runs smoothly and the client remains satisfied. From the perspective of the firm’s operating system, that situation requires very little intervention. Ironically, the better the project runs, the less attention it attracts.

Remote work has changed this dynamic slightly. When work happens through shared channels, documents, and calls, it can be easier for colleagues inside the firm to see what is happening in an engagement. In some cases, client work may also take place partly from the consulting firm’s own office rather than entirely on the client’s site.

Even so, long client assignments can still become surprisingly invisible if most of the interaction happens inside the client environment rather than within the consulting firm itself.

The Career Trade-Off

None of this means long client engagements are a bad thing. In many cases, they are the best place to develop real expertise. You gain context that short assignments rarely provide. You see how decisions unfold over time rather than in isolated workshops.

For an expert career, that depth can be extremely valuable. The trade-off is visibility.

While you become more influential inside the client organization, you may become less visible inside the consulting firm that actually manages your career. Over time, it can slow down career movement in ways that are difficult to explain, even though the work is getting harder and more interesting.

Two Practical Ways to Handle It

There is no perfect solution, but a few simple habits can help keep the balance healthy.

First, try to remain visible inside your own firm, not only at the client. Even if most of your time is spent with the client, occasional internal presentations, knowledge sharing sessions, or mentoring can help keep your work visible to colleagues who would otherwise never see it. If nothing else, make a point of talking to senior people from your own firm when they visit the client. And when annual reviews come around, make sure your achievements in the engagement are clearly described rather than assumed to be obvious.

Second, pay attention to how long you stay in one place. Continuity is valuable, but if several years pass inside a single client environment, the consulting firm’s internal network may slowly move on without you noticing. Sometimes a new project is not just a change of work but a way to reconnect your expertise with the broader organization.

Quiet Success Can Still Be Invisible

Consulting often rewards visible momentum. New projects, expanding accounts, and growing teams create signals that organizations understand easily.

Long client engagements create a quieter kind of success. The work becomes deeper, relationships stronger, and outcomes often more meaningful.

But because that success happens inside a single client environment, it can be surprisingly easy for the broader organization to overlook it. And careers, like systems, tend to respond to the signals they can actually see.

I explore these dynamics of expert visibility and career structure in more detail in The Senior Expert Career Playbook.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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)

Why does the same expertise sometimes carry a higher price when it arrives through a consulting firm?

The answer has surprisingly little to do with talent or effort. It has more to do with how value becomes visible.

When Value Has a Price Tag

Consulting makes the connection between work and value unusually explicit.

Every assignment has a price. Every day of work is tied to a billing rate. Someone inside the client organization has approved a budget and decided that this particular expertise is worth paying for. The relationship between contribution and cost is rarely perfect, but at least it exists in the open.

Because of that structure, conversations about value happen naturally. If a consulting engagement costs money, someone inevitably asks whether it is worth it. What did we get from this? Did it help the project move forward? Did it reduce risk, speed up a decision, or solve a problem that would otherwise have stalled progress?

Even when those questions are uncomfortable, they create clarity. The consultant’s contribution must be explainable in terms that make sense to decision-makers. That clarity changes how expertise is perceived.

Internal Expertise Works Differently

Inside organizations, expert work rarely carries such a visible price tag. An internal architect might influence dozens of decisions over the course of a year. A senior engineer might quietly prevent several expensive mistakes. A trusted specialist may help teams structure problems in ways that make execution smoother and less risky.

These contributions can be extremely valuable. In some cases they save far more money than any consulting engagement ever would. But the difficulty is that the connection between the work and the outcome is usually indirect.

Better decisions rarely produce a dramatic event. Prevented problems rarely appear in reports. Structures that make other people’s work easier often fade into the background once they start functioning properly. The work matters, but its value is harder to isolate.

Visibility Changes the Conversation

This difference in visibility affects how organizations talk about expertise.

In consulting, the question is explicit: is this worth the fee? Even when the answer is uncertain, the discussion itself forces the contribution into the open.

Inside organizations, that conversation rarely happens in the same way. Internal experts are already part of the system. Their salaries are fixed costs rather than project decisions. The value they create spreads across multiple initiatives, teams, and decisions, often without a clear moment where someone stops to measure it.

Over time this leads to an interesting dynamic. The same kind of expertise can appear more expensive and more valuable when it arrives through a consulting contract than when it exists quietly inside the organization.

The underlying work may not be different, but the visibility is.

Distance to Decision-Making

Another factor sits quietly behind these differences: proximity to decision-making.

Consultants are usually brought in for moments that matter. A specific IT solution is needed. A transformation needs structure. A decision carries enough risk that someone wants additional expertise in the room. Because of that, consultants often find themselves close to the points where budgets and priorities are discussed.

Internal experts may have just as much insight, but their work can be structurally further from those moments. They operate inside delivery teams, technical domains, or architectural functions that influence decisions indirectly rather than directly.

Over time that distance affects perception. The closer your work sits to budgets, trade-offs, and strategic choices, the easier it becomes for others to connect your expertise with outcomes. This is not unique to consulting, but consulting often amplifies it.

The Hidden Trade-Off

None of this means consulting is inherently better or more valuable than internal expert work. Consulting simply makes value easier to see.

The trade-off is that visibility comes with its own pressures. When every assignment has a price tag, expectations rise quickly. Consultants are expected to produce clear outcomes, explain their reasoning, and justify their presence in ways that internal experts are not always asked to do.

That pressure can be productive. It forces clarity. It also creates a kind of discipline around how expertise is applied.

Inside organizations the incentives are different. The work can be deeper, more continuous, and sometimes more influential over long time horizons. But because the connection between effort and outcome is less explicit, expert careers often evolve more quietly. Sometimes too quietly.

A Structural Difference

Once you notice this economic structure, many familiar career patterns start to make more sense.

Why consultants with similar experience sometimes earn more than internal experts. Why certain kinds of expertise become highly visible in consulting environments. Why internal experts occasionally struggle to explain the value of work that clearly improves the organization.

The explanation is rarely about individual performance. It’s about structure.

Consulting does not necessarily create more value than internal expertise. It simply makes value easier to see.

I explore some of these patterns in more detail in The Senior Expert Career Playbook, where I look at how expert careers evolve inside real organizations.

Author News

Alongside my writing on consulting, expert careers and enterprise architecture, I also work on fiction. My first novel, Pohjoisen tie (The Northern Road), was recently published in Finnish. It tells the story of a daughter trying to understand what happened after her father disappears during a glider flight.

If you happen to read Finnish and are interested, the book is also available directly from the author.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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)

For what it’s worth, I received the “Senior” title more than seven years into my consulting career. By that point, I had already been doing work that looked and felt senior for quite some time. The title simply arrived later, almost as an administrative update. That experience was useful.

It made something clear: seniority and titles do not move in perfect sync. Sometimes the work outpaces the label. Sometimes the label outpaces the work. And sometimes both move independently of what actually matters.

Many experts assume seniority is a natural byproduct of time and effort. Stay long enough, work hard enough, handle enough complexity, and seniority will eventually appear as a logical reward.

It does not work that way.

Time increases exposure. Effort increases capability. Responsibility increases load. None of those automatically produce seniority. In consulting especially, it is possible to accumulate years of experience, a dense calendar, and a reputation for reliability without fundamentally shifting your position in the system. Seniority is not a volume metric.

What Seniority Is Not

Seniority is often confused with intensity, visibility, or volume. In practice, many signals that look like seniority are simply signs of load or reputation. For clarity, it helps to separate them.

• Seniority is not more work. In many firms, the most overloaded people are described as “critical.” They sit in every meeting, handle every escalation, and carry multiple parallel threads. That visibility can resemble seniority from a distance, but it usually reflects operational dependence. The system relies on them to keep things running, not to shape where things are going.

• Seniority is not longer hours. Staying late and absorbing pressure demonstrate commitment. Structural influence, however, shows up in how problems are framed and prevented. When your presence improves decision quality before issues escalate, your contribution shifts from endurance to impact.

• Seniority is not a bigger title. Titles are administrative markers. In some organizations they track influence accurately; in others they lag or inflate. A title can formalize seniority, but it does not create it. Senior work can be done without a senior title, and senior titles can exist without senior responsibility.

• Seniority is not a reward for time served. Years in the field increase exposure and pattern recognition, but they don’t automatically increase influence. Seniority reflects structural position and decision impact, not tenure alone. Experience matters, but only when it changes how value is created and recognized.

• Seniority is not informal heroics. Rescuing projects and fixing crises build reputation and trust. They also reinforce reactive patterns. Seniority changes the structural conditions that reduce the need for repeated rescue work.

• Seniority is not being the most technical person in the room. Deep expertise matters. Seniority, however, is expressed through judgment under uncertainty. The most senior voice often clarifies trade-offs, constraints, and long-term implications rather than displaying the highest density of detail.

What Seniority Is

If seniority is not volume, title, or heroics, what remains is structural position and decision impact. It becomes visible in how your role interacts with uncertainty and value.

• Seniority is structural influence. It appears in who is invited early into conversations and whose perspective reframes decisions. Structural influence means your assessment shapes commitments before they harden into plans.

• Seniority is autonomy under uncertainty. Junior roles operate within defined scope. Senior roles operate where scope is evolving. You interpret ambiguity, define boundaries, and move forward without waiting for complete instructions. Autonomy is paired with accountability for decision quality.

• Seniority is proximity to value. You work close to decisions that affect budgets, direction, risk exposure, and long-term positioning. Your contribution connects to outcomes that matter beyond immediate delivery tasks.

• Seniority is legible judgment. Judgment becomes senior when it is trusted under pressure. Over time, colleagues learn that your assessments hold. Your perspective reduces uncertainty and stabilizes decisions.

• Seniority includes expanded scope awareness. You understand how your domain connects to adjacent areas—technology to business processes, architecture to funding, delivery to long-term maintenance. You are interested in what happens outside your immediate task, because decisions rarely stay confined within one function.

• Seniority is the ability to guide others, even without formal authority. You influence direction through reasoning, clarity, and credibility rather than hierarchy. You mentor junior colleagues, challenge peers constructively, and help teams think more clearly. Guidance does not require a title; it requires trust.

• Seniority is sustainable contribution. A senior expert role compounds. Expertise deepens, networks strengthen, and influence stabilizes over time. The organization benefits from continuity and clarity rather than episodic crisis management.

• Seniority is strategic visibility. It is not about being seen everywhere. It is about being visible in the rooms where direction is shaped. If your contribution never reaches the conversations where direction is decided, it cannot shape outcomes. Seniority is not loudness—but it is presence where it matters.

• Seniority includes knowing your limits. You understand the boundaries of your expertise and your capacity. You recognize when a topic requires deeper specialization, when another perspective is needed, and when additional workload would reduce decision quality. Clear boundaries protect both credibility and sustainability.

Why This Distinction Matters

One common misunderstanding runs underneath many stalled careers: seniority is assumed to mean “more of everything.” More projects, more responsibility, more meetings, more stakeholders, more hours. It doesn’t.

Many consultants chase seniority by increasing output. They take on additional workstreams, join more initiatives, answer more late calls, and become central to multiple threads at once. For a while, that strategy produces visibility and praise. It can even accelerate reputation. Over time, however, it usually produces exhaustion and a subtle plateau. The volume grows, but the position doesn’t.

The shift toward real seniority is qualitative, not quantitative. It requires moving from execution intensity to structural positioning. From being heavily used to being deliberately consulted. From solving problems inside predefined frames to influencing how those frames are set in the first place.

That shift rarely happens accidentally. It requires clarity about what you are optimizing for and which forms of responsibility you accept. Without that clarity, experience accumulates but position remains largely unchanged. You become more capable, yet structurally similar.

Seniority compounds when structure replaces randomness.

Over the past few years, I have tried to articulate this distinction more precisely—what actually changes when senior expertise becomes deliberate rather than incidental. That reflection eventually became The Senior Expert Career Playbook. It is not a guide to working harder or collecting titles, but an examination of how seniority forms inside real organizations—and how to build it without defaulting to management.

If the topic resonates, the book goes deeper.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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)

That is normal. And for a while, it’s even healthy. Consulting, after all, is not a static profession. It is a mix of delivery, client interaction, problem-solving, documentation, facilitation, and sometimes sales support. You might be analyzing requirements one month, coordinating stakeholders the next, and quietly fixing structural issues behind the scenes after that. The role is defined as much by client need as by your title.

In the early years, this breadth is valuable. It exposes you to different industries, operating models, personalities, and pressure situations. You learn how projects actually run, how decisions are made under uncertainty, and how organizations behave when things go wrong. You build resilience and judgment.

But over time, something changes. As your competence grows, your role becomes less about learning and more about responsibility. You are no longer just contributing. You are expected to stabilize, guide, and sometimes rescue. The market may label you a senior consultant, lead, architect, or principal—but what that actually means depends heavily on context.

And unless you start making conscious choices, your role continues to evolve by default rather than by design.

Early Career: Take the Role, Build the Base

When you are new to consulting, the priority is exposure at a very practical level. You need to see how work actually gets done: how requirements are clarified in workshops, how user stories change during development, how test cases fail for unexpected reasons, how integrations break in practice.

At that stage, you are rarely shaping strategy. You are configuring applications, modeling processes, preparing materials, fixing defects, updating slides. It is hands-on. Often repetitive. Sometimes frustrating.

You may find yourself updating documentation when you would prefer designing architectures. You may be running test cycles when you feel ready to lead discussions. You may be sitting in meetings mostly to listen and take notes. That is acceptable—if you are still learning.

At this stage, the focus is grounding. You are building an intuitive understanding of how delivery actually works. That grounding gives weight and realism to more extensive roles and deeper specialization.

When the role starts to feel manageable, it is usually the right moment to expand it slightly. Facilitate one small part of a workshop. Take ownership of a minor issue end-to-end. Present a short status update live instead of sending it by email. Growth does not require a title change. It requires initiative and awareness.

Early on, billability, learning, and progress often align. When you are trusted with real tasks and increasing responsibility, you are building the base. The tension appears only later.

The Moment When Fit Starts to Matter

An unfitting role becomes a problem when learning slows down and frustration becomes constant.

Many experienced consultants remain in roles that once stretched them but now simply consume them—stuck in the same long-running “life sentence” assignment, or doing the same type of work for client after client with only the logos changing. You are handling more responsibility and more complexity, but you are no longer developing new capabilities. The work gets heavier. The cognitive load grows. Yet your expertise deepens only in a very narrow groove, or simply repeats itself in different contexts.

It rarely feels like a crisis. In fact, you may not notice it for a long time. Everything still functions. You are busy. You are trusted. Performance reviews are fine. The absence of growth hides inside apparent stability.

At that point—often only in hindsight—the relevant question shifts from “Can I handle this?” to “Is this building the kind of expertise and positioning I want long term?” If the answer is unclear, you need structured experimentation.

Run Small Career Experiments, Not Grand Gestures

There is no reliable way to design your future role by thinking alone. You need data. And the only way to get data is to try things.

Most experiments do not require changing jobs. They require slightly expanding your exposure.

For example:

• Expand your responsibility. Lead a workshop instead of contributing quietly. Take temporary ownership of a workstream end-to-end. Facilitate a workshop once. Shadow a project manager to understand delivery economics. Embed yourself briefly with a development team if you usually operate at a higher abstraction level.

• Expose yourself to the business side of consulting. Participate in a sales case to see how expertise becomes revenue. Attend a client planning session where budgets are negotiated. Contribute to recruiting interviews. Ask directly for sponsor-level feedback instead of relying only on internal reviews.

• Test your visibility and articulation. Deliver an internal presentation outside your own team. Write one public article about your expertise. Summarize what a project truly achieved beyond delivery metrics and circulate it internally.

• Change context deliberately. Work with a client in a different industry. Move from public sector to private, or vice versa. Take on a project in a new substance area, even if you feel slightly underprepared. Try a short certification in an adjacent field to see whether a new specialization interests you.

• Use mentoring as a diagnostic tool. Find a mentor who operates one level above you and use the conversations to pressure-test your assumptions about direction. Alternatively, mentor a junior colleague and observe how you handle responsibility without formal authority.

None of these require a career overhaul. Most require a conversation and some initiative.

Small shifts reveal preferences surprisingly fast. You might discover that business development energizes you. Or that it drains you. You might find that executive interaction sharpens you—or exhausts you. You might realize that you enjoy shaping direction more than executing predefined tasks.

The point is not to optimize immediately but to shorten feedback loops. It makes little sense to spend three years assuming you would enjoy a certain type of role when you could test a small version of it within three months.

Experiment deliberately. Reflect honestly. Then adjust.

Define the Conditions of Your Work

Career discussions tend to focus on content: what role you want, what title you aim for, what specialization you are building.

The more difficult questions usually surface during job changes.

When you consider moving to a new firm—or when a recruiter calls—the conversation quickly shifts from abstract ambition to concrete conditions. Do you want direct reports? Are you comfortable with personal sales targets? How much travel are you willing to accept? Do you prefer predictable work hours or a variable pace tied to client pressure? Do you want to stay attached to a single account, or move across industries and projects?

These decisions rarely feel dramatic in the moment. They are often framed as practical details of an offer, if mentioned at all. Yet they shape your daily life more than the title does.

The mistake many consultants make is evaluating opportunities primarily through prestige or salary, without clarifying the operating model that comes with them. Two “Senior Consultant” roles can look identical on paper and feel entirely different in practice.

Job changes are therefore the natural checkpoints. If you are not clear about the conditions under which you want to work, you will default to whatever the new environment optimizes for.

Step Outside the Consulting Context

One of the most powerful experiments for an IT consultant is to leave the consulting bubble temporarily.

To work on the client side. Carry actual organization development responsibility. Live with architectural decisions for multiple years instead of recommending them in a PowerPoint presentation.

Consultants who have spent time on the client side tend to develop sharper judgment. They understand organizational constraints differently. They know what implementation pain looks like after the workshop ends.

Some return to consulting with a more grounded perspective. Others stay and become demanding, competent clients. Both outcomes are valuable.

Curiosity, With Boundaries

A certain kind of curiosity is useful in this phase. The willingness to step slightly outside your core specialization and understand adjacent areas.

If you are an enterprise architect, understand at least the basics of configuration and integration realities. If you are a developer, observe how portfolio decisions are made. If you are strategy-focused, spend time in delivery retrospectives. This kind of curiosity strengthens your core.

In any case, spending time in a “basic” software development project before moving into strategy-heavy or architectural roles provides credibility. Strategic advice without delivery experience often lacks weight. When you have seen what breaks in practice, your recommendations become more realistic.

At the same time, not everything needs to be optimized. Some consultants benefit from parallel activities—writing, teaching, entrepreneurship, professional associations. Others simply need something entirely outside IT to maintain balance. Not every interest must become a strategic asset.

Taking Responsibility for the Shape of Your Work

You do not need a perfect plan. Consulting careers are too contextual for rigid roadmaps. What matters is whether you remain purely reactive.

Early on, reacting is appropriate. You take the roles available and build competence through exposure. Over time, however, that same pattern can start shaping you more than you shape it. If you continue accepting assignments without considering their longer-term effect, your expertise will grow—but only in the direction your environment happens to need.

Clarity rarely appears through reflection alone. You cannot know in advance what kind of role or conditions truly fit you. You find out by testing—by stepping into a sales case once, by leading a workshop, by trying a different type of responsibility. Without deliberate experiments, drift can feel like stability for years.

If you do not introduce intention into your choices, the system will do it for you. It will optimize for delivery pressure, revenue, and capacity. Those are reasonable priorities for a firm. They are not automatically aligned with your long-term coherence.

At some point, responsibility shifts. It is no longer only about handling the work. It becomes about deciding which work is worth handling.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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)

On paper, everything looks stable. Utilization is strong. Clients are satisfied. Nothing is visibly broken. In many firms, that is what success looks like.

And yet something feels off.

From the inside, progress often feels static. Titles do not change. Influence does not expand. The role becomes heavier, but not necessarily clearer or more motivating. You are relied upon—but not necessarily moving n the right direction.

This is where structure starts to matter.

So what actually changes when you add it to your career? Not everything. But the right things.

From Allocation to Direction

Early in a consulting career, the primary objective is simple: stay allocated and deliver well. Billability is survival. If clients trust you and project managers want you on their teams, you are doing something right.

And early on, that is a perfectly valid metric.

I recognize this pattern in my own first years in consulting. Being reliably allocated meant trust. It meant competence. It meant I was contributing. For a long time, allocation felt like progress.

The problem is when this becomes the only strategy.

Many experienced consultants spend years embedded in demanding client projects. They handle complexity, manage stakeholders, and quietly absorb risk. Internally, however, they are simply “well allocated.” Stable. Reliable. Safe revenue.

Only later did I realize that stability and direction are not the same thing.

Early in your career, billability is a reasonable proxy for value. At a senior level, it is no longer sufficient. A senior expert must create value that extends beyond their own hours—by shaping decisions, influencing direction, and strengthening the firm’s long-term positioning, not just delivering inside a single assignment.

Adding structure means shifting the question from “Am I billable?” to “Where is this taking me?”

You begin to evaluate assignments not only by their difficulty or visibility, but by how they build the expertise and positioning you want long term. The same project can either deepen your trajectory or keep you stationary. Without structure, it is difficult to see which.

From Senior Resource to Shaping Force

At some point, many consultants become the person who fixes difficult situations. When a program struggles, they are brought in. When a client escalates, they step forward. They are the safe pair of hands.

This is recognition of competence. But it is also a trap.

If your role is defined primarily as “the person who makes broken things work,” you operate inside other people’s agendas. You react to complexity rather than shaping how complexity is approached.

Adding structure means asking a different set of questions. Am I only solving problems thrown at me, or am I influencing how problems are framed? Am I executing decisions, or helping define them? Am I critical to delivery, or relevant to direction?

The difference is subtle but significant. In consulting firms, that distinction often determines who remains a senior consultant and who evolves into a senior expert whose perspective shapes both client and firm-level thinking.

From Invisible Value to Legible Impact

Consulting organizations reward what they can explain. Revenue growth is easy to explain. New accounts are easy to explain. Team expansion is easy to explain. Expert judgment is not.

Much of senior expertise shows up indirectly: better architectural choices, fewer long-term mistakes, avoided risk. From inside the project, this feels substantial. From a leadership meeting, it may look like “steady delivery.”

I have experienced this myself in my architecture assignments. A significant part of the work is simply making implicit things explicit—mapping dependencies that no one had fully articulated and documenting assumptions that were circulating informally. From the client’s perspective, it is valuable. It reduces future mistakes and prevents avoidable complexity. At the consulting firm, however, it can still look like “another stable assignment.” Nothing dramatic happens—because the confusion had been removed before it could turn into a visible problem.

Structure forces you to think about legibility. Where does my work intersect with decisions that matter? Who inside the firm understands its impact? Can someone describe my contribution in one sentence upward?

Legibility does not mean exaggeration. It means translation. There are some simple ways of doing this. Writing a short internal summary after a demanding assignment. Making explicit what was influenced. Connecting your contribution to the firm’s strategic themes—cloud positioning, industry focus, account expansion. Not loudly. Just clearly.

This is not about self-promotion. You cannot compensate for weak fundamentals with marketing. But if your value cannot be connected to something the organization considers strategically important, it remains local, no matter how technically strong it is.

Senior expertise becomes directional only when its impact is understandable beyond the project room.

From Drift to Deliberate Non-Goals

Most consultants are clear about what they want more of: influence, interesting work, recognition, better compensation. Fewer are clear about what they are not optimizing for.

Without explicit non-goals, availability becomes the default posture. You say yes often enough and gradually become central to everything. But central is not the same as directional.

For me, one important shift happened about five years ago. I became clear that I did not want direct reports or personal sales targets. Not because those roles lack value, but because they would pull my attention away from the kind of expertise I wanted to deepen. That clarity simplified many decisions.

Adding structure means defining that kind of boundaries. Perhaps you are not optimizing for headcount management. Perhaps you are not optimizing for pure sales responsibility. Perhaps you are not optimizing for being the emergency fixer in every complex situation.

These decisions reduce noise. They make trade-offs visible. They prevent your calendar from becoming your strategy.

From Randomness to Internal Logic

Many consulting careers evolve through chance. A project needs you. A client trusts you. A reorganization opens—or closes—a door. You move because something looks interesting, not because it fits a deliberate direction.

I know this firsthand. The core area of my own expertise—enterprise architecture—came from a university project I happened to get involved in early on. It was not part of a long-term strategy. It was simply the only opportunity that appeared. I learned the topic deeply because it was in front of me, not because I had mapped out a future role around it.

For a while, this works. Growth feels fast and organic. You build skill through exposure. You say yes to what is available. Experience accumulates.

Then progression slows down, and it becomes difficult to explain why. Nothing is broken. Nothing is visibly wrong. The stepping stones simply stop appearing.

Structure does not eliminate randomness. Consulting will always involve timing, opportunity, and context. What structure introduces is internal logic. It gives you criteria.

Instead of asking only “Is this interesting?”, you start asking whether it strengthens your positioning, deepens your chosen expertise, or increases your influence in a direction you actually care about. Opportunities are no longer taken at face value; they are interpreted through a defined trajectory.

Over time, this reduces drift. A sequence of projects becomes something more coherent. Not perfectly planned—but internally consistent.

Capability Needs Direction

Structure does not replace capability. You still need strong technical competence. You still need consulting skills. You still need trust.

What structure changes is the presence of direction.

That direction does not have to be a ten-year master plan. It does not require a detailed roadmap or a fixed end title. In consulting, too many variables are outside your control for that to be realistic.

What it does require is clarity at a simpler level:

• Clarity about what kind of expertise you want to compound.

• Clarity about the types of problems you want to become known for.

• Clarity about what you are deliberately not optimizing for.

Without that clarity, your career is shaped mostly by context. You move from assignment to assignment, reacting to opportunity, demand, and availability. You may grow in responsibility, but not necessarily in coherence.

With structure, direction does not mean rigidity. It means internal logic. Projects start connecting. Decisions reinforce each other. Your role becomes easier to explain—to others and to yourself.

Effort builds skill. Structure makes sure that skill is moving somewhere. That is what actually changes.

Over the past few years, I started documenting this shift more systematically—what actually changes when senior expertise stops being accidental and becomes deliberate.

That thinking eventually became The Senior Expert Career Playbook. Not as a productivity manual, but as a structured reflection on how expert careers evolve in real organizations, and how to introduce direction without turning into a manager.

If this topic resonates, the book goes deeper.

✍️ Author News

In a slightly different direction, my debut novel Pohjoisen tie (The Northern Road) will be published in Finnish in March 2026 by Momentum Kirjat.

It’s a psychological and adventurous story about loss, family secrets, and the search for answers. A young woman travels deep into the far North—both geographically and mentally—after receiving an unexpected lead about her father’s disappearance years earlier.

Yes, this is somewhat different from my consulting work.

The book can be preordered directly from me, without commitment. Preordering ensures early delivery at a reduced price, with the option of a signed copy.

More details closer to publication.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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)

There were senior people, of course. Very capable ones. But the underlying assumption was simple and rarely questioned: sooner or later, you would move into management. Team lead. Project manager. Account owner. Something with people responsibility, sales responsibility, or usually both. That was what progress looked like. If you were good, you would be “trusted with more”—which usually meant managing others.

If you didn’t want that, things got vague surprisingly fast.

Expert roles existed mostly as transitional states. You were a senior consultant until you became something else. Or until you didn’t, in which case your title stopped changing and your career quietly flattened out. Nobody said it out loud, but the structure was clear enough once you paid attention.

Things are better today. At least on paper. Many organizations now talk about dual career ladders, principal roles, and senior experts. Titles exist. Job descriptions exist. Slides exist.

And yet, many experienced IT consultants still get stuck—often right at the point where their expertise should be most valuable.

This is not a motivation problem. It is not lack of ambition either. And it is rarely about skill. It is a structural issue, and IT consulting is a particularly fertile environment for it.

The Plateau Nobody Warns You About

Most expert careers don’t stall abruptly. They slow down. The work keeps coming. In fact, it often gets more complex and more critical. You are pulled into the difficult client situations, the messy programs, the high-risk decisions. People rely on you. You are trusted. From the outside, everything looks fine—sometimes even impressive.

Inside, progress feels oddly static. Titles stop changing. Responsibility grows faster than compensation. You absorb more risk, make more things work, and fix more problems that never quite make it into status reports. You are “important,” but in a way that is hard to convert into anything tangible for yourself.

This is the point where many consultants start blaming themselves. Maybe I’m not visible enough. Maybe I should network more. Maybe I should say yes more often. Maybe I should finally take that lead role, even if it’s not really what I want.

That advice is common. And it is also often wrong.

Consulting Systems Are Optimized for Managers, Not Experts

IT consulting firms are, at their core, delivery and sales organizations. That is not a criticism—it is just reality. Progress is easiest to measure when it scales: more people, more revenue, larger accounts, bigger teams. Management careers fit this logic well. Expert careers don’t.

Expert impact is indirect. It shows up in better decisions, avoided mistakes, client satisfaction, and long-term coherence. Much of it is invisible unless something goes badly wrong. A senior expert who prevents ten future problems creates less visible “evidence” than a manager who heroically fixes one public crisis.

As a result, expert progression is often vague by design. It relies on judgment, sponsorship, and timing rather than explicit criteria. Even in firms that genuinely value expertise, the structures are usually clearer for managers: how they grow, what they are measured on, and how their compensation evolves.

Expecting such systems to naturally handle expert careers is optimistic at best.

The Quiet Expert Problem

There is a particular type of IT consultant who is especially vulnerable to getting stuck: the reliable one.

They deliver. They don’t escalate unnecessarily. They don’t create drama. Projects tend to run smoothly when they are involved and noticeably worse when they are not. They fix problems early, quietly, and efficiently. Clients trust them. Project managers sleep better when they are on the team.

From a systems perspective, it is dangerous. Organizations are very good at noticing noise, but much worse at noticing absence. When a project explodes, it gets attention. When a crisis is avoided, nobody asks why. Quiet excellence disappears into normality. Over time, the consultant becomes indispensable but strangely invisible at the same time.

If you spend most of your time embedded in a long-running client project that is not strategically important to your own organization, senior leadership may barely notice you at all. You can be doing excellent, demanding work day after day—and still be largely absent from the internal conversations where careers are shaped. From the firm’s perspective, you are “safely billable.” From your own perspective, you are slowly drifting out of sight.

I’ve seen this repeatedly in senior expert roles, and I’ve lived parts of it myself. In my own case, I spent years doing demanding client work with growing responsibility before anything formally changed. Titles lagged behind experience. Seniority accumulated quietly, without clear milestones. Looking back, nothing was “wrong”—but nothing in the system was actively pulling things forward either.

Over time, you accumulate judgment, context, and trust. The shift into true seniority happens slowly and unevenly. There are no clear milestones, no obvious promotion moments. Then, at some point, people suddenly start treating you as “very senior,” almost as if it happened overnight. In reality, nothing sudden occurred. The work simply crossed a visibility threshold where others could finally recognize it.

The problem is that careers often don’t wait for that threshold to be crossed. If you remain quiet, reliable, and fully occupied in non-strategic delivery for too long, the system will happily keep you there. Not out of malice, but because nothing is visibly broken. And systems rarely optimize for things that appear to work just fine.

Overload Is Not Seniority

Another common trap in IT consulting is overload disguised as trust. If you are competent, you get more work. More meetings. More responsibility. More “can you just quickly look at this as well?” Over time, your calendar fills up and your role becomes a dense knot of dependencies. Everything routes through you.

From the outside, it looks like success. Internally, it kills growth.

Senior expertise requires space. Space to think, to connect patterns, to reflect, and to shape direction instead of just responding to problems. Overloaded experts rarely have that space. They may work on complex topics, but the mode is reactive. The work keeps the system running rather than moving it forward.

Over time, this kind of invisible load is not just a career problem. It quietly erodes energy and motivation as well.

There is a cruel irony here: the better you are at handling overload, the more you are rewarded with it. Until, eventually, you are too “critical” to promote and too busy to develop.

Why Randomness Plays Such a Big Role

Looking back, my own expert career was shaped largely by chance. The general area of my core expertise came from my first real job at the university. I didn’t choose the domain strategically—it was simply the kind of work that happened to be available, and I learned to understand it well. From there, my career progressed into consulting through local decisions rather than a long-term plan. I said yes to projects because they were available, not because they clearly moved me in a specific direction. I changed jobs when something felt wrong, or when someone offered something that sounded interesting.

For a long time, it worked. Progress felt real. Only later does the risk become visible. When randomness dominates for too long, progression becomes fragile. You may advance quickly for years and then stall without a clear reason. Nothing breaks, but nothing really moves forward either.

Managers usually have ladders. Experts often have stepping stones floating in fog. As long as the next stone appears, everything feels fine. When it doesn’t, you realize how little structure there actually was.

Some randomness is inevitable. But when it becomes the main driver, your career quietly turns into an outcome of whatever happens around you.

The Real Issue Is Structure, Not Effort

Most IT consultants who get stuck are not lacking in talent, discipline, or work ethic. They are operating in environments that have no deliberate plan for expert growth—and they haven’t built enough structure of their own to compensate.

Doing good work is not enough. Value is always contextual. It exists only in relation to what the organization or client currently recognizes, can explain upward, and is willing to reward. You can solve real problems and still create surprisingly little perceived value if your contribution is not legible at the decision-making level.

This took me a long time to accept. For years, I relied on effort, availability, and a fair amount of luck. I assumed things would somehow sort themselves out. And for a while, they did. Until they didn’t.

The real shift happened when I started treating my own career more deliberately—almost like an architecture problem. I clarified what I was optimizing for, what I explicitly was not optimizing for, and what kind of expertise I wanted to compound over time. Once skill, effort, and energy were no longer the bottleneck, structure turned out to be the missing piece.

I eventually wrote The Senior Expert Career Playbook to make sense of that shift. Not as generic career advice, but as a way to document what actually changed things once working harder stopped helping. I kept seeing the same patterns repeat among experienced IT consultants who were clearly capable, highly trusted—and quietly stuck.

Expert careers don’t stall because experts are less valuable. They stall because value is poorly structured, poorly communicated, and too often left to chance. And unless you introduce some structure of your own, that chance will keep making decisions on your behalf.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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)

The problem is not that these skills are missing. It’s that they are often assumed rather than practiced. Below are five skills that are widely claimed—and much harder to demonstrate consistently in real client work.

1. Listening Without Immediately Solving

For many consultants, the first challenge is simply staying quiet while the client is talking. Not interrupting, not finishing sentences, not jumping in with a solution halfway through the problem description.

A more advanced step comes after that. It is listening without mentally solving the problem at the same time. Without filtering what you hear through a ready-made model, framework, or slide deck. Without silently deciding what the “real” problem is before the client has even finished describing their version of it.

Real listening means allowing vague, messy, or even partially wrong problem descriptions to exist for a while. It means resisting the urge to reframe too early—especially when the reframe happens to match something you already know well.

How to develop it:
In your next client conversation, wait until the other person has clearly finished and then summarize what you heard before offering any solution. If your summary feels almost boringly literal, and you feel slightly impatient while doing it, you are probably listening properly.

It also helps to remind yourself that even a consultant is allowed to say, “Let me think about this and get back to you.” Having an immediate answer is optional. Understanding the question is not.

2. Explaining Without Showing How Smart You Are

Most consultants can explain complex things. For many, the basic challenge is simply not overexplaining. Not adding one more caveat, reference, or edge case “just in case.”

But only few can explain things in a way that does not subtly center yourself (or your company) in the explanation.

Clear explanations require restraint. Choosing simpler words when more complex ones would be available. Leaving out details that are technically impressive but practically irrelevant. Getting rid of the jargon. Allowing the client to arrive at the conclusion slightly on their own, instead of being walked there step by step. If what remains feels thin or awkward, the explanation may have been doing more signaling than clarifying.

This often feels uncomfortable at first. It can feel like underselling your expertise. In reality, it usually does the opposite.

How to develop it:
After explaining something, ask yourself whether it would still make sense without jargon, technical details, or marketing pitches. Then ask whether it would still hold if someone else repeated it five minutes later. If it only works when you are the one delivering it, it probably needs simplifying.

3. Saying “It Doesn’t Matter” (And Meaning It)

Consulting attracts people who like to optimize. The problem is that when everything looks important, nothing really is.

Strong consultants can say, with credibility, that some issues are not worth solving right now. Or at all. This takes judgment rather than analysis. It also means being comfortable leaving potential value on the table, which goes against the instinct to demonstrate usefulness in every discussion.

Often the difficult part is not deciding what matters, but being willing to say out loud what does not.

How to develop it:
In meetings, practice explicitly naming one thing you are not going to focus on and explain why. If it feels slightly uncomfortable to say, it is probably the right kind of prioritization.

4. Staying Neutral Under Pressure

Everyone claims to be objective. Some even manage to stay neutral while the situation is still calm.

The real test comes when neutrality has a cost. When stakeholders disagree, politics surface, money is on the line, or there is quiet pressure to “just support this direction so we can move on.”

True neutrality is not fence-sitting. It is the ability to describe trade-offs honestly even when the room would clearly prefer a simpler story. That often means slowing things down when others want speed, or adding nuance when consensus feels close.

How to develop it:
When presenting options, make it a habit to articulate at least one downside of the preferred option—especially if everyone else seems aligned. Do it calmly, without drama. The goal is not to block decisions, but to keep them honest.

5. Knowing When to Step Back

Many consultants are good at stepping in. The harder part is noticing when continued involvement starts to dilute ownership. When you are still in the room, still answering questions, still smoothing things over—but no longer enabling real learning or independent decision-making.

At that point, staying involved can actually slow things down. Not because the consultant is doing poor work, but because the client never quite has to carry the full weight of the decisions themselves. Things move forward, but they do not always stick.

Stepping back at the right moment requires confidence that your value is not measured only in visibility, slides, or hours billed. Sometimes the most useful thing you can do is to let the client continue without you and see whether the thinking holds on its own.

How to develop it:
At the end of a project phase, ask explicitly whether your role is still needed in the same way. It feels risky. In practice, consultants who do this often help ownership take root—and are trusted enough to be invited back later.

What Actually Makes the Difference

None of these skills are rare in theory. Most consultants recognize them immediately and would say they practice them regularly.

What makes them difficult is not complexity, but context. Time pressure, expectations, client dynamics, and the quiet incentives of consulting work all push behavior in the opposite direction. Toward faster answers, clearer positions, visible activity, and continuous involvement.

That is why these skills tend to fade exactly when they matter most.

Good consulting is less about having the right traits and more about applying restraint at the right moments. Listening a bit longer. Explaining a bit less. Letting some things go. Staying neutral when it would be easier not to. Stepping back before being asked.

These are small choices, but they compound over time. They often separate consultants who are merely competent from those clients genuinely trust. Not because they know more, but because they are more deliberate in how they use what they know.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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 | Technology Consultant Fast Track | Successful Technology Consulting | Kokonaisarkkitehtuuri (FI) | Pohjoisen tie (FI) | Little Cthulhu’s Breakfast Time
Web resources: Enterprise Architecture Info Package (FI)

Underneath that sits another, closely related tension. It is not really about employers or loyalty, but about the consulting role itself: the constant balancing act between integrating into the client’s team and keeping enough professional distance to remain useful.

This article looks at that balance.

Why Integration Is Necessary

Without integration at the client, consulting does not work. You need access, context, and relationships. You need to understand not just formal processes, but also the informal power structures, histories, and sensitivities. You need people to speak openly around you.

Being close to the client is not a flaw. It is a prerequisite.

This is why many consultants aim to become “one of the team.” It reduces friction, speeds things up, and makes everyday work easier. In many long-running assignments, full integration feels like the only realistic way to get anything done.

And often, at least for a while, it works exactly as intended.

Why Distance Is Also Needed

At the same time, consulting does not work without distance either. Not much of it, but enough.

Distance is what allows a consultant to notice things insiders no longer see. To ask questions that feel unnecessary—or even naive—to people who have lived with the system for years. To slow things down when everyone else is optimizing for speed and continuity.

Without some distance, it becomes hard to separate what is from what has simply always been. Structures, constraints, and trade-offs start to look natural and unavoidable, rather than chosen and therefore open to challenge.

This does not mean standing outside the organization or keeping people at arm’s length. It means having a role that is adjacent rather than fully internal. Close enough to participate, but not so close that perspective disappears.

Integration gives access. Distance preserves perspective. Consulting relies on both, even if only one of them is visible in daily work.

When Integration Starts to Erode the Role

Problems begin when integration turns into assimilation. At some point, the consultant stops being adjacent to the organization and starts being absorbed by it. Language shifts. Priorities align. Internal constraints begin to feel self-evident rather than questionable.

When you are fully “one of us,” certain things become harder—not because you suddenly lose honesty or courage, but because the cost of speaking up quietly changes.

Critical comments start to feel disruptive rather than helpful. Questioning long-standing practices means questioning decisions made by people you work with every day. Pointing out problems may sound like criticizing colleagues, not systems. And reminding the organization that your role is temporary can feel awkward when your calendar, identity, and social ties say otherwise.

None of this requires explicit pressure. The incentives are subtle but effective. You want to keep momentum. You want meetings to go smoothly. You want to avoid being seen as negative, theoretical, or “not getting how things really work here.” Over time, it becomes easier to adapt your message—or keep some observations to yourself. The role has not disappeared, but its edges have softened.

Distance Depends on the Role

It is also worth saying out loud that professional distance does not matter equally in all consulting roles.

In execution-oriented work—hands-on IT delivery, implementation, operational support—deep integration is often not just acceptable, but necessary. The value comes from getting things done efficiently inside the client’s setup. In those roles, blending in reduces friction and improves results.

The balance shifts in advisory, design, and strategic work. Here, value comes less from execution speed and more from judgment: framing problems, challenging assumptions, and helping the organization see trade-offs it would rather not look at. In those roles, full integration can quietly remove the very conditions that make that work possible.

Trouble often starts when the same integration model is applied across roles that rely on fundamentally different kinds of value. What enables delivery work can dilute advisory work.

Professional Distance Is Also Structural

This is not just a moral issue. And it is not mainly about backbone or honesty.

Professional distance is structural. It depends on how the role is defined, how success is evaluated, and where feedback comes from. When a consultant is deeply embedded, evaluated mainly by the client, and socially integrated into the team, distance does not disappear because of weakness. It disappears because the role no longer actively supports it.

In that setup, maintaining distance requires swimming against the current. Expecting individual consultants to do that consistently through sheer willpower is unrealistic.

If distance is needed for the role to work, it has to be built into the role itself.

Balancing Without Resolving the Tension

There is no clean solution here. Independence and integration pull in opposite directions, and neither can be maximized without weakening the other.

Too much distance, and you become irrelevant. Too much integration, and you become indistinguishable.

The point is not to resolve the tension, but to recognize it—and to stop pretending it does not exist. For consultants, managers, and consulting firms alike, that means being honest about what long-term embedded work does to roles, perspectives, and expectations.

That said, a few small, practical choices can make the “in-between” position slightly more sustainable:

• One is being explicit about your role, at least occasionally. Not in every meeting, but at the right moments. Saying things like “from an external perspective” or “this may sound obvious from the inside” is not rhetorical fluff. It is a way of reintroducing distance without breaking trust.

• Another is maintaining at least one regular touchpoint outside the client context. A manager, a colleague, or even a peer conversation where you can speak freely without adapting to the client’s internal logic. Not to complain, but to recalibrate.

• A third is noticing what you stop saying. When certain observations keep getting postponed because “now is not the right time,” that is often a signal worth paying attention to. Not necessarily to act immediately, but to acknowledge internally.

None of these remove the tension. They just keep it visible.

The consultant’s job is not to stand outside and criticize. Nor is it to disappear inside the client organization. It is to operate in between. And that, by definition, is not a very stable place to stand.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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 | Technology Consultant Fast Track | Successful Technology Consulting | Kokonaisarkkitehtuuri (FI) | Pohjoisen tie (FI) | Little Cthulhu’s Breakfast Time
Web resources: Enterprise Architecture Info Package (FI)

On paper, it looks like success. The client trusts you. You are deeply embedded. There is continuity, efficiency, and no wasted context switching. Many consulting firms actively aim for exactly this.

What is less often discussed is what happens on the other side of that setup.

Becoming Part of the Client’s Everyday Reality

The first phase is usually pleasant. You learn how things really work. You know who actually makes decisions, which things matter, and which ones only exist in slides. Meetings become easier, communication more informal. You are no longer “the consultant” but simply someone people work with.

If you are physically present at the client’s premises, this effect is amplified. Coffee breaks, hallway conversations, and shared frustrations create a sense of belonging. You start using “we” without thinking much about who it refers to.

From the client’s perspective, this is often ideal. From the consultant’s perspective, it feels like effectiveness. But it is also where a subtle shift begins.

The Consulting Firm Moves to the Background

While your role at the client deepens, your connection to your employer—the consulting firm—often does the opposite. Not because of conflict or disappointment, but because of simple arithmetic: your attention is finite, and most of it is spent elsewhere.

Colleagues are busy on other projects, facing different problems, working in different contexts. There is little time to keep up with internal emails. Discussions happen while you are in client meetings. Development initiatives, informal knowledge sharing, and small cultural moments pass by without you noticing.

Gradually, your consulting firm turns into a background structure. It pays your salary, handles contracts, and reminds you to log hours. Professionally and emotionally, however, your day-to-day reference point is no longer there. The transition is usually so smooth that it is hard to say when it actually happened.

Fewer Touchpoints, Less Visibility

Over time, this distance becomes concrete. You simply meet your own people less. Colleagues, leadership, even your direct supervisor fade into the background of your everyday work. In the worst case, your manager appears mainly in formal development discussions, once or twice a year, trying to reconstruct what you have actually been doing.

Visibility upwards is often limited as well. Client work happens out of sight, by definition. Ironically, being deeply embedded at a client—doing exactly what consulting is supposed to be about—can make your contribution less visible inside your own firm. This can quietly affect career progression, recognition, and future opportunities, even when performance at the client is excellent.

A Shift in Professional Identity

At some point, many consultants realize that most of their professional validation comes from the client. Tasks, feedback, appreciation, pressure, and even stress originate from that direction. The client organization becomes the place where success and failure are defined.

This is not inherently wrong. But it does change how you see your role. The consulting firm is no longer where your professional identity is actively shaped. It is where you are employed, not where you belong in practice.

The risk is not loyalty or disloyalty, but unconscious adaptation. You start optimizing for the client’s internal logic, constraints, and narratives, often without noticing it yourself. This connects closely to questions of professional distance and dual loyalty.

Why This Rarely Feels Like a Problem—At First

One reason this issue often stays invisible is that it does not announce itself as a problem. There is no dramatic conflict, no clear dissatisfaction. On the contrary, things usually run smoothly.

The effects surface later. Engagement with your consulting firm weakens. Interest in its long-term direction fades. Internal initiatives start to feel distant or irrelevant. When people talk about “us,” you may notice that your mental reference quietly points somewhere else.

In more extreme cases, consultants find themselves mentally halfway out the door, without ever having consciously decided to leave.

Naming the Phenomenon Matters

This is not about blaming consultants for “not being committed enough,” nor about accusing firms of poor management. It is a structural consequence of how consulting work is often organized.

A 100 % client allocation is not a neutral arrangement. It shapes professional identity, loyalty, and perspective over time. Ignoring that fact does not make it disappear.

Simply naming the phenomenon already helps. It allows both consultants and firms to think more deliberately about how work is structured, how connections are maintained, and what kind of consulting culture they actually want to build.

Not every problem needs an immediate solution. Some just need to be acknowledged before they quietly do their work in the background.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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 | Technology Consultant Fast Track | Successful Technology Consulting | Kokonaisarkkitehtuuri (FI) | Pohjoisen tie (FI) | Little Cthulhu’s Breakfast Time
Web resources: Enterprise Architecture Info Package (FI)

Organizations are generally good at starting initiatives. A new project signals movement. It shows intent, ambition, and responsiveness. In many cases, this is exactly what is needed. Without that bias toward action, change would stall before it even begins.

This tendency doesn’t stop at strategy decks—it quickly turns into concrete work. From an IT consulting perspective, it is also practical. If organizations like to start things, there will be work to do. New initiatives, new phases, new programs—often addressing familiar problems under slightly different names. That part is not a flaw. It’s how work gets moving.

The more interesting question comes later: not why organizations start so much, but why so few things ever feel clearly finished—and what that means for IT consultants working in the middle of it.

The Real Pattern: Starting Is Rewarded, Finishing Is Not

Organizations are good at starting things because they are built to reward it. Launching a new strategy, program, or IT initiative signals action and responsiveness. It creates momentum, attracts attention, and often unlocks funding. Starting something is visible—and visibility matters in large organizations. It is far easier to justify a new initiative than to explain why an old one should be stopped.

This dynamic becomes particularly visible in IT. Strategic goals tend to materialize quickly as IT initiatives: new applications, platforms, data programs, or large-scale transformations. A kickoff meeting, a roadmap, and a target architecture create an early sense of control over complexity—even though, at that point, very little has actually changed.

Many IT initiatives don’t clearly end. They evolve into follow-up phases, extended roadmaps, or “continuous development.” Something is delivered, but rarely closed in a way that creates a shared understanding of what is done, what remains open, and what should deliberately stop. The work moves forward, but the finish line keeps shifting.

Yes, sometimes IT initiatives struggle simply because the project was poorly set up, under-resourced, or badly led. That happens. But even well-run projects are not immune to the broader pattern.

Finishing requires reflection, trade-offs, and occasionally admitting that the original goal has changed, or was never fully reachable. Those moments are less visible and less rewarding than starting the next initiative. As a result, organizations keep moving, while closure quietly fades into the background.

Why This Matters for IT Consultants

Here’s the slightly uncomfortable part: IT consultants usually recognize this pattern.

We’ve seen how projects stretch, how scopes blur, and how unfinished work quietly turns into the next phase. We also know that this tendency can’t really be fixed at the organizational level—at least not from within a single project.

But consultants do have one important advantage. The projects end for us.

Engagements have boundaries. Contracts expire. Even when the organization continues with the same themes, the consulting work eventually stops. That creates distance—and with it, perspective.

And that perspective comes with responsibility. Not to fix the organization’s structural habits, but to keep our own work honest: to be clear about what was actually done, what was left open, and what should not quietly roll forward just because it’s convenient.

Keeping Your Own Corner Clean

The realistic role of an IT consultant is not to make organizations perfect at finishing things. That would be neither feasible nor credible.

The role is smaller—and more practical. Since consultants recognize the pattern of constant starting and fuzzy endings, the responsibility is to avoid reinforcing it in their own work. Not by forcing artificial closure, but by being deliberate about what the engagement actually does and does not achieve.

In practice, this usually comes down to a few very concrete habits:

• Be explicit about what this project does not resolve. Every engagement has boundaries. Naming them early and repeating them later helps prevent unfinished work from quietly turning into assumed success.

• Help define what “done” means for this specific engagement, even if broader work continues elsewhere. Completion does not have to mean finality. It does have to mean shared understanding.

• Avoid framing continuation as automatic success. Moving on to the next phase is not, by itself, evidence that the current one worked.

• Make open issues visible instead of letting them drift silently forward.
  Unresolved questions age poorly when they are left unnamed.

In short: don’t contribute to the illusion of closure—but don’t pretend everything must be closed either. Keeping your own corner clean is often the most realistic and most useful contribution an IT consultant can make.

A Modest but Meaningful Point

Nothing here is particularly dramatic. Organizations starting more than they finish is not a scandal—it’s a predictable outcome of how large systems work.

The consultant’s contribution is not to fight that tendency head-on, but to be aware of it and act accordingly. To keep at least one project, one scope, and one set of promises reasonably intact.

That may sound modest. In practice, it often makes the next start a lot more sensible.

📚 Related Reads from the IT Consulting Career Hub

If this topic resonated with you, you might also enjoy:

👨‍💻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 | Technology Consultant Fast Track | Successful Technology Consulting | Kokonaisarkkitehtuuri (FI) | Pohjoisen tie (FI) | Little Cthulhu’s Breakfast Time
Web resources: Enterprise Architecture Info Package (FI)

Many Threads, One Calendar

Looking back, 2025 was above all fragmented. Several projects running in parallel, different kinds of deadlines, and an unusually large amount of polishing and closing things off rather than starting something new. Not particularly glamorous work, but absolutely necessary if you want outcomes instead of half-finished initiatives.

In many ways, the year looked less like a clean roadmap and more like a portfolio already in execution mode. Fewer new bets, more responsibility for delivery.

One Visible Milestone, a Lot of Invisible Work

The only clearly visible publication milestone was the release of my English-language enterprise architecture book in October: Enterprise Architecture: Your Guide to Organizational Transformation. By then, the actual writing phase was already behind me.

What followed was familiar to anyone who has ever tried to get something properly out the door: layout comments, detail fixes, coordination, and a surprising amount of marketing work. Not especially interesting, but unavoidable. I spent more time on marketing than in any previous year, and it showed very concretely in my calendar.

When “Almost Ready” Is the Hardest Phase

After the summer, my focus returned to my debut novel Pohjoisen tie (The Northern Road), with a hard deadline in November. This was probably the heaviest single project of the year.

Not because anything essential was missing, but because there was always something that could still be improved. This phase is deceptively expensive: diminishing returns, growing uncertainty, and the constant temptation to keep tweaking. At some point, you have to decide that this version is good enough, and move on.

Parallel Deliverables, Different Audiences

Alongside that, I finalized a children’s nonfiction book about money, built around storytelling, with a deadline at the end of the year. This one required only a couple of editing rounds, as the core writing had been done years earlier.

In the fall, I also took part in a children’s writing competition with another narrative nonfiction manuscript. Earlier in the summer, I published a short English-language children’s book as a self-publishing experiment.

Experiments, Competitions, and Accepting Mixed Results

On the short fiction side, the year was oddly split in two. A school-themed competition, Art Breaks Walls, brought a top-16 placement and an anthology publication for a text that came together with surprising ease. That was the clear highlight.

At the same time, an atmospheric horror story didn’t place in either Nova or Portti (established Finnish speculative fiction writing competitions), despite being one I personally liked quite a lot. On the brighter side, a short story combining Cthulhu with politics—originally started back in 2023—finally seems to have found a home for 2026. Towards the end of the year, I wrote one more competition entry.

Writing as Ongoing Professional Practice

Writing didn’t stop at books or fiction. I published four articles in Juomaposti (Finnish publication focused on beverages, drinking culture, and related industry topics), wrote weekly for my Substack newsletters, and kept LinkedIn active. Along the way, I also started writing on Medium—mostly about writing itself.

Much of the work never shows up as a single publication: website updates, marketing materials, presentations, and similar background tasks. Marketing took noticeably more time than in earlier years, but at this stage it felt like a justified investment rather than a distraction.

Choosing Not to Start Something New

What I didn’t do was start any entirely new book-length writing projects, either fiction or nonfiction. Ideas certainly existed, and I even pitched one of them to a publisher. It didn’t move forward—too B2C-oriented for their list—which was a sensible call. There was already more than enough in flight.

A Solid Year, Without a Grand Finale

So how did the year go? From my own perspective: quite well. There was a lot to do, and a lot got done, even if there wasn’t a single obvious finish line or triumphant moment. In hindsight, 2025 feels more like a year of building, consolidation, and preparation than one of visible breakthroughs. And that’s fine.

None of this would have been realistic without a four-day workweek. Without that structural decision, pushing this many parallel efforts forward simply wouldn’t have worked.

What Comes Next

What’s next, then? In March, my debut novel will be released by Momentum Kirjat. In the summer, the children’s nonfiction book will follow with Aviador. There’s also an interesting new nonfiction idea in the back of my mind—but we’ll see what it turns into, if anything.

👨‍💻About the Author

Eetu Niemi is an enterprise architect, consultant, and author.

Follow him elsewhere: Homepage | LinkedIn | Substack (enterprise architecture ) | Medium (writing) | Homepage (FI) | Facebook | Instagram
Books: Enterprise Architecture | Technology Consultant Fast Track | Successful Technology Consulting | Kokonaisarkkitehtuuri (FI) | Pohjoisen tie (FI) | Little Cthulhu’s Breakfast Time
Web resources: Enterprise Architecture Info Package (FI)