Founder's Mentality Blog
Embrace Conflict
Embrace Conflict
Conflict is not the problem.
- Min. Lesezeit
- Summarize with Generative AI
Founder's Mentality Blog
Conflict is not the problem.
Companies with a Founder’s Mentality® don’t just accept conflict, they revel in it.
One key goal of good organizational design is to create conflict. At its simplest, customers benefit when companies are ruthlessly focused on delivering to them two kinds of benefits:
Unless you’re a big technology company with lots of fancy algorithms, bringing consumers the right balance of the similar and the different is a hard slog. Many companies have embraced the matrix organizational structure, in part to ensure that portions of the organization are looking for the benefits of the similar and portions are searching for the benefits of the different. Not surprising, that creates conflict.
To illustrate a typical debate in big companies, let’s revisit the tomato soup example:
The winner? The Malaysian consumers. They will either get perfectly spicy soup tailored for them or something close enough, but a bit cheaper. They will either get the poodle off the label, so they don’t think of lubricants when they eat soup, or they will enjoy the benefits of a multinational poodle telling them something about the less expensive soup.
Conflict in an organization is a good thing. Done right, it creates the debates necessary to ensure that customers benefit from the optimal blend of the different and the similar. Companies with a Founder’s Mentality understand this. Their bias for action and their obsession with the front line ensure that the conflict doesn’t bog down the organization.
Incumbents and struggling bureaucracies, however, learn to hate conflict. And that is ironic, given their organizations are often paralyzed by it.
This is how conflict goes wrong:
In short, the surface of the water appears calm at these big organizations, but schools of piranhas are warring at the deepest levels. To make conflict productive, it must be encouraged at the right times and places—and then resolved, before it goes any further.
One CEO of a Turkish firm told his story: “We love conflict. We understand its role. We have a Monday meeting each week with our full leadership team, and I expect major fights.”
Recently, the firm discovered that some of its products had been poorly packaged in colors that did not match its specifications. “We were stuck in a situation where we either pulled the stock because it didn’t fit our brand standards or let it pass to avoid stock-outs,” the CEO said. “This was a big issue. We were either going to disappoint our consumers or disappoint our channel partners.”
As the discussion progressed, though, one thing made the CEO angrier than the packaging: an overly acquiescent executive. “Our head of marketing was being way too reasonable. He understood the consequences of stock-outs and was quickly trying to explain that the color issue wasn’t that bad,” the CEO recounted. “I was furious. During a break, I told him that he was not doing his job. If he wasn’t going to stand for the consumer in that meeting, then I didn’t understand why he came.”
In this CEO’s view, a Monday morning meeting without heated debate—and resolution—is a failed effort. “Ultimately we execute our decisions as an integrated team,” he said. “But when we’re taking these decisions, I demand conflict. Otherwise, we’re letting our customers down.”
Conflict is not the problem. If there is a problem, it always lies in the speed and spirit in which conflicts are resolved.