What Postphenomenology Teaches Journey Designers
Most customer experience frameworks treat the customer as a subject with preferences: someone who wants things, dislikes other things, and makes decisions based on the balance betw
Most customer experience frameworks treat the customer as a subject with preferences: someone who wants things, dislikes other things, and makes decisions based on the balance between them. This is a useful simplification, but it misses something important about how people actually experience technology and services. The philosophical tradition of postphenomenology offers a richer account — and practical implications for journey designers who want to understand not just what customers prefer, but what they actually live through.
Postphenomenology, developed most accessibly by Don Ihde and extended by Steph Stienstra and others, examines how human beings relate to the world through technologies. The core insight is that technologies are not neutral conduits for human intention — they shape the relationship between the person using them and the world they are engaging with. A GPS changes not just how you navigate but how you relate to spatial knowledge. A customer portal changes not just how you interact with a company but how you understand your own relationship to that company's services.
The Transparency Trap in Journey Mapping
One of postphenomenology's most useful concepts for journey designers is the distinction between technologies that are transparent (where the tool disappears into use) and technologies that are conspicuous (where the tool itself becomes the focus of attention).
When a customer is using a product smoothly — when the interface disappears into the action they are trying to accomplish — the technology is functioning transparently. The customer is experiencing the world through the product, not experiencing the product. When the interface breaks, when the process is confusing, when the next step is unclear — the technology becomes conspicuous. The customer is now dealing with the tool, not accomplishing their goal.
Journey management's experience scoring system is partly a measure of this dynamic. A score of –2 at a particular stage means the technology at that stage is profoundly conspicuous: the customer's attention is consumed by dealing with the product rather than by accomplishing what they came to do. A score of +2 means the technology has become transparent: the product is enabling the customer to do what they want without demanding attention itself.
"Design that achieves transparency doesn't feel like design at all to the person using it. They're not thinking about the interface. They're thinking about what they came to do."
Embodied Experience and Insight Types
Postphenomenology also helps explain why the four insight types — needs, pains, gains, pressures — are structured the way they are. Needs correspond to what the customer is trying to accomplish: the embodied intention that brings them to the product. Pains correspond to the moments when the technology becomes conspicuous: when the customer's experience of the tool interrupts their engagement with their goal. Gains correspond to moments when the technology enhances the customer's relation to their goal, creating value that exceeds what they came for.
This framing reorients the design question. It is not "how do we satisfy customer preferences?" It is "how do we design interactions that become transparent in use — that disappear into the customer's engagement with their own goals?" The answer requires understanding those goals from the inside, which is precisely what jobs-to-be-done research attempts to do.
The Cultural Dimension
Lucy Suchman's foundational work, "Plans and Situated Actions," adds another layer: real behavior diverges from scripts. The journey map is, in a sense, a script: an idealized sequence of customer actions that the organization has designed for. Real customers deviate from the script constantly — because their context is different, their goals are slightly different, their prior experience with similar products shapes their expectations in ways the designer did not anticipate.
Journey management's discovery process is specifically designed to surface these deviations: the moments where the designed experience and the lived experience diverge. The customer insight that reveals a deviation is more valuable than the one that confirms the design worked as intended — because it reveals something about the actual conditions of use that the map did not anticipate.
Postphenomenology is not a design method. It is a reminder that the people moving through your journeys are not users with preferences — they are human beings with embodied relationships to the tools you build. That reminder changes how you ask the research questions and what you listen for in the answers.
Back to Writing