Questions Clients Ask Before Starting

Before we kick off a project charter or set up a weekly reporting rhythm, most sponsors and delivery leads ask the same handful of questions. They are fair questions, and the answers shape how we structure the first few weeks of an engagement. Here is what comes up most often, and how we tend to respond.

"Do we need to change our project management tool?"

Usually not. We work inside whatever you already use, whether that is Microsoft Project, Smartsheet, Jira, or a well-maintained spreadsheet. The point is to make your existing tool more useful, not to introduce a new platform that nobody wants to update. If your current setup genuinely cannot handle basic scheduling or RAID tracking, we will say so early and suggest a lightweight alternative. But forcing a tool migration is rarely the right first step.

"How much of our team's time will this take?"

Less than people expect, once the initial structure is in place. The first two to three weeks involve more workshops and document setup. After that, we aim for a weekly checkpoint of about an hour, plus a short status update from each workstream lead. The goal is to keep documentation lean enough that people actually maintain it, rather than treating it as a compliance exercise.

"What does good weekly reporting look like?"

A report that gets read by a steering committee is short, specific, and honest. It highlights what was completed, what is at risk, and what decision is needed this week. It does not list every task status or repeat the project plan. We have seen too many reports that are twenty pages long and read by nobody. Our template fits on one page, with a RAID summary attached when something actually needs attention.

"How do you handle scope creep?"

Scope creep usually happens because changes are absorbed silently into the plan. We make change visible. When a sponsor asks for something new, we log it, assess the impact on timeline and resources, and present the trade-off. The decision stays with the sponsor. Our job is to make sure the cost of a change is understood before it is approved, not to block it.

If you are weighing up whether structured delivery makes sense for your team, it often helps to talk through your current gaps first. A discovery session is a low-pressure way to do that. You can also read about what to prepare beforehand or how to choose a service format that fits your situation.