OrgChart's State of Workforce Planning 2026 found that 46% of HR leaders cite economic uncertainty as their biggest planning challenge, ahead of concerns about AI, data quality, or anything else on the list. That's a reasonable thing to worry about. But in my experience, when someone describes an entire plan as "uncertain," what they usually mean is something plainer: I don't know what's happening in it.

A good plan doesn't leave you there. It tells you what percentage is going to be delivered as it stands, what percentage is at risk, and specifically why.

What that actually looks like

At Triumph, we broke the long-term forecast down this way, not against economic conditions directly, but against what products actually belonged in the portfolio. We applied categories across each layer of the plan, covering three distinct questions.

From a quality perspective:

  • Is this element backed by a genuine team plan, or is it still sitting as a template or a rough forecasting estimate?
  • Where in the timeline is this work: concept, design, development, or launch?
  • Confidence as to how committed the business was to a given product: do we want this, is it likely, or are we still exploring the segment?

Layered together, those three categories let you graphically represent exactly what proportion of the plan carries which kind of risk, rather than treating the whole thing as one undifferentiated forecast.

Where the risk actually comes from

Some of it is internal. A template or an estimate is sitting in the plan where a proper plan should be. A project further along in delivery is more confirmed simply by virtue of how much work has already gone into it. Some of it is external: what the market actually wants, and how much of that is still being tested rather than known.

Neither of those is the same as "uncertainty" in the vague sense. Each one is a specific, nameable reason, attached to a specific piece of the plan.

What changes once you can see it

The real value of layering these categories in isn't the diagram. It's that it drives attention to exactly the right place. Why is there still a template sitting in the plan at this stage? Go and build a real one. That project is still in concept. How tight is the scope, really? What market evaluation is actually needed to firm up the project we're not sure about, and when will we know?

None of those are abstract questions about the future. They're concrete actions against a specific piece of the plan, and that's the difference between a forecast that produces anxiety and one that produces a to-do list.

The takeaway

If your planning conversations keep landing on "it's just uncertain out there," that's usually a sign the plan hasn't been broken down far enough yet, not a sign the future is unusually unknowable. Categorise what you actually know, what you're assuming, and what you're still waiting to find out, and the uncertainty stops being a fog over the whole plan and starts being a specific, workable list.

If your own forecasts feel uncertain everywhere rather than uncertain in specific, nameable places, that's usually fixable. Book a free 45-minute consultation and we'll look at where the real risk actually sits in yours.