// Case study / Question discovery
The workaround broke. The data showed the gap. Frontline staff knew why.
A transaction anomaly surfaced inside an unrelated lifecycle model. A Sense-Making-informed conversation with floor staff explained why: the designed system had never supported the informal compatibility workflow they depended on.
What happened
A transaction anomaly became a product capability.
A consumer-electronics retailer now relies on a compatibility-checking configurator: automatic part filtering, inventory integration, a dedicated assembly service tier, and mobile-first floor use. The capability did not start as a feature request. It started as an anomaly inside an unrelated lifecycle-marketing build.
A Sense-Making-informed conversation with floor staff surfaced the missing piece: an informal compatibility tool had stopped working. The official system had never supported the real floor workflow.
Situation
The model was for lifecycle marketing. The signal was about product experience.
While building post-purchase lifecycle segments, an odd pattern emerged: a meaningful cohort returned shortly after purchase to buy additional major parts — not incidental accessories. A return is not unusual, but the type and scale of those purchases pointed to customers discovering compatibility gaps after leaving the store, not adding optional extras. Nobody had asked for this investigation. The anomaly appeared while the work was pointed somewhere else.
Task
Turn the anomaly into a diagnosis without overclaiming what the data could say.
The transaction pattern showed that a gap existed. It did not explain why. Closing that diagnostic gap meant going to the people holding the lived context: floor staff using workarounds because the official tools were wrong, slow, or not designed for floor use.
Quant signalReturning cohort
Lifecycle segmentation surfaced customers returning shortly after purchase for additional components.
Qual diagnosisFloor staff
Neutral questioning surfaced the failed workaround behind the returns.
Root causeShadow IT
An informal compatibility tool had quietly carried the workflow until it broke.
Product responseConfigurator
The client shipped a compatibility-checking configurator, now central to the business.
Built post-purchase customer segments for lifecycle marketing, not for product discovery.
A returning cohort suggested customers were buying additional components soon after the original purchase.
Sense-Making-informed neutral questioning let the diagnosis emerge from floor staff rather than from analyst assumptions.
An informal compatibility tool had been built because official tools were insufficient; when it broke, the hidden workflow became visible.
Action
The finding was framed as a resourcing question, not an analyst mandate.
After the anomaly surfaced, the finding was evaluated further with staff directly. I presented the diagnosis to the CX team across stakeholders without formal authority over product, framing the gap as a workflow and resourcing issue rather than as a top-down recommendation.
The staff evaluation also surfaced secondary friction around error messaging, which shaped the eventual product response.
Outcome
The compatibility-guidance gap was resourced and addressed.
- Compatibility-checking configurator shipped, with automatic part filtering and inventory integration.
- Dedicated assembly service tier built around the new capability.
- Mobile-first floor use, because staff needed the tool in context, not at a desk.
- Improved error messaging addressing a second friction point staff surfaced.
- Second iteration planned for 2026, shaped by continued staff input.
Design lesson
Shadow IT is evidence, not noise.
When staff build informal tools or procedures, they are revealing the shape of work the official system does not support. Analytics can help locate that gap, but diagnosis often belongs to the people working around it every day.