Acting Before You Understand: How to Choose a First Step You Can Take Back
You can't always wait for a full diagnosis. How to choose a small, reversible first step that helps you learn the cause as you act.

Imagine a hypothetical customer support team where handover errors have doubled in two months. The director wants action by Friday.
Nobody yet knows why. The obvious moves are a retraining course, a stricter process or a conversation with the person who makes most of the errors. Each assumes a cause.
Waiting for certainty isn't realistic. Guessing isn't wise either. This article is about the space between.
The short version: Acting early isn't the mistake. Acting on a guess about cause is. When you can't wait, choose a first step that is small, easy to undo and tells you something about the cause. Say in advance what you expect to see, and by when.
Acting early isn't the gap
We often describe a bad intervention as one that came too soon. The failure is a response built on an unchecked assumption about cause. Our guide to Behaviour Intelligence makes the case for understanding before deciding.
Sometimes the situation really can't wait. A client is at risk, a launch date is fixed or a team is visibly struggling. Doing nothing is also a decision.
So the question changes. It isn't "Should we act?" It is "What is the smallest sensible step that doesn't lock us in?"
A reversible first step is an action that costs little, can be undone, and teaches you something about the cause whichever way it turns out.
Four checks for a first step
Use these when you're choosing between options. They're our working checks, not a formula.
Reversible. Can you stop or undo it within days, without the person carrying a mark from it? A trial can be dropped. A formal warning can't.
Proportionate. Is it smaller than the problem you think you have? A first step that is as large as a final answer is a final answer.
Informative. Will the result tell you something about the cause? If the step works, what does that suggest? If it doesn't, what does that rule out? A step with no answer to both questions teaches nothing.
Open. Does the person know what you're doing and why? A step taken behind someone's back changes the situation, and not in a way that helps them or you.
The same observation, three responses
Illustrative scenario. The hypothetical support team, with three candidate responses.
| Response | Reversible | Size of step | Informative | Open |
|---|---|---|---|---|
| A mandatory retraining course for the whole team | Partly. The time is spent. | Large | Little. If errors fall, was it the course or a quieter month? | Yes |
| For two weeks, cap new work per person and ask each person to log what was happening at each error | Yes | Small | A lot. It shows whether workload, process or something else sits behind the errors. | Yes |
| A private warning to the person with the most errors | No. It stays on record. | Large | Little. It assumes the cause is the person. | No |
The second option isn't a solution. It's a way to find out. Suppose the logs show most errors came when someone held more than a few open handovers. Workload then moves up the list of explanations. If the logs show no such link, you've ruled one cause out cheaply.
It has a cost too. Capping work slows the team down for a while, so say so openly and keep it short.
The first option may turn out to be right. It simply asks the team to spend the most before you know anything. The third closes a door that you may need to reopen.
Decide in advance what would change your mind
Before you act, write three things down, such as these:
- What you expect to see if your guess about the cause is right.
- When you'll look.
- What result would make you drop the guess.
That last line is the hard one. Once a step is under way, it's easy to read any result as support. Errors fall, so it worked. Errors stay level, so it needs longer. Writing the answer first removes that room.
For example, the hypothetical support team's note might read: "We expect errors to cluster where people hold the most open handovers. We'll look at the logs in two weeks. If there's no such link, we'll drop workload as the lead explanation and look at the handover process next."
That is three sentences. It commits you to a result before you see it, and it tells the team what you're doing and why. It also leaves you with a next question whichever way the two weeks go.
Keep the review date short, in line with the step: days to a couple of weeks is our working guide. If it's too early to tell, extend it once, and say why.
For help choosing what to look at, What Changed Around the Person? shows how to build the timeline. Performance Is a Signal. Not a Diagnosis. covers the conversation that comes with it.
Hold the steps that close doors
Some responses are hard to take back. They aren't wrong in every case. However, they're costly to get wrong, so they belong later, once the picture is clearer. Examples include:
- A formal warning or improvement plan.
- A change of role, team or reporting line.
- A team-wide announcement about one person's results.
- A written label on someone's file.
Each changes how the person is seen by others, and how they see their work. If the cause turns out to sit elsewhere, you can't remove that change. What If the Behaviour Isn't the Problem? describes where causes can sit when it isn't the person.
Common questions about first steps
What if the cause turns out to be the person?
The first step has still helped. You will have ruled out other explanations, and the person is more likely to have been treated fairly along the way. A skills or motivation conversation then rests on better ground.
What if there's no time at all?
Choose the most reversible option you have and say plainly that it's a first step. Tell the person, and set a date to review it. A short, open step is better than a confident one you can't undo.
How small is small?
Small enough that you'd be comfortable stopping it next week. If stopping would feel like a failure, it's too big for a first step.
Where this leaves you
You will rarely have the full picture before you must act. What you can control is how much a wrong guess costs, and how soon you find out.
Small, open, reversible steps keep the cost low and the learning high. They also treat the person as someone to understand, not a problem to solve.
Opptimise helps people leaders see what they know and what they're still assuming, so the first move leaves room to learn.
A good first step buys understanding. Better understanding comes before better action.
Sources
Opptimise Editorial Team
Leading research and enterprise implementation in organizational psychology, executive development, and continuous Behaviour Intelligence.
Ready to Embed Behaviour Intelligence in Your Organisation?
Explore how Opptimise turns behavioural science into actionable daily coaching for your leaders and teams.
Related Insights & Next Reads
Halo and Recency: How One Impression Can Shape a Whole Review
Halo and recency effects can distort a performance review. How each works, and four checks to run against a dated record before you submit.
The Fundamental Attribution Error at Work: Why We Explain the Person and Miss the Situation
The fundamental attribution error explains behaviour through the person and underweights the situation. What it looks like at work, and what to check.
Observation vs Interpretation: How to Describe What You See Before You Explain It
Observation describes what happened; interpretation explains why. How to spot interpretation in your notes and rewrite it before a people conversation.
