Enterprise UX
Designed operational tools for sales, service, cashiers, buyers, and managers—developing direct familiarity with the systems behind the customer experience.
B&H · Customer Insights & Customer Experience
A score can show that something changed. The useful work begins when feedback reveals where the experience is failing, which customers are affected, and what operational system may be responsible.
A change in vantage point
The work changed from shaping individual interfaces to building a system for listening, comparing, diagnosing, and communicating what customers were experiencing across the business.
Designed operational tools for sales, service, cashiers, buyers, and managers—developing direct familiarity with the systems behind the customer experience.
Worked on a two-person team designing and maintaining surveys, analyzing feedback, identifying experience drivers, and reporting issues to the CMO and executive leadership.
Helped select and implement the CX platform, then built and maintained its surveys, permissions, dashboards, topic rules, validation, and data connections.
Customer feedback became another view into the operating system.
Earlier enterprise knowledge made it possible to ask not only what customers disliked, but which process, handoff, rule, or technical system might be producing the experience.
01 · From score to cause
Likelihood-to-recommend and overall-satisfaction scores established direction. Open-text feedback and experience-driver analysis supplied the clues needed to find specific, actionable causes.
Operational example
A pattern noticed in customer feedback prompted investigation beyond the survey data. The team helped trace the complaints to a malfunction in an automated warehouse system.
02 · A measurement program
The program combined continuously maintained experience surveys with shorter investigations designed around a specific question. Ad hoc findings could then influence recurring studies and the questions added to ongoing surveys.
Continuously maintained across multiple customer experiences, with parameters, conditional questions, and routing logic.
Focused, time-limited studies created to investigate a specific issue, audience, or decision.
Recurring surveys exposed questions worth deeper study; focused research supplied findings and questions that could become part of ongoing measurement.
03 · Survey architecture
Parameters and query strings carried context into Medallia. Conditional questions and routing logic then adapted the survey to the customer’s experience, while enriched data and topic rules supported later analysis.
Experience, transaction, customer, and invitation context arrive with the response path.
Questions and branches change according to what the respondent actually experienced.
Technical and Data Warehouse coordination adds business context and resolves cross-system issues.
Measures, open text, classifications, and operational context become usable views for analysis.
04 · Validate the automation
Topic classification and sentiment analysis can create the appearance of precision. R and Excel were used to test how well those outputs held up across different slices of the program rather than assuming the platform was correct.
05 · Platform stewardship
Helping evaluate and select Medallia led into implementation, the initial role-and-permission structure, launch, and continuing responsibility for configuration, diagnosis, and improvement.
Contributed to evaluating and selecting the CX platform, then to the implementation and initial role-and-permission architecture.
Medallia launched at B&H, moving the work from implementation into ongoing survey, dashboard, topic, permission, and integration stewardship.
Earned the Medallia Super Admin Credential in 2023 and Partner Credential in 2024, supporting more advanced configuration and diagnosis.
What the work left behind
The evidence is not a gallery of interface screens. It is the structure connecting questions, customer context, analytical methods, platform rules, and operational findings.
This page uses abstract diagrams and documented scope rather than reconstructing confidential dashboards, survey screens, customer data, or internal system views.
Continue through the chronological portfolio.