Complaint & Feedback Lifecycle Modernization
A large regional bank's complaint and employee-feedback systems had grown into a patchwork of disconnected tools, inconsistent categorization, and manual workarounds. This project reimagined the end-to-end lifecycle, from the moment an issue is raised to the moment a fix is verified, for the seven types of employees and customers who touch it.
My Role: UX Research, Product Strategy, UX Design, Stakeholder Workshops
Methods and Tools: Discovery Interview, Thematic Analysis, Persona Development, Validation Workshop, Prioritization Exercise & Concept Creation, Future-State Journey Mapping
The Problem Space
Complaints entered through a dozen disconnected channels. Employees retyped the same issue three or four times per case because no field talked to any other. Once a complaint or feedback was logged, it disappeared into a black box, no visible owner, no status, no way to know if it was ever actually fixed.
“My team works out of 20 different systems just to do research.”
Discovery
We started by understanding how complaint handling actually worked across the organization, who touched a complaint, what systems they relied on, where handoffs happened, and where people were creating workarounds to get the job done
01. Kickoff & Stakeholder Alignment
Before writing a single interview question, we reviewed existing process documentation and worked with the core team to map who needed to be at the table.
Complaint handling touches frontline banking, contact centers, compliance, legal, risk, IT, and multiple lines of business — each with a different relationship to the same system.
This mapping shaped the 13+ stakeholder groups selected for discovery.
We also ran periodic stakeholder alignment syncs throughout the project to keep leadership updated between formal milestones.
02. Discovery Interviews
Because a compliance specialist and a frontline banker experience the same system completely differently, we created a distinct interview guide for each role rather than relying on a single generic script.
Every session followed a consistent arc:
Understand the role → Walk through the lifecycle → Identify pain points → Explore opportunities
This allowed us to compare experiences across very different roles while still surfacing the nuances of each one.
03. Synthesize & Make Sense
With perspectives coming from 13+ stakeholder groups, the challenge was moving beyond individual anecdotes to understand the patterns connecting them.
Each transcript was coded stage by stage across the complaint lifecycle:
Capture → Research → Resolve & Close → Insights → Root Cause → Hand-off
We tagged what was happening today, the pain points and needs raised, and opportunity ideas volunteered by stakeholders. Verbatim quotes were preserved alongside each coded point so the context behind each finding wasn't lost during synthesis.
-
Before writing a single interview question, we reviewed existing process documentation and worked with the core team to map who needed to be at the table.
Complaint handling touches frontline banking, contact centers, compliance, legal, risk, IT, and multiple lines of business — each with a different relationship to the same system.
This mapping shaped the 13+ stakeholder groups selected for discovery.
We also ran periodic stakeholder alignment syncs throughout the project to keep leadership updated between formal milestones.
-
Because a compliance specialist and a frontline banker experience the same system completely differently, we created a distinct interview guide for each role rather than relying on a single generic script.
Every session followed a consistent arc:
Understand the role → Walk through the lifecycle → Identify pain points → Explore opportunities
This allowed us to compare experiences across very different roles while still surfacing the nuances of each one.
-
With perspectives coming from 13+ stakeholder groups, the challenge was moving beyond individual anecdotes to understand the patterns connecting them.
Each transcript was coded stage by stage across the complaint lifecycle:
Capture → Research → Resolve & Close → Insights → Root Cause → Hand-off
We tagged what was happening today, the pain points and needs raised, and opportunity ideas volunteered by stakeholders. Verbatim quotes were preserved alongside each coded point so the context behind each finding wasn't lost during synthesis.
This synthesis gave us two critical outputs: a shared understanding of who experiences the system and a clear picture of where the system breaks down.
Personas
The complaint lifecycle is experienced differently depending on where someone sits in the system. We translated the research into seven role-based personas, each representing a distinct relationship with the complaint lifecycle.
Add a new, how 7 personas look-like Visual over here: leverage Figma Make for it.. Maybe overview + One persona deepdive through Figma Make. Maybe top 2?
Key Findings
Through our research, we— complete this line.. Also add pic from interivew and synthesis somewhere here.
—add small emojis below like the other projects. Add a view in deatil button for this iGUESS?
01
Lack of
Efficiency
The complaint system doesn't fit how people actually work, so complaints get skipped, rushed, or missed.
02
Inconsistent Taxonomy
There are no shared standards for how complaints should be captured, classified, or documented.
03
Lack of Connectivity
Complaints move through too many disconnected systems with no single thread holding them together.
04
Lack of
Visibility
Once a complaint is submitted, accountability and status effectively disappear.
05
Early-Stage Automation
Critical complaint work still depends heavily on individual effort and informal workarounds.
IMPLICATION
The bank is managing the complaints it knows about, not the full volume that exists, creating blind spots in risk, reporting, and customer experience.
The data reaching reporting and root-cause analysis is unreliable from the start.
Every handoff requires someone to rebuild context from scratch — adding time, increasing error risk, and forcing customers to repeat their story.
Untracked complaints resurface and resolutions remain inconsistent.
Key steps still depend on people manually coordinating work that could be system-supported.
Key Findings
Through our research, we— complete this line.. Also add pic from interivew and synthesis somewhere here.
—add small emojis below like the other projects. Add a view in deatil button for this iGUESS?
01
02
03
Lack of Connectivity & Integration
Complaints move through too many disconnected systems with no single thread holding them together.
“My team works out of more than 15 different systems just to do research and pull documentation.”
04
Lack of Visibility
Once a complaint is submitted, accountability and status effectively disappear.
“We just take care of capturing the complaint… we’re not sure what happens after that.”
05
Lack of Efficiency
The complaint system doesn't fit how people actually work, so complaints get skipped, rushed, or missed.
“Five weeks in, I still don’t know how to submit a complaint.”
Inconsistent Taxonomy
There are no shared standards for how complaints should be captured, classified, or documented.
“There’s no rules that says if someone is complaining about this, categorize it this way.”
Early Stage Automation
Critical complaint work still depends heavily on individual effort and informal workarounds.
“We have a checklist… a physical checklist that compliance has us fill out for every case.”
KEY FINDINGS
Complaint logging is unintuitive and high-effort.
Logging can take 7–10 minutes in some cases.
Users avoid or delay logging under time pressure.
Actual complaint volume may therefore be higher than captured volume.
KEY FINDINGS
Employees categorize identical complaints differently.
There are no consistent steps or templates.
Key regulatory fields aren't always mandatory.
Inconsistent categorization weakens reporting and routing.
KEY FINDINGS
Complaints enter through multiple channels.
There is no single view of the customer or complaint.
Teams rely on email and informal follow-ups.
Case context must often be manually reconstructed.
KEY FINDINGS
The lifecycle becomes a “black box.”
Ownership becomes unclear across teams and handoffs.
Follow-through is inconsistent and difficult to see.
There is no structured feedback loop.
KEY FINDINGS
Documentation and compliance checks are manual.
Escalation relies on email and direct outreach.
Reporting and quality oversight require significant manual effort.
Physical checklists and manual calculations remain part of the process.
IMPLICATION
The bank is managing the complaints it knows about, not the full volume that exists, creating blind spots in risk, reporting, and customer experience.
IMPLICATION
The data reaching reporting and root-cause analysis is unreliable from the start.
IMPLICATION
Every handoff requires someone to rebuild context from scratch, adding time, increasing error risk, and forcing customers to repeat their story.
IMPLICATION
The bank is managing the complaints it knows about, not the full volume that exists, creating blind spots in risk, reporting, and customer experience.
IMPLICATION
Key steps still depend on people manually coordinating work that could be system-supported.
Current State Journey Map
We mapped the end-to-end complaint lifecycle across five stages, capturing employee experiences, pain points, handoffs, roles, and systems to create a shared view of the current state.
We used the journey as a working artifact in the stakeholder workshop, where teams validated the findings, added gaps, and identified opportunities for improvement.
Add image of the journey, (blurred out)
👆
Current-state journey used as a collaborative workshop artifact. Stakeholders annotated pain points, gaps, handoffs, and opportunities across the complaint lifecycle.
Validation & Defining the Direction
With the current-state journey, personas, and key findings in place, we validated the research with stakeholders who work in the process daily.
In the workshop, we pressure-tested insights, surfaced gaps, and aligned on the direction forward. Stakeholders reviewed the journey, confirmed key pain points, added missing context, and challenged assumptions before we moved into solutioning.
From
Fragment, manual complaint handling
To
a connected, guided, and transparent experience
subjective complaint identification
consistent, intelligent capture and classification
disconnected systems and repeated reconstruction
a consolidated view of the customer and complaint
a black box after submission
visibility into ownership, status, and next steps
manual reporting and disconnected insights
a closed loop between insight, action, and measurable outcomes
From Insights to Concepts
With the experience direction established, we translated the validated needs into five concepts spanning the complaint lifecycle. Each concept was framed as a “How might we…” question and tested with stakeholders in co-creation sessions to validate direction and surface key tensions before prioritization.
01 | Capture Once, Capture Right
Prototype
Success Metrics
60% Increase
in succesful approvals
86% Reduction
in Processing tIme
Conclusion
This project was a deep dive into cross-functional collaboration. Working with multiple stakeholders across UX, product, and architecture taught me the value of domain immersion and active alignment. Navigating different perspectives helped me sharpen not just my design thinking, but also my ability to translate complex requirements into usable, meaningful solutions.
Being open about our process, including where we needed time to explore solutions, helped manage expectations. Co-creating timelines and working plans with stakeholders not only kept the project on track but also created a more invested, collaborative environment
