Branchford Leadership Labs
Leading with AI
We help leaders evaluate AI-supported recommendations and manage the organizational changes that come with them.
Explore the leadership labHow Branchford helps
Our advisory and leadership development work helps organizations establish how AI-supported work will be reviewed and address the conditions that affect adoption.
Decision authority & review
Define who reviews AI-supported recommendations, when issues require escalation, and who remains accountable for decisions.
Workflow & adoption
Identify process barriers and conflicting incentives. Assess whether teams have the capabilities needed to make new ways of working effective.
Leadership practice
Use facilitated scenarios to help teams evaluate recommendations, question assumptions, and apply the context of their organization.
The Green Dashboard Problem
An interactive case study in organizational change, AI-supported analysis, and human judgment.
Apex Regional Services
The company is six months into a transformation designed to improve customer response, coordination, and decision quality through a new enterprise workflow platform.
- Implementation milestones remain on schedule.
- Training completion exceeds the target.
- Every business unit has access to the platform.
- Customer response measures remain stable.
- Teams return to spreadsheets and email when workload increases.
- Managers approve workarounds to protect response times.
- Employees enter information twice to satisfy both systems.
- Critical decisions still occur outside the new workflow.
The project appears successful when measured through implementation activity. Daily behavior suggests the new operating model has not taken hold.
What should the executive team do next?
Select the action you would recommend first. You will see the implications of your choice before comparing it with the AI analysis.
What your decision could produce
Which evidence would you want before committing the entire organization to this course of action?
A prepared AI recommendation
Launch a 30-day adoption sprint. Require all business units to discontinue nonapproved workarounds, establish daily usage dashboards, assign managers adoption targets, and provide focused retraining to teams with the lowest platform utilization.
- Training completion has not translated into consistent use.
- Parallel processes increase rework and weaken data quality.
- Manager behavior is reinforcing the workarounds.
- Clear ownership and measurable expectations are absent.
- It establishes urgency and a defined time horizon.
- It connects managers to adoption outcomes.
- It creates measurable implementation discipline.
- It targets additional training where use is lowest.
What the initial analysis did not see
The recommendation is logical, but leaders possess context that was absent from the original input.
The old metrics still govern performance.
Managers are rewarded for response speed. The new workflow temporarily slows case processing, so managers protect the measure that still determines how their performance is evaluated.
Several workarounds protect customers.
The new platform does not yet handle two high-risk case types reliably. Forcing immediate compliance would remove safeguards employees created to prevent service failures.
Training covered navigation, not work.
Employees learned where to click. They did not practice making complex decisions through the new process under realistic workload and time pressure.
Employees were excluded from design.
The implementation team configured the workflow around the documented process. Experienced employees know that the documented process does not reflect several conditions encountered in daily operations.
Stricter compliance would increase visible adoption while concealing design defects and conflicting incentives. The organization could become more compliant with a process that is not yet capable of supporting the work.
Convert the rollout into a focused learning cycle
One defensible response to the full case is to pause expansion for 30 days without abandoning the transformation. Two business units become learning sites for redesigning the operating model. The scope and timing would need to reflect the organization’s actual risks and commitments.
Observe the work
Study when and why employees leave the platform, with specific attention to peak workload and high-risk cases.
Remove conflicting signals
Adjust manager measures so adoption, customer outcomes, and learning are evaluated together.
Redesign with users
Use experienced employees to improve the workflow and identify which workarounds represent risk and which reveal necessary capability.
Practice under pressure
Replace navigation-focused retraining with realistic cases that require teams to execute the new workflow during demanding conditions.
Scale from evidence
Resume expansion after the learning sites demonstrate improved adoption, reduced rework, and stable customer performance.
The prepared analysis organized the available evidence and proposed an adoption plan. Additional context revealed why that plan needed revision. Leaders remain accountable for checking the information behind a recommendation and deciding whether it fits the work.
Leadership lesson
Implementation measures show whether the project is moving. Behavioral and operational evidence shows whether the organization is changing. Leaders need both.
Bring the discussion to your team
Use the Green Dashboard case to examine how your team evaluates recommendations and responds when implementation measures conflict with operating experience.
A facilitated session includes a team discussion of the case and an examination of what it means for your organization’s workflows and decision practices.

