Couverture de The Experience Strategy Podcast

The Experience Strategy Podcast

The Experience Strategy Podcast

De : Dave Norton Aransas Savas and Joe Pine
Écouter gratuitement

Offres de saison | 0,99 € par mois pendant les 3 premiers mois

5,99 €/mois par la suite. Des conditions s’appliquent. Annulation mensuelle possible.
With over 100 episodes, the Experience Strategy Podcast is that secret superpower that helps strategists around the world grow their business acumen. Your hosts, Aransas Savas, Joe Pine, and Dave Norton discuss the most important topics in the business world, but they do it by focusing on the experiences and transformations that customers attain.2024 Economie Management Management et direction
Épisodes
  • Time Value — The Measurement Framework Every Intelligent Company Needs

    Time Value — The Measurement Framework Every Intelligent Company Needs
    Sep 24 2026
    The Experience Strategy Podcast | theexperiencestrategist.substack.com Part four of a four-part mini-series unpacking the frameworks in Dave Norton's new book, Human Context: How Intelligent Companies Build Customers. You can build the right market strategy, identify the right situations, understand your customer's mode — and still not know if what you built is actually working. Time value is the measurement framework that closes that gap. In this final episode of the series, Dave explains the four categories of time value, how they map to the Stupid/Dumb/Smart/Genius framework, and why AI creates a compounding effect that changes what customers expect from every minute they spend with a product. What's in This Episode Why time value is the right measurement. NPS, sales lift, likelihood to buy — these are all useful, but they measure the company's outcomes. Time value measures the customer's outcome. When someone uses a tool, an app, a service, or an AI, what they're actually asking is: was this worth my time? That question has always mattered. Now, with AI compressing what used to take months into hours, customers' expectations for the value of their time are rising sharply — and companies that measure with yesterday's metrics will miss what's actually happening. The four categories. The framework has been part of Dave and Joe's work for nearly twenty years, and it's now a central chapter in Human Context: Time wasted — the experience consumed time and delivered nothing. The baseline failure case.Time well saved — the experience completed something faster than the alternative. Adjusting a thermostat with Alexa. Quick, functional, done.Time well spent — the experience was worth being in, beyond just efficiency. Engagement mattered. The person was present and got something from it.Time well invested — the time spent now pays dividends later. A skill developed, a relationship deepened, an outcome that compounds. Any experience — dumb, smart, or genius — can land in any of these categories. A pen and paper can be time well invested. A sophisticated AI tool can be time wasted. The category isn't determined by the technology; it's determined by the customer's experience of it. The compounding effect of genius solutions. With AI, there's a fifth dynamic layered on top: compounding. When a well-trained AI starts doing in hours what used to take months, customers don't just experience time saved — they experience something closer to a superpower. And that changes the baseline expectation. The more capable the tool appears, the less tolerance there is for failure. Dave's point: we need measurement frameworks that account for this — because evaluating a genius solution by the same standards as a dumb one misses what's actually at stake. Stupid is in the incident, not just the category. The episode's sharpest clarification comes through a live case study from the TV show The Pit: a hospital AI tool takes dictation and charts for the doctor, immediately freeing up time. But it mishears a drug name and records the wrong medication. Was it time wasted? Joe's framing cuts through the debate cleanly: an incident can be stupid even when the overall tool is smart. The doubter on the show sees the error and says the whole thing is risky. The loyalist says you still have to proof your work. Both are right in their own frame. Dave's conclusion: if errors like that happen repeatedly, the tool loses value. If it happens occasionally and the system learns from it, the tool gets better. The key variable is whether the person using it can train it. The trainability gap. Companies haven't caught up to what consumers now expect from AI tools. People who use Claude, ChatGPT, or Gemini daily have learned to train their tools — to shape responses, correct mistakes, build better versions over time. Then they open Copilot and find a system that can't learn the way they need it to. Dave's diagnosis: the doctor in The Pit should be able to flag the wrong drug and have the system remember. That's what closes the gap between smart and genius. And it's what most enterprise AI deployments are still missing. What's actually working right now. A quick round of AI tools the hosts are finding genuinely useful: A transcription app (beginning with G) that can handle multi-person conversations at a table, distinguishing speakers in real time.OpenAI's voice interface — Dave's son switched from Claude to ChatGPT specifically for this, and Dave says Siri now feels painful by comparison.Google's paid Workspace / Gemini integration — Aransas is getting smart email suggestions, natural-language search across past conversations, and contact introductions that pull in context automatically. Useful enough to feel slightly unsettling. Three questions for measuring dumb experiences. For solutions with no intelligence layer, Dave offers a simple diagnostic: Did I accomplish what I set out to do? How engaged was I with the ...
    Afficher plus Afficher moins
    18 min
  • Modes — The Missing Variable Between Situation and Personalization

    Modes — The Missing Variable Between Situation and Personalization
    Sep 18 2026
    The Experience Strategy Podcast | theexperiencestrategist.substack.com Part three of a four-part mini-series unpacking the frameworks in Dave Norton's new book, Human Context: How Intelligent Companies Build Customers. Most companies build their entire models around habits and routines. But the number one behavior people exhibit today isn't a habit or a routine — it's mode acquisition. People move fluidly between modes all day, they're fluent in the language of them ("I'm in writing mode, don't talk to me"), and they expect the companies they interact with to understand where they are. Most companies don't. This episode explains what modes are, how they connect to situational markets, and why knowing someone's mode tells you more about how to serve them than any demographic ever could. What's in This Episode The definition that matters most — and it's one word. A mode is a mindset and a set of behaviors that a person gets into temporarily. That last word is what separates modes from habits (permanent patterns) and routines (permanent structures). Right now, the three hosts are in podcast mode. When they hit stop, they won't be. Joe takes a different tone between episodes. Aransas's voice changes. Dave gets Joe's "I'm in writing mode" texts. People are already living this way — the framework just names what's happening. The ballpark and the batter. To connect modes back to the last episode: if situational markets are the ballpark — the bounded context, the market you're going after — then modes are the batter. The same situation can contain many different modes. Two people can both be in the situation of choosing a college for their daughter. One is in full mommy mode — relational, emotionally loaded, cross-domain in its implications (financial, personal, professional, aspirational). Another is an adult returning to education for themselves, in a more self-directed, pragmatic mode. Same situational market. Completely different mode. Completely different support needed. Joe's extension makes it even richer: everyone on the field is in a different mode at every moment. The batter stepping up with a runner on third is in a different mode than when he's in the dugout. And if you know someone's in dugout mode — Dave's point is clear — sunflower seeds are your product. Modes cross demographics. That's the whole point. Aransas in mommy mode could be any age, any income, any geography. The mode — not the demographic — tells you what she needs. Joe names the full stack of jobs that mode carries with it: functional, emotional, social, and aspirational. Know the mode, and you know the context. Know the context, and you can personalize in a way that demographic data never allows. How modes, situations, and jobs connect. The three frameworks work together as a system. Jobs to be done describes what the customer needs broadly — the functional, emotional, social, and aspirational outcomes they're hiring for. Situational markets describe the bounded context: the when-statement, the market that's been identified and sized. Modes describe how — the specific mindset, energy, and intention the person brings to that moment. Dave's summary: situation tells you the market, mode tells you how they're experiencing their time within it. Know all three, and you have context that's genuinely actionable. Why modes replace personas — and why that matters. Personas imply a static, monolithic person. Modes are the opposite: dynamic, contextual, temporary. A person is not their persona. They are whoever they are in this moment, in this situation, in this mode. That concept changes what you build, what you say, and how you show up. The mode map in Human Context gives companies a practical tool: map your specific situations to the modes customers are likely to enter, and build for those combinations rather than for a type of person. Most companies are leaving this on the table. Dave has been developing the modes framework for over a decade. He remains genuinely surprised that more companies don't use it — especially now, when the language of modes is so embedded in how people describe themselves. The person who texts "I'm in writing mode" is handing you a direct signal about their context. Most companies have no system for receiving it. Get the Book Human Context: How Intelligent Companies Build Customers by Dave Norton is available now on Amazon (Kindle and print) and on Dave's Substack. The book includes a mode map framework and industry-specific workbooks showing how to apply modes, situational markets, and the other frameworks to your category. Find the hosts by name or as The Experience Strategist at theexperiencestrategist.substack.com.
    Afficher plus Afficher moins
    16 min
  • Situational Markets — The Framework That Replaces Traditional Market Strategy

    Situational Markets — The Framework That Replaces Traditional Market Strategy
    Sep 11 2026
    The Experience Strategy Podcast | theexperiencestrategist.substack.com Part two of a four-part mini-series unpacking the frameworks in Dave Norton's new book, Human Context: How Intelligent Companies Build Customers. Every time you segment your target audience by who they are, you limit the number of people who could buy from you. That's the uncomfortable truth at the center of this episode — and the reason situational markets may be the most practically disruptive framework in Human Context. Dave and Joe trace the idea from Joe's original "markets within" concept through to how AI is already forcing companies to make this shift whether they're ready or not. What's in This Episode Where the idea came from: Joe Pine's "markets within" framework. Joe developed a framework he calls the bow tie — narrow in the middle, wide on both ends. On the left is the traditional marketing view: a company has a market, which it segments into smaller groups. On the right is the insight that flips everything: there are multiple markets within each individual customer. We want different things at different times, in different situations, in different contexts. The pivot point — where the bow tie narrows — is the recognition that every customer is their own market. Situational markets is Dave's extension of that idea into something companies can operationalize. The Amazon account problem as a live demonstration. Joe and his wife share an Amazon account. She buys Kindle fiction. He buys business and theology books. Amazon treats them as one customer and gets it wrong for both of them — recommendations that belong to one land with the other, constantly. Dave's point: even without the shared account problem, you and Joe are essentially the same demographic. Similar age, same household. Classic targeting tools wouldn't distinguish you at all. That's exactly what's broken. The situation — who's shopping, for what, in what mindset — is the only thing that actually tells you something useful. Every time you segment the "who," you shrink the market. Dave landed on this as one of the book's most clarifying insights. Six demographic segments means six defined targets — and an unknown number of people excluded because they show up in the situation sometimes but don't fit the profile always. Situational markets are inclusive by design: anyone who finds themselves in the situation is a potential customer. You're not narrowing to a type of person. You're identifying a moment that any type of person can enter. This is what Clayton Christensen was pointing at. Dave connects situational markets to Christensen's "Marketing Malpractice" — the argument that the job, not the customer, is the unit of analysis. Christensen developed this through Jobs to Be Done. Dave's situational markets framework arrives at the same threshold from a different direction: stop asking who your customer is, start asking what situation they're in. The analytical tools that worked for demographic segmentation — sizing, prioritization, value creation — all transfer. The difference is you're no longer excluding people who don't fit a profile. What a situational market actually is. Three elements: A when statement. "When I am making a hotel reservation." "When I want restaurant-quality pizza at home." "When I want water at a concert but don't drink alcohol and want to look cool." The when statement creates a boundary around the context — something specific enough to design for.The who stays generic. As generic as possible. The situation defines the entry point. Don't pre-filter by demographic.Size it. A situation isn't a market until you can size it. It also needs to be a situation the customer actually wants to hire you for — not just something that arises. Dave spends significant time in the book on how to size situational markets, because that's what separates a use case from a genuine market opportunity. Three types of situations. Obvious situations — making a hotel reservation, back-to-school shopping, holiday gifting — are already well-understood and competed over. Less obvious situations are where differentiation lives. And then there are externally-driven situations: COVID is the clearest example, a time-bound, universal situational market that few companies were built to serve and even fewer anticipated. The examples that make it concrete. Liquid Death — built entirely around the situation of wanting water at a concert without alcohol and without a plastic bottle, while still looking like you fit in. The situation defined the product, the design, and the brand.Ooni pizza ovens — when I want restaurant-quality pizza at home. Aransas's read: it's less about the pizza than about looking like you know how to make one. Either way, the situation is specific, sizeable, and worth designing for.Google Search — what if Google had decided academics were the primary users and targeted accordingly? Instead, they said: whenever someone ...
    Afficher plus Afficher moins
    16 min
adbl_web_anon_alc_button_suppression_t1
Aucun commentaire pour le moment