How can I learn from a peer without simply copying their method?
Quick answer
Ask your peer to explain the purpose behind key steps, the conditions that make them useful, and the signs they use to decide what to do next. Compare those conditions with your responsibilities, tools, and constraints before trying anything. Adapt one element at a time, check whether it helps your work, and keep or revise it based on what you observe—not just because your peer does it that way.
The question, the details, the next step.
A teammate has a way of handling a recurring task that looks effective. How do I observe it without turning the conversation into “show me exactly what you do so I can copy it”?
Frame the goal as understanding their decisions, not collecting a script. Ask to observe one ordinary example, if they are comfortable, and request that they talk through what they notice and why they choose each important step. Pay attention to the problem each step is solving: preventing a missed detail, coordinating with someone, or deciding when the work is ready to move on.
You could say: “I’m trying to improve how I handle this task. Would you walk me through one example and explain what you’re paying attention to? I’m interested in the reasoning, so I can see what might apply to my version.”
Ask before observing or reviewing their materials. Your aim is to learn the logic behind a method while respecting that you may have different assignments.
What questions help me find out which parts of their approach depend on their particular situation?
Ask about conditions and decision points rather than just sequence. For example:
- “What tells you this step is needed?”
- “When would you skip it, change it, or ask someone else?”
- “What information or access do you need before you start?”
- “Which part is specific to your responsibilities or experience?”
- “How do you notice that the result is ready to hand off?”
Listen for dependencies: a certain kind of request, a familiar contact, a tool you do not use, or authority that may not be part of your role. If something is unclear, ask for an example and check your understanding: “So you do this when X is true, but not automatically every time—is that right?”
This helps separate a useful principle from a personal habit. A peer’s explanation is a starting point for your judgment, not proof that every step fits your situation.
Once I understand their reasoning, how do I decide what I can adapt without taking on a method that does not fit my role?
Compare the circumstances behind their choice with your own. Consider the task outcome, your responsibilities, the information available to you, the people you need to coordinate with, and any expectations you have been given. If a difference could change the result or who is responsible, clarify it with the relevant person before changing that part of the work.
Suppose your peer makes a short checklist before sending a routine update. If your updates involve the same kinds of details, you might try that checklist. If your work requires an approval your peer does not need, do not remove that step just because it is absent from their method. Preserve your responsibility and adapt only the reminder format.
Choose one small, reversible change when possible. Notice whether it helps you meet the task’s intended outcome or creates extra work or confusion. If the result is mixed, adjust or stop. You are testing a fit, not trying to become a copy of your teammate.
Can you give me a short guide I can use in the conversation and afterward, so I remember what I learned?
Use this note with your own details; do not treat your peer’s answers as instructions for every case:
Task I want to improve: [task]
What my peer was trying to achieve: [intended result]
Their important decision points: [what they look for, and when they change course]
Conditions their method depends on: [tools, information, authority, timing, or collaborators]
What is different in my role: [responsibilities, constraints, or expectations]
One element I will try: [small adaptation]
How I will judge whether it helped: [observable sign related to the task]
What I will clarify first: [open question or boundary]
You can close with: “I’ll try [adaptation] for [suitable kind of task] and check whether [observable sign]. I’ll keep [existing responsibility] unchanged. If I run into [condition], I’ll ask before proceeding.” If the method depends on an unclear team expectation, ask your manager or the process owner to clarify it.
A practical checklist
Ask permission to observe or discuss a specific example.
Record the reasoning and decision points, not just the order of steps.
Identify conditions that differ between your peer’s work and yours.
Clarify role boundaries or team expectations before changing a consequential step.
Try one suitable adaptation and name an observable sign that would show whether it helps.
A few more useful answers
What if my peer says, “That’s just how I do it”?
Ask about a recent moment when they chose that step: what they noticed, what they hoped to prevent, and what might make them choose differently. If there is no particular reason, treat it as a personal preference rather than a rule.
How do I avoid making my peer feel judged?
Describe your own learning goal and ask curious, specific questions instead of rating their approach. Thank them for explaining their reasoning, and avoid implying that your task must be done their way.
How many changes should I try at once?
Start with one change where you can reasonably observe its effect. That makes it easier to tell what helped and to reverse or adjust the change if it does not suit your work.