This post is part of my “Actually Doing It” series, where I document what I’ve experienced while setting up my own electronic vault. Up to this point, most of what I’ve written has focused on the process—what worked, what didn’t, and what I changed along the way.
I thought I was ready to hand things off. I had built the vault, organized the information, and I had written what I believed were clear vault access instructions explaining how to access it.. I gave those instructions to my wife, who is also my primary helper. From my perspective, the next step was simple.
What Actually Happened
That’s not what happened. The reaction wasn’t technical. It wasn’t about whether the steps were correct or whether the system worked. It was emotional. When I handed her the instructions, it hit immediately.
She wasn’t just reading steps—she was confronting what those steps meant. The possibility that she might someday need to use this, under circumstances neither of us wants to think about, became very real. She was crying. She was shaking. She couldn’t continue.
Why It Hit So Hard
After things settled down, we talked about it. I tried to explain that having access to the vault could also help in much less serious situations. If I was traveling and didn’t have access to something, she could step in and get it. If I needed information and couldn’t get to it, she would have it.
There are practical, everyday reasons for this to exist. But by that point, it didn’t matter. The emotional response had already taken over.
What I Assumed
From my perspective, this should have been straightforward. She uses a computer every day and is comfortable with tools like Dropbox. The instructions were clear—at least to me. I assumed she would be able to follow them without much trouble.
That assumption turned out to be wrong.
What I Missed
Looking back, the problem wasn’t just the instructions. It was what the instructions represented. She understood what the helper role meant and was prepared to step in if needed. But being asked to access the vault made that role feel immediate and real.
I was thinking about a system. She was reacting to what that system meant.
Where the Instructions Fell Short
At the same time, the instructions assumed more than I realized. They assumed an understanding of what a “vault” is, familiarity with Cryptomator, and comfort navigating setup steps that connected Dropbox, software, and file systems.
I had written the instructions so they made sense to me, but not necessarily to someone seeing this for the first time. This is something I ran into earlier when I wrote about the importance of writing for the backup helper.
Everything made sense if you already understood the system. If you didn’t, it was a lot to take in.
The Real Problem
Those two things—emotional weight and technical assumptions—came together in a way I didn’t anticipate. The result was simple: it was too much, all at once.
Not because the system was wrong, and not because the instructions were incorrect, but because the starting point was off.
What I Changed
I realized I was approaching this the wrong way. I wasn’t just asking her to follow instructions. I was asking her to understand something new, set it up, and be ready to use it—all at the same time.
Instead of asking her to figure it out, I changed the approach. I set up everything on her computer myself and removed the need for her to install or configure anything.
Now I was ready to introduce her to the vault in a way that didn’t require her to figure anything out first.
What This Means
This isn’t unique to our situation. Most people avoid this kind of preparation for a reason. It’s not just about documents, passwords, or accounts. It’s about what those things represent.
When the first interaction makes that reality feel immediate, it’s natural to hesitate—even if you’re willing and capable.
Closing
You can have the right tools, the right structure, and even clear instructions. But if you don’t account for how this feels to the other person, the system won’t work.
This is all part of getting your affairs in order, and it’s often harder than it looks from the outside.
I’ll walk through what I did differently—and how it worked—Actually Doing It #13 — Walking Through It Together Works Better Than Testing It Alone.