Chaordic Organization

Two failure modes, not one

Micky Malka received the principle from Dee Hock, the founder of Visa, over ten to twelve years of visits: "he is the believer that you should never over-organize. The best expression of humans is in the intersection between chaos and order. If you're too orderly, you don't innovate. If you're too chaotic, you don't communicate and you break."¹ The two failures are worth separating, since most organizational advice only names one. Too much order fixes the paths information can travel, so novel combinations stop happening even as the organization keeps functioning. Too much chaos does not just get messy, it breaks: coordination degrades until the organization cannot hold together at all. Hock's prescription is negative rather than an optimum to engineer: do not over-organize.

The generational extension

Malka argues that founders in their early twenties look at org charts "very differently": "I don't think the org-chart structure that we inherited and that we grew up with applies anymore." This is not a philosophy they adopted so much as a consequence of the technology they grew up inside: "these kids are doing a great job by pure nature of how they were trained and wired with this era of technology to be in the epicenter of chaordic."¹ He credits the same principle for how he built Ribbit Capital and his earlier startups: no partner of record, group decisions, calendars and inboxes visible to everyone, deliberate over-communication in a small team, and an internal vocabulary, Jedis, Wookies, meetings called "tattooing", that carries culture where structure would otherwise have to.¹

Why it matters

The principle supplies a diagnostic rather than a target. Ask which failure the organization is currently producing, not innovating or not communicating, and move in the opposite direction, which is more usable than being told to find the right balance. The generational claim is the higher-stakes, testable part: if Malka is right, younger founders are not rejecting the org chart on principle, they are skipping it the way they skipped desktop software; if he is wrong, self-organization is simply what small companies look like before they scale, and they will rebuild hierarchy at the same headcount everyone else does.

Open question

Never over-organize is difficult to falsify without a measurable threshold, since every organization that failed can be read afterward as having gone too far one way. Malka's own account concedes that even David Senra, who has read Hock's Visa book twice, cannot fully reconstruct how it was operationalized at Visa's scale, and Ribbit itself is a team of roughly a dozen people, so full inbox transparency and group decision-making have not yet been tested against an organization anywhere near the size Visa reached. The generational claim also risks confusing stage with cohort: nearly any company of nine people looks self-organizing, whatever the founders' age.