Skip to content
Blogs Best-practices

Introducing a new system: start with one department, build for all

Introducing a new system: start with one department, build for all

Start with one department, build for all: that is the short answer if you are torn between switching over in one go or building up gradually. Yet we see business owners who sensibly start small still ending up with two systems side by side three years later. Starting small is only half the advice.

Say your business has 25 people, split across sales, delivery and administration. You choose a new system and the temptation is strong to switch everything over on a single monday. One date, one training session, done. It feels efficient. In practice, on that monday everyone has to learn something new at the same time, everything has to work on the same day, and you have no proof yet that the system actually does in your business what the salesperson promised.

And something always goes wrong. An integration that does not sync, a field that is set up incorrectly, a report that stays empty. With a big bang, the whole business immediately grinds to a halt. Quotes do not go out, planning gets stuck and the phone keeps ringing. That is exactly when resistance is greatest, because everyone is affected and nobody has yet experienced what it delivers.

So many business owners choose the safe route: one department first. That is sensible too. But it often goes wrong there in a different way, and you only notice after a year or two. One department works beautifully in the new system, the rest still works as it always has, and the handover between them runs through email, Excel and loose notes.

Start small, think big

Start with one department. That keeps it manageable, you learn what works and what does not, and the rest of the business is not affected. You can adjust course without the whole organisation watching. And once it runs, you immediately have your first internal success story. The colleagues in that department naturally become your ambassadors, and that works better than any presentation from management. A colleague who says "I spend an hour less on quotes every week" convinces the rest faster than you do.

With most clients we therefore start with sales: customer data, quotes and follow-up. It is a clearly defined process, the gain is quickly visible and usually only a few people work in it. Only when that is running well does delivery join. That order is logical, because in most businesses information flows in that direction too: first sell, then deliver.

But here lies the pitfall. If you only look at that one department, you build an island. Sales then works in a nice system, but the handover to delivery still goes via email. And it is precisely in that handover that most of the gain usually lies. So decide in advance how the whole business should run later, and set up that first department with that in mind.

Three questions before the first department goes live

What does "building for all" mean in concrete terms? It means the structure is already ready for the next step, even though nobody uses it yet. We work with a simple framework of three questions, which you answer before the first department goes live. If you cannot answer them, you are not ready to start. That sounds strict, but it costs you a few afternoons of thinking at most, and it saves you months of rebuilding and double entry later.

What will the next department need?

Walk through an ordinary job with someone from delivery. What information do they look up as soon as a customer signs? Address, agreements, chosen options, deadline, contact person on site. If sales records those fields from day one, even though nobody looks at them yet, nothing needs to be rebuilt later. Skip this step and in a year you will discover that half of what delivery needs is not recorded anywhere, and you start entering data all over again.

The second question is about the moment of handover. When does a job move from sales to delivery, and what happens then? Today that is often an email with a PDF. In the new system you want a signed quote to automatically become a job. Map that out in advance on a single A4 sheet, even if delivery only joins in six months. Then you simply connect that next department later instead of starting again.

Without a date, it stays at one department

The third question is the one most often forgotten: when does the next department move over? Plan that step straight away, preferably with a fixed date in the diary. Without a date, what we see time and again happens. The first department runs well, everyone is satisfied, there is always something more urgent, and you spend years on that one department. Meanwhile you still have two systems side by side, exactly what you wanted to solve with a new system.

Put the three questions next to the two familiar approaches and the difference becomes clear. Everything in one go: you do have a plan for the whole business, but no room to learn, and everything stops when something goes wrong. Department by department without a plan: you do learn, but you build silos that later do not fit together. Start with one department, build for all: you learn on a small scale and every step already fits into the whole. That is not a compromise between the two, but a different order of thinking.

So the choice is not between everything at once or taking it slowly. What matters is that you start small and think big: one department live, the structure ready for the rest and the next step in the diary with a date. Start only small and you end up with an island. Think only big and you bring the business to a standstill. If you are unsure which department is the best place to start in your business and what the next one will need, we at Lead Innovation will put that on paper with you before anything is set up.

Want to know more about monday.com?

The Lead Innovation team at work