There are two ways to make a colleague uncomfortable while sharing your screen. One is to reveal a browser tab you meant to close. The other is to reveal 12,486 unread emails.
For some people, that number is a cry for help. For others, it is simply where the emails live. Somewhere nearby, an Inbox Zero enthusiast is archiving a webinar invitation with the quiet satisfaction of someone restoring order to civilisation.
I’m less interested in who has the tidier inbox than in who remembered the commitment they made to the customer. In Solutions Consulting, I would rather have a well-prepared discovery conversation and a few unread newsletters than a pristine mailbox and no idea what tomorrow’s demo is supposed to prove. Yet email counts, packed calendars and instant replies are tempting ways to judge a working day. They are visible. Whether we helped someone make a better decision takes more thought.
Inbox Zero was never supposed to be a competitive sport
First, a small correction in defence of Inbox Zero. Merlin Mann’s own explanation makes clear that the “zero” is about the attention we give our inbox, rather than a permanent absence of messages. Spending hours emptying it at any cost misses his point. The intention is to stop email occupying your head while you are trying to do something else.
That seems entirely reasonable. The trouble begins when an empty inbox becomes the achievement itself. Archiving a customer’s question does not answer it. Moving a difficult request into a folder called “Action” does not give it an owner or a deadline. It does, however, make the inbox look reassuringly clean.
The opposite approach needs scrutiny too. “I can find everything with search” is a reasonable filing strategy, but a questionable way to remember promises. Search helps when you know what you are looking for. It is less helpful when you have forgotten that you owe someone a response.
There is a useful distinction in the research here. In a 2011 study, E. J. Masicampo and Roy Baumeister found that making specific plans for unfinished goals eliminated the cognitive interference effects they measured. Participants did not have to finish everything first. That is not proof that any particular email system works, but it suggests a more useful goal than “clear everything”: know how you will deal with what remains.
My practical translation would be to give customer commitments a next action and a review date somewhere you actually check. “Customer follow-up” is vague. “Confirm the integration requirement with engineering on Thursday, then update the customer” gives you something to do. Whether the original email stays in the inbox is a much smaller decision.
Being available is part of the job. Being interruptible all day needs a discussion.
Solutions Consulting is customer-facing work. Sometimes the account executive needs an answer now, the demo environment breaks before a call, or a technical clarification is holding up a decision. A productivity method that assumes we can disappear for four hours every morning has not met the calendar.
Still, there is a difference between handling an urgent request and checking Teams halfway through every paragraph. Sophie Leroy’s research on attention residue examined how attention can remain attached to a previous task after switching, affecting performance on the next one. You do not need a universal “multitasking costs 40%” statistic to take that seriously. Reading a customer’s architecture diagram while composing an unrelated reply gives two demanding tasks a claim on the same attention.
Imagine a discovery call where you are also clearing email. You catch the product names, but miss the hesitation when someone explains who owns the implementation. Later, the demo answers the technical requirements beautifully and completely misses the organisational problem. The email you answered was probably excellent.
I would aim for predictable availability: agreed windows for routine responses, a clear route for genuinely urgent requests, and protected preparation time that the team understands. “I’m preparing tomorrow’s workshop until 11; call if the live customer session is blocked” is more useful than either permanent silence or permanent interruption. The exact arrangement should fit the role, the time zones and the commitments we have made.
A colourful calendar can still contain a badly designed week
I have no objection to colour-coded calendars. If purple helps you see that you have left no time to prepare for six customer meetings, purple has done its job. The problem is treating the completed calendar as evidence that the work is under control. A block labelled “Focus” still needs a purpose, and someone still has to defend it when another invitation arrives.
Microsoft’s 2025 “infinite workday” report found that 48% of surveyed employees described their work as chaotic and fragmented. You may also have seen its claim about interruptions every two minutes. The methodology matters: that calculation concerned the top 20% of users by incoming ping volume, and the telemetry excluded EU and education tenants. It counted incoming communication events, not individually observed losses of concentration. It should not become a universal fact about every knowledge worker.
For a consulting team, I would start with a more local question: where does preparation actually fit? Six calls with no room to capture decisions or test the next demo are six calls with unfinished work attached. Booking every gap simply moves that work somewhere else, often into time that was never supposed to be available.
Nor would I declare war on meetings. Discovery, coaching and resolving an ambiguous customer requirement can deserve a conversation. A status update may work perfectly well in a shared note. Before sending an invitation, ask what needs to be different afterwards. If the answer is a decision, make sure someone who can make it will attend. If it is simply awareness, consider whether everyone needs to acquire that awareness simultaneously.
Asynchronous work needs the same discipline. A useful request explains the context, the decision needed and when a response is due. Otherwise, we have merely converted a vague meeting into a vague thread with a longer lifespan.
Your task manager should not require its own task manager
There is an enjoyable stage of adopting a productivity app where everything seems possible. The projects have icons. The dashboard has views. You have created a category called “Strategic”, and for a brief moment this feels very close to having a strategy.
I would judge the setup by what it helps you remember and finish. Can you find your next action without searching five places? Can you see what is waiting on someone else? Will it remind you of the customer commitment when the week becomes messy? A sophisticated tool may earn its place, especially when a team needs shared ownership and visibility. Complexity should have a job.
Cal Newport’s 2024 book, Slow Productivity, offers a useful alternative to endlessly optimising the list: “Do Fewer Things; Work at a Natural Pace; Obsess Over Quality.” This is a proposed approach to work, not experimental proof of a perfect system. What I find useful is the permission to question how much work we have started.
Applied to Solutions Consulting, that could mean agreeing which evaluations actively need our attention this week, which are waiting for customer input, and which should not start yet. A paused opportunity should have a reason and a review point. It should not keep generating preparation work simply because nobody has explicitly paused it.
That also changes the conversation about new requests. Instead of “I’ll squeeze it in”, try “I can prepare that custom demo by Friday if we move the internal enablement session. Which matters more?” The workload becomes a decision we can make together. No new subscription required.
AI makes the question more interesting, not less necessary
AI deserves a place in this discussion because its benefits are measurable in some settings. In Generative AI at Work, researchers studying 5,172 customer support agents found an average 15% increase in issues resolved per hour with AI assistance. The benefits varied substantially, with less experienced and lower-skilled workers gaining more. That is evidence of a useful application, rather than a promise that every consultant will finish every task 15% faster.
Another field experiment, Shifting Work Patterns with Generative AI, covered 7,137 knowledge workers across 66 firms. Its November 2025 revision reports that, in the second half of the six-month experiment, workers who used the provided tool spent two fewer hours on email each week. Beyond individual time savings, the researchers did not detect changes in the quantity or composition of tasks. Giving individuals a faster tool did not automatically redesign their work.
For an SC, my starting point would be a bounded task: turn approved discovery notes into a draft follow-up, suggest questions to investigate, or help adapt a demo script. Then check the output against the source material and the customer’s actual situation. A confidently invented requirement is still invented, even when it arrives in a very attractive table.
I would measure the whole job, including checking and correcting the result. Did we produce an accurate follow-up sooner? Did the draft help us notice a missing question? Or did we generate five pages that somebody now needs to reduce to five sentences? It is perfectly possible to automate the writing of an email that would have been better left unwritten.
The part we cannot fix with personal discipline
The productivity advice I find least convincing assumes that everyone has enough control to apply it. Protect your mornings. Decline more meetings. Switch off notifications. Sensible options, perhaps, but who decides whether those choices are acceptable? If a manager expects an immediate reply, an employee’s focus block is a request for permission disguised as a calendar entry.
Simon Sinek puts it neatly: “Working hard for something we love is called passion.” I like the reminder to care about the work. I would be wary of using it to explain away an overloaded team, though. Meaningful work still needs realistic commitments. Enthusiasm is not a staffing plan.
For me, the management responsibility is to make priorities credible. If a new evaluation becomes urgent, say what can wait. If preparation matters, give it room in the schedule. When someone identifies a poor fit early and saves the customer and the team a pointless proof of concept, recognise the judgement involved. Counting demos alone would miss that contribution.
A useful experiment would be to change one part of the working week for a fortnight. Agree response expectations, protect a preparation block, or reduce the number of evaluations being actively worked. Then look at missed commitments, avoidable rework and whether customer conversations were better prepared. Ask the team what happened. Treat the result as local evidence to learn from, rather than a new rule for everyone.
On Friday, I would rather discuss why a customer now understands the implementation trade-off than celebrate how many messages we archived. And if that conversation happens over a shared screen showing 12,486 unread emails, I can live with it. I may still ask where you keep the follow-ups.
