Perseid Echo Book a call

Customer experience design

Customer experience by design

Every customer walks a path: finding you, asking, booking, being served, coming back. I find where that path breaks, then fix the handoffs, scripts and steps behind it, so it feels easy on both sides of the counter.

The real thing

See it for yourself.

A customer journey map in five stages, from discover to return.

A customer journey, mapped

Every step a customer takes, stage by stage, drawn with my own journey-mapping tool. This one is a sample online shop, not a client.

Sound familiar?

What you get

The journey, mapped

Every step your customer takes, and where it gets hard.

Clear ownership

Who does what at each handoff, written down.

Guidance your team uses

Simple procedures, scripts and checklists for the front line.

A way to measure it

Agreed signs of improvement, checked after the change.

How it works

  1. 01

    Fit Check

    A quick read on where to start.

  2. 02

    Walk the journey

    Together, from the first call to the follow-up.

  3. 03

    Fix and check

    Put the changes in place, then measure what changed.

More than 21 years in customer experience and operations: service journeys, frontline procedures, and making change stick.

Proof from the floor

Practical experience, put to work.

Figures describe documented scope, not a forecast of your results.

Work order 01

Journey flow tool

Internal workflow tool, from my customer experience work

~20designers on the team
Mostadopted the tool

Created a field-driven tool that turned structured journey inputs into leadership-ready flows. It removed repetitive PowerPoint formatting, from box alignment to text spacing, and was adopted by most of an approximately 20-person design team.

Work it takes off a person: Designers could spend more time on the journey and cross-team decisions instead of recreating the presentation.

Work order 04

Buyer's guide sign-up

Client project, family client, quoted with permission

Fewersteps to send invitations
Automatedpayment receiving

Built the vendor invitation emails, sign-up tracking and payment collection for a home care technology buyer's guide, and kept its pages and categories easy to change.

Work it takes off a person: Searching for updated contact emails and keeping track of bouncebacks and replies by hand.

“Bryan took over and automated absolutely everything about the backend workings while leaving the customer-facing part intact. He saved me hours, perhaps weeks, of busy work. And now my service is ready to go, months sooner than I could have released it using my manual methods.”

Tim Rowan · Public 5-star Google review

Disclosure: Tim is my stepfather, which is how I got the job, and why he had no reason to be polite about it. The review is public on Google.

Bryan Piard at his desk in Renton, Washington.

Who you are dealing with

One person, and he answers.

I am Bryan. For more than 21 years, I worked across customer experience and operations: improving service journeys, shaping frontline procedures, helping teams support new products, and bringing different functions together to make change work.

  1. You work directly with me, from understanding the problem to putting the change into practice.
  2. You get clear documentation, agreed responsibilities, and guidance your team can use.
  3. We agree how to judge the improvement before we start, so progress means more than finishing a project.
  4. If a clearer message, a step removed, or better ownership is enough, that is the recommendation you get.

Questions owners ask

Is this just a report?

No. The point is a working change: new steps, guidance and tools your team actually uses.

Do you work with small teams?

Yes. Most of this work is with owner-led businesses and small teams.

Where does AI come in?

Only where it helps. Sometimes the fix is a clearer message or a better checklist, not new technology.

Do I own it, or am I renting it from you?

You own and control what is built for your business. You get the credentials, the configuration, the documentation, and a plain-English owner's guide: everything needed to run it or hand it to someone else.

You are one person. What happens if you disappear?

Fair question. Everything is documented well enough for another competent person to pick it up, monitored so problems announce themselves instead of going quiet, and built on tools you can access without me.

What happens to my data?

Before anything is built, you get it in writing: what the work touches, which outside services process it, what is stored and for how long, and who has access. If any of that is not acceptable to you, we design around it or we do not build it.

Let's see if it fits.

One short call. You talk to the person who does the work.

Book a free 20-minute call

Other ways I can help