Some weeks the work clusters around a single deadline. This one clustered around a single question: who is this actually for? Whether it was a system that captions and narrates video for people who can’t hear or see it, a website for neighbors trying to follow a local committee, or a year of data pointing toward what real visitors needed next, the team spent the week making sure the people on the other end of the screen were the ones we were building for.
Passing Down a System Built for Accessibility
A client brought a new team member on board this week, and that gave us a chance to do one of the most underrated things in any long engagement: explain how the machine works. We walked the new hire through a system we’d helped this client build earlier—an approach that makes sure every video on their site ships with both closed captioning and described video for viewers who are blind or have low vision.
That second piece is where most organizations stop short. Plenty of teams will add captions. Far fewer build described video into the pipeline so that what’s happening on screen is narrated for people who can’t see it. Designing both into how content ships, by default, is genuinely industry-leading work—and the fact that it keeps running smoothly enough to hand off to a new person is part of what makes it good.
Accessibility done this way rarely makes the highlight reel. It’s quiet, detailed, and easy to skip. But a system that outlasts the people who built it, and that a newcomer can pick up and run with, is exactly the kind of thing worth pointing to.
See our User Experience Consulting services →
A Community Committee Gets a Home Online
Some of the most rewarding work we do never carries a corporate logo. This week we helped a local community committee set up the infrastructure to do its job in the open—a shared workspace for committee documents and feedback, and a secured landing page on the municipal website where residents can follow the committee’s progress.
It’s a small build by most measures. But for the people it serves, it’s the difference between a committee that meets behind closed doors and one the community can actually watch and weigh in on. Good digital infrastructure isn’t only for the organizations that can pay the most for it. Sometimes the highest-impact page you’ll build all month is the one that helps a few hundred neighbors stay informed.
Learn about Website Roadmapping →
Turning a Year of Data Into a To-Do List
When you’ve got a full year of behavioral analytics on a website, the temptation is to admire the charts and move on. The harder, more useful work is turning all that data into specific decisions. This week we took a client’s year-in-review analytics report and wrote a set of enhancement ticket recommendations—concrete changes, prioritized and ready to act on, each one traceable back to something real visitors were actually doing on the site.
This is what data over drama looks like in practice. Not a dashboard nobody reads, and not a gut-feeling redesign either. Just evidence pointing clearly at the next handful of improvements worth making. The report tells you what happened. The tickets decide what happens next.
Explore the Experience Helpdesk →
Visual QA at Scale: A Rollout Across More Than a Dozen Markets
An enterprise client spent the week rolling a new service out city by city, and the content calendar showed it—a heavy slate of press releases announcing market-by-market launches, regional business events, and local awards. Each one came through our visual QA process before publishing: formatting checks, image placement, metadata review, and a final sign-off before it hit the newsroom.
When the same announcement ships to more than a dozen markets with the city name and details swapped each time, consistency stops being a nice-to-have. One misplaced image or broken layout, repeated fifteen times, becomes fifteen problems. The steady, unglamorous discipline of checking every piece is exactly what keeps a high-volume rollout from turning into a high-volume cleanup.
Learn about Content Operations →
That’s the week: an accessibility system solid enough to hand off to a new teammate, a committee that’s easier for its community to follow, a year of data turned into a clear next step, and a national rollout held to a steady standard. Different clients, different scales—but the same question underneath all of it. If your organization is trying to build something that works for the people it’s actually meant to serve, let’s talk.
