Phil Le-Brun:

Rather than pretending you can craft the perfect organisation chart and operating model, I advocate starting with principles and tenets to guide your organisation. The former method is an overly logical and static approach to human issues, as I described in my first post on untangling your organisational hairball. Principles have (I hope) shifted from outdated concepts, such as spans of control, in search of elusive efficiencies to those better suited for an era where complexity, speed, and innovation define organisations. Previous blog posts give in-depth examples of principles and decision-making tenets. But remember, the most beautifully crafted principles in the world mean nothing unless a comprehensive understanding of them cascades throughout the organisation.

I was having an after-work chat with Simon a while ago. We were discussing how we can cultivate a more resilient culture at work, specifically enhancing the capacity of individuals to constructively handle feedback.

He mentioned that he’d been reading Thanks for the Feedback which emphasises that, contrary to popular advice, it’s better to focus on helping people get better at receiving feedback rather than giving it.

This reminded me of a design principle in software engineering called the “Robustness principle” or “Postel’s law”. This principle guides how software systems should be designed to communicate with each other.

It’s often summarised as: “Be conservative in what you send, be liberal in what you accept”.

It felt like when it came to feedback and people working better together we were talking about the same thing, i.e. Postel’s law for people.

This makes me wonder what other software design principles might be useful when applied to people.

A pretty good list.

Ryan Florence:

Rackt is a GitHub organization that was created to ensure critical open source projects in the React community receive long-term support and maintenance.

…

We believe these four principles will provide a strong ecosystem of our open source projects by ensuring projects have active and enthusiastic owners and contributors.