Project Management

Please login or join to subscribe to this thread

How do you deal with fuzzy requirements?

linkedin twitter facebook   Requirements Management   Scope Management  
avatar
Mike Frenette Manager, IT PMO| Halifax Water (retired) Halifax, Nova Scotia, Canada
Have you ever been asked to lead or take part in a project that had unclear requirements?

What did you do about it? How did your actions fit within the approach selected for the project (agile, predictive, hybrid, etc.)?
Sort By:
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Mike -

I'd argue that almost always there are unclear requirements unless the project was preceded by an initiative that yielded a detailed requirements baseline. This is why a PM needs to take the time early in the life of the project to meet with key stakeholders and work through a progressive elaboration of what's in vs what's out.

Unclear is different than evolving - the latter might influence an approach choice whereas the former is universal.

Kiron
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
The short answer is to iterate - either iterative elaboration or iterative development would be preferrable to iterative projects, but there are probably cases where that is acceptable, too.
avatar
Gisselle Herrera Dubai, Du, United Arab Emirates
The first thing I do is understand who is the main sponsor and that tells me a lot about the priority of the project and the reasons why the requirements are not clear. Picture this, most times when the CEO or someone in the C level is pushing for work to start this automatically creates a sense of critical priority that makes everyone unease when they have to explain that we should take our time to clarify the scope and the approach. With this in mind, I move into understanding the main idea and if that would work well with a hybrid approach, iterative or it needs to be rock solid waterfall. From there all I need to do is take charge by discussing the approach, my reasoning and the consequences of not taking our time to discuss at least high level requirements.
avatar
Amanda Loewy
Asking questions and drilling down/decomposing the scope from the top down has usually helped me. You may encounter resistance though, as most people initiating projects with unclear requirements are under time pressure, so you need to get them to slow down and think critically about the problem.
avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal

Absolutely — dealing with fuzzy or evolving requirements is almost a rite of passage in project leadership.
When I encounter unclear requirements, my first step is to acknowledge and frame the uncertainty — not as a barrier, but as an opportunity for co-creation and discovery.
Regardless of the methodology, I rely on active listening, visual thinking tools (like story maps or mockups), and collaborative validation.
Above all, transparent communication is key to managing expectations and building trust as we move from fuzzy to focused

Please login or join to reply

Content ID:
ADVERTISEMENTS

Very funny, Scotty. Now beam down my clothes.

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters