Introducing change with a conservative person: innovating with evidence

The team has spent three months working on a new way of working. The presentation is ready, the schedule is set, and from Monday everyone is expected to switch over. Then your conservative colleague asks a single question: “What problem are we solving here that can’t be solved in the current process?”

The energy drops in the room. For the project group, the question sounds like resistance to work that’s already been done. For your colleague, it’s a necessary check before trading a trusted method for something whose benefits aren’t yet visible.

That difference makes change unnecessarily personal. One person sees opportunities that only arise when you move. The other sees value that quietly disappears as soon as you move.

A good change doesn’t ask a conservative person to trust innovation as an idea. It makes clear what needs to improve, protects what already works, and gathers evidence in a trial that can be reversed.

Conservative doesn’t mean against change

In a personal user manual, a conservative person is on the side of practical work, routine, and a predictable environment. This colleague values familiar methods not just because they’re familiar. They often contain experience that’s never been fully written down: which exceptions matter, where mistakes arise, and which step gives customers confidence.

That can bring a lot to a change. A conservative person asks questions about usefulness, evidence, and execution. They are more likely to spot which daily action is missing from an abstract plan and can prevent a team from replacing a reliable process with an attractive story.

The flip side comes with the same preference. What’s familiar can feel safer than it really is. A new approach sometimes only gets support once all uncertainty is gone, when you actually need to try to gather evidence. An exception from the past can then outweigh a recurring problem in the present.

That’s why “you need to be more open to change” isn’t a useful starting point. It makes a work question personal and says nothing about what needs to improve. The better question is: what evidence do we need to fairly assess something new without carelessly discarding what already works?

ConservativeCuriousProgressive

Replace the big leap with a limited trial

A conservative person doesn’t necessarily need more convincing. They need a change that is controllable.

Start with the problem in the current way of working. Name where it becomes visible, how often it occurs, and who is affected. “We want to work in a more modern way” doesn’t give a reason to give up something proven. “In one out of five intakes, information is missing, causing customers to wait a day” does.

Then make explicit what will be preserved. Think of a check that prevents errors, a contact moment that customers value, or an overview colleagues rely on. Not every part has to change at once to solve a single problem.

Finally, test the smallest version that delivers usable evidence. Choose one team, one type of request, or two weeks. Agree in advance on which outcome counts, when you’ll decide, and how you’ll revert if the trial works worse. This way, participation isn’t an irreversible commitment.

1. 1
   PreserveName what already works

   Record which quality, control, or habit must remain intact during the trial.

2. 2
   TrialTest one concrete improvement

   Limit the target group, duration, and method so the change can really be assessed.

3. 3
   DecideCompare based on agreed evidence

   Choose the measurement points, decision moment, and fallback route in advance if the result is disappointing.

Make the same idea concrete enough to assess

Many change messages start with words like future-proof, smarter, and more efficient. They sound positive but leave open what will actually be different on Monday and how someone will notice it’s better. For a conservative person, such a message feels like a request to trade certainty for a promise.

The content doesn’t need to be more cautious. Make it testable. Name who is trying what, what stays the same, how long the trial lasts, and which outcome will lead to a broader decision.

For this, we offer transformations in the personal guides. Open the guide of the person you want to write a message for. If your preferences differ, the guide suggests a suitable transformation. You paste your message into the tool and get back a version that lands better with the recipient. The content and intent remain the same. Only tone, word choice, structure, and framing change.

For a conservative colleague, for example, “Make an idea concrete for Noor” fits. The trial and intended decision remain, but the wording makes the scope, measurement points, and limits of the change more visible.

Original

From Monday, we’ll optimize the intake with a new form. Team North will use it for three weeks. After that, we’ll compare lead time and rework with the current process. Existing files will remain where they are for now. If both results improve, we’ll roll out the new method more broadly.

Transformed

From Monday, team North will test one new intake form for three weeks. Existing files will stay in the current process. After three weeks, we’ll compare two points with the current method: lead time and rework. Only if both improve will we roll out the form more broadly.

Three perspectives on the same change

What you need to watch out for when working with a conservative colleague also depends on your own preference. Two conservative people can protect valuable stability and wait too long together. A curious person can translate between old and new but keep postponing a decision. A progressive person can bring movement but explain too little about why this particular change is needed.

If you are conservativeMake inaction testable too

Protect what works, but agree on which recurring problem makes a trial necessary.

If you are curiousTranslate and dare to decide

Connect the new approach to practice and prevent weighing options from becoming an endless in-between phase.

If you are progressiveEarn space with a trial

Make the problem and evidence concrete, and ask which existing quality must be preserved.

If you are also conservative

Two conservative people can thoroughly test a change. You know the existing work, recognize practical objections, and are less likely to implement something just because it sounds new or attractive. That protects customers and colleagues from avoidable unrest.

The blind spot is that you see the same risks and take the same trusted solution for granted. A temporary problem quickly gets more attention than the costs of years of not changing. No one in the conversation represents what can’t yet be proven because it’s never been tried.

So don’t just make the change testable, but also inaction. Agree on a threshold: if the same problem occurs five times this month, we start a limited trial. Also invite one curious or progressive colleague to formulate an alternative. Not to convince you, but to make sure there’s really something to compare.

If you are curious

As a curious colleague, you usually look for a balance between the familiar and the new. You can translate an abstract idea into a practical application and understand why a conservative person wants to see evidence. That often makes you the natural bridge in a change.

Be careful not to become just a translator. If you process every objection into yet another variant, another analysis, or another extra pilot, no one has to take the risk of deciding. It may look like there’s movement, but the organization stays stuck in an in-between phase.

Make clear in advance when research turns into choosing. Help the team make a fair comparison and then state your advice. “Both routes have advantages” can be true. It’s only useful if you also say which route comes out best on the agreed measurement points.

If you are progressive

As a progressive colleague, you probably quickly see possibilities outside the existing way of working. You bring ideas, complexity, and imagination into a process that would otherwise mainly be improved with small steps. That’s exactly the addition a conservative person doesn’t automatically provide.

The pitfall is that you hear questions about evidence as a lack of ambition. Then you make the idea bigger, mention more benefits, or present it even more enthusiastically. For your conservative colleague, it becomes less clear which concrete improvement is worth the extra uncertainty.

Don’t start with everything the new approach makes possible. Start with the problem you both recognize. Then propose a trial that’s small enough to reverse and big enough to learn something. Finally, ask: “Which quality from the current process must we not lose during this trial?” That way, you make preservation part of the design instead of a blockade at the end.

Five agreements you can use right away

A change with a conservative person doesn’t need special treatment. It needs mutual agreements that make both innovation and preservation testable.

1. We describe the problem before choosing a solution. We name where it occurs, who it affects, and why the current method doesn’t solve it sufficiently.
2. We record what must be preserved. A trial may not quietly remove a proven check, customer promise, or necessary routine.
3. We test on a limited scale first. Every trial has a target group, start, end, and owner. Temporary doesn’t mean unclear.
4. We choose the measurement points in advance. We decide before starting which evidence argues for continuing, adjusting, or stopping.
5. We make a visible decision at a set moment. After the trial, we choose to implement, adjust, or revert. We don’t let the test quietly become the new standard.

These agreements also help when no one calls themselves conservative. In our analysis of 2,705 personality profiles, 11% were conservative, 43% curious, and 46% progressive. A change process that only rewards enthusiasm misses a recognizable group that can see which value must be preserved.

What usually backfires

“We need to become future-proof” is not a reason anyone can test. Name which future requirement is already visible and which part of the work must change because of it.

A huge presentation with all the possibilities rarely helps either. More abstract benefits don’t automatically make an idea more concrete. It’s better to show one practical example, one trial, and two measurement points.

Also, don’t call questions about risks resistance. That makes critical information socially unsafe. Ask further: what risk does the other person see, what is it based on, and how can the trial check it?

And don’t quietly make a pilot permanent. If there’s no decision moment and fallback route, it wasn’t a trial but an implementation with a friendlier name. That damages exactly the trust the next change will need.

The smallest usable start

You don’t have to redesign the whole change process. Before the next announcement, fill in these four lines together:

The problem in the current way of working is: …

During the trial we will preserve: …

We will test with: … from … to …

We will decide based on: …

That short block does more than ask for an open attitude. It gives a conservative person something concrete to assess and a progressive person a fair route to create new evidence.

An anchor point is only useful if it leads to such an agreement. Want to see how a different preference changes daily collaboration? Read how to plan projects with a flexible person and how to run meetings with a quiet person. On Personal User Guide for work you can then create your own manual and compare your preferences with a colleague’s. That way, you don’t implement change for a label, but with the people who have to do the new work every day.