
What to Do When Someone Does It Differently
TL;DR: When an employee does a task differently than you expect, name which steps must stay the same, usually safety, billing, and customer promises, and which steps can vary without creating risk. Watching someone work a different way feels like a problem, but the real question is whether the outcome and the fixed steps are intact. A short, plain conversation that separates the two settles it faster than an argument about style.
Key Takeaways
- An employee doing a task differently is not automatically a problem if the required outcome and the fixed steps are unchanged.
- Fixed steps are the parts of a process tied to safety, billing accuracy, or a promise made to a customer, and they cannot vary by person.
- Flexible steps are the parts of a process where different methods produce the same acceptable result.
- A handoff or training document should state explicitly which steps are fixed and which are flexible, so no one has to guess.
- Correcting someone’s method without checking the outcome first creates unnecessary friction and can shut down a better way of working.
- The right response to a different method is a specific question about the fixed steps, not a general objection to the difference itself.
When an Employee Does a Task Differently, What Should You Check First?
When an employee does a task differently, check whether the outcome matches what was required and whether any fixed step, meaning a step tied to safety, billing, or a customer promise, was skipped or altered. If the outcome is correct and every fixed step held, the different method is a variation that does not need correcting. If a fixed step was changed, that is the actual concern, not the fact that the method looked unfamiliar.
A manager who sees an unfamiliar sequence can assume it is wrong because it is different and step in before checking the result. That reaction treats difference and error as the same thing, and they are not.
A different method can be a valid method. The question is whether it holds the parts that were never supposed to move, not whether it matches the original approach.
A different method is valid when the required outcome and every fixed step hold.
What Counts as a Fixed Step Versus a Flexible Step?
A fixed step is a part of a task that must stay the same no matter who performs it, because changing it creates a safety risk, a billing error, or a broken promise to a customer, while a flexible step is any part where a different approach still produces an acceptable result. The split is about which parts of the task, if altered, create downstream cost or harm, and which parts are just habit, not about preference or tradition.
A task can carry both kinds of steps mixed together, which is part of why this gets confusing in the moment. The order someone opens files, the tool they use to track their own progress, the way they phrase a routine email, these usually can vary. The number entered on an invoice, the verification step before a bulk change, the words used to confirm a delivery date with a customer, these usually cannot.
| Type | Definition | Example (illustrative) |
|---|---|---|
| Fixed step | Must stay the same for every person who does the task | Verifying a customer’s account number before processing a refund |
| Flexible step | Can vary without changing the outcome | Using a spreadsheet versus a notepad to track daily tasks |
| Gray area | Looks flexible but touches a fixed outcome | Skipping a confirmation email because the person believes it is unnecessary |
A disagreement often starts in the gray area row. Someone changes a step they believe is flexible, but it quietly touches billing accuracy or a customer-facing promise, and nobody flagged it as fixed in the first place.
A fixed step is any step where a change creates a safety risk, a billing error, or a broken customer promise.
Why Naming the Fixed Steps Matters More Than Naming the Right Method
Naming the fixed steps matters more than naming the right method because it lets an employee choose their own approach for everything else, which reduces unnecessary correction and keeps attention on the parts that actually carry risk. A written rule that says “do it this way” invites every deviation to look like noncompliance. A rule that says which steps cannot move and leaves the rest open removes that ambiguity.
The concern is whether the fixed steps, the ones tied to safety, billing, or a customer promise, stayed in place, and the method matters less.
This also protects against a different failure: correcting someone for a flexible step and ending a better approach before anyone tests it. SCORE’s guidance on delegating tasks advises owners to resist stepping in when a delegated task goes wrong during the learning process, and to let the employee notice and fix the mistake first. Stepping in on a flexible step teaches someone to stop making decisions rather than to make better ones.
After an issue with a bulk update to records on a healthcare IT team, leadership required an extra comparison check against the other system’s records before any bulk action, to reduce downstream tickets and collisions. When a similar request comes up, I hold to that check, and if the person can’t run the comparison, I bring in someone who can validate it before the update goes ahead. The comparison check is the fixed step in that example.
How to Say Which Parts Are Fixed Without Starting a Fight
Say which parts are fixed by naming the specific outcome required, the specific step tied to safety, billing, or a customer promise that cannot move, and then stating plainly that everything else is open. This gives the other person a clear target instead of a vague sense that their work is being questioned, and it keeps the conversation about the task, not about the person’s judgment.
A workable version sounds like this:
- State the outcome you need, in plain terms, not the method you expected.
- Name the one or two steps that are fixed, and say why (safety, billing, or a customer promise).
- Say explicitly that the rest of the approach is flexible and theirs to decide.
- Ask whether the fixed steps were followed, as a direct question, not an accusation.
- If a fixed step was missed, address that specifically. Do not reopen the whole method.
A plain way to resolve this disagreement is to ask which fixed steps were followed, and to leave the method itself out of the question.
Correct the fixed step that changed and leave the rest of the method alone.
What not to do: do not open with “that’s not how we do it.” That framing puts the method on trial before anyone has checked the outcome, and it tells the employee that deviation itself is the offense, which discourages the kind of initiative that sometimes finds a better way.
In Practice: Separating Fixed From Flexible Steps
Situation: An office manager notices that a new hire processes customer refunds in a different order than the written procedure, starting with the account lookup instead of the payment confirmation.
Steps:
- Identify the outcome the task is supposed to produce, using the written procedure or policy as the reference point.
- List every step in the current procedure and mark each one as tied to safety, billing accuracy, or a customer promise, or as open to variation.
- Confirm with the employee which steps they followed, using the marked list as the basis for the conversation.
- Check the result against the required outcome, such as whether the refund amount and account match the original transaction.
- Document the fixed steps in the handoff or training material, stating explicitly that the rest of the sequence is flexible.
- Revisit the list after a few uses to confirm the fixed steps still hold and nothing drifted.
Result: A short written list exists that separates fixed steps from flexible ones, and anyone new to the task can read it and know exactly which parts cannot move. A different method no longer triggers a correction once the fixed steps are the only thing being checked.
Common mistake: Treating the entire procedure as fixed because it was written down once. Fix this by reviewing the list and asking, for each step, whether changing it creates a safety, billing, or customer-promise problem. If not, it is flexible.
If it goes wrong: If the outcome is off after a different method was used, trace the result back to the specific fixed step involved rather than reverting to the original method wholesale.
This is a generic illustration, not a client result.
FAQs
How do I know if an employee’s different method is a problem?
It is a problem only if the outcome is wrong or a fixed step, tied to safety, billing, or a customer promise, was skipped or changed. If the result matches what was required and the fixed steps held, the different method is a variation worth noting, not correcting. Check the outcome before judging the method.
What is a fixed step in a work process?
A fixed step is a part of a task that must stay the same for every person who performs it, because changing it creates a safety risk, a billing error, or breaks a promise made to a customer. Everything else in the task is open to variation as long as the required outcome is still met. Fixed steps should be named explicitly in training material or a handoff document.
Why does watching someone do a task differently feel uncomfortable?
It feels uncomfortable because an unfamiliar method looks like a departure from what was taught or expected, and the instinct is to treat unfamiliarity as a risk before confirming whether it actually is one. That discomfort is a normal reaction to seeing a known process change shape, and it is worth separating from the actual question, which is whether the outcome and fixed steps are intact.
Should I correct an employee every time they do something differently?
No, correct only when a fixed step was changed or the outcome did not meet the required standard, since correcting flexible steps discourages initiative without reducing any real risk. SCORE’s guidance on delegating tasks recommends letting an employee notice and fix a mistake during the learning process rather than stepping in immediately. Reserve direct correction for the steps that actually carry risk.
How do I write down which steps are fixed and which can vary?
List every step in the task, mark the ones tied to safety, billing, or a customer promise as fixed, and mark the rest as flexible, then share that list as part of training or a handoff. Keep the fixed list short and specific, naming the exact step rather than a general category. Update the list if a new risk is identified later.
What should a handoff document include when a task changes hands?
A handoff document should state the required outcome, list the specific fixed steps and why each one is fixed, and say plainly that any other part of the method is left to the person doing the work. This keeps the next person from guessing which parts matter and which parts are just the previous person’s habit, and it gives a manager a clear reference point when checking the work later.
Is a different method always a sign of a training gap?
No, a different method often reflects a reasonable choice made by the person doing the work, and it only signals a training gap if a fixed step was missed or the outcome came out wrong. Treating every variation as a gap discourages people from adapting a process to their own strengths. Check the fixed steps and the result first, then decide if training is actually needed.
Next Steps
Separating fixed steps from flexible ones takes one short conversation and a written list, and it settles these disagreements before they start. Share this with someone who’s learning to let go of how a task gets done.
