<?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 Hunter Nielsen on Medium]]></title>
        <description><![CDATA[Stories by Hunter Nielsen on Medium]]></description>
        <link>https://medium.com/@hunternielsen.ca?source=rss-e38f804ef694------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nE-gPRlvWlDJNR54mOp1Qw.jpeg</url>
            <title>Stories by Hunter Nielsen on Medium</title>
            <link>https://medium.com/@hunternielsen.ca?source=rss-e38f804ef694------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:13:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hunternielsen.ca/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[Hacking Innovation]]></title>
            <link>https://medium.com/guidewireux/hacking-innovation-bbd34fcdaa2e?source=rss-e38f804ef694------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbd34fcdaa2e</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[insurance]]></category>
            <dc:creator><![CDATA[Hunter Nielsen]]></dc:creator>
            <pubDate>Fri, 20 Aug 2021 19:00:40 GMT</pubDate>
            <atom:updated>2021-08-20T19:00:40.250Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*li-ea7iKv6KsSnAO_huQdA.jpeg" /></figure><p>Hackathons are all about bringing together a diverse group of people who are passionate about innovation and want to push the boundaries of design and development. Guidewire recently invited 85 participants from 12 countries to take part in its first-ever virtual hackathon. It was a great opportunity to put Jutro, our design system and UI framework, through its paces and to see the creativity of Guidewire partners on display.</p><p>A total of 17 teams took part in the event. Participants included front and backend developers, UX designers, and SMEs. Internal Jutro experts provided guidance and coaching, sharing their knowledge, expertise, and experience.</p><p>The focus of this hackathon was on generating solutions in the area of claims submission and intake. At the beginning of the hackathon, teams were given a series of real business challenges to jumpstart their builds and promote creativity. They included a mix of ideas ranging from building components to enriching and extending claim details screens to development of a full-blown microapp. In all instances, participants were able to reference Figma for storyboards, components, and other resources.</p><p>Because the majority of participants were new to Jutro, we also constructed a hackathon microsite to onboard UX designers and developers. Creating a central place for support tools facilitated knowledge discovery and skill development. The hackathon microsite hosted our design system documentation, which provides guidelines and best practices for working with Jutro components and patterns. In addition, participants could use the site to enroll in learning missions that introduce the basics of designing and developing with Jutro. These self-paced exercises covered a variety of topics, such as how to customize the look and feel of Jutro applications and tips for working with metadata.</p><p>One of the primary goals of this hackathon was to inspire other teams to take a design-minded approach to problem solving and solution finding. While it’s frequently engineers who participate in hackathons, UX designers play an integral role in helping to articulate the user’s perspective and tell a story that is clear, concise, and compelling. Before the actual building starts, for instance, it’s important to ask questions like:</p><ul><li>What are we trying to solve for?</li><li>Who is our target persona? What are their needs, goals, and motivations?</li><li>What will our users and stakeholders consider to be a successful outcome?</li></ul><p>UX professionals drive these types of conversations and enable their teams to quickly identify, prioritize, and scope features and products. Hackathons typically unfold over a period of less than a week, and that means you’re going to have to make some tough decisions about where to invest your energy. Interdisciplinary collaboration is key to balancing your vision with what can realistically be achieved in the allotted time.</p><h3><strong>And the winners are …</strong></h3><p>Judging criteria at this year’s hackathon was based in part on how well teams leveraged UX principles and best practices. Competition was fierce, but the winning teams distinguished themselves by incorporating narrative into their designs and making users the hero of their own experience. Check out the top four projects below:</p><p><strong>Team LOGOS (aka EY EMEA)</strong></p><p>Claimed the 1st place prize by not only telling a very dramatic story but also integrating the standard European accident reporting form, autocompleting a significant part of the claim, and leveraging Guidewire Jutro and AI to create a compelling mobile experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VsrHbveDY6cvc99Y-ydQHg.png" /><figcaption>Users can upload a completed accident statement, which will then populate details for loss location, impacted vehicles, and vehicle damages using Google Vision AI. ©Guidewire Software</figcaption></figure><p><strong>Fincons Italy (aka Fincons SPA)</strong></p><p>2nd place for simplifying the e2e claims process through automation and creating their own theme, which all resulted in a very fluid user experience. They also integrated their company car damage photo recognition system with Jutro as a business component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xWu5v-yVF158gEDqjdO-sQ.png" /><figcaption>Fincons Italy used straight-through digital processing to simplify claims submission and payments. ©Guidewire Software</figcaption></figure><p><strong>Tech Titans (aka PWC America)</strong></p><p>2nd place for their roadside assistance experience combined with damage detection to file a claim. They wrapped their Jutro app using Capacitor to make it a native iOS and Android application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LNSY2kMLmAGuxEWF3T8HzA.png" /><figcaption>Tech Titans’ app, UnStranded, gives customers the ability to submit service requests in seconds using AI-based damage analysis and real-time tracking. ©Guidewire Software</figcaption></figure><p><strong>Digi Tribe (aka Cognizant)</strong></p><p>3rd place for developing a micro app with new intelligent options for completing claims adjustments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tEbsviC0pdIPVYz6KFIC7A.png" /><figcaption>Digi Tribe created a simplified page view for managing activity notifications. Their Activity Manager app comes with pre-defined contextual filters and a search function. ©Guidewire Software</figcaption></figure><h3><strong>What’s next?</strong></h3><p>Guidewire UX has been hard at work synthesizing findings to improve and build upon future hackathons. These will contribute to improvements in the Jutro Design System and enable us to address gaps in Jutro designer and developer journeys.</p><p>Winning hackathon teams are invited to present at Guidewire’s annual conference, Connections, in November. In the meantime, tune in next month for a discussion on how Guidewire is transforming knowledge discovery for Jutro.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbd34fcdaa2e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/guidewireux/hacking-innovation-bbd34fcdaa2e">Hacking Innovation</a> was originally published in <a href="https://medium.com/guidewireux">Guidewire Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writing for Design Systems]]></title>
            <link>https://medium.com/guidewireux/writing-for-design-systems-b157b8f1706e?source=rss-e38f804ef694------2</link>
            <guid isPermaLink="false">https://medium.com/p/b157b8f1706e</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Hunter Nielsen]]></dc:creator>
            <pubDate>Fri, 04 Dec 2020 18:13:01 GMT</pubDate>
            <atom:updated>2020-12-04T18:13:01.076Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cZX5UESN9eSvSmHN_OLJYA.jpeg" /></figure><p>Over the past several months, Guidewire UX has worked in concert with a number of stakeholders across the organization to craft the design documentation for Jutro, our design system and front-end framework. It’s been a highly collaborative effort that’s benefited from the contributions of user experience designers, writers, product managers, researchers, and accessibility specialists, just to name a few. As we celebrate the first public release of Jutro this month, I wanted to reflect on the process that we went through, the decisions and compromises that we had to make along the way, and the future direction of Jutro design documentation.</p><p>Design system documentation is critical to driving effective design decisions, promoting consistency across solutions, and enabling rapid development. If your organization is beginning the process of documenting its design system, you need to understand the different audiences that your documentation serves, what content they need, and how you are going to structure pages to convey this information. Our team found it helpful to create a template — it doesn’t need to be anything fancy; a Word doc will suffice — that captures content requirements and the order in which you will treat them.</p><p>It’s also important to have a framework in place to facilitate collaboration. Design systems appeal to an interdisciplinary audience — designers, developers, researchers and content strategists, among others — and things can get messy fast if you don’t plan in advance. Consider what types of deliverables you will need and who will be contributing them. Will you need to draw on the talents of a visual designer for supporting graphics? We certainly did. Make sure you factor such considerations into your workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lm1LGERGA9XZYFq3ueTRtg.png" /></figure><p>There are a number of tools that you can use to expedite these processes and ensure that everyone is on the same page at all times. Before putting pen to paper, we first created a design matrix on Confluence that enabled us to track where each spec was in terms of completion. Kanban boards can also be an invaluable tool for visualizing and managing workflows. This is essential when you have multiple people writing content or signing off on content. In our case, two UX designers would typically compose the initial draft of the documentation. They would then hand the spec off for review to the UX manager and product manager who were overseeing the entire process. As the UX writer on the team, I provided content heuristics and best practices on writing for components and patterns. I also served as the final editor and reviewer. Lastly, our accessibility specialist documented the status of each UI element with regards to accessibility. The approach you adopt will likely vary based on the size of your organization, time constraints, budgeted resources, and a variety of other factors. What’s important is that you establish a rhythm early on and identify the tools and procedures that work for you and your team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ER7WJzaYf4McfQT5oCOhnA.png" /></figure><p>You may find yourself having to make some tradeoffs as you navigate this journey, including difficult decisions about audience prioritization. In an ideal world, design system documentation should appeal to a wide audience that includes both developers and designers. Each of these groups will come to a design system with different requirements and expectations. Developers may be looking for detailed documentation on code usage and implementation. Designers, on the other hand, will need guidance on when to use a component, best practices for working with UI elements, and guidelines that address visuals, interaction, and content. For the time being, we provide a link within each spec that directs users to the relevant page in <a href="https://storybook.js.org/">Storybook</a>. Once there, developers can pull the metadata they need to add to their code. The ultimate goal is to embed a Storybook tab within each component spec so that users don’t have to go to a separate site for things like code and API docs. In addition to reducing friction, this will have the added benefit of ensuring that taxonomies do not diverge. It’s up to each organization how they want to blend design and code. Choose the solution that works for you but be cognizant of the risks/rewards and how these may impact your design system long-term.</p><p>Design systems are constantly evolving and are never really “finished.” They change as a company’s customers, markets, demographics, solutions and services shift and change. Jutro is more than just a UI kit or a pattern library. It represents all of the different ways that Guidewire communicates and interacts with its users. Design system documentation plays an integral role in that conversation, articulating Guidewire’s design philosophy and point of view on content creation. We’re proud that Jutro has reached a level of maturity where we can release it to our customers, and we continue to plan for the future. The team is focused on building out our business pattern library to account for common use cases within the P&amp;C space. Moreover, we want to capitalize on the content and writing guidance that we offer for common interaction components by providing reusable and repeatable content patterns. These will help our designers to work faster and with more confidence, and users will benefit from greater consistency and clarity in our copy. This list of initiatives is by no means exhaustive and I’m sure we will continue to add to it as new opportunities present themselves.</p><p>Creating a design system from scratch is a major undertaking. It requires buy-in and contributions from many stakeholders and a commitment to maintaining and evolving that system. It’s not a sustainable model to have one person responsible for the entire project. Diverse perspectives are essential to producing a living, breathing design system that is successful in the long-term. Guidewire has a core team that is working on Jutro. We meet regularly to discuss where the design system is headed and plot future updates. Overtime, I could see this team model expanding to include contributions from others within the organization, including subject matter experts. It’s been a rewarding experience watching our own design system take shape, and I encourage others who are interested in this type of work to volunteer their talents. Design system teams thrive on interdisciplinary collaboration. The one thing that we all have in common: intellectual curiosity and a willingness to learn.</p><p><strong>Interested in working for a dynamic company that is revolutionizing the cloud space for P&amp;C insurers? Check out our </strong><a href="https://careers.guidewire.com/"><strong>open positions</strong></a><strong> and follow Guidewire UX on Medium.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b157b8f1706e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/guidewireux/writing-for-design-systems-b157b8f1706e">Writing for Design Systems</a> was originally published in <a href="https://medium.com/guidewireux">Guidewire Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflections on UX writing at Guidewire Software]]></title>
            <link>https://medium.com/@hunternielsen.ca/reflections-on-ux-writing-at-guidewire-software-e48227f2c729?source=rss-e38f804ef694------2</link>
            <guid isPermaLink="false">https://medium.com/p/e48227f2c729</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[guidewire-ux]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Hunter Nielsen]]></dc:creator>
            <pubDate>Fri, 28 Aug 2020 19:01:26 GMT</pubDate>
            <atom:updated>2021-04-12T13:23:43.068Z</atom:updated>
            <content:encoded><![CDATA[<h3>Reflections on UX Writing at Guidewire Software</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_wv9oW9fkiEo_YySAjuwjQ.jpeg" /></figure><p>Being the sole UX writer at a company, and a relative newcomer to the field of UX, comes with its own unique set of challenges and rewards. I joined Guidewire in the spring of 2020 as part of a broader initiative to expand the user experience team and promote design thinking and doing principles throughout the organization. Prior to making this transition, I served as an educator and studied classical philology, which focuses on the translation and interpretation of Latin and Ancient Greek literature.</p><p>With user experience writing still in its formative stages at Guidewire, one way to scale is to democratize the UI writing process, and to equip other members of the team with tools to evaluate copy. Heuristics are critical in this regard, as they provide a series of best practices against which designers can measure their content. Clarity and concision, for instance, are among the key attributes that we look for in effective and usable user experiences. To <a href="https://uxwritinghub.com/learn-ux-writing-with-roxana-ux-writing-manager-at-dropbox/">quote</a> Roxanna Aliaga, the head of UX writing at Dropbox, “every word in a poem has to earn its place, just like the words in UI.” The goal is to provide users with the right content at the right time. No more, no less. Simplicity is also important. Simple language that is grounded in users’ own vocabulary and avoids unnecessary jargon and tech-speak is consistently proven to be the most effective.</p><blockquote><em>User experience writing, at least in name, is a relatively new discipline. User experience writers focus specifically on the content that lives within applications. They partner with a variety of stakeholders to develop a voice, tone and style that informs the production of all UX/UI text.</em></blockquote><p>The collaborative nature of user experience writing is its greatest strength. Honing this strength is important in software development, as the responsibility of writing for application copy is shared by a few different teams. It’s incumbent upon us as dedicated writers to ensure that we are using the same vocabulary across applications, and our application documentation. During my time at Guidewire, I’ve teamed with numerous people from across the organization to tackle design challenges. This includes a recent study on provisioning terminology. I conducted interviews with approximately ten internal users, including cloud operations system administrators. This provided a foundational vocabulary to go forward, and yielded valuable insights as far as how users understood the provisioning process. Working in concert with UX researchers and designers, I then constructed a survey that was intended for both internal and external personas. The goal of the survey was to validate proposed terminology in the UI and obtain alternatives wherever applicable. Survey participants were asked to define terms in their own words, respond to hypothetical scenarios using low-fi mockups, and match definitions with the appropriate term. The results of the study confirmed the importance of tapping into users’ existing mental models and drawing on their own vocabulary wherever possible to inform content creation.</p><p>Partnering with technical writers has also been a priority from the outset. This has involved educating members of the documentation team on the responsibilities of UX writers, how we differ from technical writers, and the ways in which we can contribute to each other’s efforts. Their product expertise, knowledge of documentation management systems and terminology, for example, has been invaluable as we iterate on design guidelines for Guidewire’s UI components. At the same time, by including a UX writer in the process, we ensure that our design guidelines, which are intended first and foremost for designers, do in fact have a design sensibility at their core. This includes addressing more granular detail, like the pros and cons of using sentence case versus title case in our UX/UI text.</p><p>User experience writing is the latest addition to our journey to become a design driven development organization, and we have a lot of exciting projects in the pipeline. This includes inclusivity guidelines for UX/UI text, to ensure that we are writing for <strong><em>all users</em></strong> and not just a few. As we advocate for a friendly and conversational tone in our writing, we need to be sensitive to how our choice of words can marginalize and exclude people. Embracing gender-neutral pronouns, for instance, can go a long way towards creating an experience that is welcoming to the LGBTQ community. UXW is also collaborating with a number of stakeholders across the organization, including marketing and services professionals, on our content style guide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqNNJvieCaItH-5nSWbM2g.jpeg" /></figure><p>Reflecting on my first year at Guidewire, I confess that I was initially concerned that my background would not translate well into a design setting. Thankfully, it’s proven to be quite the opposite! I encourage people who are considering a move into user experience to leverage their existing talents and skillsets. UX is an interdisciplinary field that thrives on diversity. In my case, I come from a background in history, education, and linguistics, all of which have proven instrumental in the work that I do. User experience writing relies on the power of storytelling to communicate user needs, goals and motivations. As a historian in my previous life, I spent many days thinking on the past, trying to construct a coherent narrative to explain human passions and emotions. In addition, user experience writers spend much of their time using content to scaffold the user experience and explain difficult concepts in plain language. Teaching isn’t all that dissimilar. The most effective instructors empathize with their students and use that empathy to create content and experiences that truly resonate. As user experience writing evolves, I’m hopeful that we as a design community will continue to bring a myriad of perspectives to bear on content creation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e48227f2c729" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>