AI Chatbot Checkbox
An AI chatbot can become a purchasing checkbox rather than a differentiator. Sean discusses the distinction between a common feature and a distinctive customer capability.
TranscriptEVERGENCES / IDEAS IN MOTION
Short videos from Sean Everett on AI, customer discovery, product design and growth. Watch a clip, explore its ideas and read the transcript.

86 videos
An AI chatbot can become a purchasing checkbox rather than a differentiator. Sean discusses the distinction between a common feature and a distinctive customer capability.
TranscriptA house-building analogy separates changing tools from the outcome a customer still needs. AI is considered as a tool for delivering that outcome.
TranscriptWhat useful new capability could make a customer’s life faster, better, easier or cheaper? Sean asks how a product could create meaningful customer value.
TranscriptA service buyer may value closed-won customers over leads at the top of a funnel. Sean distinguishes an outcome from an intermediate activity.
TranscriptCustomer discovery is a listening exercise. Start with understanding rather than selling.
TranscriptTechnology should support the human experience. Adding a feature is only useful when the experience gets better.
TranscriptA useful partnership question: what can we create together that neither of us could create alone?
TranscriptChoose the task, check that the tool can do it, then review the result. Execution is only part of the workflow.
TranscriptStart with work that matters to you, then ask what value someone else would pay for.
TranscriptTrying, failing and learning can improve the next attempt. Experience matters when tools change quickly.
TranscriptAsk about a real problem. Listen to the answer. Then follow the thread with a useful question.
TranscriptHow are decisions made? Who decides, how long does it take, and what evidence matters?
TranscriptThe test of a capability: can you deliver it again, consistently, over time?
TranscriptSeparate internal workflow improvements from the experience your customer sees. Both deserve a deliberate decision.
TranscriptIndividual skills can look ordinary. The useful combination you build over time can be much more distinctive.
TranscriptThere are only so many hours in a day. Think about the help that would actually support what you are trying to create.
TranscriptA design exercise: put the constraints aside briefly and imagine one useful thing that would make daily life easier.
TranscriptA house is a useful way to picture pace layers: the frame, the walls, the furniture and daily life change on different schedules.
TranscriptBuilding something helpful also means thinking about its second- and third-order consequences.
TranscriptSeparate the opinion from its underlying principles and evidence. Ask what another person could independently check.
TranscriptAn ecosystem can create value beyond a fight over the same customer. What could grow the pie?
TranscriptPut the decision in the middle. Test the idea together rather than treating disagreement as a personal attack.
TranscriptAsk what customers keep choosing, then ask why. The reasoning behind a preference can be more useful than the preference alone.
TranscriptA design thought experiment: what if ideas and AI architectures could be manipulated like physical objects?
TranscriptAn outcome often depends on more than one tool: people, communication, purchases and coordination. Where can you reduce that work?
TranscriptBefore rebuilding a system, distinguish its durable structure from its faster-changing layers.
TranscriptAI, robotics and other technologies are tools. Which mission are they serving?
TranscriptIf you will work on a problem for years, what keeps you drawn to it? Start with a fascination that can sustain the work.
TranscriptOnce baseline requirements are met, avoid an endless feature-copying loop. What is the larger strategic choice?
TranscriptWhen decision principles are encoded into software, their effects reach customers. Be deliberate about what you encode.
TranscriptAn AI use case needs more than code: define the behaviour you want, then check the result.
TranscriptAsk which principles support a claim, then ask for the evidence.
TranscriptKeeping the business running and improving it are different jobs. Growth asks for investment in product, service and customer experience.
TranscriptTry asking how two options feel different, why someone would choose one, and what feels expensive. Listen to the answer.
TranscriptA learning advantage depends on the pace of improvement, not just where you started. What helps your team learn faster?
TranscriptA quiet starting point for taste: remove the noise and ask what genuinely draws your attention.
TranscriptYour experiences, interactions and ways of seeing the world can become material for new products and services.
TranscriptSean describes strategy through decisions about the market, team, brand, product, service and resources.
TranscriptDescribe the outcome your customer needs, then work back to the product that helps deliver it. Make the market message match what you can actually do.
TranscriptA hypothetical wishlist for an AI guide that could research, remember and help with everyday tasks; not a claim about an available product.
TranscriptLook beyond the visible influencer or big brand: ask where the idea came from, then follow the chain back. What source would you study more closely?
TranscriptListen for the values, decision patterns and purchase criteria beneath the answer. What would change your next product decision?
TranscriptCharts need a through line: what customer frustration or value does the strategy address? Make the point clear.
TranscriptNew capabilities can start with a structural problem in the existing system. What would you change for customers and partners?
TranscriptSean considers how human connection and shared values might matter as creating products becomes easier.
TranscriptSean argues that product work goes beyond delivery processes and passing along customer feedback, while explaining what he thinks a product discussion should address.
TranscriptSean contrasts investing in new capabilities through discovery and creative thinking with automating the tasks already in a day-to-day workflow.
TranscriptHistorical data can support differentiation when losing it would materially reduce customer value. Sean contrasts accumulated useful history with data collected for a single interaction.
TranscriptSean illustrates bottom-up revenue planning: add what individual customers pay over time rather than relying only on a top-down market-share assumption.
TranscriptSean uses an illustrative pottery story to contrast learning through repeated attempts with trying to perfect a first version. This is a teaching metaphor, not a verified experiment.
TranscriptSean describes pairing a new capability with a workflow improvement that enables it, considering both sides together.
TranscriptSean uses a tic-tac-toe metaphor for combining broad knowledge with depth in more than one skill, rather than relying on a single specialization.
TranscriptUsing a water purchase as an example, Sean asks how a buyer chooses between competing products and alternatives.
TranscriptSean discusses input and output token usage as part of the cost of delivering an AI product or service. Accounting treatment depends on the business and arrangement.
TranscriptSean distinguishes the requirements customers expect before considering a purchase from the features that differentiate a product or service.
TranscriptSean considers how people can build skills as AI changes work, alongside changes in technology, companies and investment.
TranscriptSean uses expense filing, receipts, accounting codes, approvals and rework as an example of friction surrounding revenue-generating work.
TranscriptSean discusses using experience and judgment to decide where to compromise and which requirements should remain nonnegotiable.
TranscriptSean describes an illustrative design exercise: start with a meaningful memory or feeling, then connect it to colors, materials, movement and craftsmanship.
TranscriptSean suggests studying products you already own and use throughout the day, then comparing the reasons behind those purchase decisions.
TranscriptSean highlights survivorship bias in fundraising coverage: successful raises receive attention while unsuccessful attempts are less visible. This is a qualitative observation, not a measured failure rate.
TranscriptExamine the relationship between a buyer and a product company. Ask where that connection lives, how strong it is and whether you invest in it.
TranscriptDurable materials are part of lasting design. Continued usefulness matters too: consider the objects, tools and spaces people return to over time.
TranscriptOne-to-one conversations, one-to-many communication and word of mouth play different roles when a product reaches people. Start by distinguishing them.
TranscriptA complaint about a seam, durability or an unmet need can reveal something specific to investigate. Look for the product detail behind the criticism.
TranscriptListen for the requirements customers prioritize. Security, scalability, price, ROI and new capabilities can matter differently to different buyers.
TranscriptConnect quarterly product work to a business question: what revenue or EBITDA impact is the investment intended to support? Make that link explicit.
TranscriptMockups, requirements and blueprints help communicate a product. Bringing them into an implementation still involves conversation, debate and compromise.
TranscriptAn ad-supported service has users and paying advertisers. Examine how those different roles can shape engagement goals and create incentive tension.
TranscriptA brand can offer an unfolding story through its products and experiences. Consider what makes someone want to see the next chapter, beyond a new colorway.
TranscriptAsk who is steering the product and who cares about craftsmanship. A screen shows only part of what someone experiences when they encounter the real thing.
TranscriptSlow down enough to work with the people who understand the raw materials. Build toward a product vision layer by layer, with care for the components.
TranscriptBuying criteria can include trust, data use and values as well as features.
TranscriptPublicity can affect what a brand stands for and what buying it signals. Evaluate the attention in relation to the values you want the product to communicate.
TranscriptExplain the product detail that was missing from the alternatives. Use a concrete illustration to make the difference understandable to the customer.
TranscriptA new feature or colorway is not the whole iteration process. Refine the product through interaction with the market and what that interaction teaches you.
TranscriptObserve purchases at different price points while recording what else changes. Interpret the pattern alongside differences in product, audience and conditions.
TranscriptTaste is not simply discovering a song or wearing a trend before someone else. Explore the distinction between being first and developing a sturdier preference.
TranscriptFor work built around repeated steps, consider value beyond the process: judgment, improvement or helping automate it.
TranscriptA welcoming interaction can be part of a product’s value. Consider how safety, calm and the fear of data misuse shape the experience of a simple text box.
TranscriptFunding choices can influence whose needs receive attention. Consider the role of customer revenue when weighing debt and equity in a business.
TranscriptObserve shares, bookmarks, outreach and purchases alongside views. Follow the numbers with conversations that can help explain what people cared about.
TranscriptCustomer urgency can shape willingness to pay. Shipping and transaction-processing examples show why the value of speed depends on the problem and the buyer.
TranscriptAsk whether customers keep paying or must be found again each cycle.
TranscriptAn idea must become a design, implementation and usable product. AI may accelerate that work while the translation from idea to reality still needs to happen.
TranscriptClarify the principles you want your work to stand for, and consider how shared values can outlast a project.
Transcript