<?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[Paychex UX - Medium]]></title>
        <description><![CDATA[Dive into the world of user experience at Paychex, where our talented designers and researchers craft intuitive, impactful solutions to power the next generation of Human Capital Management. Discover the creativity, strategy, and passion that powers UX at Paychex. - Medium]]></description>
        <link>https://medium.com/paychex-ux?source=rss----b5f024a70dc0---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Paychex UX - Medium</title>
            <link>https://medium.com/paychex-ux?source=rss----b5f024a70dc0---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:04:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/paychex-ux" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Frameworks We Forgot]]></title>
            <link>https://medium.com/paychex-ux/the-frameworks-we-forgot-46db4a261c9e?source=rss----b5f024a70dc0---4</link>
            <guid isPermaLink="false">https://medium.com/p/46db4a261c9e</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Jon Daiello]]></dc:creator>
            <pubDate>Fri, 01 May 2026 17:05:14 GMT</pubDate>
            <atom:updated>2026-05-01T17:05:13.713Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we keep repackaging what already works…making it worse.</h4><p>I got into the industry around 2008. Worked at a small agency for four years, then freelanced for another four. I was making things and shipping work. And at the time, I thought I was doing fine. But looking back, I was floating. Roaming from project to project, hoping to stumble into the right answers without any real framework to stand on. And nobody around me pointed it out.</p><figure><img alt="hand drawn compass with ? instead of NWSE indicators. “Which way?”" src="https://cdn-images-1.medium.com/max/1024/0*mj3-UjKFki2FuLCN.jpeg" /><figcaption>Trying to design without a solid foundation is like aimlessly wandering.</figcaption></figure><p>That changed around 2015. I landed a job where people actually talked about this stuff. Nielsen’s 10 heuristics. Peter Morville’s honeycomb. Jesse James Garrett’s five layers of UX. Information architecture. Interaction design. At first, it was overwhelming, like they were all speaking a foreign language. But, I spent the next four years soaking it up, learning to apply these ideas day in and day out.</p><p>Over time, it felt like I built a map. It didn’t give me all the answers, but it gave me direction. Clarity on how to approach challenges instead of aimlessly wandering through them. For the first time in my career, I felt like I’d found a shared language…a common foundation the whole industry used. It felt like I was flying.</p><p>Then I changed jobs. And the shared language wasn’t shared.</p><h3>The Blank Stares</h3><p>In my new role, I repeatedly referenced these frameworks in conversations with my new team. Morville’s honeycomb for defining value. Garrett’s layers for diagnosing where a problem actually lives (this one a lot). Most of the time, I just got blank stares. The only framework anyone seemed to know was a watered-down version of design thinking. The map I’d been using to guide me was unknown around me. Worse yet, when that map is missing, we’re left arguing over relativistic opinions.</p><p>At first, I was confused, wondering why no one else shared these frameworks. I wondered why we were still discussing opinion, when there were clear principles to be designed from. At the time, I ignored it and just focused on embedding these frameworks in the culture of the work.</p><h3>The Tipping Point</h3><p>A few years later, my thinking really got going after I picked up <a href="https://amzn.to/4sKPXAb">a book on design education</a>, filled with research from the past 50+ years. The work was excellent. Thoughtful, grounded, backed by real study (instead of one person’s isolated experience). These researchers understood how design functions, how people learn it, and what makes designers effective. And almost nobody in the industry today has heard of any of it.</p><p>That’s when it clicked. This wasn’t just my experience at one company. This is a pattern. The design industry keeps doing this. We find solid, time-tested, research-backed frameworks. We use them for a while. Then we move on. Not because they stopped working. Because they stopped being new.</p><figure><img alt="hand drawn trash can full of garbage: “Abandoned frameworks”" src="https://cdn-images-1.medium.com/max/1024/0*-UocxIRBDL__xpCB.jpeg" /><figcaption>We’re too eager to throw existing frameworks in the trash for something new.</figcaption></figure><h3>The Pattern</h3><p>These proven frameworks keep getting abandoned across this industry. And the replacements aren’t better. They’re just newer.</p><p>Take Jakob Nielsen’s 10 usability heuristics. In the last two years alone, multiple articles have proposed “new” heuristics for AI, condensed the originals into three “core principles,” or declared them insufficient for modern interfaces. But those heuristics weren’t pulled from thin air. They were derived from a factor analysis of 249 usability problems across 11 professional projects. They haven’t needed changing since 1994 because human cognition hasn’t changed since 1994. The shape of software has changed, but the people using it haven’t.</p><p>Or look at Nigel Cross. He spent decades doing rigorous research on how designers actually think and work. Then IDEO took the general concept, simplified it into a five-step process, and branded it “design thinking.” Today, most designers couldn’t tell you where design thinking actually came from. The lineage is gone, in favor of innovation theater.</p><p>And then there’s my personal favorite. Every single year, someone publishes “10 UX Principles for [next year].” Typically, these are fad-based tidbits that are less proven than Bigfoot.</p><h3>How It Happens</h3><p>So how does an industry keep losing its own foundations? I think there are at least four forces at work, and they all lead to the same place.</p><ol><li><strong>Personalization</strong>. A framework doesn’t perfectly fit your context, so you start adapting it. You rename a step here, tweak a category there, adjust the language to match your team’s vocabulary. Each change feels small and reasonable. But after enough tweaks, the original is unrecognizable both in name and in value. The shared language disappears one customization at a time, and the value of the framework is eroded.</li><li><strong>Universalization</strong>. A framework doesn’t cover every possible situation, so you try to build one that does. One model to account for every context, every application, every edge case. It’s an impossible goal. And the pursuit of a universal framework quietly replaces the proven ones that were broadly working.</li><li><strong>Unnecessary Reinvention</strong>. Maybe it’s maker instinct. Maybe you want ownership. Maybe you genuinely believe your situation is unique enough to warrant a new approach. Whatever the reason, the original gets replaced rather than understood and applied. Another framework enters the world, watering down the trust in design rationale.</li><li><strong>Inexperience</strong> (probably the most common). Many never learned the originals in the first place. That bootcamp taught you Figma and user flows but skipped the discipline that makes the tools useful. You can’t abandon something you never knew existed. And when you eventually encounter a gap in your toolkit, your instinct is to build something new, because you don’t realize something already fills that gap.</li></ol><h3>What We Actually Lost</h3><p>These battle-tested frameworks aren’t just tools or methods. They give us a common vocabulary for talking about design. They are a shared set of criteria for evaluating whether something was working or not. When you and I both know Morville’s honeycomb, we can have a grounded conversation about whether a product is findable but not credible. When we both know Garrett’s layers, we can diagnose whether a problem is structural or visual. We’re not arguing opinions and feelings. We’re reasoning through shared criteria.</p><figure><img alt="two hand drawn chat bubbles “this violates the law of proximity” vs “i think blue is dumb”" src="https://cdn-images-1.medium.com/max/1024/0*SzSCH0eRaatAdKLA.jpeg" /><figcaption>Grounding conversations in proven principles avoids preference talks.</figcaption></figure><p>Without that shared ground, design conversations collapse into exactly <a href="https://medium.com/design-systems-collective/why-engineers-can-say-this-is-wrong-and-designers-cant-e6492aded0b3">what Kevin Muldoon described</a>:</p><blockquote><em>“The field has made expertise indistinguishable from preference.”</em></blockquote><p>When there’s no agreed-upon standard to point to, invoking color theory gets the same shrug as saying “I don’t like the blue.” The designer who cites Gestalt principles gets treated the same as the one stating a personal preference. The cost isn’t just inefficiency. It’s that we’ve lost the ability to agree on what “good” even means.</p><h3>The Grounding Already Exists</h3><p>I’m not going to pretend I’m above this pattern. A few years ago, I started building my own framework for design. Not for UX specifically, but for design as a discipline. I had real reasons. I saw real gaps. I still use it in my own work to help me make sense of the design world. It’s a helpful map for me.</p><figure><img alt="hand drawn map showing four areas: elements of UX, laws of UX, Orville honeycomb, 10 usability heuristics" src="https://cdn-images-1.medium.com/max/1024/0*LcgaEieQ4I61P4Bt.jpeg" /><figcaption>Established frameworks are useful and applicable because humans are still the same.</figcaption></figure><p>But I don’t put it on anyone else. And I don’t sell it for money. Because the honest truth is we don’t need another framework right now. We need to actually use the ones we’ve got. It’s hard to let the dream of creating the next big framework die. But nobody seemed to get it anyway. Or care about it. And maybe that’s the point. Maybe the industry doesn’t need my map. It needs to pick up the maps that are already drawn.</p><p>The shared ground already exists. It’s just waiting to be remembered.</p><ul><li>Nielsen’s heuristics give you a research-backed standard for evaluating usability.</li><li>Garrett’s five layers help you diagnose where a UX problem actually lives, not just at the surface, but deep into strategy and structure.</li><li>Need grounded language for why a layout feels off? That’s Gestalt principles (or PARC).</li><li>Trying to define what makes something valuable to users? Morville’s honeycomb.</li><li>Yablonski’s Laws of UX connect your design decisions to proven psychological research that’s been validated for decades.</li></ul><p>These aren’t relics from a bygone era. They’re shared vocabulary that’s been sitting on the shelf, collecting dust while we keep reinventing the same ideas with new names. They may need to be applied in new ways as software evolves, but they’re still relevant and valuable.</p><p>So before you build something new, ask yourself a simple question. Does something already exist that does this job? You might be surprised how often the answer is yes. The most useful move you can make might not be invention. It might be adoption. The grounding is already there…you just have to look for it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46db4a261c9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paychex-ux/the-frameworks-we-forgot-46db4a261c9e">The Frameworks We Forgot</a> was originally published in <a href="https://medium.com/paychex-ux">Paychex UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Delivery is a trap]]></title>
            <link>https://medium.com/paychex-ux/delivery-is-a-trap-2e4cd0354c1b?source=rss----b5f024a70dc0---4</link>
            <guid isPermaLink="false">https://medium.com/p/2e4cd0354c1b</guid>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Erik Sagen]]></dc:creator>
            <pubDate>Thu, 29 Jan 2026 18:30:44 GMT</pubDate>
            <atom:updated>2026-03-19T02:28:35.012Z</atom:updated>
            <content:encoded><![CDATA[<h3>Delivery is a Trap</h3><h4>How UX slid from strategy to service</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RLYTOYmGk_U4Nag9YBRckg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jannesjacobs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jannes Jacobs</a> on <a href="https://unsplash.com/photos/low-angle-photography-of-rock-formation-VEH_xb3IIqQ?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>We’re making drawings.</strong></h3><p>That thought hit me a few years ago. Credit to a former manager who made it obvious. We were stringing together polished screens into nice-looking workflows, testing them with a handful of people meant to represent everyone, and calling that validation. Somewhere along the way, the drawing became the work. Not the thinking behind it. Not the problem it was meant to solve. The artifact itself.</p><p>But the drawings weren’t the thing. They were pictures of the thing. And the people we tested with weren’t always users. They were proxies, doing their best to react to something that didn’t exist yet.</p><p>The whole ritual assumes that testing a picture is the same as testing reality. That a subset of people in a lab or in a remote usability session can predict how the larger population will receive your work.</p><p>But what if there’s a better way?</p><p>What if you built quickly and learned from real feedback instead? Not skipping research, but shifting where the learning happens. Less time perfecting drawings. More time with rough, real things in front of actual people doing actual work.</p><p>The polished deliverable isn’t just unnecessary. It might be the thing slowing us down from learning what actually matters.</p><p>So how did we end up here?</p><h3>How we got here</h3><p>I don’t know exactly when things shifted. There wasn’t a memo. But somewhere along the way, design went from thinking to making. From shaping what gets built to producing assets after someone else already decided where the winds would blow.</p><p>And here’s the truth: We were complicit.</p><p>The polished end-to-end vision felt like progress. It looked good in the deck. Marketing could use it. Sales could reference it. Leadership could point to something tangible and say “this is where we’re going.”</p><p>That shininess came with a cost. The more complete the vision looked, the harder it became to change. Iteration became inconvenient. The drawing became the destination instead of a waypoint. And we got comfortable there, because a beautiful artifact is easier to defend than a rough idea that might not work.</p><h3>The seat isn’t the goal</h3><p>For years, I would hear through murmurings that the industry talked about getting a seat at the proverbial table, in the room where it happens (to quote Hamilton). And we got it, sort of. Designers are in the room now. But the seat comes with limitations. You’re there to represent “the user.” To raise concerns. To make sure things look right and feel usable. Important work, but bounded work.</p><p>The seat was never the real goal anyway. Influence was. The ability to shape direction, not just react to it. To be part of the early conversations where the actual decisions happen: what we build, why we build it, what we’re willing to bet on.</p><p>But influence doesn’t come from a meeting invite. It comes from trust. And trust comes from being right about things that matter, often enough, that people start asking what you think before they’ve already decided.</p><h3>Show up differently</h3><p>So how do you build trust when you’ve been boxed into delivery?</p><p>You can’t ask for it. You can’t petition your way back to influence. Nobody grants strategic relevance because you made a compelling case in a meeting.</p><p>You have to show up differently.</p><p>That means arriving early with something rough instead of late with something polished. A sketch. A prototype. A question framed as something people can react to. Not “here’s the answer” but “here’s a possibility, does this hold?”</p><p>The polished deliverable closes conversations. It says “I’ve thought this through, now approve it.” The rough experiment opens them. It invites people to think with you instead of evaluating you.</p><p>It also means being willing to be wrong faster than the system is comfortable with. Most organizations are built to minimize risk. They want confidence before commitment. The whole apparatus of reviews and approvals and sign-offs exists to make sure nobody ships something embarrassing.</p><p>But confidence before commitment is expensive. You’re paying in time, in process, in drawings that might not matter. And you’re learning slowly, from proxies, from pictures, from guesses about what real people might do.</p><p>What if you paid less up front and learned faster on the back end? Built something rough, put it in front of real users, watched what actually happened, and then iterated based on reality instead of predictions?</p><h3>Trust takes time</h3><p>Here’s the thing about influence: you earn it through action, not words.</p><p>When a team starts inviting you into conversations, that’s a good first step. You’re there. They want you there. But the seat is just the beginning.</p><p>What comes next is harder. Everyone has to loosen their grip. And it’s not even about control, really. It’s about letting people experiment. Build POCs. Try and fail and try again. It’s about creating the conditions where learning is more valuable than being right.</p><p>That takes time. This isn’t an overnight change. Trust builds slowly, through small moments where you show up differently and deliver something useful. Where you’re wrong and recover well. Where you help the team see something they couldn’t see before.</p><p>It also takes leadership willing to take the risk. Leaders who value the relationship-building, not just the end result. Who can see the throughline between messy experimentation now and better outcomes later. Who understand that trust isn’t a distraction from the work, it’s what makes the work possible.</p><p>There’s no shortcut. Just the work, repeated, until people start asking what you think before they’ve already decided.</p><p>And when they do? You’re not making drawings anymore. You’re making decisions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e4cd0354c1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paychex-ux/delivery-is-a-trap-2e4cd0354c1b">Delivery is a trap</a> was originally published in <a href="https://medium.com/paychex-ux">Paychex UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mentoring Is Not What You Think]]></title>
            <link>https://medium.com/paychex-ux/mentoring-is-not-what-you-think-07747e7db21c?source=rss----b5f024a70dc0---4</link>
            <guid isPermaLink="false">https://medium.com/p/07747e7db21c</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[mentorship]]></category>
            <dc:creator><![CDATA[Nate Schloesser]]></dc:creator>
            <pubDate>Tue, 09 Dec 2025 18:12:20 GMT</pubDate>
            <atom:updated>2025-12-09T18:12:19.230Z</atom:updated>
            <content:encoded><![CDATA[<h4>It is simpler, more human, and far more essential than we realize</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tq_kBR45kC57pKXdVYtQyQ.png" /><figcaption>Illustration of two people walking side-by-side</figcaption></figure><p>Most organizations have job descriptions, performance reviews, goal trackers, quarterly plans, and detailed workflows. Yet many do not have a clear path for developing people. They assume growth happens naturally. They assume learning will simply occur. They assume potential will rise to the surface on its own.</p><p>Then everyone is surprised when it does not.</p><p>Early in my career I watched this play out again and again. A talented employee would be promoted and handed a team with little guidance. They were not shadowing anyone. They were not coached. They were not mentored. They were simply given more responsibility and expected to figure it out. When they struggled, the organization quietly decided they were not leadership material.</p><p>No one asked the more important question: <em>Who showed them how to lead in the first place?</em></p><p>This is the mentoring gap. It exists in almost every industry, and it slowly drains the potential of people who could have thrived if someone had simply taken the time to walk with them.</p><p>Mentoring is often talked about as a luxury. Something extra. Something that happens if there is time. It is seen as a program instead of a relationship. A calendar event instead of a conversation. A transfer of expertise instead of a partnership in growth.</p><p>In reality, mentoring is none of those things. And our wrong assumptions about it are the reason so few people ever step into it.</p><p>This article is about clearing away the confusion. When we understand what mentoring is not, what mentoring is, and why it matters for everyone, we discover something simple and freeing. You do not need to be perfect to mentor someone. You only need to be present.</p><h3>The Misconceptions That Hold People Back</h3><p>The biggest barrier to mentoring has nothing to do with time, talent, or titles. The barrier is the belief that mentoring is for experts. People imagine a mentor as a seasoned veteran with decades of wisdom, flawless decision making, and answers to every question. Since no one actually feels like that person, mentoring becomes something only the mythical elite qualify for.</p><p>I have heard variations of this for years:</p><ul><li>“I am not senior enough.”</li><li>“I do not know enough yet.”</li><li>“I am still figuring things out.”</li><li>“I am not a natural teacher.”</li><li>“I do not feel like a mentor.”</li></ul><p>These doubts are remarkably consistent. They mirror the same fears that keep people from developing others in any context, whether spiritual, relational, or professional.</p><p>Here is the truth that cuts through all of it: <em>If something has helped you grow, you have something to share.</em></p><p>You do not need to be extraordinary. You do not need to have every answer. If you have learned anything at all, you can offer that insight to someone who is a few steps behind you.</p><p>Mentoring is not mastery. It is generosity.</p><h3>The Cost of Not Mentoring</h3><p>We often underestimate the quiet consequences of a workplace without mentoring. It can feel fine on the surface. Projects get completed. Meetings happen. Work continues. But beneath the familiar routine is a slower erosion.</p><p>When people are not guided, they improvise. When they improvise, they guess. When they guess, they repeat the same mistakes over and over, and eventually those mistakes shape the culture.</p><p>Here is what a mentoring gap creates in an organization:</p><ul><li><strong>Unclear expectations.</strong> New employees try to perform tasks without knowing what success looks like.</li><li><strong>Underdeveloped talent.</strong> High potential workers plateau because no one is helping them grow in the right direction.</li><li><strong>Burned out managers.</strong> Leaders pull double duty, doing their own job and the job of those who were never taught how to do theirs.</li><li><strong>Disjointed culture.</strong> Every team member interprets values differently, which produces friction that no one can name.</li><li><strong>Increased turnover.</strong> People do not leave companies because of compensation first. They leave because they feel unseen and unsupported.</li></ul><p>None of these problems are solved through policy changes. They are solved through presence. They are solved when someone says, “Let me walk with you a bit. Let me show you what has helped me. Let me help you take the next step.”</p><p>Mentoring is not expensive. The absence of mentoring is.</p><h3>So What Is Mentoring Really?</h3><p>Once we remove the myths, mentoring becomes surprisingly simple.</p><p>Here are the four things that mentoring actually requires.</p><h3>1. See the Person</h3><p>People want to be known. They want their strengths noticed. They want their goals heard. They want to feel like more than a title or task list.</p><p>A mentor starts by seeing the person behind the role.<br>What motivates them?<br>What slows them down?<br>What do they hope for in their career?<br>What are they afraid of?</p><p>You cannot develop what you do not notice.</p><h3>2. Clarify the Purpose</h3><p>Most employees work hard but do not fully understand the purpose behind their growth. They have vague ambitions. They have loose ideas. They might even have large dreams but no defined path.</p><p>A mentor asks:<br>Where are you trying to go?<br>What does progress look like for you?<br>Why does this matter to you?</p><p>Purpose ties their story to their development. Without it, mentoring becomes a series of disconnected conversations. With it, mentoring becomes a journey.</p><h3>3. Walk the Path Together</h3><p>This is where mentoring becomes practical. Not theoretical. Not philosophical. Not inspirational. Just real.</p><p>Walking the path means showing up regularly. It means helping people practice new skills, reflect on their decisions, and explore opportunities. It means offering guidance without taking control and offering perspective without taking responsibility away from them.</p><p>It is steady. It is relational. It is a rhythm, not an event.</p><h3>4. Create Opportunities to Practice</h3><p>Growth does not stick until it is practiced. Mentoring is not only about conversations. It is about giving someone the space to try.</p><p>A mentor might invite a younger designer to sit in on client calls.<br>A mentor might let a new engineer lead a sprint review.<br>A mentor might help an intern run a small part of a larger project.</p><p>Practice builds confidence. Confidence builds ownership. Ownership builds leaders.</p><h3>The Surprising Truth: Anyone Can Mentor</h3><p>One of the greatest misunderstandings about mentoring is the idea that it must be formal. Many believe it requires a program, a sign up process, and a monthly calendar slot with carefully crafted agendas.</p><p>Those things can help, but they are not the heart of mentoring. Mentoring is most powerful when it is organic. It often begins with a simple question.</p><ul><li>“How are you doing with this project?”</li><li>“Do you want feedback on that idea?”</li><li>“Would it help to talk through what you are learning?”</li></ul><p>You do not have to be in management to mentor someone. You do not have to be in leadership. Mentoring is not a title. It is a posture.</p><p>It is the choice to invest in another person’s growth. Anyone can do that.</p><h3>Why Mentoring Builds Stronger Teams</h3><p>Teams with active mentors function differently. They share knowledge. They solve problems faster. They avoid repeating mistakes. They feel connected rather than isolated. They move as a unit rather than as individuals.</p><p>When mentoring becomes normal inside a workplace, several things happen:</p><ul><li>People ask for help sooner because asking no longer feels embarrassing.</li><li>New leaders emerge because they have been prepared instead of thrown into the deep end.</li><li>Conflict decreases because communication improves.</li><li>Retention increases because individuals feel valued.</li><li>Innovation rises because people feel safe to experiment and learn.</li></ul><p>Mentoring strengthens both the human and the organizational side of work. It builds skills, but it also builds trust. And trust is the currency of any healthy team.</p><h3>A Simple Way to Begin</h3><p>If mentoring still feels unclear or intimidating, here is a simple practice that brings everything into focus. It requires nothing more than a notebook. Digital or physical does not matter. What matters is that you create a place where you think intentionally about the person you want to invest in.</p><p>I use a three word framework that keeps me grounded and purposeful.</p><p><strong>Person: </strong>Who they are.<br><strong>Purpose: </strong>Why you are mentoring them.<br><strong>Plan: </strong>What you will actually do.</p><p>These three words turn good intentions into meaningful action. Here is how I use them.</p><h3>Person</h3><p>Write down their name and role. This keeps the work centered on a real human being rather than a vague idea of developing “talent.” Before you think about skills or performance, start by asking simple questions about the person.</p><ul><li>Who are they?</li><li>What strengths do they show consistently?</li><li>What motivates them?</li><li>What challenges are they facing?</li></ul><p>It sounds small, but naming the person anchors your mindset. Mentoring is relational. It begins with seeing someone clearly.</p><h3>Purpose</h3><p>After you name the person, identify the purpose. Why are you mentoring them? What specific area are they growing in, or what potential do you see in them that could be developed?</p><p>Purpose might look like this:</p><ul><li>Grow in confidence during presentations.</li><li>Develop project ownership skills.</li><li>Improve communication across teams.</li><li>Explore leadership potential.</li></ul><p>A clear purpose gives direction. It prevents mentoring from drifting into pleasant conversations that never translate into growth. Purpose ensures that both of you know what you are aiming toward.</p><h3>Plan</h3><p>Finally, write out a simple plan. This is the step that turns mentoring into something real. What will you actually do to help them grow?</p><ul><li>Will you meet regularly?</li><li>Will you recommend a book?</li><li>Will you read a book together?</li><li>Will you pull them into meetings so they can observe?</li><li>Will you find them stretch opportunities?</li></ul><p>The plan does not need to be complicated. It only needs to be actionable. One clear step is better than ten vague ones.</p><p>When you combine these three elements, you create a small but powerful framework. Person. Purpose. Plan. It takes mentoring out of the realm of intention and places it firmly into practice.</p><p>I recommend this to anyone who wants to mentor but does not know how to begin. It creates clarity. It builds confidence. And it gives your mentoring direction that grows over time.</p><p>It all starts with three simple words in a notebook.</p><h3>A Closing Thought</h3><p>Every organization has people with potential. Some realize it. Many do not. The difference is often one thing. Someone took the time to walk with them. Someone made their growth a priority. Someone believed their development was worth investing in.</p><p>The modern workplace talks constantly about leadership, culture, and talent. We spend millions on strategy and almost nothing on mentorship. Yet mentoring is the thing that shapes people in a way no workflow or process ever will.</p><p>If you have learned anything that has helped you grow, you already have what you need to mentor someone.</p><p>Do not wait until you feel qualified. Do not wait until you feel like an expert. The future leaders in your workplace cannot afford to wait for your perfection.</p><p>They need your presence.</p><p>And you are more ready than you think.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07747e7db21c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paychex-ux/mentoring-is-not-what-you-think-07747e7db21c">Mentoring Is Not What You Think</a> was originally published in <a href="https://medium.com/paychex-ux">Paychex UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shaping AI Experiences: A Practical Guide for UX Practitioners Who Want to Design the System, Not…]]></title>
            <link>https://medium.com/paychex-ux/shaping-ai-experiences-a-practical-guide-for-ux-practitioners-who-want-to-design-the-system-not-97d769f109ea?source=rss----b5f024a70dc0---4</link>
            <guid isPermaLink="false">https://medium.com/p/97d769f109ea</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Adrienne Baker]]></dc:creator>
            <pubDate>Fri, 07 Nov 2025 19:35:01 GMT</pubDate>
            <atom:updated>2026-02-11T01:16:47.964Z</atom:updated>
            <content:encoded><![CDATA[<h3>Shaping AI Experiences: A Practical Guide for UX Practitioners Who Want to Design the System, Not Just the Interface</h3><p>The landscape of design is undergoing a fundamental shift.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zk_uzjN0_7FaHIAK" /><figcaption>Photo by <a href="https://unsplash.com/@sortino?utm_source=medium&amp;utm_medium=referral">Joshua Sortino</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Suff Syed, researcher at Microsoft, recently wrote <a href="https://www.suffsyed.com/futurememo/designers-have-to-move-from-the-surface-to-the-substrate">a piece</a> about how designers should engage with the foundational logic, data, and infrastructure that drive intelligent systems — rather than just the “surface” (visuals, UI, and interactions).</p><p>I’ve spent the past year and a half building Paycor Assistant, and as I dive into generative UI capabilities for my next project, Suff’s piece resonates deeply with what I’ve learned. I encourage everyone to go read <a href="https://www.suffsyed.com/futurememo/designers-have-to-move-from-the-surface-to-the-substrate">the piece</a>, then come back here to learn some practical ways you can be influential in the conversations that are happening, and even shape decision making, all without being a data scientist or engineer.</p><p>If while reading Suff’s piece you felt a sense of panic, or asked yourself, “How do I actually do this work?”, “What does it look like to shape the context window? or define a system message?”, then keep reading.</p><p>I’ll walk you through how we shaped the Paycor Assistant experience at both levels — designing the interface while also influencing the system logic beneath it.</p><h4>You’re Designing an AI Solution — Now What?</h4><p>Start by building relationships with the engineers, data scientists, and architects on your team. You don’t need to understand their work at the deep level they do, but some foundational knowledge is essential. Ask them to walk you through the infrastructure they’re building and how the different pieces connect. Keep asking questions until you can grasp the high-level architecture.</p><p>Supplement these conversations with your own research into the basics of LLMs, machine learning, natural language processing, and agentic systems. Understanding why these technologies are used and how they work together will help you speak the language of your engineering partners — just as knowing the basics of HTML, CSS, and JavaScript has always made you a more effective designer.</p><p>When designing AI experiences, you can’t create a mockup for every possible scenario — but that doesn’t mean you shouldn’t create anything. Whether you’re working with an existing library of AI interaction patterns or establishing new ones, your role is to help the team understand the vision for how users should experience AI in your product. This vision becomes especially critical given that AI output is non-deterministic and can’t be controlled the way traditional experiences can be.</p><p>As you work, constantly ask yourself: “How can I influence what the user gets from AI?”</p><p>Here are some practical ways you can do exactly that.</p><h4><strong>Shaping the System Message</strong></h4><p>The system message is a set of natural language instructions that tells an AI model how to act — and as a designer, you have more influence over this than you might think.</p><p>Start by identifying who on your team is responsible for building the model and writing the system message, then express your interest in collaborating on it. If a system message already exists, ask to review it and understand any constraints (like length limitations driven by cost considerations).</p><p>The real magic happens when you can test iteratively. Ask your engineer if there’s a playground where you can experiment with different system messages without touching code. This kind of environment lets you refine the message based on how closely the AI’s responses match your desired user experience. Document what you try and what works — you’ll want to reference which modifications had the biggest impact later.</p><p>When my team built <a href="https://www.paycor.com/hcm-software/paycor-assistant/">Paycor Assistant</a>, a conversational experience designed to give employees instant access to HR answers and company policies, we took a systematic approach to shaping the system message. We started by defining three potential personas for the Assistant, each with a distinct voice and tone based on our Marketing team’s brand personality guidelines. For each persona, we wrote example questions and answers to illustrate how it would feel to interact with that version of the Assistant.</p><p>Next, we ran unmoderated perception tests to understand which tone would feel most trustworthy to users. Based on those results, we crafted an initial system message. Then came the iterative part: using Azure Chat Playground, we tested the system message with prompts that real users might input, documented how responses changed with each revision, and refined until we got closer to our desired outcomes.</p><h4><strong>Evaluating Outputs</strong></h4><p>Your engineering partners are likely building a plan to test the output from AI. They will evaluate factors such as accuracy and relevance. You should evaluate the output as well through the user&#39;s lens.</p><p>Start by identifying who on your team is responsible for creating validation data sets, then share your interest in providing guidance on desired responses and test prompts. If the data set includes “ground truth” responses — examples of ideal outputs the model should learn from — this is your opportunity to write the desired AI responses in your own words. As the engineer or data scientist runs tests with this data, give feedback on the actual responses you see. This becomes an iterative process: you’ll repeat it across all validation data sets until the responses consistently match your desired outcomes.</p><p>For Paycor Assistant, contributing to validation data sets became one of our most impactful design activities. We started by writing example questions and answers, then designed screens that visualized the complete user flow with both questions and our desired responses. This helped the team see not just what the AI should say, but how it fit into the larger experience.</p><p>We then collaborated with data scientists to input these desired answers directly into the validation data set as “ground truth” examples. We also suggested prompts we knew would be commonly used based on our user research, along with edge cases that might trigger undesired responses — the kind of boundary testing that designers are naturally good at. As the model was tested, we provided ongoing feedback on the actual answers, commenting directly in the validation data set spreadsheet about accuracy, length, voice, and tone.</p><h4><strong>Understanding Context Windows</strong></h4><p>A model can only remember a certain amount of text at a given time. This limitation — called the context window — determines how much input it can process and how much data it can include in the output. It directly impacts what users experience, so understanding user needs in this area is critical.</p><p>Your role here is to ground the technical constraints in user research. What do users actually expect from AI in your specific use case? Consider factors like their tech literacy, the context of their task, and the communication channel they’re using. Think about what an ideal output would include for them: Do they want longer-form answers with explanations? Step-by-step guidance? Short, scannable responses? Links to navigate elsewhere? Design the experience based on these insights, then provide feedback on whether the responses you’re seeing match those needs.</p><p>For Paycor Assistant, usability testing revealed some clear patterns that shaped our approach to context windows. Employee users on mobile devices wanted short, concise answers — they were often multitasking or looking for quick information. They didn’t desire lengthy back-and-forth conversations for simple tasks like checking their PTO balance. Most questions were occasional inquiries that didn’t require the AI to remember previous conversation context. However, users sometimes wanted access to more detailed information if the short answer raised follow-up questions.</p><p>Based on these findings, we incorporated short answers with resource links to full documents into both the validation data set and our mockups. We shared these research findings bi-weekly with the project team to ensure everyone understood the “why” behind our design decisions around response length and context.</p><h4><strong>Retrieval-Augmented Generation (RAG)</strong></h4><p>Retrieval-Augmented Generation, or RAG, allows AI models to reference external knowledge bases, documents, or frequently updated resources to create more relevant and current responses. Which resources the model can access — and which ones take precedence when there’s conflicting information — significantly impacts what users experience.</p><p>It’s important that additional knowledge sources being connected are up-to-date, relevant, and accurate. As new knowledge sources are integrated, give feedback on the AI responses you see. If responses aren’t meeting user expectations, work with your team to understand how the model is weighing these knowledge sources—sometimes the balance needs adjusting.</p><p>For Paycor Assistant, we took an active role in defining which knowledge sources would be most valuable to users. We recommended that the Assistant run semantic searches across two key areas: navigation within the app itself (to guide users to the right section) and company policy documents (to answer specific HR questions with authoritative information).</p><p>We also worked closely with developers on the terminology used in these searches. It was crucial that the system recognized both formal terms and the casual language employees actually used — for example, ensuring that both “PTO” and “time off” would correctly direct users to the Time Off section of the app.</p><p>When answers could come from multiple sources, we provided clear guidance on ordering and precedence. For instance, we specified that navigation help should only appear when no direct answer existed in company policy documents. This prevented the AI from defaulting to “here’s where you can find that information” when it could simply answer the question directly.</p><h4><strong>Tool Orchestration</strong></h4><p>Tools allow AI systems to do more than just generate text — they enable the AI to make decisions, perform calculations, solve problems using multiple data sets, and take actions on behalf of users. Because tools enable non-deterministic outcomes (if the first approach doesn’t work, the AI can try a different path), they require careful consideration of the user experience across multiple possible flows.</p><p>To influence how tools shape the user experience, start by understanding the components of each tool: its definition, the parameters it accepts, the format of its output, the logic that connects it to other tools, and any constraints on when or how it can be used. Then work with your team to define what should happen for users when errors occur — because they will. Finally, establish clear guidelines for when the AI should take action versus when it should ask for permission first. These guidelines are crucial for building user trust and preventing the AI from doing something users didn’t intend.</p><h4><strong>Moving Forward</strong></h4><p>Designing for intelligent experiences requires a fundamental shift in how we think about our work. If we want to truly impact what the user gets from AI, making sure it’s usable, accessible, and responsible, we need to shape the underlying systems that power AI experiences.</p><p>Success in this new world means collaborating closely with engineers and data scientists, ensuring that they don’t lose sight of the end user’s experience. It means being comfortable with ambiguity and non-deterministic outcomes. And it means being willing to learn enough technical language to participate meaningfully in conversations that used to happen without us.</p><p>But the reality is, your success in this work depends heavily on the level of collaboration your engineering partners are willing to engage in. Company culture plays a role. Individual personalities do too. Some engineers will welcome your input on system messages and validation data; others may need more convincing that designers have valuable contributions to make at this level. This is why the relationship-building I mentioned at the start isn’t just a nice-to-have. It’s essential. The trust and rapport you build with your technical partners will determine how much influence you can actually have on the systems beneath the interface.</p><p>Start with curiosity. Ask questions. Offer to help. Show your engineering partners that you’re not trying to do their job, but that you’re trying to make their work more user-centered. Over time, as you demonstrate the value of user-centered thinking at the system level, you’ll find more opportunities to shape these intelligent experiences in meaningful ways.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97d769f109ea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paychex-ux/shaping-ai-experiences-a-practical-guide-for-ux-practitioners-who-want-to-design-the-system-not-97d769f109ea">Shaping AI Experiences: A Practical Guide for UX Practitioners Who Want to Design the System, Not…</a> was originally published in <a href="https://medium.com/paychex-ux">Paychex UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multiplayer AI]]></title>
            <link>https://medium.com/paychex-ux/multiplayer-ai-995a21b39101?source=rss----b5f024a70dc0---4</link>
            <guid isPermaLink="false">https://medium.com/p/995a21b39101</guid>
            <category><![CDATA[creative-intelligence]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Erik Sagen]]></dc:creator>
            <pubDate>Tue, 28 Oct 2025 16:57:23 GMT</pubDate>
            <atom:updated>2025-10-28T16:57:22.384Z</atom:updated>
            <content:encoded><![CDATA[<h4>From solo to shared thinking</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RB97EL8QdBX5U3tRXsRy6w@2x.jpeg" /><figcaption>Photo by <a href="http://gracemadephotography.com/">Hannah Busing</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When I was a kid, I sang in a school choir. I still remember how proud I felt standing on that stage, singing a simple song with my classmates. It wasn’t about being the loudest voice. It was about listening, finding the right moment to blend, to breathe, to rest and let others carry the melody.</p><p>That’s where harmony happens. You learn when to step forward and when to pull back. Everyone adds something, but no one owns the song.</p><p>Lately, I’ve been thinking about that again as AI starts moving from solo to multiplayer.</p><p>For a while, using AI has felt like a quiet duet. Just you and the model, trading ideas back and forth. But now tools like <a href="https://www.theverge.com/news/804122/microsoft-copilot-real-talk-mode-group-chats-features">Microsoft’s new Copilot Groups</a> are changing that. Soon, we’ll be working with AI together in shared spaces, in real time.</p><p>That’s exciting. But it also changes how we think.</p><h3>Beyond the machine</h3><p>Frank Chimero wrote something that stuck with me in his piece <a href="https://frankchimero.com/blog/2025/beyond-the-machine/?ref=sidebar">Beyond the Machine</a>:</p><blockquote>“You use a tool, but you play an instrument.”</blockquote><p>It reminds me that working with tools isn’t about control. It’s about feel, about showing up, paying attention, and keeping your humanity in the process.</p><p>AI fits that perfectly. It’s not here to automate your thoughts. It’s here to amplify them. The best sessions don’t feel like transactions; they feel like collaboration.</p><h3>From solo to ensemble</h3><p>So what happens when that solo performance becomes an ensemble?</p><p>When AI joins the group, we’re not just playing faster. We’re learning how to listen again. How to stay curious. How to keep space for tension and disagreement.</p><p>Because the risk isn’t that AI will make teams less creative. It’s that it might make them too agreeable.</p><p>Good collaboration needs friction. It needs a few rough edges. If we treat AI like just another voice in the room, we might start confusing alignment for insight.</p><h3>A simple framework for shared thinking</h3><p>When you bring AI into group work, it helps to have a few simple rules. Not to control the process, but to keep it intentional.</p><p>Think of it like cooking with too many chefs in the kitchen. Everyone’s adding ingredients, but if you’re not careful, the soup ends up muddy. Or like a choir, where one person singing too loud can throw off the harmony.</p><p>Here’s a simple framework for working with AI together:</p><p><strong>1. Assign roles</strong></p><p>Who’s leading the session? Who’s guiding the prompt? Who’s reflecting on the results? Don’t let everyone talk to AI at once.</p><p><strong>2. Set your intent</strong></p><p>Before you start, agree on what success looks like. Are you exploring, critiquing, or deciding? That shapes how you use AI.</p><p><strong>3. Keep the human check</strong></p><p>AI can suggest, reframe, and clarify, but it shouldn’t make the final call. Always close the loop with human reasoning.</p><p><strong>4. Reflect before acting</strong></p><p>Don’t rush to use what AI gives you. Ask, “Does this fit what we actually need?” or “What’s missing from this answer?”</p><p>When everyone knows their part, AI becomes a helpful instrument, not noise in the system.</p><h3>Keeping the thought partner</h3><p>The real value of AI isn’t in finishing work faster. It’s in sharpening how we think.</p><p>When it starts doing your thinking for you instead of with you, that’s your cue to slow down.</p><p>If you find yourself copying and pasting without reflection, take a breath and recalibrate. The best use of AI is when it makes your thinking clearer, not quieter.</p><p>AI can question your patterns, point out blind spots, and help you see the edges of your ideas — but it still needs you to lead the song.</p><h3>Collective intelligence</h3><p>We’re just starting to figure out how to build with this new partner in the room. But maybe the next step isn’t about making AI smarter. Maybe it’s about helping groups stay human as they use it.</p><p>Multiplayer AI isn’t about productivity. It’s about presence. It’s about listening, blending, and knowing when to let the group carry the next verse.</p><p>Better machines only matter if they help us become better together.</p><h3>A next chapter</h3><p>This piece builds on the idea from <a href="https://medium.com/paychex-ux/ai-as-a-thought-partner-not-a-shortcut-3859d5b486ed">AI as a Thought Partner, Not a Shortcut</a>. That one was about personal use; how to think with AI, not through it.</p><p>This one looks at what happens when that thinking becomes collective.</p><p>We’re not soloists anymore. We’re part of something bigger, and how we choose to listen will shape the overall sound we make together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=995a21b39101" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paychex-ux/multiplayer-ai-995a21b39101">Multiplayer AI</a> was originally published in <a href="https://medium.com/paychex-ux">Paychex UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why great products start as bad drawings]]></title>
            <link>https://medium.com/paychex-ux/why-great-products-start-as-bad-drawings-4fde6f137ce5?source=rss----b5f024a70dc0---4</link>
            <guid isPermaLink="false">https://medium.com/p/4fde6f137ce5</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[storyboarding]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-discovery]]></category>
            <dc:creator><![CDATA[Erik Sagen]]></dc:creator>
            <pubDate>Mon, 25 Aug 2025 13:31:31 GMT</pubDate>
            <atom:updated>2025-08-25T16:05:25.529Z</atom:updated>
            <content:encoded><![CDATA[<h2>Why Great Products Start as Bad Drawings</h2><h4>What Disney’s storyboarding process can teach product teams about doing the right work first</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nUKX-SbYGkxLMtsrMJf0wg@2x.jpeg" /><figcaption>Photo by Nasim Keshmiri on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>The views expressed here are that of the author and do not necessarily reflect those of Paychex.</blockquote><p>If Design needs room to think was about giving design the time and space it needs, this is about using that space well; especially from a product point of view.</p><p>Ever shipped something and thought, “We should’ve caught this earlier”? That feeling has a price. Slow down at the start and you spend less later.</p><h3>First, let’s rewind a bit</h3><p>In the 1930s, Walt Disney Studios developed storyboarding to pre-visualize an animated film before pouring money into production. Instead of scripts, they mapped the plot in drawings, pacing scenes, planning camera moves, and refining the story before a single frame was animated (<a href="https://disneyanaplus.com/vare-kategori/original-animation-art/storyboards/">see examples here</a>). Rough beginnings can lead to big things. Kevin Eastman’s napkin doodle of a turtle in a mask became Teenage Mutant Ninja Turtles.</p><p>Product teams face the same challenge, and the same opportunity to save time and money up front. Before sinking resources into a direction only to find out it’s wrong, you can explore the problem space. That might mean messy sketches, scribbled UIs, or object maps via OOUX. Think whiteboard covered in sloppy marker, not a shiny mockup. These aren’t filler steps; they’re quick, disposable tools that surface better options without burning budget.</p><p>Whether it’s OOUX, storyboarding, or another early discovery activity, starting at a lower fidelity lets you solve a lot before you commit. It still leaves room for surprises later; you’re just not forcing them to happen all at once.</p><p>Once there’s a direction worth pursuing, then you move into production. That’s when the design system and polished UI mockups shine, speeding up the work, keeping things consistent, and cutting cost.</p><p>The ideal? Being able to sketch an idea on a napkin and have the team see exactly how to bring it to life, and still have everyone ready to act.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fF4lLW4oMU-9lL0Nv4-Syg@2x.jpeg" /></figure><h3>Four reasons to start with messy sketches</h3><ul><li><strong>It’s cheaper to be wrong early.</strong> Fixing a napkin sketch costs nothing. Fixing a built feature costs everything.</li><li><strong>You see more options.</strong> Low fidelity keeps ideas loose, so you can explore instead of defend.</li><li><strong>It builds shared understanding.</strong> A messy drawing sparks conversation and alignment faster than a polished screen.</li><li><strong>It speeds up the “real” work.</strong> Once the thinking’s done, production flows; a strong design system turns decisions into screens fast.</li></ul><p>Bad drawings aren’t a sign of weak design. They’re a sign you’re making space for the thinking that leads to better products.</p><p><strong>Here’s the challenge:</strong> in your next planning session, skip the polished screens. Fill a wall with quick sketches. If you need a model, remember how Snow White was planned at Disney: rough boards that mapped the way. Track how many decisions you make in that hour and then compare it to an hour in Figma.</p><p>Once you’ve got the right idea, the next challenge is shaping and delivering it without losing what made it right. That’s where we’ll go next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fde6f137ce5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paychex-ux/why-great-products-start-as-bad-drawings-4fde6f137ce5">Why great products start as bad drawings</a> was originally published in <a href="https://medium.com/paychex-ux">Paychex UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design needs room to think]]></title>
            <link>https://medium.com/paychex-ux/design-needs-room-to-think-59ec15d739b5?source=rss----b5f024a70dc0---4</link>
            <guid isPermaLink="false">https://medium.com/p/59ec15d739b5</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Erik Sagen]]></dc:creator>
            <pubDate>Mon, 18 Aug 2025 12:41:37 GMT</pubDate>
            <atom:updated>2025-08-25T13:34:20.985Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why dual track models feel more natural and more human</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ro8qoja0DKdADFVJZg4YoQ@2x.jpeg" /><figcaption>Photo by <a href="https://www.karlsolano.com/">Karl Solano</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>The views expressed here are that of the author and do not necessarily reflect those of Paychex.</blockquote><h3>Before the build comes the blur</h3><p>Design work rarely begins with certainty. You usually start with fragments; a hunch, a user quote that stuck, a sketch that solves one part of the problem.</p><p>This is the blur or what I sometimes call the fuzzy, unknown part. And it’s where design usually begins.</p><p>But we often try to skip it. We cram design into sprints and treat it like delivery work — neat, predictable, fast. Something you can check off a list.</p><p>That’s not how good design works. It loops. It wanders. It uncovers things you didn’t expect. And if it feels a little uncomfortable, that probably means you’re asking the right questions.</p><p>If you’ve built products at scale, this’ll sound familiar. That tension between speed and clarity, between moving fast and thinking deeply. The notion of we need to “get it into the sprint” and “hang on, we don’t even know what this is yet.”</p><p>It doesn’t mean something’s broken, it does mean something needs space.</p><h3>Why jumping to hi-fi too early trips us up</h3><p>Years ago, Jesse James Garrett laid out five layers of user experience:</p><p><strong>Strategy &gt; Scope &gt; Structure &gt; Skeleton &gt; Surface.</strong></p><p>With this layer cake, most teams start at the top; surface. The UI. What it should look like.</p><p>It’s tempting. It feels productive.</p><p>But when you start there, you’re polishing guesses instead of solving the right problem, it’s the illusion of confidence.</p><p>The best design work I’ve seen moves the other way. It starts with what’s true, with what’s needed and with what’s broken.</p><p>Then it moves up.</p><p>Things like service blueprints, system maps, and collaborative OOUX sessions help teams think through this.</p><p>They bring clarity before decisions get locked in.</p><p>That’s not a delay, it’s actual alignment.</p><h3>Start with the experience, not the object</h3><p>Greg Storey reminded me of an exercise that shows this clearly and delves into the hand-off of divergent and then convergent thinking.</p><p>Ask someone to design a chair, and they’ll draw four legs and a back.</p><p>Ask them to design a way to rest your body after a long day?</p><p>Now you’re getting hammocks, bean bags, lounge chairs, maybe even a towel placed on some beach sand.</p><p>You’re not designing a thing, you’re set on designing an experience.</p><p>That shift; from object to need, that’s what early design work is about and it only happens when you give yourself space to look past the first idea.</p><h3>Exploration or what we also call discovery isn’t extra, it’s the job</h3><p>Design is more than making something look nice. If it were only that, the job itself would be as easy as pouring a bowl of cereal on a lazy Sunday.</p><p>It’s spotting complexity before it hits production.</p><p>It’s asking the questions that might change the whole scope.</p><p>It’s getting Product, Dev, and Design in a room and realizing,</p><blockquote>“Wait, this isn’t just a button. It’s a whole flow.”</blockquote><p>And a lot of that happens before a single screen gets made.</p><p>It might even look like mapping how a system works; rethinking relationships between objects.</p><p>Or walking through a messy Miro board full of half-ideas that don’t make the final cut but needed to happen anyway.</p><p>That’s not extra work, it’s what keeps us from wasting time later.</p><h3>Scrum’s not broken but it’s not the whole picture</h3><p>Scrum is a solid framework. It adds structure, it helps teams deliver work but it also works best when you’re all clear on what you’re building.</p><p><strong>But here’s the truth: You’re almost never completely clear on what you’re building.</strong></p><p>And that’s okay. That tension is useful, it’s where the better questions live.</p><p>Scrum helps teams move in a straight line. Discovery doesn’t.</p><p>That’s why dual track models feel more honest.</p><p>One track for exploring, one for building. Two distinct rhythms, shared together and guess what? It doesn’t mean slowing down.</p><p>It means thinking more clearly so you don’t have to redo things two sprints from now. Who finds any fun in that?</p><h3>We keep revising how we work</h3><p>We’re still figuring this out, still learning when to explore, when to move, and how to balance clarity with curiosity.</p><p>But design needs room to think. And honestly? Most things do.</p><p>In work, in life, in the way we build things; what we do evolves and so should how we do it. That kind of rethinking isn’t a weakness. It’s part of getting better.</p><p>And most of the time, that doesn’t start in a sprint ticket.</p><p><strong>I’m curious: is your team moving this way? Let me know.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59ec15d739b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paychex-ux/design-needs-room-to-think-59ec15d739b5">Design needs room to think</a> was originally published in <a href="https://medium.com/paychex-ux">Paychex UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Confessions from a Sell Out Designer]]></title>
            <link>https://medium.com/paychex-ux/confessions-from-sell-out-designer-007a2b4f638d?source=rss----b5f024a70dc0---4</link>
            <guid isPermaLink="false">https://medium.com/p/007a2b4f638d</guid>
            <category><![CDATA[design-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Jon Daiello]]></dc:creator>
            <pubDate>Thu, 07 Aug 2025 16:07:22 GMT</pubDate>
            <atom:updated>2025-08-25T13:33:51.660Z</atom:updated>
            <content:encoded><![CDATA[<h4>The uncomfortable truth about increasing your impact as a designer</h4><blockquote>The views expressed here are that of the author and do not necessarily reflect those of Paychex.</blockquote><p>Two weeks ago, I was in a meeting with some other leaders. We were working through resource allocation, trying to crack a staffing problem with some reprioritized projects. The words that came out of my mouth that would have made a previous design purist version of myself roll my eyes and flop on the ground with disgust.</p><blockquote>“Hmm, I’m not sure if we have the resources for that, and whether the ROI is worth it.”</blockquote><p>As the words were leaving my mouth, I cracked a smile because I sound exactly like every “out of touch” corporate leader I used to complain about in my early years of design. The kind of person who “just doesn’t get design.” The kind of person who puts business metrics over user needs. The kind of person I’d throw under the bus for lacking user empathy. The kind of person who cared only about putting more dollars in the corporate bank.</p><figure><img alt="Hand drawn words reading “Corporate Sell Out?”" src="https://cdn-images-1.medium.com/max/1024/1*4rLnfTF5H6tK3OKib1i_lw.jpeg" /><figcaption>Is this really becoming a corporate sell out?</figcaption></figure><p>Yikes. I’ve become the anti-design villain in my own story. Right?</p><p>The early career version of myself would be absolutely disgusted with corporate me. I believed good design was inherently valuable. It needed no explanation or justification. Just design good stuff. If we just cared enough about users, the dollars would magically airdrop into our bank account. Anyone who talked about ROI and resource allocation lacked the rigor to make tough decisions and fight for the user.</p><h3><strong>Six Phrases I’ve Adopted</strong></h3><p>It’s clear I’m not the same designer I was five years ago. Actually, am I even still a designer now that I spend my days in a management role?</p><p>Either way, I’m owning accountability for the change. Let’s explore a few of these “sell out” phrases…</p><h4><strong>💬 “What’s the ROI on that?”</strong></h4><p><strong>I used to think:</strong> Good design speaks for itself. If leadership can’t see the value, they’re completely missing the point. It’s good for users, so why wouldn’t we do it?</p><p><strong>Now I know:</strong> A business has to remain profitable to stay alive and deliver value to users. Every hour we spend on work costs money, and without some idea of what we get in return, it’s foolish to spend money.</p><p>I used to roll my eyes when leaders asked about return on investment. How do you put a number on delight? How do you measure the value of intuitive interactions?</p><p>Turns out, you can. It takes work. It’s not a prediction. And, it’s not exactly scientific. But designers need to learn how, because when the company needs to improve its bottom line, designers need to be able to have conversations that offer value.</p><p>Now when I hear “What’s the ROI,” I get excited. Because I know how our design decisions contribute to that last million in revenue. I know which interface changes increased conversation rate, and which UX concessions are still lingering out there that can be improved. I can connect design decisions to a business outcome that leadership actually cares about.</p><p>This isn’t selling out. It’s speaking a different language. A language that designers aren’t typically taught to speak.</p><h4><strong>💬 “That’s a great idea, but it’s not aligned with our strategy.”</strong></h4><p><strong>I used to think:</strong> If our users want it, we’re fools to ignore it. How is “helping our users” not our “strategy”?</p><p><strong>Now I know:</strong> Scattered efforts help no one effectively. It’s the difference between the sunshine spread everywhere, vs focusing the sunshine with a magnifying glass to burn a hole in something. Focus matters.</p><p>Strategic focus isn’t corporate speak for “we don’t care.” It’s saying, “We can’t do it all and we can’t serve everyone, so we’re going to choose to make the most of the time and money we have.”</p><p>When you try to solve everyone’s problem, you solve no one’s well. When your product tries to serve every market, it doesn’t “fit” with anyone specific. And when you constantly ship generic features to your users, they’re never truly satisfied. Which means they’ll look elsewhere to solve their needs. They’ll look for something that feels like it understands their needs and makes their lives easier.</p><p>Strategic focus isn’t about caring less. It’s about caring so much that you’re willing to concentrate your energy where it can make the biggest difference. It’s choosing to dramatically improve the quality of life for a specific set of people. It’s caring in a way that more users will actually feel.</p><h4><strong>💬 “We can’t have scope creep.”</strong></h4><p><strong>I used to think: </strong>More features equal more value. Why wouldn’t we want to make the project even more valuable?</p><p><strong>Now I know:</strong> Unchecked scope kills projects and wastes time and money.</p><p>This is directly connected to strategic focus (see previous section). If someone has a brilliant addition to our project, including it isn’t always the “right” decision. More functionality doesn’t always mean better user experiences.</p><p>Scope creep is the enemy of delivering value to users. It’s how six-month projects become eighteen-month projects that get killed because they are taking too long and not impacting users. Unchecked scope creep makes projects less effective because they spread resources thin. They bolt on ideas mid-project stream and never fully integrate for smooth experiences.</p><p>Now when I identify scope creep, I’m asking questions to help protect the project’s ability to actually help users. Focused scope means usable solutions that people can actually benefit from. It means supporting our strategic focus.</p><h4><strong>💬 “That’s not technically feasible.”</strong></h4><p><strong>I used to think: </strong>Stop making excuses and do hard things. It’s just code, rewrite it. I redesign screens all the time. It’s not like I’m asking for a time machine.</p><p><strong>Now I know:</strong> Constraints are real. Technical complexity is wrought with deep difficulties. Typically, technical debt is incredibly expensive to pay off.</p><p>As a young, bright-eyed designer, I used to think technical feasibility was someone else’s problem. I would do what was asked, figure out a solution. If I designed something amazing, it was the engineering team’s job to figure out how to build it. Technical complaints felt like laziness.</p><p>Now I understand that working within technical reality keeps businesses running. You can’t rebuild the ship every 6 months and expect to turn a profit. Technical constraints can actually breed creativity. In fact, they should. When you understand what’s actually possible, you can design solutions that will exist in the real world, not just in your imagination. And, if you can’t implement your ideas, they fail the test of delivering value. Fantasy ideas don’t impact users.</p><p>The best design solutions work with constraints, not against them. When you understand the technical landscape, you can push boundaries intelligently instead of proposing impossible dreams.</p><h4><strong>💬 “It doesn’t have to be perfect.”</strong></h4><p><strong>I used to think: </strong>We can’t compromise on quality. I won’t put my name on anything crappy. It’s not my fault if leadership can’t see the glaring issues. Plus, users need the best, not an experience with a bunch of holes.</p><p><strong>Now I know:</strong> Users can’t benefit from solutions they never see because they are still being worked on. Plus, you won’t know how well something works until it’s in the wild, unprotected world. So, don’t overinvest in things.</p><p>Remember “pixel perfect”? Every interaction had to be flawless. Every edge case had to be considered and solved before we could ship anything. While it’s important to maintain high-quality experiences, we will never reach a perfect state, so we need to adjust our expectations and deprioritize things that can be improved later.</p><p>Why? Because perfect solutions that never ship help no one. “Good” solutions in users’ hands beat perfect solutions in perpetual development. It’s being frugal with time while getting value to users faster.</p><p>This doesn’t mean shipping garbage. Nor does it mean scoping solutions down so they are worthless. It means recognizing that continuous improvement beats perfection. Ship something good, learn from real usage, then make it great. Users would rather have a solution that works 90% of the time today than a solution that works 100% of the time next year.</p><p>And remember, what seems perfect today will quickly become imperfect over time.</p><h4><strong>💬 “How does this benefit the business?”</strong></h4><p><strong>I used to think: </strong>That’s gross. Don’t be so self-centered. It’s not about you, it’s about the user. I mean, we are USER experience designers. User benefit IS business benefit. If it’s good for users, that should be enough justification.</p><p><strong>Now I know:</strong> Our business can’t help anyone if we go out of business. So, it’s a balance of serving the business in how we serve the user.</p><p>When I came to terms with this idea, it was sort of a crisis moment in my career. Asking how design benefits the business felt like betraying my user-centered training. Wasn’t putting business needs first exactly what design was supposed to fight against? Weren’t we supposed to “fight for the user” just like Tron?</p><p>But here’s what I’ve realized: companies that don’t make money don’t survive. Companies that don’t survive can’t help users long-term. When design drives business results (increased revenue, increased user retention, etc.), businesses trust design enough to invest in more design. When businesses invest more in design, more users get better experiences. It’s <a href="https://medium.com/@jondaiello/when-survival-mode-corrupts-user-experience-26573aa239b7">not an excuse for underhanded or shady UX practices</a>. It’s a call to consider all the people you’re designing for.</p><p>The most user-centered thing you can do is create design solutions that make the business successful along with the user. Finding this balance is important the longer you’re in design.</p><h3><strong>Why “Selling Out” Happen</strong></h3><p>I can imagine the skepticism that some readers might have. That’s ok. I’m not here to change your thinking. I’m here to confess my sell-out status, remember? I’ve become everything my former idealistic self swore I’d never become. I speak in business metrics. I prioritize strategic alignment. I make decisions based on resource constraints instead of unchecked passion for users.</p><p>And here’s my experience: it works. In fact, it’s necessary.</p><p>“Serving the business” can feel icky. We’ve all heard horror stories of corrupt businesses doing shady and downright illegal things. But, that’s not every business. In fact, that’s not even most businesses.</p><figure><img alt="A hand drawn picture of a person with business words coming out of their mouth." src="https://cdn-images-1.medium.com/max/1024/1*cGsyBM5kd7w9Fs6DR45gAw.jpeg" /><figcaption>Learning to speak a different language.</figcaption></figure><p>I want to encourage you, that <a href="https://medium.com/paychex-ux/design-business-not-versus-977a8546ee04">serving the business doesn’t have to conflict with user impact</a>. When you focus your energy, you create bigger changes. When you speak business language, you clearly show the importance of design work. When you understand technical limitations, you design solutions that actually ship.</p><p>Selling out was the superpower I didn’t know I needed. Converting design-speak into results-speak. Leaders don’t care about design. In fact few even know what design really is. Leaders care about results. When you can translate “user will like this” into “this reduces support costs by 25% and increases retention by 12% leading to a potential revenue increase of $2.5 million dollars,” suddenly business leaders and leaning forward in their chair.</p><p>This isn’t about abandoning design principles. It’s about making those principles attractive to the people responsible for budgets and priorities.</p><h3><strong>For Designers Ready to Evolve</strong></h3><p>If you’re reading this and feeling defensive about my corporate transformation, I get it. The “design school” version of myself would have written a scathing response about how I’m part of the problem.</p><p>But here’s what I wish someone had told me earlier: this evolution doesn’t make you a sell out. It makes you effective.</p><p>Learning business language doesn’t compromise your user advocacy. It scales it. The designers who mature in business understanding become the ones that make a bigger impact. They become the ones with time, trust, and the ability to create change at scale.</p><p>Your passion for users is still there. That should never go away. But now it’s informed by how the business works, focused by thinking strategically, and grounded in today’s reality. That makes it more powerful, not less.</p><p>The goal isn’t to become a heartless corporate drone bent on profit at all costs. Nor is the goal to normalize unethical or evil practices. The goal is to become so strategically valuable that leadership seeks you out when they are making product decisions.</p><p>If you’re interested in learning more about this, I’d recommend reading <a href="https://thecdo.school/books/">Business Thinking for Designers</a> by Ryan Rumsey. It’s a great primer to give you some practical advice on how to “speak business”.</p><p>So yes, I’ve become a corporate design sell out. And it’s been a huge part of my career growth. Now, my impact on people is bigger than I had imagined before.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=007a2b4f638d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paychex-ux/confessions-from-sell-out-designer-007a2b4f638d">Confessions from a Sell Out Designer</a> was originally published in <a href="https://medium.com/paychex-ux">Paychex UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI as a thought partner, not a shortcut]]></title>
            <link>https://medium.com/paychex-ux/ai-as-a-thought-partner-not-a-shortcut-3859d5b486ed?source=rss----b5f024a70dc0---4</link>
            <guid isPermaLink="false">https://medium.com/p/3859d5b486ed</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[creativity]]></category>
            <dc:creator><![CDATA[Erik Sagen]]></dc:creator>
            <pubDate>Tue, 22 Jul 2025 13:30:42 GMT</pubDate>
            <atom:updated>2025-07-22T13:30:42.352Z</atom:updated>
            <content:encoded><![CDATA[<h4>Rethinking disclosure, process, and how we shape ideas and think with machines</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ztGlja1U1WeYZc_YJlHipQ@2x.jpeg" /><figcaption>Photo by Youjeen Cho on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>The views expressed here are that of the author and do not necessarily reflect those of Paychex.</blockquote><p>I don’t use AI to generate my work. I use it to challenge and shape how I think.</p><p>That alone shifts the conversation and, I’d argue, makes the current wave of AI disclosure policies feel oddly misaligned. Not wrong. Just incomplete.</p><p>Because when companies ask for AI disclosure, it’s often through the lens of “Did you use a shortcut?” Like you typed in a prompt, took whatever came back, and passed it off as your own. But that’s not how real collaboration with AI works — at least not the kind that’s meaningful.</p><h3>What we get wrong about disclosure</h3><p>There’s an assumption behind most AI usage disclosures: that there’s a clean line between what was “human-made” and what was “machine-assisted.” But when the process is conversational, when ideas are shaped in collaboration with AI, over time and through multiple turns, that line gets blurry.</p><p>And honestly, it should.</p><p>The more nuanced the thinking, the harder it becomes to say who “authored” what. Not because we’re hiding anything, but because the output isn’t a static product. It’s the byproduct of working through something alongside a system that thinks differently than we do.</p><h3>Not just the best sandwich</h3><p>Most people treat AI like a shortcut machine.</p><blockquote>“Help me make the best tuna sandwich.”</blockquote><p>But the more valuable interaction sounds more like this:</p><p>“Wait. Should I even be making a tuna sandwich?”</p><p>“It’s summer; what’s in season?”</p><p>“Do I have anything fresh in the garden?”</p><p>“Am I eating alone, or making this for someone else?”</p><p>“Is tuna what I actually want, or just what I always make?”</p><p>It starts with a prompt, sure. But then it becomes a process; a back-and-forth that shifts your thinking. You don’t just optimize the sandwich. You reevaluate the whole lunch.</p><p>That’s when the collaboration becomes meaningful.</p><p>Not because the output is better, but because the reason behind the output is clearer.</p><h3>Creative intelligence in action</h3><p>Greg Storey calls this Creative Intelligence. The ability to move through distinct thinking modes when collaborating with AI:</p><ul><li><strong>Exploratory mode</strong> surfaces better questions</li><li><strong>Generative mode</strong> sparks ideas and rough drafts</li><li><strong>Critical mode</strong> challenges weak assumptions</li><li><strong>Strategic mode</strong> helps you weigh context and constraints</li><li><strong>Synthesis mode</strong> connects ideas across unexpected domains</li></ul><p>The modes aren’t mechanical. They’re human. You move between them naturally, and AI supports you differently in each one. When it works well, it doesn’t feel like outsourcing. It feels like progress.</p><h3>Disclosure isn’t the problem, it’s the framing</h3><p>I’m not against disclosure. But most of what’s being asked right now is checkbox-level thinking.</p><blockquote>Did you use AI: Yes or no?</blockquote><p>That binary framing leaves out the most important part; how we used it, why we used it, and whether it actually made the work more thoughtful, more considered, more clear.</p><p>If we reduce that to a prompt log, we’re missing the point.</p><p>Because the output isn’t the proof. The process is.</p><p>Here’s what I’d rather be asked:</p><blockquote>“How did AI help you think better?”</blockquote><p>That question opens the door to process. To the different modes, to reflection.</p><p>It encourages a conversation, not a confession.</p><p>And it moves us closer to something that feels honest.</p><p>Not just about AI — but about how we think, collaborate, and create.</p><h3>Companion reading</h3><p>Want to know more about this topic? This piece pairs closely with Greg Storey’s book “Creative Intelligence: Thinking Beyond the Algorithm”.</p><p>If the modes I mentioned resonated with you, or if you’ve been rethinking how AI fits into your process (not just your tools) I highly recommend reading his work.</p><p>It’s not about prompt optimization.</p><p>It’s about creative collaboration with systems that challenge you.</p><p>You can read more here:</p><p>👉 <a href="https://brilliantcrank.com/creative-intelligence-sample/">Creative Intelligence</a> by Greg Storey</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3859d5b486ed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paychex-ux/ai-as-a-thought-partner-not-a-shortcut-3859d5b486ed">AI as a thought partner, not a shortcut</a> was originally published in <a href="https://medium.com/paychex-ux">Paychex UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Bones of UX]]></title>
            <link>https://medium.com/paychex-ux/the-bones-of-design-0debd6341106?source=rss----b5f024a70dc0---4</link>
            <guid isPermaLink="false">https://medium.com/p/0debd6341106</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jon Daiello]]></dc:creator>
            <pubDate>Thu, 29 May 2025 22:25:49 GMT</pubDate>
            <atom:updated>2025-07-16T16:22:32.979Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>What the human body teaches us about organizing and design</em></h4><blockquote>The views expressed here are that of the author and do not necessarily reflect those of Paychex.</blockquote><p>Over my 15+ years in the world of design, I’ve seen a lot of projects. Some tend toward a gigantic mess. They progress slowly, experience constant rework, expectations are misaligned, etc. But every once in a while, you get a project that just hums along. Things move fast. Teams are in sync. Decisions come easily. Everyone knows what they’re doing and why. When it happens, it’s usually by accident. But what if we could encourage it to happen more often? What if it wasn’t up to the muse?</p><p>We had one of those smooth projects recently. But it wasn’t up to luck. It was structure. More specifically, it was the result of years of increasing our practice of Object Oriented UX (OOUX). It provided a foundation of shared structure, and it made all the difference.</p><p>If design exploration and creativity is the muscle, then structure is the skeleton. Muscle doesn’t work without a structure to pull against. Muscles without bones are just a blob. No meaningful movement or power. Structure gives our creative work the tension to create power. Our design strength isn’t weakened by structure, it’s empowered by it.</p><figure><img alt="Hand drawn illustration showing arm bones and muscle creating power." src="https://cdn-images-1.medium.com/max/922/1*6-fxnSFrqshAH7Rzpunwmw.jpeg" /><figcaption>Power need structure to work.</figcaption></figure><h3><strong>The Pitfalls of Unstructured Design</strong></h3><p>It’s way too easy for teams to jump straight into flows and interface mockups. Stakeholders ask for features. Project deadlines get established. Agile backlogs are screaming. Designers…they respond with screens. It’s the most concrete thing they can show, and makes all the team members feel like they understand where things are headed.</p><p>But without clear organization, things are unnecessarily murky.</p><p>It’s like trying to flex muscles without a skeleton. The muscles tighten up, but there’s nothing to flex against. What happens? Misalignment, rework, and weak solutions. People are moving, but not together and not effectively.</p><p>So, the question is…how do we prevent this?</p><h3><strong>Structural Thinking That Changed Everything</strong></h3><p>I came across Object Oriented UX over three years ago. A coworker introduced me to it, and as someone who’s spent time as a developer with Object Oriented Programming, the thinking just clicked. I was hooked.</p><p>While I didn’t dive deep early on, I started working with the basics: identifying core objects, naming attributes, and mapping relationships. Immediately, I began to see clarity emerge. It was easier to spot gaps, drive conversation with stakeholders, and lead design activities with more confidence. While I had a personal love for OOUX, it wasn’t broadly used as an approach across the organization.</p><p>That is…until recently. In the last few months, a couple of people on the team picked up OOUX thinking and started running with it on a recent project. I was elated that someone else saw the value of structural thinking!</p><figure><img alt="Hand drawn illustration of a leg showing a knee hinge applying muscle power" src="https://cdn-images-1.medium.com/max/1024/1*i-ewz27s-rCRyPhON6Xp3w.jpeg" /><figcaption>Bones work like a lever to apply force from muscles</figcaption></figure><p>This project was fast-moving. But someone on the team had the foresight to slow down early in the project to inventory and map the objects and relationships. They used a home-grown tool based on object-oriented thinking. In just a few sessions, it gave us a clear foundation on what would be surfaced to the user, how those elements related, and what structure held them together. It created the skeletal structure for the team to rally around. And, that brief slow down paid off incredibly.</p><p>I saw three huge benefits:</p><ol><li>That clarity unlocked <strong>stronger partnerships</strong>. Everyone on the project quickly agreed on a clear object model. That meant we were all pulling in the same direction. We didn’t waste time reinterpreting vague requirements or untangling miscommunications. Product leaders, engineers, architects, and designers all understood what we were designing and how things connected.</li><li>Teams could independently <strong>run in parallel.</strong> That clarity meant death to waterfall design handoff. It increased the trust between teams and disciplines, all founded on a strong shared understanding. The teams could run independently in parallel because they knew the general structure to keep their work in harmony.</li><li>It <strong>doubled the speed of design work.</strong> The designers didn’t have to waste exploration to get clear on what information the user would see and the relationships of those items. Instead of what to show, they could focus on how to show it. Their design energy was focused on the best methods of arranging the objects to the user.</li></ol><p>While there are other benefits, these three were high on my list as a design leader. Because we had the bones in place, the creative work (the muscle) could do its job. The solid structure provided an anchor point to leverage the strength of creativity. The designers moved quickly, confidently, and with purpose. And best of all, they did it in harmony with the teams around them.</p><h3><strong>Getting Started with OOUX</strong></h3><p>Now, you may be wondering how you can see these same results? Well, your mileage may vary depending upon your project and culture. But, in my personal experience using OOUX and watching my teams rely on it…I highly recommend this toolset.</p><figure><img alt="Hand drawn illustration of an apple tree with sun and grass" src="https://cdn-images-1.medium.com/max/1024/1*_hwm-9DFwYfbnthsfa1ETw.jpeg" /><figcaption>Mapping objects doesn’t have to be overly complex</figcaption></figure><p>You don’t need to overhaul your entire process to start benefiting from OOUX. Please don’t do that. It’s another tool in your tool bag for making sense of design problems.</p><p>You can start small and grow into it over time:</p><ul><li>Identify the <strong>core objects</strong> your users will interact with. Some people refer to these as the “nouns” of your experience. They are the “objects” that you have to account for in your project. If you are building a fruit experience, one object might be an apple. It’s a thing, concrete and definable. Not eating the apple, but the apple itself. You can start asking: what are the “things” that exist in the real world that have to be represented in the digital experience? What “things” are created and managed? This thinking will give you a solid starting point for what comes next.</li><li>Define the <strong>attributes</strong> of each object. Each “thing” (or object) has defining qualities. Just like an apple has a color like green, red, or yellow. An apple also has ripeness. These are the defining characteristics of objects that are represented in the system, making each object unique and distinguishable. What characteristics define the objects in the system? Which things can be changed or not changed? (titles, descriptions, colors, statuses, dates, etc.) These attributes quickly provide the details that frame people’s interactions with these objects.</li><li>Map the <strong>relationships</strong> between them. This is one of the next critical steps. Objects (or the “things” in the system) don’t live in isolation. They interact with other objects. An apple has a relationship with a tree, and the crate it gets shipped in, and the display at the grocery store that sells it. Mapping how these objects relate to each other provides clarity in how a user could make sense of them. Are there parent-child relationships? Does one object require another? Are there any hidden objects? These relationships provide clarity on how the bones are arranged and bound together.</li></ul><p>Even simple exercises like these bring clarity fast. And they scale beautifully. They provide the starting point for clarity. No, they’re not a full representation of the OOUX toolset, but they are the beginning of object-oriented thinking that you can get comfortable with and start using today.</p><p>If you want to go further, you can check out <a href="https://www.ooux.com/resources/introducing-orca-the-third-diamond-in-your-ux-process">the ORCA process</a> from Sophia Prater at <a href="https://www.ooux.com/">OOUX.com</a>. And if you want to dive even deeper, you can join the <a href="https://www.ooux.com/community">OOUX community</a> and take some <a href="https://www.ooux.com/training">official training</a>. These tools give you the structure to support more ambitious design work — without guessing.</p><p><em>(Important disclaimer: Despite what you may be thinking…there are no affiliate links or kickbacks here. It’s just my passion for sharing useful resources to help designers be more effective.)</em></p><h3><strong>Structure is an Asset</strong></h3><p>Let’s revisit our human skeleton analogy. Without an organized skeleton of bone, muscles cannot create human mobility. We can’t lift or move objects. Humans need both muscle and bone. Those bones must be organized. Whenever a bone breaks, it reduces the ability for muscle to exert force.</p><figure><img alt="Hand drawn illustration of a skeleton with missing bones: Structure Needed" src="https://cdn-images-1.medium.com/max/1024/1*ryQ4dkJIyffYaoOh7IhX-A.jpeg" /><figcaption>Structure is required to use creative power</figcaption></figure><p>Plus, there are a variety of bones in the human body. The femur is extremely strong. The inner ear bones are small and sensitive. You can rely on the femur to direct the power of strong leg muscles…not so much with the inner ear bones. Organizing these bones, understanding their attributes, and arranging their relationships provides the context for muscle to be effective.</p><p>It’s the same way with design. Organization provides the structural clarity for you to apply the power of creative muscle. It makes your design power effective. Just think about the incredible strength of Olympic power lifters. It’s all made possible by a healthy skeletal structure.</p><p>When projects are murky and ill-defined, ask yourself if you briefly slow down to get organized.</p><p>How can you take a design exploration approach to understanding the objects of your project? How can you partner with the teams in your space to align on this kind of map?</p><p>The rigidity of structure should be an asset, not a detractor. Especially when it’s used as a supportive element. It’s what allows creative thinking to provide momentum, rather than wasteful effort. Because the best muscles in the world are useless without something to pull against.</p><p>OOUX thinking gave our team the bones to move with purpose. And every time we use it, we’re reminded: structure isn’t a barrier to creativity…it’s what maximizes its power.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0debd6341106" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paychex-ux/the-bones-of-design-0debd6341106">The Bones of UX</a> was originally published in <a href="https://medium.com/paychex-ux">Paychex UX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>