5 ms·
As a manager myself, I'm going to post this evergreen I keep continuously revisiting every half a year. It's extremely concise while complete on every aspect I
by endymi0n 7y ago
As a manager myself, I'm going to post this evergreen I keep continuously revisiting every half a year. It's extremely concise while complete on every aspect I would have loved in a manager while being an employee. That's why it's my gold standard and the one thing I'm handing out to every new manager at our company.
https://www.defmacro.org/2014/10/03/engman.html https://www.defmacro.org/2014/10/03/engman.html
Relevant HN thread:
https://news.ycombinator.com/item?id=14381264 https://news.ycombinator.com/item?id=14381264
The one thing I'd add on top of it from my last 5 years in CTO experience is:
- Communicate context as high level and as complete as possible.
If you say "I want that button in red" when you really mean "I want to increase sign-ups on this landing page", then what you REALLY mean and want to communicate is that you want as many customers as possible to find your valuable product.
Letting the team jump in with own ideas, even if you think you already have the best solution will make them grow in responsibility, accountability and self-confidence.
Likewise, ideas like a company/team "Mission" and "Strategy" are 90% used in bullshit contexts, but articulated correctly and repetitively, they make sure people run into the right direction, even if you don't follow every of their moves.
- deleted 7y ago[deleted]
- Loughla 7y agoGenuinely thank you for that link.
- marapuru 7y ago> https://www.defmacro.org/2014/10/03/engman.html https://www.defmacro.org/2014/10/03/engman.html Great article, I can see why you revisit this frequently :)
- wool_gather 7y ago> Don’t > 7. Personally fix bugs and ship features. You have to write code to remain an effective tiebreaker... Should "write" be "read" here? I'm not sure I understand this point.
- kemitche 7y agoI read that bullet point as "Yes, you should still write code now and then, so that you're at least loosely familiar with the code base and challenges, but don't put yourself anywhere near the critical path for your product."
- C4stor 7y ago> 32. Have difficult conversations as soon as possible. Waiting will only make a bad situation worse. Gosh, that is so true and so hard at the same time.
- jppope 7y agoThe concept of "mission" purely exists so you can disagree constructively with management. That's why it's so powerful...