<?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[STG UX Dailies - Medium]]></title>
        <description><![CDATA[The daily reflections of an experience design consultancy team. We’re collecting our thoughts and insights as we engage with all sorts of teams and projects. - Medium]]></description>
        <link>https://medium.com/stg-ux-dailies?source=rss----9b10a3981838---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>STG UX Dailies - Medium</title>
            <link>https://medium.com/stg-ux-dailies?source=rss----9b10a3981838---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:36:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/stg-ux-dailies" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Pre-story Story Points?]]></title>
            <link>https://medium.com/stg-ux-dailies/pre-story-story-points-9c32b8301673?source=rss----9b10a3981838---4</link>
            <guid isPermaLink="false">https://medium.com/p/9c32b8301673</guid>
            <category><![CDATA[software-estimation]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Tommy Bay]]></dc:creator>
            <pubDate>Fri, 07 Dec 2018 00:08:23 GMT</pubDate>
            <atom:updated>2018-12-07T00:08:23.675Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bxu5WjdSE9-IDMrqOealwQ.jpeg" /></figure><p>Today was a first for me — we used Fibonacci story points to estimate… <strong><em>not</em></strong> stories. Yup, the company wants estimates <em>pre</em>-stories.</p><p>It felt like I used up 30 minutes of the estimation meeting trying to wrap my head around the value that was supposed to come from putting stories points against a project that hadn’t been discussed, researched, or designed. In honesty, I still don’t get it… but we were able to come up with a [really] rough estimate. The exercise wasn’t terrible; our team learned some things through the discussion.</p><p>I think it points to the company’s interest in understanding what it’s committing to before committing to it. But it’d be nice to know that it was providing solid value to somebody.</p><p>There are all these ideas bouncing around my brain lately about user story mapping, and experience mapping, and OKRs, and Jobs to be Done, and defining/measuring success, and... I’m hoping that sometime soon my brain will stop churning and pour out something smooth and delicious that will help me better prioritize my efforts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c32b8301673" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stg-ux-dailies/pre-story-story-points-9c32b8301673">Pre-story Story Points?</a> was originally published in <a href="https://medium.com/stg-ux-dailies">STG UX Dailies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What do you mean by “process flow”?]]></title>
            <link>https://medium.com/stg-ux-dailies/what-do-you-mean-by-process-flow-f5519d5a6acd?source=rss----9b10a3981838---4</link>
            <guid isPermaLink="false">https://medium.com/p/f5519d5a6acd</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[process]]></category>
            <dc:creator><![CDATA[Tommy Bay]]></dc:creator>
            <pubDate>Tue, 04 Dec 2018 00:10:59 GMT</pubDate>
            <atom:updated>2018-12-04T00:10:59.040Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ndNxHOlxe-J7-dhMWZPDqw@2x.jpeg" /></figure><p>I had a good learning opportunity today.</p><p>We went into a two-hour meeting with some of the claims department leadership. The meeting had been titled, “Whiteboarding process flow for Claims”, but it became clear that we weren’t all on the same page for what that meant. Consequently, we spent the first 45 minutes starting and stopping — trying to figure out what we were trying to figure out.</p><p>Eventually, we got some traction and made some helpful flows and, by the end, I had learned a lot more about the users involved, what their journey looks like, and what the needed solution should do. The biggest takeaway, however, was to set better expectations for meetings (especially when working with new people) and to come to those meetings better prepared.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5519d5a6acd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stg-ux-dailies/what-do-you-mean-by-process-flow-f5519d5a6acd">What do you mean by “process flow”?</a> was originally published in <a href="https://medium.com/stg-ux-dailies">STG UX Dailies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing… testing…]]></title>
            <link>https://medium.com/stg-ux-dailies/testing-testing-5cdd3915cf74?source=rss----9b10a3981838---4</link>
            <guid isPermaLink="false">https://medium.com/p/5cdd3915cf74</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[typography]]></category>
            <category><![CDATA[usability-testing]]></category>
            <dc:creator><![CDATA[Tommy Bay]]></dc:creator>
            <pubDate>Wed, 21 Nov 2018 00:17:25 GMT</pubDate>
            <atom:updated>2018-11-21T00:17:24.783Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jj9v7-xpBOpi5vrDO5r6dg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/5JhHiSAEiz0?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Gritte</a></figcaption></figure><p>We started the day with an awesome usability test for one of new products! It’s so encouraging to see the organizational support for listening to, and observing our users. In this case, we were talking to internal users. There was a solid list of takeaways logged, both for IA and UI. Afterward, our team was able to discuss improvements we’ll make in the future to the usability testing process. We’ll test with some external users next week.</p><p>I did a typography audit today across three of our web apps. Our text usage is scattered, but not the worst I’ve ever seen. Still… it’s interesting how common it is to design an interface without thinking about the larger system it belongs to. Most don’t love to spend their day in documentation, but from past experience, it’s SO NICE to stop spending time making decisions about typography and colors and instead focus on solving real problems.</p><p>I’m putting together a typography proposal that I’ll run past the other designers next week along with the refined color palette from yesterday.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5cdd3915cf74" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stg-ux-dailies/testing-testing-5cdd3915cf74">Testing… testing…</a> was originally published in <a href="https://medium.com/stg-ux-dailies">STG UX Dailies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We gon’ find you]]></title>
            <link>https://medium.com/stg-ux-dailies/we-gon-find-you-bf555d078a9b?source=rss----9b10a3981838---4</link>
            <guid isPermaLink="false">https://medium.com/p/bf555d078a9b</guid>
            <category><![CDATA[antoine-dodson]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[ux-process]]></category>
            <category><![CDATA[user-advocate]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Tommy Bay]]></dc:creator>
            <pubDate>Fri, 16 Nov 2018 05:57:25 GMT</pubDate>
            <atom:updated>2018-11-16T05:57:25.186Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MgpmBcbMoonWvNyYWLOSMA.jpeg" /><figcaption>Antoine Dodson</figcaption></figure><p>Lots of meetings today. It was really great… but I’m glad it’s not every day.</p><p>This morning, UX + Dev met about process. There was a good discussion and I think we all feel pretty good about where we landed. Once we get QA’s input and buy-in, we’ll get it documented. It’ll be a six-step process:</p><h3><strong>Discover | Explore | Design | Build | Test | Deploy</strong></h3><p>In two separate meetings, we heard some very impassioned feedback from a user / facilitator of one of our Insurance Claims systems. It was great to hear her perspective and pain points! I think the “advocating for users” part of UX definitely includes letting users vent; get frustrations off their chest. A couple of our guys did a fair amount of that between meetings today. Hopefully we can find some appropriate, meaningful ways to help improve her life.</p><p>It definitely makes me wonder how many other people throughout (and outside) the company are struggling with systems and solutions that are sub par and make their day-to-day frustrating. We’ll have to find them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*CVqbrFjoaiJqOXs2hZbAIQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf555d078a9b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stg-ux-dailies/we-gon-find-you-bf555d078a9b">We gon’ find you</a> was originally published in <a href="https://medium.com/stg-ux-dailies">STG UX Dailies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our principles will guide us]]></title>
            <link>https://medium.com/stg-ux-dailies/our-principles-will-guide-us-bf226009b0a8?source=rss----9b10a3981838---4</link>
            <guid isPermaLink="false">https://medium.com/p/bf226009b0a8</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-decision]]></category>
            <category><![CDATA[principles]]></category>
            <category><![CDATA[style-guides]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Tommy Bay]]></dc:creator>
            <pubDate>Thu, 15 Nov 2018 00:31:16 GMT</pubDate>
            <atom:updated>2018-11-15T00:31:15.881Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iEiv_51x1Q7txTzQKnWK4g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/iDzKdNI7Qgc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jordan Madrid</a></figcaption></figure><p>Last night, I spent a few hours with ten UX Designer colleagues of mine. One of them gave 15 minutes of a presentation he’s building for developers about the principles of web design (it’s awesome, btw). We had an excellent discussion after he was done about copying others’ work vs following rules vs applying principles. It was a really good reminder to me that the goal in any endeavor is best served by understanding the underlying principles.</p><p>Today, I’ve been trying to think about the principles guiding our design system; <strong><em>why</em></strong> we are choosing to adopt certain rules and guidelines. I’m sure there are style guides and pattern libraries out there that do a good job of articulating those core motivators or brand truths… but I’m guessing they’re absent more often than not. It’s something to aspire to as we continue to build out our standards, components, and processes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf226009b0a8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stg-ux-dailies/our-principles-will-guide-us-bf226009b0a8">Our principles will guide us</a> was originally published in <a href="https://medium.com/stg-ux-dailies">STG UX Dailies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s play “What does this icon mean to you?”]]></title>
            <link>https://medium.com/stg-ux-dailies/lets-play-what-does-this-icon-mean-to-you-9a223802e3df?source=rss----9b10a3981838---4</link>
            <guid isPermaLink="false">https://medium.com/p/9a223802e3df</guid>
            <category><![CDATA[icons]]></category>
            <dc:creator><![CDATA[Jac "Jake" Madsen]]></dc:creator>
            <pubDate>Tue, 13 Nov 2018 01:50:57 GMT</pubDate>
            <atom:updated>2018-11-13T01:50:56.857Z</atom:updated>
            <content:encoded><![CDATA[<p>UX Dailies</p><p>I don’t get to build icons as much as I’d like. Our current design system didn’t have an icon that represented what I needed. I guess I’ll need to make one.</p><p><em>*Designer rubs hands together while giggling gleefully</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yh9QdjzWRK_84T7gKuZPLQ.png" /></figure><p>So tell me, what might this icon represent?</p><p>This icon was built in Figma. Not the first tool that comes to mind for building icons, but serviceable and limiting in all of the right ways. It was also really helpful to have an existing library to refer to for style. I’ve found that most of the work in building a library is learning the rules. That tends to come after I’ve built a few icons. The language starts to dial in. I find myself reworking the early icons to fit the new visual dialect. It takes a lot of time and effort to refine. Extending a set is tricky, but having similar objects in shape and concept really accelerates the process. And golly, it sure is fun.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a223802e3df" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stg-ux-dailies/lets-play-what-does-this-icon-mean-to-you-9a223802e3df">Let’s play “What does this icon mean to you?”</a> was originally published in <a href="https://medium.com/stg-ux-dailies">STG UX Dailies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Back in the saddle]]></title>
            <link>https://medium.com/stg-ux-dailies/back-in-the-saddle-2c33c829124c?source=rss----9b10a3981838---4</link>
            <guid isPermaLink="false">https://medium.com/p/2c33c829124c</guid>
            <category><![CDATA[style-guides]]></category>
            <category><![CDATA[pattern-library]]></category>
            <category><![CDATA[practice]]></category>
            <category><![CDATA[transparency]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Tommy Bay]]></dc:creator>
            <pubDate>Tue, 13 Nov 2018 00:31:38 GMT</pubDate>
            <atom:updated>2018-11-13T00:31:37.756Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jmh0Tnkf9thM3HZKIkO3Jg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/qwbA2RcohIU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Roxanne Desgagnés</a></figcaption></figure><p>The end of last week was spent at the <a href="https://www.frontutah.com/workshops/">Front Workshops</a> in West Jordan. It’s always nice to get out and do different things; especially when you’re learning and practicing new skills. But it was good to be back in the saddle today reengaging problems and trying to apply new knowledge.</p><p>I spent some time digging into my client’s marketing department style guide. It was helpful to see how they outlined logo and color usage… but it definitely raised questions and concerns— surfaced some inconsistencies. The marketing team is super cool and easy to work with. I’m not really interested in changing or fixing their style guide. I just want to be transparent with everyone if we adopt some different standards in our own Pattern Library.</p><p>We realized today that we need to include profile info in our interfaces (and the ability to log out). We talked through our options and picked a direction to move. It will actually help unify some formerly disparate apps (💪).</p><p>One of our Practice Practice presenters had kids get sick, so we spent the morning figuring out how to best replace him tomorrow night. <a href="https://medium.com/@davidhstoker">Dave Stoker</a> and I have quite a list of things we’d love to spend time practicing or learning, so it wasn’t hard filling the time. Tomorrow, we’ll go over design critiques, STG goals for 2019, and a whiteboarding framework to try out. I love it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c33c829124c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stg-ux-dailies/back-in-the-saddle-2c33c829124c">Back in the saddle</a> was originally published in <a href="https://medium.com/stg-ux-dailies">STG UX Dailies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eerie button talk]]></title>
            <link>https://medium.com/stg-ux-dailies/eerie-button-talk-68c54a7d900f?source=rss----9b10a3981838---4</link>
            <guid isPermaLink="false">https://medium.com/p/68c54a7d900f</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[button]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Tommy Bay]]></dc:creator>
            <pubDate>Thu, 08 Nov 2018 00:18:24 GMT</pubDate>
            <atom:updated>2018-11-13T00:08:58.773Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*bhaJe5yhOpSLjMocQd01vA.jpeg" /></figure><p>We’re in a fun stage right now. I feel like everyone is asking good questions and we’re making decisions that will help us become faster, more efficient, and more consistent. I just hope we’re getting it all documented so we can stick to it!</p><p>We had an eerie moment this morning when I asked another designer a bunch of questions on Slack about our buttons, and literally two minutes later, a developer walked over and asked the <strong>exact same questions</strong>. It was fantastic (albeit random) timing and we were able to quickly get aligned.</p><p>We met with marketing about the company website and were able to agree on a rough plan and timeline for the redesign. That team is awesome and came prepared with a lot of helpful information like page visit analytics and heat map printouts.</p><p>One of our designers (that is new to UX) is going to head up the UX effort for the website and I’m really excited for him to take it through our process. We talked about starting with empathy and then filling the holes around what we know vs don’t know. He’s going to do great.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68c54a7d900f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stg-ux-dailies/eerie-button-talk-68c54a7d900f">Eerie button talk</a> was originally published in <a href="https://medium.com/stg-ux-dailies">STG UX Dailies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thanks, California]]></title>
            <link>https://medium.com/stg-ux-dailies/thanks-california-a7e1effb5984?source=rss----9b10a3981838---4</link>
            <guid isPermaLink="false">https://medium.com/p/a7e1effb5984</guid>
            <category><![CDATA[california]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[understanding]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[style-guides]]></category>
            <dc:creator><![CDATA[Tommy Bay]]></dc:creator>
            <pubDate>Wed, 07 Nov 2018 00:07:33 GMT</pubDate>
            <atom:updated>2018-11-07T00:07:33.205Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*roHelfxDCBoQfVCIJrIB8Q.png" /></figure><p>We started working on a new style guide today. It’s amazing how clarifying that kind of effort can be. We made a short list of items to start with (colors, typography, buttons, text fields, etc). Already, we’ve found several great things to investigate before we can nail them down. The primary red we’re using in our designs (#ba160a) doesn’t match the one being used in production (#ba3f33), but is way prettier. Also, our element spacing and sizing doesn’t follow any kind of unit grid or convention. Plenty of fun stuff to dig in to!</p><p>I talked with one of our lawyers today about the giant legal “disclaimer” or explanation that lives in our website footer. He was super nice and helped me go through the actual requirements. Turns out, we have to have it on our site because of a California law (go figure). Anyway, I think we’ll be able to remove it from the footer and find some other strategic places to show it (yay).</p><p>It’s a good reminder that we should always ask; seek to understand why things are the way they are. We could have just left the text in the footer — nobody asked us to remove it. But everyone from the lawyer to the developers to the designers to the users are happy at the prospect of it being diminished.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7e1effb5984" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stg-ux-dailies/thanks-california-a7e1effb5984">Thanks, California</a> was originally published in <a href="https://medium.com/stg-ux-dailies">STG UX Dailies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New challenges]]></title>
            <link>https://medium.com/stg-ux-dailies/new-challenges-e5e95a33d4eb?source=rss----9b10a3981838---4</link>
            <guid isPermaLink="false">https://medium.com/p/e5e95a33d4eb</guid>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[windows]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Tommy Bay]]></dc:creator>
            <pubDate>Tue, 06 Nov 2018 00:13:29 GMT</pubDate>
            <atom:updated>2018-11-06T00:13:28.822Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s3s1WlqmkzSzTd_wlt5tqg.jpeg" /></figure><p>A local insurance company decided to take the UX plunge. They’ve started building a user experience team and I’m on board to help get things moving!</p><p>One of the great benefits of being a UX consultant, imho, is frequently shifting to new environments, new industries, new problems to solve. Another benefit (hopefully) is that most people expect a UX consultant to come in asking a lot of questions. I like asking questions.</p><p>Right now, our little three-man team of UX designers are outlining the product process we want to follow. Defining a process is a bit of a process — every team is different; they have different personalities, roles, responsibilities, etc.</p><p>We’re putting something together that we think will work for <em>this</em> team. Then we’ll show it to the developers and stakeholders, get their input, and nail it all down. We want this to help us all align our expectations going forward.</p><p>They did throw me a curve ball by handing me a Windows laptop on my first day. I feel like I’m brushing my teeth with the wrong hand. My wife says it’s good for me. She’s usually right.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5e95a33d4eb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stg-ux-dailies/new-challenges-e5e95a33d4eb">New challenges</a> was originally published in <a href="https://medium.com/stg-ux-dailies">STG UX Dailies</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>