A Few Shared Scenarios, Not One Firm Forecast or No Written Plan: Team-Lead Anticipation Practices and Team Adaptation to Unplanned Disruption

Abstract

Across 274 team leads in nine organizations followed over one fiscal year in which each team met at least one unplanned disruption, leads who wrote two or more short, plausible scenarios for the year and walked their team through them ("shared-scenario," n=96) led teams that reached an agreed revised plan after the disruption in 11.2 days on average, versus 14.0 days for leads who shared a single committed forecast ("single-forecast," n=101; a 25% gap) and 14.4 days for leads with no written anticipation at all ("no-written-plan," n=77; a 29% gap). Members of shared-scenario teams rated their own understanding of the team's situation higher (5.3/7) than members of single-forecast teams (4.4/7, a 20% gap) or no-written-plan teams (4.2/7, a 26% gap). Shared-scenario leads reported the least expectation-gap stress after the disruption (3.5/7, versus 4.4/7 for single-forecast and 3.9/7 for no-written-plan leads), but paid for it up front: they logged 5.2 hours of planning meetings in the year's first month, against 4.1 hours for single-forecast leads. The benefit largely disappeared among the 17 shared-scenario leads who wrote five or more highly detailed scenarios, whose teams took 13.9 days to re-plan, close to the single-forecast figure.

1. Introduction

A team lead who writes down one confident forecast for the year gives the team something clear to work toward. When that forecast breaks — a supplier fails, a budget is cut, a reorganization lands mid-quarter — the same clarity can turn into a sharp gap between what everyone was told to expect and what is actually happening. Scenario practice, long associated with strategy departments, takes a different approach: sketch several plausible futures, none of them a promise, and talk through what each would mean. Whether this is worth the time at the level of an ordinary team lead, rather than a corporate planning office, has received little direct study.

There is also a reasonable worry in the other direction. A lead who builds an elaborate scenario set may start fitting events to the nearest scenario instead of reading them fresh. We compared re-planning speed, team members' understanding of their situation, and leads' own stress after a disruption across three anticipation practices, and looked separately at leads whose scenario sets were unusually large and detailed.

2. Method (Summary)

We recruited 274 team leads (teams of 4–15 people) across nine organizations in manufacturing, logistics, software, and public-service administration. All teams experienced at least one unplanned disruption during the study year, defined as an event logged in the organization's project-tracking system that forced a formal change to the team's quarterly plan. Leads were classified from planning documents submitted at the start of the year and confirmed by a team-member survey: "shared-scenario" if the lead wrote two or more distinct plausible scenarios for the year and discussed them with the team in at least one meeting (n=96); "single-forecast" if the lead shared one committed forecast or plan with the team (n=101); and "no-written-plan" if the lead produced no written anticipation document beyond assigned targets (n=77). Within the shared-scenario group, a split by scenario count was defined after data collection: 79 leads wrote two to four scenarios and 17 wrote five or more scenarios of at least a page each.

The primary outcome was the number of days from the disruption's logged date to the team's first agreed revised plan, taken from project-tracking records. Secondary outcomes were team members' rating of their understanding of the team's situation and priorities after the disruption (1–7, surveyed within three weeks of it) and the lead's self-reported expectation-gap stress over the same period (1–7). Shared-scenario and single-forecast leads also logged time spent in planning meetings during the first month of the year; no-written-plan leads, having no separate planning meetings, did not. For teams with more than one qualifying disruption, the first was used for all outcomes. Two coders blind to group rated each qualifying disruption's severity.

3. Findings

Shared-scenario teams reached an agreed revised plan in 11.2 days on average, versus 14.0 days for single-forecast teams (a 25% gap) and 14.4 days for no-written-plan teams (a 29% gap). Single-forecast and no-written-plan teams did not differ meaningfully from each other on this measure. Team members' situational-understanding ratings averaged 5.3/7 in shared-scenario teams, 4.4/7 in single-forecast teams (a 20% gap), and 4.2/7 in no-written-plan teams (a 26% gap).

Expectation-gap stress among leads ran in a different order. Single-forecast leads reported the most (4.4/7), no-written-plan leads less (3.9/7, a 13% gap below single-forecast), and shared-scenario leads the least (3.5/7; a 26% gap versus single-forecast). Shared-scenario leads logged 5.2 hours of planning meetings in the first month, versus 4.1 hours for single-forecast leads (27% more).

Within the shared-scenario group, teams whose lead wrote two to four scenarios re-planned in 10.6 days on average. Teams whose lead wrote five or more detailed scenarios (17 of the 96) took 13.9 days, close to the single-forecast figure. Because the two-to-four subgroup was defined after the fact and excludes the slowest-replanning shared-scenario leads, its 10.6-day figure likely overstates what the practice itself delivers.

4. Discussion

The headline gap cannot separate the scenarios themselves from the act of discussing them with the team, since every shared-scenario lead did both. What the design can say is that the combination was associated with faster re-planning and with team members who felt they understood where things stood. The upfront hours were real, and they were not only the lead's: each planning meeting also drew on the team's time in a month that rarely has spare hours in it. The return arrived later, and mostly to the team as a whole.

The stress ordering is worth noting, with caution. A single committed forecast left its leads somewhat more stressed than having no written plan at all, which may reflect a firm expectation sharpening the jolt when it fails. Several rough scenarios seem to have cushioned that jolt without leaving leads unprepared.

The 17 leads with large, detailed scenario sets complicate any simple "more anticipation is better" reading. Their teams re-planned about as slowly as single-forecast teams. One possibility is that an elaborate scenario becomes another firm forecast in practice, just one chosen after the fact. Whether there is a level of detail at which a scenario stops informing the team's reading of events and becomes a position to defend is still open, and the follow-up should test it directly.

5. Limitations and Future Directions

Leads chose their own anticipation practice, so leads who were already more flexible or more communicative may have been drawn to scenario work and may also have re-planned faster for reasons unrelated to it. The five-or-more subgroup is small (n=17) and its result should be treated as a signal worth testing, not an estimate. Situational understanding was rated by team members who knew which practice their own lead used, and expectation-gap stress was self-reported by leads who had chosen their own practice. Disruptions varied widely in severity; a severity rating assigned by two coders blind to group showed no meaningful difference across the three groups, but severity was not held fixed by design. A follow-up will randomly assign a brief scenario-sketching protocol to a subset of single-forecast leads at the start of a planning year.

Editorial Note

This report underwent CfAHC's Rapid Review Protocol, including AI-assisted literature cross-checking and a two-reviewer human sign-off.