<?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[Sense and Signal - Medium]]></title>
        <description><![CDATA[The purpose of this blog is to create a place where rigorous discussions around Leadership, Organization Dynamics, and Sense Making can have home. - Medium]]></description>
        <link>https://medium.com/sense-and-signal?source=rss----34ad259549c3---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Sense and Signal - Medium</title>
            <link>https://medium.com/sense-and-signal?source=rss----34ad259549c3---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:24:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/sense-and-signal" 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 Usability Trap (or: Why That Avocado Stick Shouldn’t Exist)]]></title>
            <link>https://medium.com/sense-and-signal/the-usability-trap-or-why-that-avocado-stick-shouldnt-exist-c48633bce41a?source=rss----34ad259549c3---4</link>
            <guid isPermaLink="false">https://medium.com/p/c48633bce41a</guid>
            <category><![CDATA[model]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jodah Jensen]]></dc:creator>
            <pubDate>Tue, 13 May 2025 03:46:07 GMT</pubDate>
            <atom:updated>2025-05-13T03:46:07.372Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zPSa9EFWDylmarvV" /></figure><p>Not long ago, I found myself staring at a product roadmap, the way you might look at a lasagna someone left out overnight — still vaguely recognizable, but clearly not safe to touch.</p><p>We were deep in “the usability phase,” which, for the uninitiated, is the part of product development where people obsess over whether buttons should be teal or cerulean and declare that “onboarding needs to feel like butter.” Nobody ever defines what that means. Salted? Unsalted? Churned with machine learning?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*15rhfRG9Ykb2YEVL" /></figure><p>Product Road Map</p><p>In these moments, I am reminded of something painfully simple: just because something is easy to use doesn’t mean it’s worth using.</p><h3>The Avocado on a Stick</h3><p>Picture this: someone hands you a stick of deodorant, only instead of Old Spice, it’s mashed avocado. You twist the base and glide it across your armpit like a green glue stick.</p><p>Is it easy? Absolutely. Is it useful? hmmm….perhaps for the few die hards who just get enough of that vegetable that insist on being a fruit.</p><blockquote><em>This is what happens when teams fall in love with usability.</em></blockquote><p>We build frictionless, delightful, beautifully designed nonsense. Nonsense that demos well. Nonsense that gets applause in design reviews. Nonsense that no one actually needs. But ultimately nonsense.</p><h3>Usability: The Polite Cousin of Value</h3><p>Usability is like that polite cousin who always shows up with pie and offers to help clean. You want them around — but you don’t build your house around them. It’s made of things like:</p><ul><li>Learnability (Can they figure it out?)</li><li>Efficiency (Can they do it quickly?)</li><li>Memorability (Do they remember how?)</li><li>Errors (How often do they screw it up?)</li><li>Satisfaction (Do they smile or swear at the screen?)</li></ul><p>These are important. Just not alone.</p><p>I’ve seen entire products championed because “users said it was easy.” Of course they did. <em>So is falling asleep at work</em>. Doesn’t make it useful.</p><h3>Usefulness: The Actual Point of the Whole Thing</h3><p>Usefulness is a slipperier creature. It’s less about delight and more about doing something that matters. Something that actually helps the person — or their boss, or their customer — get a job done.</p><p>It’s the difference between designing a doorknob that turns smoothly and realizing the door leads to a brick wall.</p><p>The trick is: usefulness is messy. It’s tied to context, perception, politics, purpose. The user may not even be the person who feels the benefit. Sometimes the user is just a courier delivering value to someone else.</p><h3>Performative Products and The TAM Model</h3><p>I once worked with a team that spent six weeks crafting a dashboard. Visually, it was impeccable — rounded corners, elegant hover states, animations that felt deliberate and smooth. It showcased strong design execution and attention to detail.</p><p>But there was a problem…</p><blockquote><em>No one had asked for it, and more importantly, no one could explain how it supported a core task or business objective.</em></blockquote><p>When we launched it, the most common reaction wasn’t praise — it was confusion: <em>“What is this for?”</em></p><p>It was a clear example of what the Technology Acceptance Model (TAM) helps us understand: that perceived ease of use matters — but perceived usefulness matters more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oWt8rTB1n_FdeceW" /></figure><h4>TAM MODEL</h4><p>In this case, the dashboard delivered on ease — it looked great and interacted smoothly — but it fell short on usefulness. It didn’t align with a specific need, workflow, or goal the users actually had.</p><p>TAM research shows that perceived usefulness is 1.5x more predictive of actual adoption than ease of use. That distinction is critical. We can’t rely on polish alone to carry a product forward. A smooth experience doesn’t justify itself unless it’s anchored in real value.</p><p>Since then, I’ve come to think of these kinds of projects as performative products — well-intentioned work that demonstrates capability, but misses connection. They remind us that good design starts not with what we <em>can</em> build beautifully, but with what’s <em>meaningful to build</em> in the first place.</p><h3>Provotypes and the Art of Product Honesty</h3><p>At this point, I’m supposed to recommend prototyping. But honestly, I prefer provotypes — the rough, lo-fi, honest kind of visual thinking that’s not built to test <em>how</em> something works, but <em>whether it should exist at all</em>.</p><p>Where a prototype is often a refined simulation used to validate usability — layouts, interactions, flows — a provotype is deliberately raw. It’s designed to test the idea itself, not the execution. Prototypes say, <em>“Does this feel intuitive?”</em> Provotypes ask, <em>“Does this even matter?”</em></p><p>Prototypes are about optimization. Provotypes are about exploration.</p><p>You might sketch it on a whiteboard, walk someone through a storyboard, or mock up a fake landing page with a big “Sign up” button just to see if anyone bites. It’s not meant to simulate the product — it’s meant to surface reactions, spark conversations, and challenge assumptions before polish makes things too precious to question.</p><p>A provotype says: “I’m not finished. I’m not polished. But is this solving a problem you actually have?”</p><p>And when you use that approach, something critical happens: You stop building avocado sticks. You start building with intent.</p><h3>In Conclusion: Make It Easy and Meaningful</h3><p>I love good design. I love elegant workflows, well-placed interactions, and the quiet satisfaction of something that just works.</p><p>But it’s worth remembering: ease of use is only part of the equation. A smooth experience isn’t enough unless it’s tied to something that truly matters to the people using it.</p><p>The goal isn’t to create something that just feels good — it’s to create something that does good in the context of real needs, real work, and real value.</p><p>Because even the most beautifully crafted experience won’t last if it doesn’t help someone accomplish something that matters.</p><blockquote><em>Design should inspire. But it should also serve.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c48633bce41a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sense-and-signal/the-usability-trap-or-why-that-avocado-stick-shouldnt-exist-c48633bce41a">The Usability Trap (or: Why That Avocado Stick Shouldn’t Exist)</a> was originally published in <a href="https://medium.com/sense-and-signal">Sense and Signal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build it and….Who Will Come?!]]></title>
            <link>https://medium.com/sense-and-signal/build-it-and-who-will-come-2ee1779a7bff?source=rss----34ad259549c3---4</link>
            <guid isPermaLink="false">https://medium.com/p/2ee1779a7bff</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[research]]></category>
            <dc:creator><![CDATA[Jodah Jensen]]></dc:creator>
            <pubDate>Thu, 20 Mar 2025 02:08:10 GMT</pubDate>
            <atom:updated>2025-03-20T01:35:41.998Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ndPf3vsYf5Eg5ry7iuM9Jw.png" /></figure><h4>Are you asking the right questions about your Use-cases?</h4><p>There is a particular kind of optimism that I have seen at times take hold in the world of product design and development — a faith, really — that echoes the old quote from the movie Field of Dreams: <em>Build it, and they will come.</em> It’s an alluring idea, romantic really. The notion that an idea, with enough conviction and belief, will naturally draw an audience. That the value we see in our own creation is so evident that discovery by others is a mere formality.</p><p><strong>And yet, this belief — so often dismissed as naive — is not without its moments of truth. </strong>Under the right conditions, it is a legitimate approach. When confidence is high, when the consequences of failure are low, and — perhaps most crucially — when the process itself is fulfilling, this kind of thinking isn’t just reasonable; it can be fulfilling. Because oftentimes, the act of building is its own reward.</p><p>However there is a limit to this way of thinking — a line where optimism turns into recklessness. In the context of building a successful company, whether a scrappy startup or an industry giant, the <em>build it and they will come</em> mindset <em>can</em> be dangerous. It risks squandering precious resources on ambitious but uneducated bets.</p><p>Product development is, at its core, a series of bets — some big, some small, some risky, and some that feel like a sure thing. While this isn’t about dissecting the mechanics of those bets, there’s something even more important that needs to be considered: the critical questions we ask about them.</p><p>In my experience, the an important part of product development isn’t simply having all the right answers or even identifying the “sure things” — it’s about ensuring we’re asking the right critical questions in the first place. Questions shape how we evaluate risks, challenge assumptions, and uncover potential blind spots before they become costly mistakes. The act of questioning is powerful because it forces us to confront uncertainty head-on and refine our thinking before we commit to a bet.</p><h3>Use-cases... An under appreciated tool for bet analysis</h3><p>I don’t think it’s necessary to point out that if use-cases were the only place you were asking product-related questions, we’d likely already be in trouble. However, assuming questions have been proposed, tested, and validated, I’d like to share my thoughts on use-cases for guiding future product strategy and decision-making.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XITAvwmI462g8z7jxLAhYA.png" /></figure><p>At the risk of stating the obvious, let’s quickly define what a use case is. The good news is, it’s exactly what it sounds like: a specific scenario that illustrates how a system, product, or process is used to achieve a goal. It’s a story — who’s using the thing, what they’re trying to do, and how they get there. Sometimes it’s formal, with diagrams and structured templates. Sometimes it’s scribbled on a whiteboard. Either way, the format doesn’t matter as much as whether it actually communicates the right information to your team. Simple enough.</p><p>So what’s the hard part?</p><p>Use cases tend to show up late in the development process — when engineers are deep in the code and product is hammering out final details. They’re often treated as a way to translate product decisions into engineering terms, a communication tool rather than a validation tool. But if you dig into their intended purpose, you’ll find they’re meant to do a lot more:</p><ul><li>Communicate requirements</li><li>Guide design and development</li><li>Facilitate testing</li><li>Prioritize features</li><li>Understand user needs</li></ul><p>User needs made the list, but barely. It’s one of five, and if we’re being honest, it’s not the reason most teams use them. This is unfortunate, because these are a great place to explore your bet before commiting more chips to the table. Its a great place to ask some really critical questions, even if you might not have the answers (it is a bet after all). What are these critical questions?</p><ol><li>What is the users goal?</li><li>What information does the user need to achieve their goal?</li><li>What action does the user take, what happens next?</li><li>How does this screen connect to the next step in the flow?</li></ol><h3>Map your Personas to the Use-case</h3><p>If someone is using your solution, then someone is an actor in your use case. Do you know who they are? Have you at least asked the question and formed a hypothesis? Or are you simply building with the hope that <em>they</em> will come?</p><p>Critically examining the <em>who</em> of your use case is incredibly valuable.</p><p>In the image below, I’ve provided a simple example of a use-case overview comparing two identified personas. Let’s assume we’ve both just been dropped into this situation — I don’t know how these personas were chosen, nor do I have a full picture of where they’re headed. However, what I <em>can</em> see is that the team believes the CFO and Risk Manager are key personas who will engage with the system, particularly within this specific use case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l0rcoIB_k-nppyQm9Qu8aA.png" /></figure><p>I’m going to use the word <em>screen</em> loosely here, as modern apps blur its traditional meaning. With dynamic interfaces and real-time updates, what users see is more fluid than fixed. Yet, we still use <em>screen</em> as a familiar way to discuss different parts of an interface.</p><p>So with that said, ask the previous 4 questions fort each persona per screen. Thats right. For each screen in the flow, ask yourselves:</p><h4>What is the Users Goals?</h4><p>This might be the most important question. I’ve encountered situations where I was brought in to help push a project across the finish line, only to find that the team couldn’t answer this simple yet critical question. They had a clear idea of the “output,” but struggled to articulate the actual goal. This was partly because they hadn’t clearly identified the persona, but also because they simply hadn’t thought of it as a goal in the first place.</p><p>I won’t dive into the complexities of defining goals — there are countless ways to approach them — but I’ll leave you with this: Asking <em>“What is the user’s goal on this screen?”</em> ensures that each step in a use case flow has a clear purpose. It helps cut through unnecessary complexity, aligns teams on what truly matters, and guides design decisions that support user intent. If a screen lacks a well-defined goal, it’s a signal that it needs to be reworked, simplified, or even removed.</p><h4>What information does the user need to achieve their goal?</h4><p>Once you’ve identified the user’s goal, the next question is whether you’ve provided them with the right information to achieve it. This answer often varies depending on the persona. For example, a CFO will likely need a different set of information to make decisions than a risk manager, with varying levels of detail and complexity tailored to each role’s needs.</p><p>Asking, <em>“What information does the user need to achieve their goal?”</em> ensures that every screen delivers the essential details at the right moment. It helps prevent cognitive overload, reduces friction, and keeps users focused on what matters most. If critical information is missing or buried, it can disrupt the experience and make it harder for users to accomplish their task efficiently.</p><h4>What action does the user take, what happens next?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a6W8qb5z7aypdE7GAOckYw.png" /></figure><p>This question ties into the previous one, as both are deeply influenced by the persona and their expectations. Depending on the target persona, the actions users take and their anticipated outcomes may vary significantly. It’s important to assess whether the designed engagement aligns with what your personas would realistically expect. If there’s a mismatch, you’ll need to reconsider whether the solution is right for that persona or if a tailored learning experience is needed to guide them effectively.</p><p>Asking, <em>“What action does the user take?”</em> is key to understanding the flow and ensuring that each action leads to a clear, logical outcome. If the next step isn’t intuitive or doesn’t match user expectations, it can create confusion, disrupting the flow and making it harder for users to accomplish their tasks efficiently.</p><p>I really love the second part of this question — <em>“What happens next?”</em> In software, everything revolves around input and output — data flowing in and out, constant handoffs between stages. Each time a user takes an action, it’s essential to consider whether the persona has everything they need to move seamlessly to the next step. This is where the power of handoffs comes in: Are they equipped with the right information, tools, or context to keep the flow moving smoothly? Thoughtfully designing these transitions is key to creating a fluid, frictionless experience. Without smooth handoffs, users can get stuck, and the overall process becomes disjointed.</p><h4>How does this screen connect to the next step in the flow?</h4><p>Thinking rigorously about how the one screen works with another screen is really getting into some weeds, but the kind of weeds that pays of in a garden of success.</p><p>Asking <em>“How does this screen connect to the next step in the flow?”</em> is critical for maintaining a smooth and cohesive user experience. When the connection between screens is seamless, users feel confident in the solution, trusting that each step logically follows the last. However, if the flow feels disjointed or thoughtless, it undermines that confidence — users may start to doubt the solution’s effectiveness or question whether it can truly meet their needs. A poorly connected flow can disrupt the user’s sense of control and purpose, causing frustration and potentially leading to abandoned tasks or disengagement. A thoughtful, intentional flow reinforces trust and keeps users moving toward their goals without hesitation.</p><h3>Use-cases are a great way to build your hypothesis</h3><p>Ultimately, what I’m suggesting here is to use your use cases as a framework for asking critical questions about the value proposition your team is providing. You don’t have to have all the answers upfront — just ask the right questions to understand where you stand. What do you know? What do you still need to know? As you progress, make adjustments to the design based on the answers you uncover. Decide whether the answers you’ve gathered are sufficient to move forward or if it’s better to reduce the product scope to mitigate risk, or perhaps maintain the current scope but inject some short-term research to gain clarity. Here are the key points:</p><ul><li>Leverage use cases as a way to ask value proposition questions.</li><li>Identify all the personas you anticipate will engage with the use case (is this the right phrasing?).</li><li>Clarify what each persona needs from the solution at every step.</li><li>Continuously evaluate whether the current design supports the goals of all involved personas.</li><li>Use insights gathered to refine the design and determine the next steps — whether that means moving forward, reducing scope, or investing in additional research.</li></ul><p>That is it; thats all I got. Until next time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ee1779a7bff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sense-and-signal/build-it-and-who-will-come-2ee1779a7bff">Build it and….Who Will Come?!</a> was originally published in <a href="https://medium.com/sense-and-signal">Sense and Signal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Provotype: Digging Deeply into the Problem Space]]></title>
            <link>https://medium.com/sense-and-signal/provotype-digging-deeply-into-the-problem-space-7665d86e4707?source=rss----34ad259549c3---4</link>
            <guid isPermaLink="false">https://medium.com/p/7665d86e4707</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jodah Jensen]]></dc:creator>
            <pubDate>Thu, 20 Feb 2025 06:44:20 GMT</pubDate>
            <atom:updated>2025-02-20T06:44:20.524Z</atom:updated>
            <content:encoded><![CDATA[<h4>Bridging the Gap Between Business Goals and Solution Hypothesis</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wuC7VEGPZbFRMneRA4Np0g.jpeg" /></figure><p><strong>Provotype!</strong> No, that’s not a typo. It may look like “Prototype” with a minor spelling adjustment, but in function, it’s an entirely different beast. Right now, it’s not a widely adopted concept — but give it time. I’m willing to bet more of you will be using it in your product development practices soon enough.</p><p>So, what is it? Think of it this way: a <strong>shovel</strong> is to a Provotype as a <strong>hammer</strong> is to a Prototype. While a prototype is built to test a specific solution, a Provotype exists to <strong>dig or</strong> <strong>stir things up</strong> — to provoke reactions, challenge assumptions, and surface insights before you even have a solid hypothesis. It’s not about refining an idea; it’s about <strong>finding the right problem to solve in the first place</strong>. Provotypes expand, Prototypes Narrow.</p><p>In this article I will discuss …</p><ol><li>Brief Review and limitations of the <em>Prototype</em></li><li>The Idea behind the <em>“Provotype”</em></li><li>How to use a “<em>Provotype”</em></li></ol><p>So without further ado…</p><h3>Prototypes: Better than Guessing</h3><p>A prototype is the first tangible step in bringing an idea to life — a quick, scrappy version built with whatever tools are available, whether that’s duct tape and code or a polished mockup in a design tool. Its purpose isn’t perfection; it’s to answer a critical question: are we on the right track? By keeping risk and resource investment low, prototypes serve as powerful tools for validation before full-scale execution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4QxBao9FbkRwwsgAfefxsg.png" /></figure><h4>Validating Assumptions Before Committing Resources</h4><p>At its core, a well-executed prototype is a <strong>low-cost, low-effort experiment</strong> that helps teams test their assumptions before making big commitments. Whether it’s validating a high-level value proposition or fine-tuning UI and interaction design, prototypes provide a practical way to gauge how well a solution addresses a problem. By building and testing prototypes, teams establish reference points — seeing how close or far they are from their target — all at a fraction of the cost of developing the full product.</p><h4>Gathering Real Feedback from Users and Stakeholders</h4><p>Prototypes are most often used to collect <strong>real-world feedback</strong> from users and stakeholders. An idea, no matter how well-articulated, remains abstract until people can interact with it. Even a rough prototype gives them something tangible to react to, and their responses provide insights far more valuable than theoretical discussions. This direct engagement helps refine the concept and steer it in the right direction.</p><h4>Reducing Risk and Build Confidence</h4><p>By surfacing potential flaws, usability issues, or technical challenges early, prototyping helps mitigate costly mistakes. It minimizes uncertainty, confirms what works, and de-risks the development process. Just as importantly, it builds momentum — giving teams the confidence that they are on the right path before investing heavily in full-scale execution.</p><h4>Course Correction Machine</h4><p>Every team hopes to nail it on the first try, but anyone with experience knows that’s rarely the case — especially with complex challenges. More often than not, a prototype will highlight what works while revealing areas that need improvement. The key is to learn from the feedback and refine the approach. How the team responds will depend on various factors, but some best practices include:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8m_GBZYKLYgqPrLdoyTcVw.png" /></figure><ul><li><strong>Prioritize Issues</strong>: Identify the most critical issues that impact the user experience and functionality. Prioritize these for immediate attention.</li><li><strong>Categorize Feedback</strong>: Group similar feedback to spot common themes or patterns. This helps in understanding recurring problems and areas that need improvement.</li><li><strong>User Interviews and Surveys</strong>: Follow up with users who provided feedback to gain deeper insights. Conducting interviews or surveys can clarify specific issues and gather more detailed suggestions.</li><li><strong>Celebrate Successes</strong>: Acknowledge and celebrate the areas where the prototype received positive feedback. This boosts team morale and reinforces what works well.</li><li><strong>Set Clear Goals</strong>: Define clear goals and objectives for the next iteration based on the feedback received. This helps the team stay focused and aligned on what needs to be achieved.</li></ul><p>All of this is great — but how did you arrive at this hypothesis in the first place? There’s a significant gap between identifying a business goal and landing on a solution hypothesis. While there are many established methods to bridge this gap in product and service development, I’ve often found that prototypes are overloaded, expected to do too much. When this happens, they risk becoming a catch-all tool rather than serving their true purpose.</p><h4>Misunderstanding, Research Depth, and the Risk of Over-Reliance on Prototypes</h4><p>Prototypes are invaluable tools, but they come with risks — particularly when they become a substitute for deeper research. One common pitfall is <strong>misinterpreting a prototype as the final product</strong>. Users may see a polished prototype and assume it’s nearly complete, focusing their feedback on surface-level design details rather than core functionality or viability. This can lead teams to refine elements that don’t truly matter instead of uncovering fundamental issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y17A1WVtBhe9UpBdzraIDg.png" /></figure><p>Conversely, a prototype that’s too rough can skew feedback in the opposite direction. If users struggle to see past its unfinished state, they may fixate on minor flaws rather than engaging with the bigger idea. Instead of validating the concept, teams end up gathering feedback that merely reflects the limitations of the prototype itself.</p><p>Compounding these challenges is the tendency to use prototypes as a <strong>shortcut to avoid deeper exploration</strong>. The specificity of a prototype dictates the type of feedback teams receive — if it’s too narrow, it can lock teams into a limited perspective, preventing them from questioning broader assumptions. This can be useful when refining a well-defined value proposition, but risky when fundamental questions remain unanswered.</p><p>Most of these issues can be mitigated by setting clear expectations with users — explaining what’s being tested and why. However, the very act of prototyping shapes the research approach, influencing the depth and richness of insights gathered. Prototypes are fantastic at narrowing your efforts, not exapnding. This is where the Provotype Comes into the picture.</p><h3>Enter Provotype</h3><p>At first look a Provotypes can look much like a prototype, and in fact in some situations one persons prototype might be another&#39;s provotype. What really sets the two apart is the intention behind them . This intention will often then result in something quite different from your stabndrard prototype. In a nutshell…</p><ul><li>A <strong>prototype</strong> is designed to test and refine a solution by validating assumptions and improving functionality.</li><li>A <strong>provotype</strong> is meant to provoke discussion, challenge assumptions, and spark new thinking rather than validate an existing idea.</li></ul><p>That’s right — <strong>provoke</strong> is the key word here. A <strong>provotype</strong> isn’t just about finding answers to existing questions; it’s true power lies in its ability to uncovering new questions that haven’t been asked yet. This distinction is crucial because true innovation often emerges in the space between what we think we know and what we’ve yet to explore.</p><p>By deliberately challenging assumptions and pushing boundaries, provotypes help product teams break out of conventional thinking. There absolutly no intent to validate anything with a provotype, rather they open up unexpected avenues for exploration — leading to novel insights, unrecognized pain points, and entirely new opportunities for problem-solving. As I said, the Provotype is a shovel of discovery.</p><h3><strong>Fidelity &amp; Realism</strong></h3><ul><li>A <strong>prototype</strong> often aims for realism, even if it’s low-fidelity, to simulate a potential final product.</li><li>A <strong>provotype</strong> can be deliberately exaggerated, unrealistic, or even absurd to push boundaries and expose hidden biases or gaps in thinking.</li></ul><p>These key differences are where the rubber meets the road. When testing a <strong>prototype</strong>, it’s crucial to ensure that the right elements are in place — both to avoid confusing participants and to accurately validate or invalidate your hypothesis. If critical aspects are misaligned or unclear, the feedback you gather may be misleading, ultimately compromising your data.</p><p>With <strong>provotypes</strong>, fidelity is less of a concern. Instead of fine-tuning details for validation, the goal is to provoke participants into thinking more deeply about a problem. A provotype serves as a <strong>conversation piece</strong>, sparking discussions and uncovering new perspectives within the problem space you’re exploring. It’s not about proving a solution — it’s about expanding the way people think about the challenge itself. Its the <a href="https://en.wikipedia.org/wiki/Rorschach_test">Rorschach test</a> of UX.</p><h4>Designing for Conversation, Not Just Outcomes</h4><p>So what does this mean in practical terms? It means that what you show in a prototype should <strong>serve the conversation</strong> rather than aiming for a specific implementation outcome.</p><p>Let’s say you’re exploring a particular set of functionalities on a page — functions A, B, C, D, F, and G. Your goal isn’t to test how best to implement these functions but rather to understand how participants perceive the set as a whole and whether it even makes sense.</p><p>In a <strong>prototype</strong>, you might organize these functions in a dropdown menu — perhaps because that’s how they would likely appear in a real product. But in a <strong>provotype</strong>, this wouldn’t make sense. Your objective isn’t to refine the execution but to challenge and explore the value of the set itself.</p><p>In this case, I might lay out all the functions as <strong>radio buttons or checkboxes</strong>, making them visible at once. This approach reduces the cognitive load of having to remember what’s inside a dropdown, allowing for a more effective discussion about the necessity, arrangement, and completeness of the set. The focus shifts from “How should we implement this?” to “Does this collection of functions make sense at all?”</p><h4>Provoke is the operative word</h4><p>I want to stress here the Provotypes are intended to provoke. This means you can actually insert “wrong”stuff into it.</p><p>Entering what seems like <strong>wrong</strong> information or design data into a provotype can be incredibly effective because it forces reactions, uncovers assumptions, and sparks deeper discussions. When something feels “off,” participants are more likely to question it, articulate why it doesn’t work, and, in doing so, reveal insights that might not have surfaced with a more polished, expected design.</p><p>For example, if a provotype deliberately includes an unnecessary or missing function, users may instinctively correct it — revealing what they truly find valuable. This approach shifts the focus from <strong>validating a solution</strong> to <strong>exploring possibilities</strong>, making it a powerful tool for early-stage innovation.</p><h3><strong>Intended Outcome</strong></h3><p>So as a quick reminder:</p><ul><li>A <strong>prototype</strong> is used to refine and de-risk a concept before further development.</li><li>A <strong>provotype</strong> is used to <strong>provoke reactions</strong>, inspire fresh ideas, and challenge conventional wisdom — often leading to unexpected insights rather than direct iteration.</li></ul><p>Provotype work yields many valuable outcomes, but the two most important ones I’ve found are improved <strong>problem definition</strong> and <strong>better team alignment</strong>. By engaging in provotyping, your team increases the likelihood of not only solving the right problem but solving it in the right way. This process opens up opportunities for innovation and disruption within the problem space, as it provides a deeper, more accurate understanding of the challenges at hand.</p><p>Before I leave you the following is a short list of things to think about as you jump into the world of Provotypes:</p><h4><strong>1. Intention Over Execution</strong></h4><ul><li>The goal is to provoke reactions and uncover insights, not to refine implementation.</li><li>Focus on <strong>exploring the problem space</strong> rather than perfecting a solution.</li></ul><h4>2<strong>. Visibility &amp; Cognitive Load</strong></h4><ul><li>Present information in a way that makes it easy to process at a glance.</li><li>Avoid hiding key elements that will help explore a naritive</li></ul><h4>3. Challenging Assumptions</h4><ul><li>Introduce <strong>“wrong” or unexpected data</strong> to surface hidden assumptions.</li><li>Force users to question <strong>why</strong> something works or doesn’t.</li></ul><h4>4. Encouraging Open-Ended Discussion</h4><ul><li>Design the provotype to invite feedback, not just validation.</li><li>Use ambiguous or incomplete elements to see how users fill in the gaps.</li></ul><h4>5. Low-Fidelity, High Impact</h4><ul><li>Keep it simple — provotypes should be quick to build and modify.</li><li>Prioritize <strong>learning over polish</strong> to allow rapid iteration.</li></ul><h4>6. Testing the Right Thing</h4><ul><li>Ensure you’re exploring the <strong>problem itself</strong>, not necessarily usability or UI. (<em>This does not mean avoid these discussions. If this stuff comes up , by all means lean into it.)</em></li><li>Frame questions around <strong>what should exist</strong> rather than how to execute it.</li></ul><h4>7. Set Expectations</h4><ul><li>Absolutley set the expactions of the effort. Let the participant know what they are getting into and how they should approach the session.</li></ul><p>Ta dah! We are done. If you have any questions by all means let me know. I would love to hear your thoughts on the matter.</p><p>Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7665d86e4707" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sense-and-signal/provotype-digging-deeply-into-the-problem-space-7665d86e4707">Provotype: Digging Deeply into the Problem Space</a> was originally published in <a href="https://medium.com/sense-and-signal">Sense and Signal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feature-Creature Part 1]]></title>
            <link>https://medium.com/sense-and-signal/feature-creature-part-1-e77b1ca7fd7f?source=rss----34ad259549c3---4</link>
            <guid isPermaLink="false">https://medium.com/p/e77b1ca7fd7f</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[features]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jodah Jensen]]></dc:creator>
            <pubDate>Sat, 15 Feb 2025 22:50:04 GMT</pubDate>
            <atom:updated>2024-12-05T07:03:17.419Z</atom:updated>
            <content:encoded><![CDATA[<h4>Don’t Let Your Product Become a Monster?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DZkMvyY-i_ZyADXjIY6Agg.jpeg" /></figure><p>A few years back, there was this movie called <em>Wonder Boys.</em> It follows Grady Tripp, a washed-up writer and professor caught in a chaotic weekend involving a stolen manuscript, a troubled student, and a secret affair with his boss’s wife. It’s a fun, fast-paced movie starring Michael Douglas, and I highly recommend it — but that’s beside the point.</p><p>In the film, Grady lugs around a massive, unfinished manuscript that he seems hesitant, maybe even afraid, to publish. One standout scene captures this perfectly: after sharing the manuscript with a student he once had a fling with, they end up alone, and he waits, uneasy, to hear her thoughts. After a bit of back and forth, she finally says, “Didn’t you tell us in class that every story is a series of choices? Well… this feels like you never made any choices.” I love that. <a href="https://youtu.be/I8PLjzTzy08?si=AGRKl3lyuqfr1w0s">here is a link to that scene.</a></p><p>The world of product creation is not unlike the world of Authorship; Like a book its important to have a clear theme otherwise your customer wont be able to follow you or your products vision. Whether or not your customer sees the value of your service or product in their lives has everything to do with the choices made (and unfortunately often not made) by you and your team.</p><h3>The Feature-Creature</h3><p>What are Feature-Creatures? “Feature-Creatures” are a byproduct of a product or feature-set that has been stitched together from various, often unrelated ideas, added in response to different stakeholder demands or competitive pressures without a clear purpose or cohesive design. Much like Frankenstein’s monster, it’s made up of disparate parts that may serve individual requests but don’t align well with the product’s core functionality or user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*fnq5aGPMc9XdaVJVjbweiw.png" /></figure><p>Feature-Creatures typically emerge as a result of feature creep. They combine elements that may sound appealing individually but, when combined, create a confusing, cluttered, or bloated product experience. Instead of enhancing the product, each feature disrupts the narrative, fragments the experience, decreases usability, and slows down performance. This introduces unnecessary complexity, ultimately diluting the product’s value and focus.</p><h3>Feature Count ≠ Feature Creep</h3><p>Before moving on, it’s important to note that the volume of features (or feature count) doesn’t necessarily lead to feature creep, resulting in a Feature-Creature situation. These are related but not exclusively tied to one another. This complexity and massive feature set align with the experts’ training and mental models. A modern jet airliner cockpit exemplifies handling complexity effectively. While the sheer number of controls might seem overwhelming, a pilot’s training makes these interfaces highly usable and functional. Attempting to simplify a cockpit interface to the level of Facebook’s simplicity would almost certainly lead to catastrophic consequences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GxMxi9NOkCjuCBltaju39g.png" /></figure><p>There’s an interesting paradox worth noting when it comes to the number of features a product offers. Let’s be clear: feature count doesn’t necessarily equate to feature creep, but it does have a strong correlation with customer adoption. A <a href="https://hbr.org/2006/02/defeating-feature-fatigue">marketing study </a>conducted a few years ago revealed a statistically significant relationship between the number of features and the customer’s perception of value. Simply put, the more features a product had, the more valuable it seemed in the initial evaluation process — especially in professional-grade products, where expertise is required to unlock their full potential.</p><p><strong>But here’s the twist: </strong>once customers actually used the product, that correlation flipped. Suddenly, the abundance of features didn’t look like added value — it looked like a problem. Products with too many features began to feel overly complicated, and their perceived value dropped.</p><p>This creates a dilemma: the very thing that attracts customers initially is often what drives them away later. I’m not diving into this “feature count paradox” here, but it’s worth mentioning because it’s easy to confuse with what I’m trying to address in this article. For now, let’s stick a pin in it and move on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*mFshCGPhV0R0eKivbDBDPg.png" /></figure><h3>“Feature Creatures” Eat Brand Identity for Lunch….and Dinner</h3><p>Again, a Feature Creature is not a product with <em>too many</em> bells and whistles (remember, the more the better in certain circumstances) , but rather one that has lost its narrative coherence due to excessive additions. It is characterized by a haphazard collection of functionalities that, while possibly innovative in isolation, fail to integrate seamlessly with the core product vision or user experience. This lack of coherence not only confuses users but can also significantly harm the brand’s reputation by portraying it as unfocused and inconsistent.</p><p>Your Feature Creature will have the following negative impacts on your brand:</p><h4><strong>Dilution</strong></h4><p>Your Feature Creature can blur your brands core purpose, making it difficult for customers to associate the brand with a specific value. This often leads to confusion about the brand’s identity and undermines its unique market positioning, risking customer loyalty. Harvard Business School Online highlights that a clear value proposition is crucial for reinforcing brand identity and differentiating from competitors. You can explore this further in their discussion of effective value proposition strategies here​. <a href="https://online.hbs.edu/blog/post/creating-a-value-proposition">Harvard Business School Online</a></p><h4><strong>Negative</strong> <strong>Perception</strong></h4><p>Overly complex products frustrate users and harm usability, tarnishing the brand’s reputation. Feature bloat can make it seem like the brand values quantity over quality, alienating customers who prefer simplicity and efficiency. Negative user experiences often lead to reduced trust, less advocacy, and potential loss of loyalty. According to UX Matters, feature bloat overwhelms users, diminishes satisfaction, and negatively impacts the brand’s image. You can explore more insights on this topic <a href="https://www.uxmatters.com/mt/archives/2014/03/beware-of-feature-overload-a-case-study.php">here</a>​</p><h4><strong>Erosion of Personal Connection</strong></h4><p>When a brand strays from its core narrative or adds unnecessary features, it risks alienating its audience. Customers may feel the brand no longer understands or prioritizes their needs, leading to a loss of trust. This emotional disconnect weakens loyalty, reducing long-term engagement and advocacy.</p><h3>Your Feature Creature will Torture your Customers</h3><p>Your product is a story, a narative that must to resonate with your customers needs. To think about it in another way, your customers are trying to get a job done and they are goong to hire your product to help. Thats the perspective Anthony Ulwick takes with his ODI or <a href="https://medium.com/envato/a-step-by-step-guide-to-using-outcome-driven-innovation-odi-for-a-new-product-ded320f49acb">Outcome Driven Innovation framework</a>. Anything you add to your product that does not directly or indirectly help your customer get their job done will be clutter or noise.</p><p>Thats exactly what the Feature Creature adds, <strong>noise</strong>…and noise is friction, and friction is abandonment, and abandonment is market loss.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*ePtxDiiNwplLctKFW0WN_w.png" /></figure><p>The following are 3 ways your Feature Creature will torture your customer:</p><h4>Its Simply Less Usable</h4><p>The Feature Creature, a monstrous amalgamation of unchecked ambition and misguided design, lurks in the shadows of product design. Its insatiable appetite for new tabs, redundant menus, and tools no one asked for transforms sleek, purposeful interfaces into unwieldy labyrinths. Users, instead of gliding through intuitive workflows, stumble into a tangle of unnecessary complexity. Frustration builds as they waste time hunting for essentials, only to be met with errors and dead ends.</p><p>The Nielsen Norman Group warns against the Creature’s chaos, emphasizing that simplicity is the key to usability, while complexity drives users away. The UX Collective describes the havoc it wreaks, showing how unnecessary features turn streamlined designs into bloated, disjointed experiences. Left unchecked, the Feature Creature doesn’t just inconvenience users — it devours the very soul of a product.</p><h4>Cognitive Overload</h4><p>Navigating a product with too many unrelated features feels like being handed a map where every path competes for attention but leads nowhere meaningful. Each option demands mental energy to process, categorize, and decide whether it’s relevant, steadily increasing the cognitive load on users. Instead of streamlining their tasks, the experience slows them down, causing decision fatigue and frustration.</p><p>Barry Schwartz’s <em>The Paradox of Choice</em> captures this phenomenon, illustrating how an abundance of options can overwhelm rather than empower. Similarly, the Interaction Design Foundation highlights how excessive features create cognitive strain, undermining the product’s usability and leaving users disengaged. Overcomplicated designs don’t just slow progress — they make it harder for users to see the value of the product itself.</p><h4>Frustration</h4><p>When users are forced to navigate a bloated product, struggling to understand its complexities, frustration quickly sets in. This disconnect isn’t just a passing annoyance — it alienates users, making them feel that the product — and the brand behind it — doesn’t prioritize their needs or provide a solution they can rely on. Over time, these negative feelings erode trust and emotional connection, leaving users disengaged and disillusioned.</p><p>Research from Forrester underscores how frustration directly impacts customer satisfaction, loyalty, and long-term brand perception. When a product feels unintuitive or unresponsive to user needs, the emotional bond with the brand weakens, potentially leading to abandonment.</p><h3>This is the end of Part 1</h3><p>Alright, let’s break this down…</p><p>So, there’s this idea called the “Feature Creature.” Imagine your product is like a movie script. If the story doesn’t make sense, people won’t follow along, right? Similarly, if your product gets loaded with too many random features to please everyone, it turns into a confusing mess. These scattered additions can make the product hard to use and dilute its value.</p><p>Now, just because a product has a lot of features doesn’t mean it’s fallen into feature creep. For example, complex tools used by experts might have tons of features that are necessary and make sense. Think about a jet airliner’s cockpit — it’s loaded with controls, but pilots are trained to use them efficiently.</p><p>However, there’s a catch. More features might initially attract customers because they seem valuable, but once they start using the product, all those extras can become overwhelming and frustrating. This can make them feel the brand doesn’t really understand their needs, leading to a loss of trust and loyalty. Essentially, your product should have a clear vision that aligns with what your customers need, avoiding unnecessary complexity to maintain their trust and satisfaction.</p><p>In part 2 I will discuss a bit more about how Feature Creatures are created and explore some process and tools to thwart these foul beasts</p><p>See you soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e77b1ca7fd7f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sense-and-signal/feature-creature-part-1-e77b1ca7fd7f">Feature-Creature Part 1</a> was originally published in <a href="https://medium.com/sense-and-signal">Sense and Signal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Many Faces of Design Thinking]]></title>
            <link>https://medium.com/sense-and-signal/the-many-faces-of-design-thinking-01cc54710374?source=rss----34ad259549c3---4</link>
            <guid isPermaLink="false">https://medium.com/p/01cc54710374</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jodah Jensen]]></dc:creator>
            <pubDate>Mon, 06 Jan 2025 17:32:07 GMT</pubDate>
            <atom:updated>2024-12-11T00:00:39.654Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uVRUKZ5TsCBltQruJr0mtQ.png" /></figure><p>Have you heard of Design Thinking?</p><p>I ask that with a slight smile, because I’d be shocked if you haven’t at least heard it mentioned somewhere, even if the specifics are a bit of a blur. I personally see at least one post about it in my LinkedIn feed every single day — people can’t stop talking about it, and for good reason. But just in case it’s slipped under your radar, or you’ve heard the term but are still unclear on what it really means, let me help. Design Thinking is far more than just a buzzword — it’s a proven approach to problem-solving and innovation. It’s a methodology that has transformed the way companies create products, services, and experiences. And when done right, it can be a game-changer.</p><p>Here are some definitions from some reputable sources that might help shed some light on the subject…</p><ul><li>Interaction Design Foundation (IxDF): “Design thinking is a non-linear, iterative process that teams use to understand users, challenge assumptions, redefine problems, and create innovative solutions to prototype and test. It is most useful to tackle ill-defined or unknown problems and involves five phases: Empathize, Define, Ideate, Prototype, and Test1.”</li><li>BYU Design Review: “Design thinking is both a tool set and a mindset. It can be described as a step-by-step process with design activities or as a general pattern of thought3.”</li></ul><p>If you’re wondering about the big players, here’s the answer: they’re all in on Design Thinking. Google’s innovation machine runs on it — empathy, expansive thinking, and experimentation are their secret ingredients. The method blends creativity with structured chaos to solve complex problems.</p><p>Stanford, where it all began, calls it “creative problem solving” — rooted in deep empathy, not sympathy. It’s about understanding users, defining the problem, brainstorming solutions, prototyping fast, and testing relentlessly.</p><p>And then there’s Jeremy Utley from Stanford’s <a href="http://d.school/">d.school</a>, who boils it down perfectly: Design Thinking is “a way to come up with ideas and see if they’re any good.” No frills, just results.</p><h3>One Design Thinking; Many Faces</h3><p>If you take a quick look, you’ll see that there’s a growing chorus of schools, consultancies, and organizations all touting the same gospel of Design Thinking. And the best part? They all agree. Perfect harmony. No debate. No nuance. No room for disagreement. It’s as if the world has collectively stumbled upon the one true way to approach problem-solving. So, that’s it. Case closed. Move along. Nothing more to see here. See you in the next piece, folks.</p><p>Wait, I have a bridge to sell you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*y0M7aKc7b-0zBfY2" /></figure><p>No, and, fortunately for us, they’ve all approached the same problem from slightly different angles. “Design Thinking” might be ubiquitous in the world of software and product development, but there’s no single flavor that dominates. It’s not like there’s a one-size-fits-all recipe everyone’s following. Each school, each organization, has taken the fundamental principles and reworked them to fit their own needs, to solve the specific challenges they’re facing.</p><p>Lets take a quick stroll through some of the top Design Thinking Contenders….</p><h3>Stanford d.school’s Design (My Goto Flavor)</h3><p>Standfords <a href="http://d.school/">d.school</a> is the unsung guru of UX and interaction design — quietly pushing the boundaries of Design Thinking while the rest of us fumble through the process. For years, they’ve hammered home the same five-step mantra: Empathize, Define, Ideate, Prototype, and Test, with a reminder to iterate because, of course, nothing ever truly ends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*cQo_uWhwGRBrpleM" /></figure><h3>IDEO’s Human-Centered Design Process</h3><p>IDEO is the kind of company that thrives on chaos — where creative minds collide, experiment, and fail fast. It’s a place where “design thinking” is a method of bending the world to your will, one wild idea at a time. In the end, their secret isn’t just about solving problems — it’s about reshaping what we think of as a problem in the first place. They have distilled their thinking down to three stages : Inspiration, Ideation, and Implementation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*r2XRa1TN30k-UjNW" /></figure><h3>Double Diamond</h3><p>I don’t lean on this model as much as the Stanford version, but I’ve got a soft spot for it — mainly because of the way it visualizes the process. It’s got this neat trick where it emphasizes divergent and convergent thinking, forcing people to step back and approach a problem from all angles before narrowing in. The whole thing is broken into four stages: Discover, Define, Develop, and Deliver. Simple, clean, and deceptively brilliant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*rU08L4-2Tat1-Pmz" /></figure><p>Double Diamond Image</p><h3>LUMA System of Innovation</h3><p>LUMA’s System of Innovation takes the lofty concept of Design Thinking and grounds it in a pragmatic, actionable framework. By organizing 36 human-centered methods into three simple categories — Looking for insights through observation, Understanding them with analysis, and Making solutions through creativity — it transforms problem solving into a process anyone can follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*zcR5Eq4BVkD65XVf" /></figure><h3>Google Design Sprint</h3><p>While Google didn’t invent design thinking or its core principles, they adapted these ideas into the Design Sprint — a time-boxed, structured process for solving problems and testing ideas in just five days. The methodology became highly influential and has been widely adopted outside of Google after the release of Jake Knapp’s book, Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days (2016).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*0t2PLNH-klqvN00T" /></figure><h3>IBM Design Thinking</h3><p>IBM’s Enterprise Design Thinking approach tailors traditional design thinking principles to address the complexities of large organizations, focusing on collaboration, scalability, and business outcomes. It emphasizes continuous alignment among stakeholders, clear objectives, and user-centered innovation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*qjtBk7G1_YmgTG4z" /></figure><p>IBM’s has a unique take on design thinking by introducing some key distinctions that they leverage throughout their Design Thinking process. They swap vague problem statements for Hills — crisp, user-focused objectives that anchor the process. Sponsor Users, real people involved throughout, keep solutions honest with constant feedback. Regular Playbacks — team updates to stakeholders — ensure alignment and transparency. The Looping Framework lets teams circle back as insights evolve, while the Scalable Framework blends Agile and design thinking, enabling even global teams to innovate cohesively. It’s design thinking, IBM-style: structured, inclusive, and built for scale.</p><h3>Whose Kung Fu is the Best</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*WFsZvtIAlaR5Z8rV" /></figure><p>After combing through the heavyweights of Design Thinking — the classic Stanford model, IBM’s enterprise machine, and Google’s rapid-fire Design Sprint — you might be itching for the big reveal: Which one’s the champ? Which reigns supreme? Is there a best version? Well, here’s the twist: there isn’t.</p><p>These models aren’t rivals in some design gladiator arena (product development world). They don’t compete — they adapt. Over time, each has been shaped by the needs of its audience. For some, it’s about unlocking creativity; for others, it’s a framework to teach students or synchronize sprawling teams. For UX designers, it’s a user-focused playbook. The secret sauce? Empathy, ideation, and iteration, flexed and reshaped to fit whatever challenge is at hand. It’s not about supremacy — it’s about finding the right tool for the job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*L2zb2d6fs-noF-T6" /></figure><h3>Empathize, Ideate, Iterate….Rinse and Repeat…..Empathize, Ideate, Iterate….</h3><p>Sure, some might slice it a bit differently, but let’s be honest — most of us would land in roughly the same place. At its core, every Design Thinking model is just trying to guide you through an iterative process: dive deep into empathy, generate a flurry of ideas, and refine until something sticks. The variations aren’t a sign of weakness; in fact, they’re proof of the method’s strength. Despite the tweaks and branding spins, they all stick to the same basic sequence — Empathize, Ideate, Iterate. That consistency is what makes the whole thing work.</p><h3>Empathize</h3><p>Empathy is crucial in creating a product because it ensures the solution truly meets the needs, desires, and pain points of the users. By understanding users on a deep level — beyond just their surface-level needs — teams can design products that are intuitive, meaningful, and valuable. Empathy helps to avoid assumptions, guiding the team to focus on what users truly care about, leading to better user experience and higher product adoption. It’s not just about solving a problem, but solving the right problem in a way that resonates with the people who will use the product.</p><h3>Ideate</h3><p>Ideation is a critical phase in product creation because it fosters creativity and exploration. During ideation, teams are encouraged to think broadly and generate as many ideas as possible, no matter how unconventional or impractical they might seem at first. This process is important because it opens the door to innovative solutions that might not emerge from linear or constrained thinking. By ideating freely, teams uncover a variety of potential approaches, allowing them to assess the strengths and weaknesses of each. The goal is not to settle on the perfect idea immediately, but to build a diverse pool of options that can later be refined and tested, ensuring the team explores every possible way to solve the user’s problem.</p><h3>Iterate</h3><p>Iteration is like testing a paper boat in the water as a kid. You make the boat, set it on the surface, and watch it float, only to quickly realize it might be too heavy on one side or sink in the middle. So, you adjust — fold a corner differently, add a little more paper, or trim another part. The boat might not sail perfectly on the first try, but each time you test it, you learn something new and refine it. This process of prototyping, testing, and tweaking mirrors how ideas evolve in product development. With each cycle, the product gets closer to what’s needed, ensuring it works well in the real world. Like adjusting a boat’s design after each test, iteration keeps teams from getting stuck in the pursuit of perfection and helps them adapt to new challenges and insights. Through this continuous refinement, products become more practical, functional, and aligned with what users actually need.</p><h3>Mapping Googles Design Sprints</h3><p>Some of you who are familiar with Design Sprints might already be ready to point out the differences. Yes, my version might not match exactly with your interpretation of the process. Design Sprints have evolved over time, and today there are countless variations, each tweaking the order or wording to emphasize specific stages or ideas. Nothing about this is set in stone. But for the sake of clarity and moving forward, I’m sticking with the approach outlined here in the article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*V55CNhiUzqae1J6C" /></figure><h3>1) Empathize = Understand or Map</h3><p>Design Sprints start with an Understand phase. The Understand phase of a design sprint is about building a shared knowledge base among the team to ensure everyone grasps the problem’s scope, the users’ needs, and the context in which solutions will live. Its also called the Mapping phase because this is exactly what you and your team are doing when gathering insights from user research, expert interviews, and existing data to deeply explore the “why” behind the problem. This phase serves empathy by immersing the team in the users’ experiences, uncovering their challenges, motivations, and pain points, and ensuring that every decision moving forward is rooted in genuine understanding.</p><p>Note: Empathizing is crucial in product creation decisions because it ensures the solutions developed are genuinely tailored to meet users’ real needs and challenges, ultimately leading to more effective and user-friendly products. Without this knowledge you can very easily find yourself fixing problems that do not exist.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/0*MGDm7GH_0txTN8Yx" /></figure><h3>2) Ideate = Diverge or Sketch</h3><p>Once the team has a solid understanding of the customer’s problem, as well as their hopes, desires, and goals, it’s time to move into the ideation phase. In the Sketch phase of Design Thinking, participants quickly generate multiple ideas, often through low-fidelity sketches. The aim here is to explore a wide range of potential solutions, without getting bogged down in perfection. It’s all about divergent thinking, where creativity is the priority over practicality. The team sketches individually, each bringing their own perspective to the table. In the end, what you get is a collection of rough ideas to refine and test later — a foundation for moving forward.</p><h3>3) Iterate = Decide , Prototype, Validate</h3><p>At some point in the ideation process, you’ll likely have a number of promising ideas, each addressing the problem in its own way. In a design sprint, there are specific techniques to handle this, but ultimately, the team needs to settle on one concept to move forward with. This is where Iteration comes in. Google’s approach to iteration begins by having the team decide which concept to focus on (after all the heavy lifting has already been done). From there, they create a prototype of that idea, at whatever level of fidelity makes sense, and then rapidly test it to validate the concept’s hypothesis.</p><h3>No One Size Fits All</h3><p>In the world of Design Thinking, there’s no one-size-fits-all approach. From Stanford’s foundational model to IBM’s enterprise-focused version, each iteration adapts the core principles to fit specific needs and challenges. Despite the variations, all models share the same fundamental sequence: Empathize, Ideate, and Iterate. This iterative cycle ensures that products and solutions are built on a deep understanding of users’ needs, followed by creative exploration and continuous refinement. Whether you’re mapping a customer’s pain points, sketching out new ideas, or testing prototypes, the process remains rooted in the idea that empathy, creativity, and testing are key to creating effective, user-centered solutions. The true power of Design Thinking lies not in any one version, but in the flexibility to adapt it to whatever problem you’re trying to solve.</p><p>Until next time…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=01cc54710374" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sense-and-signal/the-many-faces-of-design-thinking-01cc54710374">The Many Faces of Design Thinking</a> was originally published in <a href="https://medium.com/sense-and-signal">Sense and Signal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Thinking Perils & Pitfalls]]></title>
            <link>https://medium.com/sense-and-signal/design-thinking-perils-pitfalls-dfe56aff7064?source=rss----34ad259549c3---4</link>
            <guid isPermaLink="false">https://medium.com/p/dfe56aff7064</guid>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Jodah Jensen]]></dc:creator>
            <pubDate>Thu, 26 Dec 2024 23:20:45 GMT</pubDate>
            <atom:updated>2025-01-06T19:07:55.414Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-IPYT7AfqrubAlyqDP48SA.png" /></figure><h3>Perils &amp; Pitfalls of Empathy in Design Thinking</h3><h4>Evil Traps That Can Thwart Problem Discovery Adventures</h4><p>Last article I wrote, I dipped my toes into the foamy waters of Design Thinking, writing a quick piece aimed at untangling its many flavors — IDEO, Stanford d.school, and the like. If it left you wanting more depth, my apologies. That would be a task better suited for a book or at least a meaty white paper. Plus, there are already so many good sources out there on the mechanics of Design Thinking, some of which I will provide links to at the end of this. No, my intent was simpler: to demystify the crowded landscape of Design Thinking and distill it down to its essence — Empathy, Ideation, and Iteration. You don’t need to have read that article to follow along here, but if curiosity gets the better of you, here’s the link to <a href="https://medium.com/@jodahjensen/the-many-faces-of-design-thinking-01cc54710374">The Many Faces of Design Thinking</a>.</p><p>Moving on…it’s one thing to grasp the mechanics of Design Thinking, to map out the process and have the confidence to steer a product through its prescribed phases. It’s another thing entirely to have the insight to know how to avoid the <strong>Perils and Pitfalls of Design Thinking </strong>— those hidden traps that can quietly undermine its promise if you’re not paying close attention.</p><h4>Failing Forward: The Cost of Passive Participation in Design Thinking</h4><p>With so much hinging on each phase, Design Thinking is system that truly demands full engagement from every participant, every step of the way. Each phase requires its own mindset — its own hat, if you will — and teams that fail to shift their thinking accordingly are setting themselves up for reduced results at best, and outright failure at worst. The process isn’t some magic power saw that does the hard work for you; it’s more like a blueprint, guiding your efforts and ensuring they’re pointed in the right direction. <strong>But without active, intentional participation, the whole thing can feel like a costly exercise in going through the motions.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Wd5nANno79NKoDYh5FdaQ.png" /></figure><p>In my experience, I’ve found that the Empathy, Ideate, and Iterate phases each come with their own hidden traps — pitfalls that aren’t always solved by the prescribed steps of any given Design Thinking system. These dangers, often silent and unnoticed, can derail even the most well-intentioned efforts, stemming not from the process itself but from the dynamics and culture of the team. The solution, then, isn’t necessarily in the Design Thinking framework but in the hands of the leader — someone capable of navigating the team’s unique challenges and guiding them through the minefields.</p><p>In this first of 3 articles I will discuss where the early Empathy stages can go wrong. I call this pitfall…</p><h3>the Swamp of Misunderstanding</h3><p>The Swamp of Misunderstanding is where well-intentioned teams often find themselves sinking before they’ve even begun. Empathizing in a business context is a notoriously tricky endeavor, and not without reason. Organizations thrive on movement — producing, creating, delivering, always pushing the metaphoric ball forward. Results are the currency of business, and anything that doesn’t immediately translate into action can feel like a squandered investment. It’s not that empathy is outright dismissed; it’s that, when compared to tangible phases like building or shipping, it feels like the soft, squishy middle — important in theory, indulgent in practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C1bUi-k5pAV6l56fq2sdkw.png" /></figure><p>And so, teams rush through it — or worse, skip it altogether. They assure themselves they already know the customer, the problem, the solution. After all, haven’t they been thinking about it for months, maybe years? Why linger in the muck of ambiguity? Why question what feels so obvious?</p><p>But that’s precisely the danger of the swamp: it lulls you into a false sense of clarity. The moment you think you have all the answers is the moment you stop seeking the truth. Overconfidence builds like quicksand, keeping teams from seeing the gaps, nuances, and outliers that could change everything. Certainty won’t just stifle curiosity — it has the potential to suffocate it. Without curiosity, you’re left with nothing but recycled thinking, circling the same old terrain, never uncovering the unexpected breakthrough hiding just beneath the surface.</p><p>The worst thing about this swamp is that it has the potential to trick you into thinking you are making good progress. You and your team could very well be checking all the process boxes filling you with the sense of accomplishment one should have after several hours, or days, of collaborative work. But if you are stuck in the Swamp of Misunderstanding then unfortunately, there is a good chance your effort is not providing you the insights you wil need to be as successful as you could be.</p><h3>Getting Stuck in the Muck</h3><p>The thing about the Swamp of Misunderstanding is that it doesn’t swallow your team whole. They march right through, feeling productive, maybe even energized. <strong>It’s the data points — the critical insights about the problem space — that get sucked under, lost to the muck.</strong> The real danger? The team often doesn’t even realize it’s happened. It’s like losing all your food provisions to quicksand during a trek and only noticing the lighter packs after you’ve already set up camp — too far down the trail to go back, and woefully unprepared for what’s ahead. So why does this happen?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iwBsU7Y-wKX7BKvhzeW54w.png" /></figure><p>There are lots of reasons this phase is given minimal effort. But here are the top three:</p><h4>1. Overconfidence in Assumptions</h4><p>Team members often convince themselves they already know the customer or the problem well enough to skip the empathy phase, especially if they have prior experience or deep familiarity with the domain. And let me be clear: expertise and experience absolutely have a role to play here. In fact, they can and should serve as valuable assets during the Empathy phase. But — and this is where things get tricky — that same confidence can sometimes turn into a trap.</p><p>The problem is that experience can quietly morph into overconfidence, creating blind spots. Instead of fueling curiosity, it starts to dismiss it. Teams lean on their prior knowledge, waving off the need for deeper exploration or the possibility of uncovering something new. It’s not outright arrogance; it’s subtler than that. It’s the quiet assumption that “we’ve seen this before” or “we already know what we need to know.”</p><p>But here’s the rub: the very nature of discovery demands a certain level of openness, a willingness to set aside what you think you know in pursuit of what you don’t. And when experience starts shutting the door on curiosity, teams risk building solutions based on recycled assumptions rather than fresh, user-driven insights. That’s not leveraging expertise; that’s letting it undermine the very foundation of Design Thinking.</p><h4>2. Confirmation Bias</h4><p>Confirmation bias is the sneaky saboteur of Design Thinking, a close cousin — perhaps even a twin — of overconfidence. Instead of using empathy to uncover fresh insights, teams unconsciously shape the process to reinforce what they already believe. Conflicting feedback is dismissed as an outlier, inconvenient data points are rationalized away, and groupthink takes hold. This isn’t done out of malice or intention — it’s a natural human tendency to seek coherence and confirmation.</p><p>The danger lies in its subtlety. Teams often don’t realize it’s happening, mistaking agreement for clarity and validation for progress. But when confirmation bias takes root, it locks teams into their existing assumptions, shutting the door on the curiosity and open-mindedness that fuel true innovation. Without vigilance, the process becomes a loop of self-reinforcement rather than a path to new understanding.</p><h4>3. Misperception of Empathy as “Soft” Work</h4><p>Some team members view empathy as abstract or non-essential, especially compared to more tangible tasks like building or implementing. To them, it feels like a diversion — a detour from the “real work” that wastes valuable time and talent. This mindset can be the hardest to shift, as it stems from a deeply ingrained belief that prioritizes action over exploration.</p><p>While this perspective is less common than it once was, it still lingers in some teams. It ties back to the broader misconception discussed earlier: the idea that empathy is a soft, indulgent exercise rather than a strategic investment. For these skeptics, reframing empathy as a critical step toward meaningful solutions — not just another task — becomes key to breaking through their resistance and unlocking their engagement.</p><h3>Escaping the Swamp, Leaning into Curiosity</h3><p>The ultimate secret to avoiding or escaping the swamp is to spark genuine curiosity in the team — a deep, unrelenting desire to truly understand the customer and their problem. <strong>Curiosity</strong> might just be the magic word here, the safeguard against the creeping complacency that so often derails fresh thinking. When curiosity teams up with empathy, it transforms the process. Suddenly, it’s not enough to skim the surface or rely on assumptions. The team becomes rigorously invested in uncovering the conditions and experiences that shape the customer’s world — what they’re trying to achieve, the obstacles they face, and how a potential solution might fit into their lives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CE8A8pYK00WkYXqe0nWl0Q.png" /></figure><p>This doesn’t mean you and your team need to embark on some costly, time-consuming vision quest to forge a mystical, soul-bonded unity. That’s a bit much — not to mention arguably unnecessary — I myself would not even know how to do that. The level of understanding your team needs to achieve about the space and the customer is often directly proportional to the stakes of getting it wrong.</p><p>If you’re working on a one-week design sprint, the time you spend on empathy might be minimal — enough to keep the project moving without derailing. But if you’re diving into a $500,000, six-month initiative, the stakes are higher, and so is the demand for rigor. In short,<strong> the investment in understanding scales with the cost of failure</strong>.</p><p><em>Whatever empathy initiative you and your team undertake, fully commit to it…lean in.</em></p><h3>Path to Getting Complete Team Engagement</h3><p>Engaging your team in the empathy stage requires a shift in both mindset and practice. It starts with reframing empathy as an <strong>essential investment</strong>, not an optional detour. Leaders play a crucial role in connecting the dots: empathy isn’t “soft” work — it’s the <strong>foundation for solving the right problem</strong>. Skipping it risks wasted resources, misguided solutions, and failure.</p><p>Here’s how to move the needle from resistance to engagement:</p><h4>1. Set the Stakes Early</h4><ul><li><strong>Communicate the Risks</strong>: Clearly outline what’s at stake if the empathy phase is skipped or glossed over. For example:<br><em>“If we don’t understand our users, we might build something they won’t use. That could mean months of work down the drain.”</em></li><li><strong>Tie it to Outcomes</strong>: Explain how empathy prevents costly missteps and ensures that the team’s efforts are focused on creating solutions users actually need.</li></ul><h4>2. Make It Tangible</h4><ul><li><strong>Hands-On Activities</strong>: Involve the team in user interviews, shadowing sessions, or contextual observations. Assign roles, such as interviewer, note-taker, or observer, to ensure everyone is actively participating.</li><li><strong>Facilitate Immersion</strong>: Use tools like empathy maps, journey mapping, or role-playing exercises to help team members visualize and connect with the user’s experience.</li><li><strong>Leverage Real Stories</strong>: Share compelling user anecdotes or feedback to demonstrate the practical impact of empathy.</li></ul><h4>3. Create Space for Aha Moments</h4><ul><li><strong>Debrief Together</strong>: After each activity, facilitate a team discussion to surface insights. Encourage them to share surprises or moments that challenged their assumptions.</li><li><strong>Focus on Specifics</strong>: Highlight how a single piece of user feedback might change the design, shift priorities, or prevent a misstep.</li></ul><h4>4. Emphasize Efficiency Through Empathy</h4><ul><li><strong>Time Well Spent</strong>: Reinforce that time spent on empathy saves time later by reducing iterations, rework, and false starts. For example:<br><em>“Spending two days here might save us two months later.”</em></li><li><strong>Right-Size the Effort</strong>: Adjust the depth of empathy work to the project’s scale. A week-long sprint might only need a few user interviews, while a long-term initiative warrants deeper research.</li></ul><h4>5. Cultivate Curiosity</h4><ul><li><strong>Model Curiosity</strong>: As a leader, ask questions that challenge assumptions and demonstrate genuine interest in user needs.</li><li><strong>Celebrate Discovery</strong>: Highlight breakthroughs or key insights as wins for the team, reinforcing the value of their engagement in the process.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qCEwNETGzZI9fXJ5X3CS0g.png" /></figure><h3>Avoiding the Swamp of Misunderstanding</h3><p>You don’t need to tackle every strategy I’ve outlined to prevent your team from getting stuck in the Swamp of Misunderstanding. Think of it as a menu of options. The key is to stay alert for signs that the team is losing curiosity or veering off course. When you notice those signs, revisit the list and identify which approaches might help steer them back on track. The goal isn’t to follow a rigid checklist but to recognize when engagement falters and take the right action to keep the team rooted in empathy and discovery.</p><h3>Final Thoughts on the Empathy Pitfall</h3><p>The key to navigating the Empathy phase of Design Thinking lies in maintaining a balance between curiosity and engagement. Skipping or rushing through this phase can set your team up for costly mistakes, whether through missed insights or misguided solutions. As a leader, your role is to guide the team through these potential pitfalls by emphasizing the importance of truly understanding the user, creating opportunities for hands-on involvement, and fostering a mindset of exploration. By doing so, you’ll not only avoid the swamp of misunderstanding but also ensure that your team’s efforts are focused, deliberate, and positioned for success. The investment in empathy isn’t a detour — it’s the very foundation for building solutions that truly resonate with users. So, lean into the process, engage fully, and watch the breakthroughs unfold.</p><p>Next article we will explore major “Ideation” and “Iteration” Pitfalls….stay tuned.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfe56aff7064" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sense-and-signal/design-thinking-perils-pitfalls-dfe56aff7064">Design Thinking Perils &amp; Pitfalls</a> was originally published in <a href="https://medium.com/sense-and-signal">Sense and Signal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Jig is up!]]></title>
            <link>https://medium.com/sense-and-signal/the-jig-is-up-1d626faabc49?source=rss----34ad259549c3---4</link>
            <guid isPermaLink="false">https://medium.com/p/1d626faabc49</guid>
            <category><![CDATA[project-management-tool]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[tools-for-design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jodah Jensen]]></dc:creator>
            <pubDate>Thu, 30 May 2024 00:59:56 GMT</pubDate>
            <atom:updated>2024-05-30T16:50:32.235Z</atom:updated>
            <content:encoded><![CDATA[<h4>…or How to Keep All Your Fingers in Product Development</h4><p>I am addicted to watching <em>This Old House</em>. I love it; it’s a relaxing yet informative TV experience that satisfies both my type A and B personalities. To all my other responsibilities, I apologize; I’ve devoted too many hours watching our favorite Bostonians improve Massachusetts, one Colonial Revival at a time.</p><p>But now, after an inordinate amount of time “wartching” Tom, Richard, Kevin, Tom, and Roger wow me with their knowledge, I am prepared to say the following. <strong>Software Product Development can learn a thing or two from them.</strong></p><figure><img alt="The cast of This Old House. Roger Cook, Tom Silva, Kevin O&#39;Conner, Norm Abram, Richard Trethway" src="https://cdn-images-1.medium.com/max/1024/1*-d-aWdGveERTcNRxuEAfdQ.png" /></figure><p>While I believe software development can learn many valuable lessons from carpentry and construction, I am particularly fascinated — and somewhat envious — of their tools. These tools are the unsung heroes, enabling craftsmen to transform raw materials into precise, high-quality structures. They boost efficiency, allowing carpenters to work faster and safer, and empower them to explore and execute complex designs with remarkable finesse.</p><p>But, in my naive opinion, one carpenter’s tool stands out above the rest: <strong>the jig</strong>. Highly leveraged among woodworkers, the jig epitomizes the craft and discipline of carpentry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/708/1*HDNgAEKX1hL1Hto7MwBnNg.png" /></figure><p>What is a Jig? In carpentry, a jig is a custom-made tool used to <em>control the location and/or motion of another tool</em>. It is typically used to ensure accuracy and repeatability in tasks such as cutting, drilling, and shaping wood. Jigs help carpenters perform these tasks consistently and efficiently, making complex or repetitive jobs easier and more precise. Jigs are tools for tools made by other tools.</p><blockquote>The Jig stabilizes the working environment removing variables that can mess up the end result if not accounted for.</blockquote><h4>Lots of Give, Little Forgiveness</h4><p>I work in software development as an Experience Solution Architect and Strategist in the Enterprise InfoSec/Big Data space. This field is characterized by infinite complexity, requiring numerous moving parts to come together seamlessly to be effective. There is often a lot of flexibility, but little room for error.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UeTSRyrrE8GF5aMEnpFP4A.png" /></figure><p>Given the frequent competing signals and countervailing noise in product design and development, I propose we explore the idea of creating our own “jig” to stabilize the product creation process. Just as a woodworking jig ensures precise and consistent results, a well-designed framework in software development can streamline processes, minimize errors, and enhance efficiency. This could involve developing standardized templates, automating repetitive tasks, or creating robust testing protocols. The goal is to reduce the likelihood of critical mistakes — akin to avoiding cutting off one’s fingers in woodworking — thereby ensuring a smoother, more reliable development process</p><p>So, is there such a thing as a Jig in software product dev space? There are, and I have one particular type of tool in mind.</p><h4>Intro to the Canvas</h4><p>My introduction to the “canvas” concept came from my colleague Brad Topliff during our time at Tibco. Brad was fervently advocating for a new approach to modeling business, leveraging the Business Model Canvas (BMC) as a communication tool. Its simple visual design, encapsulating all critical components on a single page, immediately captured my interest and imagination.</p><p>What exactly is a Canvas? Are we talking about paint here?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*5OUSz7RH6n14F6CNbf_8Ew.png" /></figure><p>While many might first think of an artist’s canvas, the type I’m referring to is a tool designed for the facilitation and presentation of process models; and those specifically used in your organization. Think of it as a blank space where you can visually map out and organize the fundamental aspects of a concept or strategy, staying on point, while providing a flexible and adaptable surface for exploration.</p><p>This type of canvas serves as more than just a visual aid — it’s a powerful tool for clarity, communication, and collaboration. It helps stakeholders grasp the intricacies of a system or strategy, identify opportunities, and align on shared objectives. By offering a visual representation of the structure and relationships, it facilitates strategic decision-making and innovation in a dynamic environment.</p><p>Lets relate this back to the Business Model Canvas for a more concrete example. By the way, none of this is rocket science.</p><h4>The Business Model Canvas</h4><p>The Business Model Canvas has one goal, distill the complex essence of a business into a simple, <em>visual framework</em>, allowing business leaders to see their venture from every critical angle and innovate with clarity. The tool turns strategic planning into a “precise art”, aligning every component of the business in a coherent, actionable narrative.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*usOnrxQ1I-94cAQ1Rfe42w.png" /></figure><p>The BMC does all of this by creating a simple one page layout communicating the “big rock” components of a business, and their relationships. It is a structured framework that consists of <em>nine</em> key building blocks, each representing a crucial aspect of a business model. These blocks include <em>Customer Segments, Value Propositions, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partnerships, and Cost Structure</em>. Together, they provide a comprehensive overview of a business.</p><h4>Guard Rail and Blank Page?</h4><p>Ifeel I have suggested the canvas serves as both a blank page and a guardrail. Like a carpenter’s jig, locking down certain dimensions of your problem relieves a significant cognitive load, allowing you to focus more effectively on the identified problem or solution space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oYKln58QsFc__JeA3dnx-A.png" /></figure><p>Locking in specific dimensions of a business problem or controlling a set of variables helps streamline the creation process by providing a clear and stable framework. This approach reduces complexity and uncertainty, enabling teams to concentrate their creative efforts on specific areas without being overwhelmed by too many changing factors. By narrowing the scope and defining key parameters, it becomes easier to identify viable solutions, make informed decisions, and maintain consistency throughout the development process. This ultimately leads to more efficient and effective problem-solving.</p><h4>Canvas = Jig = makes my life easier</h4><p>Okay, so back to the lead. besides the BMC there are all sorts of canvases these days helping teams execute their plans or model their efforts. There are customer discovery canvases, project canvases, empathy map canvases, lean UX canvases, and learning experience canvases, and…. The list goes on, with more being created all the time. Its the decade of the canvas.</p><p>Here is why I suggest <em>the canvas</em> is the jig for business process :</p><p><strong>Guidance and Structure</strong><br>Both the Canvas and a carpenter’s jig provide a structured approach to their respective tasks. The canvas guides planning and approach, while the jig guides physical crafting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SeZUwmgv5WA-nVRYLq_iWg.png" /></figure><p>By visually highlighting the essential components that need attention, the canvas streamlines the process by directing your team’s focus to the most critical variables. It allows you to concentrate solely on “this” one thing. If someone strays off track, the canvas serves as a gentle reminder, guiding them back to the immediate priorities. This approach alleviates the pressure on any single individual to keep things on course, fostering a collaborative and focused environment.</p><p><strong>Efficiency and Consistency</strong><br>Both tools enhance efficiency by providing a clear template to follow, reducing errors and ensuring consistency. The canvas ensures all the process or models components are considered, while the jig ensures uniformity in physical production.</p><p>Canvas tools present all the critical considerations in an easily consumable format. One of the key aspects of creating an effective canvas is identifying only the most salient points, which requires clearly defining the canvas’s scope. By trusting the canvas’s structure, you can be confident that all necessary topics for the specific effort are being addressed. Its sort of a visual narrative of a defined process.</p><p><strong>Customization</strong><br>Both can be customized for specific needs. The Canvas can be adapted for different industries or business types, and jigs can be tailored for specific tasks or projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NJDd4pzsXo3nHI749ND_Qg.png" /></figure><p>As mentioned earlier, there are many kinds of Canvases out there these days. Because the idea of as canvas is basic in principle, there is really no limit for which they can be used. One could come up with a “how to watch TV” Canvas if they wanted.</p><h4>Canvas In Execution</h4><p>A canvas is sort of like a runbook, or something that tells you how to do something, but with a big important difference….it leans in on questions rather than immediate answers. Like all blank canvases, it is ….blank. You and your team need to fill in the answers.</p><p>One can go about filling out a canvas all by them lonesome, but the real value around the canvas comes into play when the team is involved. When this is done, you ensure that everyone is aligned, understands their role, and feels valued. This collaborative approach not only <em>enriches the canvas with diverse insights </em>but also fosters a sense of shared ownership and commitment to the business’s success.</p><p>Sure, start filling it out by yourself; I call this seeding. By seeding you can provoke people into engaging. Put some wild ideas in there to give people a chance to perhaps reject some stuff, call you out; or maybe to your surprise, give the crazy idea a thumbs up. The goal here is to get your team engaged. More detail on this later.</p><h4>Finally, Canvas Creation</h4><p>Not everyone will create a canvas, but I would argue its a great way to get yourself familiar with the needs of any scoped effort. In some ways its a visual manifestation of the <a href="https://en.wikipedia.org/wiki/DSRP">DRSP</a> approach to systems thinking</p><p>DSRP stands for Distinctions, Relationships, Systems, and Perspectives. Lets take this into the building of a canvas.</p><ol><li><strong>Identify the scope of the effort.</strong> You will find yourself going in circles if you don’t define a scope. As you work through the canvas, this scope might change, but it should always serve as the framework for your canvas (often defined by the title).</li><li><strong>Identify the parts or distinctions of the process or model.</strong> What are the key aspects that need to be addressed and answered to consider the effort completed or sufficient to move forward? These aspects should be the variables that get filled in when engaging a team.</li><li><strong>Identify systems and relationships. </strong>The parts are laid out on the canvas to highlight the variables. In the Business Model Canvas (BMC), these are large boxes that touch other boxes they have immediate relationships with. In other canvases, these relationships can be represented by arrows or visual groupings. This is where the art comes in.</li><li><strong>Identify the perspective.</strong> Who is affected by this canvas? Who will use this canvas? In the end, someone needs to care about this effort. Who are they? This will inform you on how to structure the canvas.</li></ol><p>Thats if you want to make a canvas. (You should)</p><h4>Thats it!</h4><p>I hope I have convinced you that the canvas is a jig worth adding to your tool chest, and that I have not forced any metaphors beyond their breaking point. If so, you have not seen anything yet!</p><p>Cheers from the<br>Accidental Human Experience-naut</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d626faabc49" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sense-and-signal/the-jig-is-up-1d626faabc49">The Jig is up!</a> was originally published in <a href="https://medium.com/sense-and-signal">Sense and Signal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[If you cant Research, Measure]]></title>
            <link>https://medium.com/sense-and-signal/if-you-cant-research-measure-92f696edf53b?source=rss----34ad259549c3---4</link>
            <guid isPermaLink="false">https://medium.com/p/92f696edf53b</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[research-and-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[experience-design]]></category>
            <dc:creator><![CDATA[Jodah Jensen]]></dc:creator>
            <pubDate>Thu, 02 May 2024 03:26:47 GMT</pubDate>
            <atom:updated>2024-05-30T01:48:26.590Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dVtzZoK2OaogNSBunQVjuQ.png" /></figure><p>Let’s begin by acknowledging that measuring is essentially a form of research. However, when someone mentions research, it often evokes various notions, with simply measuring typically being the last among them.</p><h4>Research is perceived as a time-consuming and expensive endeavor that should be avoided whenever possible.</h4><p>Although rarely voiced aloud, this sentiment is internally acknowledged by many. Unfortunately, they’re not entirely mistaken. Having worked on numerous research projects while designing software solutions, I can attest that for various reasons, a considerable number failed to yield insights of significant value. I’ll delve deeper into these reasons in a future post. But for now, understand that conducting research solely for the sake of it can often be a wasteful expense.</p><h4>Wait….thats BS!</h4><p>Research is not a waste of time. This reality holds much more weight, especially when entrusted to knowledgeable researchers or those with a research-oriented mindset. Research is invaluable, serving multiple purposes such as deepening understanding, updating knowledge, challenging assumptions, discovering new perspectives, and identifying knowledge gaps.</p><p>Consider this: if you’re about to invest $2 million over the next year in developing a new solution, wouldn’t it be prudent to conduct some upfront research to mitigate potential risks? Isn’t it worth the effort and investment?</p><h4>But we don’t have time for Research….we are agile!</h4><p>Here’s where my assertion comes into play: “if you can’t do research, measure.” In the Agile world, the product itself becomes the subject of research. It involves a focused and condensed type of research where a small engineering effort, typically spanning 2 to 3 weeks, is executed and then observed for its effectiveness.</p><p>This is when you bring out the measuring tape. Even if it’s not specifically an agile project but merely constrained by resources and time, start measuring. But what should you measure?</p><h4>Outcomes, Outcomes, and maybe some other things</h4><p>Every software solution should have an outcome if not several outcomes. What are they? They things like the following:</p><ol><li>Value Proposition: Is it doing the job and helping the customer as expected? Is it successfully helping the customer get their job done? This is closely related to the last poin t on this list, but is meant to be an observation.</li><li>Functionality: Does the software perform the intended functions effectively and efficiently? Are all features working as expected without any critical errors or bugs?Its important to know the difference between this point and the previous one. A solution could have a function performing as desired, but not ultimately help the customer in a satisfactory way.</li><li>Usability: How easy is it for users to interact with the software? Is the user interface intuitive and well-designed? Are there adequate instructions or documentation to help users understand how to use the software?</li><li>Performance: How fast does the software execute its functions? Does it meet performance requirements in terms of response time, throughput, and resource utilization?</li><li>Customer Satisfaction: Ultimately, are users satisfied with the software? Do they find it useful, reliable, and easy to use?</li></ol><h4>Identifying the outcomes has its own “goals”</h4><p>Outcome Identification is a whole thing unto itself, but Ill say this to get you started. Identifying outcomes aligns with specific goals. Outcomes should directly contribute to achieving these goals; otherwise, they are wasted efforts. Begin by identifying the goals surrounding your new product endeavor, and ensure that the expected outcomes align with these goals.</p><p>An outcome should make a tangible difference. For instance, if the goal involves enabling users to download a file, an outcome could be “User can successfully download file every time for the first time.” Or perhaps, “User satisfaction score increases by one point due to enhanced download functionality.”</p><h4>This is no substitution for a robust research effort, but its better than nothing-</h4><p>Not only is it better than nothing, but if you are having problems getting your team to start thinking from an ABCD (Alway Be Collecting Data) perspective, this is a great gateway drug.</p><p>Any way, there is my most recent rant for ya, I hope this kick starts some thoughts.</p><p>With Love,<br>The Accidental Experience Architect</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92f696edf53b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sense-and-signal/if-you-cant-research-measure-92f696edf53b">If you cant Research, Measure</a> was originally published in <a href="https://medium.com/sense-and-signal">Sense and Signal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Systems Thinking” is the Hot Knife on your Communication Butter]]></title>
            <link>https://medium.com/sense-and-signal/systems-thinking-is-the-hot-knife-on-your-communication-butter-2ff21a291014?source=rss----34ad259549c3---4</link>
            <guid isPermaLink="false">https://medium.com/p/2ff21a291014</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[clarity]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[Jodah Jensen]]></dc:creator>
            <pubDate>Mon, 28 Aug 2023 22:36:03 GMT</pubDate>
            <atom:updated>2023-08-28T22:36:03.561Z</atom:updated>
            <content:encoded><![CDATA[<h4>Another Take from the Accidental Explorer</h4><h4>Admittedly I’m burying the lead, but indulge me…</h4><p>How well do you speak? Do you feel you have a command of your language? Are you able to articulate your ideas sufficiently enough so that when people walk away from a conversation with you they know, with confidence, your perspective? I am not here to say that you are bad at communicating. However, I can’t help but think of this quote by George Bernard Shaw (maybe).</p><blockquote>“The single biggest problem in communication is the illusion that it has taken place”</blockquote><p>Your general societal languages, while a versatile tool for communication, often lack the precision required in business contexts. Its inherent imprecision can lead to confusion and misunderstandings, which are particularly detrimental in the business world where clear and accurate communication is paramount.</p><p><strong>So, Here is the Problem with Language</strong></p><p>In businesses or organizational structures, discussions often involve intricate details, specific figures, and well-defined terms. Reliance on general language can result in vague statements that fail to convey crucial information accurately. Ambiguities arising from imprecise language can cause misinterpretation of expectations, project goals, and contractual terms. This can lead to costly errors, missed deadlines, and strained relationships between stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uLdcMwSnDErLE_kyl-u-6w.png" /><figcaption>To guys talking about vague UI improvements</figcaption></figure><p>Moreover, individuals may interpret general language differently, based on their personal experiences and perspectives. This divergence in understanding can lead to conflicting interpretations and decisions, hindering effective collaboration and problem-solving. In contrast, precise language in Organizational communication leaves no room for misinterpretation, facilitating better alignment among team members and partners.</p><p>With that all that said, wouldn’t it be nice if there was a framework out there that could help provide some clarity to the often complex problems we often find ourselves attempting to solve in our place of work.</p><h4>Now for the lead…Enter Systems Thinking.</h4><p>In a nutshell Systems thinking is a holistic approach that views the world as interconnected systems, emphasizing how parts influence each other and the whole. It aims to understand complex phenomena by considering relationships, feedback loops, and emergent properties, leading to insights into underlying patterns and dynamics.</p><p>Now, I am very much aware I am approaching the conversation of Systems Thinking in a somewhat tangential and perhaps circuitous way. Most people bring up Systems Thinking when they are discussing ways to address complex or perhaps even “wicked” problems. However, I am telling you, the tools and mental models that Systems Thinking leverages will help you address your daily communications (and infuriate your loved ones if you bring it home with you).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zrf42Gq6TYwU6SjpYEyrXA.png" /></figure><p>There are many leaders and thinkers in the Systems Thinking space, and I am not going to even touch the Complexity Theory stuff here. There is simply too much in this specific domain to take on in this Hot Take. I am going to focus on one example and see where it takes me and how it resonates with you.</p><h4>Introducing Derek Cabrera and DSRP</h4><p>Derek Cabrera is a prominent educator, researcher, and thought leader known for his contributions to the field of systems thinking and education. He is recognized for developing the DSRP (Distinctions, Systems, Relationships, and Perspectives) framework, which serves as a cognitive tool for enhancing problem-solving and understanding complex systems.</p><p>The thing is, life is a complex problem. There is really nothing simple about it. I don’t know about you, but I have found the imprecise nature of day to day communication great for generating connections but problematic when precision is of the utmost importance. It’s Derek Cabrera’s tools, and more specifically, concepts around DSRP that I find useful.</p><p>The DSRP framework is a cognitive tool designed to enhance understanding and problem-solving by breaking down complex systems into four key components: Distinctions, Systems, Relationships, and Perspectives. Distinctions involve identifying individual elements within a system. Systems focus on recognizing the interconnections and structures. Relationships highlight the interactions between elements. Perspectives consider diverse viewpoints and contexts.</p><p>By applying DSRP, one can analyze and synthesize information more effectively, enabling a holistic view of intricate systems. This approach promotes critical thinking, fostering a deeper comprehension of complex issues and facilitating innovative solutions through the exploration of diverse perspectives and the connections that shape our world.</p><p>Okay, that’s a mouthful, and I do not expect you to learn DSRP in this short (but maybe too long) article. Also, are probably saying to yourself, there is no way I am going to use this every time I find myself talking to someone. This guy is either nuts or clinically pedantic. It’s too much; I agree. However, I am not proposing that you consider this as a formal exercise in every situation. NO, I am catually saying learn it to forget it (by forget it I mean internalize it).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wouCr8Idme-dXdL4vTq-Lw.png" /></figure><p>I am a piano player. I have been playing Jazz piano for years. As some of you might know, learning any instrument requires all sorts of drills and exercises such as learning your scales and chords. The thing is, you don’t learn scales to play the scales (although some might). You learn the scales so that you might generate intuitions about what to play during certain harmonic situations. You are likely not to play every note of the C scale over a C chord, but rather just one or two (there are seven in total). You are training yourself to internalize the concepts, not think about them. I am saying this is how one can use DSRP.</p><p>So here are the Drills of DRP. Like all drills, you don’t take on everything at once. My suggestion is start with the first component of DSRP, Distinctions. Practice having those conversations with both yourself and those around you. How clear can you make the distinctions? How much alignment can you get around the distinctions? Eventually, this will become second nature. You will find yourself developing an appetite for distinction clarity, and with a little effort and luck, so will your team.</p><p>Once you have gotten familiar with Distinction identification then move onto Systems..and so on. I promise that you won’t find yourself forcing people to a whiteboard. THis will just be a natural course in conversation.</p><ol><li><strong>Distinctions:</strong> This involves identifying and clarifying individual elements within a system. It’s about recognizing the different parts or entities that make up the whole. By making meaningful distinctions, one can better understand the diversity and complexity present in a system.</li><li><strong>Systems: </strong>This aspect focuses on understanding how the identified elements or parts come together to form a larger functioning entity. It involves recognizing the structures, organization, and overall behavior of the system as a whole.</li><li><strong>Relationships: </strong>Relationships refer to the connections and interactions between the various elements of a system. Understanding relationships helps uncover the dependencies, influences, and dynamics that drive the behavior of the system.</li><li><strong>Perspectives: </strong>Perspectives involve considering multiple viewpoints and contexts that shape how a system is perceived. By examining different perspectives, one gains a more comprehensive understanding of the system’s implications and impacts.</li></ol><h3>The Takeaway</h3><p>As a leader or a team member it is often incumbent upon you to grasp a problem space or situation as comprehensively as possible. You also need to be able to articulate it as clearly as possible. How do you do this?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EBLLySbufuqGAjvyl4S5Lg.png" /></figure><h4>Strengthen your ability to identify the distinctions or the atomic components?</h4><p>This is not easy. Distinctions are a function of context and ultimately subjective in nature. Problems arise when the team members make their own “distinct” distinctions. Help the team clearly articulate the parts that are pertinent toward understanding and modeling the problem space. Get agreement or at the very least a shared understanding on how the others see the distinctions. Seeing other people’s perspectives goes a long way in moving forward with confidence. If you do this, and nothing else in the DSRP world, you will have improved your chances of success by a <strong>million percent</strong>.</p><h4>Group those components of a space into Systems</h4><p>Once you start to gain an understanding of the atomic parts, start to think about how these distinctions relate to a broader system. As an example, the heart is a distinction (which could easily be broken down into smaller distinctions), but it’s also part of a system known as the circulatory system. Admittedly, this is made difficult without thinking of the relationships at this point, but the exercise is worth the effort. It sparks great conversation around where things should be placed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zbEdq0vDFLW1_7bSWgv9Tg.png" /></figure><p>I think of this as the map of the environment, or the skeletal structure from which all the “whys” hang from. If you get this part wrong, then the effort of identifying the relationships and perspectives are jeopardized. Imagine if one were to incorrectly suggest the knee bone was part of the lymphatic system. This would probably result in all sorts of bizarre medical outcomes; most probably being bad, with perhaps some happy accidents.</p><p>In the end, articulation of the system at this point allows you and your team to better comprehend the space you are looking to address. You will begin to gain confidence that you and your team are talking about the right things and that those things actually do exist. Sometimes this is half the battle.</p><h4>Relationships will start to expose any failure points</h4><p>Relationships represent the connections and interactions between various components within a system. They highlight how different parts of a system influence and impact one another. Understanding these relationships is essential for comprehending the functioning of a system as a whole. This often involves cause-and-effect interactions. By understanding these causal relationships, we can identify factors that drive change within a system. This is crucial for predicting the outcomes of various actions and interventions.</p><p>Systems often exhibit emergent properties — properties that arise from the interactions of individual components but cannot be predicted by analyzing those components in isolation. THis effort helps uncover these emergent properties and understand the complexity that emerges from simple interactions.</p><h4>Finally, Gain some perspective and provide some value</h4><p>Who cares? This is often from the perspective of the people who are involved in the problem, but it does not have to be. It could be an animal, car, or an atom. The question you are asking is what are the entities that have skin in the game, and what does it mean to them?</p><p>This is when the conversation around value will really hold the most “ value”. By identifying who will have a perspective and what those perspectives might be, you will begin to understand the areas that are working and those areas that are not. If you are a product person, this is when you will begin to really identify areas of either new or improved value. Lean in hard here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TBXBXt6F1MHJYwOBC_4Z9Q.png" /></figure><h4>Wrap-up</h4><p>This is clearly a hand-wavy article on the concept of DSRP and Systems Thinking, and I wholeheartedly recommend reading more about this very rich space. You should also explore the area known as Complexity Theory, which some seem to think is a competing theory of Systems Thinking, but a tend to think of as complimentary. Finally I want to suggest watching the interview<a href="https://medium.com/u/109c4607c72a"> Daniel Tarker</a> and I will have with Derek Cabrera on the<a href="https://www.youtube.com/channel/UCHrVSzsADa1PQCzLEbr10YQ"> Sense and Signal Podcast</a> which should be dropping September 3rd of 2023.</p><p>The DSRP Systems Thinking approach is a fantastic framework to familiarize yourself to help you not only tackle complex situations, but once internalized, a way to begin to think about all the systems in your life. It also has to be said that DSRP is just one flavor of Systems Thinking, and Systems Thinking is just one of thinking about complexity. So I say to you, go forth and…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ff21a291014" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sense-and-signal/systems-thinking-is-the-hot-knife-on-your-communication-butter-2ff21a291014">“Systems Thinking” is the Hot Knife on your Communication Butter</a> was originally published in <a href="https://medium.com/sense-and-signal">Sense and Signal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>