Logo SAMRIDHI
  • Home
  • Services
  • Careers
  • Contact
  • Consult Now
  • Privacy Terms Cookies
Privacy • Terms • Cookies • AI Summary

About

Finding the Real Problem: Research Before Solutions

Published : Aug 13th, 2026

Finding the Real Problem: Research Before Solutions

How interviews, observation, contextual research, and qualitative insights prevent organizations from solving the wrong problem.

In fast-paced business environments, organizations fall in love with solutions far too quickly. When a service underperforms, customer churn spikes, or employee support queues backed up, leadership often rushes to action: build a new mobile app, launch an AI chatbot, redesign the website interface, or roll out an intensive staff training module. Huge budgets are allocated, engineering teams work around the clock, and flashy new digital tools are deployed—only for the core operational issues to remain entirely unchanged.

This costly cycle happens because teams treat surface-level symptoms rather than root causes. They rush to answer "How might we build this solution?" before asking "What is the actual problem we need to solve?" In service design, solving the wrong problem efficiently is still a total operational failure. Thorough research—powered by qualitative interviews, field observation, contextual inquiry, and deep synthesis—acts as an essential strategic filter, ensuring that organizations invest their time, capital, and energy into solving real human and system problems.


1. The Danger of the "Solution-First" Mindset

Organizations are naturally conditioned to be solution-oriented. Executives are rewarded for rapid decision-making, and software development cycles prioritize shipping features quickly. However, when a solution-first mindset bypasses deep problem discovery, teams build expensive infrastructure based on unverified assumptions, internal biases, and executive hunches.

Surface-level symptoms are frequently mistaken for root problems. For example, if customers are flooding a call center to ask basic account questions, a solution-first team assumes: "Our customers are lazy or uninformed; let's build an AI chatbot to automate responses and cut support costs."

However, if the team had conducted exploratory research first, they might have discovered the true root cause: the initial billing invoice is written in confusing legal jargon, making it impossible for customers to understand their charges. Building an AI chatbot simply digitizes the confusion—it automates responses to a problem that shouldn't exist in the first place. Fixing the invoice language eliminates the calls entirely at a fraction of the cost.

The iceberg of organizational assumptions

When organizations rely solely on boardroom discussions and high-level quantitative dashboards, they operate on assumptions that obscure operational realities:

  • Quantitative data tells you what is happening, but never why. Analytics can show that 40% of users drop out at Step 3 of a registration flow, but they cannot tell you if users left because of a security concern, a technical bug, confusing copy, or a sudden loss of trust.
  • Executive perspectives are insulated from frontline friction. Leadership rarely experiences the daily workarounds, clunky software workarounds, and frustrating policy barriers that frontline staff and customers navigate every day.
  • Solutions built on assumptions create "waste loops." Fixing a poorly researched feature post-launch costs up to 100 times more than researching and validating the problem beforehand.

2. Qualitative Methodologies: Uncovering Hidden Realities

To move beyond surface assumptions, service design relies on a suite of immersive, qualitative research methodologies. These tools allow researchers to study human behavior in its natural context, uncovering unstated needs and operational bottlenecks.

1. In-Depth Qualitative Interviews

Qualitative interviews go far beyond standard closed-ended surveys. Rather than asking rigid rating questions ("On a scale of 1-10, rate your satisfaction"), service design interviews explore mental models, past experiences, emotional triggers, and personal contexts.

Effective interviewing focuses on past behavior rather than hypothetical future intentions. Asking a user "Would you use a feature that does X?" yields polite, aspirational lies. Asking "Walk me through the last time you tried to complete this task—what went wrong, and how did you feel?" uncovers authentic operational realities.

2. Contextual Inquiry and Shadowing

What people say they do during an interview and what they actually do in practice are often radically different. Contextual inquiry combines open interview techniques with direct, real-time observation in the environment where the service actually takes place.

Researchers sit alongside call center agents, walk hospital halls with triage nurses, or accompany field technicians on repair visits. Shadowing frontline staff exposes the informal "shadow systems" employees invent to survive—sticky notes with software cheat codes, manual spreadsheets created to track lost orders, or unofficial phone trees used to bypass slow approval chains. These workarounds pinpoint exactly where official enterprise systems are failing.

3. Non-Intrusive Observational Research

Observational research involves silently studying how people interact with physical and digital environments without intervening. By observing body language, hesitations, spatial navigation, and micro-frustrations in waiting rooms, bank branches, transit hubs, or digital portals, researchers identify friction points that users themselves have become so accustomed to that they forget to mention them in surveys.

4. Longitudinal Diary Studies

Many services—such as applying for a mortgage, undergoing medical treatment, or completing higher education—unfold over weeks or months. Longitudinal diary studies require participants to log their real-time thoughts, screenshots, photos, and emotional reactions across their extended journey. This captures the critical gaps, waiting periods, and anxiety windows that occur between official service touchpoints.


3. The Double Diamond: Structuring Problem Discovery

Service design structures the relationship between problem discovery and solution delivery using the renowned Double Diamond framework, developed by the UK Design Council. The model illustrates how research and design alternate between divergent thinking (opening up options and exploring broadly) and convergent thinking (focusing and defining tightly).

Diamond 1: Finding the Right Problem

  • Phase 1: Discover (Divergent): The process begins by opening up the problem space completely. Instead of accepting the initial project brief at face value, researchers conduct field research, interviews, contextual observations, and competitive audits to gather broad human and operational insights.
  • Phase 2: Define (Convergent): The team synthesizes raw research data to narrow down the noise. They map customer journeys, pinpoint root causes, identify systemic bottlenecks, and reframe the core issue into actionable problem statements—often phrased as "How Might We..." challenges.

Diamond 2: Finding the Right Solution

  • Phase 3: Develop (Divergent): Only after the problem is strictly defined does solution generation begin. Cross-functional teams brainstorm wide-ranging concepts, draft storyboards, and explore diverse operational models.
  • Phase 4: Deliver (Convergent): The team prototypes, tests, refines, and implements the most effective solutions, validating them through real-world pilot runs before full enterprise deployment.

The fatal mistake most organizations make is jumping straight to Diamond 2. They spend millions developing and delivering solutions for a problem they never took the time to discover or define.


4. Reframing Problems: Moving from Symptoms to Root Causes

A primary output of qualitative research is the ability to reframe problem statements. Reframing takes a narrow, symptom-level complaint and elevates it into a systemic, human-centered opportunity.

Consider the real-world reframing examples below:

Example 1: Public Transportation Network

  • Initial Symptom/Request: "Commuters are complaining about bus delays; we need to build a new mobile app that tracks bus arrival times down to the second."
  • Research Insight: Field observation revealed that commuters were comfortable waiting 10–15 minutes if they knew why delays occurred. Panic and anger occurred when buses disappeared from display boards without explanation.
  • Reframed Problem Statement: "How might we provide clear, honest communication and visual reassurance during unexpected transit disruptions so passengers feel informed and in control?"

Example 2: Banking & Wealth Management

  • Initial Symptom/Request: "Young adults aren't opening savings accounts; we need to gamify our mobile banking app with badges and reward points."
  • Research Insight: In-depth qualitative interviews showed that young adults felt overwhelmed by financial jargon and anxious about unpredictable monthly expenses, causing them to avoid looking at their bank accounts entirely.
  • Reframed Problem Statement: "How might we demystify daily budgeting and build financial confidence so young adults feel empowered to set aside money stress-free?"

5. Overcoming Institutional Resistance to Research

Despite the overwhelming benefits of research-led design, service design teams frequently encounter institutional pushback. Stakeholders may view research as an unnecessary delay, an added expense, or a threat to existing project timelines.

Here is how service design leaders overcome common institutional objections:

Objection 1: "We don't have time for research; we need to launch in three months."

The Counter-Strategy: Highlight the massive cost of rework. Shipping a flawed product or service on time guarantees that you will spend the next six months in fire-fighting mode, patching bugs, dealing with customer support backlogs, and re-engineering failed workflows. Research doesn't delay projects—it prevents catastrophic rework later.

Objection 2: "We already know our customers; we have years of quantitative analytics."

The Counter-Strategy: Demonstrate the blind spots of quantitative data. Show how analytics track user actions but completely obscure user intent, confusion, and emotion. Pair a chart showing drop-off rates with a 2-minute video clip of a real user struggling, hesitating, and expressing frustration during a qualitative usability test. Human video evidence instantly shifts executive mindsets.

Objection 3: "Qualitative research with 15 people isn't statistically significant."

The Counter-Strategy: Clarify the difference between statistical validation and behavioral discovery. You do not need thousands of participants to uncover core usability flaws or operational friction. In qualitative research, studying 5 to 12 well-chosen participants per persona group routinely exposes 80% to 90% of the primary usability and process breakdowns.


Curiosity as a Strategic Advantage

The most innovative, resilient organizations in the world do not succeed because they have better solutions from day one. They succeed because they possess the institutional humility and relentless curiosity to ask better questions.

By prioritizing qualitative research, field observation, and contextual empathy, organizations protect themselves from the immense waste of solving the wrong problems. Investing in research before committing to solutions transforms service delivery from a game of expensive guesswork into a precise, human-centered science—ensuring that every system, process, and interface built truly serves the real people who depend on it.

1. What Is Service Design—and Why Does It Matter?

Core principles of service design

An accessible introduction to service design, moving beyond products and interfaces to the complete experience people have with a service.

2. Designing for Real People: The Human Side of Services

Putting customers first in service design

Why empathy, lived experience, accessibility, trust, and dignity should be the foundation of service design.

3. From User Journey to Service Journey

Understanding the full experience

Journey mapping and how a customer's experience connects with frontline staff, processes, policies, technology, and infrastructure.

4. Finding the Real Problem: Research Before Solutions

How real is the business problem?

How interviews, observation, contextual research, and qualitative insights prevent organizations from solving the wrong problem.

5. Service Blueprints: Seeing What Users Cannot See

Discoveries that become the design foundations

Service blueprints and how frontstage and backstage processes shape the user experience.

6. Designing Services with, Not Just for, People

Together with the customer is better

A practical exploration of co-design, participatory design, and involving communities and frontline workers in decision-making.

7. The Frontline Is the Service

Interface is the experience

Why frontline employees are not simply service delivery mechanisms—and how their tools, incentives, constraints, and experiences affect outcomes.

8. Designing for the Last Mile

Bridging the customer experience accessibility and availability gap

Exploring the gap between a service as designed on paper and how it actually reaches customers, particularly in complex or resource-constrained environments.

9. From Insight to Intervention: Turning Research into Action

Actionables

How service designers translate research findings into opportunity areas, concepts, prototypes, and actionable interventions.

10. Prototyping Services Before Scaling Them

Managed Scaling

Why services should be tested in small, low-risk ways before large-scale implementation.

11. Measuring What Matters in Service Design

Measuring effectiveness

Moving beyond vanity metrics to experience, accessibility, adoption, trust, effectiveness, equity, and system-level outcomes.

12. Service Design as a Capability, Not a Project

Shaping the best of customer experiences

How organizations can embed service design into strategy, teams, governance, and everyday decision-making.