Store Manager Performance Conversation: Decision Brief
Prepare a store manager conversation that places one dated operational trend beside work conditions, then assigns an action and review.
Short answer
A store manager performance conversation should begin with one clearly defined operational trend and the conditions in which it occurred, not a conclusion about the manager. Bring the numerator, denominator, period, source and relevant changes; keep employee and manager accounts distinct from verified records. Use the discussion to test competing explanations, choose one proportionate action, assign its owner and decide what will be reviewed. The KPI remains an operational measure rather than a score of the person.
1. State the decision and the measure
Write the question the meeting can answer. Use one measure at a time and retain its calculation so a percentage cannot float free of the work it represents.
- Decision: which local action, check or support can this meeting reasonably assign?
- Measure: name the operational event, numerator, denominator, unit and authoritative source.
- Period: exact dates, trading days, opening hours and any exclusion agreed before comparison.
- Reference: the earlier period, target or peer context and why it is comparable enough to inspect.
- Boundary: state what the measure does not show about cause, quality, individual effort or manager performance.
2. Make a three-column context pack
Keep different kinds of information in separate columns. This makes it easier to challenge an explanation without dismissing the experience behind it.
- Operational records: counts, hours, volume, stock events, system incidents and planned changes, with source and date.
- Accounts: what employees, the manager or another owner described, with population, period and agreed sharing boundary.
- Open checks: records or people needed to examine an account, plus the named person responsible for obtaining them.
- Coverage: relevant roles, shifts and days represented or missing from the pack.
- Formal routes: safety, grievance, conduct, absence or customer issues that belong in their authorized processes rather than this brief.
3. Ask the manager to test the picture
Share the purpose, metric and period before the discussion. Ask the manager to correct the record, add conditions and distinguish what is known from what still needs checking.
- Does the measure match how the work was actually recorded during these dates?
- Which changes in demand, staffing, stock, layout, equipment or process should be verified?
- Which account fits the records, which conflicts with them and which cannot yet be checked?
- What was within the manager’s scope, and which dependency belongs to another owner?
- What alternative explanation should remain open before choosing an action?
4. Record a bounded conclusion
End the evidence review with one of three states: sufficiently supported for a local action, needs another check, or no action from this brief. Record disagreement rather than forcing a shared explanation. If an individual performance or formal employment issue emerges, move it to the appropriate process and use the general conversation pack where relevant.
5. Assign one action and its review
Choose a step proportionate to the evidence and within the named owner’s control. The action card should make implementation and later interpretation possible.
- Action and owner: the exact change or check, responsible person and required approval.
- Conditions: stores, shifts, dates, support and dependencies included in the action.
- Implementation check: how the team will know the action occurred as intended.
- Review evidence: the operational numerator and denominator, context measures and relevant accounts to revisit.
- Decision date: when to continue, adjust or stop, without promising that the measure will improve.
- Feedback: who will report the decision to the manager and participating employees.
Why this guide is useful
This original decision brief is for a regional or retail operations lead preparing a discussion with a store manager about one store-level trend. The general performance-conversation pack supplies an agenda and individual record; a short team briefing addresses a shared work problem with the team. This page performs a different job: it combines a bounded operational measure with store conditions before an accountable action is chosen.
Build the evidence pack before explaining the result
Fix the measure and comparison before the meeting. UK guidance from Acas says objectives should be fair and reflect a person’s usual tasks and workload, and that the written discussion record should be shared. UK HSE and US OSHA guidance on worker involvement in health and safety shows why relevant work accounts and formal safety routes need deliberate treatment. Apply those ideas narrowly: invite context, preserve uncertainty and route any safety concern through the applicable process. A store trend alone does not establish a manager’s contribution or cause.
Concrete example
Fictional example: a store’s share of click-and-collect orders ready by the promised collection time changes from 184 of 200 orders, or 92.0%, in four weeks before a layout change to 176 of 220, or 80.0%, in the following four weeks. That is a 12.0 percentage-point difference, while order volume is 10% higher. The operations log also records a staging move and five handheld-access incidents. Seven employee conversations describe difficulty locating completed orders; the manager describes later inbound deliveries. Those accounts suggest questions, not established causes. The regional lead and manager assign the manager a two-week test of a ten-minute pre-opening handover between the picking and collection leads using the existing approved process. They will review the same definitions of eligible orders and on-time readiness, recorded exceptions and time used. The result may support continuing, changing or stopping the handover; it will not measure the manager as a person.
What to look for
- One operational measure with a fixed definition
- Comparable periods and visible denominators
- Verified changes separated from work accounts
- More than one plausible explanation
- An action owner, review date and stop condition
Explore with Lontra
Lontra can support focused employee conversations about a defined store work moment. The regional lead and store manager place what a named reviewer has looked at beside authorized operational records, check the context and decide the follow-up. Lontra can score conversations against criteria you define and links each score to what was said, but it does not infer causality from the KPI or make a performance decision.
Explore focused employee conversations
Related reading
- Use the general performance-conversation record
- Compare store context before choosing a test
- Document a practice another store may test
Questions that come up
Can a store KPI show that a manager caused a result?
No. A store KPI describes an operational result under a stated definition and period. Examine demand, staffing, process, equipment and other conditions before discussing contribution, and retain uncertainty when the available evidence cannot establish a cause.
How should two store periods be compared?
Use the same numerator and denominator definitions, source and exclusion rules, then show material differences in trading days, volume, hours and operating conditions. If the periods are not sufficiently comparable, use the contrast to frame questions rather than a performance conclusion.
Are employee accounts facts in a manager conversation?
They are accounts of work experience. Preserve what was said and its coverage, then check relevant records or context where appropriate. Do not convert a recurring account into a finding about an individual manager without a suitable process and evidence.
Bring one performance question.
See the product on a question like yours, and what a first campaign could involve.