The philosophy
Built to Fit
The principle
The square-peg problem is simple enough for a child's toy. Each piece has a place where it fits, and pushing harder does not turn the wrong opening into the right one. Businesses forget that lesson every time people are told to reshape their work around a piece of software.
Every new tool asks something of the people expected to use it. There is another login, another screen to check, and another place where information can disappear. The subscription price arrives on an invoice. The cost of fitting that tool into a working business is harder to see.
I call that the integration tax. You pay it in interruptions, repeated data entry, retraining, missed handoffs, and time spent reconciling systems that were supposed to make the work easier.
Technology earns its place when it reduces that burden. I place it where your work already happens.
01
Adoption is part of the system
A tool has no practical value until someone uses it consistently. That sounds obvious, yet software decisions are still made from demonstrations, feature lists, and technical specifications. The daily experience of the person doing the work receives attention after the purchase, when resistance has already started.
People reject the extra labor wrapped around technology. If using a tool means leaving the conversation, opening another application, finding a record, copying information across, and returning to explain what happened, the tool has broken the flow of the task. Repeated across a team and a workweek, those steps become the job around the job.
Training cannot solve a poor fit. It can teach someone where the buttons are, but it cannot justify unnecessary steps. People create shortcuts, keep private notes, delay updates, or abandon the system. The official process survives in a manual while the real process carries on somewhere else. A system that looks complete from the administrator's seat can feel unusable to everyone responsible for keeping it current.
I start by locating the moment when help is needed. That moment can be inside an open customer record, in the communication channel where a request arrives, or behind an action that already makes sense to the person using it.
A custom script inside your CRM can handle a repetitive task without sending anyone to a separate dashboard. An AI assistant inside your communication stack can organize or route information where the conversation is already taking place. The interface follows the work, so the person does not have to become the connection between two systems. A proper fit accounts for what that person knows at that moment, the decision in front of them, and what the next person needs to receive.
I also pay attention to failure. If an automation stops, the people affected should know what happened and have a clear way to continue. A quiet tool is useful. A silent failure is dangerous. Building something into an existing workflow means making its status and limits understandable without turning everyone into a technician.
02
Put the capability where it belongs
03
Fit does not mean preserving every habit
There is an important boundary here. I will not automate a broken step simply because it is familiar. Some friction comes from the tool, and some comes from a process that has outlived its purpose. Good integration requires knowing the difference.
If a step protects quality, judgment, or accountability, the system should respect it. If a step exists because two applications have never shared information, I want to remove it. If the current process asks the same person to enter the same fact twice, the technology should carry that fact forward. The aim is to preserve the parts of the work that matter and stop making people compensate for the software around them.
This is also why I resist the promise of a zero learning curve. Any change worth making requires some orientation. The better standard is a tool people can understand because it behaves in ways that make sense inside their work. Training becomes focused and finite instead of a permanent effort to overcome a foreign system.
I judge fit by what disappears from the day: unnecessary screens, copying and pasting, missed handoffs, and records that fall out of date because updating them lives outside the task. People spend less attention managing the machinery around their work.
The best integrated systems feel almost ordinary. That is a compliment. They appear at the right moment, do the job they were given, and leave the person free to continue. You need the technology you already paid for, and the intelligence you are adding, to work as one useful part of the business you already run.
