A branching learning experience that makes everyday data decisions visible, before development begins.
✳
BEHIND EVERY GREAT EXPERIENCE
A thoughtful storyboard.
01
02
03
The right choice starts with a pause. ↗
FORMATStoryboarding
SCOPE5-screen storyboard
PROJECT TYPESelf-initiated concept
01 / THE CHALLENGE
Learning with a clear purpose.
Everyday requests can make oversharing feel convenient. Learners need to check purpose, recipient, and minimum necessary information before sharing.
Who it’s for
Employees handling personal or confidential workplace information.
By the end, learners should be able to…
Identify unnecessary personal information in a request.
Choose a response that limits disclosure.
Apply a pause-and-check routine to a new scenario.
02 / THE APPROACH
Make the thinking visible.
A short branching scenario makes the decision and its consequences explicit. Each screen specifies copy, narration, visuals, feedback, and navigation for development.
My design process & rationale
Map the decision tree, align each branch to an objective, draft screen content and feedback, then review the storyboard for clarity and accessibility before authoring.
Tools & development plan
Implemented: HTML storyboard preview
Planned: authoring tool to be selected
03 / EXPLORE THE SAMPLE
The blueprint, screen by screen.
Five screens, one intentional decision tree. All content below is a fictional learning example.
A colleague asks you to send a customer list to a new external partner. What should you check first?
Visual directions
Split layout: a clearly marked fictional chat message and a customer-list document. No real personal data.
Narration
A routine request can involve sensitive information. Take a moment before you share.
Interaction
Select “Review the request” to continue.
Branching & navigation
Continue → Screen 02.
02 / Make a decision
On-screen text
The file contains names, email addresses, and internal notes. The partner only needs a count of customers by region.
Visual directions
Document preview with field labels; highlight unnecessary fields using text labels as well as color.
Narration
Which response meets the purpose while limiting the information shared?
Interaction
Choose A: send the full list, or B: verify authorization and share only the required summary.
Branching & navigation
A → Screen 03. B → Screen 04.
03 / Rethink the risk
On-screen text
The full list includes information the partner does not need. Once sent, you may lose control over how it is used.
Visual directions
Document with excess fields labeled “Not needed for this purpose.”
Narration
Convenience does not remove the need to check who should receive the information.
Interaction
Select “Try again” to reconsider the decision.
Branching & navigation
Try again → Screen 02. No forced time limit.
04 / A more thoughtful choice
On-screen text
Verify the request and authorization through an approved channel. Use the approved process to share only the required summary.
Visual directions
A minimal regional count table with a checklist: purpose, recipient, minimum information.
Narration
Checking the purpose and recipient helps you decide what information is necessary.
Interaction
Select “Apply the checklist” to continue.
Branching & navigation
Continue → Screen 05.
05 / Take it with you
On-screen text
Before sharing: pause, check the purpose, verify the recipient, and minimize the information. If uncertain, follow your organization’s guidance.
Visual directions
Four-step recap with clear icons and text. Completion message appears in the reading order.
Narration
Use this routine the next time a request asks you to share information.
Interaction
Choose “Review decision” or “Finish.”
Branching & navigation
Review → Screen 02. Finish → case-study page. Completion has no scored outcome.
04 / REFLECTION & NEXT STEPS
Always room to learn.
Next: review the fictional scenario against a real organization’s policy and develop an accessible prototype. This is a learning concept, not legal guidance.