5: Sample Templates
- Page ID
- 48830
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)
๐ Appendix A.1 – Risk Breakdown Structure (RBS) Template
Use in Milestone 1: Structuring Risk
This template helps teams create a 3-tiered Risk Breakdown Structure by organizing risks into categories and subcategories, moving from general domains to specific examples.
๐งฉ Structure:
| Level | Purpose | Example |
|---|---|---|
| Level 1 | Broad Risk Domain | Technical Risk |
| Level 2 | Subdomain / Category | Device Integration |
| Level 3 | Specific Risk | Bluetooth sync fails with certain glucose monitors |
๐ Blank RBS Table:
| Level 1 – Risk Domain | Level 2 – Category | Level 3 – Specific Risk Examples |
|---|---|---|
✍️ Instructions:
-
Brainstorm risks from planning inputs (scope, budget, schedule, etc.)
-
Group them by domain (e.g., Technical, Human, Clinical, Regulatory, UX)
-
Drill down to specific, nameable risks
-
Ensure each branch has at least 2–3 entries at Level 3
๐ Appendix A.2 – Planning Meeting Input Checklist
Use in Milestone 1: Facilitating a Risk Planning Session
This checklist ensures all foundational elements are reviewed before risk structuring begins.
๐งพ Planning Inputs:
| Input Type | Guiding Questions | Notes |
|---|---|---|
| Scope | What’s in vs. out? What’s vague or evolving? | |
| Schedule | What is the pilot deadline? What dependencies exist? | |
| Cost | What’s funded? What’s forecasted? Are resource assumptions stable? | |
| Communication | What communication channels are formal/informal? Are there silos? | |
| Enterprise Environmental Factors (EEFs) | What external factors (laws, norms, vendors) shape risk? | |
| Organizational Process Assets (OPAs) | What templates, norms, or past habits influence this team’s behavior? |
๐ Appendix A.3 – Risk Statement Template
Use in Milestone 2: Prioritizing and Categorizing Risk
This template helps teams write clear, actionable, and non-ambiguous risk statements that can be tracked, scored, and discussed effectively.
๐ฏ Format:
Each risk should be written using this structured sentence:
“There is a risk that [uncertain event] may occur, which would lead to [impact], affecting [project objective(s)].”
๐งพ Example Risk Statements:
-
“There is a risk that patient alert thresholds will be misconfigured, which would lead to inappropriate warnings, affecting user trust and clinical safety.”
-
“There is a risk that API vendor changes could break real-time sync, impacting product stability and delaying launch.”
๐งช Risk Statement Table:
| Risk ID | Statement | Source | Owner | Notes |
|---|---|---|---|---|
| R-001 | ||||
| R-002 | ||||
| R-003 |
๐ Appendix A.4 – Risk Impact Matrix Template
Use in Milestone 2: Ranking Risk by Impact and Likelihood
The impact matrix helps prioritize risks by scoring them along two dimensions:
-
Likelihood (1–5): How likely is this to occur?
-
Impact (1–5): How severe would the consequences be?
๐ Matrix Grid:
| Impact: 1 (Low) | 2 | 3 | 4 | 5 (High) | |
|---|---|---|---|---|---|
| Likelihood: 5 (Very Likely) | |||||
| 4 | |||||
| 3 | |||||
| 2 | |||||
| 1 (Rare) |
Each risk is plotted as a coordinate point (e.g., R-004 = Likelihood 4, Impact 5)
๐ Scoring Table:
| Risk ID | Description | Likelihood (1–5) | Impact (1–5) | Combined Score (L×I) | Priority Rank |
|---|---|---|---|---|---|
| R-001 | |||||
| R-002 | |||||
| R-003 |
๐ Appendix A.5 – Stakeholder Risk Scoring Sheet
Use in Milestone 3: Validating Risk Perception Across Roles
This sheet allows teams to gather and compare how different stakeholders rank the importance of specific risks based on their expertise or role.
๐งฉ Instructions:
-
Distribute risk statements to 3–5 stakeholders (or personas).
-
Each scores risks on a 1–5 scale for importance or concern.
-
Collect scores and analyze patterns of agreement or disagreement.
๐ Stakeholder Input Table:
| Risk ID | Risk Statement | Patient Score (1–5) | Clinician Score (1–5) | Engineer Score (1–5) | Product Score (1–5) | Avg / Notes |
|---|---|---|---|---|---|---|
| R-001 | ||||||
| R-002 | ||||||
| R-003 |
๐ง Optional Analysis Prompts:
-
Where did stakeholder views differ most sharply?
-
Are there “blind spots” where one group scored a risk low and others scored it high?
-
What does this suggest about stakeholder alignment and risk ownership?
๐ Appendix A.6 – Preventive Control Checklist
Use in Milestone 4: Designing Practical Control Strategies
This template helps teams turn risk concerns into preventive actions with clear ownership, timing, and review criteria.
✅ Control Design Table:
| Control ID | Risk Addressed | Preventive Control Action | Owner | Timing / Frequency | How Will We Know It’s Working? |
|---|---|---|---|---|---|
| C-001 | |||||
| C-002 | |||||
| C-003 |
๐ก Control Examples:
-
“Create clinician review sign-off for all alert language before pilot”
-
“Run weekly sync test with test data to detect device API drift”
-
“Add onboarding tooltip to clarify ‘out of range’ thresholds for new users”
Controls can also be annotated with:
-
Priority level (P1–P3)
-
Preventive vs. Detective vs. Corrective
๐ Appendix A.7 – Root Cause (Fishbone) Diagram Template
Use in Milestone 5: Diagnosing Underlying Risk Causes
This visual tool helps teams uncover the root causes behind a recurring or high-impact risk by grouping contributing factors into categories.
๐ฏ Purpose:
Move beyond the surface-level issue (“Alert failed”) to explore system-level causes (“Lack of QA process,” “Confusing design handoff,” “Vendor delays”).
๐ Fishbone Structure (Cause Categories):
-
People
-
Process
-
Technology
-
Environment
-
Communication
-
Tools / Vendors
✏️ Sample Setup (Diagram):
Effect (The Risk) → [Alert fatigue during pilot]
Branches →
↳ People: unclear roles
↳ Process: skipped usability test
↳ Technology: alert logic hardcoded
↳ Environment: rushed deadline
↳ Tools: EHR data delay
๐ Blank Table Version:
| Category | Contributing Factors |
|---|---|
| People | |
| Process | |
| Technology | |
| Environment | |
| Communication | |
| Vendors / Tools |
๐ Appendix A.8 – TOWS Matrix Worksheet
Use in Milestone 6: Framing Strategic Risk Moves
This matrix inverts SWOT into TOWS to generate strategy options that reduce risk using strengths and opportunities.
๐ Definitions:
| TOWS Quadrant | Description |
|---|---|
| S–O (Strength–Opportunity) | Use strengths to leverage opportunities and reduce risk |
| S–T (Strength–Threat) | Use strengths to defend against threats |
| W–O (Weakness–Opportunity) | Use opportunities to overcome internal weaknesses |
| W–T (Weakness–Threat) | Minimize weaknesses to avoid external threats |
๐ Worksheet Template:
| TOWS Strategy Type | Strategy Ideas | What Risk(s) Does It Address? |
|---|---|---|
| S–O | ||
| S–T | ||
| W–O | ||
| W–T |
๐ Example Entry:
| Type | Strategy Idea | Risk Addressed |
|---|---|---|
| S–T | Use our clinical advisor team to validate alert safety before release | Alert misinterpretation by patients |
๐ Appendix A.9 – Patient-Facing Business Model Canvas (Risk-Adapted)
Use in Milestone 7: Mapping Risks from the Patient Perspective
This adapted version of the Business Model Canvas helps teams surface risks embedded in how patients experience the product, not just how it’s built.
Each segment prompts teams to think about:
-
How the product supports (or fails) patient goals
-
Where risk might emerge due to assumptions, gaps, or unmet needs
-
What emotional, behavioral, or access-based risks are involved
๐งญ Canvas Segments + Risk Prompts:
| Canvas Segment | Patient-Facing Questions | Risk Prompt |
|---|---|---|
| Customer Segments | What types of patients will use this? Who is excluded? | Exclusion due to tech, language, or health literacy |
| Value Proposition | What promises are we making to the patient? | Confusion or disappointment if expectations aren't met |
| Channels | How do patients access the tool? | Device or digital access barriers |
| Customer Relationships | What tone or persona do we convey? | Feeling judged or unsupported |
| Revenue | Who pays, and what do patients know about it? | Distrust if data use isn’t transparent |
| Key Activities (Patient) | What must the patient do to benefit? | Data fatigue or disengagement from complexity |
| Key Resources (Patient) | What knowledge, tools, or support does a patient need? | Risk of dropout due to insufficient onboarding |
| Key Partners | Who else supports the patient (clinicians, caregivers)? | Breakdown in shared care plans |
| Cost (to Patient) | What time, energy, or trust must the patient spend? | Emotional burden outweighs perceived value |
You may use a visual canvas or complete this table with 1–2 risks per section.
๐ Appendix A.10 – Decision Tree Template
Use in Milestone 10: Structuring and Evaluating Risk Tradeoffs
This decision modeling tool helps teams visualize:
-
A central decision
-
Possible actions
-
Consequences or follow-ups
-
Costs, likelihoods, or strategic considerations
๐ณ Components of the Decision Tree:
-
Decision Node: What are we choosing between?
-
Branches: What are the possible actions/options?
-
Chance Nodes: What could happen next?
-
Outcome Nodes: What is the final result or risk?
๐ Example (Narrative Style):
Decision: Redesign alert or suppress alert volume?
-
Option A: Redesign Alert
-
Outcome 1: Improved clarity and trust (80%)
-
Outcome 2: Delay to pilot launch (20%)
-
-
Option B: Suppress Alert Volume
-
Outcome 1: Patient safety risk (30%)
-
Outcome 2: No change noticed (70%)
-
๐ Blank Table Format:
| Decision | |
|---|---|
| Option A | |
| → Outcome 1 | (Likelihood %, Impact) |
| → Outcome 2 | |
| Option B | |
| → Outcome 1 | |
| → Outcome 2 |
You may also draw this using a branching tree format, software diagramming tools, or slides.
๐ Appendix A.11 – Contingency Planning Sheet
Use in Milestone 11: Planning for Risk Activation
This sheet helps teams define what to do when a specific risk activates—including triggers, roles, immediate actions, and escalation paths.
⚠️ For Each Risk, Capture:
| Field | Description |
|---|---|
| Risk Scenario | A clear description of the risk (e.g., “API sync failure on new device”) |
| Trigger Condition | What event will signal that this risk has occurred? |
| Immediate Response | What happens first? Who is notified? What is paused or contained? |
| Primary Owner | Who is responsible for leading the response? |
| Support Roles | Who else must be involved (e.g., clinical, comms, tech)? |
| Communication Plan | Who needs to be informed (internally or externally)? How quickly? |
| Recovery Plan | What will restore stability, functionality, or trust? |
| Escalation Threshold | At what point does this become a Tier 2 or Tier 3 issue? |
๐ Sample Entry:
| Risk | Trigger | Immediate Response | Owner | Escalation |
|---|---|---|---|---|
| Consent flow leads to patient confusion | Drop in form completion rate > 30% in 48 hrs | Pause campaign, notify PM & legal | Product Manager | Tier 2 if not resolved in 3 days |
๐ Appendix A.12 – Integrated Risk Review Table
Use in Milestone 12 & Capstone (4.2.1): Synthesizing Risk Across Milestones
This table is designed to help students or teams track risk evolution, recurrence, and insights across the full SMDC case.
It helps surface:
-
Where a risk originated
-
How it was addressed
-
Whether it reappeared
-
What cultural or process issues made it worse—or better
๐ Table Template:
| Milestone | Key Risk(s) | Control or Decision | What Worked | What Resurfaced Later | Cultural Factors (SEW, Collaboration, Memory) |
|---|---|---|---|---|---|
| M2 – Risk Impact Matrix | Patient alert misinterpretation | Ranked as low priority | Prioritized others | Became major issue in M7 | Early silence, empathy gap |
| M5 – Root Cause | Repeated data sync issues | Control added | Bug resolved | Similar issue in M9 | No team-wide debrief, info silos |
| M8 – Stakeholder Conflict | Misaligned clinician vs. dev priorities | Conflict mapping | Highlighted key tensions | Delayed resolution | Roles weren’t given equal decision power |
๐ Appendix A.13 – Final Recommendation Slides Template
Use in Capstone Presentation (4.2.2)
This template provides a slide-by-slide guide for presenting your final risk recommendations to instructors, stakeholders, or peers. It’s designed for clarity, brevity, and synthesis across milestones.
๐ฅ️ Suggested Slide Outline:
| Slide | Title | Content |
|---|---|---|
| Slide 1 | Executive Summary | Brief overview of key findings, priority risks, and high-level takeaways |
| Slide 2 | Top 3 Risk Areas | Describe the most urgent or impactful risks that remain |
| Slide 3 | Control Insights | What controls worked? What failed? What surprised you? |
| Slide 4 | Stakeholder Alignment | Where were the biggest conflicts or blind spots across roles? |
| Slide 5 | Cultural Recommendations | Based on SEW, memory, collaboration—what norms or systems must evolve? |
| Slide 6 | Action Plan | Your proposed next steps: policies, rituals, systems, roles |
| Slide 7 | Call to Action / Closing | One statement that captures your risk philosophy or what future teams must remember |
๐ Tips:
-
Use visuals sparingly—emphasis should be on message clarity
-
Practice a 5–7 minute delivery if used in class
-
Consider sharing in PDF format for archival
๐ Appendix A.14 – Risk Culture White Paper Outline
Use in Optional Extension (4.2.3)
This scaffold supports students in drafting a professional, systems-level reflection on risk culture. It draws on course themes from Chapters 4.1–4.2 and encourages original thinking.
๐ Structure:
| Section | Prompt |
|---|---|
| Title Page | Choose a compelling, precise title. Include author, date, subtitle (optional). |
| Executive Summary | 1–2 paragraphs summarizing your position and previewing key recommendations |
| Definition of Risk Culture | Define the term. Frame it in your own words. Cite course models or moments. |
| Pillar 1 – Emotional Fluency (SEW) | How should teams become better at naming and responding to discomfort and uncertainty? |
| Pillar 2 – Communication Systems | What rituals, formats, or expectations should change? What does risk-safe collaboration look like? |
| Pillar 3 – Organizational Memory | How should teams capture lessons, document failure, and reduce recurrence? |
| Call to Action | What should your audience do differently now? What mindset should they adopt? |
| Closing Reflection | How has your view of risk leadership evolved? What do you carry forward from this experience? |