Builder
«How would my team experience this?»
Won't decide against their own group, and the question they're really asking isn't whether the product is good but what happens to the people who'll have to use it. Pressuring them on timing freezes them: what they need is a path that doesn't break anything.
How you recognise them
- They say «we» where a Pilot would say «I».
- They ask how the team will react, not what the licence costs.
- They defer the decision to an internal discussion that wasn't on the agenda.
- The first risk they name is the one to the people, not the one to the budget.
How to open
«I'm not asking you to change how your team works. I'll show you what changes for one person in one week, and it's very little.»
«We'd start with two salespeople for a month. If it isn't useful, you switch it off and there's nothing left to dismantle.»
The proof they weigh most
The story of a rollout that went smoothly at a similar company, told from the point of view of the people who had to use it: who pushed back, what it took to convince them, how long it really needed. A phased introduction plan is worth more than one extra feature.
The vocabulary
- «nothing changes for the rest of the team»
- «we start small, with two people»
- «if it gets switched off, it switches off with no consequences»
- «we do it with you, we don't hand it over»
- «these are the objections your colleagues put to us»
- artificial deadlines and time-limited discounts
- «transformation», «disruption», «paradigm shift»
- asking them to decide in the meeting
- talking about their team as resistance to be overcome
- presenting the rollout as immediate and painless
The classic trap
Reading the delay as a soft no and pushing harder. When a Builder postpones, it is almost always an internal mandate they still have to build: what's needed isn't another call with them, but the material they can use to convince the others without exposing themselves. Give them the document they'll take into the meeting, and they'll hold the meeting.
If you're one too
Two Builders build an excellent relationship and a consensus that never reaches a signature: neither of them wants to be the one who forces the pace. If that's your pair, you're the one who has to propose the step — small and reversible — and you're the one who has to name the date.
And then there are the Regulators
The archetype sets the course, not the volume. Two people of the same archetype with opposite Security prepare differently: one wants guarantees and ways out, the other tolerates uncertainty when the opportunity is good. The same goes for Openness and Method. They're the three sliders that turn four categories into a prescription for one person.
How the TANDEM method worksThe other three archetypes
- Pilot
«Let's get to the point.»
- Promoter
«Let me tell you something.»
- Architect
«Could you send me the documentation?»
An archetype is a hypothesis about communication style, not a judgement on the person and not a diagnosis. It exists for someone who has to prepare a conversation, and it should be dropped the moment the conversation says it was wrong.