AI Workforce Transformation with an Expense Software Management Company

/0 Comments/in /by

Case Study

Role: Head of Client Services
Timeline: July 2025 – November 2025 (5 months)
Organization Size: ~800-person organization
Team: Cross-functional implementation team with training specialists and change management practitioners

Challenge

A C-suite leadership team wanted to transform their organization into an AI-first company. The organization faced critical readiness and cultural barriers:

Cultural and Capability Gaps:

  • Widespread skepticism about AI value and practical applications
  • Limited organizational understanding of generative AI capabilities
  • No established AI literacy baseline across workforce
  • Lack of hands-on experience with AI tools beyond basic awareness

Risk and Governance Concerns:

  • Anxiety about ethical AI use and potential misuse
  • Data integrity questions and concerns about hallucinations
  • Security vulnerabilities from uncontrolled AI tool adoption
  • No framework for responsible AI implementation

Organizational Readiness:

  • No structured approach to AI training that would create lasting behavior change
  • Missing community infrastructure for peer learning and support
  • Lack of practical application opportunities for skill development
  • No mechanisms for identifying and prioritizing AI use cases across functions

Mandate: The CIO brought me in to design and lead workforce enablement and business transformation programs that would build AI literacy, create sustainable adoption practices, and establish governance frameworks while measuring meaningful business impact.

Approach

Phase 1: Assessment and Program Design (Month 1)

Organizational Readiness Assessment

Conducted comprehensive evaluation to understand current state and design appropriate interventions.

Assessment Activities:

  • Benchmarking survey to measure existing AI literacy and tool usage
  • Stakeholder interviews to identify adoption barriers and opportunities
  • Risk analysis covering data integrity, security, and ethical use concerns
  • Current state mapping of informal AI adoption and workarounds

Program Architecture:

  • Designed two-tier training approach (basic and advanced) based on role requirements
  • Built change management framework addressing skepticism and resistance
  • Created governance structure balancing enablement with security and ethics
  • Established metrics framework for tracking adoption and business impact

Phase 2: Training Development and Launch (Months 1-3)

Comprehensive AI Workforce Enablement

Delivered structured training programs focused on practical application rather than theoretical knowledge.

Basic AI Training Program:

  • Fundamentals of generative AI and how language models work
  • Responsible use principles: privacy, security, bias, hallucinations
  • Hands-on ChatGPT proficiency building with prompt engineering
  • Workflow integration exercises applying AI to daily work tasks

Advanced AI Training Program:

  • Custom GPT development for specialized use cases
  • Integration with enterprise tools and systems
  • Advanced prompt engineering and context management
  • Use case identification and business value assessment

Implementation Approach:

  • Blended learning with asynchronous content and synchronous practice sessions
  • Small group workshops (6-10 people) enabling peer learning
  • Real-world application assignments requiring participants to apply tools to actual work
  • Office hours and troubleshooting support addressing specific challenges

Phase 3: Community Building and Sustained Practice (Months 2-5)

Communities of Practice and Project Groups

Created infrastructure for ongoing learning, peer support, and practical application beyond formal training.

Communities of Practice:

  • Established AI user groups organized by function and expertise level
  • Regular demo sessions where members shared use cases and techniques
  • Slack channels for asynchronous questions, tips, and resource sharing
  • Guest speakers and case study presentations from successful adopters

Project Groups:

  • Formed cross-functional teams to tackle specific business problems with AI
  • Each group received coaching support and structured project methodology
  • Required groups to demonstrate measurable business value from AI application
  • Show-and-tell sessions sharing learnings and results across organization

Change Management Integration:

  • Identified and trained AI champions within each business unit
  • Created feedback loops to surface concerns and address resistance patterns
  • Built recognition programs celebrating successful AI implementations
  • Developed communication cadence reinforcing AI-first mindset and progress

Phase 4: Governance and Measurement (Months 2-5)

Responsible AI Framework

Established guardrails ensuring ethical use while enabling innovation.

Governance Components:

  • Security protocols for approved AI tools and data handling
  • Ethical guidelines for appropriate use cases and bias mitigation
  • Data integrity standards and verification processes
  • Escalation pathways for questions about responsible use

Business Impact Measurement:

  • Tracked adoption metrics: training completion, active tool usage, feature adoption
  • Measured productivity gains through time-saved assessments and workflow improvements
  • Collected use case examples demonstrating business value across functions
  • Conducted follow-up surveys measuring confidence levels and perceived value

Results

Adoption and Engagement:

  • 80 organizational leaders completed AI literacy training
  • Active participation in Communities of Practice with consistent attendance
  • Project groups identified and implemented high-impact AI use cases across technology, product, and operations functions
  • Shift from skepticism to curiosity with employees proactively seeking AI applications

Capability Development:

  • Organization moved from AI-curious to AI-capable with practical proficiency
  • Leaders equipped to identify opportunities for process redesign and automation
  • Cross-functional collaboration improved through shared AI project work
  • Built self-sustaining peer learning network reducing dependency on formal training

Business Value Examples:

  • Customer service team reduced response time by automating routine inquiry responses
  • Operations team streamlined reporting processes, saving 10+ hours weekly per analyst
  • Product team accelerated user research synthesis, shortening insight-to-action cycles
  • Technology team improved code documentation and review processes

Organizational Change:

  • Culture shift from resistance to experimentation with AI tools
  • Established data-driven investment decision framework for C-suite leaders
  • Built organizational capability for ongoing AI integration without external support
  • Created repeatable model for technology adoption programs

Constraints and Context

Skepticism Management: Initial resistance required careful change management. Some employees viewed AI as threat to job security or dismissed it as hype. Champions network and visible quick wins gradually shifted sentiment, but pockets of resistance remained throughout engagement.

Security and Ethics Tension: Balancing enablement with appropriate guardrails created friction. Overly restrictive policies would have stifled adoption, while insufficient governance risked security incidents. Iterative approach to policies based on observed usage patterns helped navigate this tension.

Variable Adoption Rates: Different business units adopted at different speeds based on use case clarity and leadership support. Technology and product functions moved quickly while some operational areas lagged, requiring targeted interventions.

Measurement Challenges: Quantifying productivity gains from AI adoption proved difficult. Time-saved estimates relied on self-reporting which could be inflated. Focused on concrete use case examples with observable impact rather than precise ROI calculations.

Key Lessons

Hands-On Practice Beats Theory: Training that required participants to apply AI to their actual work created lasting behavior change. Lectures about AI capabilities were quickly forgotten, but solving real problems with AI tools built confidence and habits.

Communities Sustain What Training Starts: Formal training provided foundation, but Communities of Practice created ongoing peer learning that sustained adoption. People learned most effectively from colleagues sharing practical use cases in their own context.

Address Fear Before Teaching Tools: Skepticism and ethical concerns weren’t solved by better training content. Required explicit discussions about job security, responsible use, and organizational commitment to ethical AI before people would engage authentically.

Champions Make Change Scalable: Identifying and enabling AI champions within each business unit created distributed change agents. Central team couldn’t be everywhere, but champions could address local resistance and answer questions in real-time.

Leadership Coaching at Academic Medical Center

/0 Comments/in /by

Case Study

Role: Senior Consultant (Leadership Coach)
Timeline: February 2024 – September 2025 (19 months)
Organization Size: ~50-person marketing department within academic medical center
Team: Coached 8 leaders from manager to director level

Challenge

A leading academic medical center’s marketing department was transitioning to agile ways of working while simultaneously facing significant organizational upheaval. Leaders struggled to maintain effectiveness amid cascading challenges:

Leadership Issues:

  • Leaders transitioning from peer to manager roles without clear frameworks
  • Managers operating reactively rather than strategically
  • Weak delegation practices creating bottlenecks and burnout
  • Imposter syndrome and low confidence limiting leadership presence

Organizational Dysfunction:

  • Teams not consistently delivering high-value, high-priority work
  • Infighting and distrust between team members
  • Poor cross-functional alignment and communication
  • Organizational reduction in force creating anxiety and uncertainty

Mandate: The AVP of Marketing brought CMG Consulting in to develop leaders who could champion agile practices and effectively lead their teams through transformation and uncertainty.

Approach

Phase 1: Foundation Building (Months 1-6)

Individual Leadership Development

Established coaching relationships with 8 leaders, focusing on self-awareness, leadership identity, and core management practices.

Key Interventions:

  • Built confidence addressing imposter syndrome and peer-to-manager transitions
  • Strengthened 1:1 meeting structure and effectiveness
  • Developed vulnerability-based leadership approaches
  • Increased assertiveness and executive presence

Outcomes:

  • Leaders gained clarity on leadership identity and role expectations
  • Improved delegation while maintaining high standards
  • Stronger tools for coaching direct reports through uncertainty

Phase 2: Strategic Leadership (Months 7-13)

Leading Through Complex Change

Coached leaders through a reduction in force and multiple high-stakes organizational changes while maintaining team morale and performance.

Change Management Challenge:

  • Organizational layoffs created fear and distrust across teams
  • Leaders needed to maintain steadiness while processing their own uncertainty
  • Website governance initiative required 9-month change management approach
  • Multiple competing priorities (Legacy Integration, PWR, Brand Refresh) demanded clear strategic focus

Implementation:

  • Developed people-first communication strategies for difficult announcements
  • Built frameworks for strategic planning vs. reactive problem-solving
  • Coached leaders to create and communicate clear vision through ambiguity
  • Established tools for advocacy and impact reporting

Results: Leaders maintained team stability and performance through significant upheaval, with one director successfully launching a governance initiative that gained senior leadership support.

Phase 3: Organizational Impact (Months 14-19)

Building Capability and Influence

Focused on expanding leaders’ organizational influence while developing their teams’ capabilities.

Key Developments:

  • Implemented GROW goals and OKRs to drive team alignment
  • Strengthened cross-functional partnerships and communication
  • Improved performance documentation and accountability practices
  • Developed coaching skills for addressing performance and interpersonal issues

Results: Leaders demonstrated measurable growth in strategic thinking, team development, and organizational influence.

Results

Leadership Capability

  • 8 leaders developed from reactive managers to strategic leaders
  • Improved delegation practices freeing up 20-30% of leader time
  • Enhanced coaching skills for developing direct reports
  • Increased confidence and executive presence across leadership team

Team Performance

  • Better alignment to high-priority work through OKR implementation
  • Reduced infighting through improved communication and role clarity
  • Stronger onboarding and role definition processes
  • More effective performance management and accountability

Organizational Impact

  • Successfully navigated reduction in force with minimal team disruption
  • Launched governance initiative with executive support
  • Strengthened cross-functional partnerships across university
  • Leaders contributing visibly to university-wide problem-solving

Cultural Shift

  • Moved from crisis management to strategic planning mindset
  • Built vulnerability-based leadership culture
  • Increased resilience and emotional intelligence across leadership team
  • Established people-first management practices

Constraints and Context

Organizational Turbulence: The coaching occurred during a period of significant uncertainty, including layoffs, reorganization, and merger of marketing with communications. This required constant adaptation of coaching priorities to immediate organizational needs.

Competing Priorities: Leaders managed multiple high-stakes initiatives simultaneously (Legacy Integration, PWR, Brand Refresh, website governance), making sustained focus on development challenging.

Agile Transition: The organization was learning agile practices while leaders were developing their leadership capabilities, requiring coaching on both fronts simultaneously.

Successful Transition: Engagement concluded as planned in September 2025 with leaders operating independently and organization entering sustainment phase.

Key Lessons

Leadership Identity First: Leaders couldn’t effectively adopt agile practices until they developed confidence in their core leadership identity. Addressing imposter syndrome and peer-to-manager transitions was essential groundwork for organizational transformation.

People-First Leadership in Crisis: Leaders who maintained empathy and steadiness during the reduction in force preserved team trust and performance. Vulnerability-based leadership proved more effective than traditional command-and-control approaches during upheaval.

Strategic Clarity Through Chaos: The most effective leaders created and repeatedly communicated clear vision, even when circumstances were uncertain. This practice anchored teams and reduced reactive behavior.

Delegation as Development: Teaching leaders to delegate intentionally both freed their time for strategic work and developed their direct reports’ capabilities. High standards and delegation aren’t mutually exclusive when approached thoughtfully.

Transformation Rescue for Specialized Medium-Sized Saas Company

/0 Comments/in /by

Case Study

Role: Engagement Lead
Timeline: 15 months
Organization Size: 500-person technology organization (18 product teams, 4 value streams)
Distribution: US, India, Ukraine, Latin America

Challenge

A specialized SaaS company was six months into a Scaled Agile Framework (SAFe) implementation that had stalled due to a lack of transparency of the portfolio work, inconsistent agile practices, and political infighting among the Senior Leadership Team (SLT). The organization faced critical delivery and operational problems, such as:

Delivery Issues:

  • Deployment times remained stagnant with work sitting undeployed for 6+ months
  • No CI/CD pipeline established
  • Security vulnerabilities discovered with no clear remediation path
  • Bloated operations organization

Organizational Dysfunction:

  • Zero visibility into teamwork or how results were measured
  • Teams using fragmented Jira instances (mix of team-owned and company-owned boards, creating a lack of transparency into the team’s backlogs)
  • Low trust between Product and Technology organizations
  • Open conflict between the Chief Product Officer and the CTO creating a highly charged political environment
  • Constant political maneuvering across the VP and C-suite levels

Mandate: The CTO brought me in to restructure the deployment strategy and transform PI planning to deliver more value in less time while moving the organization toward flow-based delivery.

Approach

Phase 1: Establish Visibility (Months 1-3)

Standardized Jira Instances Across All Teams

The priority was creating transparency into work and measurement. Teams were operating with fragmented, inconsistent Jira boards that hid problems and prevented any systemic view of delivery.

Change Management Challenge:

  • Strong resistance from teams who felt they were losing autonomy
  • Product managers had built elaborate but brittle workarounds
  • Passive resistance manifested as avoided meetings and ignored feedback requests
  • Political opposition from VPs and C-suite members

Executive Support: Secured public backing from CTO in company town hall, legitimizing the change and reducing passive resistance.

Outcomes:

  • Created systemic visibility into bottlenecks and deployment process variations
  • Identified teams with hidden internal dysfunction
  • Enabled data-driven decisions about team restructuring (broke apart struggling teams, reducing overall strain)

Phase 2: Prove the Model (Months 2-4)

Kanban Pilot with CTO’s Moonshot Teams

Selected highly technical teams working on innovation initiatives without heavy product oversight to demonstrate the value of flow-based delivery.

Implementation:

  • Transitioned pilot teams to Kanban methodology
  • Established weekly demos, creating natural accountability
  • Eliminated cross-departmental approval delays

Results: Within 2-4 weeks, visible progress convinced the C-suite to mandate scaling across the organization.

Phase 3: Scale and Optimize (Months 4-15)

Restructured Planning Process

  • Reduced PI Planning from 4 days to half-day quarterly planning sessions
  • Refocused time from process to outcomes
  • Financial Impact: $250,000 annual cost savings

Standardized Deployment Practices

  • Established 2-week deployment cadence across all 18 teams
  • Shifted from large-batch irregular releases to small-batch frequent deployments
  • Cleared 6-month backlog of undeployed work

Connected Work to Strategy

  • Coached Release Train Engineers to consistently ask whether work fed into company OKRs
  • Improved priority clarity and strategic alignment across teams

Improved System Reliability

  • Partnered with DevOps team to establish outage reporting
  • Technical Impact: 10% increase in system stability (2023)

Optimized Vendor Management

  • Restructured vendors under my domain
  • Financial Impact: $8,000 annual savings

Results

Operational Improvements

  • Deployment Velocity: Moved from irregular releases with 6-month backlogs to standardized 2-week deployment cycles
  • Cycle Time: Improved through systematic bottleneck identification and process mapping
  • System Stability: 10% improvement through established outage reporting
  • Risk Reduction: Smaller batch deployments reduced deployment risk

Organizational Improvements

  • Strategic Alignment: Improved priority clarity through consistent OKR-to-work connection
  • Team Health: Higher morale as coaches engaged more deeply with visible work
  • Conflict Resolution: Surfaced and resolved previously hidden team dysfunction

Financial Impact

  • $258,000 in annual cost savings: 
  • $250,000 from restructured planning (4 days → half day)
  • $8,000 from vendor management optimization

Constraints and Context

Political Environment: The transformation occurred within a challenging political environment. Open conflict between the CPO and CTO created friction that cascaded through the organization. Opposition from other VPs and C-suite members alternated between overt and covert resistance.

Incomplete Transformation: The engagement ended after 15 months when I was laid off as part of broader organizational cuts in January 2024. The layoff occurred before completing the full transition to flow-based delivery.

Cultural Limitations: Some cultural issues proved resistant to change within the available timeframe:

  • OKR misuse (treated as commitments with 100% completion targets instead of 80% stretch goals)
  • Reinforcement of wrong behaviors through promotion decisions
  • Deep-rooted political dynamics at executive level

Key Lessons

Visibility as Foundation: Standardization may be unpopular, but transparency is non-negotiable. You can’t fix what you can’t see. Jira standardization, despite resistance, enabled every subsequent improvement.

Executive Alignment is Critical: Executive-level conflict limited the scope of possible change. The CTO’s public support was essential for legitimizing the work and overcoming passive resistance, but misalignment at the C-suite level ultimately constrained the transformation’s reach.

Prove Value Quickly: The kanban pilot with moonshot teams demonstrated results within 2-4 weeks, creating momentum for broader adoption. Quick wins matter when facing organizational skepticism.

Change Management Requires Sustained Effort: Passive resistance doesn’t disappear. It shifts between overt and covert forms based on political dynamics. Sustained executive support and consistent follow-through are essential.

Scientific Publishing Organization SAFe Implementation

/0 Comments/in , /by

Case Study

Role: Engagement Lead (Consultant)
Timeline: July 2024 – February 2025 (8 months)
Organization Size: ~400-person publishing organization (18 teams, 3 value streams)
Team: 1 Agile Coach, 1 Product Coach (both reporting to Engagement Lead)

Challenge

A leading non-profit scientific publishing organization had scattered agile practices following a major reorganization. The organization faced critical delivery and operational problems:

Delivery Issues:

  • Too much work in process with no prioritization by business value
  • Overburdened, reactive teams managing multiple competing priorities
  • One small, low-complexity ART with no identified value streams
  • Lack of end-to-end product management causing delays and dependency conflicts

Organizational Dysfunction:

  • Siloed decision-making with each business area independently solving common problems
  • No visibility into how work aligned to strategic goals
  • Product management resistance despite early involvement in planning

Mandate: The VP of Transformation brought me in to lead an end-to-end SAFe implementation, scaling and formalizing agile practices to align 18 teams across 3 value streams to strategic goals.

Approach

Phase 1: Foundation and Structure (Months 1-3)

Value Stream Identification and ART Formation

Identified 3 value streams (Journals, Technology Refresh, Engagement Platform) and organized 18 teams into 3 ARTs with 1:1 value stream mapping.

Change Management Challenge:

  • Strong resistance from one product manager who felt threatened despite early involvement
  • Confrontational behavior disrupting team dynamics
  • General anxiety about process changes across organization

Executive Support: VP of Transformation sponsored the work and provided consistent backing throughout implementation.

Outcomes:

  • Established Executive Action Team and SAFe Transition Team
  • Implemented Portfolio Kanban (new for organization) forcing strategic prioritization conversations
  • Built champions network to reduce resistance
  • Resistant individual eventually removed; organization able to move forward

Phase 2: Training and Enablement (Months 2-5)

Comprehensive Training Program

Delivered multi-tiered training to build organizational capability and ensure sustainable practices.

Implementation:

  • Trained 18 teams on agile and SAFe foundations
  • Trained 25 leaders in Leading with Agility
  • Trained and certified 2 RTEs
  • Trained 5 coaches on coaching practices
  • Engaged 5 agile champions to drive continuous improvement
  • Delivered workshops: epic/feature/story writing, estimation, WSJF, Lean Portfolio Management, blameless retrospectives

Results: Built sustainable capability with trained RTEs and coaches ready to continue the work post-engagement.

Phase 3: Process Implementation and Refinement (Months 4-8)

PI Planning and Portfolio Management

Executed first PI Planning in January 2025, established portfolio governance, and built continuous improvement mechanisms.

Established Portfolio-Level Practices

  • Portfolio governance and intake flow
  • Regular cadence for all portfolio meetings
  • 2 Communities of Practice established (RTEs and others)
  • Value Management Office capabilities implemented

Addressed Organizational Design Gaps

Identified teams missing technical skills and Product Owners with too many dependencies. Recommended org design changes that were implemented during and after the engagement.

First PI Planning Outcomes

Teams surfaced significant dependencies and learned they needed better pre-planning and prioritization. These learnings informed improved backlog preparation practices for subsequent PIs.

Results

Organizational Improvements

  • Strategic Alignment: Work 95% aligned to division goals and strategy through Portfolio Kanban and value stream organization
  • Reduced Silos: Cross-functional collaboration greatly improved through ART structure
  • Teams Formed and Aligned: 18 teams organized in ARTs and aligned to value streams
  • Dependencies Reduced: Teams reformed during and after engagement to reduce dependencies

Capability Building

  • 18 teams trained and operating in SAFe model
  • 25 leaders equipped with agile leadership skills
  • 2 RTEs trained and certified to sustain practices
  • 5 coaches trained to continue team development
  • 5 champions driving continuous improvement culture
  • 2 active Communities of Practice established

Process Maturity

  • Portfolio governance and intake flow established
  • Portfolio Kanban forcing strategic prioritization conversations
  • Teams moving toward predictable delivery
  • Continuous improvement practices embedded

Constraints and Context

Resistance Management: The transformation faced initial resistance from product management. One individual’s confrontational behavior required eventual removal from the organization. Built champions network and provided real-time coaching to address broader concerns.

Organizational Design Limitations: Teams initially lacked appropriate technical skills and Product Owners, creating too many dependencies. Some recommended changes were implemented during the engagement, others after departure.

Successful Handoff: Transitioned leadership to Product Coach and Director of Strategy & Execution in February 2025. Teams in refinement mode with nothing at risk, positioned for continued improvement.

Key Lessons

Build Champions Early: Engaging 5 agile champions early created advocates who could address resistance and model desired behaviors throughout the organization.

Transparency Drives Prioritization: Portfolio Kanban visibility forced difficult but necessary conversations about what work truly mattered, ultimately aligning 95% of work to strategic goals.

First PI is About Learning: Teams surfacing dependencies and planning challenges in the first PI was expected and valuable. These learnings informed better practices for subsequent planning cycles.

Sustainable Capability Requires Investment: Training 2 RTEs, 5 coaches, and establishing Communities of Practice ensured the organization could continue improving after the engagement ended.

I was the bottleneck (and I didn’t know it)

/0 Comments/in /by

When I was leading agile strategy for a scaling software company, I had a problem I couldn’t see. My team would complete work, and I’d redo it. They’d make decisions, and I’d second-guess them. They’d solve problems, and I’d explain why my approach was better.

I told myself I was maintaining quality. Being thorough. Ensuring excellence.

Really, I was burning myself out and undermining their work because they weren’t doing it my way.

The breaking point came when I realized I was headed for one of those “exhaustion” rehab situations you hear about with celebrities. Everything lived in my head. Every decision needed my approval. Every output needed my review. I was the bottleneck. And I’d built it myself.

The Uncomfortable Truth

When I finally figured out that the way my team did things was different from mine (and often more effective) it was deeply uncomfortable. Because it meant admitting something I didn’t want to face: I had been confusing my personal preferences with actual requirements for success. Their approach wasn’t wrong. It was just different. And different felt like wrong because I’d never separated “what must happen for this to be successful” from “how I personally do this.”

The Real Problem with “I’ll Know It When I See It”

  • When success criteria live only in your head, you become the mandatory filter for everything.
  • Your team can’t make decisions without you because they don’t know what you’re actually evaluating. They think you’re judging the work, but you’re really judging whether they did it your way.
  • This isn’t a delegation problem. It’s not a trust problem. It’s a clarity problem.
  • You can’t clone yourself until you separate what MUST happen from how YOU happen to do it.

Here’s the Framework

Non-negotiables = Must be true for success (these are requirements)

  • Strategic alignment to company goals
  • Delivery predictability
  • Quality standards that protect the customer

Your way = How you personally achieve those requirements (these are preferences)

  • Your specific planning process
  • Your communication style
  • Your method of organizing information

The trap = Treating your preferences as requirements

When I made this shift, something remarkable happened. I stopped being the quality control checkpoint and started focusing where my brain actually needed to be: long-term vision and strategy. The work still got done. Often better. Just differently.

The Self-Assessment

Ask yourself:

  • When you review someone’s work, what are you actually evaluating? The outcome or the method they used to get there?
  • If someone achieved the right result using a completely different approach than yours, would you be satisfied? Or would you want them to redo it your way?
  • Can you articulate your non-negotiables in 3-5 clear statements? Or do you default to “I’ll know it when I see it”?
  • Are you the bottleneck for decisions that don’t actually require your expertise? What percentage of your day is spent reviewing work vs. setting direction?
  • When you say “I can’t delegate this,” is it because only you CAN do it, or because only you know what “good” looks like?

If you’re struggling to answer these clearly, you’re probably confusing your preferences with requirements. Which means you’re the bottleneck.

The Way Forward

  • Define what winning looks like – the actual outcomes and non-negotiables – not how you personally win.
  • Document it. Share it. Let your team figure out their own path to get there.
  • It will feel uncomfortable. Their way will look different. That’s the point.
  • You’re not trying to clone yourself. You’re trying to clone the results.
  • And that only works when you know what results actually matter.