The Maverick's guide to Strategic Portfolio Management
March 20, 2025 | Live Webinar
Fuzzy dates are dates that have a bit of wiggle room. They are approximate dates, placeholders, flexible time periods rather than a fixed date. For example, “week commencing 27 January” is a non-precise date, that offers some flexibility, and so is “Quarter 1”.
Why would you plan with fuzzy dates rather than precise dates? Precise dates can be better as they give more certainty, but sometimes you just don’t know. For example, if you are doing rolling wave planning, or any type of iterative planning, you might not have the right level of detail to commit to a fixed date at this point.
Managing risk
You might be dealing with a lot of risk, and fuzzy dates allow you to build risk into the schedule by giving yourself a relatively large window in which to complete the work, driven by unknown factors such as what the weather will be like and whether that will enable you to complete the work or not.
Using fuzzy dates can help reduce the risk of unrealistic scheduling by acknowledging potential unknowns early. You aren’t just guessing at what the risk will be or what impact it will have on the schedule, or hoping that you can hit the specific milestone. You’re building contingency into the schedule which helps keep the project timeline realistic when you can’t (yet) commit to specifics.
Probabilistic ranges and conditional dependencies
Sometimes, fuzzy dates are expressed as ranges (“2-4 weeks from now”) or probabilities (“likely to happen by the end of March”). That gives you an indicative time frame without a hard commitment, and I find it’s quite a good way to set expectations with stakeholders. You can always explain why you are presenting ranges instead of fixed dates.
One of the reasons that drives ranges is external dependencies (“The materials will arrive some time in the first half of February but the supplier doesn’t know exactly when…”). Another example is when you are waiting on feedback from either internal reviewers or external clients, and they haven’t committed to providing an exact date by which they will get back to you. A task might be due “two weeks after client approval,” where the actual start time depends on an external party.
Moving on from fuzzy dates
Of course, you can’t have everything as a fuzzy date, and there comes a time when you can switch out your ranges and vague commitments for something more concrete. Incrementally refine your project schedule and replace the fuzzy dates with specific dates as more information is known and your confidence levels improve.
Communicating fuzzy dates
In essence, fuzzy dates provide a way to communicate tentative timelines while keeping the schedule flexible and adaptable, making them valuable in early-stage planning or for projects with high uncertainty.
However, they are a pain to show on a schedule unless your scheduling tool allows for the presentation of earliest/latest completion dates. In one of my mentoring sessions recently we talked about using earliest/most realistic/latest date markers on a PowerPoint timeline or using a bar with gradient colours fading out at each end to show the ‘fuzzy’ part of the timeline.
Some software tools will display start and end dates with a range if you have these parameters set; others will only work with a specific date as the end date, which is why in the main the project managers I have spoken to tend to create another timeline (often on a slide) to show the concept. Or you just create a task that stretches out to the latest possible target date and use that, making the fuzziness opaque and avoiding talking about it at all.
How would you do it?
Posted on: February 08, 2025 12:00 AM |
Permalink