9.3: Establishing purpose, scope, goals, and expected results

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.3: Establishing purpose, scope, goals, and expected results

    A team’s purpose explains why its work matters. In the freezer example, the purpose is a more reliableBiotechnology quality improvement framework.png part of the alarm-response process used to protect research materials. “Hold weekly meetings” is an activity, not a purpose. People are more likely to make useful choices when they understand the result the activity is meant to support.

    Scope identifies the boundaries of the assignment. It includes what the team will study and what it will leave to other people or projects. A narrow scope can still address an important problem. Improving handoffs for two freezers may provide a manageable starting point before the organization considers a wider change.

    A goal states the improvement intended, its measure, and its evaluation period. In this example, 12 of 40 eligible alarm events lacked documented acknowledgment within the approved time: 12 ÷ 40 × 100 = 30%. The proposed goal is no more than 10% over four full weeks after implementation. These are hypothetical project choices, not industry standards or new acceptance limits.

    Define an eligible alarm event, the timing start and end, the approved response interval, and any justified exclusions before comparing results. Count an event once even if it produces several messages or reaches several staff members. Use records that can reveal events whose notifications were not delivered. For this project, late, absent, or unverifiable acknowledgments all count as lacking documented timely acknowledgment. Report those categories separately as well, so a record gap is not mistaken for proof of what happened.

    Apply the same rules to the baseline and comparison period. Show the numerator and denominator: one event out of Biotechnology quality improvement framework.pngten and ten out of one hundred both equal 10%, but provide different amounts of evidence. If a new definition changes the baseline count, recalculate and document the baseline before judging improvement.

    If no eligible live alarm events occur, the percentage is undefined, not zero. Approved test messages can check routing and workflow, but they do not establish live-response performance. Keep them separate from live events. Few observations may require a longer evaluation or a limited conclusion even when the numerical target is met.

    Deliverables are the specific outputs the team must provide, such as an approved workflow or completed training records. They help show that assigned work was finished. However, a completed document alone does not show that performance improved. The team needs both deliverables and evidence about results.

    Watch for scope creep, the gradual addition of work beyond the agreed assignment. A request to redesign the entire cold-storage system may be reasonable, but it requires a separate decision about time, resources, and authority. Record the request and bring it to the sponsor. Do not allow an informal suggestion to become an unplanned obligation.


    This page titled 9.3: Establishing purpose, scope, goals, and expected results was last modified on Sun, 08 Nov 2026 11:37:17 GMT and is shared under a CC BY-SA 4.0 license and was authored, remixed, and/or curated by Emalee MacKenzie.