Estate portal with dynamic step flow

Settling an estate is, for most bereaved relatives, not only administratively heavy but emotionally loaded. At a moment when they mostly want to mourn, they're facing forms, agencies, and deadlines that have nothing to do with that grief — and everything to do with legal correctness.

In this project it was crystal clear that the experience of those relatives had to come first. The steps in the process had to be logical and understandable, in language that didn't get unnecessarily formal, with a visual calm that doesn't push away but invites in. At the same time it had to be dynamic: not every situation follows the same path, so the step flow had to adapt to who the user is and what they had answered earlier.

As the front-end developer I worked on this with an AngularJS 1.4 application on Vert.x and Java 8 underneath. The step flow itself was a layered concept: a main route through the settlement, branches based on answers, and smaller sub-processes that surfaced at the right moments — for example for specific arrangements or assets.

A lot of attention went into tone and visual calm. The design team and developers worked very closely together: screens were designed jointly, not thrown over a wall. Decisions about color, animation, and hierarchy were tested every time against the same question: does this help a person who feels heavy right now, or not?

Under the hood the system had to be legally precise. What the user sees as 'a question' is often, internally, a combination of source data, rules, validations, and consequences. By modeling that layer cleanly and separately we could keep evolving the step flow on substance without having to touch the UI every time.

A challenging project, but deeply rewarding to see how my contribution made the process slightly less heavy for those left behind. For me this remains a lasting reminder that technology only becomes truly valuable in the spots where it removes quiet, daily friction.