Peopleware
Management Best Practices: Situational Management 4 minutes read.
Simple yet powerful framework by Tomasz Tunguz. Use it as a tool to figure out the best approach regarding every employee in your team. I'd argue that for "High motivation, low skill", the best thing you can do is be empathic, teach them the tools, but do not hold their hands. Let them fail so they'll be able to understand the reasons behind your advices over time. Micro-management is a great way to achieve short-term productivity, but it's so easy to abuse (hence continuing to Micro-manage even if not needed anymore). In order to create long-lasting growth, you should develop their pattern-matching skills. Then, get out of the way while they experiment with it and share some feedback on it. Rinse and repeat.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Managing a Backlog 7 minutes read.
Managing a backlog is not only a "product job". The skills required to prioritize, communicate and connect to the business's KPIs are required for every leadership position in the company. We are not working in a void. Use this post as a way to figure out how to manage your own backlog. For example, if you manage engineers and running your own technical backlog, you can translate questions such as "will this make our product grow?" to "will this help us develop faster, with better quality?"
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
Distributed Team: Solving the Trouble With Timezones 5 minutes read.
Even if your team is not fully distributed, it often happens when development sits in one country while business and marketing in another. Tom Moor from Sqwiggle shares 5 easy tips to ease timezones-diff hell. What I loved most about this post is how practical Tom's advices are, on such a complicated subject.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.