4 ms·
Everything he said resonates with me. Here's the magic sauce that nobody talks about though: Having one magic document that explains everything isn't good enoug
by throwawaaarrgh 4y ago
Everything he said resonates with me. Here's the magic sauce that nobody talks about though: Having one magic document that explains everything isn't good enough. Everyone "should" this, "should" that, isn't good enough.
For this stuff to work well, you need real leadership. Leadership should not build consensus, take polls, or let structure grow slowly and organically. You know what structures grow organically? Mold. Know what doesn't? Steel. Don't grow mold; build steel. Use the precise amount of material, at the right temperature and pressure, follow the right workflow, and inspect the result, then ship it with confidence. Don't hope it gets done; ensure it.
Leadership needs to force everyone to use the one magic doc, to follow the one magic process, and take training to be able to immediately and effectively work with them, without wandering around wondering how to do what's expected of them. Otherwise your teams/org will forever be slow, inconsistent, and buggy. Systems are a result of humans doing work. The better organized the work, the better organized the system.
- taurath 4y agoExamples of this in practice? I've never seen a magic doc for a large org that changes strategy frequently that is up to date for more than a year.
- froh 4y agothe doc should describe how you collaborate. and that shouldn't change direction frequently. systems engineering is much less about the deliverables than about how you collaborate to build them, how you ensure consistency, how you walk that talk.
- throwawaaarrgh 4y agoAnd one great public example is The GitLab Handbook
- Kinrany 4y agoYou can't force people to update the doc when it gets out of date, can you? There are limits to what can realistically be done through coercion.
- deleted 4y ago[deleted]