Krizo is inspired by how aviation deals with risk and crisis management. Aviation and pilots are arguably some of the best in the world to deal with sudden disruption. Crisis management plans here are extremely pragmatic, operational and easy to understand. Basically, it's a checklist based on a scenario that has been used in an exercise. This creates instant coordination and efficiency; the pilot knows exactly what to do, the cabin crew the same and of course the control tower as well.
We are teaching our clients to manage crises the same way a pilot does. We enable them to respond effectively to any disruption without proven templates in our Crisis Management Orchestration Platform.
What it does
In all the crises we have dealt with there’s always 2 main problems: Extremely difficult to maintain an overview of the situation. What’s the latest decision? What are the facts? What are the assumptions? What actions are we currently taking? No proper documentation. Difficult to maintain a comprehensive log of ‘who did what when’ while working under intense pressure and stress. Logging is always neglected.
Krizo is a Crisis Management Orchestration Platform that enables organisations to respond fast and efficiently to any type of disruption while maintaining a clear overview and documenting everything automatically. Krizo re-use existing tools users already are familiar with such as e-mails, Slack/Teams, SMS, Outlook etc. This reduces the learning curve significantly.
Krizo has 5 modules:
- Planning 1.1 Import highly operational and pragmatic crisis management response plans that have been used before
- Notification 2.2 Notify the right people instantly with mail, SMS and push notifications
- Assessing 3.3 Assess any event with powerful assessing tools
- Delegate & Manage 4.4 Have a complete overview of all delegated actions
- Evaluation 5.5. Evaluate effectively as all data is stored automatically
How we built it
We built it by constantly talking and reiterating on the feedback of crisis managers of big organizations. We identified their struggles, and after many versions we came up with this solution. The functional programming tech stack is chosen due to its expressiveness, and reliability.
Challenges we ran into
The #1 challenge we faced was introducing "another app" and a new way of working on a problem that happens rarely. Basically, would users be able to remember how to use the system effectively if they haven't used it in 6 months? Tough problem.
We solved this by pivoting into Crisis Management Orchestration. Instead of having users download and install an application we would rely on a digital system they already had in place. Krizo then orchestrates a response by integrating with existing systems users are familiar with. By training a few key employees as super users in Krizo you can be up and running within just 2 hours. By pivoting into an Orchestration platform instead of a stand-alone application we were also able to cut down implementation time significantly because fewer people needed access.
Within 2 hours any organisation can be up and running and using the platform.
Accomplishments that we're proud of
- Developed an end-to-end pandemic plan in close collaboration with our clients that we are now offering for free
- Signed Tryg (Denmark's largest insurance company)
- Signed Fujifilm
- Signed Vodafone
What we learned
- How important it is to have a solid product before scaling sales
- Haskell makes us highly efficient, but can be difficult attracting new talent. The ones we do end up hiring are highly motivated and eager to learn on the positive side.
- People act completely different in a real crisis compared to an exercise. Having a product that can be used for both was difficult, but nonetheless achieved!
What's next for Krizo - Orchestration for crisis management
Highly focused on helping our clients navigate through COVID-19 at the moment.
Try It out
angular.js, docker, elm, google-cloud, haskell, kubernetes, mongodb, sendgrid