Whenever a new technology emerges, we tend to talk about it.
Its features.
What it lets you do.
How it works.
The possibilities it opens up.
It makes sense. Novelty grabs our attention.
But there’s a much more interesting moment in the life of any technology: the moment when we stop talking about it.
Not because it has ceased to be important, but precisely because it has become so seamlessly integrated into the way we work that we no longer need to constantly think about it.
We turn on a light without thinking about the electrical grid behind it. We use an elevator without wondering about all the systems that make it work. We make a video call without pausing to analyze the technologies that make it possible for the image and sound to reach the other end.
The technology is still there.
It has simply stopped demanding our attention.
This idea is not new. As early as the 1990s, Mark Weiser, one of the pioneers of ubiquitous computing at Xerox PARC, argued that good technology could become so seamlessly integrated into our environment that we would stop paying conscious attention to it. Later, together with John Seely Brown, he would develop the concept of “calm technology”: technology capable of integrating into our activities without constantly occupying the center of our attention.
Decades later, this line of thinking still holds a lot of weight.
Especially within organizations.
When Technology Becomes Part of the Job
Let’s think about any new business application.
During the first few weeks, it’s perfectly normal to hear questions like:
“Where do I log in?”
“How do I do this?”
“Where is it saved?”
“Which option should I select?”
“Do I have to do this here or in the other app?”
The tool takes up a significant portion of the user’s attention.
Over time, if it’s well-designed and integrated, those questions should gradually disappear.
The user stops thinking about the system and simply starts using it to get what they need.
And that shift is significant.
Because the goal of business technology shouldn’t be to get people to use technology. It should be to help them do their jobs better.
The difference may seem small, but it completely changes the way we approach a solution.
Complexity may lie behind it—not necessarily in front of it.
Enterprise technology environments are complex.
There are corporate systems, specialized applications, repositories, databases, integrations, security models, automations, business rules, services, and a multitude of components that must work together.
In many cases, that complexity is unavoidable.
What should not be inevitable is passing that complexity entirely on to the user.
A user may need to access information stored across multiple systems without necessarily needing to understand the underlying architecture.
They can participate in a process involving numerous validations, rules, and automations without having to manually execute each one.
They can access a document without necessarily knowing on which infrastructure it is stored.
They can work with information subject to permissions, access controls, or corporate policies without having to personally manage each of those mechanisms.
Architecture can be complex and, at the same time, offer a simple experience.
In fact, that is probably one of the major challenges facing any mature technological environment.
More tools don’t always mean a better experience
For years, digital transformation has led organizations to adopt new solutions.
Each one addresses a specific need.
One for communication.
Another for managing specific tasks.
Another for storing information.
Another for approval.
Another for analysis.
Another for automation.
The problem arises when we look at the whole from the user’s perspective.
Individually, they may all be good tools, yet the overall experience can be complicated.
The user doesn’t necessarily perceive a technological architecture.
They perceive that to perform a task, they have to open three applications.
That one piece of information is in one place and another related piece is in another.
That they have to copy data from one system to enter it into the next.
Or that they must remember which tool corresponds to each part of their work.
At that point, the technology becomes too visible.
And that visibility comes at a cost that isn’t always reflected in technology projects: friction.
Integration also involves reducing friction
When we talk about technology integration, we usually do so from a technical perspective.
APIs.
Connectors.
Interoperability.
Information synchronization.
But there’s another way to understand integration: from the user’s perspective.
Two systems can be technically connected yet still force the user to fully understand where one begins and the other ends.
And the opposite can also be true: behind a seemingly simple experience, there may be different platforms working together.
From this perspective, good integration isn’t just about getting systems to exchange information.
It also involves ensuring that this exchange truly makes people’s work easier.
The less users have to worry about where the information is stored, which system performs a particular action, or what technology is behind it, the closer we’ll be to achieving that goal.
Invisible doesn’t mean simple
There is also an interesting paradox.
Often, the simpler a technology seems to the user, the more work goes into making it that way.
Making the complex simple requires making many decisions.
Deciding what the user should see and what they shouldn’t.
What can be automated.
What information they need at any given moment.
How exceptions are handled.
How different systems are integrated.
How security controls are maintained.
How to avoid unnecessary steps without losing control or traceability.
That’s why making technology invisible doesn’t mean eliminating its technical complexity.
It means managing that complexity so that it does not unnecessarily fall on people.
And what about artificial intelligence?
The advent of artificial intelligence brings this issue back to the forefront.
We are living in an era in which AI is, inevitably, taking center stage.
We’re talking about models, assistants, agents, automation, and new ways of interacting with information.
It makes sense: we’re still in the discovery and adoption phase.
But perhaps a sign of maturity will come precisely when we stop constantly thinking that we are “using AI.”
When we simply ask a question.
When a task is automated at just the right moment.
When we receive the information we need right within the tool we’re already working in.
When certain actions can be carried out without requiring us to understand all the systems involved behind the scenes.
In short, when artificial intelligence stops being a feature we have to go out of our way to find and starts becoming a natural part of certain processes.
The technology behind it can be highly sophisticated.
For the user, it will simply have made their job easier.
Users shouldn’t always have to adapt to technology
For a long time, we’ve assumed that introducing a new technology inevitably means that people have to learn how to use it.
And, of course, any change requires some learning.
But we can also turn the question around:
To what extent should technology adapt to the way people work?
It doesn’t mean sticking with inefficient processes or rejecting new ways of working.
It means designing by first considering what the user needs to achieve, and then what technology makes that possible.
It’s an idea we also find in Don Norman’s work on human-centered design: as technology matures, factors such as ease of use and user experience become increasingly important. Technology ceases to be the end goal and becomes the means to an end.
A sign of technological maturity
Perhaps that is why we should not measure the success of a technology solely by the number of features it includes.
We could also ask ourselves other questions.
How many steps have we eliminated?
How many unnecessary decisions have we spared the user?
How many times do they have to switch apps to complete a task?
How much do they need to know about the systems behind the scenes?
Can they find the information when they need it?
Does technology interrupt their work, or is it a natural part of it?
These questions are less eye-catching than talking about new features.
But they probably say much more about the true quality of a solution.
Because the best technology isn’t always the most visible.
Sometimes it’s the technology that’s always there, enabling processes, information, and people to work together seamlessly, without demanding to be the center of attention all the time.
And perhaps it is precisely then—when we stop thinking about it—that we can say technology is truly doing its job well.
