1 of 8

A critical system goes down at 5pm Friday. What happens?

AYou already know — your monitoring alerted you before anyone noticed. Runbook is open.

BYou call your IT person and hope they pick up.

CYou restart the server. Problem solved. Probably.

DTotal chaos. But somehow it gets fixed by 7pm. Nobody knows how.

Your password strategy is best described as:

AUnique 24-character generated passwords for everything. 2FA on every account. Password manager mandated for the whole team.

BCompany name + year. Different number depending on which site. It works.

CWritten on a Post-it. Under the keyboard. Look, it's secure-ish.

DWhatever IT set up. You assume someone thought about it.

Software update notifications — what do you do with them?

AApplied automatically, tested in a staging environment first. Change log reviewed.

BYou let IT handle it. Or whoever handles it. Someone does, right?

C"Remind Me Tomorrow." 847 times. You'll get to it.

DYou turned the notifications off. They were annoying.

Your IT documentation is:

AA living wiki with runbooks, network diagrams, and version history. You know exactly what runs where.

B"It's all in my head." Has always worked fine.

CA folder called "STUFF" on the desktop. And a few email threads from 2021.

DYou've been meaning to write some. For three years. Next quarter for sure.

Someone downloads a "free" pirated version of expensive software. You:

AGet a real-time alert before they finish installing. The machine is quarantined in 60 seconds.

BFind out three months later when it causes a ransomware incident.

CActually... you suggested it. The licensed version is expensive.

DIT handles that stuff. You assume they caught it.

Your backup strategy is:

A3-2-1 rule. Tested quarterly. RTO and RPO are documented. You could restore from scratch in 4 hours.

BOneDrive is on — that counts, right?

CThere's a hard drive in a drawer. Pretty sure it still works.

DYou should really set that up.

A new SaaS tool comes out that could genuinely help the team. You:

AEvaluate it against your security policy, run a 2-week POC with a test account, get formal approval.

BSign up immediately with your work email. Tell nobody. Add it to the company card later.

CSubmit a request to IT. Estimated approval time: 4 months minimum.

DYou just make it work somehow. Can't explain how. It works.

How would your colleagues describe your relationship with technology?

A"They built a monitoring dashboard for the monitoring dashboard. It has alerts."

B"They just want it to work, man. Don't ask them to update anything."

C"Somehow their stuff never breaks. Nobody knows why. Don't question it."

D"There are 14 Slack integrations they added and nobody approved. Somehow they all work."

What does this mean?

Want to actually fix the gaps?

Whichever archetype you are, a good MSP fills the gaps — without jargon. Get connected with vetted local IT providers. Free, no obligation.

🧠 What IT Personality Are You?