2: PART I- Foundations
- Page ID
- 48745
\( \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{\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}\)Introduction
The SMDC case study is the backbone of this practicum. Every milestone, decision, and design conversation takes place within its context. Understanding SMDC not just as a project—but as a living, evolving organization with constraints, stakeholders, and ambitions—is essential for meaningful engagement with the risk work ahead.
In this chapter, we take a narrative and systems-level view of SMDC: who they are, what they’re building, what forces shape their world, and why risk management is not just important—but defining.
1. The Founding Problem: Self-Managed Diabetes is a Data Burden
Diabetes is a chronic condition. But unlike most chronic conditions, diabetes is largely managed not by clinicians—but by patients themselves. Every day, people with Type 1 and Type 2 diabetes make dozens of data-informed decisions:
-
When and what to eat
-
When and how much insulin to administer
-
How to interpret glucose fluctuations
-
When to seek help or adjust routines
Yet the data tools available to them are fragmented, technical, or emotionally confusing. Real-time Continuous Glucose Monitor (CGM) data lives in one app. Fitness data in another. Meal logs in a third. Advice from clinicians might arrive by text, email, or not at all.
This is the gap SMDC (Self-Managed Diabetic Care Inc.) was formed to address.
2. The SMDC Vision
SMDC is a health technology startup with a mission to:
“Translate complex diabetes data into simple, actionable insight that builds trust, safety, and independence.”
Their goal is to design a patient-facing dashboard that:
-
Consolidates device data
-
Visualizes blood glucose trends and alerts
-
Offers behavior prompts that support self-care
-
Enables secure data-sharing with clinicians
-
Respects patients’ autonomy, privacy, and emotional experience
This is not just a product—it’s a personal assistant, risk interpreter, and decision partner for people managing one of the world’s most data-dependent conditions.
3. Timeline, Funding, and Product Scope
As the course begins, SMDC is six months into its startup life. It has:
-
A small seed funding round (enough to build an MVP)
-
A multidisciplinary founding team (tech, product, and clinical advisory)
-
A commitment to pilot with early user groups in three months
-
A narrow MVP scope with high expectations
The team is under pressure to:
-
Deliver a demo-ready product within a fixed sprint calendar
-
Balance speed and clinical credibility
-
Meet HIPAA compliance
-
Establish internal process and culture from scratch
Startup risk is baked into every aspect of the SMDC timeline. There is no buffer. Every decision, control, and breakdown has consequence.
4. Key Stakeholders and Their Tensions
SMDC is a system of humans. The risks and decisions in this book live in the tensions between stakeholders:
Patients
-
Manage diabetes daily
-
Seek tools that feel supportive, not judgmental
-
Vary widely in tech comfort, education, language, and routine
-
Care about clarity, control, and emotional safety
Clinicians
-
Provide expert guidance, but only intermittently
-
Need accurate data that doesn’t overwhelm
-
Are wary of tools that confuse patients or undermine their role
-
Balance legal liability with ethical responsibility
Engineers
-
Build the dashboard logic, data architecture, and APIs
-
Depend on third-party data (CGMs, trackers, nutrition apps)
-
Work under tight technical constraints
-
Often lack visibility into clinical or emotional design issues
Product and UX Designers
-
Bridge user needs and business requirements
-
Translate between behavior, interface, and compliance
-
Make tradeoffs between clarity, control, and speed
Regulators, Funders, and Partners
-
Influence how features are scoped and communicated
-
Require documentation, consent protocols, and safe defaults
-
Evaluate whether SMDC builds trust and demonstrates future value
All these voices are active—but not always aligned.
5. Why Risk Thinking Matters at SMDC
SMDC operates in the real world, with real stakes. Risks at SMDC are:
-
Technical (system downtime, data mismatch, alert failure)
-
Clinical (dangerous recommendations, misread trends)
-
Emotional (patient overwhelm, clinician distrust)
-
Cultural (inequity, exclusion, usability assumptions)
-
Legal (HIPAA, FDA oversight, audit trails)
-
Strategic (burnout, funding gaps, unclear handoffs)
Risk cannot be owned by one team or avoided through perfection. It must be surfaced, structured, and shared.
In this practicum, you will step into the SMDC team as a risk strategist and analyst, embedded in their journey. Your work will not be theoretical—it will reflect the real choices that early-stage teams must make under pressure, ambiguity, and mission-driven urgency.
6. A Final Word Before You Begin
Remember: you are not just evaluating someone else’s project. You are stepping into a living system—with data, tension, emotion, and tradeoffs.
You are here to help a team manage risk—not just protect the product, but protect the people it’s designed to serve.
Now turn the page—and step into SMDC.
- 2.1: Chapter 1 – Understanding Risk in Practice
- Chapter 1 redefines risk as a dynamic, integral part of project success—introducing key distinctions, lifecycle integration, five management pillars, and a risk-aware leadership mindset.
- 2.2: Chapter 2 – The SMDC Case Study
- Chapter 2 introduces SMDC, a simulated health-tech startup navigating real-world constraints and complex risks, serving as the immersive, evolving environment for practicing risk management.
- 2.3: Chapter 3- Managing Diabetes in a Data-Driven World- What Risk Thinkers Need to Know
- Chapter 3 introduces diabetes management challenges, highlighting data fragmentation, patient risks, and social factors while framing SMDC’s mission and the need for structured risk analysis starting with Milestone 1.
- 2.4: Chapter 4- Building SMDC- The Real-World Challenges of Launching a Health-Tech Startup in a High-Stakes Environment
- This chapter outlines SMDC’s real-world startup challenges—technical, regulatory, organizational, and user-driven—framing the need for structured risk thinking as students begin Milestone 1.
Thumbnail: OpenAI. AI-Generated Images Using ChatGPT with DALL·E. 2024. Digital illustration. OpenAI, https://openai.com.

