Fundamentals
Business IT Fundamentals
Business IT is the mix of accounts, devices, files, networks, and applications a company uses to do its work. This guide names those pieces so you can describe your own workplace without guessing.
What “business IT” means here
In a shop or an office, technology is usually four layers stacked together. People sign in with accounts. They use devices such as laptops and phones. Those devices reach files and mail over a network. Applications sit on top: bookkeeping, quoting, payroll, a website, a warehouse scanner.
If you can name those four layers for your company, you already have a working picture. You do not need a diagram with every cable. You do need to stop treating “the computer is slow” as a single problem. Slow can be the device, the Wi-Fi, the application, or the person waiting on a password reset.
Example: a ten-person office
Imagine a contractor’s office in a small Alberta town. Five people work at desks. Five more are on sites with phones and a shared laptop in a truck. Mail lives in Microsoft 365. Quotes live in a folder someone once called “Server” even though it is now OneDrive. Invoices go through a bookkeeping app in the browser. The Wi-Fi password is on a sticky note in the kitchen.
That picture is ordinary. It is also enough to study. The accounts are Microsoft 365 plus the bookkeeping login. The devices are the desks, the phones, and the truck laptop. The files are OneDrive plus whatever still sits on a USB stick. The applications are mail, quoting, and bookkeeping. Once those are written down, questions become specific: who can see the quotes, what happens if the truck laptop is stolen, and whether the bookkeeping app has its own backup.
Map the tools you already use
Do this on paper before you change anything.
Open a note and make four headings: Accounts, Devices, Files, Applications. Fill them from memory, then walk the office and correct the list. Include personal phones if people read work mail on them. Include the printer. Include the person who left last year if their mailbox is still open.
- List every way people sign in: email, bookkeeping, payroll, the Wi-Fi portal, the alarm panel if it has a login.
- List devices the company paid for, and devices people bring from home if they hold work files.
- Write where a new quote, a signed contract, and a paid invoice actually live today.
- Name the applications that would stop work if they were unreachable for a day.
- Mark who currently “knows the password” for each item. If the answer is one person, write that down as a risk, not as a personality trait.
Keep the list. Workplace guides use it when you set up a new computer. Backup education uses it when you decide what must be copied.
Accounts are not the same as devices
A laptop can be replaced. An account that still belongs to someone who left is a hole in the company. Shared logins hide that hole: if five people know the bookkeeping password, you cannot remove one person without changing it for everyone, and you usually forget.
A useful habit is one person, one account, wherever the software allows it. Shared mailboxes can exist as a mailbox that several people are granted access to, not as one password written on the wall. When someone leaves, the first job is to remove sign-in, then to transfer files, then to collect the device.
Files need an owner and a place
Work files scatter: email attachments, a desktop folder called “Final_v3”, a USB stick in a drawer, a personal OneDrive, a paper copy on a desk. The company cannot back up what it cannot find. It also cannot say who should see a contract.
Pick one primary place for each kind of file and write it down. “Quotes live in this SharePoint library. Invoices live in the bookkeeping app. Photos from site live in this folder, not in iMessage.” People will still email attachments. The point is that the official copy has an address. Microsoft 365 learning covers OneDrive and SharePoint in more detail.
Common mistakes
Treating a personal Gmail or iCloud account as the company archive. Buying a new application every time a process feels slow, without assigning an owner. Leaving admin rights on every laptop “so we are not blocked”. Assuming the person who set up the Wi-Fi five years ago still works there.
Another frequent error is copying a large company’s process. A ten-person firm does not need a 40-page change board. It does need a one-page list of systems and a rule that a leaver loses access the same day.
How to describe a problem so it can be solved
“It doesn’t work” wastes an afternoon. A usable description has four parts: who is affected, what they were trying to do, what they saw instead, and whether it ever worked. Add the time, the device, and whether others still can do the same task.
Example: “At 09:40, Maya on the front desk laptop could not send a PDF from Outlook. The error said the attachment was too large. Ahmed sent a smaller file two minutes later from his own PC and it went through.” That is enough for someone to test size limits rather than reinstall Windows.
What this guide does not cover
It does not tell you which vendor to buy from. It does not set a price. It does not describe industrial machinery, medical devices, or 911 systems. Those need specialist material.
If your workplace already has written rules, those rules win. This page is a way to think, not a policy for a company you do not work at.
Starter checklist
Use this after you have read the sections above.
- Four lists exist: accounts, devices, files, applications.
- Each application has a named owner, even if that owner is “the office manager”.
- You know which email system you use, and whether files live in that system or somewhere else.
- You can name at least one person who still has access they should not have, or you have checked and found none.
- You can describe yesterday’s worst technology snag in four sentences: who, what, what they saw, whether others were affected.
- You know this site will not configure those systems for you; the next reading is a topic page, not a support ticket.
Questions people ask
I only have five people. Do we still need this map?
Yes. Small offices lose more time to “ask Jordan” than to missing enterprise tools. The map is short on purpose.
Should I start by buying new software?
No. Name what you already run. New software without an owner becomes a sixth place files can hide.
Turn the map into daily habits
The workplace guides cover passwords, files, and a computer you can rebuild if it fails.