Two myths circulate wherever families do business together, and they are opposites, which is how you know at least one of them must be wrong. The first myth says love is enough: we are a close...
Two myths circulate wherever families do business together, and they are opposites, which is how you know at least one of them must be wrong. The first myth says love is enough: we are a close family, we pray together, we would never cheat each other, and so the business will be fine. The second myth says systems are enough: get the accounts audited, write the contracts, professionalize everything, and it will not matter that two brothers have not exchanged a warm word since their father's funeral. Both myths are comfortable, because each one lets a family work on the problem it prefers and ignore the one it fears.
Eric G. Flamholtz and Yvonne Randle spent more than thirty-five years inside family businesses as consultants, and their book Building Family Business Champions exists, in large part, to break both myths at once. Their central claim fits in a single formula, which they draw as Figure 1.1 on nearly the first page: degree of organizational development plus degree of family functionality equals degree of family business success. Two factors. Not one. A business needs real infrastructure, the systems and structure and processes that let it operate at its size, and it needs a functional family, one whose members can work together without turning the company into a battlefield. The book's whole argument is that these two things are independent. You can have either one without the other, and families constantly do. Which means love is not enough, and systems are not enough, and the family that believes either myth is flying with one instrument reading zero and its eyes on the other.
Cross the two factors and you get a two-by-two grid, the kind consultants love, except this one earns its keep. Strong family, strong infrastructure: the authors call these superstars. Strong family, weak infrastructure: high-potentials. Weak family, strong infrastructure: feuding families. Weak on both: sinking ships. The names are blunt on purpose. A family that can say out loud "we are a high-potential" or even "we are drifting toward feuding family" has language for its condition that carries no accusation against any single person, and that alone can lower the temperature of a hard conversation by several degrees.
What each type must do differs completely. Superstars have to build systems to keep doing what already works and adapt it for the next generation. High-potentials have to build the infrastructure their goodwill has been substituting for. Feuding families have to contain the family's damage to a machine that otherwise runs well. Sinking ships have to do everything at once, which is why, in the authors' experience, most of them are eventually sold or fail.
Two of the book's cases put flesh on the grim half of the grid, and a note of honesty first: the authors state plainly that their dysfunction cases are real but disguised, with names, industries, and details changed. Treat them as patterns from a consulting practice, not as citable facts about named companies. In one feuding family, which the authors wryly label "Battling Brothers, Inc.," a family board removed the eldest son as CEO for poor performance and installed his younger brother, who then did everything right: better operational systems, size-appropriate management systems, a formal approach to culture. And the older brother, still on the leadership team, periodically undermined all of it. The company had bought the machine and the family kept pouring sand in it.
The sinking ship case is darker and stranger. A talented founder built a food-processing company whose products sold so well that money masked everything. Relatives accumulated: mother, siblings, and a father who, in a consulting meeting, apparently worried about his meal ticket, threatened to "punch out" one of the authors for the offense of trying to help his son manage better. The author offered to punch back and sue; the founder watched the exchange with a bemused look, as if this were normal, because in that family it was. The authors' verdict is the quiet kind of devastating: despite a product good enough to carry it to roughly one hundred fifty million dollars in revenue, the firm's internal strife capped it there, and it was ultimately sold. The market kept saying yes. The family said no until the family won.
How common is all this? The authors estimate that "more than 50 percent of family businesses are dysfunctional in some way." Honesty requires a flag here: that number is Flamholtz and Randle's own estimate from their decades of consulting, not an independent academic finding, and consultants, by definition, meet a skewed sample of businesses, since healthy ones call less often. But even discounted, the direction of the claim survives. Dysfunction is not the rare disaster that happens to other families. It is roughly a coin flip, and the coin includes yours.
If the grid stopped there it would be a sorting machine, and sorting machines breed fatalism. The book's most valuable sentence cuts the other way: "superstar family businesses do not start out that way. They typically begin as 'high-potentials'" and become superstars by building the organizational capability their size demands.
Their prime exhibit is Bell-Carter Foods, the century-old California olive company that anchors the whole book. "Bell-Carter was a high-potential for the first eighty years of its operation," the authors write. Eighty years. For eight decades, what carried the company was not infrastructure but the family itself: openness to new ideas, willingness to work problems together, the absence of internal warfare. The authors describe exactly what a functional family buys you: "A functional family does not waste time and energy on intrafamily battles; rather, the focus is on getting things done and solving the problems of the business." That focus compensated for underdeveloped systems for three generations, until the 1992 acquisition of the Lindsay brand nearly doubled revenue in a year and the family, to its lasting credit, recognized that goodwill had reached the edge of what it could carry. They spent the next several years deliberately building the systems of a superstar, and the fourth generation now runs the result.
Read the two halves of that story together and the myth-breaking becomes precise. The family's functionality was real wealth: it kept a under-systematized company alive and growing for eighty years, which no org chart could have done alone. And it was insufficient: past a certain size, the most loving family in California still needed formal planning, defined roles, and real performance management. Love bought time. Only structure could buy scale.
There is a mirror lesson in the other direction, and the authors state it as one of their closing seven lessons: of the two deficits, low family functionality is the more dangerous, because "it is much easier to develop a strong organizational infrastructure than it is to 'fix' family functionality problems." Systems can be bought, hired, and installed. A brother's resentment cannot.
Now the translation, because this typology needs one. Every diagnostic in the book assumes a Western-style formal company: incorporated, with shares, a board, written roles, and revenue visible in audited accounts. The authors' scoring questionnaires ask about planning processes and performance management systems. None of it contemplates the form in which much of the world's family enterprise actually exists: unregistered or loosely registered, extended-family in structure, with ownership that lives in understanding rather than certificates, and with obligations running to cousins and in-laws the org chart will never show. A business like that can be deep into feuding-family territory with no board minutes to prove it.
So here is the grid's spirit, rebuilt as questions any family can ask at any scale, formal or informal. For organizational development, ask: does the business run for a month if the founder is sick? Can anyone state, from records rather than memory, what came in and went out last month? Does each person working in the business know, and agree on, what their job is? For family functionality, ask: when family members disagree about the business, does the disagreement get resolved, or stored? Are family members held to the same standard as anyone else who works there, or does blood buy immunity? When did the family last change its mind about something in the business because a younger or quieter member was right?
Mostly yes on the first three and mostly no on the second three: feuding family, whatever your paperwork says. The reverse: high-potential, and Bell-Carter's eighty years say that is a fine place to be, provided you know you are there and start building before growth forces you. Honest yeses across all six describe a superstar in the only sense that matters, even if the whole enterprise fits in two market stalls. The revenue thresholds were American. The two questions underneath them, does the machine work and does the family work, have no nationality.
Here is where we go a step further than the book. Flamholtz and Randle wrote for CEOs and their consultants, and their questionnaires are scored by leadership teams. But the whole point of the two-factor formula is that half of it, family functionality, cannot be assessed by the founder alone, because the founder is inside it. A patriarch who scores his own family's functionality is grading his own exam. The elders may believe the family is at peace when the peace is actually silence; the silence of adult children who have concluded that disagreement is pointless is not functionality, it is a feud on a delay timer.
So the naming has to be done together, and it has to be safe. Put the grid in front of the family, define the four types in plain language, and let each adult, including the ones who do not work in the business, privately write down which square they believe the family occupies. Then compare. The gap between the founder's answer and everyone else's is itself the most important data point the exercise produces. A family that lands in different squares is not failing the exercise; it is finally seeing itself.
This is standing work for a family council, the regular, structured meeting where the family governs its shared affairs, and the Family Council module in LegacyPot is built to hold exactly this: put the four-type question on the agenda once a year, record where each member placed the family, and track whether the answers converge over time. A family that can watch itself move on that grid, year over year, has already built the willingness to learn and change that the authors count among the six pillars of functionality.
Here is the one thing to do this month. Call the family together, the working members and the watching ones, and put the four names on the table: superstar, high-potential, feuding family, sinking ship. Explain the two factors honestly, that the machine and the family are separate things, that either can be strong without the other, and that more than half of family businesses, by the estimate of two people who spent thirty-five years looking, are dysfunctional somewhere. Then ask everyone to place the family on the grid, in writing, before anyone speaks.
If the answers agree and the square is a good one, you have something rarer than revenue, and your work is to build systems worthy of it before growth arrives to test you. If the answers disagree, or the square is a hard one, you have not been condemned; the authors are explicit that where a company stands now "is not a verdict, but an indicator," and every case of movement in the book, including the eighty-year high-potential that became a champion, started with a family willing to say the true name of its square out loud. The businesses that sank were not the ones with the worst squares. They were the ones that never looked.