Designer - Articulate Storyboards for phase 1

Articulate Storyboards early on to enable firefighters, designers, software & hardware people review them before development and identify conflicts, issues and refinements (as well as have a shared sense of scope).

e.g. ’_Firefighter with a watch and smartphone receives ‘status red’ alert’_ - the storyboards can state things like:
* What the firefighter will see / hear / feel when alerted during field conditions (e.g. can take into account 8% of men are red-green color-blind).
* Where the visible things are and what they're doing - visibility of the sensor LED / Smart Watch / Phone under field conditions.
* What happens when 1 device (sensor) is in play - how the alert goes off, how a firefighter responds to or cancels it.
* What happens when 1 combinations of devices are in play (sensor / phone / watch). How a firefighter responds to or cancels these. Which device is mainly responsible for alerts? (would multiple devices alerting be OK / confusing?) etc...

Likewise ’Command Center leader receives ‘status red’ alert for a Firefighter’ - the storyboards can state things like:
* Does the response depend on knowing what the conditions are? e.g. will the next actions be different if
** toxic level of NO2 for a few seconds, but stopped
** experiencing a combination of {high temp + CO} right now
** has been exposed to too much NO2 cumulatively over the last 15 minutes
** etc...

Additional value from storyboards:
* Put them on github for onboarding new O/S contributors - help them get quickly up to speed and feel engaged
* Initial outline for Communications to spec out a promo / video / demo