Every new service eventually runs into the same question: what does this actually include? You can publish a clean landing page and a fair price, but until someone asks “would you also help with ___?” you don’t really know where the edges of the work live.
Last week was a week of drawing those edges—for our own Experience Helpdesk, and for the clients whose work, frankly, is exactly what an Experience Helpdesk was built for.
Rewriting How We Describe the Work
A long-overdue project finally moved off the sticky note: rewriting how we describe the Experience Helpdesk across every public surface we own. Headline, About section, channel descriptions, bios—LinkedIn, Bluesky, and YouTube all got pointed at the same idea.
The shift is subtle but real. We don’t just do UX. We do the broader work of customer experience—the design problem, yes, but also the editorial system around it, the privacy screen that stalled a release, the carousel hero that needs to ship before Friday. Calling it an “Experience Helpdesk” instead of a “UX Helpdesk” isn’t a rebrand for the sake of one. It’s an honest description of the surface area we already cover.
Alongside that, we wrote out the full implementation plan for three welcome email sequences—the on-ramps that move someone from a free newsletter, to a low-cost website reality check, to membership. Not glamorous work. But sales pipelines don’t build themselves, and good ones leave nothing on a sticky note.
Learn more about Experience Helpdesk →
Reading the Component, Not Just the Mockup
Sometimes the most useful UX work isn’t a redesign or a research study. It’s a careful look at how something is actually being used in the wild.
A stakeholder at an enterprise media client had been watching a component on their website and noticing something off. Not broken. Not bad. Just… off. The kind of “I think this isn’t quite working as well as it could” observation that’s hard to act on without evidence.
We pulled the behavior data, wrote up the findings, and sent the report. Whatever the team decides next—iterate, redesign, or leave it alone—they’re making that call from a position of data instead of a hunch.
It’s the kind of mid-flight UX read that helps a busy team move forward with confidence instead of guesswork. Not a full engagement. Not nothing. A focused, evidence-backed look that turns a vague worry into a clear next step.
See our User Experience Consulting services →
Visual QA That Most In-House Teams Wish They Had Time For
One of our clients publishes more articles in a week than most companies publish in a year. Every one of them needs a visual pass before it goes live—tone, layout, typography, image cropping, the small things readers don’t notice unless they’re broken. We worked through three live story posts last week, and our content partner kept the queue moving without a rollback or a missed deadline.
That’s the kind of work most in-house teams want to do but can’t carve the hours out for. It’s exactly what an Experience Helpdesk is built to absorb.
Learn about Content Operations →
If you’ve ever found yourself thinking “we don’t need a full agency, we just need someone we can email on a Tuesday”—that’s the helpdesk. Last week, we spent some time making sure the description matched the work. The work itself just kept happening.
