# Psycho-Logic *Logic should close this. It won't.* --- You're in a meeting room with a procurement team and your champion, the ops director who brought you in. The demo went well. The business case is clean: their current process burns forty hours a week across the team, your platform cuts it to four, and the ROI pays back in under six months. Your champion has said, twice now, that the numbers speak for themselves. The CFO nods politely, asks about implementation timelines, then says they'd like to revisit it in Q3. The head of IT asks whether the existing system could be extended instead, and someone mentions a failed migration three years ago. Your champion looks at the table. The conversation drifts into car-park language: "circle back," "more due diligence," "broader alignment." You leave with a follow-up scheduled for a date that will get pushed twice. --- Nothing in that room was about your numbers. The ROI was never in dispute, nobody challenged the forty hours or the six-month payback, and the objections that surfaced were procedural, not analytical. The real ones were never spoken aloud. Stay with the CFO for a moment. She is eighteen months into the role, hired after the previous CFO left mid-restructure. Her mandate from the board is stability: clean audits, predictable costs, no surprises. She has spent those eighteen months unwinding the commitments her predecessor made, and the board has rewarded her for it. She is, in her own mind and in the organisation's story about her, the person who steadied the ship. Now your proposal arrives. The ROI is real. She can see it. But approving a major platform change means becoming the CFO who gambles on technology projects, and that is a different person from the one who steadied the ship. The risk is not financial. She already ran the numbers and they work. The risk is that a failed implementation rewrites who she is in the organisation's memory. The careful steward becomes the person who approved the thing that blew up. She doesn't say any of this. She says "Q3." --- The IT head is running a similar calculation, though the inputs are different. He has spent two years stabilising the current stack after the migration that failed. His credibility rests on the system running without incident. A new platform means months of integration work, with his name on every outage during the transition. The person who mentioned the failed migration remembers the blame that followed, and raised it not as analysis but as a warning flare: remember what happened last time someone tried this. Your champion, who stuck their neck out to get you in the room, just watched the energy drain out of their own proposal. Nobody in that meeting was evaluating your platform. They were evaluating what happens to them if it goes wrong. --- The instinct is to come back with more evidence. A stronger deck, tighter numbers, a reference customer in the same sector, maybe a pilot proposal that lowers the perceived risk. All of this is logical, and all of it misses the point. What they lack is not information. It is safety, and a version of the change that lets them remain who they already believe they are. --- This is the mechanism worth understanding. Every person in that room carries a working identity, a story about who they are in the organisation and what kind of decisions someone like them makes. The CFO's identity is the steady hand. The IT head's identity is the person who keeps the lights on. Your champion's identity is the operator who gets things done. These identities are not vanity. They are shortcuts for navigating hundreds of decisions a week without rethinking each one from scratch. "Would someone like me do this?" is faster than a cost-benefit analysis, and in practice it runs first. When a proposal is consistent with someone's working identity, the analytical case is enough. When it conflicts, no amount of evidence will close the gap. You are showing them why the decision is right. They are asking whether the decision is them. [[Alchemy|Rory Sutherland]] calls the operating system underneath this psycho-logic: rules that look irrational from the outside but are internally consistent. The CFO's "let's revisit in Q3" is a perfectly coherent move inside her frame. Protect the identity that earned her the role. --- The useful question is: what would make the current state feel more expensive than the change? Your champion already told you the answer, though probably not in those words. The forty hours a week is not just a number on a slide. It is the ops team staying late on Wednesdays to reconcile data that should flow automatically. It is the monthly board pack arriving two days late because someone has to re-key figures from three systems into a spreadsheet. It is the IT head fielding tickets for workarounds that exist because the current platform cannot do what the team needs it to do. "This system saves ten hours a week" gets a nod. "Your team gets home before their kids are in bed instead of burning another evening on spreadsheets" gets a different reaction. Same fact, different frame. But reframing alone is not enough. You still need to resolve the identity problem. The CFO needs a version of this decision where saying yes is something a careful steward would do, not something that contradicts the story she has built. --- Behaviour comes first. Attitude follows. The conventional model of persuasion runs: change someone's mind, then they change their behaviour. The evidence runs the other way. Get someone to act, even in a small way, and they will supply the justification themselves. People need their actions to make sense retrospectively. A small commitment that works creates the conditions for a larger one, because now they are the kind of person who made that choice. Go back to the CFO. A full platform rollout asks her to become someone different overnight: from cautious steward to technology sponsor. She won't do it, and more evidence won't help. But a four-week pilot on the ops team's Wednesday reconciliation process asks her for something much smaller. It is scoped enough that a failure is contained. It solves a problem she already knows about. And it lets her frame the decision as due diligence rather than commitment: "Let's test it before we decide." Four weeks pass. The Wednesday reconciliations that took the ops team three hours now take twenty minutes. The board pack lands on time for the first time in six months. The IT head, who was sceptical, notices his ticket volume for workarounds has dropped. None of these people decided the platform was right. They experienced it being right, in a context small enough that their identities were never at risk. Now the CFO faces a different question. She is no longer being asked to approve an unproven platform. She is being asked to extend something that already works, something she approved, something that has her name on the pilot. Saying yes now is consistent with who she already is: the careful leader who tested before committing. The identity gate opens, and the analytical case, which was always strong, finally gets through. --- The sequence matters. Large commitment first, and identity blocks the door. Small action first, and identity reorganises around it. This is the tool. For any change that meets resistance despite a strong rational case, ask three questions. First: whose identity does this threaten? Map the room, not by job title but by working identity. The careful steward, the technical guardian, the consensus builder. Second: what is the smallest action that is consistent with their current identity but moves in your direction? Not a commitment to the change. A step that lets them experience the outcome without rewriting who they are. Third: what evidence will that step produce that makes the next step feel like continuity rather than a leap? The pilot is the most common form, but it is not the only one. Sometimes the small action is a site visit where the sceptic sees the system working elsewhere. Sometimes it is giving the blocker ownership of the evaluation criteria, so the decision becomes theirs to make rather than yours to sell. Sometimes it is as simple as asking the right question: "What would you need to see to feel comfortable?" instead of "Here's why you should feel comfortable." The first respects their identity as a careful decision-maker. The second tries to override it. --- [[Two halves of trust]] shapes the ground this plays out on. In a room where people feel safe to say what they actually think, the identity concerns surface early enough to address. The CFO might say, "I'm not against this, but I need to understand the implementation risk before I'll back it." That is an invitation, not a rejection. In a room without that safety, she says "Q3" and you never learn what was really in the way. The reasons people give for their decisions are rarely the ones that actually produced them. Your job is to change the conditions so that the decision, the real one, comes out differently. ---