Why Most Managers Get Caught Off Guard

By Ty Sutherland

You didn’t see it coming. A key project suddenly doubled in scope. Two team members resigned in the same month. A new company initiative landed on your desk with a six-week deadline. Now you’re scrambling—hiring in a hurry, overloading your best people, or delivering half-baked work because you simply didn’t have enough hands.

This isn’t bad luck. It’s a planning gap. And it’s one of the most common struggles for new and mid-level managers, because forecasting feels like something senior leaders do in spreadsheets during quarterly reviews. It doesn’t feel like your job—until everything falls apart.

The truth is that workforce forecasting doesn’t need to be complex or time-consuming. It’s a thinking habit, not a finance exercise. And once you build it, you stop reacting and start leading.

What Team Forecasting Actually Means

Forecasting your team’s needs means asking one core question on a regular basis: What will my team need in the next 30, 60, and 90 days—and do we have it?

That question covers four dimensions:

• Headcount: Do we have the right number of people to handle what’s coming?
• Skills: Do those people have the capabilities the upcoming work demands?
• Capacity: Even if we have the right people, do they have the bandwidth?
• Stability: Are there risks—departures, burnout, shifting roles—that could disrupt us?

Most managers only think about headcount, and only when there’s already a gap. Building a forecasting habit means thinking about all four, before the pressure hits.

Start With What You Already Know

You don’t need a sophisticated model to start forecasting. You need to take stock of what’s already visible. Before you look ahead, look at where you are right now.

Map your current workload honestly

Write down every significant project or responsibility your team is carrying. Next to each one, estimate how much of your team’s weekly capacity it consumes. Be honest—most managers underestimate ongoing work because it feels routine. Routine work still takes time.

When you add it up, you’ll often find your team is already at 90–100% capacity before any new work arrives. That’s not a sustainable foundation for handling uncertainty.

Identify your single points of failure

A single point of failure is any situation where one person holds critical knowledge, a key relationship, or an irreplaceable skill. If that person leaves, gets sick, or gets promoted, you have a problem with no backup plan.

Ask yourself: if any one person on my team disappeared tomorrow, which part of our work would immediately suffer? That’s a risk you should already be thinking about—before it becomes urgent.

Check the stability signals

Forecasting isn’t just about work volume—it’s about people. Are there team members who seem disengaged, burned out, or quietly job searching? Are any roles undergoing informal scope creep that hasn’t been officially recognized? Is anyone approaching a natural transition point, like finishing a long project or completing a development milestone?

These are signals you can read now, and they’re often more reliable predictors of near-term disruption than any spreadsheet.

Look Ahead: The 30-60-90 Framework

Once you have a clear picture of today, shift your attention to what’s coming. A simple 30-60-90 day horizon keeps your forecasting practical without requiring you to predict the unpredictable.

The next 30 days: confirm and commit

The next 30 days should be relatively clear. Deadlines are visible. Projects are active. At this horizon, your job is to confirm that your team has what it needs to deliver what’s already committed.

Ask:

• Are any team members overloaded heading into this period?
• Are there dependencies—waiting on other teams, approvals, or information—that could create bottlenecks?
• Is anyone scheduled to be out that we haven’t fully planned around?

If you find gaps at the 30-day mark, you’re already in reactive mode. The goal is to catch these a month earlier—at the 60-day horizon.

The next 60 days: anticipate and prepare

At 60 days out, things get less certain but more adjustable. You have time to act—to redistribute work, start a hiring process, or begin cross-training someone before the need becomes acute.

Ask:

• What new projects or initiatives are likely to land in this window?
• Are any current projects about to enter a more demanding phase?
• Are there known risks—like an employee considering leaving, or a contract renewal decision—that could affect team structure?

You won’t have perfect information here, and that’s fine. The goal isn’t certainty. It’s early awareness that creates options.

The next 90 days: scenario planning

At 90 days, precision matters less than range. Instead of predicting what will happen, think in scenarios. What’s the best case? What’s the most likely case? What’s the case that would stress your team the most—and how would you handle it?

This is where you think about skills gaps, not just headcount. If the business is moving toward a new technology, a new market, or a new operating model, what capabilities will your team need that they don’t currently have? Ninety days is often the minimum time you need to hire, onboard, or develop someone to a useful level of readiness.

How to Gather Better Information

Forecasting is only as good as the information feeding it. Here’s where most managers stall—they wait for formal updates instead of actively gathering signals.

Talk to your manager regularly about what’s coming

Your manager often has visibility into organizational decisions, budget shifts, and strategic priorities that haven’t been communicated downward yet. Make it a habit to ask in your one-on-ones: “Is there anything on the horizon I should be planning my team around?” Most managers will share what they can, and even a vague heads-up gives you a meaningful advantage.

Build relationships with adjacent teams

The teams you depend on—or who depend on you—are often the source of your next surprise. If another team is about to get stretched thin, it will affect your timelines. If a cross-functional initiative is gaining momentum somewhere else in the organization, your team will likely get pulled in. Stay connected across your peer network, not just within your direct team.

Ask your team what they’re seeing

Your team members are often closer to the actual work than you are. They notice when requests are picking up, when a client or internal stakeholder is signaling new demands, or when a process is starting to strain. Create space in your team meetings or one-on-ones to ask: “What are you seeing coming that I should know about?” This question builds a forecasting culture, not just a forecasting habit for you alone.

Make a Skills Inventory

One of the highest-value forecasting tools you can build is a simple skills inventory of your team. You don’t need software or a formal HR process. A spreadsheet with the following columns is enough:

• Team member name
• Current strengths (what they do well today)
• Developing skills (what they’re building toward)
• Gaps (skills the team needs but currently lacks)
• Availability for new work (bandwidth and any known constraints)

Update it every quarter. When you look at a new project or an upcoming demand, you can quickly see whether your team has what it needs—or whether you have a gap to close through hiring, training, or bringing in outside support.

This is also a powerful tool for development conversations. When your team members see you actively tracking their growth and planning their future, they feel invested in rather than managed.

Build Flexibility Into Your Plans

Even the best forecast will be wrong sometimes. The goal isn’t to predict the future accurately—it’s to be ready to adapt when things change. That means building slack into your plans intentionally.

Protect a capacity buffer

If your team is operating at 100% capacity all the time, any unexpected demand creates a crisis. Aim to keep your team at roughly 80–85% of theoretical capacity. That remaining 15–20% isn’t wasted—it’s your buffer for the unplanned work that always arrives, and it’s the breathing room that prevents burnout.

Getting to this point often requires saying no to lower-priority requests or being explicit with stakeholders about trade-offs. That’s a harder conversation, but it’s part of managing well.

Cross-train for resilience

Cross-training reduces single points of failure and gives you flexibility when work shifts unexpectedly. You don’t need everyone to be able to do everything—but having two people who can cover each critical function means you can absorb disruption without going into crisis mode.

Build cross-training into your regular workflow rather than treating it as a special project. Pair team members on tasks, rotate responsibilities on lower-stakes work, and make knowledge sharing a normal part of how your team operates.

What to Do When You Spot a Gap

Forecasting is only useful if it drives action. When you identify a gap—a skills shortfall, a capacity crunch, or a staffing risk—you have a small window to address it before it becomes a crisis. Here’s a simple decision sequence:

• Can the gap be closed internally? Reassign work, cross-train someone, or adjust timelines if the business allows it.
• Can it be closed through development? If the skill is needed in 60–90 days, can someone on your team develop it with the right support?
• Does it require a hire or contractor? If so, start that process now. Hiring takes longer than you expect, and onboarding takes longer still.
• Does it require a stakeholder conversation? If your team genuinely cannot absorb an upcoming demand, your manager and key stakeholders need to know early—not the week the project is due.

Early visibility gives you options. Late visibility gives you excuses. Neither is the outcome you want, but only one of them keeps your credibility intact.

Forecasting as a Leadership Practice

The managers who consistently have high-performing, stable teams aren’t the ones who react fastest. They’re the ones who see things coming early enough to shape what happens next.

Forecasting your team’s needs isn’t a once-a-year activity buried in a planning cycle. It’s a weekly and monthly discipline—part of how you think about your role. It’s asking what’s coming before you’re forced to ask what went wrong.

Start small. Pick one horizon—the next 30 days—and assess it honestly this week. Ask your manager what’s on the horizon. Update your read on your team’s capacity and stability. Write it down somewhere you’ll revisit.

That’s not a big commitment. But done consistently, it’s one of the most powerful habits a manager can build.