When expertise becomes a bottleneck and smart organizations fail to see clearly

Executive Summary

Annie Lu, a Harvard University graduate of 2022 and co-founder of Laminar (formerly H2Ok Innovations), is building self-optimizing manufacturing systems by integrating sensors, AI, and real-time data into a full-stack platform. Founded in 2021 by her and her brother, David Lu (the company’s CTO), the company has raised $12.4M and is already deployed across global manufacturing environments. It works with major enterprises such as AB InBev, Coca-Cola, Unilever, and Danone, delivering real-time optimization at scale. In conversation, what emerged was not just the technology, but a distinct way of thinking: a refusal to accept fragmented approaches, a deep reliance on first-principles reasoning, and an emphasis on understanding reality on the factory floor—highlighting how expertise, silos, and distance from lived experience often prevent organizations from seeing the problem clearly in the first place.

The Limits of Expertise

Early in their journey, Annie Lu and her team presented their approach to a large, established industry player. In the room were senior experts—individuals who had spent decades studying and operating within the system, some with over 40 years of experience.

Their response was immediate and unequivocal: what Laminar was attempting was impossible.

The conclusion was not casual. It was grounded in deep expertise, accumulated knowledge, and long-standing assumptions about how the system functioned. From their perspective, the boundaries of what could be achieved were already well understood.

Annie and her team saw it differently.

Not because they possessed more information, but because they were not constrained by the same models. As she later reflected, “ the more you know, the more cemented what you think is impossible becomes.” Where the experts saw constraints, her team saw assumptions—many of which had never been re-examined.

They did not attempt to argue the point. Instead, they focused on building and testing their approach, working through the problem from first principles and validating it in real-world conditions.

Over time, the results became evident. What had been dismissed as infeasible began to demonstrate measurable outcomes. The same organizations that had initially rejected the idea started to re-engage.

Nothing fundamental about the system had changed. What changed was the frame through which it was understood.

The episode illustrates a recurring pattern. Expertise does not merely inform judgment; it shapes the boundaries of what is considered possible. When those boundaries go unchallenged, they become constraints—not of reality, but of perception.

Highly capable organizations—staffed with experienced leaders, supported by data, and guided by proven practices—routinely make fundamental errors. These are not execution failures. They are failures of perception.

Organizations do not act on reality. They act on their interpretation of reality.

Over time, this interpretation becomes increasingly structured. Experience accumulates, models are refined, and best practices are institutionalized. What begins as insight gradually hardens into an assumption. As one founder observed, “the more you know, the more cemented what you think is impossible becomes.” Expertise, which should expand perspective, often narrows it.

At the same time, organizations fragment their understanding of the system. Functions optimize independently—technology improves, processes are refined, metrics are met. Yet integration is missing. “Sensor companies build sensors, software companies build software—but no one connects the system.” The result is progress in parts, without progress in the whole. The system improves on paper, but not in reality.

Compounding this is distance. Leaders increasingly rely on abstractions—dashboards, reports, aggregated data. These representations are necessary, but incomplete. The lived experience of those closest to the system is filtered out. When that layer is missing, what appears to be an efficiency problem is often something else entirely. In one instance, a factory manager remarked, “No one has ever cared this much about what I had to say.” The observation reflects not sentiment, but absence—an absence of true understanding.

What emerges is a consistent pattern. Knowledge creates certainty. Structure creates fragmentation. Distance creates distortion. Together, they produce organizations that are confident, capable—and misaligned with reality.

The solution is not more information. It is perspective-building.

Perspective building is the deliberate discipline of expanding how reality is seen before acting on it. It requires questioning assumptions at their root—“why does something work the way it does?”—rather than optimizing within inherited models. It requires direct engagement with the system as it operates, not just as it is measured. It requires integrating across domains, ensuring that improvements connect into a coherent whole.

Above all, it requires tolerance for discomfort. To build perspective is to confront uncertainty, to accept that what appears obvious may be incomplete, and to remain in that ambiguity longer than is comfortable. Most organizations resolve this tension too quickly, defaulting to familiar interpretations. In doing so, they preserve alignment at the cost of accuracy.

Those who see differently tend to operate at the edges. They are less constrained by established models, less invested in preserving them, and more willing to question them. As a result, they expand the frame of the problem itself. Outlier outcomes are not produced by better execution alone, but by different perspectives at the outset.

For leaders, the implication is direct. The primary constraint is not capability. It is the ability to see clearly.

Perspective building, therefore, is not a soft skill or an abstract ideal. It is a strategic discipline. Without it, organizations risk becoming highly effective at improving what does not matter. With it, they can align action with reality.

Clarity is not a function of intelligence.
It is a function of discipline.