Inside Tech Comm with Zohra Mutabanna
Inside Tech Comm is a show for anyone interested in learning more about technical communication. It will also be of interest to those who are new to the field or career-switchers exploring creative ways to expand their horizon. You can write to me at insidetechcomm@gmail.com. I would love to hear from you.
Inside Tech Comm with Zohra Mutabanna
S8E3 Sentient Design for Intelligent Interfaces
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
What if we stopped thinking about AI simply as a tool for doing our existing work faster—and started treating it as a new material for designing experiences?
In this episode, I talk with Josh Clark and Veronica Kindred, co-authors of Sentient Design, about what happens when intelligence moves beyond the chatbot and becomes part of the interface itself.
Josh and Veronika define sentient design as the practice of creating intelligent interfaces that are aware of context and intent and can adapt to users in the moment. We explore what that looks like in practice, from dynamically assembled dashboards to AI agents that behave more like collaborators within an interface.
And for technical communicators, there’s an interesting implication: our ability to define context, instructions, rules, guardrails, and behavior could make us important contributors to these emerging experiences.
Want to explore the ideas further? Inside Tech Comm listeners can get 20% off Sentient Design from Rosenfeld Media with code SENTIENT-TECHCOMM through October 31, 2026.
Some highlights from our conversation:
- Moving from AI as a tool for production to a material for product
- What sentient design actually means—and what it doesn’t
- Combining probabilistic AI with deterministic systems
- How adaptive interfaces can respond to context without giving AI unlimited control
- Why technical communicators may have a new audience: the AI systems themselves
- What Salesforce and Cisco are already experimenting with in adaptive interfaces
- Why AI could change collaboration across content, design, development, and product
- Making room for experimentation and “mad science”
- Using defensive design to build trust and guardrails into AI experiences
- Designing AI to express uncertainty instead of pretending to know everything
- Why critical thinking and AI literacy may become more—not less—important
Use discount code ITC26 to save $200 on registration for LavaCon 2026.
Season Kickoff And Guest Welcome
ZohraHello friends and welcome to season eight of Inside Techcom with Zahara Mutabana. This season features a collection of conversations that explore the ideas, challenges, and opportunities shaping technical communication today. From AI and content strategy to leadership, product thinking, and the future of our profession. Each episode offers a fresh perspective from people doing the work. Let's get started. Today's guests that I have are Josh Clark and Veronica Kindred. They are the co-authors of Sentient Design. And Josh is the founder of Big Medium and a longtime design leader known for helping organizations navigate major shifts in digital product design. Veronica is a product designer and design technologist whose work explores how AI is reshaping the way we design intelligent experiences. So we are going to dig into intelligent experiences and what does sanction design mean and just learn more about their world and how it impacts our field technical communication. So, Josh and Veronica, welcome to my show.
SPEAKER_02Sora, so happy to be here.
SPEAKER_00Thank you so much for having us. Yeah,
Meet Josh And Veronica
SPEAKER_00thank you.
ZohraThank you so much for taking the time so early in the morning. So I want to, you know, kind of have both of you introduce yourselves.
SPEAKER_02Terrific. Well, why don't I start? As you said, I lead a design agency called Big Medium. And a lot of what we do is helping companies design for what's next. And that changes from year to year. Most recently, you might have heard of this thing called AI. It's sort of a it's turning into a sort of a big deal. Everyone's obviously thinking about it. What is this thing? I mean, I think that's also that is a real question, you know? It's like, what is this? What does this mean for us? And so one of the things that we're doing as a product design strategy company and product design company as well, is helping companies figure out what does this mean for how it changes the experience of products? And so Veronica and I have written a book called Sentient Design, as you said, which kind of codifies the practice that we've developed around designing intelligent interfaces. And we'll talk about that some more. I will let Veronica introduce herself, but I will say that we are very different generations, that I've been doing this for 30 years, and Veronica is coming into this somewhat new in her career, and we can talk a little bit too about why that's been so important to have those two perspectives. But Veronica, over to you.
SPEAKER_00Yeah, that's right. And um, for listeners who can't see us, I'll politely say that Josh has a few more gray hairs than I do.
SPEAKER_02Hey, hey.
SPEAKER_00All respect, all respect. But yeah, that's right. I was in my last year of school when ChatGPT came out when OpenAI dropped ChatGPT in the world, and LLMs really exploded onto the world. And I remember my data science professor walking into the classroom very somber one day and just being like, the world has changed. And we were all like, what? Because like no one had ever really heard of it. And then by of course, like the next week, the whole campus was like flooded with LLM-generated content. But yeah, that's right. So my whole career in design has really been kind of AI native. And I've spent the past couple of years working at Big Medium, and I've spent the past couple of years working at Big Medium and really exploring AI as a modality with design.
SPEAKER_02Yeah. And you know, I mean, something that I'll say is Veronica is not only my colleague, but she is my daughter, and I'm very proud of her in a lot of different ways. Okay. So we are we are very literally two generations of design.
ZohraOh my god, that's so beautiful. I'm so glad that you shared that with us. So that's fair, Veronica. He's definitely many, many gray hairs ahead of me, if I may say so.
SPEAKER_02She's allowed to say. She's allowed to say.
ZohraAll right, and Veronica and Josh, I mean, congratulations. This is such an amazing thing to have a father-daughter project.
SPEAKER_02It's been a personal and professional highlight for me to I can imagine.
SPEAKER_00As a parent, I know. It's been very fun. I think like writing a book is not always the most pleasant task and it is so solitary. I think it's really nice to be able to go through it with a close family friend.
ZohraAbsolutely. Absolutely.
SPEAKER_02I think too, that's just sort of what we're saying is like, as you heard, Veronica doesn't yet have my experience. You know, I've been doing this and I've seen a lot of different transitions over the past 30 years, and Veronica's coming to this new. So she doesn't yet have my experience, but she's also not burdened by it, which I think is sort of an important thing right now, where what we're seeing is that the possibilities that AI opens for user experience means that we're able to make things that we weren't able to make before and experiences to provide to customers and users that we weren't able to do before. And that requires us to go back and say, are those best practices still best practices? Just because we've been doing it this way, should we continue doing it this way, or is there a better way? And I think having Veronica's fresh eyes has really changed the way that I have worked. And I think our practice around this wouldn't be the same. And the book certainly wouldn't have been the same without her. I couldn't have done this without Veronica.
ZohraStop it. Oh, well, so we are going to have two different perspectives. And this is almost like I feel like an inflection point in our field, and where we are not just pivoting, but kind of rethinking and challenging some of the old ways of doing things. So what a great way for you two to bring that perspective.
What AI Really Means Now
ZohraAnd you said, what is AI? So to give that scope and in your words, describe AI and how it kind of lends itself to this new design material that, you know, rather than a simple tool.
SPEAKER_02Yeah, it's a great and surprisingly complex question. I mean, we think of AI as this new thing, but it's been with us for gosh, over 75 years now, the better part of a century in one form or another, and it adapts. And the really interesting thing, and we see that dialogue happening right now, is at every new step, there's this question of like, is this artificial intelligence? Is this it? And the conversation now, is this AGI? Is it coming? And at every stage, kind of the goalposts keep changing. So when we first taught a computer how to play checkers, it's like, well, that's not real intelligence. That's just sort of rule following. Well, what about chess? Oh, no, that's not it. Well, what about Go? No, that's not it. And so the our expectations of what AI means is really different. If we had shown the people 75 years ago what large language models can do now, everyone's heads would have exploded. I mean, like Veronica was saying, on campus, people's heads did explode when it sort of came out. I mean, it's amazing how quickly we say, oh, you know what, that we become used to it. I mean, the the things that large language models enable now or the experiences we can have are truly incredibly different from what computing was just five years ago. So the way that we're thinking about it is what do we do with this latest era of large language models, things that can do some kinds of reasoning well, but also are incredibly stupid in other places.
Defining Sentient Design
SPEAKER_02What we talk about with sentient design is it's the practice of creating intelligent interfaces, which are experiences that are aware of context and intent with the agency to adapt to the user in the moment. And that can take a whole range of changes. But essentially what we're talking about is what happens if we share design decisions in the moment with AI and we teach AI within our guardrails, give it a creative brief and the rules to decide, to make content or behavioral or structural or visual changes in the interface. Almost as if a designer was there being like, oh, I can create a custom interface for you in the moment. So this can be as wild as websites designing themselves, or small little interventions, or AI having some presence as just another user and a multiplayer experience driving its own cursor around your Figma or Canva board and making comments on your document, just like your colleagues would. That's a lot. But I mean, that's the idea is like, oh, we can make our experiences more intelligent. That's different than how do we use AI to produce stuff, to do the stuff we already do. It's about creating genuinely new experiences.
ZohraAnd thank you for taking the time to kind of explain how you see AI. And then what I caught was the experiences that are aware and can adapt. Essentially, that's to me, that means that intelligence comes with that definition of sentient design.
SPEAKER_02That's right. And I don't know, Veronica, it's like we hear a lot of sort of questions, sentient design, eh? That seems like an ambitious title.
SPEAKER_00Yes, yeah. And what we'll say, we don't mean sentient in the in the literal sense, but by sentience, we do mean that awareness of context and intent. One of the things that has really taken me and that I've become increasingly interested in in the past year or two is really the combination of probabilistic and deterministic systems. So when we talk about things that are aware of context and intent, that's an LLM, right? Like you can say something and it will an LLM will understand what you mean. You don't have to have like an exact, you don't have to know SQL to be able to manipulate data anymore. You should still know data principles, but you know, that's a whole nother thing. But combining these algorithms that are probabilistic, like an LLM with deterministic systems, more of like old-fashioned algorithms that can be selectors, unlocks so many possibilities. And I think that's really what we're talking about when Josh is talking about kind of systems that can design themselves and systems that are like having a designer there for you in the moment, because you can combine prefab selections that a designer has approved and that makes sense for the customer experience and for the journey, and that's all been made and decided. But an LLM can come in and probabilistically choose the right one for the moment. So that's the combination of things that gets really interesting because there's no customer journey, there's no happy path, but you still have these reliable pieces, Lego pieces that you can like build together for an experience.
ZohraI'm thinking doing something without a customer involved is a pretty bold thing to do, right?
SPEAKER_02So to be clear, right, it has to begin with the customer's needs and of course the business needs too. And how do you marry those? And I think the the way that we've managed that traditionally is by defining some sort of course personas or segments and then designing static paths for those. It's the best we could do, right? It's like in truth, there's a million different scenarios that users bring to things. And we can't historically design a million scenarios. So maybe we design seven different dashboards for these different scenarios, or people individually create things. And then over time, it's like, oh, we've got a thousand dashboards that now people have to navigate. And so the idea here is not to say, oh, we don't care about what the user thinks, or that we're not designing around those user needs. But rather we're saying, what could we do if AI could help interpret that need in the moment and bring that experience to the user instead of make them climb through some complex navigation? So this can sound somewhat abstract, but really what we're doing, and this is what Veronica is talking about about sort of an LLM working within a deterministic system, is that we still, as designers, create the structure and the environment that both humans and AI will work within. So I don't know, as a very more concrete example, Veronica, do you want to talk about like Salesforce or Cisco? So this sounds like, wow, this is kind of a wild, fluid world. Who's doing this? And it turns out even in the very kind of conservative, buttoned-up world of enterprise software, we're seeing it.
SPEAKER_00Yeah, that's
Adaptive UI With Guardrails
SPEAKER_00right. The Salesforce example is something called Salesforce Generative Canvas. And it takes the context of a user. So whether that maybe it will look
Salesforce And Cisco In Practice
SPEAKER_00at a user's calendar and it sees that they have a meeting coming up with a client. This and we'll say this is a sales team member, and they see that they have a meeting coming up with the client, and they assemble their dashboard such that there are notes from the last time they had a meeting, the most up-to-date stats on that customer in the Salesforce database. And so it's assembling all of these components in the moment way, using context from the user's calendar. You can also ask it a direct question and it will and it will populate the canvas. But what's great here is that the data is not being LLM generated. The content of the components is not being made in the moment, but it's taking the data that already exists in the Salesforce system and bringing it to the user so that they don't have to navigate throughout. And you can definitely imagine this being really useful in like a client meeting where you're trying to stay focused, maintain good eye contact, even over Zoom, but you still have kind of the things you need coming to the service. So you can just quickly glance and keep talking.
SPEAKER_02It's not like making up the design, right? That's got this little sort of scoped design system of sort of different widgets that are tuned to present certain kinds of information. And it's got certain sources of information. And it knows kind of like, oh, here's this sort of dashboard archetype. So there's rules involved, right? And AI is sort of saying, oh, here's the context, here's the kind of data that I should do. Let me fetch that. Oh, and here, because it's this kind of data, here are the right components to display. And so it's making sort of simple decisions within a fixed system, but that can give this a huge variety of results to the user.
ZohraNow, to a large extent, it makes sense to me. I'm thinking right now, I'm trying to build a daily digest where I get to see what my day is going to be looking like. And maybe if an LLM can create a dashboard for me as the day changes, as my priorities change, that's a very positive user experience. Would that be something about it?
SPEAKER_02Yeah, that's exactly it. And right, like you think about the different types of days that we have. Oh, this is a thinking day where I'm creating and making. What are the materials or context that I need for that? Or this is a meeting day. Like, remind me who these people are, what we decided the last time, what's next. Like those are very different kinds of experiences that you want to have different information. How can AI help to make that? Like we've been talking about adaptive interfaces and personalization for decades, but we finally have a technology that can actually help to do that on the fly at the presentation level, right? Like it's not about AI making up facts. It's about making, oh, really sort of simple decisions from available design material. And so as designers, we create that environment and then we teach AI to work within that environment. And that sort of behavior design, and this is like what technical communicators are great at. Like it's like, oh, let me actually explain how you do this thing. That skill becomes incredibly important at this sentient design layer because you're teaching do's and don'ts, you're teaching behavior, you're kind of giving, in a way, a little a junior designer the brief for how to respond to the user and what to do, what happens when it's a confusing situation, what happens when the data is ambiguous? What do you do in these situations? And so, in a sense, technical communicators have a new audience, that it's not just the people on the company side and the people on the customer side. It's this enabling collaborative layer that AI provides at generating these experiences.
SPEAKER_00Veronica, would you like to add something? Thanks, Josh.
SPEAKER_02Yeah.
SPEAKER_00Yeah, maybe I'll just talk about another example, if that's all right. I can go for it. Yeah. So we talked about the Salesforce example. The other example that Josh mentioned is the Cisco dashboard. And the Cisco dashboard is similar to the Salesforce canvas in that it's assembling things on the fly. But rather, if you can picture it visually, on the left hand side you have a kind of traditional LLM chat, and on the right hand side, you have like a big dashboard. And as you ask questions of the chat, it starts to populate the dashboard in in in response to your question. You can also ask specific questions about what's already on the dashboard, and it might show you a Viz in chat, which you can then drag onto the dashboard. So in this situation, you're really able to assemble dashboards. This has a heavier hand, right? You're assembling dashboards according to what you need and according to your questions rather than kind of imbued context. And then you could see how you can push this further. Like, oh, can I share this dashboard? Can I invite people onto my dashboard? Can I save it for later and come back to it? So there's all these possibilities when you start thinking of these dashboards that really bring content to you.
SPEAKER_02This is just one of the examples. You know, I know we're being sort of very dashboard focused. It tends to be an example that's kind of easy to visualize. It's like, all right. It's like these elements that are being assembled on the fly. That's a pattern that we call bespoke UI, which is just like a custom interface that's being generated for users. But we have 14 other experiences, including, you know, how do you work with agents right now? Sort of this mainstream idea of agents, it's a very text-based, almost console-based experience. What happens when you have that, those actions and actors in the interface itself? So that they are in the same way, if you think about an agent as a multiplayer experience, like in other collaborative environments, how should they show up as collaborators in the experience? When you're editing a document, we know how one of our colleagues would edit in the comment and markup a document. What happens when AI shows up in that interaction? Or in a Canvas experience like Figma? What if an agent has its own cursor to do tasks for you or add comments? And so it's it's this thing of really about weaving intelligence into the interface so that the interface itself becomes a collaborator with the user or is responding in real time, as Veronica's mentioned in the Salesforce and and Cisco examples.
SPEAKER_00And I'll say what they're not plugs. We're not no one's paying us to talk about them.
SPEAKER_02Salesforce, Salesforce makes enough money.
ZohraYeah, no disclosures here.
Fear, Hope, And New Value
ZohraBut what I want to ask you, Veronica, is you know where I'm looking from. I am a Gen Xer and I have kids who are probably just a little younger to you. I look at AI with I used to look at AI with fear, not as much anymore. But how are you looking at your future? Like I want to bring I want to understand your take on that.
SPEAKER_00Yeah, thanks so much for that question. It's definitely something I've thought a lot about. And I think the fear that you used to feel, I think a lot of people still feel that. And there's like a lot of anxiety around AI and AI adoption. And it makes so much sense. Like AI is having a pretty tangible impact on the workforce, and people are worried about jobs or they've lost their jobs, partly in thanks to AI automation. And that's so scary. Like there's so many reasons to be fearful. And there's also like the other impacts of AI. Like, we don't know yet the social and economic impacts of this technology, and it's kind of being allowed to run rampant without great regulation or legislation surrounding it. So I think that's where a lot of my anxiety around it still comes in. It's like, oh wow, I really wish we were addressing this more head-on at an institutional level. That seems like a whole separate podcast, but I think what gives me hope is I think thus far the focus on AI has been on efficiency and has been on making things faster or cheaper. And that is just such a race to the bottom. Like, you know, who can make this the fastest and the cheapest? Has what about quality, you know? And so I think so much focus thus far has been on tooling. And even in like the design industry, a lot of our focus has been on like the tooling of AI, like, oh, how can I make my designs faster? Or how can I expedite this whole process? Like all of this. And what there's not been much focus on, and what Josh and I have tried really hard to focus on, is making new kinds of things. You know, what new products can I make? What new experiences the This enable? And I think that has yet to hit mainstream or to hit other industries, not just our book specifically, though you know, I hope it does. But just that idea of like, okay, this technology does mean we can do things faster. It does mean we don't have to write long emails anymore. And that's where a lot of people stop thinking about it is like, oh, how can this help me do what I already did with lesser effort? And there's not been a ton of innovation or imagination around what new types of things it can do. So I think that's where I get very hopeful and excited.
SPEAKER_02You and I are generational peers, Zora. And so there's like a lot of this thing that is, oh man, all right, this does this threaten my decades of experience and hard-won knowledge? Is this just gonna sort of take over? I will say that I have never been so excited as a designer than I am right now in this career for exactly the reasons that Veronica is mentioning about sort of the upsides of this. If we shift our thinking from how do we save money, how do we cut, how do we do what we have always done, but faster, that's fine. There's like there's value to that for sure. I like productivity, I like efficiency. But what's missing is how do we create new value? How do we create something that we couldn't do before that can create a tremendously valuable and meaningful experience for both customer and business? Like that's exciting. We have new material to work with. And that's the shift that Veronica is talking about is going from a tool for production to a material for product. And product ultimately is what we're all here for. Production is just a means to an end. What the only thing that matters is what we put in front of the customer and what happens next. And we have the opportunity to invent meaningful new ways to do that. And when you think about that, right, my job isn't just about the production, it's about imagining what's possible and now working with this new to the world material to make those things happen. That is exciting. And that is design and content work. You know, there's the the old saying in product management of good, fast, cheap, pick two. If fast and cheap are just available to everybody, then the only thing that matters is good, right? Is what shall we make? What shall we imagine? And that we have a whole new world to invent right now. With sentient design, we're trying to establish what are the foundations that are emerging now, what are sort of some of the principles that we can use to invent these new kinds of experiences, but there's still so much invention ahead. And I think that's gonna take a generation of work to figure out in the same way that the web itself and mobile took generations to figure out. And that's the work, Veronica, for you ahead.
ZohraWhat
Jobs, Craft, And Team Collaboration
Zohrais the one thing that you can say if you're kind of worried, looking through the lens of where you are sitting?
SPEAKER_02I mean, jobs are changing, and some of the tasks that we associate with our role will go away. And some jobs may go away too, some roles may go away. And you know, I mean, I don't think it's anything super new to say that production is at risk, right? The stuff that it used to take, you know, that especially around code, some aspects of writing, although that really depends on the context, are at risk that AI can just crank this stuff out or at least make an incredibly credible first draft. And so the shift has to be around we are more than just generators of code or generators of word, that we think about what's important, why are we creating this thing? And so, in some ways, while a lot is changing in terms of the production of our work, all of those kinds of efficiency things that Veronica was talking about, or what we can just ask Claude or ChatGPT or Jim and I or co-pilot to just please just do this thing and it happens. That is at risk for sure. And that work is changing. But I think it also lets us use these things as material to create new things, like we were talking about. And I think that that's especially important at the at the product level of you know, what can we get show to customers, not just how do we get to it faster, but what can we show to them that's new? But also like the foundations of our work don't change. So, especially for Zora, for folks like you and I who have been at this for a while, I want to give some reassurance that it's still about the fundamental questions of what problems are we trying to solve? What frictions can we overcome? And now we have a new material to work with to do that. Like we've just like when the web came around, it's like, oh, this is new. This is a new vocabulary to learn as a creator and as a consumer. Same with mobile, you know, and so every 10 or 15 years we get one of these things that are both crisis and opportunity. And so I think that the way to think about it and to sort of future-proof our jobs or adapt our roles is how do I work with this new material, not as a tool, but as a something that can deliver outcomes in new ways. And I think an exciting and challenging thing is that this does change the process of our work and the kind of collaboration that we can have, that this idea of working together to help AI make good decisions really calls for more collaboration. And the cool thing is that the work surface and workspace can be the same. And by the way, this is like stuff that technical communicators are can be really great at. That if we think of, you know, really what we're talking about is giving systems the context and instructions that they need to make good decisions, whether they're writing technical documentation or we're teaching them the behavior of creating one of these bespoke interfaces that Veronica was talking about. This takes many disciplines: product, technical communicators, designers, developers. And traditionally, that's been a waterfall step, right? You know, despite all the talk about Agile, we're not working together on this stuff. But now we can. We can, through all of the phases of a product development, we can all contribute our discipline to this common workspace, this common system prompt, the context that goes in it together. And one of the things that Veronica and I are experiencing a lot is that all of our teams are working together in the same common repo. And even if we aren't coding, we are contributing the documentation that AI needs to make good decisions in the moment. And it's been really powerful. The risk is that we do things, is that AI makes me think, oh, I can do all of this on my own without my colleagues. I'm a designer, but now I can deliver code. I don't need developers. I'm a developer, but now I AI can do the design. I don't need designers. That's a risk because then everyone runs in different directions. The real opportunity, and this is another area to think about for career, is how do we collaborate better? How do we bring people together to make decisions together quickly and iteratively in the same workspace that is product focused, customer focused? Those are new skills. I think there's a lot of talk about, oh, you can be a 10x designer, you can be a 10x technical communicator. What about your team? Like this is, you know, how do we make our team awesome? And more to the point, how do we make our customer awesome?
SPEAKER_00Well, I'd love to kind of pick up on something Josh was talking about, which is just this idea of like a shared workspace within a team. I think with the I think with AI coming into the mix, there's been this kind of flattening of skills where, like Josh was saying, like now when I'm designing, most of the time I'm designing in cloud code. Like I use Figma probably 80% less than I did last year, which is just a crazy difference in process for one year. And I think what's really interesting is now when I'm in Figma, more often I'm in a fig jam board rather than a Figma design file. And more often I'm in that Fig Jam board specifically to collaborate with people from different disciplines. So having like a product person and a developer all in the fig jam board working on the same thing and all trying to get our ideas out. So there's less technical barriers. And so just to kind of pull a thread that Josh was picking out as well, it becomes even more important to really have your discipline's perspective. Like I still need to, even though I'm working on code technically, what you know, and you know, that gets sent to the developer who's like making sure it's healthy, just to catch any claudisms or anything. But it becomes so important for me to have that design perspective and to really hone down on like the main thing a designer is there for, which is like, how am I looking out for the customer? Like, how am I making sure the customer is getting what they need from this experience? And and the techniques, which you know, last year was like, how well can you use Figma? And don't get me wrong, like I can use Figma, but it's becoming less important as the perspective that you're bringing and the principles that you're bringing to it. So I think that's been really exciting. It's like a strange distillation of the craft.
SPEAKER_02I do think there's sort of an evolution of how we adopt new technology that that I think Veronica is calling out here. Is first we start with, oh, we have these tools. How do we fit this into our existing process? How do we do what we already do faster? And then that has some knock-on effects. It's like, oh, wait, I'm I'm working differently. Now we as a team have to work differently. How do we change process and maybe organization? Those things can be hard, especially in large organizations. That's not nothing, right? And I think that most companies are there right now in the between those first and two stages of changing our tooling. Now, how do we change our process? And then that third bit is like, how do we change our product? And that's the bit that that Veronica and I are especially fascinated with and that we help our clients work with is like, what is the new thing that instead of just making the old thing faster, how can we make the new thing? And what are the opportunities? Does that open? And I think that's the most exciting thing for the next generation of product design and product organizations. Because from there, what happens is sometimes those things open up entirely new lines of business. And in some small cases, might even disrupt a whole industry and sort of reshape an industry. Most companies aren't in the disruption business, you know, that we're sort of like looking at, you know, how do we do, how do we provide our services now better? And I think that is like an especially exciting thing about that product invention phase. So it's okay. It's okay if you recognize it's like, oh, you know what, we're still doing tooling. We're not saying you're doing the wrong thing. That is where things begin. And learning to use those tools often say, oh, what if we did that in our experience, in our product? How did or what new product would we create?
ZohraI think we need to step away and kind of really think about where can I, what can I do differently?
SPEAKER_02Yeah.
Try AI, Play, And Explore
SPEAKER_02I mean, I think one of the things that's interesting too, like Veronica was saying, there's so many reasons to be skeptical or even fearful of this change and what it means for us individually and as a field. There are plenty of reasons for that. I guess I would say that skepticism and fear should be more reason to engage with this, not less, and not least because the technology changes so quickly, that the capability changes. And so thus, so it's the possibility and creative material. And so I think one thing is if, for example, you're someone who hasn't tried to use AI to do a task in say six months, because it was sort of meh then, you may be very surprised at how well it can do that thing now, either in a customer-facing way or how it supports your own work. And so I think one of these things is if you think of AI as your enemy, well, then know your enemy because soon you might be able to like understand it better, make it a friend. I don't want to sort of like over-personalize uh what AI is here, but I do think there is this thing of like understanding the material will help you use it in ways that serve not only yourself, but the customer and the business.
ZohraVeronica, would you like to add something?
SPEAKER_00Yeah, I not to be a downer, but I just want to acknowledge, I think there are some barriers that lead to people not adopting new tools. You know, if you are in a huge enterprise, you know, there's very real like firewalls and you can access this and that type of thing, as well as yeah, that that intimidation factor. So for anyone who maybe feels like they face those kinds of obstacles, I would just want to give a message of encouragement to just try and even even for a month, you know, just to really like push it as far as you can and use it in in different ways, not just for work. Zora, you're talking about, oh, like maybe I can assemble this dashboard to help me get through my day. And it's like, yes, totally. And Josh, you were talking about, you know, is it a thinking day or is it a meeting day? And I think it's also like, well, are you responsible for picking kids up from school? Do you have to go grocery shopping later? Can it give you the recipe when you need the recipe and all these things? Like, because I think using it in non-work circumstances is really been a place where like my imagination around it grows. And I'm like, or I discover new tooling, or I'm like, I didn't know Claude could do this because I'm like doing it out of a context that I like think that I already know.
SPEAKER_02I mean, that's getting at that perspective shift from tool to material. Like a lot of things, if you can shift your thinking as a technical communicator, as a designer, as a product leader, from how do I just use AI over here in this specific role of making the thing that I need to make to how do I incorporate it into the thing that I make? That is a big unlock, is what we've discovered of creative possibility for the individual and product for the end user.
ZohraThis is definitely, I think, stepping outside of what you're doing, Veronica. I want to go back to your thought, what that you shared. Stepping away from what you do day to day and thinking creatively can actually be fun. So interact with that's that's such a fun way of thinking.
SPEAKER_02There is this thing too, right? It's like in projects now, we reserve some time for what we call mad science to experiment and play around the subject instead of rushing to solution. Because right now there is opportunity to discover new ways to accomplish something or to present something. And so I think it's really important that kind of play and experimentation that both of you are talking about.
ZohraYeah, I love the phrase on that side because oh, that that totally vibes with me, I think.
SPEAKER_02Not that I'm a scientist, but uh, feel like one, yeah.
ZohraYeah, I know, or why not feel like one, right? Uh and I think AI allows me to think that. So why not?
SPEAKER_00Absolutely. You're like, I can code. I'm like super I'm so STEM.
Defensive Design And Trust Signals
ZohraYou introduced the ideal of defensive design. What do you mean by that?
SPEAKER_02We don't want to kind of come off as boosters and that AI can do everything. All of us have had the experience working with AI where it's like that's not right, or it's just made that up, or terrible assumptions, or we've all had experiences where things go sideways. And so, you know, I think Veronica, if you want to talk a little bit about this, we've had this kind of strategy around defensive design, both as a mindset and specific patterns that you can use to sort of promote safety and trust.
SPEAKER_00Yeah, absolutely. Yeah, defensive design is is really the practice of designing in guardrails. So rather than just right now, you know, you're using an LLM and there's like a bit of legalese below a chat bot, it's like answers might not be right. Double check. Or there's, you know, you see a new feature on a website and there are some purple sparkles on it. And those purple sparkles are symbols of AI. So you know you're using AI, like we're all very well adjusted to that symbol now. But it's kind of giving you the message of like this might not work, like this is for fun, this isn't you know central to your task, or it can't exactly be relied upon.
SPEAKER_02Do not trust.
SPEAKER_00Do not trust, yeah. So rather than designing in guardrails, we're getting used to these kinds of like caution or warning signs. So, which really kind of go to undermine the product because if it doesn't work, why are you putting it on your website? That said, of course, AI hallucinates, it can't be trusted 100% of the time. It does a remarkably good job of giving you things that look like answers, and in a very miraculous way, it's often right. Like it is often the correct answer. But there is, you know, that 10 or 5 or 1% of the time where it's wrong. And in a creative context, that can be fine, fun, whatever. That picture now has six fingers on somebody's hand, like that's funny. But in other situations, that's a real problem. If you're in healthcare or airlines or any kind of safety regulation that is super, super high stakes, you can't be wrong like that. So, how can you build in signals that encourage productive humility within the system? So the system is not being too arrogant about its own abilities, as well as some healthy skepticism on the part of the user without just like adding those sparkles in. And there's a number of different ways to do this. You know, there are things to be said for the way something is worded. There was an interesting experiment done that said if you present percentages to people, like if you're like this is 90% likely to be an elephant and it's a picture of a giraffe or something like that, but that doesn't mean much to people. There's a similar thing, maybe this is a better example on on Netflix where it like has a movie and it's like you are 74% likely to like this movie. And it's like, what does that mean? Like, what does 74% likely mean? But if you're wording something and saying, like, um, you're like probably gonna like this movie, there's a lot more information being given, also in my tone, right? Like, you're probably gonna like, you know, it's you know, we're able to understand that it's like, oh, I don't know, I might not, you know.
SPEAKER_02Right. But saying it's saying I'm 10% confident is different from I really have no idea. So I'm making this up a little bit, but here's a guess based on very slim data. Like that's really different. And it's just like, oh, I'm listening to you now and I'm understanding so so there's a presentation aspect, not just a clinical.
SPEAKER_00Yes, the presentation aspect. So in the wording and also in the tone, I'm trying to like encourage some healthy skepticism on your part, and I'm being a little bit humble about what I know, even if I'm not saying, you know what, I don't actually know, I'm still giving you an answer, but it's giving you an answer that is also like encouraging, like you might want to look a little further into this. It doesn't really work right, you know, like lawyers don't like that. They're gonna lie, that type of thing. But I think it's giving a type of personality to these systems, personality in the sense of presentation rather than personas. Like we're not trying to pass them off as people or as human, but a certain personality of deference or humbleness that is is missing a lot right now.
Critical Thinking And AI Literacy
ZohraCritical thinking, in your opinion, is that going to go away or is that something that will get sharpened?
SPEAKER_02Yeah, I mean, I think a lot of that is up to us as product designers of how we present this stuff. You know, our friend Chris Nossel wrote a wonderful book called Designing Assistive Technologies that is about exactly this. How do we create assistance that amplify judgment and agency instead of replace it? You know, and I think we've all had experiences where we have become dumber by using technology. I cannot read a map anymore unless it has a little glowing blue dot on it. There are definitely things where we're like, oh, I have outsourced some critical thought here and lost some skill before. There is de-skilling as a risk. So I think one of the real challenges are what are the things that we actually is a skill that we legitimately don't care about or need that is appropriate for technology to do? And what are the things that we want to reinforce as we think about introducing intelligent interfaces, as we think about productivity? What are the things we don't want to automate away? Either because they are special to us, prized by us, things that we want to, as human beings, continue to do as part of our craft, or things that just require at this point our discernment and judgment, and that we should have people involved in this in a collaborative process. So I think that there are a lot of things of like, where do we want to pause and make people think? And there are moments of where do we want to put intentional friction into this? Just to give a super fast example, you know, kind of of like what Veronica was talking about, about sort of different kinds of presentation. We see this in the familiar things of Google search. If you ask, is a lizard a good pet, you'll get different results from if you ask, is a lizard a bad pet. You're asking the same information, but the way you've asked biases the algorithm. And so Google tries a lot of things around this. They will detect that. And when you ask, is our lizards good pets? it will say, also showing results for our lizards' bad pets. It has recognized that these things are similar but different queries, and it will ask both and give you the results. Or people also ask, right? Those things of like, you can ask it this way or that way. And what it's doing is showing adjacent answers or models. There's more than one way to get this. And here's a few nearby paths that suggest A, the system is only showing one corner of this area and helping the user to show how to explore more. So it's becomes it reveals its bias and it helps the user overcome it and show through it. And it's like, oh, that's subtle. There's a lot of nuance there. How do we think about that of like showing, revealing the shortcomings of the system and helping the user answer those?
ZohraGreat. Veronica, what's your take?
SPEAKER_00Yeah, I will wrap up by kind of referencing our generational difference again. And I've thought about this in terms of literacy, in terms of media literacy and as well as data literacy. We've really seen Gen Z grow up in the age of social media and kind of develop this skepticism and cynicism towards social media, towards advertisements. I think Gen Z is much more easily able to tell when something is an ad, you know, just because like we're so exposed to it and inundated with it. And it's not always a problem, but it does become a problem when it's not disclosed. And so I do wonder if Gen Z and Gen Alpha and ensuing generations will develop a similar kind of literacy towards AI.
Closing And Listener Requests
ZohraAnd on that note, thank you so much, both of you, for you know joining me this morning and educating me. I hope you all had fun as well as I did.
SPEAKER_02You really did, Zora.
SPEAKER_00I definitely did. Thank you so much. And we have a discount code for your listeners.
ZohraYes, please. And I will be adding that in the show notes. So thank you for reminding me about it. Thank you and have a lovely day. Thank you for listening to InsightTechcom. If there's a guest you would love to hear on the show, please let me know. And don't forget to follow and catch every episode on your favorite podcast app. See you next time.