Safety Reporting
One operational problem. One deliberately focused digital solution.
The problem
People attending sporting events need a simple way to report a safety issue when it happens.
In that situation, complexity is the enemy. The person reporting something may be standing at an event using a mobile phone. The process needs to be immediate and obvious.
The approach
Don’t build more than the problem requires.
Create a focused mobile-first reporting experience for the person raising the issue and a central management environment for the people responsible for receiving it.
- 01Event attendee
- 02URL
- 03Mobile report
- 04Submit
- 05Central management dashboard
What we built
A mobile-first web application through which event attendees can access a URL and submit a safety report.
Submitted reports feed into a central management dashboard where they can be viewed and managed.
The design principle
“The complexity belongs behind the experience, not in front of the person trying to report something.”
The public-facing interaction is intentionally simple.
Outcome
A specific operational requirement became a focused bespoke application rather than being forced into a larger generic software product.
Evolve principle
Bespoke doesn’t have to mean enormous.
Connected record
Where this leads
Related questions
- When does a focused bespoke application make sense?
- What does bespoke software cost now?
- Build vs buy: how should a business decide?
Knowledge links will activate as relevant Learn material is published.
Related projects
Relevant pathway