Rollout and everyday use
A system does not get good because everything is switched on. The real question in the first weeks is what you take out and what you keep.
You sit at your desk on a Monday morning and look at the usage logs. You just introduced a new system to tame the daily chaos. Until now, you ran the company in an Excel file, a WhatsApp group, a shared drive and three different subscriptions. You wanted to clean this up. You prepared for weeks, assuming the junior team members would need time to adjust to the rules. Instead, the juniors are working smoothly. The problem comes from the person sitting in the corner office.
Your most senior, most professional colleague is the one finding every possible flaw in the new tool. They complain about the interface. They say it slows them down. They miss deadlines they never missed before. They sigh during meetings when the software is mentioned. You might think they are just tired or bad with new technology. That is rarely the truth.
Your best employee is not struggling with the buttons. They understand exactly how the tool works. What they are fighting against is not the interface, but the fact that the tool takes away their informal power. Over the years, they built a position where they are the ultimate safety net for the company. When every task, deadline and file is visible to everyone, being the only person who knows how to run a project loses its value. They are not sabotaging the software. They are sabotaging the transparency.
A business does not just run on written rules. It runs on the habits and unwritten agreements that form over the years. When a company grows, one or two people naturally become the central hubs of information. They know which client pays late, which supplier needs a phone call instead of an email, and how to handle a delayed shipment. Over time, this knowledge makes them irreplaceable.
When you bring in a new tool to organise the workflow, you expect resistance from those who struggle with technology. However, the loudest complaints usually come from the experts. They do not want to be a simple user in a system where their daily tasks are visible to a junior colleague. They want to remain the gatekeeper of information.
This is where the choice of tool matters immensely. Specialised software is deep. Most of that depth is something the majority of users do not understand and do not use. Therefore, the real value is not depth, but breadth and clarity. IntrApp is not another tool at the end of the line. It is the Business Operating System the company runs on. It is not a CRM and not an ERP. IntrApp covers what a small or mid-sized company does day to day, without the complexity. If you are looking for the deepest tool in a single area, you will find better ones, and that is fine. This is not a shortcoming, but a choice.
When the tool is simple and clear, the senior colleague cannot hide behind the excuse that the software is too complicated for the rest of the team. The excuses run out, and the real issue surfaces.
The first concrete sign of sabotage is the parallel system. Two weeks after you announce that all client data must go into the central database, you notice your top performer is still typing into a spreadsheet. When you ask them about it, they give a highly rational answer. They tell you they can find the phone numbers faster in their own file. They say the new layout takes too many clicks, so they keep a separate list to stay productive.
This sounds like a workflow problem, but it is a control problem. The secret Excel file is a barrier. As long as the data remains on their screen, anyone who needs a client history has to ask them. They control the flow of information. If they go on holiday, nobody can reach the files they were managing. Work stops until they return, which constantly proves how crucial they are to the operation.
You might think the solution is to find a system tailored exactly to their specific industry knowledge, hoping they will adopt it. An industry specialisation is never a limitation on the software side. The professional knowledge belongs to you, the development belongs to us, and the two work together side by side. What the veteran employee is doing is keeping that professional knowledge hostage. The parallel spreadsheet ensures that if a problem arises, they are the only one who can solve it.
During the transition period, you hold a meeting to see how everyone is adapting. Your veteran colleague speaks up with a prepared list. They describe a highly specific scenario. They bring up a supplier from three years ago who required a split return form, accompanied by a physical stamp and a fax confirmation. They point out that the new software has no dedicated button for this exact sequence.
They use this rare exception to argue that the entire tool is unfit for your daily work. By focusing on the rare cases that do not fit the standard process, they try to invalidate the daily routine that does. They want to prove that the company operations are too complex to be handled by a standard method. If the operations are hopelessly complex, then the company absolutely needs their personal oversight every single day.
We see this dynamic often, and it is built into how we develop the product. What happens when something is actually missing? It is not a dead end, because you can request a feature. If roughly three quarters of our customers would also use it, we build it for free and it becomes part of the shared product. IntrApp decides what meets this threshold, because we see the entire customer base. Anything that falls below that threshold, something that is entirely unique to your process, is built on a custom branch, while you still receive the shared updates. The rare exception is just a task to be solved, not a reason to abandon the transition entirely.
The real conflict appears when it is time to delegate. You hire a new person to take some weight off the senior employee's shoulders. You ask the veteran to hand over a specific monthly reporting task. A week later, you see the veteran doing the report themselves. When you ask why, they say it was simply too complicated to explain to the new starter, so they decided to do it alone to save time.
In a company without a central core, tasks exist only in people's heads. The steps to complete a project are a personal asset. When you move those steps into a shared space, the process becomes visible. The tool has a manual and a built-in tour, so if you do not understand something, the app explains it. The junior employee can look at the screen, read the steps, and complete the report without asking for permission or guidance.
Transparency turns personal magic into a repeatable company process. The senior colleague feels this as a loss. They used to be the person who saved the day at the end of the month. Now, the day does not need saving, because the steps are clear and anyone can follow them. The veteran is no longer the bottleneck. They are no longer the single point of failure. This is not about the new system lacking features or being hard to use. It is about the veteran losing their monopoly on how work gets done.
You cannot win this battle by arguing about button placements or edge cases. If you try to convince them that the new layout is slightly better, they will always find another rare exception to prove you wrong. You have to shift the conversation from technical details to company policy. The first step is removing the technical excuses entirely.
With IntrApp, the automated installation takes roughly 30 minutes, and you are live. You can start alone, and we do not invoice for implementation or training. If you still want assistance, our expert team is happy to help, and that is your choice. You start the free trial, and if it does not fit, you cancel it like a streaming subscription. The software costs roughly the price of a lunch per month for a three-person company. It uses per-head pricing, so you do not have to buy a package twice the size for one new colleague. The storage is included, and there is a volume discount. There is no massive financial or technical risk you need to defend.
Tomorrow morning, do not ask your senior colleague how they feel about the new tool. Sit down with them and set a strict boundary. Tell them that any client request that is not in the system will not be processed. Tell them that the separate Excel sheet is no longer an acceptable format for weekly reports. Acknowledge their vast expertise, but make it clear that their value to the company is in their professional insight, not in hoarding basic information. You pay them for their judgment and experience, not for being the only person who knows how to find a document on a shared drive.
If this topic is useful to you, these are good ones to read next.
Rollout and everyday use
A system does not get good because everything is switched on. The real question in the first weeks is what you take out and what you keep.
Rollout and everyday use
The answers exist, they are just not written down, so the same two people keep getting interrupted. What an internal wiki changes, and what it does not.
Rollout and everyday use
Four different things travel on the same channel, which is why decisions get lost. What changes when the conversation sits next to the work it is about.
The demo shows an invented company with all its data filled in, and it needs no sign-up. A few features are switched off in it, and it resets every night.