Enterprise risk platform · Case study

Making enterprise risk workflows easier to understand and act on.

Riskabilitie helps organisations run their risk management as a workflow instead of a yearly spreadsheet ritual: registering risks, assessing them, routing approvals, and reporting upward, at every level of the organisation.

Product
Riskabilitie
Role
Product designer
Deliverable
End-to-end Figma prototype
Method
Stakeholder workshops
Domain
Enterprise risk management
Scope
Workflows · analytics · reporting
01

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 with four different tolerances for detail. Most tools pick one audience and punish the other three.

The brief said simple. The problem had other plans: multi-level workflows where a risk travels across teams, hierarchy levels, and approval chains without anyone losing the thread.

ONE RISK, FOUR ALTITUDESRegisterevery risk, ownedAssesslikelihood × impactApprovethe right sign-off chainReportboard-ready in one viewASSESSMENT MATRIXimpact →likelihood →AnalystRisk ownerCommittee
Fig. 01One risk, four altitudes: register, assess, approve, report. Each view built for its reader.
02

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.

03

Design system and interaction thinking

The whole product was delivered as a high-fidelity, interactive Figma prototype, with states, edge cases, and the boring-but-vital patterns (tables, filters, empty states, permission-aware actions) treated as first-class design work. Enterprise software earns trust in its tables, not its landing page.

04

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.

05

What changed in my thinking

Riskabilitie made me respect altitude as a design variable. The same object needs different interfaces at different heights in an organisation, and “one dashboard for everyone” is how enterprise tools end up loved by no one. I now ask “who reads this, standing where?” before I ask what goes on the screen.

Next case studyN1 Care