What to notice in your first month of retail.

Write down the question customers keep asking.

The first month of a new store contains a lot of useful detail that can disappear between shifts. A customer asks whether two products work together. Several people look for the same size. Someone reaches the payment point still unsure how the service works. Give the team a simple place to record these moments.

Capture the question as closely as possible, along with the relevant product or part of the store. Avoid attaching a name or unnecessary personal information. The purpose is to understand the experience and the information people need.

Ask the team to separate what happened from what they think it means. Three customers asking about a material is an observation. The conclusion that the market misunderstands the brand is a much larger claim. The next step may be as small as making the material information easier to find.

Keep the trading conditions next to the numbers.

When reviewing sales or store activity, add the context that could affect the interpretation. Record opening hours, product availability, events, promotions and any disruption that changed the customer experience. Compare like with like where the available information allows it.

For example, a hypothetical store sees fewer purchases of one style during its second week. Before changing the display, check whether the relevant sizes were available. A stock gap and a lack of customer interest call for different responses.

Agree definitions before comparing reports. If two people use different meanings for a visit, an inquiry or an unavailable item, a tidy spreadsheet can hide inconsistent information. Keep the method stable enough that the team understands what has changed from one review to the next.

Ask the store team where the work gets awkward.

Some of the most useful opening feedback concerns ordinary tasks. Where does replenishment interrupt service? Which display is difficult to restore? What question sends staff searching through several messages for an answer?

Invite a specific example and follow the routine in the space. If packaging is hard to reach, watch someone pack a purchase. If a product is difficult to find, trace the route from the customer’s request to the stock location. This gives the team a shared problem to discuss.

Sort the findings into problems to fix now, changes to try and questions that need more observation. Assign responsibility so the same item does not return every week without a next step.

Make a change you can follow.

Choose a clear question for each adjustment. A revised sign might be intended to answer a recurring product question. Moving a display might be intended to make a category easier to find. Record what changed and when, then look for the observation that would tell you whether to keep exploring it.

Changing the assortment, display, offer and messaging at once makes it difficult to understand any one effect. Where practical, narrow the change and keep the wider trading conditions visible. Treat the result as useful information for this store in this context.

Some issues will need specialist analysis or more time. A small observation log cannot establish why every sale happened or predict the performance of another location. It can help the team choose better questions for that deeper work.

Send headquarters a decision, as well as an update.

A useful first-month review gives the global team a concise account of what was observed, what the local team changed and what still needs a decision. Include a few representative examples and the limits of the available evidence.

Finish with named actions: information the team needs, an operating correction, a design adjustment or a question for the next review. For example, request a decision on replenishing a repeatedly unavailable size, supported by the recorded requests and current stock position.