Test a Business Change in a Week

On Monday, you rewrote your first reply to a customer: you added the price, how the work happens, and how to book. On Wednesday, you changed the rescheduling rule. On Friday, you moved products near the checkout because it seemed more logical that way. At the end of the week, a familiar question appears: did things get better, or did you simply move a lot of furniture in the process?

One customer thanked you for a clear message, another stopped replying. It seems easier for an employee, but a new question has appeared in the chat. Impressions of changes are quick and convincing, especially when you came up with them yourself. But memory likes vivid cases, and several changes at once turn finding the cause into a drawer of cables: everything is connected, but it is unclear what exactly is not working.

You do not need a complex system to avoid guessing. You need a simple way to look at one change through a specific problem for a customer or the team. Not to prove the cause of everything that happened during the week, but to decide honestly: keep the new approach, adjust it, or abandon it.

“Improve the service” is a good idea, but it is too general. Look for a recurring moment when a customer stops, gets confused, or does not know what to do next.

The team also reveals such moments. If you or employees have to explain the same thing again and again, search for information in messages, or manually rewrite orders, the problem may not be with people but with the path itself. Usually, it is more useful to start with one recurring friction than to rebuild the whole way of working at once. State the problem in an ordinary sentence. Not “we need more sales” and not “we need to get things in order.” Write: “After the first reply, people often ask whether delivery is included in the stated price” or “After booking, people do not know what to bring with them.” Such a sentence already shows who the change concerns and exactly where it should help.

Choose one point to check

Then choose one problem for this week. If everything seems urgent, look at its daily cost: it takes money because the person does not reach the order; it takes your time because the answer is repeated; or it takes the customer’s patience because the path has extra steps. Also think about how often this situation repeats and whom it gets in the way of today. This is not a mathematical formula for priority, but a way not to start with the thing that simply asks for attention louder than the others.

Imagine a cake workshop. The owner notices that after asking “How much does it cost?” some people disappear. She does not declare that the price is to blame: there may be several reasons. Instead, she narrows the problem down: the first reply does not make clear what the price depends on or what the customer needs to do next. She adds a short explanation and asks for the date, number of guests, and preferred flavour. This is no longer an abstract “improvement in communication,” but one change you can observe.

Do not change everything else around it if you can avoid it. When you are checking a new reply text, a parallel change in price, advertising, or payment method will confuse the picture. In life, it is not always possible to isolate circumstances completely. But the fewer things you change at the same time, the easier it is to understand where to look next.

A sign of success is a simple, noticeable change in customer behaviour or team work that you use to check your idea. It does not answer the big question, “has the business become better?” It answers the narrower one: what exactly should become easier after this action?

For a small change, one sign is often enough. Customers ask one clarifying question less often. Fewer people ask for an explanation of rescheduling. Confirmation appears without extra messages. The team repeats the same instruction manually less often. Choose what is directly connected to the problem, not what is simply easy to see.

Write a check sentence before launching the new approach. For example: “After the new booking confirmation, customers ask about the address and payment less often.” Or: “After the cost explanation, customers more often move on to clarifying order details instead of returning with a question about what is included in the price.” You do not need to invent a metric that sounds impressive. You need a phrase you can compare with real situations.

Record what was there before the change

The starting situation is a short description of how the problem appeared before the change. Write it down next to it: which questions repeated, where people stopped, what had to be explained. Without this record, at the end of the week it is easy to believe that the current state has always been there, or, conversely, that everything used to be perfect.

Imagine a manicurist. Customers book in messages, and after confirmation they often ask about the address and payment method. The manicurist adds these details to the usual message. Her sign of success does not sound like “raise the service level.” It sounds simpler: “After confirmation, the same two questions come in less often.” The starting situation is a note that these questions repeated before the change. This way, the new template is checked by its usefulness, not by whether it is nicely written.

Remember the boundary of this kind of observation. If there were more or fewer enquiries in a week, that alone does not mean your new rule was the cause. The situation may be affected by a different type of enquiry, seasonality, a recommendation, advertising, or an event outside your control. The check helps you notice a basis for the next decision, not present an assumption as proof.

A check log is a list of short observations about situations after the change. Its job is not to collect the entire message history. It helps you avoid arguing with your own memory at the end of the week.

Anonymised notes are records without names, phone numbers, or other personal data when the essence of a person’s action or question is enough for the decision. A simple line in notes, a spreadsheet, or a work document may be enough: “after confirmation, they asked for the address again,” “the customer immediately sent the order details,” “the employee did not look for the terms in an old chat.”

After an enquiry, order, or workday, record only what answers your check sentence:

• what the customer did or asked;
• whether the exact difficulty you wanted to remove appeared;
• what the team had to explain or do;
• a short phrase from the person, if it explains the reason.

Do not turn the log into a diary. The note “they asked for the address again, although it was in the message” is more useful than a long retelling of the chat. And the words “I did not understand what to choose first” often explain the problem better than a dry note saying “did not order.” In our experience, short words from customers and employees often show which exact word, order of actions, or missing detail prevents them from moving forward.

Do not look only at what became more convenient for you. A new rule may remove manual work for the team while adding an extra step for the customer. For example, you removed the option to ask a question before checkout in order to exchange fewer messages. If people then disappear or return with the same doubts, convenience for the team does not make the rule successful. It will probably need to be reworked.

Mark unusual circumstances. A large atypical order, a service outage, a new advertising channel, or a mention of you in someone else’s post does not need to be hidden or crossed out. Simply add to the record that the day differed from the usual one. This way, one exception will not become the main argument for or against the change.

Compare the starting situation, the check sentence, and the log. Look not for one successful story but for a recurring pattern: did the confusion disappear, and did it become easier for both the customer and the team?

Sometimes the problem was clear and the new approach almost removed it. Then the change makes sense: keep it and write down the reason so you do not have to remember it from scratch in a few months. Sometimes it became a little easier, but customers still stumble over one sentence or a sequence of actions. In that case, you do not need to throw away the whole approach: clarify the specific part and keep observing.

It can also happen differently: the team spends less time, but it became harder for the customer. That is not half a success. It is a signal to return to the problem and look for an option that does not shift the inconvenience onto the person on the other side of the message. And when there are few notes or the entire week was atypical, it is more honest not to invent a conclusion. Continue observing the same change if the situations still repeat.

In the end, you have three normal decisions: keep, clarify, or cancel. Write one reason next to the decision. “I am keeping the confirmation because the address and payment stopped being separate topics in most bookings”; “I am clarifying the choice order because people still ask where to start”; “I am cancelling the new rule because it created a new misunderstanding.” This is not bureaucracy. It is your memory of why the rule appeared in the first place.

Do not wait for perfect confirmation. You are not conducting research on the entire market. You are choosing the next working action based on what you actually saw. Regularly checking small changes usually gradually replaces a mode where you only put out fires and remember the loudest one.

A short log works well when you are checking one small change and can see the customer path yourself. But a business may grow: enquiries come from different places, several people take part in the work, and records remain across different chats and systems. Then manual notes begin to fall apart not because you are doing them badly, but because it is already hard to bring the whole picture together.

In this situation, you may need systematic measurement: an agreed way to understand what exactly to track and where to get the data. It does not mean you need to collect more numbers for the sake of numbers. Its purpose is to ensure that the same problem does not disappear between a customer’s message, the team’s action, and the owner’s conclusion. This way, the reason is not lost between separate stages of work. Even with larger tools, start with the same question: which obstacle do you want to remove? A tool will not make this question clearer for you. But it can support clarity when you no longer have time to keep the entire story in your head.

The first step is simple: remember one recurring customer question from this week, write down where it appears, and choose one answer or action you will check next.