[Planning] How do you build a project plan when the scope is still rough?

Example Answer

When the scope is still rough, I don't try to fake precision. I start by building a planning frame instead of a false final plan. That usually means clarifying the objective, the major work areas, the likely phases, the biggest dependencies, and the key unknowns that still need to be worked through.

Then I make the assumptions explicit. I want people to understand what we know, what we don't know yet, and what would need to become clearer before I would call the schedule more committed. That gives the team enough structure to start moving without pretending the rough draft is a finished answer.

I've found that's a much healthier way to plan early work. The project gets direction, but it doesn't inherit fake confidence that later turns into surprise.

Common Poor Answer to Avoid

"I still put together a detailed plan and refine it later if needed."

Why it's weak

That sounds efficient, but it can create false certainty very early. Hiring managers want to know that you understand the danger of precise-looking plans built on rough scope.

Why this works

It sounds more like a real PM response. It shows structure, honesty, and an understanding of how early planning should actually work under uncertainty.