The standard playbook of product design is built on a quiet assumption: the user wants to be here. They are motivated, a little curious, and have the energy to explore. We design to activate them, to reach the aha moment quickly, to reduce friction so a willing person can move faster.

Bereavement flows violate every part of that assumption. The person did not choose this. They are grieving. They may be exhausted, suspicious, or numb. They are not looking to be delighted. They need to be treated with care and then helped to do one necessary thing. At BlockWill, where the moment of inheritance is the entire point of the product, we had to develop a different set of principles for these flows. Here are the seven that guide us.

1. Name the emotional state before you design a screen

The first artifact in a bereavement flow is not a wireframe. It is an honest written description of what the person is feeling when they arrive. Shock. Confusion about what this platform even is. Possibly guilt or urgency. We write that at the top of the brief and return to it constantly, because it is easy to drift back into designing for the cheerful default user out of habit.

Every screen then has to pass one test: would this feel okay to receive on the worst day of your life? That question alone removes a surprising number of patterns that are normal everywhere else.

2. Strip out celebration

Progress bars that congratulate. Confetti on completion. Cheerful "you're almost there" copy. Streaks. These are the reflexes of engagement-driven design, and they are exactly wrong here. Celebrating that someone finished a step in settling a death is jarring at best and cruel at worst.

The tone of a bereavement flow is calm and plain. It acknowledges weight without dwelling on it. It never performs enthusiasm. Removing celebration is not a small cosmetic choice. It changes how the whole experience feels in the hand.

3. Lead with the person, not the platform

The trust a grieving user needs in that moment is not trust in your brand. It is recognition that this came from someone real. So the first thing they should see is the name of the person who set this up and a plain human sentence about what is happening, not your logo and a feature tour.

We deliberately keep BlockWill in the background of these flows. We are the messenger. The message belongs to the person they lost.

4. One clear path, one action at a time

A motivated user benefits from options and exploration. A grieving first-time user needs the opposite: a single forward path with no side doors. We remove every secondary link, every optional detour, every choice that does not have to be made right now.

Each step does one thing and says what comes next. If something can wait, it is not on the screen. Cognitive load is the enemy, and the way you beat it is by making fewer things compete for a tired mind's attention.

5. Security without interrogation

This is the hardest principle to hold, because the security cannot be relaxed. Releasing an estate to the wrong person is catastrophic, so identity verification is non-negotiable. But verification done thoughtlessly feels like an interrogation at the worst possible time.

The resolution is framing, not weakening. The same cryptographic check runs underneath, but the person experiences a short step explained in one reassuring sentence about why it exists, to make sure this only opens for you, rather than a wall of requirements. Security and compassion are not a trade-off. They are a design problem you solve together.

6. Let people stop

Grief does not keep a schedule. A flow that demands completion in one sitting, with countdowns and pressure, fights the reality of the person using it. So bereavement flows must save state generously and let people leave and return without penalty or lost progress.

There are no timers urging speed. The product waits. That patience is itself a form of respect.

7. Measure the right thing

If you optimize a bereavement flow for speed or completion rate, you will make it colder, because those metrics reward removing the very pauses and gentleness that make it humane. We deliberately do not chase activation here.

What we watch instead is whether people can complete the essential task without reaching out to support in distress, and the qualitative sense of how the experience felt. The goal is not a fast funnel. It is that someone, later, would say the hardest day was made a little less hard rather than a little harder.

Why this discipline improves everything

Designing for the most vulnerable user forces a rigor that quietly improves the rest of the product. Plain language. Single clear paths. Security explained rather than imposed. A refusal to manipulate attention. These are good principles everywhere. Bereavement flows just make them non-optional, which is why we treat them as the truest expression of what BlockWill is meant to be: infrastructure that shows up well on the day it actually matters.

Frequently Asked Questions

What is a bereavement flow?

A bereavement flow is any part of a product that a grieving person uses, such as a beneficiary accessing an inheritance or a family member settling a digital estate. It requires different design principles than standard onboarding because the user is distressed and did not choose to be there.

Why shouldn't bereavement flows use normal engagement patterns?

Patterns like confetti, progress celebrations, streaks, and upbeat copy assume an excited user. For someone grieving, these feel jarring or cruel. Bereavement flows should be calm, plain, and free of celebration.

How do you keep security strong while being compassionate?

By changing the framing, not the security. The cryptographic verification stays fully intact, but it is presented as a short, clearly explained step focused on protecting the person, rather than as a list of demands. Compassion is in the language and pacing, not in weaker controls.

What metric should bereavement flows optimize for?

Not speed or completion rate, which reward coldness. Better signals are whether people complete the essential task without contacting support in distress, and qualitative feedback on how the experience felt.

Why lead with the person who set up the account?

Because the grieving user's trust comes from recognizing that this originated with someone they knew, not from your brand. Leading with that person's name and a human explanation grounds the experience in something real.

Do these principles only apply to estate or inheritance products?

No. Any product touching illness, loss, crisis, or other vulnerable moments benefits from the same principles. Estate planning makes them unavoidable, but the discipline improves software broadly.

Further reading: