Organizational silos: how to break them down in a small team
Short answer Silos form when each person or crew has its own number, its own records and its own way of passing work on. In a small business, fix the handoffs, not the people: one shared customer record, a written checklist and a named owner for each handoff, one company number everyone sees, and a short weekly look at what got dropped.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callHow do you break down silos in a small business?
Fix the places where work changes hands. A silo is rarely a people problem in a small company; it's a job that moves from one person to the next with nothing written down and nobody owning the move. Six fixes, cheapest first:
| Fix | What it means | Cost |
|---|---|---|
| Map the handoffs | Follow one customer from first call to final payment; list every time the job changes hands | One hour |
| Name an owner per handoff | One person is responsible until the next person confirms they have it | Free |
| Write a handoff checklist | The 4–6 facts the next person always needs | An afternoon |
| One customer record | Notes, quotes, photos and promises live in one place everyone can open | A shared sheet, or a CRM |
| One shared number | A company goal that no single person or crew can hit alone | Free |
| Weekly 15-minute review | What got dropped this week, where, and which handoff to fix | 15 minutes a week |
New software, team-building days and longer meetings come last, if at all (more below).
What is an organizational silo?
A silo is a part of the business that works well on its own but doesn't share what it knows with the rest. In a large company that's a department. In a small one it's the office and the field crew, the front desk and the technicians, the estimator and the installer, or the owner, whose head holds what nobody else wrote down.
The customer feels it first. They explain their problem twice, the crew arrives without the part the office promised, or the invoice doesn't match the quote.
Why do silos form, even in a 10-person company?
Four causes, all ordinary:
- The number of conversations explodes. Every pair of people is a line that can break. Three people have 3 pairs; 5 have 10; 10 have 45; 20 have 190. Somewhere along that curve, "we'll just talk" stops working, and nobody notices the day it happens.
- Each person is judged by a different number. The front desk counts booked appointments, the crew counts jobs finished, sales counts signed quotes. Nobody owns callbacks, refunds or the bad review, because those land between two people.
- Each role keeps its own records. The office has the calendar, the tech has photos on a personal phone, the estimator has notes in a notebook. Information that lives in one tool stays with one person.
- Handoffs run on memory. "I told him" isn't a system. When the busy season hits, memory is the first thing to fail.
Your business tends to mirror how its people talk. In 1968 the computer scientist Melvin Conway put it this way:
"organizations which design systems (in the broad sense used here) are constrained to produce designs which are copies of the communication structures of these organizations." (Melvin E. Conway: How Do Committees Invent?)
For a service business, the "system" is the customer's experience. If the office and the crew barely talk, the customer feels that gap.
Signs your team has silos
Two or more of these, and it's costing you jobs:
- Customers repeat their story to each new person they speak with.
- Two people do the same task, like both calling a customer back, because neither knew the other had.
- Return trips happen because a part, a measurement or a detail didn't get passed on.
- People say "nobody told me" more than once a week.
- Only one person can answer "where is this job at?", and it's usually you.
- Quotes go out but nobody follows up, because sales thinks the office does it, and the office thinks sales does.
- Each person's numbers look fine while reviews, margins or repeat business slide.
The six fixes, step by step
1. Map the handoffs
Pick one recent job and trace it on paper: call or form, reply, quote, booking, visit, invoice, follow-up, review request. Circle every point where it moved from one person (or one tool) to another. Then mark the ones where something went wrong in the last month; start there.
2. Give each handoff an owner and a checklist
The sender owns the job until the receiver confirms they have what they need. The checklist lists only what the next person always needs: for an office-to-crew handoff, that might be address and access, the problem in the customer's words, what was promised (price, time window, parts), photos, and who to call with questions.
Hospitals have tested this hard, because a dropped handoff there can hurt a patient. In a 2014 study across nine hospitals, a standard spoken and written handoff format, plus training, was followed by 23% fewer medical errors and 30% fewer preventable adverse events, and spoken handoffs took no longer: 2.4 minutes per patient before, 2.5 after (Starmer et al., New England Journal of Medicine, 2014). Your handoffs are simpler; a checklist is enough.
3. Keep one customer record
Everything about a customer goes in one place: contact details, what they asked for, quotes, photos, promises, notes from each visit. A shared spreadsheet works while one or two people handle customers. A CRM (customer relationship management software: one shared file per customer) earns its cost once more people do. Pick the tool after the checklist exists, so you know which fields matter.
4. Set one shared number
Choose a goal nobody can hit alone, such as "jobs done right on the first visit" or "new customers who leave a review". Put it where everyone sees it each week. Personal numbers can stay; the shared one shows where they collide. For lead-to-sale handoffs, sales and marketing alignment covers the shared lead list.
5. Review the drops weekly, without blame
Fifteen minutes, same time each week: what got dropped, at which handoff, and one change to the checklist. This only works if people admit drops. Google's study of 180 of its own teams ranked psychological safety first among five factors of team effectiveness, describing members who feel
"confident that no one on the team will embarrass or punish anyone else for admitting a mistake, asking a question, or offering a new idea." (Google re:Work: Understand team effectiveness)
Ask "where did the process let you down?", not "who forgot?". Go first: name a drop of your own.
6. Cross-train
Have the person who books jobs ride along on a few calls, and have each tech spend an hour at the front desk. People pass on better information once they've seen what the next person does with it.
What doesn't break down silos
- More meetings. A meeting shares news once; a checklist shares it every time.
- A new chat app. It adds one more place to look. Fix the record first.
- Sitting together. Google found that seating teammates in the same office was not significantly connected with team effectiveness in its study (Google re:Work: Understand team effectiveness). Being nearby doesn't mean the information gets passed on.
- A team-building day. Good for morale; it doesn't change who owns a handoff.
Where automation helps
Automate a handoff only once it's written down and working by hand. Then software can do the passing: a web form that creates the customer record, a missed call that triggers a text back, a finished job that triggers the review request. Automating a messy handoff just drops work faster. See AI marketing automation setup for the order to do it in.
How do you know it's working?
Track three things for two months, before and after:
- Return trips or callbacks caused by missing information.
- Time from a customer's first contact to a reply (speed to lead explains why this one matters).
- "Nobody told me" moments raised at the weekly review. It should fall each month.
Example
Illustrative, with round numbers.
An HVAC company with 12 people (US$)
About 4 return trips a month happen because the office booked the job without the unit's model number. Each costs roughly $150 in time and fuel. The office-to-crew checklist adds "model number or photo of the label". Return trips for missing parts fall to 1 a month, saving about $450 a month.
A dental office with 8 staff (C$)
Patients complain the treatment plan they discussed isn't what the front desk bills. The fix: the dentist's plan goes into the patient record before the patient leaves the chair, and the front desk reads it back at checkout.
A landscaping company run by its owner (US$)
The owner is the silo: only he knows each client's gate code and dog. He moves every client note into one shared sheet. His crews stop calling him 20 times a day.
FAQ
Are silos ever a good thing?
Focused specialists are fine. The problem is the edges, where work moves between people without the right information.
Is it true people persist 64% longer when they work as a team?
It traces to a 2014 Stanford study where everyone worked alone; those merely told they were a team persisted 48% longer (Association for Psychological Science).
What's the first thing to fix?
The handoff that drops the most work. Map one job end to end and count where it went wrong.
Do I need a CRM to break down silos?
No. A shared spreadsheet and a written checklist come first. Add a CRM once more than two people handle customers.
Different for you?
- The silo is between whoever runs ads and whoever answers the phone: sales and marketing alignment.
- Leads go missing between marketing and sales: sales and marketing handoff.
- Calls go unanswered when the office is busy: missed calls.
- You want follow-up and lead handoffs run for you: Conversion.