Kept in the dark by its leader and buried in busy work, a team never learns enough about the wider strategy to object, organize, or even know what to resist.
An example
At an engineering services firm, the infrastructure manager and her team of fourteen were given a six-month "stabilization sprint" that took every working hour: patching, retiring old servers, and documenting every system in detail. They had excellent task dashboards and weekly targets, and no briefings on strategy. Two projects they had started the year before were canceled before release, with no explanation. Strategy meetings seemed to be happening without the chief information officer's usual staff. In month four, a friend in procurement mentioned a vendor-transition steering committee that met on Thursdays. The manager asked the chief information officer what it was for and was told it was routine vendor management and she should concentrate on the sprint. In month six, the firm announced that infrastructure operations would move to an offshore provider, and the documentation her team had written became the transition package.
Why it works
Heavy workload makes keeping your head down the easy path, since there is no spare time for anything else. Rich task data helps: people act confidently because their local picture is clear, and the missing context feels like focus. Organizing looks worthless, because without strategic context the team cannot know what it is resisting, who decides, or what a counter-proposal would look like. Trying anyway is costly, since stepping away from assigned work opens performance gaps and strategic questions mark the asker as outside their lane. The precondition is one leader controlling both the team's information and its tasks, with no dotted-line or cross-team escape routes.
The thinking behind it
Mancur Olson The Logic of Collective Action: Public Goods and the Theory of Groups (1965) argues that individuals who would all benefit from acting together have little personal reason to bear the cost, so groups often fail to act. A team buried in busy work faces a higher cost still, since stepping away from assigned tasks opens performance gaps. Connections the manager does not control lower the cost of comparing notes, the first step toward acting together.
Herbert A. Simon Designing Organizations for an Information-Rich World (1971) argues that attention is the scarce resource and that information consumes the attention of its recipients. A heavy load of detailed task data uses up a team's attention, leaving none for the strategy the work serves. Peers in better-informed departments supply the missing picture without drawing on that scarce attention, which is why they are the most efficient route.
Warning signs
A team gets no strategy briefings while its workload spikes. Its projects repeatedly never ship. Task-level data is rich, and the link to strategy is missing, explained as need-to-know or confidential. Strategy conversations seem to be happening elsewhere, with people your team used to see. Questions about direction get a request to focus on delivery. The work being asked for would be very useful to someone taking it over.
How to defend yourself
From inside the work there is no moment when the problem announces itself, so use routes the leader does not control.
- Talk to peers in better-informed departments. Procurement, finance, legal, and human resources often see the strategy first.
- Use dotted-line reports, senior colleagues with their own networks, and outside advisers.
- Compare notes across teams about what each slice of work is for. A combined picture often shows what no single slice does.
- If the combined work looks consequential, ask leadership in writing what it adds up to.
When one person controls both what you know and how you spend your time, treat that as a warning sign.
How a leader shuts it down
Brief every team on the strategy its work serves, uncomfortable parts included, and give teams dotted-line or cross-functional connections their manager does not control. Watch for teams whose projects never ship and whose workloads spike without explanation. If a change will affect a team, tell them early enough for their concerns to shape it.