Skip to content

Comment on One common behavior seen in “mature” software engineersparent

Comments

One successful way I've seen this down is to proactively give people ownership of sub-projects with collaboration, or leadership scope N+1. It is explicitly acknowledged (so no shadow work that your team is covering to support) and acts as a way to gauge maturity, while limiting risk.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.