i just wanted to show my design of them:3 SHGSHE
seen from China
seen from United States

seen from T1

seen from United States

seen from T1

seen from United States
seen from United States
seen from United Kingdom
seen from United Kingdom

seen from Colombia
seen from Poland
seen from China

seen from T1

seen from United Kingdom
seen from United States
seen from China
seen from United States

seen from United Kingdom

seen from T1

seen from United States
i just wanted to show my design of them:3 SHGSHE
some kind of design of fem argbur!!... i just like it a lot this outfit for her...<3
The job of leadership isn't to "reduce complexity" in the work itself but to create an environment where people can work effectively with complexity
TBM 321: "Reducing Complexity" - by John Cutler
Nan Yu, Head of Product at Linear, has advised dozens of startups of all stages and sizes. He unpacks why founders should be suspicious of symmetry in their team structure, and offers a three-part framework on how to optimize for an “heirloom tomato” org chart.
An interesting take on org design: build lopsided org charts. Start with one monolithic team that is “the product” and only cleave off secondary teams when needed, keeping them small by comparison.
A great collection of best practices, all of them worth your consideration. “An ideal organization has fractal leadership: Decentralized decision-making on local teams. And centralized goal setting, context-setting, and coordination.”
Software development slows down over time. I wrote a whole book to help leaders reverse this slowdown and the central point of the book is a process any engineering leader can apply. I call this process Technical Coherence and you can mostly achieve it in a single meeting with your leaders. You can implement it in your org gradually or all at once. The central idea is this: We identify the necessary user experience domains for our products We identify the shared product domains that underpin multiple user experience domains We organize engineering into three layers, the top two correspond to the above domains and the third provides infrastructure.
I’m a sucker for organizational design theory. I like the model, and I also wonder how it best maps to a smaller organization, where teams will own multiple domains.
I initially gave this talk at Lead Agile Brighton in October 2022, then updated and refined the slide deck for Agile Manchester in May 2023, so I’ve updated this post too. I've noticed an increasingly worrying trend in the industry of focus on specialisms at the expense of collaboration, shared r
I’ve noticed an increasingly worrying trend in the industry of focus on specialisms at the expense of collaboration, shared responsibility and valuable outcomes.
Professional protectionism is a term I borrowed from healthcare. When I read about it, I recognised the behaviour; it happens when people feel overprotective over their role at the expense of collaboration and sharing with others. These anti-patterns serve to reinforce this behaviour.
“The introduction of new roles or new ways of working can be perceived as a challenge or threat to pre-existing professional identities.”
https://www.aomrc.org.uk/wp-content/uploads/2020/05/Developing_professional_identity_in_multi-professional_teams_0520.pdf
For example, if a doctor regards a particular medical test as a core part of their professional role, then ceding this task to another person can feel like a loss of status, authority, responsibility or experience. This is particularly true if the power and organisational structures reinforce this behaviour.
In order to be truly multidisciplinary, we need to recognise that disciplines and specialisms are not the same as roles. People’s roles overlap; this is great and makes for far more collaborative teams working together towards a common goal.