<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Thomas Havranek Jr. on Medium]]></title>
        <description><![CDATA[Stories by Thomas Havranek Jr. on Medium]]></description>
        <link>https://medium.com/@thomas.havranekjr?source=rss-1b7621cec1d9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*kshOhEsHdKZhZhe1asm0YA.jpeg</url>
            <title>Stories by Thomas Havranek Jr. on Medium</title>
            <link>https://medium.com/@thomas.havranekjr?source=rss-1b7621cec1d9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:58:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thomas.havranekjr/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Get Real]]></title>
            <link>https://medium.com/teletracking-design/get-real-89148e9895c9?source=rss-1b7621cec1d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/89148e9895c9</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Thomas Havranek Jr.]]></dc:creator>
            <pubDate>Wed, 19 Dec 2018 19:53:28 GMT</pubDate>
            <atom:updated>2018-12-20T13:39:45.860Z</atom:updated>
            <content:encoded><![CDATA[<h3>Get Real: The problem with using a lot of words and not really saying anything.</h3><h4>We’ve all been there…</h4><p>You’ve just listened to a presentation filled with loads of concepts, data, and jargon. The presenter asks if there are any questions or comments. Someone says something about slide 9 having a typo. Another person raises an arbitrary concern that’s really just a plug for their own project. The rest remain silent.</p><p>The presenter smiles and thanks everyone for their time. The meeting is adjourned and the assumption is that all parties now have a shared understanding of the material.</p><p>And yet they don’t.</p><p>You know they don’t. They know they don’t. The presenter even has a pretty good idea that they don’t. But the meeting is finally over and you can all get back to that thing you need to finish before the end of the day.</p><p>How does this happen? Why are we trapped in this cycle? I have a theory: It’s because we are far too reliant on words. Yeah I know, words matter. But they’re also notoriously unreliable.</p><p>Words are not concrete, but rather an abstraction of real life. If they were concrete there wouldn’t be 2,000+ languages spoken today; each one having been uniquely abstracted from a shared, concrete reality.</p><p>Words are also too easy. Anybody can fill a presentation deck with words and make it look like they accomplished something. But it takes significant energy and rumination to move past the abstract and articulate something concretely. It also requires something better than words.</p><h4>Systems Thinking &amp; The Importance of Diagramming</h4><p>It’s been said that if you can’t explain something simply, you don’t understand it well enough. It’s a great sentiment, but how does one go about properly understanding something? The first step is to adopt a systems mindset and embrace the fact that “<a href="https://medium.com/disruptive-design/tools-for-systems-thinkers-getting-into-systems-dynamics-and-bathtubs-1f961f7c4073">our world is made up of interconnected and interdependent systems.</a>” — Dr. Leyla Acaroglu.</p><p>Systems are inescapable. And the field of Experience Design exists to serve systems, whether we acknowledge it or not. Be it workflows, journey maps, user networks, etc. Make no mistake, we are designing for and within systems.</p><p>“But <em>I</em> care about the <em>user</em>,” you might say with your chest puffed and left eyebrow cocked. Great. Is your user alone on an island with zero dependence on his or her surroundings? Of course not. Your user is one component of a complex system. One element in an elaborate <a href="https://medium.com/teletracking-design/solve-for-x-1818099bdb9c">equation</a>.</p><p>As designers we are constantly stepping into new spaces and having to make sense of systems that are completely foreign to us. And the best way to make sense of any system is to <em>diagram</em> it.</p><blockquote>di·a·gram: a simplified drawing showing the appearance, structure, or workings of something; a schematic representation.</blockquote><p>The <strong><em>workings</em></strong> of something… That term doesn’t get tossed around as much as it should. It raises a very interesting question; do we truly understand the workings of our systems or are we just pretending that we do by using a lot of words? The process of diagramming forces us to answer this question by separating the abstract from the concrete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bsDYOyH4p1_Yy5itEFNKEw.png" /></figure><p>Without properly diagramming a system, our understanding of that system is often a complicated mess of concrete and abstract ideas (usually represented by a lot of words). This is a problem because what is abstract is often subjective, ambiguous, contradicting, and unreliable. If we aren’t careful to draw that out, the same will be true of our understanding of the system.</p><h4>Example: The Human Circulatory System</h4><p>Let’s take a look at a system we’re all intimately familiar with; the Human Circulatory System.</p><p>An overview of the Human Circulatory System might look something like this…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fDs5z3NI4-kHeRXP9q98LQ.png" /></figure><p>But is this a system? No. This is terminology. Terminology is used to <em>describe</em> the system. Terminology is abstract. And because it’s abstract, it doesn’t tell us anything about the appearance, structure, or workings of this system. So let’s focus on what is concrete…</p><p><strong>Purpose:</strong> The purpose of this system is to circulate blood through the human body. This is critical… <em>Blood</em> is the focus of this system. If we don’t maintain that focus, there’s nothing stopping us from diagramming the entire human anatomy.</p><p><strong>Elements:</strong> As we can clearly see above, there are many different terms for the elements of this system, but when you break them down, there are really just two <em>core</em> elements; Blood Vessels and Organs.</p><p><strong>Functions:</strong> There are four functions that these elements can perform; oxygenate blood, pump blood, carry blood, or process blood.</p><p><strong>States:</strong> There are two states in which blood can be; either oxygen-rich, or oxygen-poor.</p><p><strong>Blood Flow Direction:</strong> Last, there are two directions that blood can be flowing; away from the heart, or toward the heart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tqi-U9QCdTN3t46MsFw5lA.png" /></figure><p>Now we have some very objective categories, and we can use these to properly frame this system. For example, we all have an innate understanding of our lungs. But when we use the term “Lungs,” what does that really mean in the context of this system?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t5ZQZH00A-jAUyrz76xMbQ.png" /></figure><p>Objectively, “lungs” are an organ that oxygenates oxygen-poor blood in this system. Of course that sounds like a mouthful, but avoid the temptation to oversimplify this just for the sake of convenience. Convenience comes at the cost of properly understanding.</p><p>What about a “vein?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cq0Zn6YaxS9kTgSq5u5-nQ.png" /></figure><p>And an “artery?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y-k9cPD06bDVCLbZMnR-EQ.png" /></figure><p>Starting to get the idea? When we focus on these concrete elements, we can begin to properly diagram this system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fdjij-aidZJaaLgeP1X7Qw.png" /></figure><p>Even if we strip away all of the terminology, we can still get a sense of how this system works with just a few key items explained; it’s a network of organs and blood vessels, moving blood through various states of oxygenation and use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sct53QiWTW4bB6M2sBNQRg.png" /></figure><p>No words required. In fact, the Circulatory System offers a great example of words being unreliable: 85% of the time the term “artery” implies a blood vessel that is carrying oxygen-rich blood (red), and “vein” implies a blood vessel that is carrying oxygen-poor blood (blue). But there is one pair of blood vessels where this pattern breaks down and the terminology is actually opposite than the rest. Any guess where that occurs?</p><p><strong>Answer:</strong> The Pulmonary Vein and Artery, which connect the lungs and the heart together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kxs0HZ0jdQW9T-Z8l2H_Aw.png" /></figure><p>This is essentially the sub-system that is responsible for recycling, or oxygenating, the blood. So it’s the one place in the system where the terminology essentially contradicts itself. In this case, the concrete category that is driving the terminology is the direction of blood flow (away/toward heart), rather than the oxygenation state of the blood.</p><p>This type of synthesis requires a lot of work and critical thinking, but if done correctly can prove invaluable; allowing teams to focus on solving problems rather than constantly relearning domain knowledge. But when we neglect to do this heavy lifting up front, the burden doesn’t magically disappear. It gets pushed downstream, manifesting itself in the form of unproductive meetings, redundant conversations, and far too many words.</p><p>Get real. Do the work. And focus on what is concrete.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89148e9895c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teletracking-design/get-real-89148e9895c9">Get Real</a> was originally published in <a href="https://medium.com/teletracking-design">TeleTracking Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solve for X]]></title>
            <link>https://medium.com/@thomas.havranekjr/solve-for-x-1818099bdb9c?source=rss-1b7621cec1d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/1818099bdb9c</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[experience-design]]></category>
            <dc:creator><![CDATA[Thomas Havranek Jr.]]></dc:creator>
            <pubDate>Fri, 12 Oct 2018 12:00:58 GMT</pubDate>
            <atom:updated>2018-10-12T12:00:58.066Z</atom:updated>
            <content:encoded><![CDATA[<p>An Analytical Approach to Experience Design</p><p><strong>Challenge:</strong> Solve the following equation without googling…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k5q3S4iRlIydMUa5fpPuLw.png" /></figure><p>Were you able to do it?</p><p>Did you cheat?</p><p>Did you just keep scrolling and assume that I would eventually show the answer?</p><p>Well if you <em>did</em> attempt to solve the equation, there’s a good chance that at some point you rearranged it to look something like this…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZuEuKOkUSv2jDZ8tn7L2mg.png" /></figure><p>If you remember anything about algebra, you might recall that the goal when attempting to solve an equation is to consolidate the things that you know and isolate the one thing that you don’t know: <strong>X</strong>.</p><p>Combining “like terms,” going through the order of operations, all that fun stuff you probably thought you’d never have to hear about again. And yet here we are.</p><p>The interesting thing about equations is that if <strong>X</strong> wasn’t there, this problem would be easy. All you’d have to do is add, subtract, multiply, and divide. But when you throw an <em>unknown</em> in there… now you have a mystery. Now you have to do some work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b9Bo-dqs_IGo8GnrvU0IQg.png" /></figure><p>And if you’ve done your job correctly, and <strong>X</strong> is properly isolated. Then, and only then, are you able to just <em>do math </em>(X equals 3, by the way… lazy bum).</p><p>When we do this, when we consolidate the things that we know and we isolate what we don’t know, what we really have is a “Solution Space” and a “Problem Space.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G1zoVMCpmC8uV706U9glKA.png" /></figure><p>Our answer is <strong>X</strong>. But our problem is the unique combination of numbers and operations on the other side.</p><p>The same is true in Experience Design. The solutions that we craft are born directly from a unique set of people, roles, workflows, environments, dependencies, constraints, technologies, etc.</p><p>This is <em>chaos</em> when you first enter a new environment as a designer or design researcher. But through careful investigation and discovery, you begin to uncover something. You start to see patterns, relationships, priorities. You start to uncover a unique equation.</p><p>This is the first step in Experience Design; stepping into the chaos and working to uncover the equation. We can’t even begin understand the problem until we first uncover the equation.</p><h3>Uncovering Equations</h3><p>So what does that look like in real life? Obviously the equation metaphor is meant as an illustration, but you might be surprised at how well it holds up when we take it a little further. For example, there are two different types of numbers in algebraic equations and they both appear in the original example from before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SvL1pVQfhIh_nbRiQyhNTA.png" /></figure><p>Coefficients and Constants; numbers which multiply the unknown, vs. numbers that stand on their own. These are strikingly similar to what I would consider Direct Actors and Indirect Actors in an environment or workflow. Like Coefficients, Direct Actors play an active role in the equation. They have a direct relationship with “<strong>X</strong>.” Indirect Actors on the other hand play a passive role. Like their mathematical counterpart, they still have an impact on the unknown, just indirectly.</p><p>Take Uber for example. Some Direct Actors in that equation might be the driver, the passenger, the credit and bank card companies, even the dispatching logic. But there are also some Indirect Actors that can impact the “Uber Equation.” Traffic Patterns, road closures, weather. Even businesses; the open hours of common destinations, perhaps. Uber has no control over these factors and yet they still have a major impact on the kind of solution that Uber needs to deliver.</p><p>When we identify these elements during discovery, we begin to uncover the unique equation of the opportunity before us. It might seem like total chaos at first, but that’s the point. We have to first step into the chaos before we can begin to make sense of it.</p><h3>Framing Problems</h3><p>So let’s say we’ve uncovered our equation and we’ve rearranged it to isolate “<strong>X</strong>” from the things that we know. We have our Solution Space and our Problem Space.</p><p>Here’s the critical takeaway… What happens if I change the 7 to a 2 in this equation?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T1Y2Jx6n9M_QOfkSwiATCw.png" /></figure><p>Does X still equal 3? No! We should get a completely different answer for X now.</p><p>This is crucial, don’t miss it: Our solutions, whether in algebra or Experience Design, are ENTIRELY dependent on our understanding of the problem. With algebra, our success depends on our ability to break the equation down accurately. The same is true for framing the problem in Experience Design. Our solution is meaningless if we’re not solving the right problem. It sounds silly to point out but it’s so easily missed.</p><p>A problem is <em>“A perceived gap between an existing state and a desired state.” </em>In the equation, our “desired state” is one in which the left side is equal to the right. We know it’s possible, it’s just a matter of determining what X needs to be in order make it work. In order to cross the chasm and get to our desired state.</p><p>So after we’ve uncovered the equation, that’s when we really get to work. We interview various roles in the context of their workflows. We observe. We analyze. And we do this because we know that there is something missing. There is a <em>solution</em> lurking somewhere in this equation. A new <strong>X-</strong>perience that will bring balance (tacky, I know. But you’ll remember it). And we draw it out by framing and understanding the problem.</p><h3>Designing Solutions</h3><p>Once we’ve clearly framed our solution space and our problem space, the process of actually designing a solution isn’t as black &amp; white as algebra. Instead what you find is that each time you solve for X and you plug it back into the equation to test it, you learn that there is actually more to the equation than you originally thought or observed. And here is where the true maddening beauty of Experience Design lives.</p><h4>Example</h4><p>Let’s say I’ve come across this great design opportunity. I just met someone who is in dire need and she says…</p><blockquote>“I need something that I can fill with liquid and drink from.”</blockquote><p>Simple enough problem space, right? Container. Liquid. Drink. In the back of my mind I might even have a rough idea of what “<strong>X</strong>” might be …</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/392/1*APCVUOePvPAANByuhCLSNA.png" /></figure><p>But I want to understand a little more about this problem. So I say, <em>“Tell me more about this. What kind of things are you going to be drinking? Water? Milkshakes? Tea?”</em></p><blockquote>“Well… I need it for drinking coffee.”</blockquote><p>The problem is starting to change a little bit. So my rough idea of <strong>X</strong> changes with it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*qodzGToxyFj9hl2EQEa3yw.png" /></figure><p>I keep going.<em> “How will you be using this? Just around the house? Or taking it with you when you walk the dog, perhaps?”</em></p><blockquote>“Well… I need it for my hour long commute into work, so I’d like it to keep my coffee hot for a good while.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*tTpXgd8_DvKHCbIDltfE6w.png" /></figure><p><em>“OK… what about volume? Will one cup be enough for your commute? Should it hold more? An hour long commute is a pretty long time…”</em></p><blockquote>“Now that you mention it… It should probably hold about 2 cups.”</blockquote><p>I say, <em>“OK I think I have enough to get started. Let me take some time to synthesize this into a prototype and get your feedback.”</em> I return a few days later and present her with <strong>X1</strong>…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/298/1*C9roJjyotPZN7dLphQ2nsA.png" /></figure><p>And I say, “<em>I think I’ve got a great solution for you. It’s a metal thermos that will keep your coffee hot for hours. It holds 2 cups and it’s also got an easy sip lid, good for using while driving. Just what you need, right?</em></p><blockquote>“Well… I should have clarified. It has to be microwave safe. My Keurig has a tendency to make some lukewarm coffee so I like to microwave my coffee right before I leave.”</blockquote><p>The equation just changed. It’s not terribly different but I have to think about my solution a little differently now, don’t I? I begin to solve for <strong>X</strong> again based on what I now know.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/344/1*FDy-nb4hufoYwWRs0zpmXA.png" /></figure><p>I show her <strong>X2</strong>. <em>“How does this work? It’s ceramic and completely microwave safe. And I’ll tell you what, how about you take it for a test run in your car and see how it feels. Maybe we can get some deeper feedback that way.”</em></p><p>She returns from her test drive. I ask her how it went.</p><blockquote>“Hmm… I forgot to mention that the cupholder in my car is a little small and this unfortunately doesn’t fit. Also my hands were slipping on the ceramic. I’m afraid I might drop it…”</blockquote><p>Slight adjustments to the equation but we’re getting closer…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/1*3Be1nsxSVBHwyQnbXgfJGw.png" /></figure><p>Enter <strong>X3</strong>.<em> “Ok I made the shape taller and skinnier. I also added this rubber sleeve for extra grip.”</em></p><blockquote>“Great! This is perfect! It’s just…”</blockquote><p><em>“What…”</em></p><blockquote>“I hate purple.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/1*B9gB-AbXp0nJD28pKuVkFQ.png" /></figure><p>What happened there? Did we ever take a drastic turn away from the original equation? No, we refined our understanding of the problem and at the same time we refined our solution until the two were balanced…</p><p>Now here’s where things start to get interesting. Which of these would you say is the MVP in this example?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ZpJRaM7sIxQifEZWPY4Qw.jpeg" /></figure><p>As a designer I would argue that <strong>X3</strong> is our MVP. Our client doesn’t need the color change in order to start using this solution, realizing it’s value, and providing feedback. But the iterations prior to <strong>X3</strong> wouldn’t have solved her problem adequately.</p><p>Interestingly though, when I originally gave this talk at a ProductTank Meetup, many of the Product Managers in the audience leaned toward the initial three mental concepts that precede <strong>X1</strong>. One PM in particular made a strong case for the Yeti.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-sI4aDZEf-6DQKRZ2dFexQ.jpeg" /></figure><p>Who’s right? Both roles can undoubtedly make strong cases for their respective selections. So where does that leave us?</p><h4>Partnership and The Deliberation Space</h4><p>How many meetings have you participated in where the Product, Technology, and Design teams were in complete agreement? None? Yeah, same here. And we shouldn’t expect anything different. These are very different disciplines with very different perspectives on the solution being built. It takes <strong><em>balance</em></strong> between these disciplines in order to develop products that are meaningful, marketable, and memorable.</p><p>There is never going to be a definitive right answer in these kinds of discussions. There are priorities to be weighed and constraints to be considered. That is why I call this “The Deliberation Space.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hOZhBMfVpK7DMf7AxOSU4A.jpeg" /></figure><p>We’ve narrowed our focus and now it’s a matter of making a cross-functional decision as a team. This is hard. And the only way to do it effectively is if there is balance and mutual respect between disciplines.</p><p>When there isn’t balance, that’s when things get ugly…</p><p><strong>Product + Design</strong> without Technology is <em>Vaporware</em>. We have a great idea and people seem to want it. But we can’t build it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NzEcw5oMK6Ad4Fdt2EJRAA.jpeg" /></figure><p><strong>Design + Technology</strong> without Product is a <em>Hackathon Project</em>. It looks great and it’s even fully functional, but there’s no market for it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Dt5sYxa9WKw4OQGDCcF9g.jpeg" /></figure><p><strong>Product + Technology</strong> without Design is an <em>Office Printer</em>. The necessary evils of the world that are completely at risk of being disrupted by a customer-centric innovation. Think Netflix, Airbnb, Uber again (man it would be great if someone created the “Uber of Printers”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*svTCW7_dqczC397cXcrkxg.jpeg" /></figure><p>Alternatively, when there is balance between all three disciplines, that’s when you get amazing stories of success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DAqXIGJKvgzqNAhfrm8QQA.jpeg" /></figure><p>It’s not easy. It requires a lot of work and even more humility. But it should be the top priority of any product team. That’s where magic happens. That is how you solve for X.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1818099bdb9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>