Help a New Store Manager Coach a Veteran Associate

New store managers often hesitate before giving feedback to an associate with longer tenure. Experience deserves respect, yet experience does not remove clear expectations. A manager need not prove superior knowledge. The job is to describe observed work, ask for the associate's view, and agree on a next attempt.

Start with evidence. One rushed exchange rarely supports a broad claim. Observe several interactions across ordinary shifts before calling a pattern. Notes need only record the shopper's question, the associate's response, a source checked, and where conversation ended. Leave labels such as careless, resistant, or old fashioned out of your notes. Labels invite an argument about character. Observable facts give both people material for a shared review.

In a fictional coaching conversation, April speaks with district manager Ken. “I watched Jordan answer a return timing question from memory and move on without checking policy. Jordan has more store experience than I do. I worry Jordan will say I do not understand this store.” Ken answers, “You have one observation. Gather two more from separate situations. Open with what you saw, not a verdict. Ask Jordan how those conversations look from Jordan's view.” April writes two observation times before leaving Ken's office.

The next observations should examine the same behavior without feeling like surveillance. April watches one product availability question during an afternoon shift and one delivery question during an evening shift. She records whether Jordan checks an approved source before answering, how uncertainty is expressed, and whether the shopper receives a next action. April does not follow Jordan around the sales floor or count every phrase. Her notes answer one limited question: does the first example show a repeatable habit worth discussing?

Choose a private moment for feedback. Do not begin during a rush, beside another associate, or within hearing range of a shopper. April asks Jordan for ten minutes after a shift or during a quiet coverage period. She gives a short reason: “I want to talk through two shopper conversations I observed and hear your view.” The request avoids mystery. Jordan knows the meeting concerns work examples, yet does not arrive expecting a public reprimand.

Open with a specific observation and leave space for context. April says, “On Tuesday, a shopper asked about a return deadline. You answered from memory, and no policy source came up before the shopper left. On Thursday, a shopper asked about delivery timing, and we had a similar ending. What was happening from your view?” Her wording does not assign harmful intent. Jordan might describe a busy line, a familiar policy, a slow system, or a training gap. April listens before selecting a next step. Context informs coaching without erasing the observed concern.

Listening does not mean dropping the concern. Suppose Jordan says, “I know those answers. Shoppers do not want a long search while they wait.” April acknowledges the goal, then returns to behavior: “Fast help matters. I also need us to confirm details before an answer sounds final. What would make source checking fit your pace?” Jordan might suggest keeping an approved reference open near the service desk or asking a nearby teammate to cover a shopper briefly. The plan becomes a practical adjustment, not a contest over seniority.

Avoid using tenure as a shield or an accusation. “You have been here too long for this” creates shame. “You know more than I do, so handle this your way” leaves a manager without standards. Respect shows up through preparation, direct language, and curiosity about the associate's experience. April asks Jordan which questions new hires struggle with most. Jordan's answer might improve floor support, while feedback still addresses source checking. Both contributions fit within one conversation because each points toward better work during busy shifts.

Set one observable next attempt. “Be more careful” gives Jordan no clear action. April offers a narrower agreement: “For return timing and delivery timing questions this week, check an approved source before confirming an answer. When the source does not resolve a question, tell the shopper you will follow the store process for follow up.” The agreement names the moment, action, and handoff expectation. April asks Jordan which part feels unclear before ending the meeting.

Schedule a follow up while both people sit together. A date without a purpose feels like a warning. April gives the check in a useful focus: “Next Wednesday, let us review two conversations and see how source checking worked during busy hours.” Jordan has time to bring examples, and April has another opportunity to observe fairly. Two conversations do not prove a lasting result. The follow up is a working review, not a verdict waiting at the end of a calendar entry.

Roleplay before a live discussion. In a fictional practice, Ken plays Jordan and says, “You are new here, so you do not know how this store runs.” April replies, “You know this store well, and I want your view. I also observed two conversations where no policy source was checked before an answer. Let us find a fast way to handle those questions.” Ken pauses the practice. He asks April which sentence named evidence, which sentence showed respect, and which sentence invited Jordan's ideas. April then tries a shorter version using natural words.

Watch for language which softens a message until meaning disappears. “I wondered whether we should review policy questions sometime” makes the purpose hard to hear. Direct wording is kinder. April does not need to apologize for asking an associate to use an approved source. She does need to speak without blame. Replace a long preamble with one factual example, one open question, and one agreed action. After practice, April checks whether her words describe an observation or quietly suggest a motive. If a motive slipped in, she rewrites the opening.

Written follow up has value after the conversation. April sends a brief note stating the observed focus, Jordan's chosen next attempt, and the next review time. The note does not retell every word or assign motives. A shared record helps both people return to the same agreement. When Jordan raises a concern April cannot resolve, April records the concern through store practice and seeks guidance from the relevant leader. She does not invent a policy answer merely to end an uncomfortable exchange. Clear ownership protects both the manager and associate.

Use district support with care. Ken might observe April's opening or join a later debrief, yet April leads her own conversation. Before observation, she tells Ken which feedback she wants, such as whether her opening named evidence without sounding accusatory. Afterward, Ken asks April what she noticed before offering his view. This order helps a new manager develop judgment rather than wait for a district manager to supply every sentence. Ken's role is preparation and reflection, while April carries the actual feedback conversation.

For the next practice, April places two fictional notes on a table. One records a policy question answered from memory. The other records Jordan checking an approved source before responding. April opens a ten minute roleplay, asks for Jordan's view, agrees on source checking during the next busy shift, and writes “review Thursday at 3 PM” in her manager calendar before the roleplay ends.