<?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 Ayshan Ahmadova on Medium]]></title>
        <description><![CDATA[Stories by Ayshan Ahmadova on Medium]]></description>
        <link>https://medium.com/@ayshandesigner?source=rss-2e91396f16bf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-Zlm2P6sQepzrNDT</url>
            <title>Stories by Ayshan Ahmadova on Medium</title>
            <link>https://medium.com/@ayshandesigner?source=rss-2e91396f16bf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:35:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ayshandesigner/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[What happens when AI starts thinking with us instead of for us?]]></title>
            <link>https://medium.com/@ayshandesigner/what-happens-when-ai-starts-thinking-with-us-instead-of-for-us-525884c359f9?source=rss-2e91396f16bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/525884c359f9</guid>
            <category><![CDATA[human-centered-ai]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[human-thinking]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Ayshan Ahmadova]]></dc:creator>
            <pubDate>Wed, 13 May 2026 11:21:00 GMT</pubDate>
            <atom:updated>2026-05-13T11:21:00.627Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uM4i0IXEkLbSd-KRqw1hWA.png" /></figure><p>I want to be honest about how this article started. I was procrastinating on a job application, had a conversation with an AI about how to frame my experience, and halfway through realized I had no idea anymore which ideas were mine and which had come from the machine. It was not a bad feeling exactly. But it was a strange one. And it sent me down a rabbit hole I have been in for weeks.</p><p>There is a meaningful difference between using AI to do something and using AI to think about something. The first is straightforward: you offload a task, you get a result, you stay in charge. The second is murkier. When AI is inside your reasoning process, not just downstream of it, the relationship between you and your own thinking starts to shift in ways that are hard to describe and harder to measure.</p><blockquote>The concern is not that AI will think instead of us. It is that we will stop noticing when it has already.</blockquote><p>The first thing I read that helped me make sense of this was research on cognitive offloading, which is basically the science of how humans use external tools to reduce mental effort. Psychologists Risko and Gilbert wrote a useful piece on this in <em>Trends in Cognitive Sciences</em> a few years back. They argue that offloading is generally good: it frees up space for harder thinking. Writing a list, setting an alarm, and using GPS all of these help. The brain is not diminished by using tools. It was always meant to.</p><p>That framing made me feel better for a moment. Then I found a study out of MIT’s Media Lab by Kosmyna and colleagues that complicated things. They tracked brain activity in people who wrote with AI assistance versus those who wrote alone. The AI-assisted group produced cleaner work by most external measures. But they also showed noticeably less activity in the parts of the brain associated with deep focus and creative engagement. Their brains were, in a measurable sense, less involved in what they were making. The researchers used the phrase “cognitive debt” to describe what was quietly accumulating beneath the surface.</p><blockquote><strong>What made me pause</strong></blockquote><blockquote>I tried an experiment on myself. I wrote a rough draft of something with no AI at all, just me and a blank document, sitting with the discomfort of not knowing what I wanted to say. Then I did the same exercise, starting with an AI conversation. The second version came together faster and read more smoothly. But when someone asked me a week later what I had written about, I remembered the first piece clearly and the second one only vaguely. Something about the struggle had made the thinking stick.</blockquote><p>There is also a fascinating older idea from psychology called transactive memory, developed by Daniel Wegner in the late eighties, that I kept coming back to. The idea is that people in relationships and teams do not each store all the knowledge they share. Instead, they store a kind of map of who knows what, and retrieve information through each other when they need it. Couples do this. So do good teams. Researchers like Noy and Zhang have started applying this lens to AI, suggesting that AI is becoming a genuine node in how we store and access knowledge, not just a search engine we occasionally query.</p><p>That framing helped me understand why the shift feels significant. It is not that AI is making us lazier. It is that it is becoming part of the architecture of how we think, in ways we have not consciously chosen and may not fully understand yet. And unlike a colleague or a partner whose biases and gaps you learn over time, AI’s tendencies are harder to inspect. It sounds confident even when it is wrong. It has no hesitation, no instinct to say “I am not sure about this one.”</p><p>The thing I keep landing on is sequence. Teresa Amabile’s research on creativity, which I came across through a course in my master’s program, suggests that early-stage idea generation is particularly sensitive to external input. Premature constraint or direction tends to narrow what people come up with. This implies that bringing AI in at the start of a thinking process is different from bringing it in after you have already struggled with something on your own. The struggle is not the obstacle. It is part of how the thinking gets built.</p><p>I do not think the answer is to use AI less. I think the answer is to use it with more awareness of where in the thinking process you are inviting it in. Form your own rough view first. Then use AI to challenge it, extend it, and find the holes. That way, the frame is yours. The AI is sharpening something real, not constructing something in its place.</p><p>I am still working through a lot of this. I probably will be for a while. But that question I started with, of whose ideas those were in that job application conversation, I think the honest answer is: mostly mine, but shaped in ways I cannot fully account for. Which is probably true of most good thinking, actually. The difference is that I usually know who I am talking to.</p><blockquote><strong>Where I read</strong></blockquote><blockquote>The research on cognitive offloading that shaped the first half of this piece comes from Risko and Gilbert’s 2016 paper in <em>Trends in Cognitive Sciences</em> — it is freely available and worth reading even if you are not a psychology person. The MIT brain activity study is by Kosmyna et al., published as a preprint through MIT Media Lab in 2023, and you can find it under the title “Your Brain on ChatGPT.” Wegener’s original transactive memory framework is from a 1987 book chapter that gets cited constantly; a more accessible version of the idea shows up in a lot of team cognition literature since. The Noy and Zhang productivity study was published in <em>Science</em> in 2023 and got a lot of attention when it came out — easy to find. Teresa Amabile’s creativity research is collected in her book <em>Creativity in Context</em>, though a lot of it is also summarized in her Harvard Business Review writing, which is free online.</blockquote><p><em>If something here resonated or if you think I got something wrong, comments are open. I am genuinely still figuring this out.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=525884c359f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing with AI: what happens when creativity meets automation?]]></title>
            <link>https://medium.com/design-bootcamp/designing-with-ai-what-happens-when-creativity-meets-automation-71a207b3adb7?source=rss-2e91396f16bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/71a207b3adb7</guid>
            <category><![CDATA[ai-design]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ayshan Ahmadova]]></dc:creator>
            <pubDate>Thu, 07 May 2026 22:38:20 GMT</pubDate>
            <atom:updated>2026-05-07T22:38:20.656Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BTBdhK0Ao0sXLw5q1yxufA.png" /></figure><p>I have been designing things, in one form or another, for about three years. Interfaces, pitch decks, Mobile apps, brand systems. And for most of that time, the hardest part of the job was not execution. It was the blank page. The moment before anything exists, when you have to reach into yourself and pull out a direction, an instinct, a starting point. That part always felt irreducibly human.</p><p>Then AI image and design tools started getting genuinely good. And now I spend a lot of time thinking about a question I did not expect to be asking: if a machine can generate a dozen credible starting points in thirty seconds, what exactly am I for?</p><p>The easy answer is that AI handles execution and humans handle meaning. The machine generates options, the designer curates and directs. And that is partially true. AI tools are genuinely remarkable at producing visual output that is technically competent: layouts that follow the rules, color combinations that work, type that sits correctly on a grid. What they are less good at is knowing <em>why</em> any of it matters. They do not know what a brand is trying to say about itself, or what a user needs to feel when they land on a page, or why this particular shade of blue is wrong for this particular client even though it is objectively a fine blue.</p><p>That interpretive layer is still human territory. But the boundaries are moving faster than most of us expected, and the honest conversation in design circles right now is not really about replacement. It is about what happens to craft when the hard parts get easier.</p><blockquote><strong>Something I noticed</strong></blockquote><blockquote>I started using an AI tool for early-stage moodboarding about eight months ago. It shortened that phase from a few days to a few hours. But I also noticed I was presenting concepts to clients sooner, with less of my own opinion baked in. The work was faster, but I was less attached to it. And when clients pushed back, I had less to defend, because I had not fought for the direction in the same way I used to. The struggle, it turned out, was doing something I had not fully valued.</blockquote><p>Researchers who study creativity have a name for the kind of thinking that happens during that struggle. They call it <em>generative friction</em>: the productive difficulty of working through constraints, dead ends, and bad ideas before arriving at something genuinely good. Mihaly Csikszentmihalyi, whose work on flow and creativity I came across in grad school, argued that the quality of creative output is closely tied to how much engagement the person brings to the process. Engagement, in that framework, is not separate from effort. It is built from it.</p><p>None of this is an argument against using AI in design. The tools are too useful to ignore, and the designers who are figuring out how to work with them well are doing genuinely interesting things. The question worth asking is more specific: at which stage of the process does AI help, and at which stage does it skip something that matters?</p><blockquote><strong>Where AI genuinely helps</strong></blockquote><blockquote>Generating volume early, exploring visual directions quickly, removing tedious production work, and freeing up time for the thinking that actually requires a human.</blockquote><blockquote><strong>Where it gets complicated</strong></blockquote><blockquote>When speed replaces judgment. When a designer curates AI output without forming their own view first. When the process produces work nobody fully owns.</blockquote><p>There is also a cultural question sitting underneath all of this that does not get talked about enough. Design has always been a field where junior practitioners learn by doing hard, slow, sometimes boring work. Redrawing things by hand. Staring at a layout that is not quite right until you understand why. That slow accumulation of pattern recognition is how taste develops. If AI removes most of that friction from the early career experience, we may end up with designers who can direct AI output competently but who have not built the underlying judgment that makes direction meaningful.</p><p>This is not a new concern. Every generation of design tools has prompted some version of it, from desktop publishing in the eighties to templates in the two-thousands. And each time, the field adapted. The tools changed what designers spent their time on, but the core of the job, understanding people and making meaning visible, stayed intact.</p><p>I believe that will happen again. But I also think it will require designers to be more deliberate about where they let AI into their process, and more honest about what it is costing them when they let it in too early. The blank page was uncomfortable. It was also, looking back, where a lot of the most important thinking happened. Whatever replaces it should at least earn the same respect.</p><p><a href="https://www.rochester.edu/warner/lida/wp-content/uploads/2022/11/creativity-by-mihaly-csikszentmihalyi.pdf">Csikszentmihalyi’s ideas on creativity, engagement,</a> and flow come from his book <em>Creativity: Flow and the Psychology of Discovery and Invention</em>, which is dense but worth it — a lot of his core arguments are also summarized in his TED talk if you want the shorter version. The concept of generative friction appears across creativity and design research literature; Don Norman’s writing on design cognition touches on related ideas, particularly in <em>The Design of Everyday Things</em>. For more current thinking on AI and design practice specifically, the Nielsen Norman Group has been publishing ongoing research reports on <a href="https://www.nngroup.com/topic/ai/">AI’s impact on UX and design workflows</a> that are grounded and practically useful. Adobe’s own research team has also published findings on how designers are actually integrating generative tools, available through their blog.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71a207b3adb7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/designing-with-ai-what-happens-when-creativity-meets-automation-71a207b3adb7">Designing with AI: what happens when creativity meets automation?</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The real reason AI feels so different at work this time ‍]]></title>
            <link>https://medium.com/@ayshandesigner/how-ai-is-changing-the-way-we-make-decisions-in-organizations-2ac293e59432?source=rss-2e91396f16bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ac293e59432</guid>
            <category><![CDATA[changing-the-world]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[organizational-change]]></category>
            <dc:creator><![CDATA[Ayshan Ahmadova]]></dc:creator>
            <pubDate>Thu, 07 May 2026 14:04:44 GMT</pubDate>
            <atom:updated>2026-05-07T14:06:21.643Z</atom:updated>
            <content:encoded><![CDATA[<p>There’s a version of this story we’ve all heard before. A new technology arrives, consultants declare it will transform everything, companies buy the licenses, and then quietly, without fanfare, it gets absorbed into the background like every other tool before it. The org chart stays the same. The meetings stay the same. Life goes on.</p><p>That’s what a lot of people expected from AI at work. Another wave of hype. Another dashboard nobody uses. But something feels different this time, and it’s not just because the tools are smarter. It’s because of <em>where</em> AI is showing up: right in the middle of how people actually spend their days.</p><blockquote>Previous technology automated what we did around the edges. AI is showing up in the middle of the work itself.</blockquote><p>Think about what past waves of workplace technology touched. Email sped up communication. Spreadsheets improved number-crunching. CRMs organized contacts. Each of those tools had a lane. They sat at the edges of how people thought and decided: useful, yes, but separate from the actual judgment calls that define most professional work.</p><p>AI doesn’t have a lane. It drafts the email, summarizes the meeting, surfaces the data pattern, and suggests the next step, sometimes before you’ve even framed the question. For the first time, technology is sitting inside the thinking process, not just around it. That’s why it feels different. Because it <em>is</em> different.</p><p><strong><em>Picture this</em></strong></p><p><em>A product manager used to spend two hours every Monday pulling together a status update from five different tools: Jira tickets, Slack threads, customer feedback, analytics dashboards. Now she describes what she needs in plain language, and a first draft is waiting in under a minute. She still edits it. She still owns it. But those two hours are now thirty minutes, and she uses the time she saved to actually talk to customers. Her job didn’t disappear. It quietly got better.</em></p><p>That story isn’t exceptional. It’s becoming ordinary. And that normalization is exactly what’s unsettling some people, even those who can see the upside. Because when a tool starts touching how you think, not just what you produce, the question of identity creeps in. <em>If AI writes the first draft, is it still my work? If it surfaces the insight, is it still my expertise?</em></p><p>Those are fair questions. But they might be the wrong ones to start with. A better question is: what does your judgment actually look like when it no longer has to fight through all the noise first?<em> Most people haven’t had a chance to find out, because the noise has always been part of the job.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XeAiuK2jeQMLFQ4bnQdHOg.png" /></figure><p>The organizations that are adapting well share one thing: they’re treating AI less like a software rollout and more like a change in working conditions, something that requires honest conversations about roles, expectations, and what good work looks like now. The ones struggling are the ones pretending nothing has fundamentally shifted, while quietly watching their people burn hours on things that no longer have to be hard.</p><p>This wave of AI feels different because it’s asking something different from us: not just to use a new tool, but to rethink what our time is actually for. That’s uncomfortable. It’s also, if you let it be, a genuine opportunity to do the parts of your work you actually care about. More of the time.</p><p><strong><em>If this got you thinking, share it with someone on your team who’s still deciding how to feel about all of this. The conversation is worth having out loud.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ac293e59432" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How AI Is Changing the Way We Make Decisions in Organizations]]></title>
            <link>https://medium.com/@ayshandesigner/how-ai-is-changing-the-way-we-make-decisions-in-organizations-4e6f08de505b?source=rss-2e91396f16bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e6f08de505b</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Ayshan Ahmadova]]></dc:creator>
            <pubDate>Wed, 06 May 2026 12:52:47 GMT</pubDate>
            <atom:updated>2026-05-06T12:52:47.843Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*17Zje8GynLj0Be4V" /></figure><p>Think about the last big decision you made at work. Chances are it involved a long meeting, a few spreadsheets, maybe a gut feeling, and a lot of back-and-forth. That process hasn’t changed much in decades. But quietly, in offices around the world, AI is starting to rewire it — not dramatically, not all at once, but in ways that are beginning to add up.</p><p>For most of organizational history, decisions flowed through a familiar hierarchy: data gets collected, someone interprets it, leadership weighs in, and a choice gets made. The bottleneck was almost always human bandwidth — there was simply too much information and not enough time. AI doesn’t solve that problem by thinking faster than us. It solves it by doing the heavy lifting we were never meant to do ourselves: sifting, pattern-matching, flagging anomalies, and surfacing the right question at the right moment.</p><p><em>Real-world example</em></p><p>A retail chain with hundreds of stores used to rely on regional managers reviewing monthly sales reports to decide which products to restock. The process took weeks, and by the time decisions were made, the moment had often passed. After introducing an AI system that continuously monitored inventory, weather patterns, and local purchasing trends, store-level restock decisions became near-automatic — flagged and ready for a manager to approve in minutes, not weeks. The managers didn’t disappear. Their role just shifted: less time on data, more time on judgment calls the AI couldn’t make.</p><p>That shift from making decisions to <em>reviewing</em> them is the real story here. It can feel uncomfortable at first. Managers who built careers on reading spreadsheets and trusting instincts sometimes find it hard to hand the analysis layer over to a machine. But the leaders who’ve navigated it well tend to say the same thing: AI didn’t take their judgment away. It gave them better things to apply it to.</p><blockquote>Before AI</blockquote><blockquote>Gather data manually, interpret patterns, debate the numbers, then decide — often weeks later.</blockquote><blockquote>With AI</blockquote><blockquote>AI surfaces patterns and flags decisions; humans review context, weigh tradeoffs, and act fast.</blockquote><p>Of course, none of this is without risk. AI systems reflect the data they’re trained on, which means biases get baked in quietly, and blind spots can go undetected for a long time. Organizations that lean too heavily on automated recommendations without questioning them aren’t faster decision-makers — they’re just outsourcing their mistakes at scale. The antidote isn’t to slow down AI adoption. It’s to build cultures where people feel safe asking “why did it recommend this?” and empowered to push back when something doesn’t sit right.</p><p>The organizations getting this right aren’t the ones with the most sophisticated AI tools. They’re the ones that have thought carefully about what decisions <em>should</em> be automated, which ones always need a human in the loop, and how to keep those distinctions clear as the technology evolves. That’s not a technology problem. It’s a leadership one — and for now, at least, it still belongs entirely to us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e6f08de505b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ “T-Shaped Designer”? What Does That Even Mean?]]></title>
            <link>https://medium.com/@ayshandesigner/t-shaped-designer-what-does-that-even-mean-ea7e56b481ae?source=rss-2e91396f16bf------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea7e56b481ae</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[skills-development]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[uxui-design]]></category>
            <category><![CDATA[career-growth]]></category>
            <dc:creator><![CDATA[Ayshan Ahmadova]]></dc:creator>
            <pubDate>Tue, 06 May 2025 18:09:19 GMT</pubDate>
            <atom:updated>2025-05-06T18:09:19.383Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve been browsing design job listings lately, there’s a good chance you’ve seen this phrase pop up:</p><blockquote><em>“We’re looking for a T-shaped designer.”</em></blockquote><p>T-shaped? What’s that supposed to mean? Is it a design style? A personality type? Some kind of strange workout routine?</p><p>Don’t worry — it’s none of those. While it might sound a bit buzzword-y, the idea behind it is actually pretty practical (and helpful). Let’s break it down in plain, human language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oHFFs9dQdeik4jBAYXVP9A.png" /></figure><h3>👀 So, What Does Being “T-Shaped” Look Like in Real Life?</h3><p>Let’s bring this idea down to earth with a few real-world examples. A T-shaped designer isn’t someone who knows <em>everything</em> — it’s someone who’s great at one thing and familiar enough with others to connect the dots.</p><p>Here’s how that might play out:</p><h4>🖌️ Visual Designer</h4><ul><li><strong>Deep strength:</strong> Visual storytelling, typography, layout, branding</li><li><strong>Also understands:</strong> Design systems, user flows, how their work hands off to developers</li></ul><h4>🔍 UX Researcher</h4><ul><li><strong>Deep strength:</strong> User interviews, usability testing, generating insights</li><li><strong>Also understands:</strong> Wireframing, product strategy, collaboration with design and PMs</li></ul><h4>🧩 Product Designer</h4><ul><li><strong>Deep strength:</strong> UX/UI design, prototyping, interaction design</li><li><strong>Also understands:</strong> Front-end basics, business goals, accessibility, and even content strategy</li></ul><p>Each of these designers is grounded in their specialty — but they also know just enough about other areas to make collaboration smoother, decisions smarter, and outcomes stronger.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VFlrkji6hG7ZyWrTHGtvjg.png" /></figure><h3>🚀 How Do You Grow Your “T”?</h3><p>You don’t need to become a unicorn overnight. Here’s how to build your T-shape naturally:</p><ol><li><strong>Start with your core</strong><br> What’s your thing? Double down on it. Build that vertical bar.</li><li><strong>Stay curious</strong><br> Read about nearby fields. Chat with your dev or research friends. Ask questions.</li><li><strong>Collaborate cross-functionally</strong><br> Pair with people outside your role. Observe their process.</li><li><strong>Take small steps</strong><br> Learn Figma’s dev handoff tools. Try writing microcopy. Sit in on a user test.</li><li><strong>Don’t force it</strong><br> Your T-shape is unique. You don’t need to be a master of everything — just a <em>connector</em> between worlds.</li></ol><h3>❌ Common Misconceptions</h3><p>Let’s bust a couple myths:</p><ul><li><strong>“T-shaped means doing everything.”</strong><br> Nope. It means <em>doing one thing deeply</em>, and <em>being aware of others</em>.</li><li><strong>“It’s just a buzzword.”</strong><br> Maybe sometimes — but when used right, it describes a real kind of collaborator. One who thrives on teams.</li></ul><h3>🧠 Wrapping It Up</h3><p>The whole idea of being a T-shaped designer isn’t about perfection — it’s about growth. Writing this, I’ve been exploring the topic right alongside you. The more I researched and reflected, the more I saw how much this mindset matters in real creative work.</p><p>So thanks for learning with me. I hope this helped clear things up — and maybe even sparked a few ideas for your own journey.</p><p>Let’s keep growing, one skill (and one connection) at a time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea7e56b481ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>