Feedback

Comparing Level 1 and Level 2

Description

At Level 1, you're starting to understand that feedback is part of your job, not just something that happens in performance reviews. You may be new to giving or receiving feedback in a professional context, and that's okay. This level is about developing openness, curiosity, and basic skills. You may not yet feel confident offering suggestions or critique, but you're learning to listen well, receive feedback without defensiveness, and ask for input when you're unsure.

Description

At Level 2, feedback becomes a regular part of your workflow. You not only receive it gracefully—you also begin offering it, especially in areas like code reviews, technical design, documentation, and collaboration. You're learning how to give specific, constructive input that helps others improve. You see feedback as part of working well with others—not just correction, but contribution.

Key Behaviors

  • Listens to feedback without becoming defensive
  • Thanks others for feedback, even when it's hard to hear
  • Incorporates simple suggestions into future work
  • Asks for clarification when feedback is unclear
  • Begins to ask for feedback on work or behavior

Key Behaviors

  • Gives thoughtful feedback on code reviews and technical documents
  • Offers both positive and constructive input, not just one or the other
  • Uses questions to guide others toward insight ("What do you think about…?")
  • Responds to feedback with curiosity and follow-up
  • Regularly asks for input on technical decisions and work quality

Common Struggles

  • May take feedback personally or shut down emotionally
  • Unsure when or how to ask for feedback
  • Hesitates to offer feedback, even when prompted
  • Over-focuses on praise and avoids critique

Common Struggles

  • May avoid giving feedback in high-stakes situations
  • Can give vague or overly general feedback (e.g. "looks good")
  • Struggles to calibrate tone—too soft or too blunt
  • Might take critical feedback on technical work personally

Success Indicators

  • Show openness and a willingness to learn from feedback
  • Act on constructive input in your day-to-day work
  • Ask for feedback when uncertain or seeking improvement
  • Begin to see feedback as a tool for growth, not judgment

Success Indicators

  • Offer specific, helpful feedback in pull requests and team discussions
  • Treat feedback as a normal, healthy part of collaboration
  • Ask for feedback before it's too late to change course
  • Communicate feedback in a respectful, timely, and constructive way

Mindset Shift

From:

"Feedback is scary or personal."

To:

"Feedback helps me get better and build trust."

Mindset Shift

From:

"Feedback is a task or a critique."

To:

"Feedback is collaboration and investment."

Questions to Ask Yourself

  • What can I learn from this, even if it's hard to hear?
  • Who do I trust to give me honest input?
  • When have I grown because of someone's feedback?

Questions to Ask Yourself

  • What feedback will help this person (or project) succeed?
  • Have I delivered feedback in a way that builds trust and clarity?
  • Am I modeling the kind of feedback culture I want to be part of?

Build These Habits

  • 1
    Ask for feedback on specific aspects of your work (e.g. code quality, communication)
  • 2
    Reflect before reacting to feedback
  • 3
    Write down recurring themes or suggestions to track your growth
  • 4
    Say thank you when someone offers feedback—even if you disagree

Build These Habits

  • 1
    Offer feedback soon after the event—not weeks later
  • 2
    Balance critique with curiosity and encouragement
  • 3
    Be clear, kind, and focused on impact

Seek Feedback

  • "What's one thing I could do better next time?"
  • "Was I clear in that message or review?"
  • "Do you have any suggestions for how I could improve this?"

Seek Feedback

  • "Was that code review helpful or overwhelming?"
  • "Is there something I missed or misunderstood in your approach?"
  • "How can I improve the way I give feedback in reviews or meetings?"

Signals You're Ready to Level Up

  • You invite feedback regularly and with specific questions
  • You respond with maturity, curiosity, and follow-through
  • Others feel safe giving you honest input

Signals You're Ready to Level Up

  • Teammates seek out your input on technical and team matters
  • Your feedback improves outcomes without damaging trust
  • You're known for being honest, thoughtful, and respectful

Focus Summary

  • Listen fully
  • Ask often
  • Grow intentionally

At Level 1, feedback becomes something you engage with—not avoid. You build the muscle of receiving input well, and that's the foundation for everything that follows.

Focus Summary

  • Be specific
  • Be timely
  • Make your feedback count

At Level 2, feedback becomes a tool you use daily—not just to improve your work, but to help your team grow. You're not just reacting—you're contributing.