The classic example is that of a combustion engine. Historically an engine was not designed, but “grown” ie iterated upon through trial and error. The heat transfer characteristics and thermodynamics were (are?) too complex to model, so engineers started out with a basic concept and iterated until they got the desired results.
I believe organizations work the same way. Instead of designing an organization from the ground up (clean sheet), most organizations actually start out organically and roles either expand or contract depending on needs and goals. There’s typically a lot of trial and error because it’s impossible to account for every variable that might affect the outcome. A heavily designed organization is liable to be very rigid, so the pragmatic path is align on shared principles and let each part of the organization organically grow according to its needs and goals.
Grown things can be designed. Designed things can be grown. Designed things doesn't always have to be grown. And lastly, Grown things doens't have to be designed.
All this sounds like Deepak Chopra's lectures.
I agree that design and grown are not mutually exclusive but I merely sought to demonstrate that they are different things.
Still your language is imprecise. Can you give examples?
> authoritative, non-iterative mega-deployment
Like what? Who designs a team like this? What are some concrete examples?
We develop everything from fighter jets to fiscal policy through "designed" organizations.