Always be leaving

Photo by Mantas Hesthaven on Unsplash
Photo by Nathanaël Desmeules on Unsplash
  • Create or update documentation: every time you create, modify or fix something try to add information at some place where you or any other person in the future could go to find answers. Create a new service?, add its related doc; update some process?, find the documentation and update with the changes; follow some outdated guide? fix that and let it be better than you found it.
  • Always share knowledge: doing a code review and saw something about you have more information?, share the link to know more; have you learned something new that could be useful for your coworkers? share the links or give them a talk.
  • Write code for others: when writing code think about if other people in the team could be able to understand easily and try to make it for them (and for your future you)
  • Work to solve the problem not the concrete case: someone asks you about something you know? instead of just tell that person, create a documentation, share with that person, get feedback en improve to ensure anyone at anytime could get the same information with the same quality (no matter you are available or not)
Photo by Arthur Edelmans on Unsplash
  • Dividing problems and adjustment: to solve a complex problem it’s always easier to break it into smaller ones and let people handle each one of them. The issue here is to be able to create a culture that knows when a problem changes and how to adapt to it. It should be a mix between creating a team which follows its procedures but at the same time it’s flexible enough to adapt to situations.
  • Delegation: creating a strong team and future leaders is key for any team. Let people handle problems, take decisions and assume responsibilities is the key. As leaders most of the time we may think that if something is “important” it should be done by us, but instead of that what we should do is always question us: “am I the only person who can handle this?”. If it’s always us who handle those kinds of stuff, we are never going to create a “self-leading team”. Not be the SinglePointOfFailure of your team!.
  • Adjusting and iterating: give advice, let people take decisions and evaluate results. Maybe the % of freedom starts at 50%, at each iteration drops the number and gives even more autonomy.
  • Give the team problems not tasks: for a full autonomy, ownership and context are required if we only assign tasks or features we are not letting the team see the big picture. To create a self-leading team, they need to have all the context and be owners of problems so they can find their own solutions.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Ángel Cereijo

Ángel Cereijo

85 Followers

Software engineer with 15 year of experience. Lately focused in Node.js ecosystem and good practices.