What happens in a first consultation with {{brand}}

What happens in the discovery weeks of an engagement

Data before opinions, interviews in week two, findings tested in week three. What our team is doing in the first three weeks, what we need from your people, and what you hold in your hands at the readout.

Nadia Brennan Avatar

·

5 min read

The first weeks of an engagement are the ones clients see least of and ask about most. There are no slides yet, the team is asking for spreadsheets, and a stream of interview invitations lands in calendars across the business. At Sterling & Cole LLP we call this period discovery, and on a typical twelve-week engagement it takes the first three weeks. This note explains what we are doing in that time, what we need from your people, and what you should have in your hands when discovery ends.

What discovery is for

Discovery has one purpose: to replace what everyone believes about the problem with what the evidence shows. Most businesses have a settled story about why margins are falling or why a team misses its targets. Sometimes the story is right. Often it is half right, and the half that is wrong is where the useful work lies.

By the end of discovery we should be able to say three things with confidence:

  • what is actually happening, in numbers
  • which of the explanations people offered are supported, and which are not
  • which two or three questions the rest of the engagement should concentrate on

The three weeks, in outline

WeekMain activityWhat your team does
1Data request, first read of existing reports, kick-off with the sponsorProvide data and name interviewees
2Interviews, site visits, first analysisAttend interviews of about 45 minutes each
3Testing early findings, first hypotheses, discovery readoutSponsor and steering group attend a 90-minute readout

Week one: data before opinions

We send a data request on the first day. It is specific: named reports, a defined period, a named format. We would rather receive an imperfect extract in three days than a perfect one in three weeks. Where data does not exist, we say so and agree a proxy.

In parallel we read what already exists: board papers, prior studies, internal reviews. It is surprising how often the answer to part of the question has already been written down by someone in the business and not acted on.

Week two: interviews and visits

We interview between twelve and twenty people on a typical engagement, chosen with the sponsor to cover every level involved. Interviews last about forty-five minutes and follow a short guide so answers can be compared. We do not attribute quotes to named individuals in anything we write, and we tell every interviewee that at the start.

Where the work touches physical operations, we visit. An afternoon on a warehouse floor or in a call centre often explains a number that three weeks of spreadsheets could not.

Interview notes and first analysis spread across a working table

Week three: testing what we think we have found

By the third week we have early findings. We test them before presenting them, with the people closest to the data, and we drop the ones that do not survive. The discovery readout presents what held up, what did not, and what we recommend concentrating on next.

The most valuable sentence in a discovery readout is usually one that begins “We expected to find… and did not.”

What we ask of your organisation

Discovery is the most demanding phase for the client side. In practice we ask for:

  1. A single point of contact who can chase data and book interviews, for about a day a week.
  2. Data within five working days of the request, or an early warning if that is not possible.
  3. Interviewees who have been told by their own leadership why we are there.
  4. Thirty minutes a week with the sponsor for a progress check.

The third point matters more than it looks. People who have not been told why consultants are asking questions tend to assume the worst, and they answer accordingly.

What you receive at the end of discovery

The discovery readout is a working document, not a polished report. It contains:

  • a fact base: the key numbers, with sources, agreed with your finance team
  • a short list of findings, each marked as confirmed, likely or open
  • the questions we propose for the next phase, and any change to the original scope
  • a list of data or access still outstanding

When discovery changes the plan

Sometimes discovery shows that the original question was the wrong one. When that happens we say so at the readout and propose how the remaining weeks should be used instead. Any change to scope, timeline or fee is agreed in writing with the sponsor before the work continues, following the change process in the proposal.

How discovery is kept on track

Three weeks passes quickly, so we keep a simple tracker from the first day and share it with your point of contact each Friday. It lists every data item requested, the date it was asked for and the date it arrived; every interview booked and held; and every early finding with its current status. When an item is more than five working days late, the tracker says so and we raise it at the weekly check with the sponsor rather than letting it slide. The same tracker becomes the list of outstanding items in the readout, which means nothing is quietly forgotten between discovery and the next phase of the work.

Common questions

Can discovery be shorter? On a small engagement, two weeks is often enough. Shorter than that, we tend to find what we expected rather than what is there.

Will you share interview notes? No. We share themes and findings. Keeping individual notes confidential is what makes people willing to speak openly.

Do we pay for discovery separately? It is part of the engagement fee, and on diagnostic engagements it is most of the work.

If you are preparing for an engagement with us, the kick-off pack your sponsor receives lists the first data request. Questions in the meantime go to counsel@example.com.

This describes our usual approach. Each engagement follows the plan and terms in its signed proposal.