People on the underground busily checking their phones.
Product & UX23 Jan 20268 min read

Design for the Distracted

Plenty of products are ‘clean’ and still make people bounce. Not because the UI is bad—because the timing is. This piece is about rhythm: the moments where your UX asks for commitment before trust, punishes hesitation, or makes people guess. Syncopation, but for nervous systems—and a practical way to audit your product’s tempo.

AccessibilityDecision-makingFelt SafetyMicrocopyOnboardingProduct DesignUX

Design is easy.

You just pick a font, choose a design system, chuck a “Get Started” button in the top right, and pray your users were born with the same attention span as your product manager.

Except they weren’t.

And deep down, you already know that.

I want to talk about syncopation—not in the “music theory” way, but in the how a body survives a room way. Because once you start noticing rhythm as a social thing, you can’t unsee it in products, brands, and teams.

And if you build digital experiences for a living, that’s either a gift…or a curse you’ll never shut up about at parties.

The default beat isn’t neutral

The default beat is generous. It holds your hand. It’s a straight line. You can follow it half asleep.

That’s why it feels “normal”: because it was built to be.

In culture, the default is what you can do without explaining yourself. In products, the default is what you can do without thinking.

And that sounds like good UX, right?

Effortless.
Frictionless.
Smooth.

But “frictionless” is a funny word, because it hides a quiet truth:

Most products aren’t frictionless. They’re frictionless for the people they assumed.

If you’re confident, calm, fluent in the category, fluent in the language, familiar with the patterns—the beat feels obvious.

If you’re tired, anxious, neurodivergent, new to the context, or just trying to do the thing in a noisy life, well, the same experience becomes a test.

You don’t just navigate it. You translate yourself through it. And that translation work has a cost:

  • Attention
  • Shame
  • Hesitation
  • Drop-off

The numbers call it “churn”. The person calls it “I can’t be bothered with this.”

Syncopation: the moment a rhythm recruits you

Syncopation is a controlled wobble. It steals certainty and replaces it with anticipation.

The obvious place to land stops being the most satisfying place to land. The beat steps sideways. And your body leans in.

That’s why dance music works when it works. It doesn’t entertain you from a safe distance. It pulls you into participation. It creates a shared problem, and the room solves it together.

That’s what I mean when I say: Syncopation is social technology.

Not because it’s clever. Because it changes what “being in the room” means.

Now swap “dancefloor” for “product”.

Great experiences recruit you too—not through manipulation, but through confidence:

  • I know where I am.
  • I know what’s expected.
  • I know what happens next.
  • I can recover if I mess up.

Bad experiences do the opposite. They demand certainty from the person entering:

  • Read this.
  • Decide that.
  • Trust us.
  • Don’t misunderstand.
  • Don’t be weird about it.

Which is hilarious, because the entire reason people use products is to reduce effort—not perform competence.

The hidden work: living in departures

There’s a reason some people are better at hearing the felt rhythm than others: Some people get to treat culture like a buffet.

Pick what they like.
Ignore what they don’t.
Assume the room will adapt.

Other people learn rooms like a map. Not because they’re special. Because they’ve had to.

For example, being gay, most of the time, isn’t dramatic. It’s small calibration: Do I say “date” or “he”? Does the room update warmly, or does it glitch? Do I correct, deflect, joke, ignore—and what does each option cost me today?

ADHD is similar in a different key. It goes a bit like this: Rehearsing “don’t interrupt” while thoughts sprint ahead. Anchoring yourself physically so you don’t drift out of the room. Building an exoskeleton of reminders because your brain doesn’t respect linear time

None of that is tragic. It’s just constant.

It’s like living in departures at an airport: always aware you might have to exit the room quickly, socially or emotionally, if the rhythm turns hostile.

And if you’ve had to live like that, you get good at noticing what rooms expect from people.

Which is why I’m suspicious of “best practice” when it’s delivered like scripture.

Because half the time, “best practice” is just the default beat pretending it’s morally superior.

Products are rooms (and people arrive with bodies)

Dead Keen has always framed work as rooms, thresholds, portals—not because it’s poetic for the sake of it, but because it’s accurate .

A product isn’t a set of screens.

It’s a room people enter carrying stress, baggage, context you will never see, and a nervous system that will decide whether to trust you before their brain does

That’s why the details matter:

  • Pacing
  • Confirmation
  • Error recovery
  • Microcopy that sounds like a human, not a toaster manual
  • Motion that feels like memory, not mechanics

And yes, accessibility. Always.

But I’m also talking about something broader:

Designing for felt safety.

Because people don’t abandon experiences when they’ve “evaluated the information architecture”.

They abandon them when their body decides: this is effort.

What “off-beat” design looks like in practice

This is the point where an article like this usually does a dramatic reveal and tries to sell you a framework with a trademark.

I won’t. But I will give you a lens.

If you want to design rooms that hold up under human weight, look for where your experience is asking the wrong thing of the person entering.

Here are a few questions I use:

1) Where are you demanding attention you haven’t earned yet?

If you hit people with complexity before trust, they don’t “learn your product”. They leave.

2) Where are you punishing hesitation?

If someone pauses, your experience should support them, not shame them with vague errors or irreversible steps.

3) Where are you relying on hidden rules?

“If you were one of us, you’d know what this means” is not a strategy. It’s a leak.

4) Where is the rhythm technically correct but emotionally false?

The flow can be “logical” and still feel like a cold office with strip lighting. People don’t want to be impressed. They want to feel capable.

5) Where are you forcing people to translate themselves?

This is the killer point.

Any moment where someone has to ask:

“What do they mean?”
“What am I supposed to do here?”
“Is this my fault?”

…is a moment where you’re losing trust.

Fixing these isn’t just UX polish. It’s respect.

The Dead Keen bit (without a sales pitch, honest)

The reason this matters to my work is simple:

I walk into other people’s worlds for a living—businesses, teams, audiences—and I build rooms that have to hold up.

Not for ideal humans. Real ones.

People with distracted minds, guarded hearts, tired bodies, loud lives.

That’s why Dead Keen is both a studio and a signal—practical delivery with a ghost in the machine .

The job isn’t to make everything “cool”. It’s to make the rhythm honest:

  • Clear enough that people can move
  • Human enough that people can breathe
  • Precise enough that teams can ship without relitigating reality every Tuesday

Sometimes that shows up as brand.
Sometimes as product.
Sometimes as code.

Sometimes as a narrative layer that makes the whole thing feel like it belongs in the world.

But the principle stays the same: Build for the off-beat, and the default becomes easier for everyone too.

A last thought, on leaving the room

There’s always a moment after a great night out when you step into the street and everything feels too quiet.

The door closes.
The world turns the saturation down.

And you realise—without trying—how many rooms you’ve learned to survive. How many rhythms you’ve memorised. How many times you’ve translated yourself into something smoother so other people don’t have to work as hard.

That’s what syncopation teaches, if you let it: The room is always asking something of you.

The question is whether you notice—and whether you design accordingly.

So what do you reckon:

Where does your product still expect people to be “the default” before it lets them in?

Article and original artwork by Ryan Taylor

A little extra

Berlin clubs don’t reject you because you’re not "cool". They reject you because you don’t match the night’s rhythm. Products do the same, quietly: if your flow expects confidence but your user arrives stressed, you’ve built a velvet rope and called it onboarding.