Nicholas Mukhtar: ‘The System Is the Outcome’ and What It Means for Business Leaders
Four words sum up the argument Nicholas Mukhtar has carried from public health into corporate consulting: “The system is the outcome,” he wrote in a column tracing his career from Detroit nonprofit work to advising family offices and executives nationwide.
The phrase compresses a longer argument: results don’t come primarily from individual effort or talent, but from the structure surrounding that effort, whether the structure is a hospital referral network or a company’s approval process.
Mukhtar has applied a version of that same argument to regulatory complexity, arguing that friction inside a system, not the intentions of the people running it, determines who gets served and who gets left behind.
A Thesis Tested Against Real Numbers
Poor workplace communication alone costs U.S. businesses an estimated $1.2 trillion annually, according to research from Grammarly and The Harris Poll surveying more than 1,000 knowledge workers and business leaders. That figure, in Mukhtar’s framing, isn’t a talent problem spread across millions of individual employees; it’s a systems problem, repeated at scale.
Business leaders surveyed for that research estimated their teams lose nearly a full workday, 7.47 hours, to poor communication each week, a cost they put at roughly $12,506 per employee annually.
Mukhtar’s own regulatory work reflects the same thesis applied to a different setting. “I’m not anti-regulation. I’m pro-simplification,” he wrote, arguing that the goal isn’t fewer rules but a system built so the rules that exist don’t compound into something unworkable.
Why the Framing Changes the Fix
Treating a problem as systemic rather than personal changes where a leader looks for a solution. Instead of replacing the underperforming employee or the frustrated customer-service representative, the fix becomes redesigning the process that put them in a bad position to begin with.
A manager operating under the personal-blame framing keeps replacing people in the same role without ever asking why the role keeps failing. A systems-first manager asks what about the process, the incentives or the information flow made failure likely regardless of who filled the seat.
That’s a harder sell than firing someone, since it requires admitting the design, not just the person, was the problem. It’s also the fix Mukhtar says actually holds up over time.
That shift, small as it sounds, is the difference Mukhtar credits between organizations that solve a problem once and those that keep hiring their way around the same one.
