<?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 Kim on Medium]]></title>
        <description><![CDATA[Stories by Kim on Medium]]></description>
        <link>https://medium.com/@kimberry?source=rss-4e78ac5adf44------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MM-Aw-ZECIui86_9YxheBw.jpeg</url>
            <title>Stories by Kim on Medium</title>
            <link>https://medium.com/@kimberry?source=rss-4e78ac5adf44------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:56:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kimberry/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[The Rebirth of the Input Field — and the Reality of Designing with and for GenAI Today]]></title>
            <link>https://medium.com/@kimberry/the-rebirth-of-the-input-field-and-the-reality-of-designing-with-and-for-genai-today-8ad2c1fbfd7c?source=rss-4e78ac5adf44------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ad2c1fbfd7c</guid>
            <dc:creator><![CDATA[Kim]]></dc:creator>
            <pubDate>Wed, 15 Oct 2025 04:59:21 GMT</pubDate>
            <atom:updated>2025-10-15T05:18:52.575Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The Rebirth of the Input Field — and the Reality of Designing with and for GenAI Today</strong></h3><p>In 2025, the humble input field is doing all the heavy lifting for UI designers. It’s everywhere. It’s become the universal interface for Gen AI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*jM8wPaAY6arjGOJU7gRqXg.png" /><figcaption><a href="https://www.w3schools.com/tags/tag_input.asp">https://www.w3schools.com/tags/tag_input.asp</a></figcaption></figure><p>But it’s not just an input field, it’s the kitchen sink of UI components — buttons, menus, filters, switches — all under the umbrella of <em>more.</em></p><figure><img alt="Annotations on top of the most popular GenAI input fields" src="https://cdn-images-1.medium.com/max/1018/1*sM29c-vg_BfEw50pB17quA.png" /><figcaption>Annotations on top of the most popular GenAI input fields today</figcaption></figure><p>We’re in the MS-DOS era of AI interfaces — typing commands into boxes, one prompt at a time. As Dylan Field put it, “In ten years, we’ll look back and say, <em>can you believe we just had this chat box?</em>”</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-7Qz7tSTfUU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-7Qz7tSTfUU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-7Qz7tSTfUU%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e1f263e4872d3df3e15658986371d5e8/href">https://medium.com/media/e1f263e4872d3df3e15658986371d5e8/href</a></iframe><p>Most of us aren’t designing for Gen AI yet — we’re designing <em>with</em> it.</p><p>Over four-fifths (83 percent) of creative professionals said they’re using generative AI tools in their work. (<a href="https://blog.adobe.com/en/publish/2024/02/02/creative-pros-generative-ai-usage">Adobe Blog</a>)</p><p>Tools like ChatGPT, Figma AI, and CoPilot are already part of the daily workflow for creatives, but while we’re fiercely designing <em>with</em> it, most are not yet designing <em>for</em> it.</p><p>I get it though — designing for AI is really hard<strong>.</strong> Ioana Teleanu (UX Goodies) has said <em>“In the future, everyone will see their own version of the internet.”,</em> and that future is already emerging, but users won’t even know it without obvious cues like typewriter effects or explicit notifications.</p><p>There are a few early glimpses of what’s next are starting to emerge — interactions like Google’s Circle to Search or new browser-side panels like Dia and Mariner. Or Peter Smart’s dynamically inserted content, from the Generative Interfaces talk.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FA5rniBTm2uo&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DA5rniBTm2uo&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FA5rniBTm2uo%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8f5af320932f52d3d5c00c5f0be3d3e2/href">https://medium.com/media/8f5af320932f52d3d5c00c5f0be3d3e2/href</a></iframe><p>This feels like biggest opportunity to shape how people interact with technology since Xerox introduced the desktop metaphor in 1973.</p><p>So how do we move past the input field?</p><p><em>What will be the Desktop Metaphor to the MS-DOS of AI?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ad2c1fbfd7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Supercharging My Designer Toolkit with Notion A.I.]]></title>
            <link>https://medium.com/@kimberry/supercharging-my-designer-toolkit-with-notion-a-i-eaa52ec7b6e8?source=rss-4e78ac5adf44------2</link>
            <guid isPermaLink="false">https://medium.com/p/eaa52ec7b6e8</guid>
            <category><![CDATA[notion-ai]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[notion]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Kim]]></dc:creator>
            <pubDate>Mon, 04 Aug 2025 11:09:34 GMT</pubDate>
            <atom:updated>2025-08-04T11:09:34.308Z</atom:updated>
            <content:encoded><![CDATA[<p>Like many folks, over the years I’ve built up my own personal repository — a curated collection of methods, approaches, points of view, and examples of what good looks like in experience design. This living library in Notion has become a daily companion. Whether I’m writing a research discussion guide, framing a new project approach, or just looking for examples of thoughtful UI, it’s my go-to starting point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p7xe4gob4OujVjh5wVtHCQ.png" /></figure><p>Since the repository already lives in Notion, I decided to experiment with Notion<strong> </strong>A.I.<strong> </strong>— not just as a writing assistant, but as a way to unlock and reuse the thinking I’ve already captured.</p><p>Here are a couple of experiments I’ve run so far — and what came out the other side.</p><h3><strong>Experiment #1: Generating a Research Plan</strong></h3><p>I wanted to see how well Notion A.I. could help craft a research plan — something I usually pull together from a few core components.</p><p>I created a fake research objective: <em>Understand people’s attitudes and behaviours towards digital privacy in everyday apps.</em></p><p>Then I asked ChaptGPT to write me a Notion A.I. prompt to:</p><ul><li>Write a research plan focused on objective</li><li>Recommend sample sizes, with rationale for the numbers</li><li>Outline a discussion guide</li><li>Include a simple recording consent and privacy notice</li></ul><p><strong>Notion A.I. Prompt</strong></p><figure><img alt="A detailed prompt for Notion A.I." src="https://cdn-images-1.medium.com/max/1024/1*c9YE7Td6XzRsWtVFi3KrYw.png" /></figure><p><strong>Output</strong></p><figure><img alt="Recording of Notion A.I. generating a response to an A.I. prompt" src="https://cdn-images-1.medium.com/max/1024/1*nfNX8CHrMbkGZgt3pdSNxQ.gif" /></figure><h3>Experiment #2: Crafting a Slide on Surprise &amp; Delight in UX</h3><p>For this one, I wanted to create a slide that explains the concept of Easter Eggs or moments of Surprise &amp; Delight in UX — something small, joyful, and unexpected that adds character to a product.</p><p>So, I asked ChaptGPT to write me a Notion A.I. prompt to:</p><ul><li>Write a compelling headline and a short blurb explaining what it is</li><li>Include an external quote or reference that supports why it’s valuable</li><li>List 1–2 things companies should think about before adding these experiences</li><li>Suggest where to add images — pulling from my UI Inspiration gallery</li></ul><p><strong>Notion A.I. Prompt</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lmXLhQh7JkrW4ZREHHoW8w.png" /></figure><p><strong>Output</strong></p><figure><img alt="Recording of Notion A.I. generating a response to an A.I. prompt" src="https://cdn-images-1.medium.com/max/1024/1*eBSko0HtSmjYXFIdqx7hig.gif" /></figure><h3>Experiment #3: Design Challenge</h3><p>For the final experiment, I wanted to see how Notion A.I. could leverage my repository to create a realistic project plan based off of a Design Challenge.</p><p>ChatGPT helped me frame up the challenge — <em>How might we improve the daily public transport experience for students across Victoria — making it more accessible, reliable, and student-friendly?</em></p><p>And the requirements for the Project plan for Notion A.I.</p><ul><li>Suggested project duration (weeks or phases)</li><li>Recommended team composition (roles and disciplines)</li><li>Key activities for each phase (e.g. research, synthesis, ideation, prototyping, testing)</li><li>Main artefacts and deliverables for each phase (e.g. journey maps, insights summary, concept mockups, service blueprint)</li></ul><p><strong>Notion A.I. Prompt</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mcRL-3vi5346GiAAOV4AAw.png" /></figure><p><strong>Output</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pTrrf-3qzNtA_QVBqBxZkQ.gif" /></figure><h3>Key Observations</h3><p><strong>Tagged Content vs Notion A.I. Content</strong></p><p>It’s difficult to tell how much tagging the sources of content influenced the outputs generated. In the Design Challenge test, there were not significant differences between the project plans generated when I tagged my Design Toolkit and when I didn’t.</p><p><strong>I still felt the urge to work in ChatGPT</strong></p><p>I found it interesting that I felt more comfortable using ChatGPT as a scratch pad to work out the prompts and details, then would execute in Notion.</p><p>It could possibly because Chats feel more disposable whereas Notion A.I. creates a page which feels more final. This reminds me of people saving their good ideas for Moleskins (Notion) while actually using a cheap notebook (ChatGPT) for working.</p><p><strong>Weaving a story</strong></p><p>In the second experiment — Crafting a Slide, I was hoping that Notion A.I. was able to extract images from my UI Examples Database and insert them into the content directly, however it only made reference to them. Similarly, in the first experiment — Research Plan, I asked it to include some relevant quotes from well-known designers from a Quotes Database I have, but it just lumped them at the end of the page.</p><h3>Final Thoughts</h3><p>Although I will be more likely to use Notion A.I. now that I’ve experimented with it a little bit, and it’s definitely faster at searching and curating my own content, I wouldn’t say it has supercharged My Designer Toolkit at this stage.</p><p>What would change my mind? Maybe…</p><ol><li>An interface (probably a chat) to go back and forth a little bit before committing to the content</li><li>Notion A.I. slowing down a little bit, and finessing the content. For example, insert those images or quotes in the right spots (see take-aways above)</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eaa52ec7b6e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m cautiously confident that I can use A.I. as a proxy for design research]]></title>
            <link>https://medium.com/@kimberry/im-cautiously-confident-that-i-can-use-a-i-as-a-proxy-for-design-research-f934d7fbbf4b?source=rss-4e78ac5adf44------2</link>
            <guid isPermaLink="false">https://medium.com/p/f934d7fbbf4b</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design-research-methods]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Kim]]></dc:creator>
            <pubDate>Tue, 09 Jan 2024 03:50:02 GMT</pubDate>
            <atom:updated>2024-01-09T03:50:02.668Z</atom:updated>
            <content:encoded><![CDATA[<p>As an experiment, I used ChatGTP to see if I could generate realistic design research outputs based on a hypothetical brief.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oI6k8w8r0QZprhi1DiLpdA.png" /><figcaption>A candid landscape close up photo of someone on their bike outside of a Sydney train station completing a survey (DALL•E)</figcaption></figure><h4>The brief</h4><p>Reimagine the public transport digital experience for a major city.</p><h4>My hunt statement</h4><p>To understand the sentiment towards commuting to work.</p><h3>I asked Chat GPT to write some customer quotes, hoping for what I would expect to hear in user interviews.</h3><pre>write 12 hypothetical but realistic quotes from Sydneysiders about how they feel about commuting to work in 2023</pre><p>Initially, the quotes returned were quite kitsch and didn’t provide any useful insight. For example:</p><blockquote>“Another day, another journey. The city beckons, and I’m ready to conquer it!”</blockquote><p>Tweaking the prompt helped quotes to feel more genuine, but was still a mixed bag. For example, this one is getting better…</p><blockquote>“Commuting can be exhausting, but it’s also my buffer zone between home and work, a transition I’ve come to appreciate.”</blockquote><p>While this one sounds like I’m interviewing a poet…</p><blockquote>“As much as I love my job, the travel time feels like a theft from my day, lost in transit.”</blockquote><p>After upgrading to ChatGPT4, it immediately introduced new themes — peak hours, price of petrol, different modes of transit, health — and I started believing the quotes.</p><blockquote>“The cost of petrol is killing me. I’m seriously considering switching to an electric car.”</blockquote><h3>Quotes alone weren’t cutting it, so I asked a simpler question.</h3><pre>what are the top 6 sentiments towards commuting in Sydney in 2023?</pre><p>While the quotes on their own lacked context and depth, asking for “the top 6 sentiments” returned interesting results which paired with the original quotes started to feel immediately more useful.</p><blockquote><strong>Preference for Remote Work</strong>: A significant number of people still prefer working from home, finding the commute to be a major inconvenience compared to the comfort and flexibility of remote work.</blockquote><blockquote><strong>Environmental and Health Consciousness</strong>: There’s an increasing trend towards more sustainable and health-conscious commuting options, like cycling or walking, though concerns about adequate infrastructure like bike lanes are also evident.</blockquote><h3>Next I wanted to add some quantitative data, but I didn’t know what existed. So I just asked ChatGPT.</h3><pre>what quantitative data is available on Sydney commuters?</pre><p>There were two stats that were relevant to my themes. However, I probably could have found these by just Googling.</p><ul><li>In 2022, Australians were spending on average 54 minutes per day commuting, which amounts to approximately 169 hours per year</li><li>In 2021, over half of the working population (53.1%) in Australia drove themselves to work. This was a decline from the peak in 2016 when 62% of the employed population drove to work</li></ul><p>Reference: <a href="https://www.abs.gov.au/articles/australias-journey-work">https://www.abs.gov.au/articles/australias-journey-work</a></p><h3>Bringing it all together</h3><p>In about 90 minutes, I was able to curate two themes that articulate Sydneysiders sentiments towards commuting.</p><blockquote><strong><em>Theme 1: Preference for Remote Work</em></strong></blockquote><blockquote><em>A significant number of people still prefer working from home, finding the commute to be a major inconvenience compared to the comfort and flexibility of remote work.</em></blockquote><blockquote>“I miss the days of working remotely. Spending over an hour on the train each day is exhausting.”</blockquote><blockquote><em>In 2022, Australians were spending on average 54 minutes per day commuting, which amounts to approximately 169 hours per year.</em></blockquote><blockquote><strong><em>Theme 2: Environmental and Health Consciousness</em></strong><em>:</em></blockquote><blockquote><em>There’s an increasing trend towards more sustainable and health-conscious commuting options, like cycling or walking, though concerns about adequate infrastructure like bike lanes are also evident.</em></blockquote><blockquote>“Cycling to work has been amazing for my health, but I wish there were more bike lanes in the city.”</blockquote><blockquote><em>In 2021, over half of the working population (53.1%) in Australia drove themselves to work. This was a decline from the peak in 2016 when 62% of the employed population drove to work.</em></blockquote><h3>When you are not able to speak to your users, or in the absence of existing primary research, ChatGPT can be helpful to curate synthetic research insights.</h3><p>It will be helpful to think of them as assumptions that need to be validated, rather than robust insights that you can base design decisions on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f934d7fbbf4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>