Field Studies Methodologies

Why do some qualitative studies generate groundbreaking insights while others barely scratch the surface? The secret is not in the data collected, but in matching your methodology to your research goals. The 5 qualitative research methods nobody talks about: 1. Phenomenology • Perfect for understanding perceptions • Uses deep interview analysis • Captures lived experiences 2. Ethnography • Based on extended fieldwork • Documents cultural patterns • Gives insider perspective 3. Narrative Inquiry • Uses conversations & artifacts • Finds patterns in experiences • Tells people's stories 4. Case Study • Answers specific questions • Uses multiple data sources • Creates rich context 5. Grounded Theory • Perfect for unexplored topics • Analyzes data continuously • Builds new theories Pick your method based on your goal: → Want experiences? Use phenomenology → Need cultural insights? Try ethnography → Looking for stories? Go narrative → Seeking answers? Case study works → Building theory? Grounded theory fits Most researchers fail because they pick the wrong method for their research question. The right method = better research. 🗞️ Join 7,278+ researchers on my weekly newsletter: https://lnkd.in/e4HfhmrH P.S. Do you check method-research-question fit?

Qualitative research in UX is not just about reading quotes. It is a structured process that reveals how people think, feel, and act in context. Yet many teams rely on surface-level summaries or default to a single method, missing the analytical depth qualitative approaches offer. Thematic analysis identifies recurring patterns and organizes them into themes. It is widely used and works well across interviews, but vague or redundant themes can weaken insights. Grounded theory builds explanations directly from data through iterative coding. It is ideal for understanding processes like trust formation but requires careful comparisons to avoid premature theories. Content analysis quantifies elements in the data. It offers structure and cross-user comparison, though it can miss underlying meaning. Discourse analysis looks at how language expresses power, identity, and norms. It works well for analyzing conflict or organizational speech but must be contextualized to avoid overreach. Narrative analysis examines how stories are told, capturing emotional tone and sequence. It highlights how people see themselves but should not be reduced to fragments. Interpretative phenomenological analysis focuses on how individuals make meaning. It reveals deep beliefs or emotions but demands layered, reflective reading. Bayesian qualitative reasoning applies logic to assess how well each explanation fits the data. It works well with small or complex samples and encourages updating interpretations based on new evidence. Ethnography studies users in real environments. It uncovers behaviors missed in interviews but requires deep field engagement. Framework analysis organizes themes across cases using a matrix. It supports comparison but can limit unexpected findings if used too rigidly. Computational qualitative analysis uses AI tools to code and group data at scale. It is helpful for large datasets but requires review to preserve nuance. Epistemic network analysis maps how ideas connect across time. It captures conceptual flow but still requires interpretation. Reflexive thematic analysis builds on thematic coding with self-awareness of the researcher's lens. It accepts subjectivity and tracks how insights evolve. Mixed methods meta-synthesis combines qualitative and quantitative findings to build a broader picture. It must balance both approaches carefully to retain depth.

Most PhDs misuse methodology. Picking methods too early = PhD trap. Research onion: Philosophy → Approach → Strategy → Methods A student showed me a thick methodology chapter. Charts, interviews, software, tables. One question broke it: why these choices? —Nothing connected. —The chapter looked busy. —The logic was missing. This image is the research onion. It shows that methodology = decisions, not decorations. Each layer answers a question students rarely write down. Here is what students miss, with clear contrasts: 1. Philosophy Missed question: what view of reality guides the study? ✖️ “I used questionnaires and interviews.” ✔️ “The study adopts interpretivism because user comfort is shaped by perception, not just measurable variables.” 2. Research approach Missed question: am I testing theory or building it? ✖️ “This study is deductive and inductive.” ✔️ “A deductive approach is used to test an existing daylight performance theory.” 3. Strategy Missed question: what is the overall logic of inquiry? ✖️ “Five interviews were conducted as a survey.” ✔️ “A case study strategy examines design decisions within a single housing project.” 4. Method choice Missed question: one method or integrated methods? ✖️ “Mixed methods were used.” ✔️ “Simulation results were integrated with interviews to explain performance outcomes.” 5. Time horizon Missed question: snapshot or change over time? ✖️ “Data were collected from users.” ✔️ “A cross-sectional design captured user responses at one point in time.” 6. Techniques and procedures Missed question: how exactly is data analysed? ✖️ “SPSS was used for analysis.” ✔️ “Regression analysis tested the relationship between window size and daylight availability.” —Good research is not about more methods. —It is about fewer contradictions. —Methodology is the spine. ♻️find this useful? —like + comment + repost —🔔follow Edidiong Ukpong(PhD Architecture) for more

BITS Design School Mumbai students participating in Design Methods 101, completed their interview field visits with specific actors they identified and observed in their work context. Fifteen teams chose very different situations in various neighborhoods in Kalyan, including a hospital, a hotel, several restaurants, a retirement home, and even a rainwear street stall shop. Before conducting interviews with their specific actor, teams crafted a stakeholder map of observed actors, identifying larger variables that affect their situation. They also formulated core and extended questions for their actor(s) and an interview protocol. Due to the monsoon rains, it was difficult for student teams to connect with their chosen businesses, and they had to revert to phone interviews. Some teams took local transportation and connected with their actors to ask key questions. The goal was to better understand what was observed by asking clarifying questions about how they thought and felt about what they were doing. Students brought the interview data back and processed interview results in an answer matrix to find patterns, define the actual job to be done by their chosen actor, identify five key challenges that face their actor, and use the five whys to identify possible root causes. They also identified specific secondary research to fill in the gaps between what they thought they knew and what they did not know. From the individual written reflections, some interesting quotes added details to how the teams completed their interviews : • One of the biggest hurdles was connecting with the locals. Initially, many, including the owner of the mess, seemed hesitant, appearing either too busy or wary of engaging with us.  • What looked simple on paper: schedule interviews, talk to participants, and capture insights, quickly became a test of patience, coordination, and adaptability.  • . . . it showed us that design research works best when observation, interviews, and secondary sources are used together; each one adds a different layer of understanding. • Observations from the field had given me a strong sense of “what” people were doing, but the interviews allowed me to explore the “why” behind their actions.  • The interview didn’t replace our observations; instead, it gave them meaning, revealing the why behind the what What student teams have come to realize is that designing is more than interacting and empathy, and that individuals and groups of people are complicated to collaborate with. They are inconsistent, contradictory, and ultimately messy. But that is what design has to work with - the messiness of artificial systems, and all the disconnects that go with life. They are starting to realize that contradictions and ambiguities are inherent to the design process. Thanks to Harroop Kaur, Mansi Wadekar, and Gautham Arumugam for their collaboration and abilities to manage 180 freshmen over nine weeks. #bitsdesign #designmethods 

**NOT ABOUT CLAUDE DESIGN** Your team isn't doing too little research... it's probably just doing the wrong kind. Do you feel like you dig into a pile of data but can't seem to find any relevant answers? Then this is for you, friend ↓ An NN/g framework places every major research method along two axes: (1) Attitudinal vs. behavioral (i.e. what users say vs. what they do) and (2) Qualitative vs. Quantitative (i.e. why vs. how many). That creates 4 distinct quadrants, each answering a specific type of question. Most teams default to the bottom-left quadrant because these tend to be self-report options that are cheaper, simpler, and, therefore, faster to execute. Send out surveys... Do some card sorts and concept tests... Compile a seemingly impressive spreadsheet... Call it a day. But the bottom-left quadrant is often a convenience trap because those methods rarely tell you how users actually move through a product, where they get stuck and give up, or why a checkout flow that tested extremely well in a survey ends up delivering a 34% drop-off in production. Here's the taxonomy and why each quadrant exists: → Attitudinal + Qualitative | Top-left quadrant User interviews, diary studies. Surfaces the why behind attitudes. Best for discovery, mental model mapping, early-stage direction. → Attitudinal + Quantitative | Bottom-left quadrant Surveys, card sorting. Measures stated preferences at scale. Useful yet limited to only what users report, forcing their holistic feedback into a spreadsheet. → Behavioral + Qualitative | Top-right quadrant Usability testing, contextual inquiry, field studies. Reveals how real people move through your product in the real world. Often underused when a team is under-resourced. → Behavioral + Quantitative | Bottom-right quadrant A/B testing, analytics, heatmaps. Excellent for proving what's broken, but it doesn't explain why. Maze's 2025 research report found that surveys are the go-to method for over 3/4 of teams... even though they only capture what users say, not what they do. Ultimately, broad familiarity isn't a research strategy. Comment below with the emoji that matches your team's current research stack: 📋 Surveys only 🧪 Mixed methods 🔥 What research...? #uxresearch #uxdesign #productdesign #userresearch #designstrategy ⸻ 👋🏼 I’m Dane—a designer creator + mentor. 🙃 Rated PG-13 for hard facts + adult language. ❤️ If you liked this, a 👍🏼 would be rad—& sharing it would be legendary. 💾 Save this for later if you found it helpful. ➕ Follow for more of my shenannies all up in yo' feed.