I’ve been watching a YouTube channel called The Space Maker Method for a while now. The host, April Scott Tandy, travels the world helping real people declutter and reorganize their homes through a series format. She’s also written a book on her methods, which I picked up recently on Kindle. I keep watching because something about her approach feels different from the usual “home makeover” shows. She isn’t just moving things around. She’s paying attention to the person in front of her first — who they are, how they got here, what they actually need — before she ever touches a single shelf.
This weekend I binged April’s series featuring Chelci, a young expat in South Korea who moves frequently and has quietly adapted to living out of boxes rather than ever fully settling in. I recognized something in her that I hadn’t quite identified in myself even though I knew it subconsciously: the habit of not committing to a space. Of treating home as temporary, even when it isn’t.
I want to change that.
Here’s my situation. My daughter and four grandsons live with me in my two-bedroom condo, and they’re staying for the foreseeable future until my daughter can get on her feet (she’s preparing to return to school for a post grad certificate). What was a manageable home for one person is now a real problem for six. The space needs to work harder, and more importantly, it needs to feel calm for all of us. So yesterday I started on a major decluttering project.
I got tapped out faster than I expected. The scope of it is bigger than I was prepared for, and it’s going to take some patience and commitment to see it through.
What This Has to Do With Technical Writing
One of the foundational principles of good user documentation is knowing your audience. Before you write a single word, you’re supposed to understand who the user is: their background, their context, what they’re trying to accomplish, what’s getting in their way. The best documentation doesn’t just transfer information. It meets a specific person where they are.
April does exactly this. For her it isn’t about the organizational systems or the storage solutions. It’s how much time she spends understanding people before offering any solutions at all. She asks questions. She listens. She identifies the underlying pattern — in Chelci’s case, a kind of resigned state of transience — before addressing the physical space. Her solutions are effective because they’re tailored.
It also made me think about what I’d say if someone asked me to document my own condo right now. What is the user (me) trying to do? Find things. Move through rooms without frustration. Feel at ease at home. What’s getting in the way? Years of accumulated objects that were never given a real place.
My “life documentation,” so to speak, is broken because the information architecture was never designed, it just grew, and now there’s a mountain of technical debt to pay for.
What Comes Next
In future posts, I plan to explore some of the specific connections I’m noticing between April’s methods and the principles we work with in technical communications — things like reducing cognitive load, organizing for individual users, and what it means to design a space (or a document) that someone can genuinely navigate. I’ll also be reporting back on the project itself, including the parts that are hard or not going well.