The internet is increasingly optimised for imitation. Algorithms surface the highest-performing work, designers save it as reference, and AI models ingest it as training data. The output is then fed back into the same system again and again. Over time, the loop becomes self-reinforcing. What begins as inspiration gradually becomes homogenisation.
This is particularly visible in software. Entire categories have fallen into the habit of eating their own kind. On the surface, this seems entirely logical, and to an extent, it is. Your competitors understand the market, the users, and the expectations better than anyone else. Ignoring them would be foolish. The problem is that everyone else is doing the same thing. Entire industries consume the same references and follow the same design trends, benchmarking themselves against one another. Everyone attempts to differentiate while drawing from an increasingly narrow pool of inputs. The result is categories that increasingly resemble themselves.
Perhaps the greatest irony is that the signals used to communicate innovation often do the inverse. This happens when software companies assume the logic governing business strategy should also govern design. If a company operates in a highly specialised market, its visual expression should be equally specialised. In that case, the category becomes both the problem and the reference point for solving it.
The Misapplication of Logic
Business strategy and design do not operate under the same rules. A legal platform needs to understand legal workflows, regulations, and customer expectations whereas design communicates through association; it does not need to mirror a category to communicate its values. A cybersecurity company may need to understand digital threats, but it does not necessarily need to present itself through hooded hackers, glowing shields, and science-fiction interfaces. These visual tropes have become so commonplace that they barely communicate anything at all.
A stronger expression might be found elsewhere, whether that is architecture, the courtroom, or perhaps an archive. None of these references are native to software, yet they communicate many of the same underlying ideas: trust, protection, control, permanence, and security.
This is where many software companies run their course. They assume that because the business problem is technical, the visual expression must be technical, too. The strongest brands often do the opposite. They solve highly specific problems while borrowing visual language from entirely different domains. Architecture, publishing, hospitality, museums, academia, luxury, and industrial design all contain insights that software categories often lack.
The Power of Implicit Associations
The power of these references lies partly in their ambiguity. A courthouse is not cybersecurity, yet it carries meanings that feel deeply relevant to the problem being solved. Unlike literal references, which communicate a single idea directly, indirect references create a wider field of view. They invite interpretation. They feel richer, more cultural, and often more memorable precisely because they are not trying so hard to explain themselves.
This is why the most distinctive visual systems are rarely the most explicit. The strongest brands often communicate through implication rather than explication. They allow audiences to arrive at conclusions themselves, creating a stronger emotional connection than any literal visual shorthand ever could. As software categories mature, the most distinctive companies are rarely those that most closely resemble their competitors. They are the ones brave enough to look further afield.
What causes visual homogenisation in software?
Homogenisation happens because design algorithms, shared reference pools, and competitive benchmarking force companies to look at the same inputs, leading everyone to replicate the exact same visual trends.
Why should design look outside its own industry?
Looking outside your immediate category allows a brand to borrow fresh visual languages, like architecture or publishing, to communicate core traits like trust and security without using tired industry tropes.
What is the difference between literal and indirect references?
Literal references mimic the industry directly (e.g., hacker imagery for security), which feels uninspired. Indirect references use associations (e.g., an archive or courtroom) to invite deeper user interpretation and memory.
Why do explicit visual systems fail to create connection?
Explicit visuals try too hard to explain themselves and leave no room for the imagination. Distinctive brands use implication, allowing the audience to draw their own conclusions and form stronger bonds.
How can a technical product build a unique identity?
By solving highly specific, technical business problems while intentionally borrowing its visual storytelling, textures, and aesthetic rules from entirely different, non-software domains.