Practical empathy and the anthropology of action in solution design based on Seth Godin's concepts

• • 🇵🇱 Polski

The article critiques a design approach that equates success with technical efficiency or formal procedural correctness. The author posits that the actual utility of a solution stems not from its specifications, but from its fit within a specific situation of human action and the real capabilities of the recipient. To avoid anthropological errors, the designer must move from superficial optimization toward 'practical empathy'—understood not as emotional resonance, but as a rigorous cognitive stance. The text integrates concepts such as Jobs to Be Done, situated action anthropology, and the ethics of care to demonstrate that responsible design requires triangulation of research methods, user participation, and an awareness of power structures. Ultimately, the author argues that the goal of innovation should not merely be increasing convenience, but expanding actual human agency within a specific social and institutional context, making design an ethical act rather than just an engineering one.

Practical empathy and the anthropology of action in solution design based on Seth Godin's concepts

Introduction

Modern design often mistakenly equates success with a product's technical proficiency. However, a formally correct solution can be entirely useless if it ignores the real-world context of human action.

The reader will learn how to move from superficial optimization toward practical empathy. This text analyzes why the key to innovation lies in understanding a product's function within a specific situation and the ethics of responsibility toward the end user.

Technical Proficiency Does Not Guarantee Utility

According to Seth Godin, designers often err by treating humans as predictable elements of a system. Even an efficient mechanism will fail if it overlooks the social consequences of change and the individual motivations of users.

The problem is that technical correctness does not guarantee utility. A solution may be engineered perfectly yet remain ill-suited to the actual needs of the people it is intended to serve.

An example is an IT system that operates exactly according to specifications but hinders productivity because it assumes a behavioral model different from the one employees actually use in their natural environment.

Practical Empathy as a Cognitive Rather Than Emotional Stance

Practical empathy is not emotional sympathy, but rather a rigorous cognitive stance. Paul Bloom warns that over-identifying with a single individual can lead to flawed judgments and the neglect of the needs of a larger group.

Sympathy alone is insufficient because intuitive reasoning about others' needs is limited by differences in economic status or culture. A systematic confrontation of assumptions with the actual experiences of users is required.

A responsible designer must combine sensitivity toward the individual with the rigor of representativeness and an analysis of collective consequences, avoiding the trap of subjectively believing they understand the user's situation.

Product Value Derives from Function in a Specific Context

In his Jobs to Be Done theory, Clayton Christensen argues that customers do not buy products for their features; instead, they "hire" them to perform a specific task. Therefore, the demographic profile of a customer does not explain the actual reasons for a purchase.

A technical feature might be processing speed, but the real need may be stress reduction or regaining control over one's time. This distinction opens new design opportunities that are invisible when analyzing product parameters alone.

An example is McDonald's milkshakes: in the morning, they served as long-lasting snacks for drivers during a boring commute, while in the afternoon, they were treats for children. The same product fulfilled two entirely different situational functions.

Summary

The most perfect tool remains useless if it is not paired with the democratization of access to resources. True design success is not an ideal product, but the expansion of actual human agency.

In a world of algorithmic optimization, the challenge is to create solutions that genuinely increase freedom rather than merely steering behavior. Success lies in the courage to reach a fair compromise where empathy meets conflicting interests.

📚 Based on

The Knot Problems Can Be Solved

Hachette UK
ISBN: 9781399645072

👤 About the book's author

Seth Godin

Akimbo

Seth W. Godin (born July 10, 1960) is an American author, entrepreneur, and former business executive renowned for his influential work in marketing, leadership, and organizational behavior. After earning degrees from Tufts University and the Stanford Graduate School of Business, Godin founded Yoyodyne, an early pioneer in digital direct marketing that was acquired by Yahoo! in 1998, where he subsequently served as vice president of direct marketing. He later founded the altMBA and Akimbo educational platforms. Godin revolutionized marketing theory by introducing concepts such as 'permission marketing'—arguing that effective promotion must be anticipated, personal, and relevant—and the 'purple cow' philosophy emphasizing remarkability. He has published more than twenty bestselling books and has been inducted into both the Direct Marketing Hall of Fame and the Marketing Hall of Fame.

Mind map: Practical Empathy and the Anthropology of Action in Design

📖 Glossary

Jobs to Be Done (JTBD)
Teoria zakładająca, że klienci nie kupują produktów, lecz „zatrudniają” je do wykonania konkretnego zadania w określonej sytuacji życiowej.
Działanie usytuowane
Koncepcja, według której ludzkie zachowanie nie wynika z sztywnego planu, lecz jest dynamiczną reakcją na bieżące okoliczności i kontekst otoczenia.
Empatia poznawcza
Zdolność do intelektualnego zrozumienia perspektywy i stanu psychicznego drugiej osoby, bez konieczności emocjonalnego współodczuwania jej stanów.
Etnometodologia
Naukowe badanie codziennych, często nieuświadomionych metod, jakimi ludzie organizują swoje interakcje i nadają sens działaniom w grupie.
Konkurencja funkcjonalna
Sytuacja, w której produkty z zupełnie różnych kategorii rywalizują ze sobą, ponieważ spełniają tę samą funkcję dla użytkownika w danej sytuacji.
Projektowanie podmiotowe
Podejście do tworzenia rozwiązań, które traktuje człowieka jako aktywnego podmiotu z własnymi celami i wartościami, a nie tylko jako odbiorcę usługi.

Frequently Asked Questions

Why might a correctly identified problem and a technically efficient response fail to produce the expected result in practice?
This happens when a solution overlooks the meaning assigned to action by the participants, their daily living conditions, and their real needs. This results from an anthropological error: treating a human being as a system element to be optimized rather than a subject with complex motivations and habits.
What exactly is practical empathy in design, and why is simply empathizing with the user not enough?
Practical empathy in design is a cognitive stance consisting of systematically confronting one's own assumptions with the actual experience of users, and combining sensitivity to individual experiences with the rigor of representativeness. Simple empathy is insufficient because a designer's subjective perceptions may be inaccurate due to cultural or economic differences, and strong emotional identification with one person can lead to overlooking the needs of a larger group of users.
Why is simply matching product features to a customer profile not enough to effectively solve a problem?
Matching features alone is insufficient because the value of a product depends on the specific situation and goal (task) that the customer wants to achieve. The key is recognizing the context of action and the circumstances accompanying the choice, rather than just analyzing technical specifications or buyer demographics.
Why does analyzing customer preferences regarding product features often fail to explain the real reasons for purchase?
Analyzing product features does not explain the real reasons for purchase because it overlooks the difference between a commercial category and a situational function. The value of a solution is often determined by a combination of factors and a specific context of use, which gives the product meaning independent of its technical properties or taste preferences.
What is the difference between a technical feature of a product and a user's actual need?
A technical feature is a characteristic of a device (e.g., operating speed), whereas an actual need concerns achieving a specific result or realizing values important to the user. This means that the customer does not desire the tool itself as an end, but rather a way to solve a problem or obtain a particular effect.
Why can declared user needs be misleading, and how can real problems be reliably diagnosed in the design process?
User declarations can be misleading because motivations for action are often unconscious, stem from habits, or are situational, and real problems often concern issues other than reported functional needs. To reliably diagnose problems, one should observe the process in its natural environment, analyzing practices under real conditions along with accompanying improvisations and informal ways of coping with limitations.
How can one reliably investigate the actual needs of a user to avoid errors resulting from the designer's excessive technical confidence?
Ethnography should be used to systematically document users' practices and observations within their work environment. It is crucial to apply method triangulation—combining field observations with interviews, administrative data, and experiments—to identify discrepancies between users' declarations and their actual behavior.
Why does ensuring the technical functionality of a product alone not guarantee its actual accessibility for users?
Functionality alone does not guarantee accessibility because the user's ability to recognize and utilize available options is key, which depends on their competencies, physical abilities, and working conditions. A technical solution may remain inaccessible if it requires knowledge or a way of operating that is foreign to the target group.
Why is focusing exclusively on the direct user experience (UX) insufficient for creating an effective solution?
Focusing solely on UX is insufficient because a product operates within a broader system of dependencies, including resource holders and those who bear the indirect consequences of interventions. An effective solution requires considering the invisible process infrastructure and analyzing hidden costs that cannot be eliminated by modifying the interface alone.
Why is simply collecting user preferences not enough to create a fair and effective solution?
Simply collecting user preferences is not enough because it may perpetuate power imbalances and overlook the situational knowledge of employees. Genuine participation in design is essential to ensure that tools support individual autonomy and democratize technological processes.
What is the difference between real co-creation of a solution with the user and ordinary consultations?
Consultations are usually limited to gathering opinions, which the designer interprets at their own discretion. Real co-creation, on the other hand, assumes the direct involvement of users in defining the problem, searching for alternatives, testing solutions, and determining success criteria.
What is the difference between designing a system that enforces specific behaviors and one that supports actual user agency?
Behavior-enforcing design focuses on nudging the user toward specific actions, which does not necessarily translate into an increase in their autonomy or competence. In contrast, design that supports actual agency creates conditions conducive to independence and a sense of influence, ensuring that actions are aligned with the user's own motivations.
Why do high product quality or formal equality of services not guarantee that a solution is actually accessible and useful for everyone?
High product quality does not guarantee usability if usage requires competencies that the recipients do not possess, or takes place in an unsuitable environment. Meanwhile, formal equality of services can be illusory, as actual accessibility depends on age, health status, financial situation, and the structure of users' caregiving responsibilities.
When does user-centered design stop being helpful and become a form of manipulation or unacceptable paternalism?
Design becomes manipulation when it exploits flaws in the decision-making process and user vulnerabilities to achieve the designer's benefits or nudge them toward actions contrary to the recipient's interests. It turns into unacceptable paternalism when the designer eliminates the user's choice, relying solely on their own interpretation of the user's best interest without adhering to the principle of proportionality.
How can one avoid excluding certain groups of users while effectively designing with limited resources?
To avoid exclusion and design effectively with limited resources, one should identify groups overlooked by standard models and include them in the solution creation process. It is worth applying the Smallest Viable Audience concept, concentrating efforts on a specific group of recipients with clearly defined needs instead of designing for everyone.
How does target audience selection in business differ from the design of public and social services?
Businesses can freely choose a specific group of customers to maximize product utility and economic efficiency. In contrast, public institutions must be guided by the logic of justice, equal treatment, and accessibility, prioritizing the needs of those in the most difficult situations instead of excluding entitled recipients.
Are participatory processes and empathetic user research always fair and representative?
These processes are not always fair because they are often dominated by confident and available individuals, while hard-to-reach groups remain underrepresented. This can lead to the reproduction of inequalities or exploitative relationships, where users' knowledge is utilized without providing them with real benefits or influence over the outcome.
How can empathy for the user be combined with ethical rigor and institutional realities in the design process?
An empathic-causal design model should be applied, which combines the recognition of actual user needs with legal analysis, privacy protection ethics, and the study of causal mechanisms. This process requires a distinction between empathy and the legitimacy to act, as well as consideration of power distribution and normative social consequences.
Is empathy alone sufficient for a fair resolution of a problem in a situation of conflict of interest?
No, empathy alone is not enough because it serves only a cognitive function and allows for a better understanding of the parties' motivations, but does not constitute an independent criterion of justice. In situations of conflict of interest, it is essential to supplement it with responsible compromise, negotiations, and transparent dispute resolution procedures.
How does practical empathy in design differ from simply complying with user wishes, and how should conflicts of interest be handled?
Practical empathy is the ability to recognize a person within their actual circumstances, not an obligation to comply with all wishes, which may conflict with the law, organizational values, or available resources. In the case of conflicts of interest, understanding others' perspectives must be supplemented by negotiation theory and fair compromise, allowing for firm decisions to be made without disregarding people's experiences.

🧠 Thematic Groups

Tags:

More in: Szkatułka kosztowności

 Content is created by Fundacja Dobre Państwo.
Edited and published by APA ONE, the Foundation's own AI-based editorial system.