Learn From Colleagues at Work: A Checklist for Busy ICs

Why learning from high performers matters

Formal mentors, courses, and manager-led programs are useful when you have them. Many individual contributors do not. Skill growth still has to happen inside the workday, on real projects, with the people already around you.

When you learn from colleagues at work in a deliberate way, you shorten feedback loops, reduce guesswork, and build judgment that sticks. The long-term value is compounding: better defaults under pressure, clearer communication, and a personal playbook you can reuse on every new assignment.

Checklist: prepare before you observe

Clarify one skill, not everything

• ☐ Pick one outcome you care about this month (cleaner estimates, sharper updates, faster debugging, calmer stakeholder notes).
• ☐ Name two teammates who already deliver that outcome consistently.
• ☐ Write what “good” looks like in one sentence so you know what to watch for.

Set lightweight boundaries

• ☐ Decide you will not interrupt deep work with constant questions.
• ☐ Prefer shared artifacts (tickets, docs, pull requests, meeting notes) over private shadowing when possible.
• ☐ Ask for short, specific debriefs only after you have tried something yourself.

Checklist: observe high performers in plain sight

Watch the process, not the personality

• ☐ Notice how they start work: intake questions, scope cuts, risk flags.
• ☐ Track how they communicate status: timing, level of detail, what they omit.
• ☐ Capture how they handle ambiguity: what they decide alone vs. escalate.
• ☐ Note recovery patterns after misses: what they change next time.

Collect evidence you can reuse

• ☐ Save one strong example per week (a message, checklist, outline, or decision log).
• ☐ Rewrite it in your words so you understand the structure, not just the tone.
• ☐ Tag each note with the situation it fits (kickoff, review, incident, handoff).

Checklist: turn observation into practice

Run tiny experiments on live work

• ☐ Choose one habit to copy for five working days only.
• ☐ Apply it on a real task before asking for feedback.
• ☐ Measure one simple signal (fewer revisions, clearer next steps, less rework).
• ☐ Keep what worked; drop what did not fit your role or constraints.

Ask better questions when you need them

• ☐ Lead with context and your attempt: “I tried X; Y still breaks; what would you check first?”
• ☐ Request principles, not full solutions.
• ☐ Close the loop by sharing what you changed afterward.

Checklist: protect the long-term value

• ☐ Keep a living “borrowed plays” list with date, source teammate, and result.
• ☐ Review it every Friday for ten minutes; promote repeats into your default workflow.
• ☐ Rotate focus quarterly so you build breadth without scattering attention.
• ☐ Credit people privately when their approach helped; goodwill keeps learning channels open.

Practical impact you should expect

This approach does not replace deep coaching when you need it. It does give busy ICs a reliable path to learn from colleagues at work without waiting for a mentor match or a new program. Benefits show up as fewer stalled tasks, stronger independent judgment, and a habit of turning nearby excellence into your own durable skill set.

Start with one skill, one teammate pattern, and one week of deliberate practice. Consistency beats intensity.