Telecom · B2B · 0 → 1 · 2024
MTS — Geolocation
A 2-week audit and backlog prioritisation cut pre-release design defects by 30%; a usability test saved ~a month of development.
TL;DR
−30% design defects, ~a month of development saved
- 01Audit in 2 weeks → a prioritised product backlog before release
- 02A usability test before development cut an unneeded feature (~a month saved)
- 03Scrum master: +20% sprint task completion
CLIENT
ROLE
TIMELINE
TEAM
Context
An MTS high-precision geolocation B2B service heading to market: industry landing pages, a client portal, a partner CRM, an equipment-management back office. I was the only designer on a team of 20.
The decision I’m proud of
The backlog held a key feature the team had already budgeted about a month of development for. I doubted it — and instead of building on faith, I brought real users and the client to a usability test before development even started. The test showed the feature wasn’t needed. We cancelled it — and saved the team ~a month of work. To me that’s what design is: not drawing a screen, but asking “is this even needed?” in time.
How I worked otherwise
In parallel, over two weeks I ran a full product audit and rebuilt the backlog by priority — which cut design defects at release by 30%. To bring departments together at the seams, I took on the Scrum-master role: +20% sprint task completion.
Result
−30% design defects at release. The cancelled feature — ~a month of development saved. +20% sprint completion. The product reached the market assembled, not “as far as we got.”
More in the blog