Redefining Design

My first months at Diviniti were spent creating visuals. Not websites. Not products. Just images. I became obsessed with details that most people never consciously notice. Light. Materials. Texture. Composition.

This was before Ai became main stream, so every element, every light source had to be put in by hand. The surprising part was how dramatically those details changed the way a product was perceived.

The product remained the same.

Only the presentation changed.

That was my first lesson.

Perception is designed.

As my work expanded from visuals to ecommerce, I began seeing a different side of design. A beautiful interface could attract attention.

It couldn't create trust.

Customers needed context. They needed reassurance. They needed enough information to feel confident in a decision.

The more I worked on websites and customer journeys, the more obvious this became. People weren't evaluating pixels. They were evaluating risk.

That changed the way I thought about design. Design wasn't just shaping perception anymore.

It was helping people make decisions

My introduction to AI began with a simple question.

What happens when software can participate in the customer experience?

I started experimenting with chatbots, automation, and AI-assisted workflows. Some worked. Some didn't.

As I spent more time inside the business, I found myself looking beyond products and screens.

I began understanding how orders were fulfilled, how products were manufactured, how customer support operated, and how decisions moved through the company. What surprised me was how connected everything was.

A customer never experiences marketing, sales, operations, and support as separate functions.

They experience one company.

Every interaction is shaped by systems most customers never see. The further I looked, the harder it became to separate design from the organization itself.

The biggest shift in my thinking didn't come from a website, a brand, or an AI tool. It came from product data.

As Diviniti began preparing for AI-powered commerce, the conversation moved away from interfaces and towards information. Product structures, databases, taxonomy, SKU architecture, and a single source of truth became the focus.

At first, none of it felt like design. There were no screens to improve and no visuals to refine. Yet many of the problems we were trying to solve originated here.

Products that were difficult to find. Information that was inconsistent. Systems that couldn't scale. I realized that some of the most important design decisions never appear on a screen. They exist in the way information is organized.

By this point, the boundaries between design, technology, operations, and information had started to blur. The challenge was no longer creating a better page or a better flow. It was creating systems that could support many experiences at once. A product database could power a website.

The same information could feed marketplaces, internal tools, customer support, and increasingly, AI systems.

The more connected these systems became, the less important individual interfaces felt. What mattered was the structure beneath them.

The interface was only one expression of a much larger system.

That was the final shift.

Design was no longer about creating artifacts.

It was about creating foundations that could scale.

When I joined Diviniti, I saw design as the act of creating.

Creating visuals.

Creating interfaces.

Creating experiences.

Over time, that definition became difficult to sustain.

The problems that shaped my thinking were rarely visual.