Search for digital experience and you will mostly find software. Platforms, suites, dashboards, scores. They are useful tools. But a tool is not an experience, in the same way a kitchen is not a meal.
A digital experience is what a person feels between arriving and leaving. Whether they understood. Whether they were respected. Whether they would come back. No platform owns that. It is designed, one decision at a time.
START WITH THE PERSON, NOT THE STACK
The usual order is backwards. A business buys a platform, then asks what to put on it. The better order begins earlier, with a plain question: who is arriving, from where, carrying what?
Someone opening a page on a phone, between two errands, in a second language, needs a different experience from someone reading at a desk with time to spare. Same business. Same product. Different conversation.
So the first job is observation. Where do people actually come from? What do they already believe? What were they doing a minute before? Software can count these moments. It cannot tell you what they mean.
DECIDE WHAT THE EXPERIENCE MUST DO
Every digital surface is asked to do too much. Inform, persuade, sell, support, entertain, collect data. When it tries to do everything, it does nothing well.
A useful experience has one main job and a few supporting ones. Help someone choose. Help someone trust. Help someone return. Name the job in a sentence, and every later decision — what goes first, what is removed, what waits — becomes easier to argue about.
DESIGN THE CONVERSATION, TURN BY TURN
Good conversations have turns. Someone speaks; someone answers; the next thing said depends on what was just heard.
Digital experience works the same way. The headline is the first turn. The visitor's scroll, tap or pause is their reply. The next section should answer what they are likely thinking now — not what the business wanted to say next.
This is why the order of a page matters more than its decoration. A beautiful page that answers questions in the wrong order feels like being talked at. A plain page that answers them in the right order feels like being understood.
REMOVE FRICTION THAT IS NOT DOING WORK
Some friction is useful. A pause before a big decision. A moment to read before agreeing. Most friction is not useful. Pop-ups before the first sentence. Forms that ask for things nobody needs. Menus that mirror the organisation chart instead of the visitor's question.
The test is simple. For every step, ask: does this help the person, or only the business? Keep the first kind. Question the second.
MEASURE FEELING, NOT ONLY CLICKS
Dashboards measure what is easy to count. Clicks, sessions, time on page. These are signals, not answers. Long time on a page can mean fascination or confusion.
Pair the numbers with something human. Watch five people use the experience. Read what they write when they contact you. Notice what they ask that the page should already have told them. Then change one thing, and watch again.
WHERE PLATFORMS FIT
None of this is an argument against software. Good platforms make good experiences easier to build, run and improve. They are the instruments.
But instruments do not compose. Someone still has to decide who the experience is for, what it must do, and in what order the conversation should unfold.
That is the work. The platform comes after.