There is a particular kind of Monday morning that operations leaders know well. The consultant is due at nine. The invite went out on Friday. Someone has booked a meeting room and ordered extra coffee, and there is a general sense that things are about to get clearer. By Wednesday, however, the mood has shifted. The consultant is still asking questions that should have been answered on day one. The finance director is unavailable until next week. The process documentation everyone assumed existed turns out to be a set of handwritten notes in a binder no one can locate. A week of expensive time evaporates into orientation. This does not have to be the pattern. The quality of a consulting engagement is largely determined before it begins — by the care, honesty, and specificity that go into the brief, and by how well the organisation prepares the ground for the person it has hired to walk across it.
The Brief Is Not a Wish List ¶
A vague brief sounds like this: we need to improve our operations and get more efficient. A useful brief sounds like this: our order fulfilment cycle currently averages eleven days from confirmed purchase to dispatch, our target is six, and we believe the bottleneck sits somewhere between the warehouse pick process and the carrier booking system, though we have not been able to isolate it ourselves. The difference is not just clarity — it is respect for the engagement. A consultant arriving to a vague brief must spend the first week constructing the map that the client should have handed over at the door. Named constraints, named systems, named timeframes, and a frank account of what has already been tried and why it did not hold: these are the materials from which a good engagement is built. The brief is a act of trust, not a performance of ambition.
Documents That Actually Matter ¶
Not every organisation has polished documentation, and that is fine — a consultant worth hiring has seen worse. What matters is gathering what genuinely exists, rather than what sounds impressive. The most useful documents to prepare are: the current organisational chart, even if it is out of date, annotated with a note about where it no longer reflects reality; any process maps or standard operating procedures that front-line teams actually use, not the ones written for an audit; a snapshot of the last twelve months of relevant performance data — throughput, error rates, headcount changes, cost per unit, whatever the operation measures; and the most recent internal review, post-mortem, or board presentation that touched the problem area. A two-page summary of what the leadership team believes is true, written plainly, is often worth more than a fifty-slide deck assembled to impress.
The People Who Need to Be in the Room ¶
Consulting engagements stall most often not because of missing data but because of missing people. Before an external consultant arrives, operations leaders should confirm the availability of three kinds of person. First, the decision-maker who can authorise a change if the consultant recommends one — if that person is travelling for the first three weeks, the engagement should probably start later. Second, the process owner closest to the problem: the warehouse manager, the customer service team lead, the finance analyst who actually runs the month-end close. These are the people who hold the tacit knowledge that no document captures. Third, at least one dissenting voice — someone inside the organisation who has doubts about the project, who thinks the diagnosis is wrong, or who tried something similar before and watched it fail. That person's perspective is not an obstacle; it is primary source material.
What a Good Kick-Off Meeting Looks Like ¶
A well-prepared kick-off is not a presentation to the consultant. It is a calibration. The operations leader walks through the brief as written, then invites the consultant to surface what is missing or surprising. Time is set aside — genuinely set aside, not squeezed into the last ten minutes — for the consultant to ask questions that may feel uncomfortable. Why was the previous attempt abandoned? Who in the organisation is resistant to this work and why? What outcome would constitute failure in the eyes of the board? A good kick-off ends with a shared document: a one-page statement of the problem, the scope, the constraints, the access that has been granted, and the first milestone. If that document cannot be written by the end of the first meeting, the brief is not yet ready.
Access, Systems, and the Small Logistics That Derail Large Projects ¶
Late autumn in a regional logistics firm in the East Midlands: a consultant was three days into an engagement before anyone thought to arrange access to the warehouse management system. The IT department required a formal request, which required a sign-off from a director who was at a trade fair in Stuttgart. That is four days of fieldwork conducted without the primary data source. It is a common story. Before the consultant's first day, operations leaders should arrange system access, physical site access if relevant, and introductions to the IT, finance, and HR contacts who will field data requests. They should also establish a single point of contact inside the organisation — one named person who the consultant calls when something is blocked, rather than a general inbox that routes to three different people depending on the day.
Honesty as Operational Infrastructure ¶
There is a version of briefing that is really a form of reputation management — sharing the information that makes the organisation look thoughtful while quietly omitting the incident from eighteen months ago, the failed restructure, the team that is actively unhappy about this project being commissioned at all. Consultants tend to find these things anyway, usually by the end of the first week, but finding them late means recommendations built on incomplete foundations. The operations leaders who get the most from external engagements are typically the ones who over-disclose in the brief: here is the political context, here is who championed this and who opposed it, here is the budget figure and why it is probably not quite enough. That level of candour is not weakness — it is the fastest route to work that is actually useful.
Measuring Whether the First Week Was Well Spent ¶
By the close of a well-prepared first week, the consultant should be able to articulate the problem in their own words, name the two or three hypotheses they are testing, identify the data gaps that remain, and describe what they have ruled out. The operations leader should be able to say whether that articulation is accurate. If the first week ends with both sides still discussing what the project is fundamentally about, the preparation was insufficient — and it is worth pausing to correct that before the second week begins. Engagements rarely recover from early drift. They deepen into it.
The season before a consultant arrives is where the real decision is made — not the decision to hire, but the decision to be helped. Organisations that prepare with the same rigour they expect from the people they bring in will almost always find that the first week earns its cost. Those who do not will spend it paying for orientation that should have been preparation.