Surviving Context Switching as a Consultant

When one long project turns into seven parallel assignments, memory and good intentions are no longer enough

Jun 18, 2026

There was a time when I worked on one project at a time. Sometimes for months. Sometimes for years. I knew the client, the people, the applications, the politics, the acronyms, and which coffee from the machine was the safest option.

Looking back, that now feels like a luxury product.

These days, my work looks different. At the moment, my personal record is seven billable assignments at the same time. Most of them are for different clients. Different organizations, different goals, different people, different tools, different problems, and naturally, different ways of explaining why the same three things are urgent. On top of that, there is proposal work, administration, internal development, and all the other small things that seem to increase quietly in the background.

That is consulting. At least one version of it.

The hard part is not only the workload. It is the switching. One moment you are discussing enterprise architecture governance with one client. Thirty minutes later you are co-modeling a process for another. Then you work on an offer. After lunch, you design solution architecture for a third client. Then comes an offer review meeting. At some point, there is a quick internal discussion where someone asks, “Do you remember what we agreed with the other client?”

Of course you remember. You are a professional.

You just need a few seconds, your notes, and possibly a small miracle.

The Problem Is Not Having Many Things to Do

Having many things to do is normal. Most professionals live with that. The real problem is having many different contexts that all require a different mental model.

Each assignment has its own internal logic. The client organization has a certain way of making decisions. The project has a history. Certain people are important, even if they are not officially important. Some topics are sensitive. Some words mean one thing in one organization and something completely different in another.

This is where context switching becomes expensive. You cannot just jump into a meeting. You have to reload the environment in your head.

What is this client trying to achieve? What did we discuss last time? Who was worried about what? What was I supposed to deliver? Why is this diagram called final_final_v3, and why do I already know it is not final?

Your brain cannot really multitask. It can switch quickly between things, but each switch has a cost. The previous topic does not disappear politely when the next one starts. It stays in the background, making small noises. Meanwhile, the new topic expects full attention immediately.

Some people are naturally better at this than others. They seem to move from one client to another with very little visible loading time. I am not sure whether it is a skill, a personality trait, or just better acting. In any case, context switching can also become harder with age. At least I have noticed that I appreciate my notes more now than I did earlier in my career.

Build External Memory

The first survival mechanism is simple: stop trusting your memory.

It is not a sign of weakness. It is a sign that you have learned something about consulting and possibly human biology. When you work with several clients at once, memory becomes unreliable. You may remember the substance, but forget the context. You may remember the decision, but forget who made it. You may remember that something was urgent, but forget whether it was actually urgent or just said in an urgent voice.

I write things down. A lot of things.

Usually I write them down almost as I hear them. Manually. I do not use a sophisticated personal knowledge management system with tags, graphs, and a weekly ritual. I mostly use Notepad++. It is not beautiful, but neither are most meeting notes. The point is to capture what was agreed, what remains open, who owns what, and what I need to do next.

I do this regardless of whether an official memo is required. A meeting memo is for the project, the client, or the wider group. My notes are for my own ability to continue working without reconstructing the whole situation from memory. These are related things, but they are not the same thing.

Create Landing Pages for Each Assignment

When there are many assignments, every client needs a landing page in your own working system. This can be a OneNote page, a Word document, a folder, or just a plain text file. The tool matters less than the habit.

For each assignment, I want to have the basics in one place: scope, objectives, stakeholders, key links, recurring meetings, deliverables, open issues, and my own interpretation of what is really going on.

That last part is often the most valuable. Official project material tells you what should be happening. Your own notes tell you what is actually happening.

Before a meeting, I open the landing page and reload the context. After the meeting, I update it. It sounds boring because it is. It also works, which is a respectable quality in a working method.

Keep a Master Task List for Each Assignment

Notes are useful, but they are not enough. Each assignment also needs a task list.

I keep master task lists for my assignments, even when the client already has Jira, Planner, Excel, or some other system for managing work. Those tools are useful for the project. My own list is useful for me. It contains the things I personally need to remember, prepare, check, send, ask, or quietly worry about.

My method is simple. I often keep the task list as an Outlook calendar reservation with free status. If I do not finish the items, I move the reservation forward. It is not an elegant productivity system. It is more like placing a physical object in the corridor so you cannot walk past it forever.

The benefit is that tasks stay connected to time. A task list in a document is easy to forget. A calendar entry appears in front of you at the wrong moment, which is still better than never.

This also helps with context switching. When I return to an assignment, I can see not only the previous notes but also the concrete next actions. It reduces the empty staring phase at the beginning of work. Empty staring has its place, but usually not when the next meeting starts in eleven minutes.

Reduce Switching Where You Can

Some context switching is unavoidable. Some of it is self-inflicted.

The calendar is usually the first battlefield. If every day contains five clients, six topics, and one attempt to eat lunch while reading Teams messages, the week becomes mental porridge.

I try to group work by client or by type of task when possible. Client A in the morning, Client B in the afternoon, or Client C for the whole day. Writing or modeling work in longer blocks. Administrative work in one pile, where it can disappoint me efficiently.

That is not always possible. Consulting calendars have their own weather systems. Still, even a little grouping helps. One two-hour focused block often produces more than four scattered half-hours between meetings.

The goal is to manage switching—and to stop treating your brain like a shared server with unlimited users.

Make Starting Easy

The most dangerous moment in context switching is the first five minutes. You open the wrong folder, search for the right document, read three old emails, remember another task, answer a message, and suddenly the meeting starts. You are present physically, but mentally still somewhere else.

This is why every assignment should have an obvious next step.

When I stop working on something, I try to leave a small marker for myself: continue from here, update this diagram, send this question, review these comments. Often I do this with calendar reservations. The reservation gives me a place to continue and a reminder that the work still exists.

It is also worth preparing before meetings properly. Not dramatically. Just enough. Open the notes, check the previous decisions, look at the agenda, and remind yourself what role you are supposed to play in that discussion. Jumping directly from one meeting to another may be unavoidable at times, but it is rarely ideal. You need at least a small mental airlock between contexts.

Otherwise you may start the next meeting with the wrong client in your head.

Protect the Quality of Your Thinking

The risk in many parallel assignments is that you become reactive. You answer messages, attend meetings, produce slides, update diagrams, and keep all plates spinning. From the outside, it can look productive. From the inside, it can become a slow erosion of thinking.

Consultants are paid for expertise, judgment, structure, and communication. Those require actual thinking time. If your week contains only meetings and micro-tasks, the quality of your work will eventually suffer, even if your utilization rate looks excellent. Especially then.

I try to reserve time for synthesis. What is the real problem here? What should the client decide? What is missing from the picture? What is the simplest way to explain this?

This is often where the value is created. Not in attending the tenth meeting about the same topic, but in making sense of the mess between meetings.

Use AI as Support, Not as a Substitute

AI can help with context switching, but it does not remove the need to understand the context yourself.

I use AI where it makes sense: to structure rough notes, draft meeting summaries, turn messy thoughts into clearer text, or help prepare for a discussion. It can be useful when your head is still partly in the previous assignment and you need to quickly organize what you already know.

But AI is not a place where you outsource professional judgment. It does not know the client’s internal politics, the history behind a decision, or why one innocent-looking sentence in a steering group slide may cause a small organizational weather event. You still need to know what you are doing.

There is also the obvious but important issue of confidentiality. Client information, sensitive project material, personal data, commercial details, and internal discussions cannot just be copied into any tool that happens to have a text box. Use approved tools, follow client and employer policies, and anonymize or generalize content when needed.

In consulting, trust is part of the product. Losing it because of careless tool use would be an impressively modern way to create an old-fashioned problem.

For me, AI works best as a thinking assistant. It can help clean the table, but it should not decide what is served for dinner. The responsibility stays with the consultant.

Accept That Some Friction Is Part of the Job

Even with good notes, clean folders, task lists, and a well-managed calendar, context switching remains tiring. There is no magical productivity method that turns seven assignments into one peaceful long-term project.

Some days will feel fragmented. Some transitions will be clumsy. Sometimes you will need to read your own notes and wonder who wrote them. Then you realize it was you, yesterday, apparently with confidence.

That is fine. The goal is not to feel perfectly in control all the time. The goal is to create enough structure that the work remains professional, the clients get value, and you still have a functioning brain at the end of the week.

In consulting, context switching is part of the craft. You cannot avoid it completely, but you can become better at landing, taking off, and carrying the right mental luggage to the next meeting.

And when you get another long, single-client project someday, enjoy it. It is not just an assignment. It is almost like a spa treatment.