Enterprise risk platform · Case study
Making enterprise risk workflows easier to understand and act on.
Riskabilitie supports risk registration, assessment, approvals, and reporting across an organisation. I designed an interactive prototype with different views for analysts, approvers, and leadership.
- Product
- Riskabilitie
- Role
- Product designer
- Deliverable
- End-to-end Figma prototype
- Method
- Stakeholder workshops
- Domain
- Enterprise risk management
- Scope
- Workflows · analytics · reporting
The difficult part
Enterprise risk software has a structural problem: the people who enter risks, the people who assess them, the people who approve mitigation, and the people who read the board report are four different audiences. An analyst needs the assessment detail; a board report needs a summary of exposure and action.
I needed to make multi-level workflows clear as a risk moved between teams and approval levels. Each view needed to show the current owner and the next action.
A risk workflow in four altitudes: register, assess, approve, report. Beside it, a four by four assessment matrix of likelihood against impact, and the approval chain underneath: analyst, risk owner, committee. Choose a cell in the matrix to see how far up the chain that severity has to travel before it is signed off. Low severity stops with the analyst; high severity reaches the committee.
The product story
The design work started in stakeholder workshops, mapping how risk actually moves through the organisation before drawing a single screen. Those sessions produced the backbone of the design: a risk object that stays the same while the interface around it changes per level, from the analyst’s detailed assessment view to the committee’s one-glance matrix.
Around that backbone: assessment flows with likelihood and impact scoring, approval routing that makes the current owner unmistakable, analytics for spotting concentrations, and reporting views designed to be read by people who will never log into the product.
Prototype and patterns
The whole product was delivered as a high-fidelity, interactive Figma prototype. It included tables, filters, empty states, and permission-aware actions so stakeholders could review the workflow beyond its main screens.
Result
The prototype gave the client a shared, clickable answer to “how should this work?” across workshops with stakeholders who had never agreed on that answer in text form. This case study shows only approved public material, and stays deliberately light on client specifics.
What changed in my thinking
The same risk record needed different levels of detail for an analyst and a committee member. I now establish who is reading a view, what they can act on, and what they need to decide before choosing the content for it.