Flagship Case Study
Ask What Matters Seeing Acromegaly
A branching medical scenario designed to help healthcare professionals recognize a pattern that can be easy to miss - while showing how the questions they ask affect both clinical clarity and patient trust.
Project Type
Branching Medical Scenario
Audience
Healthcare Professionals & Frontline Support Staff
Tools
Storyline 360, Camtasia, Magnific
Primary Focus
Pattern Recognition & Clinical Decision-Making
Interactive Demo
Try a decision before you read the case study.
This space can hold a short Storyline demo that introduces the patient, gives the visitor one meaningful decision, and shows the Trust and Clinical Clarity feedback system in action.
Storyline Demo Placeholder
Ask What Matters
Later, this entire panel can be replaced by the live embedded Storyline demo without changing the surrounding case-study design.
The Performance Problem
The problem was not simply knowing the symptoms.
It was recognizing the pattern.
Acromegaly can develop gradually. Symptoms may appear separately, be treated independently, or seem unrelated until someone begins connecting what the patient has been experiencing over time.
Recognition
Symptoms arrive separately
Individual symptoms may not immediately point toward one diagnosis. Learners need practice noticing when separate observations begin to form a meaningful pattern.
Communication
Trust affects what gets shared
The questions a healthcare professional asks - and how they respond - can determine whether the patient continues revealing information that may become clinically important.
Decision-Making
The next step matters
Learners need to move from isolated findings toward an appropriate next action without pretending the situation is more certain than it really is.
Audience & Performance Goal
Different roles. One connected patient experience.
Clinical Team
Notice more than the presenting symptom.
Physicians, advanced practice providers, nurses, and medical assistants practice recognizing patterns, asking stronger questions, and deciding what should happen next.
Frontline Staff
Recognize when a detail may matter.
Front-desk and support staff may hear or see something before the formal clinical assessment begins. Their role is not diagnosis - it is noticing, listening, and passing useful information forward.
Research & SME Input
The patient experience changed the design.
The project began with the experience of a close friend who spent years searching for answers to a collection of symptoms that were difficult to explain and even harder to connect. She later became the project's subject matter expert, helping me evaluate not only the clinical sequence, but also what the experience felt like from the patient's side of the conversation.
Scenario Architecture
The learner follows the patient, not a list of symptoms.
The experience is organized as a patient journey. Each scene provides another opportunity to notice, ask, interpret, and decide.
Front Desk Intake
The learner first encounters the patient through an ordinary interaction where seemingly small details can begin to matter.
Initial Observation
Information begins accumulating through conversation, visual cues, and the patient's history.
Ask Better Questions
Learners decide which questions will clarify the picture without shutting down the conversation.
Connect the Pattern
Separate observations begin to form a stronger clinical picture.
Choose the Next Step
The learner acts with incomplete information while balancing appropriate escalation and clinical uncertainty.
See the Consequence
Feedback connects the decision to both the clinical reasoning and the patient's willingness to keep sharing.
Two signals stay visible.
Decisions affect both the quality of the clinical picture and the relationship that makes that information possible.
Key Design Decisions
Every interaction had to support the same idea.
Feedback
Dual meters instead of a score
Trust and Clinical Clarity make two different consequences visible without reducing the experience to right-versus-wrong points.
Structure
A patient journey
The scenario unfolds across roles and interactions so learners encounter clues as they naturally emerge.
Decisions
Plausible distractors
Choices reflect realistic thinking rather than obviously weak answers, making the reasoning more important than test-taking skill.
Consequences
Feedback explains impact
Learners see how a choice affects the conversation and the emerging clinical picture before moving forward.
Perspective
Multiple healthcare roles
The learner sees how observation and communication move across the patient experience rather than belonging to only one role.
Media
Story first, instruction second
Video and scenario moments establish the human context before learners are asked to make decisions.
From Design to Build
Show the thinking, not just the finished screen.
These spaces can hold the artifacts that make the case study feel tangible - scenario maps, storyboard frames, interface screens, and development details.
Feedback & Iteration
The scenario changed as the feedback became more specific.
Personas
Make the roles feel believable.
Updated the personas and interactions so the healthcare roles better reflected how the patient journey actually unfolds.
Learning Outcomes
Sharpen what learners should demonstrate.
Refined the measurable outcomes so the decisions aligned more clearly with recognition, communication, and action.
Story Arc
Keep the patient visible.
Strengthened continuity between scenes and gave greater weight to the patient's experience alongside the clinical logic.
What the Prototype Demonstrates
Practice the judgment, not just the information.
Recognition
Connect scattered clues
Learners practice moving from individual observations toward a larger pattern.
Communication
Ask questions that keep the patient talking
The scenario makes communication part of the clinical task rather than a separate soft skill.
Consequences
See what each decision changes
Visible feedback connects a learner's choice to both the quality of the information and the relationship with the patient.
Reflection
What I would test next.
The project reinforced how much scenario quality depends on the reasoning behind the choices, not simply the number of branches. The strongest moments are the ones where several responses sound plausible but lead to meaningfully different consequences.
Experience the Project
See the decisions in context.
Try the short demonstration or launch the complete branching experience to follow the patient journey from intake through clinical assessment.