<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ken Caldwell on Medium]]></title>
        <description><![CDATA[Stories by Ken Caldwell on Medium]]></description>
        <link>https://medium.com/@wordydesigner?source=rss-64f804618de8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*yELmo-PZG0zNAEXrvFfQ0w.jpeg</url>
            <title>Stories by Ken Caldwell on Medium</title>
            <link>https://medium.com/@wordydesigner?source=rss-64f804618de8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:13:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wordydesigner/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Reflections on Research Week 2026]]></title>
            <link>https://medium.com/@wordydesigner/reflections-on-research-week-2026-3241c5af0ddf?source=rss-64f804618de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/3241c5af0ddf</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Ken Caldwell]]></dc:creator>
            <pubDate>Fri, 15 May 2026 21:26:32 GMT</pubDate>
            <atom:updated>2026-05-16T00:40:04.522Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5fPESdqQ-GKQeLLXSYKF0w.png" /></figure><p>I was locked in to the <a href="https://joinlearners.com/research-week/">Research Week conference</a> this week (May 11–15), a professional conference for UX researchers and others in product design.</p><p>As a researcher in fintech, I found the sessions inspiring and, at times, worth pushing back on. I’m grateful to all of the speakers named here. The fact that Learners makes this content free and accessible is what I love about this community. Here are my reflections.</p><h3>Researchers Are the Next Wave of Builders</h3><p><a href="https://www.youtube.com/live/XKccUFxl_ec?si=MnTI_29PJnKBnwlx"><em>Moonshot Research on YouTube</em></a></p><p>Eliza Kosoy talked about how researchers are closer to user needs than anyone else. I think she was right on point about how AI tools have lowered the barrier to building. So, it was inspiring to hear her suggest that researchers are empowered to go beyond their traditional role.</p><p>What struck me most is that language skills are now an essential part of the “manifestation” she described. Prompting is not coding, it’s expressing. And researchers are the people in the room who are best at expressing the real-world context in which users live, struggle, and delight. That’s not a small thing. That’s the whole input.</p><p>There is so much tacit knowledge we carry that has never been made explicit. We absorb it through interviews, observations, years of listening. In my industry, LLMs don’t intuitively understand the emotional stakes of a first-time homebuyer at the closing table, or why a mortgage broker’s relationship with a borrower is the whole product, not just the transaction around it. The more we can express that context clearly and specifically, and connect our tools to repositories that express it, the more we can build things that actually serve people’s needs. Researchers have always been translators. Now the translation has a direct output.</p><p>Eliza is right that the next wave won’t be built by coders, necessarily. It’ll be built by the people who know what to build and why. That can be anyone who is willing to pick up the tools.</p><h3>Are We Researching, or Just Narrating?</h3><p><a href="https://www.youtube.com/live/-K_ZqOKxHt4?si=kDTG1y1n1zTOuKBo"><em>Great Research on YouTube</em></a></p><p>Nizar Saqqar’s presentation was thought provoking for me. On one hand I have experienced what he described: writing research reports after decisions were made. Nizar took an even stronger position that research teams that wait for incoming requests are already behind. I have thoughts.</p><p>I think the question is: how good are your reports? Did you ask the right questions in your study, in the right way? Do your final recommendations have meaning beyond the feature du jour? Foundational user insight documented in reports can continue to serve the whole team long after a sprint. Teams can now unlock research repositories with AI-powered search tools to democratize access to information.</p><p>A research team shouldn’t have to be seen as “behind” if they have a defined intake process, if they review and prioritize requests, route to existing findings, and apply judgment to what gets answered and how. That structure can coexist with proactivity. Research teams should also be looking ahead, raising questions nobody has thought to ask yet.</p><p>That’s evidence of trust. Stakeholders don’t go around you when they bring you their questions. They’re acknowledging that your team can provide answers. And not every request needs new research. Part of the researcher’s job is pointing stakeholders toward what’s already known before spinning up a new study.</p><p>Preeti Talwai’s talk on research portfolio management resonated here. Her “Frontiers” category, the emerging areas everyone’s talking about but nobody has a well-formed study design for, inspired me to think about agentic AI as an active frontier in the mortgage industry right now. We need to understand which aspects of the mortgage process can and should be fully automated, versus which people are better suited to steer. Relationship-building with clients and partners? Nah, that’s the human part.</p><h3>On Strategic Judgment</h3><p><a href="https://www.youtube.com/live/-K_ZqOKxHt4?si=kDTG1y1n1zTOuKBo"><em>Great Research on YouTube</em></a></p><p>Danielle Flam named it most directly: Researchers who define themselves by methodology will be displaced by AI. Those who define themselves by strategic judgment will become more valuable. The same argument came up throughout Research Week in various forms.</p><p>I strongly agree, but I also don’t think this is new or alarming. Any expert in their field needs a point of view. Needs to know what projects will have impact. Needs to explain their rationale and make hard decisions.</p><p>We can all see that AI tools help automate some of the execution work. But does anyone believe that good judgment, taste, and the willingness to take a stand are somehow new requirements in this field? Because I don’t believe that they are.</p><p>Here’s what I didn’t hear much about: strategic judgment is not equally accessible to everyone. It comes with education, experience, and conviction. It also comes with a platform. Some people are more privileged than others to take the mic and speak up in meetings.</p><p>That’s not “coolness,” necessarily, as one speaker suggested. It might not even be good judgment. It could be ego, rank, or lack of structure to surface the best ideas. My point is that it’s a slippery slope to value “taste” without process. Evidence should be louder than opinions.</p><h3>On Performance, Persuasion, and the “Roadshow” Problem</h3><p><a href="https://www.youtube.com/live/-K_ZqOKxHt4?si=kDTG1y1n1zTOuKBo"><em>Great Research on YouTube</em></a><em> · </em><a href="https://www.youtube.com/live/Ka-VySkFRhk?si=6wiFzyaFl5uYdTNy"><em>Up, Up and Away! on YouTube</em></a></p><p>Denise Sauerteig argued that every readout is a performance, every deliverable is a pitch, and researchers who see themselves purely as scientists miss the salesmanship part of the role. But Jess Holbrook took a specific stance on roadshows, calling them ineffective and inherently subservient.</p><p>I agree that communicating insight persuasively is not a nice-to-have. It’s a fundamental part of the research process. If the insight doesn’t land, it doesn’t matter.</p><p>But I’d push back on making “roadshow” a pejorative. We need to meet people where they are, showing up in standing ceremonies or sprint reviews where collective attention already exists. That’s not subservience. That’s strategy. The way you show up in those settings, what you say and how you say it, can absolutely build your authority and influence over time.</p><p>I did appreciate that Jess talked about building personal trust one skeptic at a time. Still, that can be relationship-dependent, and it might not be enough to socialize insight across a large product and engineering org that isn’t reading your written reports. I’d suggest a multi-channel communication strategy: repackage your insight wherever there are eyes and ears. Slack, virtual huddles, AI-powered search tools, breakroom standees. Dare I say email. What works for your organization?</p><h3>Who Should Evaluate AI Output?</h3><p><a href="https://www.youtube.com/live/T4HN34vPlRA?si=X6JJSTqxZTg__ZXQ"><em>AI and UXR on YouTube</em></a></p><p>This is an area I’m actively interested in, and I think the distinction between automated and human evals didn’t get enough airtime. I’ve heard conversations in my organization about building agents that validate AI output, and those certainly have a place.</p><p>Automated evals can check for accuracy, consistency, or format at scale. But there’s a category of evaluation that requires a person: the willingness to look at output and ask, without hedging, “how and why is this wrong?” That’s not something you can fully systematize. It’s critical thinking applied to a system that sounds authoritative and confident even when it provides inaccurate, outdated, or contextually irrelevant information. We need both.</p><p>My approach differs with a machine or a person. With AI, I don’t pull any punches. I look for failures, I poke at edge cases, I ask what context is missing. With people, I work differently. We all have feelings about our work, and those feelings can be amplified by sunk cost. I often ask colleagues, “What kind of feedback would be helpful at this stage?” Once I understand where they are, I try to work in the “I Like / I Wish / What If” framework. Lead with what’s working, follow with a constructive push, then offer a new idea if they are open to it.</p><p>The reason this distinction matters for AI evals: In my experience, people give AI the benefit of the doubt. As amazing as these new tools can be, they need someone willing to find errors before a stakeholder or a customer does.</p><h3>On Scale, Recruitment, and the “Largest Qualitative Study”</h3><p><a href="https://www.youtube.com/live/T4HN34vPlRA?si=X6JJSTqxZTg__ZXQ"><em>AI and UXR on YouTube</em></a></p><p>In the Q&amp;A, one person described feeling “methodologically confused” about Anthropic’s 81,000-person AI Interviewer study. They questioned the approach to scale over a carefully recruited small sample followed by a generalization survey. Kunal Handa’s response was that scale reduces the selection bias inherent in recruitment, and that understanding AI’s impact across all users required reaching a lot of them.</p><p>Respectfully, I disagreed with Kunal’s rebuttal here. It mischaracterizes intentional recruitment. Crafting a carefully specified screener is not an act of bias. It’s an act of precision. The researchers I work with design screeners to be inclusive based on qualifying criteria: the right people for the question being asked, not a convenience sample filtered by willingness to participate.</p><p>That said, I’m intrigued by the scale that new tools like AI Interviewer can unlock. And they have published some methodological details on their website, which is great. I recognize the important benchmark Anthropic and team have set with this study, and I’m eager to follow their progress as tools like AI Interviewer improve.</p><p>Research Week reminded me why I love this field. The conversations happening right now, about AI, about judgment, about who gets to build and who gets to speak, are the right ones. Thanks to Learners and everyone who shared their voice this week for making that possible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3241c5af0ddf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI in UX Research: Real Examples of What Works and What Doesn’t]]></title>
            <link>https://medium.com/@wordydesigner/ai-in-ux-research-real-examples-of-what-works-and-what-doesnt-d2a4f917df3e?source=rss-64f804618de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2a4f917df3e</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Ken Caldwell]]></dc:creator>
            <pubDate>Thu, 12 Mar 2026 18:04:12 GMT</pubDate>
            <atom:updated>2026-03-12T18:04:12.911Z</atom:updated>
            <content:encoded><![CDATA[<h4>Reflections on Advancing Research Conference 2026</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*26bhobH5CSPBPKu5" /><figcaption>Photo by <a href="https://unsplash.com/@alvaroserrano?utm_source=medium&amp;utm_medium=referral">Álvaro Serrano</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This week, I attended the excellent <a href="https://rosenfeldmedia.com/advancing-research/">Advancing Research Conference 2026</a>. It was a virtual conference, but I had a chance to learn from some incredibly talented people working in my field of user research.</p><h4>In this article, I share my perspective on some of the talks that covered practical guidance about AI in research workflows. I highlight examples that speakers provided where AI adds value and where it falls short. This is the kind of “how-to” guidance I believe our field needs. My personal reflections are at the bottom.</h4><p><strong>Faster Alone, Further Together</strong> by <a href="https://www.linkedin.com/in/kurtmc/">Kurt McCulloch</a> struck a note with me, because I’ve seen how teams can view problems through different lenses — human-centered design versus metrics and funnels.</p><p>Rather than trying to force PMs to “think like researchers,” Kurt shared how he uses AI as a “bilingual” resource. He ran structured workshops that support individual thinking, AI-enhanced refinement, and group discussion.</p><p>His big breakthrough:</p><blockquote><em>Kurt McCulloch: “Sometimes our most valuable work isn’t the insights we produce. Often it’s the conditions we create for shared reasoning across paradigms that the organization can’t naturally hold together.”</em></blockquote><p>I appreciated how Kurt suggested that better communication can’t always be the solution, but instead greater cooperation is key. He emphasized that researchers should be “facilitators of collective reasoning,” which I think is an important role, especially since researchers can be connective tissue across product domains and business verticals.</p><p><a href="https://www.linkedin.com/in/tara-tressel-phd-977070a/">Tara Tressel’s</a> talk, <strong>Reclaiming Qualitative Depth with AI-Moderated Interviews,</strong> confirmed my experience: AI moderation works a lot like a glorified survey and sticks to the script. It doesn’t probe very well or recognize when a conversation should deviate. Domain context is crucial.</p><blockquote><em>Tara Tressel: “Bottom line: AI moderation did not make the research easier, it made it possible under real world constraints. I think if you go into this expecting it’s going to save you all your work time, and it’s going to be so much faster, you’ll be a bit disappointed.”</em></blockquote><p>Tara shared her experience with what AI moderation did well:</p><ul><li>Captures nuance that surveys couldn’t</li><li>Saves moderator time</li><li>Flexible scheduling</li></ul><p>AI moderation falls short with:</p><ul><li>Awkward timing/flow</li><li>Poor follow-up questions</li><li>Lacking output summaries</li></ul><p><a href="https://www.linkedin.com/in/lauraklein2/">Laura Klein’s</a> talk, <strong>Human vs. Machine: Testing AI’s Ability to Synthesize and Analyze Research</strong>, highlighted the risk of trading quality for speed when product decisions depend on accuracy.</p><p>I appreciated how she talked about the strengths of researchers. Specifically, they can observe and moderate, ask smart follow-ups, notice when participants fail tasks, and adapt based on context. These are things that AI cannot do effectively.</p><p>This quote also hit home for me:</p><blockquote><em>Laura Klein: “AI analysis and synthesis cannot do the most important part of our jobs: it can’t force your co workers to look at actual videos of research. Doing synthesis and analysis and co-creating insights with our team is a huge part of not just learning, but creating consensus for building specific things.”</em></blockquote><p>Laura’s key point: “insight-shaped things” that AI tools create may be fundamentally wrong. Practitioners already know this. It’s the classic “what users say is not necessarily what they do.” And even when AI analysis is accurate, it cannot replace the collaborative sense-making we do as a team.</p><p><a href="https://www.linkedin.com/in/mujtaba-hameed-b3521bab/">Mujtaba Hameed’s</a> talk, <strong>The New Horizon of Ethnography</strong>, offered a strong case study with results. By using AI to automate transcription and initial coding, his team reclaimed 40% of project time that they used for participatory research. This allowed them to have users co-create solutions, rather than just being observed.</p><p>This is the kind of practical example I was hoping to see: clear guidance on where AI adds value (like mechanical tasks) and where human expertise matters most (like co-creation and sense-making).</p><blockquote><em>Mujtaba Hameed: “AI gave us back time. But we had to be intentional about where that time went. If you just use it to do more projects, you’ve missed the point. Use it to go deeper on the projects that matter.”</em></blockquote><p><a href="https://www.linkedin.com/in/vmiliano/">Vitorio Miliano’s</a> talk, <strong>Don’t Call It AI: Turn Words into Numbers with Quantitative Ethnography</strong>, challenged me to think differently. He presented an approach to scaling qualitative analysis through code books with defined rules that computers can follow.</p><p>I learned some practical guidance on AI-assisted analysis. He pointed out where LLMs can shortcut some work by clustering by semantic relationships rather than keyword, but at the cost of giving up control over initial code generation.</p><p>But it also helped me think about how I might create more standard documentation, so that my research projects are more portable for future team members and computer systems to understand.</p><blockquote><em>Vitorio Miliano: “If you can’t figure out how to define the ineffable quality that made you assign that code, you can’t code it. What are the signifiers for future you, another researcher, or in our case, a computer to find? There has to be a rule for a computer to follow.”</em></blockquote><h3>My Reflections on the State of UX Research &amp; AI</h3><p>Overall, I sense some insecurity among researchers when they talk about AI. I understand that, especially for those who are seeking steady work. Others seem to seek assurance that their role will remain a crucial part of the product development life cycle.</p><p>Still others, like me, are excited about AI tools to accelerate some aspects of their work or bolster their thinking.</p><p>But AI is like any other tool. I believe there is a need for more practical, “how-to” guidance that moves beyond theory and into the strengths and weaknesses of specific AI features. It helps to demystify tools, especially non-deterministic ones like LLMs, so that we can understand where to apply them in our craft.</p><p>For my part, I am firmly in the “enthusiast” camp. As a technologist, I’ve been using tools like Copilot, NotebookLM, and Claude for almost three years, as well as the AI tools built into research-specific platforms (e.g., Dscout, Condens). I use AI throughout various stages of UX research work:</p><ul><li><strong>Planning</strong>: Using AI to draft protocols, explore problem spaces, or run mock interviews to sharpen my approach</li><li><strong>Analysis</strong>: Sifting through transcripts to identify themes, extract quotes, and build codebooks</li><li><strong>Reporting</strong>: Draft and package insights to share with stakeholders via docs, slides, and Slack messages</li></ul><p>I believe the path forward for researchers is to educate one another about AI. We should look for ways to leverage the strengths of new tools and how they might accelerate our work or improve collaboration. With the right intention, we can do this while staying user-centric and maintaining the high quality and integrity of our data.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2a4f917df3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Polar Bears in Orlando]]></title>
            <link>https://medium.com/@wordydesigner/polar-bears-in-orlando-a63bc44c6a37?source=rss-64f804618de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a63bc44c6a37</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[information-architecture]]></category>
            <dc:creator><![CDATA[Ken Caldwell]]></dc:creator>
            <pubDate>Thu, 11 Jul 2019 21:34:23 GMT</pubDate>
            <atom:updated>2019-07-12T14:14:06.549Z</atom:updated>
            <content:encoded><![CDATA[<h4>Volunteering for the Information Architecture Conference 2019</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oRPfQ3-uoR2va01-JbRdhA.jpeg" /><figcaption>The IAC19 volunteer team. That’s me wearing maize &amp; blue in the center. (Photo by Adam Polansky)</figcaption></figure><h4>TL:DR — As a <a href="https://www.theiaconference.com/person/ken-caldwell/">volunteer for the 2019 IA Conference</a>, I designed and implemented a chatbot that leveraged machine learning to answer common conference questions in the IAC19 Slack workspace. I also created over 60 <a href="https://twitter.com/search?f=images&amp;vertical=default&amp;q=%23IAC19%20from%3Atheiaconf%20since%3A2019-01-21%20until%3A2019-03-13&amp;src=typd">promotional Twitter graphics</a> to advertise the event.</h4><p><a href="https://medium.com/u/dac723571380">IA Conference #IAC20</a> is built on 20 years of best practice, so there are not many information gaps at the event. Attendees tend to be informed by the organizers, a team of volunteer supporters, and a well-executed communication campaign.</p><p>But sometimes people have short-term information needs that are well-suited to the transactional nature of a chatbot. As a volunteer for the 2019 conference in Orlando, FL, I helped organize and promote the IAC19 Slack workspace, so I was in a good position to build and integrate a custom app for its members to use.</p><p>To this end, I created “Polar Bear Bot,” a friendly assistant that could answer common questions automatically—instead of demanding volunteer time and attention.</p><h3>What a conference bot should know</h3><p>First I had to map out what people might want to know during a conference. Context matters. Most use their phones, so I wanted to avoid simply sending them off to a website. Delivering bite-sized, meaningful information in short bursts was my goal.</p><blockquote>Delivering bite-sized, meaningful information to conference attendees in short bursts was my goal.</blockquote><p>Having worked on an earlier version of the bot for the 2018 IA Summit in Chicago, I had a starting point. But the venue was different, and the last iteration tried to do too much—for example, reporting the location of each floor’s restroom was perhaps too ambitious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0XRSkZcIj2lItkOJ1rDIrA.png" /><figcaption>A planning document I created during IA Summit 2018 served as the foundation to map user intents with system responses</figcaption></figure><p>I needed to narrow the scope based on information needs of users in Chicago. The bot was created in a tool called <a href="https://dialogflow.com/">DialogFlow</a>, and I used its history to discover the most common search queries. With that information, I was able to hone in on the following set of key questions:</p><ul><li>Where can I find the schedule?</li><li>What activities does IAC offer?</li><li>Who are the IAC19 organizers?</li><li>How can I provide feedback?</li><li>What is the WiFi information?</li><li>Where are restrooms located?</li><li>Who can I contact for AV support?</li><li>Is lunch provided?</li></ul><h3>Under the hood</h3><p>In total, I planned over 50 “intents” with DialogFlow, each one mapped to a couple of hundred programmed responses—some canned, many hand-written by yours truly. Intents are just a way to tell a chatbot what a person means when they say what they say. Of course, how people ask varies widely, so it’s important to find a solution that is flexible, ideally with an artificial intelligence engine that can interpret the variability of language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z7mLnJwuvBoVVQNjaf_3jA.png" /></figure><h3>Bringing Polar Bear Bot to Life</h3><p>I knew I needed a way to list the possible commands, so people could understand how the agent could serve them. I reached out to <a href="https://medium.com/u/17166f63bbc6">Jayneil Dalal,</a> someone who laid the foundation for IAC to use Slack in 2017. He gave me some helpful words of encouragement and even share some code that helped me produce a “menu” of sorts:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-0ajlm0bHqcsUW4jU9I5Kw.png" /><figcaption>A series of direct-message interactions with the conference chatbot</figcaption></figure><p>An aside: If you don’t know the significance of polar bears to the IA community, an illustration of the animal graces the cover of a seminal text in the field, <em>Information Architecture for the World Wide Web </em>(1998, O’Reilly Media)—now in its fourth edition.</p><p>While working on the chatbot, I bought a polar bear transformer online and brought it to the conference, knowing it would be right at home. To my delight, the authors of the book held a signing. It was too perfect. This is how the autographs of <a href="https://medium.com/u/71047237711c">Peter Morville</a>, <a href="https://medium.com/u/fb66d9db2c76">Louis Rosenfeld</a>, and <a href="https://medium.com/u/6220261a62d2">Jorge Arango</a> appear on plastic fur.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MKdySgfUkTQtiOAoky3b6w.jpeg" /></figure><h3>Room for development</h3><p>If I were a developer, and given more time, I would have implemented Slack’s <a href="https://api.slack.com/docs/message-buttons">interactive message buttons</a> to allow users to select prescribed responses, rather than having to type their next command. This would address the “magic word” problem. With an AI agent like this, it wasn’t always clear when Polar Bear Bot’s smarts would break down — and all too often we would see the bot fumble. It’s the same problem intelligent voice assistants have—without prompts, we don’t always know what they are capable of. Presenting the user with choices though buttons might alleviate some of that pressure of not knowing what to ask for.</p><h3>The takeaway</h3><p>Turns out most conference-goers on Slack want to connect with other human beings. Not many people engaged with Polar Bear Bot beyond simple requests for WiFi information. And that’s OK. Over the last two IA conferences in Chicago and Orlando, I learned a lot about the planning involved in training and implementing an artificially intelligent agent, and how people interact with them.</p><blockquote>I learned a lot about training and implementing an AI agent, but I helped in other ways as a volunteer</blockquote><p>I rose to the occasion to help in other ways as a conference volunteer, like putting my marketing communications expertise to work. I designed a <a href="https://twitter.com/search?f=images&amp;vertical=default&amp;q=%23IAC19%20from%3Atheiaconf%20since%3A2019-01-21%20until%3A2019-03-13&amp;src=typd">collection of Twitter cards</a> to promote the conference, I proofread IAC emails, and I helped respond on Slack during the event—like creating a new channel for veterans and organizing a <a href="https://docs.google.com/spreadsheets/d/1vpzbwBEv-FqTVxpCxux7pDkwmJQZDa58jrfl796we6c/edit#gid=1194159644">repository for presentation slides</a>.</p><p>Oh, and by the way, there was one more polar bear I met while in Orlando…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OFj89xI_LzMnhvAMulcEQg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a63bc44c6a37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing content grounded in  research]]></title>
            <link>https://medium.com/@wordydesigner/designing-content-grounded-in-research-728eec828389?source=rss-64f804618de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/728eec828389</guid>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[communication-planning]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Ken Caldwell]]></dc:creator>
            <pubDate>Wed, 03 Oct 2018 00:36:38 GMT</pubDate>
            <atom:updated>2018-10-03T00:56:58.582Z</atom:updated>
            <content:encoded><![CDATA[<h3>Designing content grounded in research</h3><h4>A social media content strategy project — Summer 2018</h4><h4>TL:DR</h4><p>Leading a project team in social media content strategy gave me valuable experience in project management, user experience research method, and the ability to make informed content design decisions based on solid evidence.</p><p>Big thanks to the team who executed the work throughout this project: Madison Atkins, Amanda Brown, Samantha DeRosia, &amp; Annaliese Gottschalk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v06QkW7WTsaq82BsOnccDQ.jpeg" /><figcaption>The project team from L–R: Madi Atkins, Ken Caldwell, Sam DeRosia, Annaliese Gottschalk, &amp; Amanda Brown</figcaption></figure><p>As a graduate student at the University of Michigan, I have been eager to bring value back to my full-time staff role at U-M Information and Technology Services (<a href="http://its.umich.edu/">ITS</a>). After completing my first academic year, I wanted to apply some of the research method I learned in a professional context.</p><p>This summer, I created just such an opportunity that also gave me <strong>leadership experience as project manager</strong>. Being the social media lead for ITS, I initiated a content strategy project to reinvigorate ITS’s use of Twitter (<a href="http://twitter.com/umichTECH">@umichTECH</a>) and build stronger engagement with our student audience. But I wanted to make sure the project deliverables were grounded in quality research.</p><blockquote>By following a well-defined research protocol, our project team produced a set of social media writing guidelines and evidence-based recommendations to assist content contributors.</blockquote><p>I created a project charge and research protocol, sought leadership approval, then led a team of interns through a crash-course in user experience research methodology. The structure I imposed included periods of <strong>scoping and discovery, audience analysis, and content design</strong>. Ultimately, the team produced a set of detailed guidelines for contributing staff writers to more effectively write for social media.</p><h3>Origin of the project</h3><p>Our account had grown a little stale, and as contributors to a shared platform, we had begun posting haphazardly and without enough intention and strategy behind our decisions. <em>When is the best time of day to post? Is it OK to repeat the same tweet from last month? Are we reaching our audience?</em></p><blockquote>The bottom line: we were not reaching our full potential to engage with U-M students and the broader Michigan IT community.</blockquote><p>In addition, there are multiple teams within ITS contributing content without a unified plan, tone, and schedule to guide their decisions.</p><h3>Project overview</h3><ul><li>Scoping and discovery (May 14–June 8)</li><li>Audience analysis (June 11–29)</li><li>Content design and creation (July 9–27)</li></ul><h4>Objectives</h4><ul><li>Support organization project communications</li><li>Improve social media engagement with target audiences</li><li>Experiment with new forms of social content and strategy</li><li>Empower team members to gain experience writing for social media</li></ul><h4>Scope of work</h4><ul><li>1,100 tweets analyzed by engagement rate</li><li>Content categories classified by topic area</li><li>Two interview protocols (for U-M student &amp; staff subjects)</li><li>Nine qualitative interviews</li><li>Competitive analysis of Big Ten social media accounts</li></ul><p>The primary goal was to increase audience engagement with U-M students and staff, as well as IT members across campus. To do this, one year’s worth of @umichTECH tweets (June 2017–July 2018) were added to a database and<strong> qualitatively coded based on theme/topic</strong>. Three university students and four ITS staff members were interviewed to discover what our audience did and did not want to see on the ITS Twitter account. A <strong>competitive analysis</strong> of other Big 10 university IT Twitter accounts was also created to better understand how our peers are using Twitter to engage with their audiences.</p><h3>Outcomes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*10wgE5ngy4tO6qHMzoF8rA.jpeg" /><figcaption>The intern team‘s poster outlines recommendations for staff content contributors. Poster by Madi Atkins, Amanda Brown, &amp; Sam DeRosia.</figcaption></figure><h4>Deliverables</h4><ul><li>Detailed finding/recommendation pairs</li><li>Overhauled social content guidelines</li><li>Refreshed editorial calendar</li></ul><h4>The best time of day to tweet</h4><p>By analyzing a year’s worth of tweets from our account (over 1,100), the team discovered that <strong>the highest engagement rates (e.g., likes and retweets) occurred between noon and 8 p.m.</strong> Peak engagement, as measured by outlying data, was around 3:30 p.m. This finding correlated with our most active time of day, and reinforced a target publishing window to our contributors who schedule content through the day.</p><h4>The most frequently tweeted topics</h4><p>By classifying each of the 1,100+ tweets from the prior year with simple categories, the team also verified that the most prolific topic was safe computing (43.5%). The other categories — and services, campus news, and jobs and training — ranged from 14% to 24%. And yet, the most engaged with posts related to campus news topics (47.2%). <strong>Insights like these guided the team’s recommendations</strong>, helping our content contributors tweet about topics that are more likely to engagement our audiences.</p><h3>Summary</h3><p>Leading a new project in social media content strategy gave me valuable experience in project management, user experience research method, and the ability to make informed content design decisions based on solid evidence. I was fortunate to have a dedicated team who performed at a high level. I believe there is no substitute for a clearly defined project charge, a highly-motivated team, and regular communication through weekly touch-base meetings.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=728eec828389" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Netflix of classic Nintendo games]]></title>
            <link>https://medium.com/@wordydesigner/the-netflix-of-classic-nintendo-games-1aad193a5266?source=rss-64f804618de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1aad193a5266</guid>
            <category><![CDATA[nintendo-switch]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[videogames]]></category>
            <dc:creator><![CDATA[Ken Caldwell]]></dc:creator>
            <pubDate>Sun, 19 Aug 2018 15:38:05 GMT</pubDate>
            <atom:updated>2018-08-19T16:22:57.164Z</atom:updated>
            <content:encoded><![CDATA[<h4>A graduate student interaction design project</h4><p>Imagine every Nintendo game at your fingertips: Nearly 40 years of influential games released for multiple generations of hardware. Making a choice might be difficult, like deciding what to watch on Netflix. Sure, Mario is a safe bet, but there are many hidden gems to enjoy.</p><p>A new service called Nintendo Switch Online <a href="https://twitter.com/NintendoAmerica/status/1030499527126659073">arrives in September 2018</a>. As a graduate student at University of Michigan’s School of Information (UMSI), I created an interactive prototype of what I’d like to see — especially when it comes to discovering classic games to play.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FSHLj48dnyNg%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DSHLj48dnyNg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FSHLj48dnyNg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/56129060952f8faf340d7e39a5f8084b/href">https://medium.com/media/56129060952f8faf340d7e39a5f8084b/href</a></iframe><p>For business reasons, I don’t expect Nintendo’s service to offer access to such a vast game library—but it doesn’t hurt to dream. Let me share my process.</p><h4>Scoping the project</h4><p>A complete online experience for Nintendo Switch should include many features: interaction with friends, live-streaming gameplay, connection with social media, and more. Those features, while expected by online gamers, would not have differentiated my design. Instead, <strong>I decided to focus on the problem of choosing what to play </strong>amid thousands of games. I devised a system that would help users define their game preferences, then receive tailored recommendations (i.e., a “wizard”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EwOap2tfmd48-sbOHeuf8A.jpeg" /><figcaption>The main navigation structure I designed for Nintendo Switch Online</figcaption></figure><h4>Defining the audience</h4><p>Good design is the result of asking, “<em>Who is this for?</em>” early and often. Interviewing my peers allowed me to create a targeted design that addresses specific user goals. I learned that successful design narrows the scope until the end result solves a unique problem. For my project, that problem is finding the right classic game to play.</p><p>I created two primary personas for whom Nintendo Switch Online might be designed — Corey the “core gamer” and Casey the “casual gamer.” Each have their own motivations and personality, and they have slightly different goals when they use the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*Ql9Y3LEIrWZC9voSbRoc3A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*2983tcHegAd8xsShla4WBw.jpeg" /><figcaption>Based on peer feedback, I developed two user personas to serve as the primary audience</figcaption></figure><h4>Making a wizard</h4><p>Starting at the Switch home screen designed by Nintendo, I added a new, system-level app for “Online,” followed by an onboarding message and the main navigation or landing page.</p><p>Players can explore their achievements and screenshots, but the focus is on finding and playing classic games. They can use the recommendation wizard, browse alphabetically, jump to their favorites, or see a random game. Another key feature lets them mark games as favorites to easily find and play later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R0wGJcpNMtWgiD23OQ8tDg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y1WSou2I06SXMaUyKPLOAg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dR-rqaFWUJoxkKJrIxz2yw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gnZqxfac7a9yGYcV9QZFLA.jpeg" /><figcaption>The wizard allows players to filter by single- or multi-player games, difficulty level, genre, and console generation</figcaption></figure><p>The game recommendation wizard is where the fun happens. The movie industry has undergone a renaissance of discovery and personalization, and I want to see that same innovation in videogames. There were over 750 titles released for the Nintendo Entertainment System (NES) in the U.S. alone. Add hundreds more from later generations and the library becomes difficult to sort and navigate. A recommendation system would help people find classic games they might enjoy, especially newcomers who don’t know where to start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*458c0ezHENkkc_kwPYd4PA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QpP6GuSczALQvbl8-pogbQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Js47S8rBwl3LUu5BGTfZYw.jpeg" /><figcaption>A question-block button leads to recommended games where users can browse, then jump in with the ‘Play Now’ button</figcaption></figure><h4>Sketching ideas</h4><p>My ideation process began on paper, where I drew eight high-level sketches derived from a storyboard of 40 small illustrations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ZMud6Z0U0x6bwZoURrs8g.jpeg" /></figure><p>These early sketches included ideas I chose not to prototype, like a mobile app that provides a second-screen experience and data exchange between players through the infrared capabilities of their Joy Con controllers. I also brainstormed location-based leaderboards that resemble high scores in an arcade — a place where gamers might gather and upload scores to digital billboards.</p><p>While this was a good creative exercise, some of the ideas were not core to the classic game experience I had in mind. I also wanted to focus my efforts on designing for the 16:9 aspect ratio.</p><p>I even produced a paper prototype in the actual size of Nintendo Switch, with cutouts of game artwork representing the user interface elements. This paper version proved to be a great way to test early ideas and gather feedback from my peers. In particular, I learned which interactions were intuitive and which could be improved before taking time to develop them on the computer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q3N12w6A0m0mJrnqNEgDVg.gif" /><figcaption>Testing a paper prototype helped surface design problems before working on a computer</figcaption></figure><h4>Potential impact</h4><p>Digital distribution is disrupting the videogame industry in the same way it did for television and movies. We no longer need to visit retail stores to buy games — we download them instead. The problem with vast, digital libraries is navigating the overwhelming number of choices. My solution recommends games based on player preference, aiding discovery in a medium rich with experiences that everyone can enjoy.</p><p><em>Thanks to </em><a href="https://medium.com/u/67553b2ea2bc"><em>Olivier Charavel</em></a><em> for the free </em><a href="https://medium.com/bpxl-craft/designing-for-the-nintendo-switch-32cacbe4c02d"><em>Switch UI Kit</em></a><em>. Shouts to Kyle Chang for the inspirational poster, “</em><a href="https://www.kylechang.net/fullscreen-page/comp-jcz6t5m4/6b0b2d1e-179b-4a7a-bce2-1ba132a24604/1/%3Fi%3D1%26p%3Dxzeif%26s%3Dstyle-jd9dhgrs"><em>The ABCs of the Nintendo Entertainment System</em></a><em>.” Also inspired by </em><a href="https://medium.com/games-ux/thoughts-on-the-nintendo-switch-user-interface-b441129f063d"><em>thoughts on the Switch UI</em></a><em> by </em><a href="https://medium.com/u/269bb90f584d"><em>Charlie Deets</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1aad193a5266" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond the classroom: UX consulting in University of Michigan’s Design Clinic]]></title>
            <link>https://medium.com/@wordydesigner/beyond-the-classroom-ux-consulting-in-university-of-michigans-design-clinic-37f3e365c9c5?source=rss-64f804618de8------2</link>
            <guid isPermaLink="false">https://medium.com/p/37f3e365c9c5</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[usability-testing]]></category>
            <category><![CDATA[community-engagement]]></category>
            <category><![CDATA[consulting]]></category>
            <dc:creator><![CDATA[Ken Caldwell]]></dc:creator>
            <pubDate>Thu, 07 Jun 2018 01:45:54 GMT</pubDate>
            <atom:updated>2020-02-10T14:50:10.343Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x1wYL8mDHrH7RpHjPCwIxw.jpeg" /><figcaption>The Canopy-Design Clinic team from L–R: Ken Caldwell, Brandon Keelan (client contact), Chuhan Hou, Huyen Phan, Mandy Shen, Chen Li, and Aalap Doshi (group mentor).</figcaption></figure><h3>TL:DR</h3><p>Design Clinic helped me grow as an information professional and design team member. It gave me firsthand experience in consulting and community engagement. But most of all, I learned how to bring my user experience research and design skills to fruition outside of the classroom.</p><p>Volunteering my time began as a desire to get engaged outside of the classroom at University of Michigan’s School of Information. But <a href="https://si.umich.edu/programs/professional-and-community-engagement/design-clinic">UMSI Design Clinic</a> taught me more than I could have imagined.</p><p>I applied to the extracurricular program knowing only that Design Clinic is a fast-paced, semester-long project in which a group of graduate students are matched with real-world clients. Beyond that, it was difficult to describe the commitment to family members: <em>Unpaid? No credit? Is that like an internship?</em> Not really, I told them, but let’s just call it that.</p><p>Above all, I wanted the chance to apply the knowledge I was gaining about interaction design, usability research, and information architecture. It turned out to be all of that and more.</p><h3>A celebrated client</h3><p>Having experience in healthcare marketing, I expressed interest in a client that was developing a product related to end-of-life care planning. I was accepted, and the client turned out to be <a href="https://madeatmichigan.umich.edu/ventures/venture/canopy/">Canopy</a>, the oft-awarded startup comprised of three U-M alums who were also participating in the <a href="http://cfe.umich.edu/techarb/">TechArb Student Venture Accelerator</a>.</p><p>Canopy has a clear vision for social impact. They aim to address a vast, underserved market of people who have hardly thought about the end of life, let alone talked with their loved ones about an advance care directive. In short, Canopy has set out to build a Turbo Tax-like solution to facilitate the process of documenting end-of-life care decisions.</p><p>To say they had already done their homework is an understatement. I was amazed at Canopy’s professionalism and ambition. But they wanted help from UMSI to design and prototype an early version of the system, and to begin testing it with real users. Enter the Design Clinic team.</p><h3>Gaining new perspective</h3><p>I was grouped with four other master’s students with different backgrounds than my own — international students from China and Vietnam who each brought a unique contribution to the table. This was why I came to UMSI: to learn from diverse people in rigorous group settings. I was pleased at how easily our team established norms, expectations, and roles, then began to research the complexity of personal healthcare.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eofrInSdhe3NMd48xh8jeQ.jpeg" /><figcaption>The Canopy-Design Clinic team brainstorming the scope of the interactive &amp; basic prototypes we created</figcaption></figure><h3>Methodical research</h3><p>Much like a full-term course, Design Clinic required weekly, in-person meetings, but we decided to meet for two more hours each Saturday to stay accountable to each other. We also devoted extra time to conduct qualitative interviews, usability tests, card sorting exercises, and post-interview analysis.</p><p>We focused on understanding the preferred tone and balance of information for in-product content, like empathetic questions about users’ values and medical preferences. We also carefully studied the format and delivery of that content— splitting our time between a traditional questionnaire versus interactive media. Through continuous research to <strong>test, analyze, design, and ideate</strong>, we gathered data in:</p><ul><li>9 unique interviews</li><li>5 card sorting exercises</li><li>4 comparative user tests</li><li>2 design iterations</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gflvoNBqcku2-QYYh-010g.jpeg" /><figcaption>I designed the final presentation poster to summarize our major findings</figcaption></figure><h3>My contribution to the team</h3><p>I served the team as a communications and content strategist, writing summaries, presentations, and more. <a href="https://umich.app.box.com/s/3kdgv24ykb22r0jiwwz1u4vex8nu4orv">See the final poster I designed</a>. To push myself into new areas, and to build on my expertise in desktop publishing and page layout, I also contributed to the team’s interactive prototype using Sketch app, a professional tool for interface designers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YbJ1hq_fv1RqIzCml2DbNQ.jpeg" /><figcaption>Chuhan Hou and Ken Caldwell planning the final month of Design Clinic with an outline of deliverables</figcaption></figure><h3>The takeaway</h3><p>I knew the group work of Design Clinic would benefit me as a information professional, but I was grateful to find a much deeper level of engagement that taught me how to be a better design team member. True collaboration is not about bringing a full agenda and preconceived ideas to the table. It’s about meeting team members on an equal level and taking the time to listen, creating the space for everyone to contribute. It’s about giving credit where it is due and enabling group decisions to emerge organically.</p><p>I also expanded my understanding of consulting and community engagement —representing a public university in support of a private organization, complete with agreements, contracts, and deliverables. But most of all, I learned how to bring user experience research and design skills to fruition outside of the classroom.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37f3e365c9c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>