> as well as good understanding at the bottom, and a critical mass of good alignment and competence throughout the middle layers. How do you hold the middle

> as well as good understanding at the bottom, and a critical mass of good alignment and competence throughout the middle layers. How do you hold the middle together? Especially under such turbulence? "Strong" leadership isn't enough. Reflective practice [0] is one way to build that. It's common in medical and some safety-critical civil/military spheres but strangely missing from many corporate structures. I talk about it here with regard to a more mature cybersecurity stance [1]. It intersects with Agile ideas but doesn't make much noise in software engineering project management as much as it should? Anyone have this in their org? [0] https://en.wikipedia.org/wiki/Reflective_practice https://en.wikipedia.org/wiki/Reflective_practice [1] https://cybershow.uk/blog/posts/reflective https://cybershow.uk/blog/posts/reflective