“Could I ask one quick question?” is the natural predator of the consultant’s carefully planned day.
The question may take only ten minutes to answer. But that is rarely the full cost.
First, you stop what you are doing and shift your attention to the client’s problem.
Then you locate the relevant email, reopen the project files, check an assumption and work out what has changed since the last conversation.
You provide the answer, perhaps with a short explanation to prevent misunderstanding.
Then you return to your original task and try to remember where you were.
The ten-minute question may have consumed 30 or 40 minutes. More importantly, it may have broken a block of concentrated work that cannot easily be reconstructed.
This is invisible consulting work.
It rarely appears in the programme, proposal or scope. It may not be recorded on a timesheet. But it consumes real capacity and disrupts the work the consultant has already promised to deliver.
Technical consultants are particularly vulnerable because we want to be helpful. We know the answer, or we know how to find it, so responding immediately feels like good client service.
Sometimes it is.
But when every request is treated as urgent, the consultant’s week becomes a collection of other people’s priorities.
Reliable consultants do not need to ignore clients. They need a clear way of managing access.
That might include:
- agreed response times
- scheduled check-in calls
- a shared list of non-urgent questions
- defined channels for genuinely urgent matters
- a clear process for requests outside the current scope
Responsiveness is not the same as immediate availability.
A reliable consultant protects enough focused time to provide the thoughtful answer the client is actually paying for.
How many “quick questions” entered your week without ever appearing in your plan?
The Reliable Consultant, practical observations for technical professionals building independent consulting practices.