You Were Never Bad at Technology. You Just Needed a Better Way In.
Part 1 of It Was Never You, a three-part series about how technology meant to make work easier can slowly become confusing, expensive, and difficult to manage.
In this series:
Part 1: You Were Never Bad at Technology. You Just Needed a Better Way In.
Part 2: Your Business Doesn’t Need the Best Technology. It Needs the Right Fit.
Part 3: The Technology Problem That Never Got a Deadline
“Excuse Me”
“Excuse me,” he said, and then he disappeared.
Not physically. He was still on the Zoom call, camera on, sitting right there. But for the next four minutes, my longtime client, a realtor, was somewhere else entirely. His thumbs flew across his iPhone screen as he composed an email one letter at a time while I waited.
I want to tell you what happened two weeks later because it changed how I think about technology adoption for interior design studios, architecture firms, and other project-based businesses.
But first, you need to sit in that moment with me.
He was not being rude. This was simply how he worked. Camera off to eat a sandwich in the middle of a meeting. Finishing an email on the walk to the bathroom. Busy in the specific way anyone inside a project-based business recognizes, where every minute gets stacked on top of another until the day becomes a pile of half-finished things.
When he resurfaced, I brought up a dictation tool, the kind that turns your voice into text instead of requiring your thumbs.
He shut the idea down quickly.
He had tried Siri once. It made a mess of what he was saying, and he never touched it again.
You already know someone exactly like this.
You might be someone exactly like this.
You Already Tried. That Is Not Nothing.
Here is what I want to clear up before we go any further, because it matters more than anything else in this article.
The problem was never that he was lazy, stubborn, or bad at technology.
He tried something once. It failed him. With no one there afterward to help him understand why, or show him a better way in, he quietly decided voice-to-text simply was not for him.
That is the real problem in this story.
Not fear of new tools. Not stubbornness. The absence of a safe way to try again after something does not work the first time.
Most people inside project-based businesses have their own version of this. A tool they tried once, on their own, that let them down. Instead of giving it another chance, they walked away with a story they still tell themselves:
“I’m just not that kind of person.”
But that is usually not true.
You are not bad at technology. You may have simply tried the wrong tool, in the wrong way, without anyone there to help you through it.
Three Doctors and One Truth
Quite a few years ago, I was playing soccer and made a sudden turn that sent pain through my knee. Every time I walked for more than thirty minutes, it swelled up.
Ice and elevation worked quickly. But when I finally saw a doctor, expecting him to recommend rest and physical therapy, he told me I needed meniscus surgery.
I did not want to believe him.
I was 25. Surgery felt extreme for something caused by one sudden turn on a soccer field.
So I saw a second doctor. Same answer.
Then I saw a third.
The third doctor told me something the other two had not bothered to explain.
“You’re 25. You have your whole life ahead of you. Surgery takes a couple of hours. It will take a few weeks to recover, and then you have the rest of your life without this problem. It’s worth it.”
Something shifted the moment he said that.
I was no longer thinking about the next few weeks. I was thinking about the next 50 years.
That is often the difference between resisting change and accepting it.
It was never about whether the surgery was necessary. Two other doctors had already told me that.
It was about someone finally showing me what was waiting on the other side.
The first two doctors gave me a diagnosis.
The third gave me a reason.
Why the Gap Widens Quietly
I once heard a business coach say something onstage that never left me: every business is now, in part, a technology business.
Interior design studios do more than select furniture. They sell judgment, trust, and confidence in how a project will come together. Architecture firms do more than produce drawings. They turn ideas into plans people can actually build from.
Behind both, technology plays a major role in how smoothly the work moves, how quickly the team responds, and how much time is left for the work clients actually value.
When someone quietly decides, “I found a way that works for me,” and stops there, that is not a neutral choice.
It is a decision to move in the opposite direction, even when it does not feel like one.
The gap that opens is rarely dramatic.
It shows up as tasks taking a little longer than they should in a world that expects everything quickly. It shows up in the polish of a client presentation. It shows up in how much time is left for you at the end of the day.
No single moment feels disastrous.
But the minutes keep accumulating.
Two Steps Out of Ten
So what do you actually do with this?
Start on a Monday. Keep a notepad nearby, physical or digital. It does not matter.
The moment you catch yourself starting a task you dread, write down what it is and put an X next to it.
Keep going for two weeks. Three, if you want to be thorough.
You will forget some days. That is fine.
At the end, look at where the Xs have piled up the highest.
That is your target.
If you work with an IT partner, bring it to them directly. Do not describe only the task. Explain which parts drag, how much time it consumes, and everything else you can put into words.
Then do the thing almost everyone gets wrong:
Do not try to eliminate the entire task at once.
If it is a ten-step process, aim to remove two steps.
Just two.
Once those two are gone and the improvement is holding, circle back and remove two more.
Most attempts at change fail because people try to fix the entire frustrating process in one move.
That usually makes the change feel bigger, riskier, and more disruptive than it needs to be. Start by removing two steps. Let the improvement prove itself, then come back for the next two.
A notepad and a few Xs will not fix the problem on their own. They simply help you see where the friction keeps showing up.
What matters is what you do once the pattern becomes clear.
That usually means having an honest conversation with someone who can help you improve the process without turning it into a massive project. It may take some time, and sometimes some investment, but the goal is not to change everything overnight.
It is to make the work noticeably easier, one improvement at a time.
“You’d Be Proud of Me”
My client on Zoom from earlier?
Two weeks after that call, he sent me an unprompted email.
“You’d be proud of me. I wrote this email with the app you showed me.”
My first reaction was pride in my own work. I had done my job. The tool worked.
But that was not what he was proud of.
He was proud that he had been willing to try again after Siri had already convinced him he could not.
That is the whole story here.
Not the dictation app. Not really the technology at all.
It was a man who had been burned once, choosing to trust the process a second time.
That is available to you too.
Not because the tool is magic, but because someone showed up the second time who understood the shoes you were walking in.
Find the task with the most Xs next to it.
Find someone willing to remove two steps with you, not ten.
The gap does not close all at once.
It closes the same way it opened: quietly, one decision at a time.
Continue the Series
Part 2: Your Business Doesn’t Need the Best Technology. It Needs the Right Fit.
A six-person team was handed enterprise-grade infrastructure it never needed. This article shows why fit, usefulness, and ease matter more than impressive equipment or generic best practices.
Part 3: The Technology Problem That Never Got a Deadline
Some problems survive for years because they never become emergencies. This article explores why “next quarter” keeps winning and what has to change before the person carrying the problem runs out of room to keep working around it.