What to Prepare Before a First Consultation

Most first consultations go one of two ways. Either the team has a clear picture of what is slipping and where the pressure sits, or the conversation stays at the level of "we need better project management" without much underneath it. The second version is harder to turn into a useful engagement, because nobody can point at the specific decision that keeps getting delayed or the report that nobody reads.

This post is about the first version. What you can bring to a discovery session so that an independent coordinator can help you map delivery gaps instead of spending the first hour guessing at context.

Start with the last three status reports

If your team already produces weekly or monthly updates, bring the last three. Even rough ones. The value is not in the formatting, it is in what the reports reveal about how decisions are made. A steering committee pack that lists twenty open items tells a different story than one that names three decisions waiting on sponsors. The coordinator needs to see that pattern, not hear a summary of it.

If you do not have status reports at all, that is useful information too. It means the first piece of work is probably a reporting rhythm that fits how your leadership actually consumes information.

Name the project that keeps you up at night

Pick one engagement, not three. An ERP rollout, an office fit-out, a marketing campaign launch, an internal automation piece. The instinct is to describe everything that feels messy, but a single concrete example gives the consultant something to test against. You can walk through its timeline, its RAID log, and the point where it started drifting from the plan.

That one example usually surfaces the recurring issues: unclear ownership, resource conflicts nobody flagged early, or a sponsor who only hears about problems after they have grown. Those patterns are what a PMO setup or delivery governance engagement is actually built around.

Know your tooling reality

There is no point recommending a platform your team will not adopt. Before the session, write down what you currently use for task tracking, scheduling, and document storage. It might be Microsoft Project, a shared spreadsheet, Jira, or a mix of three things that do not talk to each other. The right approach works inside that reality rather than asking you to migrate everything at once.

Also note who updates these tools and how often. If the project schedule lives on one person's laptop and only gets touched before steering committee meetings, that is a governance gap worth naming early.

Bring the constraints, not just the goals

Every mid-sized operation has limits: a small project office, budget cycles that do not align with delivery timelines, or a culture where documentation is seen as overhead. Say those out loud. A realistic assessment of what can be sustained after the engagement ends matters more than an idealised process chart.

The teams that get the most from a discovery session are the ones willing to describe how work actually happens, including the parts that are not pretty. That honesty is what turns a generic proposal into something that fits.

If you are unsure whether your situation is ready for a structured conversation, that is exactly what the first call is for. You can also look at the questions other clients raise before starting, or read about how to choose a service format that matches your constraints.