You Were Never Supposed to Be the IT Person

It is 5 P.M., and you still have two things on your list that were supposed to be done by now.

You switch to email and there it is, another message about the Wi-Fi being spotty.

You hover over delete, and it hits you. This might be the fifth time someone has sent you this exact complaint.

You pushed it off before because you were knee deep in getting a new employee set up, and that ended up eating an entire day.

Now you are not one day behind.

You are two.

And tomorrow, something else is already waiting.

You close the laptop.

Somewhere in the back of your mind, the same thought surfaces that always does:

I know there is a better way to do this. This cannot be it. I just do not know how.

This is the quiet math nobody warns you about when you become the person in charge of IT at your company.

If you manage technology for an interior design studio, architecture firm, or another project based business, and you do not come from a technical background, this article is for you.

Not to teach you IT.

To show you the two things you actually need to get right so the rest stops landing on your desk.

The Job Nobody Fully Defined for You

You are the person everyone runs to when something breaks.

Not because you asked for it.

Not because you have a technical background.

Because someone had to be the point of contact, and that person turned out to be you.

You know just enough to be the one people come to.

But rarely enough to make the problem disappear in ten minutes.

And while you are trying to figure out whether you can handle it yourself, whether it is worth calling someone about, or whether you are even allowed to spend the money to fix it, you are also managing nine other things that have nothing to do with technology.

You have the responsibility. But not always the power.

That is the specific kind of exhausting nobody talks about.

The assumption, spoken or not, is that you can figure it out.

And if something gets too complex, well, that is what the IT people are for.

Just try not to call too often because it costs money, and we are already paying you.

Nobody said it out loud.

But you felt it.

She Did Not Know There Were Eleven More Steps

Earlier this year, I sat across from an office manager at a firm considering bringing us on.

She came prepared.

Real questions. Written down. Specific.

She wanted to know the best way to close out a Google Workspace account when a team member left. She leaned in, ready to take notes.

My answer stopped her.

“You do not have to worry about that. That is something we handle for you.”

Her eyes went wide.

“Oh, that is cool, but I am sure I can learn it. It probably costs extra if you do it.”

I told her the same thing I had said for the three questions before it.

All four were already part of our support plan.

No extra cost.

Nothing to learn.

I watched something shift in her.

She leaned back in her chair. The tension left her shoulders.

It was like watching someone set down a bag they had been carrying so long they forgot it was heavy.

💡 She had been trying to master step four of a fifteen step process without realizing there were eleven more steps she was never supposed to touch in the first place.

Talking to her reminded me of someone traveling the country trying to diagnose their own illness, researching medications, piecing together treatments, and finally sitting across from a doctor who says, “I see what’s happening. You do not have to figure this out alone.”

That is what the right IT setup feels like.

Not a vendor.

A diagnosis.

And then relief.

What to Actually Look for in an IT Partner

Start with your gut.

Before the proposal, before the pricing, before any feature comparison, ask yourself whether the person sitting across from you is someone who will genuinely care about your situation.

Not just close tickets.

Care.

If the answer is yes, you already have more than half of what matters.

From there, three things are non-negotiable.

1. The plan needs to include unlimited support, and it has to cover the basics.

Not just emergencies.

New employee setup. Someone leaving the team. A laptop being replaced. A new email account.

The moment you start deciding which problems are worth the cost to fix, you have already lost.

How do you put a dollar value on which problem gets solved this week?

You cannot.

And no business can afford to try.

Problems need to be solved promptly, not budgeted against.

2. Require an assessment before anything is signed.

A mature IT company does not hand you a number after one conversation.

They come back with a real picture of your situation. Your equipment. Your risks. Your gaps.

Think of it as the MRI before the prescription.

If you find a firm willing to do that work upfront, even at a cost, that is a good sign.

They are probably going to do it right.

And when they sit across from you with their findings, you will know pretty quickly whether they actually saw you, or whether they just saw a contract.

3. Choose a firm smaller than your own.

When I say do not go with a large IT company, I mean exactly that.

Do not work with one that has more employees than you do.

That may sound counterintuitive.

It is also less risky than you think.

Today, with AI, strong platforms, and specialized contractors, a lean and mature IT firm can carry more capability than a large one could ten years ago.

Size is no longer a reliable measure of strength.

What size does determine is where you rank.

When you are a ten or fifteen person business working with a large IT company, you are a small account.

You will feel that.

Responses slow down.

Requests get deprioritized.

The person you built a relationship with gets reassigned.

You stop being urgent to them, and it is very hard to fully trust a partner who does not treat your problems like they matter.

A smaller firm does not just serve you better.

They need to serve you better.

That changes the relationship.

Now, to be fair, none of this guarantees a perfect first month.

Any new IT relationship has a breaking in period, and the first few weeks usually surface problems you did not know were there.

That is not a sign something is wrong.

That is often a sign the right things are finally getting uncovered.

The alternative is another year of the same quiet math.

And that math does not improve on its own.

Stay on the Deck. You Do Not Have to Be in the Engine Room.

Here is the part that surprises people.

Even with the right IT partner in place, there is still one thing that belongs to you.

You may not be in the engine room of this ship.

You may not be at the bridge.

But you still need to be on the deck.

Feeling the breeze. Noticing where the wind is coming from. Making sure the ship is moving in the right direction.

Do not let your team contact your IT partner directly without some kind of visibility through you first.

Not to control everything.

To see the patterns.

If one person opens a support ticket every other day, that is information.

It might point to a training gap.

It might point to a recurring hardware issue nobody has named yet.

It might point to something worth a real conversation with your IT partner, or with that team member directly.

🎯 Your IT partner will not always surface that on their own.

That awareness is your job.

You are always going to be the other fifty percent of the formula.

Your IT partner handles the mechanics.

You handle the awareness.

Together, that is what actually works.

The system for this does not have to be complicated.

It can be as simple as an email to you, a quick approval, and a forward to IT.

Or it can be more structured, where requests route through you automatically and you simply keep visibility.

Either way, the goal is the same:

You stay informed without getting buried.

One more thing belongs on your side of the table: keep a little awareness of what similar businesses are doing with technology.

Not deep research.

Just enough to stay oriented.

If your IT partner works with businesses like yours, they can help here too. They already see what other firms are trying, what is actually helping, and what is just getting attention.

AI is a perfect example.

You do not need to master it. You just need enough context to ask better questions.

That is how a quarterly IT review becomes more than an update. It becomes a useful conversation about where your business is going.

When you sit down with your IT partner for a review, you will not be blank.

You will have noticed the trends.

You will know which team members are struggling, which tools keep coming up, and where the friction is building.

That context makes you a real part of the conversation, not just a point of contact.

You Have the Responsibility. Now You Have the Power.

I will be honest with you.

I have never been exactly where you are.

I am a business owner. I wear a lot of hats and switch between them constantly.

I genuinely understand about half of your pressure, because running a business means owning problems that are not always yours to solve.

But if you are not the owner, if you were handed this responsibility without always being handed the authority that should come with it, your job is harder than mine in a very specific way.

You have had the responsibility.

You have not always had the power.

What you have read here changes that.

You know what to look for in an IT partner.

You know what to require, not just what to prefer.

You know how to stay aware without getting pulled into the weeds.

And if you are not the financial decision maker, you now have what you need to walk into that conversation with more confidence and make the case for why this matters and what it will change.

It does not have to stay the way it is right now.

It really does not.

Thinking through what the right IT setup looks like for your team?

Let’s have a real conversation.

No pitch. No pressure. Just clarity.

Reach out with questions any time!