People Development
At this stage, you're stepping into your first real people responsibility. You may still be writing code, but your primary job is shifting: the most important thing you build now is trust. You're learning how to have honest conversations, set expectations, and help people feel seen. This is where a lot of new managers stumble. You might default to solving problems for people instead of helping them grow through problems. You might avoid hard conversations because you still think of your reports as peers. That's natural, but recognizing it is the first step.
Key Behaviors
- Holds regular, structured 1:1s focused on the individual, not just status updates
- Gives timely, specific feedback tied to observable behavior
- Learns each person's goals and begins connecting daily work to growth
- Addresses small performance issues early instead of letting them build
- Asks questions before offering solutions to help people develop their own judgment
Common Struggles
- Avoids difficult feedback because the relationship still feels peer-like
- Spends 1:1s on project updates instead of development conversations
- Tries to fix problems for people rather than coaching them through it
- Feels uncomfortable with the power dynamic and overcompensates with niceness
Success Indicators
You know you're successful when you:
- Your direct reports know where they stand and what's expected of them
- People feel safe raising concerns or sharing mistakes with you
- You deliver feedback that is honest and kind, not one or the other
- You're starting to see the difference between managing tasks and developing people
Mindset Shift
From:
"I need to make sure everyone's work gets done."
To:
"I need to make sure everyone is growing while doing the work."
Questions to Ask Yourself
- Do my direct reports know exactly what I expect from them?
- When was the last time I gave feedback that was uncomfortable to deliver?
- Am I solving problems for people, or helping them solve problems themselves?
Build These Habits
- 1Prepare for every 1:1 with at least one development-oriented topic
- 2Write down feedback within 24 hours of the event. Don't wait for a review cycle
- 3After giving advice, pause and ask: "Could I have asked a question instead?"
- 4Keep a running doc of each person's goals, strengths, and growth areas
Seek Feedback
- "Do you feel like our 1:1s are useful for your growth?"
- "Is there feedback I should be giving you that I'm not?"
- "How could I better support your development?"
Signals You're Ready to Level Up
- Your reports describe you as someone who genuinely invests in their growth
- You're comfortable delivering hard feedback without damaging trust
- People on your team are visibly improving in areas you've coached
Focus Summary
- Build trust through honesty
- Coach, don't solve
- Make feedback routine
At this stage, the shift from peer to leader is the hardest part. Your job isn't to be the best engineer on the team anymore. It's to make everyone around you better. Start with trust, stay honest, and don't skip the uncomfortable conversations.