How to Get Your Team Using the AI You Bought Them
Buying every employee a chatbot seat is not a strategy. The systems people use are the ones that arrive inside something they already open.
· 4 min read
Patrick Laughlin, Founder, Chief AI Officer
Naval Academy, class of 2011. Decorated naval aviator, 10+ years. President, 2023 Inc. 5000 company.

A sales rep at a licensed apparel company opens her calendar on a Tuesday morning. Inside tomorrow's meeting invite there is a brief. Who the account is. What they have bought this year and across the relationship. What is open, what shipped late, who else is on the invite and what their role is.
Nobody asked her to log into anything. There was no training session. There is no new icon. The brief is simply in the invite, in the place she was going to look anyway, because she was going to that meeting either way.
That is the entire trick. There is nothing technical about it.
The blank box problem
Tell your employees to use AI and they will not use AI. Paying for a seat for everyone has failed at company after company I have walked into, and the seat was never the problem. The blank box was.
A blank box asks a person to invent a workflow. They already have one. Theirs works, they can do it while thinking about something else, and it does not require them to explain to a colleague why they are typing at a chat window at eleven in the morning.
So the tool sits there. Renewal comes around. Somebody in finance asks what the licenses did, and the honest answer is that four enthusiasts got very good and everyone else opened it twice in March.
Nine applications, and the one with its own login
At that apparel company there are nine applications on a shared data platform: seven running, and two in their hands for testing. Among them are the meeting-prep briefs, a pitch and proposal studio, a prospecting engine, an executive dashboard and a sales dashboard.
The ones that are used share a property. The output lands somewhere the person already goes. The calendar invite. The CRM record. The proposal they were building anyway.
Now the honest part, because I would rather you hear it from me. One of them is the prospecting engine, and it has its own login and its own screen. A few weeks after we turned it on, the usage logs told us it had not yet become part of anyone's day. There was no technical problem, and the lesson was ours to learn. Version two went back out for testing.
Same firm. Same team building it. Same quality of work. The difference was that this one asked people to go somewhere new, and the others did not.
Where does the output land
That is the question I would put to any vendor, ahead of anything about models.
Where does the output appear, and is that a place my people already open every day? If the answer is a new tab, you are buying a change management project and calling it software.
What does a person have to do differently on their first day with this? The best possible answer is nothing. The second best is one extra click inside a screen they already use.
If adoption is twenty percent after ninety days, what do you do? Watch whether they have ever been asked this before. If the plan is more training, the plan is that it is your fault.
When a screen is fine
Not everything can hide, and I am not arguing that dashboards are bad. A dashboard is a good answer when looking at it is somebody's actual job. The sales director who reviews the pipeline every Monday will open a dashboard, because reviewing the pipeline is the work.
A dashboard is a bad answer when it is the adoption plan for forty people whose job is something else. Screens are for the work people choose to do. Agents belong inside the work they already do without choosing.
The strategy part
Strategy here means a decision about which work stops being done by hand, in what order, and who owns each piece afterwards. It does not need a document about artificial intelligence. Tools are what you buy once that is settled, and by then the list is short and boring and specific.
The compliment I am fishing for at the end of a build is that somebody forgot the software was there.


