Change Management at a Small Bank: Getting Partners to Use the Tool

What partners actually resist

Partners do not resist AI in the abstract. They resist specific changes to control, workflow, and accountability. Each concern needs a different answer. Research on workplace technology adoption points in the same direction: perceived usefulness, task fit, ease of use, management support, and peer norms all affect whether people accept and continue using a system. [2]

The first concern is losing control of what goes to the client. A managing director who has signed every CIM for twenty years is not going to sign one a machine wrote. The answer is that nothing about who signs changes. The associate edits a draft instead of writing from a template, and the partner reads the result the same way they always have. Say this in the first conversation, before the partner raises it.

The second concern is being asked to learn software. Partners at boutiques got where they are by being good with owners and buyers, not with tools. The answer is that the partner does not have to operate anything for the rollout to work. The associate operates. The partner reads. If a partner wants to click through a valuation trace, they can, but it is not required.

The third concern is the suspicion that the tool makes the associate’s work look better than it is. This one is legitimate and should be taken seriously. Use a review rule: every artifact has a named reader, the partner sees what was generated and what was edited, and the partner can send anything back. The tool does not shorten the review. It shortens the wait before the review.

The Monday morning screen

The practical lever is the Monday deal meeting. At most boutiques, this meeting is where the associate reports status on every mandate, the partners ask questions, and the associate goes back to find answers. It takes an hour and generates a to-do list. A live, useful screen can make the system fit the meeting rather than ask the meeting to fit the system.

Change one thing. Before the meeting, the sponsor opens the pipeline on the screen in the room. Every mandate, every phase, every open NDA, and every outstanding owner request is visible. The associate still reports, but the partners can see what the associate is describing, and some questions may answer themselves. That is a practical test of usefulness, not a promise of a particular adoption result.

Use three weeks as an illustrative observation window, not a forecast. In week one, partners may look at the screen and ask the associate anyway. In week two, one partner may ask a question, look at the screen, and withdraw it. In week three, a partner may open the pipeline on their own laptop before the meeting. That behavior is a meaningful adoption signal, but the timing will vary by firm, mandate, and task fit.

The sponsor should not turn the meeting into a product demonstration. Put the screen up, let the associate report, and watch which questions the screen answers and which it does not. Then fix the missing information before the next meeting.

The skeptical partner’s first mandate

Every boutique has a partner who says in the partner meeting that a new tool is a waste of money. That partner’s first mandate on the platform is an important test of the rollout, and it should be handled differently.

Do not assign the enthusiastic associate by default. Assign the associate the skeptical partner trusts most, with a short handoff from the first associate. The skeptical partner needs to see their own associate produce their own CIM, not watch someone else’s workflow. Participation by the people who will use the system, along with communication tailored to their work, is a recurring theme in research on technology implementation. [2]

Let the partner send things back. They may. A CIM draft may come back marked generic in three places and wrong in one, and the associate can fix all four and trace the wrong one to an inconsistency in the owner’s intake. That trace is the useful moment. The partner sees that the input was inconsistent, that the tool surfaced it, and that the associate caught it. The next draft may get less markup, but do not present that as a guaranteed result.

Ask the skeptical partner one question at the first NDA: was the CIM you signed better, worse, or the same as usual? “The same” is not proof of a measured benefit, but it can tell the sponsor whether the new workflow has cleared the partner’s minimum bar.

Where the sponsor spends political capital

The sponsor’s job in change management is narrow. It is not to convince everyone with a speech. It is to make the new workflow visible, keep the review boundary clear, and stop two forms of drift. Prosci describes active and visible sponsorship, coalition-building, and direct communication as core sponsor activities, and identifies sponsorship as a major contributor to change efforts. [1] That supports a visible operating role for the sponsor, not a claim that any particular rollout will succeed.

The first drift is a partner telling an associate to go back to the old template. This can happen under deadline pressure, especially from a partner who did not agree to the pilot. When it happens, the sponsor talks to the partner, not the associate. The message is simple: the associate will produce the draft from the platform, edit it, and the partner reviews it the same as always. If the partner wants to rewrite the whole thing after reading the draft, that is their call, but the draft gets produced first.

The second drift is a parallel workflow. One mandate on the platform and one in Word and Excel is worse than either when the associate must maintain both and the pipeline becomes incomplete. The Monday screen is then unreliable, and partners have a reason to stop trusting it. The sponsor’s rule is that every live mandate goes into the pipeline, including the ones partners want to keep the old way. The partner can ignore the pipeline for their mandate. The associate cannot.

Both decisions cost the sponsor something with the partnership. Spend that political capital deliberately. The sponsor should also ask what the system is not showing, because forcing a workflow without fixing missing data creates resistance rather than adoption.

Measuring partner adoption without a survey

Do not ask partners whether they like the tool. Count behavior and pair it with a baseline. The measures below are management heuristics, not validated benchmarks or promised outcomes.

First, count how many partners open the pipeline themselves in a given week. The sponsor can see this, or the owning associate can keep a simple log if the system does not expose the measure. A small bank might start with one partner and set a quarterly review point for broader use. Do not turn that example into a universal target.

Second, count how many status questions the associate gets by email or in the hallway per week. The owning associate can tally them for the first month and compare the count with a later month. A fall would suggest that the screen is carrying more of the reporting load. The original “more than half” target is not evidence-backed, so use the direction and the baseline instead.

Third, compare how many mandates are in the pipeline with how many are live at the firm. The figures should converge as the rollout matures, but “equal by day 90” is an illustrative checkpoint, not a verified adoption standard. If they do not converge, the sponsor has a prompt to find the parallel workflow and understand why it exists.

Put those counts beside hours and days-to-teaser in the day-90 report to the partnership. They describe partners’ and associates’ behavior more reliably than a general satisfaction question, while still requiring judgment about mandate mix, staffing, and the quality of the underlying data.

This week

Put the pipeline on the screen in the next Monday deal meeting. Do not explain every feature. Let the associate report with it behind them. Write down the questions the screen answers, the questions it misses, and which partner opens it afterward. That is enough evidence to choose the next change in the rollout.

How Acquivo Pro fits

Acquivo Pro gives the Monday screen its content: every client’s mandate in one pipeline, with NDA, IOI, and LOI status, open owner requests from the branded portal, and the phase each deal is in, on one login. A partner who wants to go deeper can open the valuation and follow any figure to its source, because the engine is deterministic and traceable, but no partner has to operate anything. Flat per-seat pricing means the skeptical partner’s mandate goes into the same pipeline at no additional per-deal cost. To see it on a live mandate, request a demo through the Contact page.