9: Launching and Sustaining a Team

Quality and Regulatory Compliance in Bioscience · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    Read aloud

    How

    Speed: 1×
    Light up
    Highlight

    Symbols: Mulberry Symbols, © 2018–2026 Steve Lee, CC BY-SA 4.0 (licence, the set), the site's own copies.

    From LibreTexts, under CC BY-SA 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    9: Launching and Sustaining a Team
    Learning Objectives

    After completing this chapter, you should be able to:

    • Explain how a team charter guides a quality improvement project.
    • Define a team’s purpose, scope, goals, and expected results.
    • Select members whose knowledge, skills, and experience match the work.
    • Establish ground rules and clear decision authority.
    • Plan meeting schedules, resources, and management support.
    • Describe common stages of team development.
    • Track actions and results, sustain participation, and transfer completed work.

    A team’s purpose, structure, and roles should fit the work. The team turns those choices into a charter and work plan. Follow-up shows whether an approved change was completed, whether it improved performance, and who will maintain it.

    A team can have skilled members and still struggle to get started. People may agree that a problem matters while holding different ideas about what the team should do. One person expects a new procedure. Another expects new equipment. A third assumes that attending meetings is the only commitment required. These differences often remain hidden until work slows down.

    Launching a team means agreeing on the assignment, authority, and support before work begins. Sustaining a team means maintaining the conditions that let people contribute. Both matter when laboratory, production, quality, maintenance, and support staff depend on one another. A change tested only during the day may leave night-shift staff without the information or resources they need.

    This chapter follows a hypothetical team improving freezer-alarm handoffs at a research-reagent facility. The situation, measurements, and charter are teaching examples, not a documented company case. A separate historical story describes the launch and early work of the National Institutes of Health’s ACTIV partnership. Together, the examples show how a clear purpose becomes organized work.

    • 9.1: Developing a team charter
      This page outlines the importance of a team charter as a brief agreement that defines a team's purpose, goals, and operating procedures. It emphasizes collaborative development among team members and highlights the need for clarity and conciseness. While it aids in understanding roles and expectations, it does not solve all conflicts. Changes may be needed as circumstances evolve, which should follow formal procedures for revisions.
    • 9.2: Example- Freezer-alarm handoff team charter
      This page describes an eight-week quality improvement project aimed at addressing the issue of untimely acknowledgment of live freezer alarms, which were noted to be at 30%. The team developed a charter focusing on improving acknowledgment and escalation processes while preserving existing workflows. The objective was to decrease undocumented acknowledgments to 10% and included clear deliverables like workflow mapping and training records.
    • 9.3: Establishing purpose, scope, goals, and expected results
      This page emphasizes the significance of a team's purpose, scope, goals, and deliverables in project management. A clear purpose guides decision-making, while the scope delineates project boundaries. Goals should include specific improvement metrics and evaluation timelines, necessitating precise definitions and record-keeping.
    • 9.4: Selecting members for knowledge, skills, representation, and diversity
      This page emphasizes the importance of selecting team members based on their relevant expertise for assignments, rather than their job titles. It advocates for diverse representation to enhance insights and suggests maintaining a core group for meetings while consulting specialists as needed. Clear expectations for contributions and time commitment are essential, along with supervisory support for sustained engagement.
    • 9.5: Establishing ground rules and decision authority
      This page outlines essential ground rules for effective teamwork, emphasizing the importance of preparedness, inclusivity, evidence-based discussions, and verification of assumptions. It highlights the need for psychological safety to encourage open communication and clarifies decision-making authority and processes. Additionally, it identifies the importance of an escalation path for urgent issues, ensuring timely responses and preventing delays.
    • 9.6: Planning schedules, meeting logistics, and resources
      This page emphasizes the significance of work plans in project management, outlining the structure of tasks, owners, dates, and dependencies. It highlights the importance of training staff according to approved procedures and identifies milestones as crucial progress checkpoints. Effective meetings are characterized by careful scheduling, clear agendas, and timely information sharing. Resources go beyond financial aspects to include time and support.
    • 9.7: Securing management support
      This page highlights the essential role of sponsors in resource allocation and decision-making for teams. Active sponsorship involves making clear commitments and documenting agreements. Effective communication of progress, goals, milestones, and risks is vital, along with promptly reporting barriers to management. The emphasis is on maintaining realistic expectations and adapting to changes in resource availability to ensure project deadlines are met.
    • 9.8: Example - Building a shared response through ACTIV
      This page discusses the NIH and the Foundation for the NIH's collaboration, ACTIV, initiated in April 2020 to boost COVID-19 treatment and vaccine research. It formed four working groups led by NIH and industry co-chairs, focusing on organized teamwork for clinical trials, supported by a resource pledge. By July 2020, a master protocol was established for coordinated research, highlighting the importance of organizational structure beneficial for various team sizes.
    • 9.9: Stages of team development
      This page discusses Bruce Tuckman's team development model, outlining its five stages: forming, storming, norming, performing, and adjourning. It emphasizes the dynamics of teamwork at each stage, including orientation, conflict resolution, coordination, effective execution, and closure.
    • 9.10: Tracking actions, progress, and accountability
      This page highlights the significance of action and decision logs in project management for enhancing accountability and effective communication. It emphasizes task assignment, documentation of decisions to avoid revisiting issues, and tracking obstacles and outcomes. Performance measures and data review are discussed to identify trends and challenges in acknowledgment and response processes, ensuring informed decision-making throughout the project.
    • 9.11: Sustaining participation and recognizing contributions
      This page discusses how effective team participation is maintained through recognition of contributions and addressing underlying issues affecting engagement. It emphasizes the importance of clear communication and record-keeping, as well as the delegation of responsibilities with performance monitoring. A sustainment plan is also highlighted, detailing ownership and strategies to handle performance challenges, ensuring the team's long-term success.
    • 9.12: Chapter Summary
      This page emphasizes the significance of a team charter in fostering unity among team members by clarifying goals, authority, and expectations. It stresses effective team composition, respectful engagement, and clear decision-making. Leaders are encouraged to clarify expectations and support team dynamics through development phases. Accountability is enhanced using tools like action and decision logs.


    This page titled 9: Launching and Sustaining a Team was last modified on Thu, 05 Nov 2026 10:12:52 GMT and is shared under a CC BY-SA 4.0 license and was authored, remixed, and/or curated by Emalee MacKenzie.