Recap Understand → Act → Create; present the 5 verticals
Choose a vertical and open its package
2
Understand
Hand out the problem cards
Choose one of the 3 problems
3
Understand
Walk through the data model of the vertical with the cheat sheet
Explore the objects, fields, and live alarms
4
Understand
Ask participants to fill in the Outcome Canvas before building
Fill in the Outcome Canvas
5
Act
Challenge the scope: "What is the smallest version that answers the key question?"
Decide the first version
6
Create
Circulate, unblock, and ask "Which decision does this help?"
Build the app
7
Create
Run a short show & tell; compare answers with the seeded scenario
Demo the app, the decision it supports, and the next increment
Outcome Canvas
Question
Answer
Who is the user?
Which decision do they need to make?
What slows that decision down today?
What does success look like?
How would we measure the value?
What is the smallest valuable first version?
What would the next increment be?
Problem Catalog
Every problem is phrased as a key question the app must answer. The backend guarantees that the data is available and that the scenario produces a clear answer – see the Data Availability Matrix.
Vertical
Problem
Key question
Suggested app pattern
Telco
Priority Dashboard
Which services require immediate attention?
Service Health Center
Customer Impact View
Which services affect the most customers?
Service Health Center
Capacity Risk Workspace
Which services may become problematic soon?
Risk & Trend Workspace
Satellite & Space
Mission Readiness Dashboard
Which missions require attention?
Service Health Center
Ground Segment Workspace
Which resources are at risk?
Risk & Trend Workspace
Customer Service Assurance View
Which services affect customers?
Service Health Center
Media & Broadcast
Event Operations Center
Which live events are at risk?
Service Health Center
Executive Service Overview
What is the overall operational situation?
Executive & Regional Overview
Incident Workspace
Which issue should operators investigate first?
Incident Workspace
Infrastructure
Operations Control Center
What requires action now?
Service Health Center
Critical Asset Dashboard
Which assets represent the highest risk?
Risk & Trend Workspace
Regional Operations View
How are locations performing?
Executive & Regional Overview
Government & Public Safety
Incident Coordination Workspace
What requires escalation?
Incident Workspace
Command Center Dashboard
Where should operators focus?
Service Health Center
Risk Prioritization View
Which locations require immediate attention?
Executive & Regional Overview
Expected App Patterns
All patterns use only backend data: the vertical data model (DOM) and real-time data from elements. Field names differ per vertical – see Vertical Terminology. Scores such as health or risk are defined by the participant – deciding how to prioritize is part of the exercise.
Pattern
Purpose
Typically shows
Service Health Center
Prioritize the top-level objects (network services, missions, events, …)
Status, active alarms, criticality, impact, upcoming activities
Incident Workspace
Investigate one object or issue
Details, assets and locations, alarms with age, alarm history, escalation, owners
Risk & Trend Workspace
Spot what will become a problem soon
Value vs. limit, 24 h trend, criticality, impact
Executive & Regional Overview
Summarize across objects or locations
Count per alarm state, impact of affected objects, alarms per location
Do's and Don'ts
Do
Don't
Insist on the Outcome Canvas before anyone builds
Let teams open App Builder before defining the outcome
Ask "Which decision does this help?" for every component
Do a feature tour or allow "build everything" apps
Celebrate a small working app that answers the key question
Reward visual polish over value
Encourage switching problems if a higher-value one emerges
Continue a path just because it was started
Use the seeded answer to check results at the end
Reveal the answer before participants explore
Close with "What is your next increment and why?"
End on the tool instead of the outcome
Tip
Good discussion points: incident vs. risk (Infrastructure), severity vs. customer impact (Telco), and alarms that cross the escalation threshold during the session (Government & Public Safety).
Success Criteria
Every participant has a working app that answers the key question of their problem
Participants can name the decision the app supports and the value it creates
Participants can name their next increment
Transition
"Your app shows the data. Next, you'll build an agent that knows how your organization handles that data – its policies, procedures, and escalation rules."