<?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 Silvia Hourigan on Medium]]></title>
        <description><![CDATA[Stories by Silvia Hourigan on Medium]]></description>
        <link>https://medium.com/@silvszak?source=rss-5f1b06d734eb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*d5tkzRlzmumUSO9UiR-TVg.jpeg</url>
            <title>Stories by Silvia Hourigan on Medium</title>
            <link>https://medium.com/@silvszak?source=rss-5f1b06d734eb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:36:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@silvszak/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 maintaining a growth mindset looks like in practice]]></title>
            <link>https://medium.com/@silvszak/what-maintaining-a-growth-mindset-looks-like-in-practice-eb6f3270f0df?source=rss-5f1b06d734eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb6f3270f0df</guid>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <dc:creator><![CDATA[Silvia Hourigan]]></dc:creator>
            <pubDate>Wed, 08 Apr 2026 10:05:59 GMT</pubDate>
            <atom:updated>2026-04-08T10:05:59.782Z</atom:updated>
            <content:encoded><![CDATA[<p>You often hear a growth mindset being summarized as “being open to change” or “staying flexible.” While those qualities are important, they only scratch the surface of what a growth mindset really means.</p><p>At its core, a growth mindset is about perception: how you interpret moments, conversations, challenges, and opportunities as they unfold around you. It’s about learning to see possibilities in places where you might not have thought to look before.</p><p>Many opportunities don’t announce themselves clearly. They don’t arrive neatly packaged with instructions or certainty. Instead, they show up quietly: in a colleague mentioning a new tool they’ve started using, in a conversation about a problem that doesn’t yet have an owner, or in feedback that nudges at an assumption you’ve long held about your own skills. Too often, these moments are brushed aside, dismissed as irrelevant, meant for someone else, or outside the scope of who we believe ourselves to be.</p><p>A growth mindset asks us to pause in those moments and ask a different question: <em>What if this is for me?</em></p><h3>Missed opportunities are often invisible</h3><p>One of the biggest challenges with maintaining a growth mindset is that missed opportunities rarely feel like missed opportunities at the time. They feel like noise. Someone shares a new platform, framework, or approach, and we tell ourselves it doesn’t apply to our role. A gap appears in a process, and we assume it’s someone else’s responsibility to solve. A discussion surfaces a challenge, and we think, <em>I’m not the expert here.</em></p><p>But that limits our opportunities for growth immensley. Growth comes from curiosity, from being willing to explore something <em>before</em> you feel fully ready.</p><p>People with a growth mindset recognize that opportunities aren’t reserved for those who already have everything figured out. They’re for those willing to engage, experiment, and learn in real time.</p><h3>Redefining who can provide the solution</h3><p>Another subtle barrier to growth is the story we tell ourselves about our capabilities. Many of us <em>assume</em> that if we’ve been doing something for a long time, our skills in that area are <em>complete</em>. We stop questioning our approach. We stop seeking new perspectives. We assume refinement is no longer necessary.</p><p>A growth mindset challenges that assumption.</p><p>It allows space for the idea that even well-developed skills can be sharpened further, and that learning from others, especially those with different experiences or viewpoints, can push us beyond our perceived limits. Sometimes growth doesn’t mean acquiring something entirely new; it means revisiting what we already know with fresh eyes.</p><p>When we believe that only certain people are capable of solving certain problems, we unintentionally limit ourselves. A growth mindset invites us to consider that we <em>might</em> be able to contribute and explore the path to being able to do so.</p><h3>Learning happens in motion</h3><p>Growth doesn’t always look like formal education, certifications, or clearly defined milestones. More often, it happens in motion, while trying something new, making mistakes, and adjusting along the way.</p><p>Maintaining a growth mindset means reframing discomfort. Instead of seeing uncertainty as a signal to step back, it becomes a signal to lean in. Instead of viewing mistakes as proof of inadequacy, they become data points for improvement.</p><p>This mindset doesn’t ignore fear or self-doubt; it simply doesn’t allow them to make the final decision.</p><h3>Choosing growth, repeatedly</h3><p>A growth mindset is a practice. It’s choosing, again and again, to remain curious. To listen more closely. To question assumptions about what’s “for you” and what isn’t. To recognize that opportunities often arrive disguised as ordinary moments.</p><p>The people who grow are the ones who notice, who engage, and who are willing to see themselves as evolving, even when it would be easier not to.</p><p>Growth begins the moment you stop assuming you’ve already arrived.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dd4XEvRTvzKxjxB2" /><figcaption>Photo by <a href="https://unsplash.com/@deliberatedirections?utm_source=medium&amp;utm_medium=referral">Deliberate Directions</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb6f3270f0df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Silos to Collaboration: My First 30 Days as a Writer on a Design Team]]></title>
            <link>https://medium.com/emplifi-design/from-silos-to-collaboration-my-first-30-days-as-a-writer-on-a-design-team-4699b98417d5?source=rss-5f1b06d734eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4699b98417d5</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[technical-writing]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Silvia Hourigan]]></dc:creator>
            <pubDate>Mon, 05 Jan 2026 11:34:57 GMT</pubDate>
            <atom:updated>2026-01-06T15:12:29.178Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HbCjt40mrf8O5Z0s" /><figcaption>Photo by <a href="https://unsplash.com/@nickmorrison?utm_source=medium&amp;utm_medium=referral">Nick Morrison</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Leaving Legacy Tech Writing Behind</h3><p>In my experience, the position of a tech writer is one that sits as an afterthought of the product release workflow. The writer is informed of changes coming to the product and updates the documentation accordingly. Whether you realize it or not, that workflow limits not only the documentation, but the product itself.</p><p>Technical writers have a lot to offer, yet we are too often an untapped resource for UI optimization. We share a comprehensive perspective on the product with teams that are often siloed and provide the customer’s point of view in complicated (and sometimes chaotic) product experiences.</p><p>Yet that hasn’t always been the reality of my career journey. So, it was a truly pleasant surprise to realize just how integrated the writers are when I started as a tech and UI writer on Emplifi’s design team. Around here, there is a different way of doing things. Being part of a forward-thinking, design-led team has pushed me to dive deeper into UI principles and fundamentally change my perspective on what a writer’s process can be.</p><h3>Breaking the Last-Minute Cycle</h3><p>The traditional tech writing workflow I’ve experienced goes something like this:</p><ol><li>Product design changes are created and implemented.</li><li>A release is announced a few days or weeks out.</li><li>Tech writers are informed during the “last wave” of information.</li><li>The scramble begins: writers rush to figure out the documentation impact and implement changes within a tight deadline.</li></ol><p>While documentation still gets updated, an accelerated timeframe doesn’t allow for content quality assurance or optimization. Synchronization with the product becomes impossible; as a result, the doc center functions as a standalone afterthought.</p><p>In contrast, an integrated system brings writers into the conversation at step one, shifting our purpose from simple writing to content strategy. Instead of scrambling, there’s time to optimize. We are given the space to take a bird’s-eye view and ensure information is presented in the best possible way.</p><p>Incorrect information, gaps, and structural inaccuracies are weeded out when writers are involved from the get-go. While some might ask, “Why should I care about documentation?” the answer is simple: <strong>this is about customer experience</strong>.</p><p>By the time a user reaches the documentation center, their experience is already “tainted.” They aren’t there for a fun read; they’re there because they’re stuck. If they are then met with inaccurate or confusing content, it could be the final straw. A broken link or a vague instruction in the docs isn’t just a typo — i<strong>t’s a failure of the safety net we promised the user when they signed up.</strong></p><h3>The Feedback Loop: Where Writing Meets Strategy</h3><p>When a writer is embedded within a design team, the benefits flow both ways. It isn’t just about the writer getting a “head start” on documentation updates; it’s about the writer being an indicator for UI complexity. It’s about creating a feedback loop that strengthens the product before it ever reaches the user.</p><h4>If it’s hard to document, it’s hard to use</h4><p>In the legacy siloed model, the writer is often the first person to realize a workflow is unnecessarily complex. However, by the time they realize it, the feature is already built. By sitting with the design team, I‘m enabled to speak up during the prototyping phase. If I’m struggling to find a logical way to explain a feature in the documentation, it’s usually a signal that the UI itself needs more clarity. This opens doors to having discussions about simplifying the design, rather than trying to explain a “clunky” experience later.</p><h4>Aligning the mental model</h4><p>Designers and developers often use internal jargon to describe new features. If those terms make it into the UI and then into the docs, the user is forced to learn a new language just to use the product. Being involved from day one allows me to help align the mental model of the user with the vision of the designer. We can ensure that the labels in the interface match the titles in the documentation center, creating a seamless narrative across the entire platform.</p><h4>Reducing the cost of knowledge</h4><p>Every time a user has to leave the product to search the documentation center, they are taken out of their workflow and forced to enter another. By collaborating with designers, we can identify which information is critical enough to live inside the UI (via tooltips or microcopy) and what belongs in a long-form article. This partnership ensures the documentation center isn’t a graveyard for things the UI failed to explain, but a library for deeper learning.</p><h3>Looking Ahead</h3><p>My first 30 days at Emplifi have been a masterclass in integration. It has been a shift in understanding what it means to be part of the product, rather than the afterthought.</p><p>I’ve come to realize that when we stop treating documentation as the last step and start treating it as a foundational design layer, the benefits are limitless. From UI optimization to reduced ad hoc code fixes and better information architecture — everyone wins. But <strong>most importantly, the customer wins.</strong></p><p>As I move into my next 30 days, I’m excited to leave the scramble behind. I’m not just writing about the product anymore; I’m helping design a better way to experience it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4699b98417d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/emplifi-design/from-silos-to-collaboration-my-first-30-days-as-a-writer-on-a-design-team-4699b98417d5">From Silos to Collaboration: My First 30 Days as a Writer on a Design Team</a> was originally published in <a href="https://medium.com/emplifi-design">Emplifi Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>