Decide what the conversation needs to achieve
Before booking a meeting, identify whether the issue is learning, coordination, workload or an immediate boundary concern. Those are different conversations. A routine skill gap can wait for a planned review; a serious concern needs the authorized escalation route. Do not hide an urgent issue inside a vague coaching agenda or label every ordinary mistake as an incident.
Choose evidence relevant to the person’s actual work. Review more than one example if possible and note how the examples were selected. Compare like situations rather than contrasting a difficult account with an unusually successful shift elsewhere. The coach should be able to explain what they observed without assuming that the observation establishes a person’s intention or overall ability.
Set a narrow objective for the session. For instance, you might want to understand why handover actions are left without owners and agree a clearer method. That is more useful than asking someone to improve everything. Prepare the current approved instruction and check whether it conflicts with another source. Coaching cannot fix an undocumented expectation that different leads interpret differently.
Open with observation and invite the explanation
Describe what happened in neutral, concrete language. Separate the event from an interpretation about effort, attitude or personality. Tell the chatter why the behavior matters to team work and ask how they understood the situation. Give them time to explain tools, workload and instructions you may not have seen from the review sample alone.
A fictional case might involve two handovers where the next action was clear but no owner was named. The chatter may have thought the incoming shift automatically assigned ownership. That explanation does not settle the issue, but it changes the next step: check the team’s understanding and document the owner field instead of assuming the person refused to follow a known standard.
Listen for evidence that challenges the initial diagnosis. If several people misunderstand the same instruction, the source may need revision. If one person understands it but cannot apply it under load, practice or coverage may be needed. Record the explanation fairly. A one-to-one should improve the shared view of the problem, not function as a performance where the lead delivers a predetermined verdict.
A fictional one-to-one agenda
Observation: which behavior was reviewed? Context: what did the chatter see and intend? Standard: which current instruction applies? Practice: what action will the chatter try? Support: what will the lead provide? Review: who will check what, and when?
Agree a behavior the chatter can practice
Translate the discussion into an observable action. Define what the person will do, where the instruction lives and which support is available. Keep the action within the chatter’s authority. Asking them to guarantee team revenue or fix an access issue they cannot control creates accountability for an outcome without a practical way to influence it.
Use a short exercise when it helps. Give a fictional handover and ask the chatter to identify the next action, owner and escalation point. Discuss the reasoning and let the person revise the note. This checks understanding without exposing private fan conversations or turning a live shift into an unannounced test. Practice should resemble the decision the person needs to make independently.
Agree a review window appropriate to the opportunity to practice. A chatter who only encounters the relevant situation occasionally needs a different observation period from someone who handles it repeatedly. Do not manufacture certainty from a tiny sample. Write down what evidence would support improvement, what would prompt another check and who will make the follow-up review.
Use one-to-ones to develop strengths as well
A recurring one-to-one should include what is working and what the person wants to develop. Ask which decisions feel difficult, where instructions are unclear and what help would be useful. This makes the conversation a source of operational information, rather than a meeting people associate only with failure. Keep sensitive personal discussion separate from public team updates.
Recognize specific contributions. A reliable handover, a thoughtful escalation or a useful question can improve the whole shift even when it does not produce a visible sales spike. Explain the behavior and its effect. Avoid generic praise that gives the chatter no information about what to repeat or the impression that one impressive outcome excuses unrelated quality problems.
For a strong performer, explore whether they can explain a decision and support another person with permission. Coaching should not require everyone to copy one style. Ask what principles made the decision appropriate and when another approach would work better. A high performer’s knowledge becomes useful to the team when it is understandable, adaptable and consistent with approved creator boundaries.
Keep a record that supports follow-through
A useful coaching note includes the topic, relevant evidence reference, the chatter’s explanation, agreed action, support and review date. Keep access limited to people who need it. Record behavior and decisions rather than speculative labels. The note should let both participants remember the agreement without preserving unnecessary private message content or a detailed transcript of everything said.
At the next review, begin with the previous action. Ask what the chatter tried, what happened and whether the support was available. If the plan was not practical, revise it with an explanation. A manager who repeatedly sets actions and never checks them teaches the team that coaching commitments are optional or that the documents exist only for appearances.
If improvement is absent, reassess before repeating the same instruction louder. The issue may need a different training method, clarified authority, workload changes or a management decision under the actual applicable process. This guide does not establish consequences or contract terms. Escalate through the responsible manager rather than inventing a disciplinary step based on a general leadership article.
Protect fairness across the whole team
Apply the same quality expectations to people with different sales results. A top performer who ignores a creator boundary needs an appropriate response, just as a newer chatter does. Fairness does not mean identical training plans: people can need different support while being held to the same underlying standard. Explain that distinction when discussing consistency with other leads.
Calibrate reviewers periodically using the same authorized example. Compare how they interpret the rubric and update ambiguous wording. Otherwise a chatter may receive contradictory feedback depending on who happens to review the shift. Keep a record of revised standards and communicate the change before assessing people against it, except where immediate protective action is required under an existing instruction.
At Bunny, the Backend Manager brief includes team calls, one-to-ones, chat analysis and developing the chatting team. Experienced candidates can demonstrate these skills through anonymized cases. Internal progression toward leadership follows consistent live-account results and individual readiness. A coaching example can support that discussion, but a well-run meeting alone does not guarantee promotion, a management vacancy or a hiring outcome.
Questions about this leadership topic
How often should one-to-ones happen?
Agree a cadence based on team needs, capacity and the topic. No specific Bunny one-to-one frequency has been supplied here, so the guide does not invent a required schedule.
Should feedback happen in the group chat?
Discuss sensitive individual feedback privately. A general lesson can be shared after removing identifying details and checking it is appropriate for the audience.
What if the chatter disagrees with the review?
Ask for their evidence and reasoning. Recheck the sample and approved standard, document the disagreement accurately and involve the responsible manager where a decision remains unresolved.
Can revenue be the only coaching measure?
It cannot explain all quality or workload issues. Review relevant observable behavior and context alongside commercial outcomes, using defined measures and comparable periods.
How do I show coaching experience in an application?
Describe an anonymized situation, what you observed, how the person responded, the action agreed and the follow-up evidence. Distinguish your contribution from other team changes.