Morgan denner

Morgan dennerMorgan dennerMorgan denner

Morgan denner

Morgan dennerMorgan dennerMorgan denner
  • Home
  • About Me
  • Approach
  • Examples
    • A Language of Teamwork
    • Empowered Team Culture
    • Medical Billing Flows
  • Contact

Building Empowered Team Culture in a Community Training Ecosystem

Get the Slide Deck

Program Manager

No one can ever truly prepare for teamwork

You have to jump in. It's not enough to learn about empowered teamwork in a classroom. 


People have to train in different ways than they were taught in school. 


Empowered teams practice removing fear and perfection. It requires collective decision making and practice. 

One person can't do it alone

Everyone needs to share the same mindset and behaviors:


  1. Interacting with the team to define process.
  2. Delivering working results early and often.
  3. Collaborating with clients and end-users.
  4. Responding to change when it makes sense.


People bring preconceptions about what it means. They may be resistant to change the ways they think and work. 

Intended business outcomes

  1. Build a common language of agility.
  2. Remove barriers to shared leadership.
  3. Model behavior to build opportunities to practice.
  4. Foster leaders who are in service of others' growth.
  5. Encourage continuous improvement in processes
  6. Provide room for experimentation and failure.

See it in action

    Project summary

    Timeline

    9 months

    Business

    Tech Fleet is on a mission to be the change that tech needs for the future. The organization offers community-driven training for people to build real team experience.

    Responsibilities

    With a team, I was responsible for:

    1. Architecting information
    2. Coaching others
    3. Defining Vision and scope
    4. Designing the experience
    5. Implementing strategy
    6. Measuring impact
    7. Managing the project
    8. Performing Research
    9. Writing Content

    Team Process

    Multiple cross-functional teams of 3 to 5 people ran Kanban method.

    How we measured success

    Cross-Functionality

    Cross-Functionality

    Cross-Functionality

    Measuring how often departments work together to achieve outcomes.

    Deliverables

    Cross-Functionality

    Cross-Functionality

    Measuring how often deliverables are completed in project success.

    Drop Out Rate

    Cross-Functionality

    Drop Out Rate

    Measuring how often people leave project teams. 

    Ownership

    Psychological Safety

    Drop Out Rate

    Measuring how much people embody a sense of ownership in their work..

    Preparation Level

    Psychological Safety

    Psychological Safety

    Measuring how prepared teammates feel to follow agile philosophies.

    Psychological Safety

    Psychological Safety

    Psychological Safety

    Measuring how often people believe they can fail and challenge without punishment.

    Shared Leadership

    Training Satisfaction

    Training Satisfaction

    Measuring the levels that people support each others' growth.

    Training Satisfaction

    Training Satisfaction

    Training Satisfaction

    Measuring how happy people are with the organization's training.

    Our target audience's pain points

    New graduates and career changers come from different careers and backgrounds. They face many barriers to succeeding in the professional world.

    1. Schools teach basic hard skills.
    2. Schools teach waterfall mindsets.
    3. Companies expect prior on-the-job experience 
    4. Teamwork requires mindset and behavior changes.
    5. Company job expectations differ.
    6. Advice varies about what it takes to succeed.
    7. Trainees are self-guided about properly doing cross-functional teamwork.

    The process for end-users

    1. Trainees take basic training classes on agility and shared leadership. 
    2. The organization maintains onboarding materials to build expectations. 
    3. Trainees work together as peers without experts.
    4. Project coordinators interview trainees.
    5. Teams rely on handbooks and videos for basic training. 

    Key changes we made

    1. Five weeks of coaching on teams.
    2. Overcoming resistance to change.
    3. Team-based reflections of learning.
    4. Behavior modeling in teamwork.
    5. Reward those who built mindsets.
    6. Workshop templates for teams.
    7. Continuous improvement training.
    8. Measuring levels of team maturity.

    Start with the "why"

    Key strategies

    Build Ownership

    Teammates need to feel they have control over their own future. They have to feel that what to do and say matters to the shared outcome. 

    Chunk the Learning

    We built training experiences that rely on progressive disclosure of information. This helps trainees learn a little at a time and start to see connections between concepts. 

    Discuss Resistance to Change

    Teams must face their own barriers, like doing something completely different from how they have been trained. In moments of stress, teams resort back to what they think is comfortable: waterfall models. We openly discuss the shift in the mindset while it was being formed through team discussions.

    Model Behavior for Teams

    People can read books, watch videos, hear experts talk, and still not be ready to perform cross-functional work. They need to see how it's done. They need to decide together. Not only do we have observation opportunities, but we have training templates that model behavior. 

    Prioritize Human Connection

    Teammates must build trust with each other and see that they are not in competition. We fostered "human time" where people got together to discuss life. This helped teams open up and see others as peers.

    How it's going so far

    In just three months of live coaching, training teams have transformed. 


    Teammates work together to produce shared outcomes. 


    Clients, teammates, and coaches are all working in unison across functions. 


    Teams are progressively making the connections they need to change their mindset and behavior. 

    What people say about the changes

    Measuring the impact

    Levels of Agility

    Empowered team maturity increased immensely during and after the projects. 


    1. Cross-functional teamwork levels increased 20%
    2. Ownership levels improved 14%
    3. Service leadership and psychological safety levels increased around 10%
    4. Preparation levels increased 20%

    Training Satisfaction

    We received a 75% training satisfaction score. This improved over 15%. People mentioned the workshop templates helped them set expectations, and do the work well. They appreciated the guidance that coaches provided while working with teams who were unsure how to proceed in the work. 

    Deliverables Completion

    Because of our common language framework for skills, tasks, deliverables, and project milestones, we saw more consistent creation of teamwork deliverables. Caches coached teams to run training templates that helped them model behavior and do the work successfully for the first time. Best of all, they didn't need a mentor giving them answers; they self-organized together.

    What we learned through validation

    1. Teams expressed desires to get subject matter expertise in the moments they are doing agile work.
    2. People struggled to work through uncertainty with clients.
    3. Some still misinterpreted the components of empowered teamwork even after training. 
    4. Co-leads dictated to apprentices instead of offering shared leadership and flat hierarchy structures.
    5. Behavior and mindset shifts take time, and people need to hear that they won't improve their agility quickly. 
    6. Some trainees didn't attend all of the workshops we've offered in pre-kickoff onboarding.

    Future recommendations

    1.  How might we decrease project training abandon rate?
    2. How might we increase full workshop attendance?
    3. How might we further reduce the gap between knowledge and readiness?
    4. How might we generate buy-in for team practices to those who haven’t shifted mindsets yet?
    5. How might we improve teammate ownership on an individual level?
    6. How might we accurately represent inclusion, learning, contribution, and challenger safety levels?

      Copyright © 2025 Morgan Denner - All Rights Reserved.

      • Home
      • About Me
      • Approach
      • A Language of Teamwork
      • Empowered Team Culture
      • Medical Billing Flows
      • Contact

      Powered by user-centered design

      This website uses cookies.

      We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

      Accept