Every project has a moment where the smartest move is to wait—and waiting well is harder than it sounds. One of our enterprise clients is heading into a major brand transition, and nobody will know what the new brand looks like for months. So most of what we finished this week was preparation: building the machinery now so the team can move fast later, and keeping people productive while the big decision gets made somewhere above everyone’s heads.
Building the Runway Before You’ve Seen the Plane
When a rebrand is coming but the direction hasn’t landed, you have two options. You can keep shipping deliverables that will need to be redone, or you can get the pipeline ready for the day the direction shows up. We always choose the pipeline.
That requires our Content Operations team to map a clearer path from “here’s a brief” to “here’s a published page”—when a design deserves custom treatment, and when it can be assembled quickly from the site’s existing component library instead of being hand-drawn from scratch. The team also started consolidating several scattered component-library projects into one place, so prototyping happens where the real parts live. And the next releases are being planned around the outer wrapper of the site, so that when new logos and typography do arrive, swapping them in is a quick change rather than a rebuild.
We also made the harder call: pausing a full site migration that was designed and ready to go. Every page layout is done and waiting. But with the brand changing underneath it, building now means building twice, so the work stays parked until the direction is real. Eventually, thousands of documents will need to conform to whatever the new brand becomes. The organizations that survive that kind of volume are the ones that set up the assembly line before the orders come in.
Learn about Website Roadmapping and Research →
New Seat, Same Standard
Teams change shape in the summer. A client’s design group welcomed a new designer this week, and we got them access to their project design files and exploration boards right away—no two-week limbo waiting for someone to remember to send an invite.
The rest of the continuity work was quieter. We coached two developers on covering content design while a departing teammate’s seat gets filled. And we updated the site’s typography documentation so the quality engineering team has a written baseline to test against, because “ask the person who knows” stops working the moment that person is on vacation, or on another project, or at another company.
The new designer also brought a question we’re hearing everywhere right now: which AI features in our design tools are actually okay to use? Rather than shrugging, we gave the team a practical interim rule—experiment with placeholder content or material that’s already public, keep anything confidential out entirely—and started checking whether the feature is officially approved so there’s a real answer on file. Now the team can experiment without wondering whether they’re allowed to.
See our User Experience Consulting services →
Small Tickets, Fast Turnarounds
Some work arrives as a ticket and leaves the same week. This week’s batch included producing audio versions of a set of articles on the client’s site, so visitors who’d rather listen than read get the same story everyone else does.
And when a client needed to take an online store offline, we handled the shutdown cleanly: a clear notice for visitors instead of a vanished page, and the navigation updated so nobody goes looking for something that isn’t there. Nobody loves closing things down. Doing it deliberately is the difference between a store that closed and a site that looks broken.
See how the Experience Helpdesk works →
And One for the Community
The community tech conference our team helps organize kept moving this week. We published the updated code of conduct, settled on a way for attendees to visibly opt out of photos, started recruiting a day-of volunteer coordinator, and began outreach to local tech press.
The photo opt-out is my favorite of the bunch. It’s a small piece of logistics that tells every attendee: you get to decide how you show up here. Nobody will write a review about it. That’s fine.
That’s the week: a design pipeline taking shape ahead of a rebrand, a team staying steady through arrivals and departures, tickets closed before they aged, and a conference quietly earning its attendees’ trust. If your organization is staring down a big transition and wondering what to do in the meantime, let’s talk.
