Discussion about this post

User's avatar
Canonical Organizational Model's avatar

I think your distinction between making a decision and making it portable is particularly important.

I wonder whether part of the exhaustion also comes from the coordination architecture through which decisions must travel. Even a well-reasoned, clearly communicated decision can lose its intent as it crosses organizational boundaries, responsibilities, and competing priorities.

Perhaps the challenge extends beyond making decisions portable to making the organization capable of carrying them through to their intended effect.

That raises another question: how do we know when a decision has actually achieved what it was meant to accomplish, rather than simply being implemented?

Marc Aden Gray's avatar

I'm brought in as a freelancer to many companies to work on leadership. Admittedly, my field of endeavour isn't strategy/business development/change management, wherein decision-making architectures and strategies are in play.

However, what you raise - the possibility that positive outcomes on all levels are directly affected by the number of decisions we're forced to make - felt profound. I never hear this spoken about when leaders tell me about their companies' problems. Yes, they speak of flattening the hierarchy or being faster, but that's usually based in operations and not in an actual PHILOSOPHY relate to the COST of a decision.

Very interesting Fiona. And I sense it IS related to my field of relational skill, self-development and how leaders respond to challenge and opportunity. Thank you for the stimulation and insight.

4 more comments...

No posts

Ready for more?