I don't think the shape of the org chart actually matters all that much. It's the channels of communication, which way information flows, and how much autonomy the leaf nodes have that actually matter.

Case in point, Amazon vs Netflix. At Amazon, every decision requires approval of someone higher. Engineers can come up with ideas, but they have to write it up, get it approved, and then get budget assigned for that particular project from management. Even Principle Engineers have to get approvals for their own ideas and projects. And if they have ideas for new company goals, they have to send that up the chain through their management to the leaders (maybe skipping a level or two).

Netflix on the other hand has the same org structure as Amazon, but operates completely differently. Management provides context, not approvals. They say, "these are the goals we are trying to achieve". Then they leave it up to the engineers to implement it however they think is best. And if they need more budget, usually the way it works is that engineers spend the money first and if it's too much someone asks them to find ways to reduce it. And if the engineers have ideas for better company goals, they send that directly to upper management. At Netflix you never have to go through a chain of management to get things done.