Three Lessons from the Retailer That Rebuilt Its Stack in 11 Months
Speed came from narrowing scope ruthlessly, not from adding headcount — a pattern emerging across fast transformations.
When a mid-sized retailer set out to replace its ageing commerce, inventory and point-of-sale systems, consultants estimated three years. The company did it in eleven months. The speed did not come from a bigger team or a bigger budget. It came from saying no — repeatedly and deliberately.
Lesson one: shrink the scope
The original plan included a new loyalty platform, a redesigned mobile app and a data warehouse migration. All three were removed from the first phase. The team focused on a single outcome: one accurate view of inventory across stores and online.
“Every feature we cut made the rest of the project faster. The hardest part was defending those cuts every week.”
Lesson two: buy, then configure
Rather than customising new platforms to match old processes, the retailer changed its processes to fit standard software wherever possible. Customisation was allowed only where it created a clear customer advantage.
- Standard workflows adopted for finance, purchasing and warehousing
- Custom development limited to the store fulfilment experience
- Every requested customisation reviewed by a business executive, not just IT
Lesson three: run the business through the change
The cutover happened region by region over six weeks rather than in a single weekend. Each region taught the team something that made the next one smoother, and the business never faced a moment where everything changed at once.
What other leaders can take from it
Fast transformations share a pattern: ruthless scope, standard technology and a sponsor willing to absorb the political cost of saying no. Speed, it turns out, is mostly a leadership decision.