Synopsis
A retailer's promotional calendar had grown busier, but launching or adjusting an offer still took three to four weeks moving through IT and legacy systems. BP3's UX design team built an intuitive dashboard, tested directly with the people who use it every day, that put promotion management in the hands of the business itself. Publishing time dropped from weeks to minutes, promotion management left IT's queue, and the retailer gained the ability to respond to sales opportunities and unexpected events as they happened.
Promotion Publishing Time Dropped From Weeks to Minutes
Retail moves at the pace of its promotional calendar, and that calendar has only gotten busier. Markets shift by the week, sometimes by the day, and the retailers that respond fastest are usually the ones that capture the sale. As one retailer's promotional calendar grew more demanding, that speed was the thing it wanted most: the ability to launch a new offer, adjust an existing one, or react to an unexpected event the moment it happened, not weeks later.
That speed was not something the existing process could deliver. Creating or changing a promotional offer or guest coupon meant working through a multi step approval process, coordinating testing across multiple departments, and depending on an IT team already stretched across a long list of other priorities. Each of those steps existed for a reason. Approval mattered because a mispriced offer or a coupon with the wrong terms could be costly to unwind once it reached customers. Multi department testing mattered because a promotion touches point of sale, inventory, and customer service all at once, and each of those teams needed to confirm the offer would behave correctly in their system before it went live. None of it was waste. It was simply a process built for a slower calendar than the one the business now had to keep up with.
The practical effect was a three to four week cycle between deciding a promotion was needed and having it live in front of customers. In a stable market, that lag is an inconvenience. When circumstances shift quickly, it becomes a real constraint. During the pandemic, for example, waves of vacation cancellations meant the retailer needed to respond with new offers and adjusted terms faster than the existing cycle allowed. A month is a long time to wait when the situation that prompted the offer has already moved on by the time the offer is ready.
BP3's UX design team took this on directly, and the starting point was understanding the process as it actually worked, not as anyone assumed it worked. That meant sitting with the business stakeholders who requested promotions and the staff who built and tested them day to day, mapping every step from initial request through to a live offer. The goal from the outset was not to make the existing process faster by trimming steps, but to rethink who needed to be involved in each step and where a person's judgment was actually required versus where a manual handoff was simply slowing things down without adding value.
What came out of that process was an intuitive dashboard built to serve as the central home for every promotional activity. Rather than promotions and guest coupons living across email threads, spreadsheets, and IT tickets, they now lived in one place, where a member of the business team could create a new offer, clone an existing one as a starting point, or adjust the terms of something already running. The dashboard was built to make each of those actions simple enough that no specialized technical knowledge was required, which was the point: promotion management was moving from a task IT executed on the business's behalf to a task the business could execute itself.
A second piece mattered just as much as the interface itself: automated event notifications. Under the old process, keeping every relevant team aware of a new promotion or a change to an existing one depended on someone remembering to loop in point of sale, inventory, and customer service separately. The new system handled that automatically, so the moment a promotion was created or modified, everyone who needed to know, knew, without a person having to chase down each stakeholder individually. That single change removed a meaningful source of delay and miscommunication that had nothing to do with the speed of any one team and everything to do with the coordination overhead between them.
None of this was built and shipped in a single pass. The design went through several rounds of usability testing directly with the client's own staff, the people who would use the dashboard every day once it launched. Each round validated specific decisions about functionality and flow: where a button needed to sit, what information a user needed to see before confirming a change, how the system should behave when an offer needed to be corrected after publishing. That iterative process is why the final dashboard fit the way the business actually worked, rather than a designer's best guess at how a retail promotions team should operate.
The result changed where promotion management lived organizationally, not just how fast it moved. What had been a development cycle task, requiring an IT ticket, a build, and a release window, became something the business team could do directly from request to published offer in a single sitting: identify the need, configure and test the offer on the dashboard, and publish it live, with no queue in between. Publishing time dropped from three to four weeks to minutes.
The impact went beyond speed for its own sake. With that agility, the retailer could adjust pricing, terms, or availability in response to sales goals or unforeseen circumstances as they arose, instead of planning weeks in advance around a process that could not react in real time. A promotion that made sense on a Monday could actually be live on a Monday, rather than becoming irrelevant by the time it finally launched a month later.
The broader lesson extends well past this one retailer's promotions calendar. Many operational bottlenecks that look like a resourcing problem, an overstretched IT team, a queue that never seems to shrink, are really a process design problem in disguise. The fix is rarely simply hiring more people to work through the queue faster. It is asking whether the people currently required at each step are the ones who actually need to be there, and building a tool that lets the people closest to the decision make it directly. When the tool matches how the business actually works, IT stops being the bottleneck, and the business gains the room to respond to whatever the market does next.