In an age of AI-enabled abundance, leaders must protect customers and their teams from unnecessary complexity
This article originally appeared in David Wilkes’s newsletter and has been adapted for Acquired Knowledge. Wilkes is the CEO of Celcat, a Volaris Group-owned business, and he frequently writes about design-led thinking for the AI-native business leader in Human + Machine | Design.
Much like the work of Danish architect and designer Arne Jacobsen, great systems are not defined by everything that they can produce but by what they intentionally leave out. Leaders of software businesses could do well by taking lessons from the design world.
In the world of software, the potential for a 50x increase in output, generated by the new age of agentic AI, creates a tension that is easy to underestimate. The system can produce far more than people can realistically absorb, interpret, or support. This tension becomes most visible at the customer interface, where all of that increased capability meets real human attention, judgment, and time.
What looks like progress at a system level can feel like overload at a human level. More features, more options, more interactions, more edge cases. Customers are presented with greater choice, and this might translate into less clarity. At the same time, frontline teams are expected to understand and support a much broader and more complex surface area. The result is predictable: customers feel overwhelmed, teams feel stretched, and experiences become inconsistent.
The constraint has not disappeared. It has simply moved. It now sits in the human capacity to make sense of what has been created.
The customer interface becomes a translation layer
Traditionally, people operating at the customer interface have treated it as a delivery function. Its role was to explain the product, support its use, and resolve issues as they arose. In a high-output environment, that definition becomes insufficient.
This interface now has to translate abundance into something usable. It must filter what matters, guide decisions, reduce unnecessary complexity, and maintain trust across every interaction, ultimately helping customers transform. This is not a marginal shift; it is a fundamental change in purpose.
If this layer is not designed deliberately, the organisation risks pushing complexity outward. The system may be powerful, but the experience becomes fragmented. What should feel enabling instead feels confusing.
Why customer intimacy becomes harder
There is a common assumption that more technology makes it easier to be customer-intimate. In one sense, that is true. Personalisation can now be delivered at scale, often automatically.
But intimacy is not the same as personalisation.
More data does not guarantee a better understanding. More options do not guarantee better decisions. More touchpoints do not guarantee stronger relationships. In fact, without structure, they tend to produce the opposite effect.
The risk is subtle but important. The organisation appears more responsive, yet feels less coherent. Customers receive tailored outputs, but lack confidence in what to choose or why it matters.
Scaling intimacy without breaking people
The instinctive response is to place more responsibility on frontline teams: more training, more information, more tools. In practice, this approach does not scale. It increases cognitive load without resolving the underlying issue.
A more effective approach is to design intimacy into the system itself.
This means giving teams clear decision frameworks rather than rigid scripts, so they can apply judgment consistently. It means using intelligent agents to guide customers through complexity, acting as an interface that simplifies rather than expands choice. It means actively reducing surface area by removing unnecessary options and designing default paths that make the right decision the easiest one.
It also requires continuity. Context must carry across interactions so that customers are not forced to repeat themselves, and teams are not starting from zero each time. The goal is not to increase effort, but to increase leverage.
The leadership implication
At a leadership level, this creates a clear opportunity and responsibility. Output can scale exponentially, but human attention cannot.
That means leaders must protect both the customer and the team from unnecessary complexity. This involves making deliberate choices about what reaches the interface, how it is presented, and how much variation is truly valuable.
Clarity becomes an act of discipline. Simplicity becomes a strategic decision. Trust becomes something that is designed, not assumed.
A lesson in designing systems from Arne Jacobsen
A leadership lesson for software business leaders in the age of AI can be taken from Arne Jacobsen, the Danish architect and designer. Although he worked in an era of expanding production capability, he consistently refused to expose users to every variation the system could produce.
Instead, he curated the experience carefully. His spaces felt calm rather than complex. His objects felt intentional rather than excessive. The system worked because it had been reduced to what mattered. The lesson is not just aesthetic. It is practical.
He designed for how people would experience the system, not for everything the system could theoretically produce.
In a 50x world, that distinction becomes critical.
