Production‎ > ‎


Delegate, delegate and delegate some more

Act the part
  • You are not a peer anymore
  • Threat people with respect
  • Communicate professionally (no gossip, no sarcasm)
  • Be approachable
  • Be a champion for the direction you're given. You can disagree in leads meeting but when they decision is made live with it and help your team make the best with it.
Establish a clear direction
  • Make sure you have a vision for how the team should work and communicate it clearly.
  • Communicate the expectations to the team so they can predict with some accuracy whether or not you will think things are going as anticipated.

Help the team improve

  • You need to find out the growth and career goals of each developer on the team.
  • Use that information to train them by letting them work on problems that they don't already have done or let them learn things that they wish to focus on.

  • Feedback is when you tell someone how to improve the work that they do.
  • It can contain both negative or positive feelings for the person you give the feedback to.
  • Some people might have problems handling the negative feedback (things that was done wrong) and others the positive (things that was done right).
  • Do feedback in public to teach people how to give and take feedback.
  • Focus on what they should to make it better, not that something was done wrong.
  • Teach everyone that it's not a disaster to make mistakes.
Criticism / Praise
  • Do criticism in private and praise in public.
  • Address problems right away
  • Don't over commit yourself with tasks
  • Let people grab tasks, assign the rest
  • Your team are or will soon be the domain experts if you let them.
  • Take interests and career goals into consideration
  • let people learn new skills and techniques
  • if possible avoid repetitive tasks
Provide challenges, not solutions
  • Create task that have the problem and the constraints.
  • You can provide suggestions for solutions but if you always do that they will not learn to act independently when needed.
  • Let your team find the solutions, they are or will soon be the domain experts if you let them.
Track Progress
  • Be aware of what each team member is doing and track the progress.
  • Use an issue tracker and add a filter that display what each team member is working on right now.
  • Look over the commits from time to time.
  • Talk to them.
  • Identify problems early and teach them to notify you early if the have a problem finding a solution.

- If don't know, gather information and follow up.
- Be proactive- Don't wait for someone else.
- Be transparent - Things go wrong, find a solution
- Be Clear - Team cant read your mind.
- Listen
- Encourage people to elaborate
- what and why are important
- Help you to get more infomation

One-on-One meetings

Should your Engineering Lead be fired? - 2017
Who will learn from this? - 2017
What specific change do I want? - 2017
Introductory bullshit detection for non-technical managers - 2017
Lead the Way! A Practical Guide to Team Leadership - 2016
Some Advice On Becoming a Lead Developer - 2015
What’s the most critical leadership skill in video game development? - 2015
Lead Quick Start Guide - 2014
Book Excerpt: How Game Developers Choose Leaders - 2009