Do not begin with abstract team building.
Begin with consequential enterprise work—and develop the leadership system through the way it senses, decides, coordinates, experiments, and learns.
Perform and transform through the same work.
The engagement has two deliverables: movement on a consequential hospital issue and increased capacity to lead similar complexity in the future.
Diagnose, commission, engage, experiment, review, and embed.
Diagnose the current system
Clarify the issue, stakeholders, recurring patterns, leadership architecture, and developmental constraints.
Commission the team
Name the shared enterprise work, authority, stakeholder responsibility, and why the whole team is required.
Engage live heat
Work a consequential challenge that reveals both the operational issue and the leadership pattern.7
Create a bounded experiment
Change one frame, relationship, decision pathway, authority arrangement, or stakeholder interface.
Review at two levels
What did the operating system produce? What did the leadership system contribute?
Embed the learning
Translate insight into meeting architecture, decision processes, role practice, circulation, and operating rhythm.
The output is not a static personality report.
The diagnostic creates a shared map of the living leadership system around one or more consequential enterprise challenges.
Methods may include
- CEO and executive interviews
- Team observation
- Developmental or personality assessment when useful
- Stakeholder listening
- Meeting and decision review
- Leadership-circulation mapping
The diagnostic product
- Current strengths
- Recurring system patterns
- CEO concentration points
- Authority and dependency map
- Developmental invitation
- Recommended live-heat practice field
Long enough to produce feedback. Short enough to preserve urgency.
Weeks 1–2
Contract and diagnose.
Clarify the live issue, commission, stakeholders, evidence, and developmental edge.
Weeks 3–4
Constitute and frame.
Establish shared responsibility, authority, meeting design, and the first experiment.
Weeks 5–10
Engage live heat.
Act, observe, reflect, receive stakeholder feedback, and recalibrate.
Weeks 11–13
Integrate and renew.
Assess movement, embed practices, and identify the next developmental passage.
Consequence, interdependence, feedback, and possibility.
The strongest practice fields are neither simulations nor unsolvable crises. They are real issues that matter enough to reveal the team and bounded enough to permit learning.
Emergency department boarding is not only an ED problem.
It can reveal discharge flow, inpatient capacity, physician relationships, workforce fatigue, finance, quality risk, authority, trust, information latency, and competing time horizons. The issue becomes a window into the whole.
Different entry points. One coherent developmental architecture.
Private CEO advisory
Leadership burden, authority, inner work, team architecture, and stewardship through live challenges.
Executive-team diagnostic
Interviews, observation, stakeholder insight, system mapping, and a focused developmental recommendation.
Executive-team retreat
Commission the team, clarify shared work, introduce the model, or create the first live-heat experiment.
Live-heat development cycle
Work one consequential enterprise issue while developing collective capacity.
90-day Executive Human System™ cycle
Diagnose, act, learn, and embed through a defined developmental passage.
Ongoing stewardship
Sustain CEO and team development as enterprise work and organizational context evolve.
Useful when the next constraint is the leadership system itself.
This work is especially useful when
- Competent executives are not yet consistently integrating the enterprise.
- Too much cross-functional complexity returns to the CEO.
- A consequential challenge exceeds any one function.
- The team must perform and develop at the same time.
- Strategy requires stronger leadership circulation through the hospital.
- The CEO wants to leave a more self-renewing leadership system.
It is probably not the right work when
- The primary issue is an unresolved individual performance problem.
- The CEO wants an advisor to fix the team without examining CEO participation.
- There is no consequential shared enterprise work.
- Leadership wants a motivational event rather than sustained practice.
- The organization is unwilling to hear stakeholder or frontline reality.
- Developmental language would be used to label or rank people casually.
Start with the issue already refusing to stay solved.
A first engagement does not require the whole framework to be adopted in advance. It begins by making one live pattern visible enough to work.
Read an anonymized field case →“ED boarding continues despite several operational initiatives. Each function understands its part, but integration repeatedly returns to the CEO. What is the operational issue asking the executive team to become capable of carrying together?”
A diagnostic can then clarify stakeholders, authority, circulation, assumptions, current strengths, and a bounded experiment for the next 90 days.
Track more than how the team feels.
- Earlier truth and weak-signal flow
- Fewer unnecessary escalations to the CEO
- Cleaner authority and decision pathways
- More direct peer work across dependencies
- Greater stakeholder and frontline intelligence
- Stronger follow-through and organizational circulation
- More disciplined learning from consequences
- Increased capacity to hold tension without fragmentation
What live issue is already carrying the developmental work?
A first conversation can identify whether the issue has the consequence, interdependence, and feedback potential to become a useful practice field.
Discuss the issue privately