Client stories

What teams noticed after a behavior engagement—approval handoffs, messy maps that helped, and cohort cuts that refused a flattering headline.

Voices from recent work

Quotes reference specific engagements. Length and tone vary because the work did.

“The audit showed that our approval step was not failing because of the form layout. Operators were waiting on reference numbers that finance uploaded a day later. We changed the handoff, not the button.”

Hyejin Park, Product lead, wholesale order platform · Customer Behavior Audit

“I wished we had started the taxonomy workshop before the spring release. We still cleaned up naming, but we spent a session untangling duplicates we had just shipped. The catalog itself is finally something engineering and product both open.”

Minsoo Han, Engineering manager, field-service scheduling app · Event Taxonomy Workshop

“Their journey maps looked unfinished at first glance—loops everywhere. That was the point. We finally saw how branch managers skipped the recommended path and still completed bookings.”

Sora Kim, Operations director, multi-branch booking system · Journey Mapping Engagement

“The cohort review did not flatter our onboarding. Accounts created during a promotional seat push returned far less than accounts trained by our own specialists. Sales wanted a softer headline; we kept the harder one.”

Jaeho Lee, Customer success lead, B2B reporting suite · Retention Cohort Review

“Response times were steady and the written pack was usable without a translator in the room. We still needed one follow-up call to clarify a funnel definition, which they handled without reopening the whole project.”

Eunji Choi, COO, logistics coordination application · Customer Behavior Audit

Extended cases

Two longer notes on how findings changed the next product move.

Customer Behavior Audit

Approval delays in a wholesale order application

A Namyangju-area wholesaler saw a sharp exit on the order-approval step after a UI refresh. The team assumed the new layout confused buyers.

DevData Sphere reconstructed paths for buyer and internal approver roles across six weeks of events. Most exits belonged to buyer accounts that reached approval while purchase-order references were still empty. Support tickets confirmed buyers abandoned and emailed sales instead. The product team restored a waiting state and notified buyers when finance attached references. Exit volume on that step fell in the following month without another visual redesign.

Retention Cohort Review

Onboarding cohorts after a seat promotion

A reporting suite offered discounted seats for two months and watched aggregate retention dip.

We split cohorts by acquisition path: specialist-led onboarding versus self-serve promotional seats. Return rates diverged within the first fourteen days. The promotional cohort completed setup wizards less often and rarely reached the first scheduled report. Customer success redirected promotional accounts into a shorter assisted setup rather than treating the dip as a product-wide failure.

Discuss a similar engagement