Actually Doing It #13 — Walking Through It Together Works Better Than Testing It Alone

This post is part of my “Actually Doing It” series, where I document what I’ve experienced while setting up my own electronic vault. In the last post, I described what happened when I tried to hand off written instructions and have my wife access the vault on her own. That approach didn’t work the way I expected. [link to Post 12]

What did work turned out to be much simpler. Instead of asking her to figure it out, I set everything up myself and then sat down with her and walked through it together. That one change made the difference between something that failed and something that actually worked.

What I ended up doing was a simple vault orientation session, and it worked better than anything I had tried before.

Vault Orientation Session: Walking Through It Together Works Better Than Testing Alone

After the first attempt didn’t work, I changed the approach. Instead of asking her to follow instructions on her own, I set everything up myself and we walked through it together. That shift removed the pressure and made the process feel manageable instead of something she had to figure out on her own.

What I Did Differently

I stopped thinking about this as something she needed to “figure out” and started treating it as something I needed to introduce. That shift sounds small, but it changed how I approached the entire process.

I set up access to the vault on her computer myself. There was no installation, no configuration, and no need for her to connect different tools or interpret instructions. By the time we sat down, everything was already in place and ready to use.

From there, we simply walked through it together. There was no pressure for her to complete anything on her own, and no expectation that she needed to get it right the first time.

From Testing to Orientation

My original plan was to test whether she could access the vault using only written instructions. That sounds reasonable, but in practice it creates a very different experience than intended.

A test assumes that the other person should be able to complete the task independently. If they hesitate or get stuck, it immediately feels like something is wrong—even if the system itself is fine.

What worked better was treating it as an orientation session instead. This wasn’t about proving anything. It was a guided walkthrough designed to make the system familiar without pressure or expectations.

The Goal Is to Know Where to Start

Going into this, I realized I wasn’t trying to teach her everything about the vault. That would be unrealistic and unnecessary.

She doesn’t need to understand every folder, every file, or every decision I made while building it. What she needs is much simpler than that.

She needs to know where to start. Once that starting point is clear, everything else becomes manageable because she has a way to orient herself and move forward.

The Orientation Document

To support this, I created a simple orientation document that we could follow during the session and that she could refer back to later. The goal wasn’t to create something detailed or complex, but something clear enough to remove uncertainty.

The document walks through how to open the vault, where to start once it’s open, how the information is organized, and how to close and secure it when finished. It gives just enough structure so that she doesn’t have to rely on memory.

What We Actually Did

The session itself was straightforward. We opened the vault together using the steps in the document, just as she would if she needed to do it on her own later.

Once it was open, I pointed her to the README file, which serves as the starting point inside the vault. From there, we looked at a few practical examples—where to find contact information, where financial accounts are documented, and where legal documents are stored.

We didn’t try to cover everything. We spent just enough time for the structure to make sense and for her to see how things were organized. When we were done, we closed and locked the vault.

What Happened

The difference from the first attempt was immediate. She was comfortable using it and didn’t hesitate to move through the folders.

After we finished, she continued exploring on her own, opening files and looking through the information without any prompting from me.

At one point, she said she needed to set up a vault for her own information. That wasn’t something I expected to hear after what happened the first time, but it made sense given how different the experience was.

What Changed

Nothing about the vault itself changed. The structure, the files, and the information were all the same as before.

What changed was how it was introduced. There was no pressure to perform, no expectation that she had to interpret instructions on her own, and no need to connect unfamiliar pieces.

She saw how it worked in a straightforward way, and that familiarity made it usable. Seeing it once removed most of the uncertainty that had been there before.

What This Means

It’s easy to assume that if you document everything clearly, someone else will be able to follow it. That assumption makes sense, but in practice it’s not enough.

People don’t need to be tested. They need to be introduced. A short walkthrough does more to make a system usable than a set of instructions ever will.

Once someone has seen how the system works and knows where to start, they have what they need to use it later if the situation requires it.

Practical Recommendation

If you’ve built a vault or are in the process of organizing your information, don’t stop at writing instructions and assuming someone else will be able to follow them.

Set it up for your helper, then sit down together and walk through it once. Keep it simple and focus on helping them understand where to begin.

You’re not trying to make them an expert. You’re making sure they’ve seen it and know how to get started.

Closing

Getting your affairs in order isn’t just about organizing information. It’s about making sure someone else can step in and make sense of it when needed.

That doesn’t happen through instructions alone. It happens when someone has seen the system, understands the starting point, and knows that they can work through it if they need to.

Leave a Reply

Your email address will not be published. Required fields are marked *