Transparent Turnaround Task Forces
Show the crisis, involve frontline experts, then redesign the organization
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 94%
Transparent Turnaround Task Forces combine an explicit case for change with employee-led operating diagnosis. The leader first paints an evidence-based picture of what is wrong, including the likely consequences of inaction. Teams then map redundant roles, systems, and business units rather than beginning with an arbitrary head-count target. Cross-functional task forces composed of frontline employees examine the work and recommend what should be consolidated, eliminated, or redesigned. This creates information flow from the people closest to operations while helping the workforce understand why painful decisions may be necessary. Leadership still owns the final choices and must communicate them honestly. The mechanism converts a threatening restructuring from an unexplained decree into a shared diagnosis followed by a disciplined redesign, increasing both decision quality and organizational comprehension.
Origin
Extracted from Masters in Business through Charlie Norris's account of restructuring McKesson Water, which had grown through acquisitions without integrating its operations.
Core principles
- 01People need a clear reason before accepting painful change
- 02Operating facts should precede restructuring decisions
- 03Frontline employees can identify duplication leaders miss
- 04Shared diagnosis improves the legitimacy of change
- 05Leaders remain accountable even when recommendations are participative
How to run it
- 1
Establish the survival case
Explain the organization's financial and operational condition in concrete terms. State what will happen to the entire workforce if the underlying problems remain unresolved.
Pro tip Use understandable measures such as profitability, staffing ratios, and duplicated costs.
Watch out Exaggerating the crisis will destroy trust once employees discover inconsistencies.
- 2
Map structural duplication
Document units, roles, systems, accounts, and workflows performing equivalent work. Distinguish necessary local variation from accidental redundancy.
Pro tip Trace complete processes across business units rather than comparing job titles alone.
Watch out Similar titles may conceal different responsibilities, while different titles may conceal identical work.
- 3
Build frontline task forces
Recruit employees close to each operating process and ask them to diagnose inefficiencies. Include multiple levels and functions to limit local bias.
Pro tip Give each group access to the relevant operating and financial evidence.
Watch out Task forces cannot make sound recommendations when information is withheld.
- 4
Request explicit recommendations
Require task forces to identify what should stop, combine, continue, or change. Ask them to explain the operational consequences of each recommendation.
Pro tip Use a common recommendation template so proposals can be compared.
Watch out Do not imply that participation guarantees every participant's role will remain unchanged.
- 5
Integrate and decide
Combine task-force findings into one viable organization design. Resolve conflicts and make the final decisions based on survival, service, and strategic requirements.
Pro tip Publish the decision criteria before announcing outcomes.
Watch out Implementing isolated recommendations without system-level integration can create new gaps.
- 6
Communicate and execute humanely
Explain what is changing, why it is necessary, and how affected people will be treated. Separate business necessity from personal judgment.
Pro tip Deliver difficult messages directly and provide practical transition support where possible.
Watch out Participation does not remove the emotional and ethical burden of workforce reductions.
In the wild
McKesson Water contained seven strategic business units performing similar work through separate systems and charts of accounts. A consolidation group then had to translate their outputs for the parent company. Norris presented the survival problem and convened frontline task forces to recommend what needed to change, including roles employees themselves recognized as duplicated.
→ The company gained an evidence-based route to restructuring and eventual turnaround rather than allowing fragmentation to drive it out of business.
Common mistakes
Starting with an arbitrary cut target
A percentage reduction imposed before mapping the work can eliminate essential capabilities while preserving redundant structures.
Hiding the severity of the problem
Employees cannot understand painful decisions when leadership withholds the operating reality that makes them necessary.
Delegating accountability to task forces
Employee recommendations improve diagnosis, but executives must still own the final design and its consequences.
Is it for you?
Best for
It is best for organizations facing insolvency, acquisition-driven duplication, excessive overhead, or fragmented operating systems.
Not ideal for
It is not ideal for healthy organizations seeking marginal efficiency gains or for leaders using employee participation to disguise predetermined arbitrary cuts.
From the transcript
“I had to paint the picture of what was wrong with the organization.”
“Nobody is going to be comfortable with that level of staff reduction if there isn't a clear reason why you're doing it”
“we set up across the board task forces made up of the frontline people to come back with their own recommendation.”
From the episode
Interview With Byron and Charlie: Masters in Business (Audio)