<?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 Benjamiz on Medium]]></title>
        <description><![CDATA[Stories by Benjamiz on Medium]]></description>
        <link>https://medium.com/@benjamin.mizrany?source=rss-aa8c53c0114d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*oV9Ou42V1S-pgYew</url>
            <title>Stories by Benjamiz on Medium</title>
            <link>https://medium.com/@benjamin.mizrany?source=rss-aa8c53c0114d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:50:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@benjamin.mizrany/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[Your UI is a memory aid for a model you didn’t design]]></title>
            <link>https://medium.com/design-bootcamp/your-ui-is-a-memory-aid-for-a-model-you-didnt-design-75b239d12635?source=rss-aa8c53c0114d------2</link>
            <guid isPermaLink="false">https://medium.com/p/75b239d12635</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[domain-driven-design]]></category>
            <dc:creator><![CDATA[Benjamiz]]></dc:creator>
            <pubDate>Sun, 17 May 2026 09:17:44 GMT</pubDate>
            <atom:updated>2026-05-17T09:17:44.303Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S4oxM61uAHCz4OybHh2O_w.png" /></figure><p>Before I built a UI for my transcription tool ScribeFloat, I built it as a Python application and used a terminal alias `rec` to run it. It recorded audio, ran it through Whisper locally, and saved the transcript as a .txt. I started there because I genuinely didn’t know if I’d use the thing. Would I go to the trouble of opening a terminal to run it? Would the transcripts be accurate enough to read? It turns out yes to both. And working at that level, before touching a UI or designing a single screen, changed what I ended up building in ways I didn’t expect.</p><p>It also got me thinking about something broader: designers have always owned the presentation layer of a system while engineers owned the model underneath. That division is starting to matter in a way it didn’t before.</p><p>Most software systems can be thought of as having two layers. The model layer holds the objects the system manages, their attributes, the actions that can be performed on them, and the rules that constrain those actions. For a transcription tool that’s a recording, a transcript, a file path, a model selection. The presentation layer is the menus, buttons, labels, hierarchy, and surfacing complexity only when needed, that makes the model usable without a manual.</p><p>Designers were brought in to shape the presentation layer while engineers handled the model, because software emerged from technical infrastructure first and the boundary calcified from there. Why does the presentation layer need to exist at all? Because the average person can’t hold 50 commands in memory. You need the interface to signal what’s possible rather than requiring you to already know it: the visual cues that communicate how something can be used.</p><p>The CLI is what the model looks like without that scaffolding. `<em>git commit -m “fix login bug”</em>` doesn’t explain itself. The syntax is exact, error messages are often cryptic, and there’s nothing to browse. You know it or you don’t.</p><p>Power users use CLIs for exactly that reason. Once you know the model, the CLI is the fastest path through it. The alias takes that further: `<em>gs</em>` for `<em>git status</em>`, or `<em>rec</em>` for a 4-flag recording command I could never reproduce from memory. You compress a known operation into a single gesture, and after a few weeks the original command fades entirely. The alias is faster because it skips the thinking. Though it raises a question: when you run it six months later in a different context, can you remember what it actually does? Did you label it something sensible?</p><p>Back to ScribeFloat, because the story doesn’t end with `rec`.</p><p>After the alias validated the model, I piled on features. Voice search, session management, a status tracker showing what had and hadn’t been indexed. None of it got used. My behaviour never changed: record, process, move on. I’d made the mistake of assuming that validating one idea validated all the adjacent ones I’d assumed would follow from it. So I stripped everything back.</p><p>One thing I noticed at the terminal: I could only remember one command reliably, the record command. I still had ` <em>— list</em>`, ` <em>— view</em>`, ` <em>— transcribe</em>`, but I could never recall how to invoke any of them without checking. So I put a UI on top using a terminal UI (TUI). Functions and settings became visible. I stopped looking things up, and the learning curve dropped. The UI didn’t change the model at all; recordings still worked the same way, files still landed in the same place. What it did was make the model’s surface area navigable without requiring syntax recall. And yet `<em>rec</em>` in the terminal was still the main way I used the tool. The UI just made it easier to reach the edge functions when I needed them.</p><p>Working at the model layer first changed what I built and how I thought about iteration. The features that never got used, the commands I couldn’t remember, how rarely I reached for an edge function: each of those told me something about value. I could focus on validating the function without spending time obsessing about the form.</p><p>At the time I was also spending a lot of time with Claude Code, MCP, and other CLI tools, and it got me thinking about who else interacts with a system at the model layer.</p><p>AI agents don’t use the presentation layer. They interact through tool schemas: structured definitions that tell the agent what a tool is called, what it does, and what parameters it accepts. The agent reads the schema, decides whether the tool fits the task, and calls it. What it has is the model, described in text, with whatever precision or ambiguity the person who wrote the schema put there.</p><p>A tool with an ambiguous description gets called at the wrong time. A tool that bundles operations that should be separate produces unpredictable results. Too much superfluous information creates the same cognitive load problem that makes CLIs hard for humans. Poorly-specified tools make agents unreliable, just at a different speed, and the failure is harder to notice because the human still holds the real intent.</p><p>So the system has two consumers now. Humans, who need the presentation layer to navigate the model. Agents, who interact with the model directly and don’t touch the presentation layer. Tools like Figma AI and v0 have made generating the presentation layer increasingly routine, and teams generating interfaces without thinking about the underlying model are doing the same.</p><p>The conversation in design right now is mostly about going deeper into strategy and empathy as AI takes over execution, and that’s reasonable. But the model layer is getting more consequential for more types of system consumer, and it’s still being designed without much design input.</p><p>Designers who work only at the presentation layer are designing for a system they didn’t help specify. Sometimes what looks like a usability problem is a model constraint that was designed without understanding the user. That’s probably why domain-driven development exists, but it raises a question: how does a developer understand a user’s domain? And why is it normal for designers to engage confidently on UI decisions but glaze over when the conversation turns to schemas and entities?</p><p>One way in is to start with the objects in a system before defining screens or flows. An object is any entity the system manages: an audio file, a transcript, settings. Each has attributes (the data that describes it), actions that apply to it, and connections to other objects. It’s a framing that works for both designers and developers, and it gives you something to test with users before anyone opens Figma.</p><p>When you go through the attributes of an object with a user, you find out fast which ones they care about and which are just data the system happens to store. With ScribeFloat, the transcript object started with all sorts of metadata: duration, model used, file size, timestamps, hashtags. In practice I only ever looked at two things: word count and approximate token count, to know the cost of the transcript when passed to an LLM (damn Claude’s rate limits!). Everything else was noise I’d assumed would be useful.</p><p>That conversation is much cheaper to have at the object level than to discover through usability testing after a UI has been built around the wrong information. It also tells you something about hierarchy before you’ve drawn a single screen: what gets surfaced prominently and what gets buried.</p><p>The systems we build, whether used by humans or agents, still need to be designed with an understanding of user intent and how people actually behave. Designers are well placed to do that work. So next time your dev team starts a conversation about schemas, don’t glaze over because design work lives there too.</p><h3>Further Reading</h3><ol><li><a href="https://alistapart.com/article/object-oriented-ux/">OOUX - Sophia V. Prater</a></li><li><a href="https://ixdf.org/literature/topics/affordances">Affordances &amp; Signifiers - Don Norman</a></li><li><a href="https://link.springer.com/article/10.1007/s10664-021-10036-y">An empirical investigation of command-line customization - Michael Schröder &amp; Jürgen Cito</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75b239d12635" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/your-ui-is-a-memory-aid-for-a-model-you-didnt-design-75b239d12635">Your UI is a memory aid for a model you didn’t design</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Menagerie principles]]></title>
            <link>https://medium.com/design-bootcamp/the-menagerie-principles-2a2e42f6b8f1?source=rss-aa8c53c0114d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a2e42f6b8f1</guid>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[mindset]]></category>
            <dc:creator><![CDATA[Benjamiz]]></dc:creator>
            <pubDate>Wed, 19 Jun 2024 22:37:42 GMT</pubDate>
            <atom:updated>2024-06-20T19:55:31.032Z</atom:updated>
            <content:encoded><![CDATA[<h4>A metaphor to solve problems without certification</h4><figure><img alt="Cat, Dog and Rat" src="https://cdn-images-1.medium.com/max/1024/1*nFjZG6RtUMMippoScBPl_g.jpeg" /></figure><p>An off-the-shelf process can only take you so far. You will eventually reach the limit of what it can achieve in your specific context. When that happens, you must reject certain aspects of the process and find your way forward.</p><p>The Menagerie Principles, are the collective efforts to transform undesirable conditions into desirable ones. At its core, this framework leverages the metamorphic traits and behaviours of three symbolic animals: the cat, the dog, and the rat. Each represents a crucial aspect of creation and problem-solving, working strategically to achieve optimal outcomes. It is my initial stab at creating a metaphorical framework inspired by design thinking, lean, and agile methodologies, viewed through the lens of the icebreaker question: <strong><em>“Are you a cat or dog person?”</em></strong></p><h3>Menagerie</h3><p>The Menagerie represents the interactions between three mindsets which encompass continuous discovery, strategic preparation, and effective execution.</p><figure><img alt="infinity diagram of the RAT CAT and DOG" src="https://cdn-images-1.medium.com/max/1024/1*NYwFMgfflBZE63OdceN3eg.png" /></figure><p>The infinity diagram above represents the flow through RAT, CAT, and DOG. By answering questions, we gain knowledge, which allows us to create a clear direction. This enables us to act and receive feedback from our actions, which either clarifies our direction or raises more questions.</p><h3><strong>Conditions</strong></h3><p>Conditions refer to the states or situations that require transformation. An undesirable condition represents challenges or inefficiencies, while a desirable condition is the improved state achieved through a Deming Cycle (plan &gt; do &gt; check &gt; act). The Menagerie Principles highlight the mindsets needed to manage these conditions effectively, ensuring that the outcomes are beneficial and sustainable.</p><p>The <em>CAT</em> <em>RAT</em> and <em>DOG</em> symbolise three dimensions of working towards optimal conditions in complex environments. While they are particularly relevant to product design and development, I have defined them in ways that extend their usefulness to various contexts. These symbols can be applied to an individual, a team, or an organisation’s journey towards desirable conditions:</p><h3><strong>CAT: Conditioning, Alignment, and Triage</strong></h3><p><em>Efficiency comes from preparation and reflection.</em></p><figure><img alt="cat peeping its head out" src="https://cdn-images-1.medium.com/max/1024/1*OC9PiiJw3wQXO9oyHWy_Zg.jpeg" /></figure><h4><strong>Conditioning:</strong></h4><p>The act of articulating desirable and undesirable conditions, identifying the vital signs of deviation, and drivers to measure progress.</p><h4><strong>Alignment:</strong></h4><p>The act of creating clarity regarding what needs to be done, the dependencies involved, and the methods of execution.</p><h4><strong>Triage:</strong></h4><p>The act of comprehending the state of play, given the information available, and formulating strategies to move forward.</p><h3>Traits</h3><h4><strong>Independent:</strong></h4><p>Like cats, who often roam and hunt alone, <em>CATs</em> promote autonomy by ensuring alignment and direction clarity.</p><h4><strong>Agile:</strong></h4><p>Like cats are nimble and quick to react, <em>CATs</em> are adaptable and can pivot swiftly in response to new information and changing circumstances.</p><h4><strong>Territorial:</strong></h4><p>Like cats that mark and defend their territory, <em>CATs</em> ensure correct resource allocation, ensure the reproduction of success, maintain communication lines and set clear boundaries.</p><figure><img alt="Confident cat walking with purpose" src="https://cdn-images-1.medium.com/max/1024/1*QELv4MA8XOyUQt0--x7CJA.jpeg" /></figure><blockquote>“We achieve desirable conditions by understanding the why, the what, and the how.”</blockquote><h3><strong>A Good CAT</strong></h3><h4><strong>Clear Goals:</strong></h4><p>Clearly defined success criteria and measurable goals.</p><h4><strong>Shared Understanding:</strong></h4><p>There is confidence in the work to be done why it should be done and who and how they benefit as well as a clearly defined target condition to assess the work against.</p><h4><strong>Effective Prioritisation:</strong></h4><p>There is an ability to assess continuously and prioritise tasks based on current information and impact.</p><h4><strong>Resource Protection:</strong></h4><p>Resources are efficiently allocated and distributed sustainably, and successful strategies are replicated.</p><h3>RAT Stage: Remove, Analyse, and Test</h3><p><em>It doesn’t need to be perfect but it does need to be verified</em></p><figure><img alt="rats in a maze" src="https://cdn-images-1.medium.com/max/1024/1*UCFT3w5du_Cex5-IS_PL5w.jpeg" /></figure><h4>Remove</h4><p>The act of minimising waste and uncertainty.</p><h4>Analyse</h4><p>The act of processing feedback for actionable insights.</p><h4>Test</h4><p>The act of validating assumptions.</p><h3>Traits</h3><h4><strong>Resourceful</strong>:</h4><p>Like rats who find ways to make the most of their surroundings, <em>RATs</em> are similarly adept at utilising available resources to get the answers needed effectively and efficiently.</p><h4><strong>Empathetic</strong>:</h4><p>Like rats who are highly empathetic creatures, displaying remarkable empathy-driven behaviour. <em>RATs</em> leverage this empathy to understand and address the needs and challenges of others, finding solutions to complex problems in innovative ways.</p><h4><strong>Quick Learners</strong>:</h4><p>Like rats, who possess remarkable learning abilities and can rapidly acquire new skills and information. <em>RATs</em> should quickly learn and adapt, rapidly acquiring the knowledge to solve problems efficiently.</p><figure><img alt="a group of three rats working tinkering with a machine" src="https://cdn-images-1.medium.com/max/1024/1*nwUODYED6ccb3yNkXlDP3Q.jpeg" /></figure><blockquote>“We recognise that we can increase our chances of creating desirable conditions when we remove uncertainty and waste through rapid exploration and validation of assumptions.”</blockquote><h3><strong>A Good RAT</strong></h3><h4>Clarity</h4><p>The outcome of <em>RAT</em> work helps to focus the direction towards the target condition.</p><h4>Defined</h4><p>The <em>RAT</em> work and its intended outcomes are predefined.</p><h4>Actionable</h4><p>Work has a bearing on what needs to be done, and the insights gathered from <em>RATs</em> directly feed into achieving desirable conditions.</p><h4><strong>Economic</strong></h4><p>The quality of the work lies in the insights acquired and the ability to get answers efficiently without excessive use of resources.</p><h3>DOG Stage: Deliver, Operationalise, and Guarantee</h3><p><em>We know what, how and why it should be done. Now let’s get it done.</em></p><figure><img alt="close up of a dog from the neck up" src="https://cdn-images-1.medium.com/max/1024/1*CdQ3nGRdN24NjoNUU3GqXg.jpeg" /></figure><h4>Deliver</h4><p>The act of creating solutions that move things closer towards desired conditions.</p><h4>Operationalise</h4><p>The act of ensuring what is delivered can be consistently done at scale.</p><h4>Guarantee</h4><p>The act of ensuring high standards of quality to maintain the longevity of desirable conditions.</p><h3>Traits</h3><h4>Loyal</h4><p>Like a loyal dog, <em>DOGs</em> are committed to the mission and dedicated to delivering value.</p><h4>Protective</h4><p>Like dogs who are protective of those they are loyal to; similarly, <em>DOGs</em> are guardians of quality and protect against the degradation of positive behaviour.</p><h4>Disciplined</h4><p>Like how a disciplined dog is a good dog. <em>DOGs</em> that train and seek positive feedback are more likely to produce quality work and achieve desirable conditions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8mA6FGywK5A2i-Y5GPBstg.jpeg" /></figure><blockquote>“We recognise that we can create desirable conditions, at scale, through consistent high standards of quality”</blockquote><h3><strong>A Good DOG</strong></h3><h4>Positive Impact</h4><p>The solutions meet or exceed the expectations of the outcome of the desired condition.</p><h4>Scalable Processes</h4><p>Operational practices are continually improving and scalable, ensuring consistent and reliable delivery.</p><h4>High Standards</h4><p>Safety, security, quality, and reliability are prioritised, maintaining high standards throughout.</p><h4>Choreographed</h4><p>Efforts are well-coordinated and synchronised, ensuring all aspects of the project are executed seamlessly and efficiently.</p><p>Using the menagerie principles, one can easily visualise ways to perform work, allowing for a more fluid approach towards achieving desirable conditions and the ability to integrate these principles into existing behaviours.</p><figure><img alt="image of 3 track streams of focus with cat work throughout and in the middle and Rat and dog work in segments dog work following on from the feedback of rat work" src="https://cdn-images-1.medium.com/max/1024/1*XEOoZ5--pDGLdwAMHETA1w.png" /><figcaption>\</figcaption></figure><p>This is one way to visualise the work, with <em>CAT</em> (consideration) as the constant between <em>RAT</em> (answering questions and validating assumptions) and <em>DOG</em> (delivering work), while continuously getting feedback and moving towards desirable conditions.</p><p>I realise I’ve failed to emphasise the need for continual iteration. Although it’s implied, it’s not explicitly stated. The image above mirrors the idea of a dual-track agile approach, where validation and clarity of work are done before operationalising, but all activities are performed iteratively.</p><p>Another thing to note is that the menagerie can occur between thinking about an action and the action itself. For instance, walking on suspect ice involves constantly assessing (<em>CAT</em>), with every step, whether the ice will break. Sometimes, the ice may crack, and you have to apply slight pressure (<em>RAT</em>) to see if it can take your weight before fully committing to a step (<em>DOG</em>).</p><p>This is a concept to help solidify the mindset, not a framework that should be followed like a gospel.</p><h3>Books that helped inspire</h3><ul><li><a href="https://www.amazon.co.uk/INSPIRED-Create-Tech-Products-Customers-ebook/dp/B077NRB36N">Inspired</a></li><li><a href="https://www.amazon.com/Lean-UX-Designing-Products-Second/dp/B08VKWDFKK/ref=sr_1_2?crid=17C5J2YH6EBNU&amp;dib=eyJ2IjoiMSJ9.D8FNEAT4Xm4NgRA-pSsdjDMYFe41K1yB5wp45_iuQT-34MnxuAQz588gp9YhIYnW_hnZ9mBZ1rUcCxVkpSpfMaKNMhQP-9QbxP_zeAActj8.0lzYSY8JsvkfWAL8GxnQfAoQDXqTP9oGrCo11WQWUzA&amp;dib_tag=se&amp;keywords=Lean+UX&amp;qid=1718836499&amp;s=audible&amp;sprefix=lean+ux%2Caudible%2C190&amp;sr=1-2">Lean UX</a></li><li><a href="https://www.amazon.com/Lean-Enterprise-Performance-Organizations-Innovate/dp/B08CS2X4PT/ref=sr_1_1?crid=1KL8RJNH7QX2R&amp;dib=eyJ2IjoiMSJ9.yC8p37u54Jqd-Q2arVrq-TwCKMrupJ-T4M_wphuRv4UuQ21YyEdXbkt_1exD19gCn-OuR651t56A8vdYYhNNgcfzOchwasLKeRC0dDAxhaSpt3HuD7xUp-_kkaF0glinQrzbdUgoo6_PnOUGE09hy7bpyvnXlHrQwdZ1cEkRYWdJv45Ud1p14W_I611Fruap2rcKn1j6eK-MaDFDb2BQ1OOPkgBtUVT4m6Y-7h8_0Gk.fOKncqcqYiCLoCj9-XD9VVn6J0bGqnYYtL_LBk8_9Tw&amp;dib_tag=se&amp;keywords=Lean+Enterprise&amp;qid=1718836481&amp;s=audible&amp;sprefix=lean+enterprise%2Caudible%2C174&amp;sr=1-1">Lean Enterprise</a></li><li><a href="https://www.amazon.com/Continuous-Discovery-Habits-Discover-Products/dp/B09XYX49KX/ref=sr_1_1?crid=1W1WYXIN0237R&amp;dib=eyJ2IjoiMSJ9.nyh5VSVfQcfODjuiJDtBtgo_EkqNGiGb24FoLvF5tQrGjHj071QN20LucGBJIEps.wQQ22oTCz9YECe57eepsDTMXa8KT43_qpOgawAOO6U4&amp;dib_tag=se&amp;keywords=Continuous+Discovery+Habits&amp;qid=1718836462&amp;s=audible&amp;sprefix=continuous+discovery+habits%2Caudible%2C179&amp;sr=1-1">Continuous Discovery Habits</a></li><li><a href="https://www.amazon.com/Art-Action-Leaders-Between-Actions/dp/B098BKYZGG/ref=sr_1_1?crid=WLGRCZXQE868&amp;dib=eyJ2IjoiMSJ9.9rz56W_zP0OWVaFTCBCR0OU5XirJnqi8-3yu4nCSeeRTsjmtIp69px6EpifJcAEXdxNNBRkPx-S0PYDLq7PaoGPna6qMPGMe8z4yEQkWKG4exGtzKLuFc0sUzNcEeV1xkm2W2R0kIGGwDjU1LK8iNmARILstrAIAMgacP29wj66U_KgQzBk0AgEsg4mRFgnoEsAA-ikQNJ3vXcIXMsW0eRlp9Ns9bt-FN0SgxPulv3k.5pRj6SDva1A_uzBmac9CIKnNxThEAxsPgsKh1ip6SvI&amp;dib_tag=se&amp;keywords=The+Art+of+Action&amp;qid=1718836437&amp;s=books&amp;sprefix=the+art+of+actin%2Cstripbooks-intl-ship%2C171&amp;sr=1-1">The Art of Action</a></li><li><a href="https://www.amazon.com/Right-Many-Ideas-Yours-Succeed/dp/0062884654">The Right It</a></li><li><a href="https://pragdave.me/thoughts/active/2014-03-04-time-to-kill-agile.html">Agile is dead (long live agility</a>)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a2e42f6b8f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-menagerie-principles-2a2e42f6b8f1">The Menagerie principles</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design is all “BS”]]></title>
            <link>https://medium.com/design-bootcamp/design-is-all-bs-7f0202f35180?source=rss-aa8c53c0114d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f0202f35180</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-researcher]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Benjamiz]]></dc:creator>
            <pubDate>Mon, 25 Mar 2024 13:17:43 GMT</pubDate>
            <atom:updated>2024-03-26T00:56:10.696Z</atom:updated>
            <content:encoded><![CDATA[<h4>The first lesson of being a designer is the art of Believing and Selling (BS)</h4><p>Designers are frequently advised to articulate their problem-solving process and solution development strategy. Like any craft, designers possess a toolkit comprising various tools — user interviews, wireframes, prototypes, and workshops, to name a few. However, not every tool is suited for every challenge. Part of being a good designer is knowing which tool is the most appropriate for the specific problem at hand.</p><figure><img alt="Hand-drawn process diagram showcasing steps from ‘opportunities/solutions’ to ‘consensus on where to start’, with intermediary steps labeled ‘open’, ‘explore’, and ‘close’. Arrows connect the phases of refinement and validation, depicted by clustered circles with some highlighted, to illustrate the workflow in idea development." src="https://cdn-images-1.medium.com/max/1024/1*04jGKfZRKpgNn3e_otf2dw.png" /></figure><p>The Double Diamond method focuses on divergent and convergent activities during two key phases: discovery, where opportunities are identified and validated, and delivery, where solutions are refined for consumer use. Ideally, this involves continuous collaboration, minimising handovers.</p><figure><img alt="Sketch of the double diamond design process in action, with the phases labeled ‘Outsider Idea’, ‘Retroactive Discovery’, ‘Wireframe’, ‘Delivery Sprint’, and ‘Release’. Arrows depict the flow, with icons like a light bulb, a stick figure, a thumbs-up, and a question mark to symbolise the transient nature of designs input." src="https://cdn-images-1.medium.com/max/1024/1*_xFAatgoo9fqeEfHurzX_Q.png" /></figure><p>However, team-wide learning isn’t always feasible. So as a product designer, I find myself riding solo through the diamonds, or sometimes being pulled into particular parts of the process to get my nod of approval. Given my non-dev or manager status I understand my role as fostering and advocating two areas within the two diamonds.</p><h4>Visualising and validating the vision</h4><ul><li>Visualising or rendering the direction of the product in line with real human needs</li><li>breaking up that vision into deliverable chunks that are usable, and lovable.</li></ul><h4><strong>Continuously cultivating consistency</strong></h4><ul><li>Ensuring what we build aligns with users’ mental models, drawing from either our past projects or their experiences outside our technology</li><li>the customer and end user experience has been consciously curated, in a way that can be implemented at scale.</li></ul><p>Ideally, design has been embedded from the very beginning of every project, so that we can do the above effectively. using design thinking to spot opportunities for delivering customer value in ways that also align with business strategy.</p><p>However, often, in reality:</p><ul><li>The decision has already been made without design input</li><li>The “vision” (a predefined set of functional requirements) has already been established</li><li>The expectation of design’s input is to make wireframes.</li></ul><p>So, in the words of Forrest Gump’s mother,</p><blockquote>“You have to do the best with what God gave you.”</blockquote><p>In a product delivery lifecycle that lacks validation, visualisations, consistency, or design collaboration, a “Believe and Sell” or “BS” design process emerges. This method focuses on the designer’s sanity by piecing together a narrative of a design process that slightly aligns with the designer’s professional standards.</p><p>It acknowledges that the only reason a design process exists is due to the presence of the design function. Yet, outside the designers’ circle, the value and impact of their work on achieving measurable success seem to be a non-issue, until there is a need to tighten the belt.</p><h3>Believe it</h3><figure><img alt="Sketch of a figure tied to a stake with the caption ‘I Believe!’ indicating a willingness to face consequences for their beliefs, surrounded by onlookers with one holding a flame, and another caption stating ‘We do not’, symbolising opposition." src="https://cdn-images-1.medium.com/max/1024/1*A9-7BiivMEfLFe3e9xXXVw.png" /></figure><p>Belief is interesting because it doesn’t need evidence, yet some people will give their lives for their beliefs. On the flip side, without belief, efforts seem lacklustre. It’s critical to develop a working process that builds a belief in the value of what you’re doing but is grounded in empirical evidence.</p><ul><li>Understand why your work matters to your users, customers and the business.</li><li>Identify where the value lies for users and how that value aligns with business objectives; so you can concentrate your efforts effectively.</li><li>Validate Solutions to ensure they’re worth pursuing. if anything elicits apathy, it needs a solid reason to remain.</li></ul><p>You first need to convince yourself before you can convince others. The hope is you have cultivated a degree of business acumen which means it takes more than consistent white spacing and proper accessibility standards to convince you of a solution you have spent time on.</p><h3><strong>Sell it</strong></h3><figure><img alt="A hand-drawn depiction of a soapbox with the phrase ‘where you want to be’ floating above it. The image suggests the concept of expressing opinions or ‘getting on a soapbox’ to share a message." src="https://cdn-images-1.medium.com/max/1024/1*KTYU2etL1ax6ty6cmxQOwg.png" /></figure><p>This involves convincing those who weren’t part of the journey of belief. You’ll need to effectively convey your insights, and design rationale with supporting evidence to ensure others grasp the design’s purpose and potential impact, even if they weren’t part of the key insights that shaped its direction (there is a lesson here to come back to).</p><p>The challenge is in navigating pushback, which generally arises for two reasons:</p><ul><li>They fail to understand the ROI</li><li>They prefer a different idea</li></ul><p>The latter scenario — not incorporating a specific idea from a person of influence — is particularly tricky. It requires a careful balance of empathy, strategic communication, and evidence-based persuasion.</p><p>When faced with questions like “Where is the return on investment?” or “What about my idea I told you about?”, it’s essential to:</p><h4>Demonstrate Value:</h4><p>Clearly articulate how the design aligns with business goals and user needs, emphasising the value and impact relative to the effort required.</p><h4>Rationalise Design Decisions:</h4><p>If certain ideas were not included, explain why, using research, user feedback, or strategic considerations to justify your approach and how it serves the overall objectives.</p><figure><img alt="Hand-drawn image of a person presenting a wireframe on a whiteboard with geometric shapes one being a triangle where a square should clearly go, while two observers discuss a change, suggesting ‘that should be a square!’." src="https://cdn-images-1.medium.com/max/776/1*df482QI6abbnyc4Mue2Z4g.png" /></figure><blockquote>Hot tip: Bring a design problem to the pitch as a talking point for internal stakeholders to solve in the meeting. Like designers, everyone wants to feel included, heard, and recognised for their genius.</blockquote><h3><strong>Warning signs and thoughtful sighs</strong></h3><figure><img alt="Hand-drawn illustration of a figure pushing a large boulder up a hill within a triangular warning sign, symbolising an uphill struggle or a Sisyphean task. The image conveys the concept of a challenging or seemingly endless endeavour." src="https://cdn-images-1.medium.com/max/1024/1*d32NNUV4qbyQFg_gWD_Vyg.png" /></figure><p>Selling your design can be challenging. Addressing the need for evidence of its value with clear data might meet some demand, but convincing others to let go of their ideas for a data-backed design is tough.</p><p>Also, remember you are grappling with your own biases. Your pitch needs to demonstrate openness to being wrong and readiness to pivot. Convincing others to relinquish their “solution baby” is nearly impossible if you are not prepared to do the same with yours.</p><p>Continuous engagement and discussion about your design with team members, including those in leadership positions, enhance the chances of gaining support. Refining your approach to address these nuanced concerns and objections is key to navigating the complexities of selling your design effectively.</p><p>It’s important to recognise that group dynamics can significantly affect interactions. Conversations held in a group setting often unfold differently compared to those with individuals in private. This discrepancy is rooted in various social and psychological factors, including the desire for conformity, peer influence, and the public versus private self.</p><p>When navigating feedback and discussions about your designs, both settings — individual and group interactions — should be strategically managed to ensure that genuine insights and opinions are accurately gauged and addressed.</p><p>The Double Diamond and design thinking are valuable frameworks for those unsure of where to begin with implementing design into their product development lifecycle.</p><p>If the people around you don’t share the values of empathy and validation, it can be difficult to communicate with them. It can feel like speaking a foreign language in a small town in Dorset — few will understand you, and many will ask if you can just speak English.</p><p>Hence, it’s useful to develop a design process that incorporates a bit of “Believe and Sell” or, “BS”.</p><p>One could probably argue that all product development and business involves some “BS”.</p><p>Further exploration:</p><p><a href="https://youtu.be/Y_hYv84KJOM?si=YGtkqThjppihQtv1">Doing is the Hard Part: How to Embed Service Design in Organisations</a></p><p><a href="https://www.youtube.com/watch?v=VFgH5GQc_UM">The two week rule</a></p><p><a href="https://www.youtube.com/playlist?list=PLJOFJ3Ok_iduKLPT5n2IQr-at29zhPS4E">NN/group design ops</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f0202f35180" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/design-is-all-bs-7f0202f35180">Design is all “BS”</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clarity in collaboration: Describe a bicycle exercise]]></title>
            <link>https://medium.com/design-bootcamp/clarity-in-collaboration-describe-a-bicycle-exercise-960297742e59?source=rss-aa8c53c0114d------2</link>
            <guid isPermaLink="false">https://medium.com/p/960297742e59</guid>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Benjamiz]]></dc:creator>
            <pubDate>Sat, 09 Dec 2023 20:51:27 GMT</pubDate>
            <atom:updated>2023-12-10T08:42:39.040Z</atom:updated>
            <content:encoded><![CDATA[<h4>The power of detailed communication and shared vision in team dynamics</h4><figure><img alt="A group of five professionals in a meeting, with a thought bubble collectively imagined above them, containing geometric shapes: a tetrahedron, an octahedron, a dodecahedron, and a cube. One of them is pointing to a whiteboard that reads “I need a shape.”" src="https://cdn-images-1.medium.com/max/1024/1*A77fKwsjzwNV-M6yVOaChA.jpeg" /></figure><p>When people create something, like software or a product, what they make is not the perfect version of what they want. Instead, they are making something close to, but not exactly, the ideal version in their mind. This ideal version is based on what experts think, what customers want, and what is needed for the business.</p><p>The problem is that everyone involved might have a slightly different idea of what this perfect version should be. Also, there are limits like time, money, and the tools they use, which affect how close the final product can be to this ideal version.</p><p>As the project goes on, the team learns more and adjusts their work and gets closer to this ideal version. They constantly (consciously or unconsciously) refine their understanding and the product, based on new information and feedback.</p><p>This journey towards a vision is littered with challenges one of which is ensuring that everyone on the team shares a similar understanding of the goal. However, do we truly appreciate how different our individual interpretations of a common concept can be?</p><p>While thinking about how to combat this issue of individual interpretations, I realised that the first thing that needs to be tackled is awareness of the issue. So, I came up with the ‘Describe a Bicycle’ exercise. It’s an exploration into how each member interprets a simple concept like a ‘bicycle’ in varied and unique ways.</p><p>The essence of this activity lies in its ability to showcase the importance of clear, detailed communication. It demonstrates that even when we agree on a general concept, the specifics can vary greatly from person to person. But it’s this understanding which is crucial in project development, where details matter and the alignment of these details among team members can significantly impact the outcome.</p><p>This exercise reveals the difference between a basic theoretical grasp of a concept and the ability to turn that concept into a detailed, tangible description ready for creation. It highlights how each individual’s interpretation of a simple idea can evolve into unique, detailed descriptions. If these interpretations are misaligned, it can lead to inconsistencies in the final creation, underscoring the need for continuous alignment and communication within the team.</p><blockquote>“Ideas scatter when details don’t matter”</blockquote><h3><strong>Describe a bicycle exercise</strong></h3><figure><img alt="A creative team in a brainstorming session around a table covered with papers, sticky notes, and design materials. A man stands presenting a bicycle image on a whiteboard to his attentive colleagues." src="https://cdn-images-1.medium.com/max/1024/1*y7RLAQlEKOBO9Q5MeEd-kA.jpeg" /></figure><h4>Purpose of the Exercise:</h4><p>This activity is designed to highlight the importance of alignment and detailed understanding within a team working on a product. It emphasises the need for clear, specific communication and understanding of a common goal by showing that while everyone may agree on a broad concept, their interpretations of the details can vary significantly.</p><p><strong>Materials Needed:</strong></p><ul><li>Pen and paper for each team member.</li><li>Timer.</li></ul><p><strong>Duration:</strong></p><p>Approximately 15–20 minutes.</p><h4>Activity Brief:</h4><ul><li>Ask the team to imagine a bicycle.</li><li>Explain that each member will need to describe their imagined bicycle in detail as if it were physically present.</li><li>Emphasise the need for specifics — the description should be unique enough to distinguish their bicycle from others.</li></ul><h4>Individual Description (5 min):</h4><ul><li>Set a timer for 5 minutes.</li><li>Each team member writes indivually a detailed description of their imagined bicycle.</li></ul><h4>Sharing Descriptions:</h4><ul><li>Go around the room, allowing each member to share their description.</li><li>Listen to each description attentively.</li></ul><h4>Debrief and Discussion:</h4><ul><li>Explain that the exercise was more than just describing bicycles; it was about understanding how different perceptions can affect a team project.</li><li>Highlight that each person’s unique description reflects how varied interpretations of a simple concept like a bicycle can be.</li><li>Invite the team to imagine what the bicycle would look like if it were created using elements from everyone’s descriptions.</li><li>Reflect on how this ‘composite bicycle’ might be impractical or illogical, illustrating the challenges of unclear or misaligned visions.</li><li>Discuss the importance of clear and detailed communication in product development.</li><li>Emphasise how different perceptions, if not aligned, could lead to a final product that doesn’t meet the intended purpose or user needs.</li><li>Conclude by stressing the need for regular check-ins and clarifications among team members to ensure everyone is aligned with the project’s goals and requirements.</li></ul><p><em>Note: Ensure that the team does not become aware of the real purpose of the exercise until the debrief, to maintain the authenticity of their responses.</em></p><h4>Example Script:</h4><p>“<em>Hello everyone, let’s gather for a quick team exercise. Today, we’re going to do a simple but revealing activity. I want each of you to imagine a Bicycle. Think about its appearance, its function, how and when it’s used, its user, and any distinctive features. Now, write a description of this bike. Be as detailed as possible — imagine you’re describing it so someone could pick it out from a large bike rack. You have 5 minutes for this.</em></p><p>[After 5 minutes]</p><figure><img alt="A focused design team engrossed in sketching, with thought bubbles above them containing various bicycle designs. The group is intently working on tablets and papers, collaborating on a project." src="https://cdn-images-1.medium.com/max/1024/1*-Qqd2xUoiNALViWZsvxzHQ.jpeg" /></figure><p><em>Let’s hear your descriptions. </em>[Proceed with sharing]</p><p><em>Thank you for your participation. The aim of this exercise was to demonstrate that even with a common understanding of a concept — like a bicycle — each of us has a unique interpretation. In our work, when we talk about our product or project goals, it’s crucial to be as specific as possible to ensure we are all aligned and working towards the same detailed vision. This is why constant checking for understanding and alignment is essential in our team.</em>”</p><h3>Further Activity: Identifying and Combating Vagueness in Team Communication</h3><h4>Extend the exercise:</h4><p>After completing the ‘Describe a bicycle’ exercise, the team can extend the activity to address common issues of vagueness and lack of detail in team communication. This part of the exercise focuses on identifying and overcoming ‘dark patterns’ of communication, where important details are often overlooked or not clearly expressed.</p><figure><img alt="A team of professionals is gathered around a whiteboard filled with words and sketches relating to ‘Communication’ strategies. They are actively engaged in a discussion, with one person pointing at the board while others look on thoughtfully. The setting is an office with a large window in the background." src="https://cdn-images-1.medium.com/max/1024/1*jLsximk-kPceVGbV__lDdg.jpeg" /></figure><h4>Discussion on Vagueness:</h4><p>The team discusses examples of vague communication they have encountered and its impact on project work.</p><h4>Identifying Indicators:</h4><p>Develop a list of ‘red flags’ that indicate when communication is becoming too vague or details are being skipped.</p><h4>Strategy Development:</h4><p>Collaboratively come up with methods and practices to improve focus and clarity. This could include setting standards for communication, using specific project management tools, or regular check-ins to ensure clarity.</p><h4>Implementation Plan:</h4><p>Decide how these strategies will be implemented in day-to-day work.</p><figure><img alt="A collaborative team is centred around a table, focusing on a sheet of paper with various diagrams, symbolising a planning or brainstorming session. Above them, a series of lightbulbs hang at different heights, with one illuminated, representing an idea or solution being realised." src="https://cdn-images-1.medium.com/max/1024/1*w96bUH5kCg8o_PCI4Mnxeg.jpeg" /></figure><p>The ‘Describe a bicycle’ exercise, aims to give a team a deeper appreciation for the necessity of concise communication and the vital role of collective understanding in collaborative projects. This activity serves as a metaphor for the challenges we face in product development, where each team member’s unique perspective and expertise contribute to shaping the outcome. It reinforces the idea that while we may share a common goal, the path to achieving it is paved with diverse interpretations and ideas. By ensuring detailed, clear communication and continually testing and refining our visions, we can work more effectively towards creating products that not only meet but exceed our collective expectations. Remember, the strength of our team lies in our ability to understand, respect, and integrate our varied perspectives into a cohesive and successful product.</p><h3>Further resources:</h3><p><a href="https://learn.microsoft.com/en-us/archive/msdn-magazine/2009/february/best-practice-an-introduction-to-domain-driven-design">Best practice: An introduction to domain driven design</a></p><p><a href="https://youtu.be/AorAgSrHjKM?si=cUX5cr_IJVi1jeJl">User story mapping with Jeff Patton</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=960297742e59" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/clarity-in-collaboration-describe-a-bicycle-exercise-960297742e59">Clarity in collaboration: Describe a bicycle exercise</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The loner in the corner: The struggle of designers in cross-functional teams]]></title>
            <link>https://medium.com/design-bootcamp/the-loner-in-the-corner-the-struggle-of-designers-in-cross-functional-teams-86a0dfa3c6b6?source=rss-aa8c53c0114d------2</link>
            <guid isPermaLink="false">https://medium.com/p/86a0dfa3c6b6</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Benjamiz]]></dc:creator>
            <pubDate>Wed, 29 Nov 2023 06:13:32 GMT</pubDate>
            <atom:updated>2023-11-29T10:24:34.120Z</atom:updated>
            <content:encoded><![CDATA[<h4>Accepting the human element in product development that drives business value.</h4><figure><img alt="A black and white illustration, in the foreground, a man sits alone at a table, appearing contemplative or disengaged from the activity around him. In the background a diverse group of seven professionals engaged in a discussion around a whiteboard." src="https://cdn-images-1.medium.com/max/512/1*XnJMZf_uekvi_5a_a6zKDA@2x.jpeg" /></figure><p>Why do designers often feel marginalised within cross-functional product teams? This exploration delves into the root causes of this prevalent sentiment in the tech industry.</p><p>As a product designer, I’ve witnessed and experienced tension between design, product, and engineering teams. My design colleagues, both within my circle and in the wider field, echo this sentiment, observing a distinct divide between the design function and the rest of the product development team.</p><p>This topic came to the forefront in a recent meeting I attended, where a Scrum Master sought insights into how design could be more seamlessly integrated into agile practices. This prompted me to consider a fundamental issue: while the roles of engineers and the command of product managers are clearly defined and recognised, the place of design in this mix is often ambiguous and undervalued.</p><p>Unlike engineers, who implement technology and have strength in numbers, or product managers, who have decision-making power, designers often find themselves alone and in a more ambiguous position. This lack of power in numbers or defined authority leads to an often overlooked power dynamic.</p><p>In the modern digital era, with technology at every turn, user experience isn’t just a critical element in business competition; it’s also become a popular buzzword. Some use it without fully grasping its implications, while others follow the trend without question. The McKinsey Design Index (MDI) study sheds light on this phenomenon, showing that successful design in business is not just about user experience. It’s a comprehensive blend of usability, functionality, and strategic implementation. Companies that score highly on the MDI aren’t just ticking boxes; they see real-world rewards. As McKinsey’s “<a href="https://www.mckinsey.com/capabilities/mckinsey-design/our-insights/the-business-value-of-design">The Business Value of Design</a>” points out, this is reflected in their revenue and shareholder returns. Here, the emphasis is on the real, measurable benefits of weaving thoughtful design into the fabric of business operations.</p><p>Design in software development is about crafting the journey for the user, creating the unwritten narrative, an impression, and the direction of the interface. A skilled designer can craft experiences that resonate deeply with users, evoking emotions and effortlessly guiding them towards desired outcomes without the need for additional interventions. This aspect of design serves as a form of unspoken and unwritten communication, crucial in shaping the user’s interaction and behaviour with technology.</p><figure><img alt="A black and white sketch of a woman sitting at a desk, working on a graphics tablet connected to a computer with design software on the screen, with personal items like a smartphone, notepads, and stationery in view." src="https://cdn-images-1.medium.com/max/512/1*a9oCnKD500vwpKAEm23Wig@2x.jpeg" /></figure><p>In more general terms, design is the coherent representation of approaches to achieve specific outcomes. Saul Bass, a renowned graphic designer and filmmaker, aptly described it as <em>‘Design is thinking made visual’.</em> Within software development, design is then also converting the team’s abstract ideas into concrete, visual forms that can be shared and refined with stakeholders and users. So, design in software goes beyond focusing on the end product’s user experience; it also plays a pivotal role in bringing the team’s vision to life.</p><p>Product ideas, before creation, are ephemeral and require focused and considerate extraction, bringing those fuzzy notions into the real world and putting them under the spotlight. Without being sketched out, it is all a theoretical concept riddled with unknowns. Only when you bring those ideas out of the mind and into the real world can they be measured for their likelihood of success.</p><p>A team member’s role, shaped by their individual skills and experiences, creates a distinct perspective and a set of priorities. For a product designer, the core objective is to thoroughly understand and meet the needs and desires of end users, ensuring their interaction with software is effective and intuitive. This user-centric approach is pivotal for designers, but if it were the focus of every team member, the essence of a cross-functional team would be lost. However, emphasising end users does lead to another crucial point. Despite the growing recognition in industry literature that product teams should regularly engage with users, customers, and stakeholders, this practice is surprisingly not widespread.</p><p>Within a team discussion, ideas, considerations, assumptions, and priorities all jostle and compete for space in the conversation. Within this chaos, it’s inevitable that choices are made (consciously or subconsciously) about what to discuss and for how long. When you are a lone voice with a non-critical perspective, it’s easy for that perspective to be diluted in the end result.</p><figure><img alt="A black and white illustration of five people from the back, looking at a whiteboard with thought bubbles containing different geometric shapes and the statement ‘I NEED A SHAPE.’, suggesting a conceptual or problem-solving discussion." src="https://cdn-images-1.medium.com/max/512/1*2ti7N6eDJGE8ceWteJz-3Q@2x.jpeg" /></figure><p>In this whirlpool of dialogue, decisions and ideas often lack the grounding of direct user validation. Such validation is crucial; it ensures that choices reflect real user needs and are not just theoretical or assumption-based. Engaging with users provides concrete feedback, bridging the gap between what the team thinks users want and what they actually need. This missing link of user validation is key to making informed, effective decisions in product design.</p><p>The challenge for designers in product teams is rooted in how businesses prioritise and define success. Typically, a team’s focus is shaped by the business’s needs. Developers play a crucial role here; without them, there’s no software. Product managers align team efforts with business goals and provide reassurance that these goals are being met. Similarly, the operational oversight provided by roles like delivery managers or Scrum Masters is vital to ensure work is completed efficiently and within budget.</p><figure><img alt="A monochrome illustration of five professionals around a board with the title ‘MUST-HAVE FEATURES’ checked off on a list, celebrating presumably a successful project with a woman in the centre raising her fist in a triumphant gesture." src="https://cdn-images-1.medium.com/max/512/1*QCgsdHSZY-7QrgPSWSVEYw@2x.jpeg" /></figure><p>However, when success is measured solely by timely completion within budget to specific functional requirements, the need for a designer who offers more than pretty UI becomes less apparent. Designers’ true value lies in ensuring human-centric outcomes, not in completing outputs. Their contribution is in increasing the likelihood of a positive and successful outcome for the end user. In an output-over-outcome environment, designers face an uphill battle, and their input is often seen as a slowdown to completion, an increase in scope, or a ‘nice-to-have.’</p><p>Before design can be truly implemented into a product development team, how the business and teams measure the success of work needs to be rooted in human outcomes.</p><blockquote>‘The product teams exist to serve the company’s customers in ways that meet the needs of the business.’</blockquote><blockquote><em>- Marty Cagan, Inspired</em></blockquote><p>This inherently means measuring success by the outcomes for the users who use the product. After all, regardless of who makes the purchase, it is ultimately humans who use the product, and if it fails to meet the needs of those users, then it becomes a wasted investment.</p><figure><img alt="A detailed black and white drawing of four individuals seated around a table in a brainstorming session, with two women standing and pointing to areas of the whiteboard, which is filled with diagrams, UI designs, and notes." src="https://cdn-images-1.medium.com/max/512/1*7AvOwvgljH8VN0lzNClXpA@2x.jpeg" /></figure><p>In the absence of being able to shape this change in measuring success, one thing a designer or team can do to promote inclusivity and guard from marginalisation is to look at how often a whiteboard is being used to follow the flow of the conversation. As well as this, who is doing that recording and how often? What is physical is referenced and its narrative is able to be followed, thus those who record, shape the conversation. I would argue everyone on the team should become proficient in this skill as the ultimate goal is to have the whole team at the Whiteboard, rubbing things out, and adding new things. By encouraging every team member to contribute to the whiteboard dialogue, we create a visual and dynamic record of our collective understanding and are better able to visualise what we are missing. Designers, by harnessing their visual thinking tools, can effectively ensure that their perspectives are not only recorded but also thoroughly understood, standing as an essential and integrated component of the team’s collective vision.</p><p><strong>Find out more about this topic:</strong></p><p><a href="https://medium.com/nice-work-from-active-voice/hey-designers-theyre-gaslighting-you-e02e5a4d9cff">Sara Wachter-Boettcher – Hey designers, they’re gaslighting you</a></p><p><a href="https://youtu.be/WSyCpwjeZvw?feature=shared">Fabian Kleeberger – Embedding design in Agile teams</a></p><p><a href="https://youtu.be/JkMse7r10bI?si=uUTNGKPPHvY1pH-l">Jeff Patton – Dual Track Development: Involving The Whole Team In Discovery And Delivery</a></p><p><a href="https://youtu.be/MesYt7PhLFQ?si=hmXJeo621deP3ZBK">Jeff Gothelf – Lean, Agile, &amp; Design Thinking @ Mind the Product Singapore 2019</a></p><p><a href="https://www.amazon.co.uk/Power-Progress-Thousand-Year-Technology-Prosperity-ebook/dp/B0BS3DJBLC?nodl=1&amp;dplnkId=f7fb293c-00fe-4750-80d3-e89cb7fcd35b">Daron Acemoglu and Simon Johnson – Power and Progress</a></p><p><a href="https://www.linkedin.com/posts/jeremykriegel_ux-is-a-sales-job-typically-cant-code-activity-7132759466206224384-bwG3?utm_source=share&amp;utm_medium=member_ios">Jeremy Kriegel – UX is a sales job, Linkedin thread</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=86a0dfa3c6b6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-loner-in-the-corner-the-struggle-of-designers-in-cross-functional-teams-86a0dfa3c6b6">The loner in the corner: The struggle of designers in cross-functional teams</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond habit and process: Product thinking through Nietzschean thought]]></title>
            <link>https://medium.com/design-bootcamp/beyond-habit-and-process-product-thinking-through-nietzschean-thought-dce3a5f5eb7b?source=rss-aa8c53c0114d------2</link>
            <guid isPermaLink="false">https://medium.com/p/dce3a5f5eb7b</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Benjamiz]]></dc:creator>
            <pubDate>Sat, 21 Oct 2023 22:06:58 GMT</pubDate>
            <atom:updated>2023-10-25T23:31:28.840Z</atom:updated>
            <content:encoded><![CDATA[<h4>How Nietzsche’s philosophy can elevate agile product team culture for sustainable innovation and long-term value</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*VIPHtL1yKRA_iTS2ut-GoQ@2x.jpeg" /></figure><p>As I continue my journey through the product development landscape, I have become more aware of the power of mindset and one’s internal approach to overcoming obstacles that really impacts product thinking and how organisations approach product development.</p><p>I take some pride in my knack for linking seemingly unrelated elements. As I delve deeper into product development – embracing ideas like design thinking, empowerment, and cross functional teams – I find myself increasingly aligned with these concepts. Interestingly, I also see connections between these modern practices and the 19th-century philosophy of Friedrich Nietzsche, a thinker I greatly admire. His prose and my own cherry picked selection of his ideas resonate with me, and thus I never miss the opportunity to muse on his writing.</p><p>I know, Nietzsche never directly tackled topics like user experience design or market positioning, but his philosophical ideas – such as eternal recurrence, amor fati, the Übermensch, and the metamorphosis of the spirit – offer invaluable insights for shaping the mindset and internal approach of product teams and organisations.</p><p>For those unfamiliar with Nietzsche, he challenged traditional moral frameworks and introduced ideas that questioned the very fabric of society and human existence. His notion of “amor fati,” or love of fate, encourages a wholehearted embrace of life’s complexities and challenges. Similarly, his idea of the Übermensch represents an individual who creates their own values, transcending societal norms.</p><p>Concerning product development, I want to make it clear that I start with the assumption that the ultimate goal of a product development team is to build products that resonate with customers while driving business value. As Marty Cagan puts it, “We need a product that our customers love, yet also works for our business.” This article aims to show how Nietzschean philosophy can inform and enrich our approach to achieving this delicate balance.</p><h3>Eternal recurrence</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*RSE0e-RwFaBLtxT2inApJA@2x.jpeg" /></figure><p>Friedrich Nietzsche’s concept of “eternal recurrence” asks us to imagine that everything in existence will recur eternally, including every pain, joy, thought, and moment of one’s life.</p><blockquote>“What if, someday or night, a demon were to steal into your loneliest loneliness and say to you: ‘This life as you now live it and have lived it, you will have to live once more and innumerable times more; and there will be nothing new in it.’”</blockquote><p>Though this idea is not new – the Stoics had a similar concept – Nietzsche believed that this thought experiment was an excellent way to gauge one’s progress towards becoming the Übermensch. The Übermensch embraces the concept of eternal recurrence as a form of self-overcoming. They uses it to affirm his existence and influence, embodying Nietzsche’s ideal of the will-to-power or intrinsic motivation. The Übermensch is not merely subjected to eternal recurrence but actively shapes it through their intrinsic motivation, and aims to leave a lasting impact on history and humanity.</p><blockquote>“Would you not throw yourself down and gnash your teeth and curse the demon who spoke thus? … Or … would you have answered him: ‘You are a god, and never have I heard anything more divine.’ … The question in each and every thing, ‘Do you desire this once more and innumerable times more?’ would lie upon your actions as the greatest weight. Or how well disposed would you have to become to yourself and to life?” <em>– Friedrich Nietzsche, Thus Spoke Zarathustra</em></blockquote><p>In layman’s terms, Nietzsche is asking if you’ve lived a life you’d be happy to relive over and over, like a movie you’d enjoy watching on repeat. So, how can the idea of eternal recurrence help teams build and maintain software? Well, let’s ask ourselves: Do we work in a way that we’re happy to repeat endlessly? In the Agile Manifesto, the eighth principle states, <em>“Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.”</em> Instead of merely “spinning plates” to keep things afloat, we should aim for longevity in our work methods, projects, and products.</p><p>But sustainability is more than just workload its also about motivation, as Marty Cagan says,<em> “We want missionaries, not mercenaries.”</em> Missionaries are content with hardship and venturing into the unknown because they believe in their cause and see the long-term benefits. To be willing to repeat life endlessly, one must believe that, in the end, something great will have been achieved – something that justifies the suffering.</p><blockquote>“If you have your why for life, you can get by with almost any how.”</blockquote><blockquote><em>– Friedrich Nietzsche, Twilight of the Idols</em></blockquote><p>“Eternal recurrence” can serve as a litmus test for a team’s approach to work. If the prospect of endlessly repeating current processes and tasks is unbearable, it indicates that the team’s understanding of their purpose has not been made clear, the vision has not been communicated, they do not understand the ‘why’.</p><h3>Amor Fati</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*tRGaWrj_M1mjJAtRAQplwQ@2x.jpeg" /></figure><p>In order to accept the implications of eternal recurrence, Nietzsche talks about “amor fati.” This is a radical acceptance and love for life in all its dimensions. He states, <em>“I want more and more to perceive the necessary characters in things as the beautiful: – I shall thus be one of those who beautify things. Amor fati: let that henceforth be my love!”</em> In essence, “amor fati” is not merely about tolerating life’s complexities but wholeheartedly embracing them.</p><p>Instead of grumbling about a flat tyre, you embrace the challenge and see it as a learning opportunity. It’s not just about putting up with life’s difficulties, but actively welcoming them as part of your personal growth journey. In this way, “amor fati” encourages us not just to survive life’s complexities, but to thrive in them.</p><p>While Nietzsche was not concerned with product roadmaps or user engagement metrics, the mindset encapsulated by “amor fati” can be helpful for product teams and organisations. I see it as an acceptance and embrace of the inherent uncertainties, complexities, and challenges that come with creating something of value for both the customer and the business.</p><p>Marty Cagan’s “two inconvenient truths” can help shed light on why Nietzsche’s “amor fati” is a useful philosophy for product teams. Cagan notes that <em>“at least half of our ideas are just not going to work,”</em> and even the valuable ones will require <em>“several iterations to get the implementation… to the point where it actually delivers the expected business value.”</em> As Cagan puts it, “strong product teams understand these truths and embrace them rather than deny them.” In order for us to do that, as in Nietzsche’s days, we should “want nothing to be different” and should “love” the inherent challenges and failures as much as the successes.</p><blockquote>“Hope in reality is the worst of all evils because it prolongs the torments of man”</blockquote><blockquote>– <em>Nietzsche Human, All-Too-Human</em></blockquote><p>This can be seen as a critique of traditional project management models like the waterfall approach, where there’s often an unrealistic expectation of achieving a perfect solution in one go. As Maria Chec points out, <em>“creating a Gantt Chart is creating a fiction that we have very detailed-level, granular control over the future.”</em> Such methods serve only as a comfort blanket for stakeholders, ignoring the inherent uncertainties of product development.</p><p>If you truly love life in all its aspects, including its challenges and complexities, then uncertainty, setbacks, and difficult conversations become not obstacles but opportunities. They offer a path that, while more challenging to face, is more beneficial to confront and ultimately more valuable to overcome for both the customer and the business.</p><p>Nietzsche’s emphasis on embracing suffering and challenges aligns well with this approach. As he puts it, <em>“The discipline of suffering, of great suffering – do you not know that only this discipline has created all enhancements of man so far?”</em> It’s not about avoiding the negative aspects of development, difficult conversations, or challenges but embracing them as part of the journey toward building something truly valuable.</p><p>“Amor fati” or “love of fate” presents a unique challenge when balancing philosophical ideals with the practicalities of deadlines, budgets, and stakeholder expectations. Embracing “amor fati” doesn’t mean abandoning responsibility or ignoring the constraints that govern the business world. Rather, it calls for a nuanced approach where one accepts these limitations, not as hindrances, but as integral components of the project’s life cycle. This perspective leads to creative problem-solving and a harmonious relationship with stakeholders. It fosters a culture of openness and adaptability.</p><p>Instead of viewing deadlines and budgets as oppressive forces, they are seen as challenges to be met with enthusiasm and ingenuity. Thus, “amor fati” can coexist with business practicalities, enriching rather than complicating the product development process.</p><h3>Übermensch</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*rfSgxPnCWMeFRKGEq5rsuA@2x.jpeg" /></figure><p>Peter Drucker once said, <em>“One cannot manage change. One can only be ahead of it.”</em> To be ahead of change, one must be continuously learning and evolving. You cannot be content with where you are, nor can you believe you have all the answers. Instead, be willing to explore the unknowns and constantly adapt in order to handle external change effectively.</p><p>In Nietzsche’s book “Thus Spoke Zarathustra,” Zarathustra presents two contrasting ideals: the Übermensch and the Last Men. The Übermensch is the pinnacle of human potential, embodying creativity, innovation, and disruption of the status quo. The Last Men, on the other hand, seek comfort and believe themselves to be the pinnacle of humanity. They represent everything Nietzsche finds undesirable for human progress.</p><p>Both Drucker’s and Nietzsche’s focus on the need for constant adaptation align with the second principle of the Agile Manifesto, which states, <em>“Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.”</em> Innovation is fraught with challenges and isn’t for everyone. It requires a conscious drive to improve, change, and actively explore unknown spaces. Teams cannot afford to become the ‘Last Men,’ comfortable with the status quo.</p><blockquote>“Who still wants to rule? Who still wants to obey? Both are too burdensome. No shepherd, and one herd! Everyone wants the same; everyone is the same: he who feels differently goes voluntarily into the madhouse.”</blockquote><blockquote><em>– Thus spoke Zarathustra</em></blockquote><p>We need empowered, cross-functional product teams, not teams siloed into separate departments. Nietzsche’s caution that <em>“By morality, the individual is taught to become a function of the herd, and to ascribe value to himself only as a function,”</em> serves as a warning. Product teams must avoid becoming mere <em>“functions of the herd.”</em> Resistance to change, adherence to established methods just because ‘that’s how it’s done here,’ and a neglect of inconvenient truths are all signals of a ‘Last Man’ mindset.</p><p>Such an attitude stifles innovation and fosters a culture proud of its mediocrity, as Nietzsche warns.<em> “They have something of which they are proud. What do they call it, that which makes them proud? Culture, they call it; it distinguishes them from the goatherds but fails to achieve anything greater.”</em> Nietzsche’s sentiments are echoed by Jeff Bezos in his 2016 letter to shareholders. He describes “Day 2 companies” as those that have settled into stasis, followed by irrelevance, painful decline, and eventually, death. In contrast, a “Day 1 company” mindset is described as one that is customer-obsessed, enables high-quality and high-velocity decision-making, and empowers employees to stay curious and experimental.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*zsUj8j5gVDIUxBbyyi2X8w@2x.jpeg" /></figure><p>Nietzsche believed that we should live in a way that would move humanity towards the Overman.</p><blockquote>“I love him who lives in order to know, and seeks to know in order that the Overman may hereafter live. Thus he seeks his own down-going. I love him who labors and invents, that he may build the house for the Overman, and prepare for him earth, animal, and plant: for thus he seeks his own down-going.”</blockquote><blockquote><em>– Thus spoke Zarathustra</em></blockquote><p>This is about building for the future not for the present.</p><blockquote>“the individual looks his own short life span too squarely in the eye and feels no strong incentives to build on enduring institutions, designed for the ages. He wants to pick the fruit from the tree he has planted himself, and therefore no longer likes to plant those trees which require regular care over centuries”</blockquote><blockquote><em>Friedrich Nietzsche – Human, All Too Human Section One: Of First and Last Things – Aphorism # 22</em></blockquote><p>This quote from Nietzsche’s serves as a poignant reminder for product teams. The focus shouldn’t be solely on quick wins or immediate outcomes. Instead, the vision should be long-term, aimed at creating enduring value that will provide “shade for long successions of generations.”</p><p>We need to think about the long-term value of our work. A continuous commitment to evolution and self-evaluation is essential. This ensures that the team doesn’t become “the most despicable man, who can no longer despise himself” – in other words, a team that can no longer see fault in their ways of working. As Nietzsche said, “one must still have chaos in oneself to give birth to a dancing star.” Therefore, for continuous innovation, a team must not fall victim to the chains of process or the status quo. Instead, be a team “who breaks their tablets of values.”</p><h3>The three metamorphosis of the spirit</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*PdnG9p6m1RRM__esrVkPxA@2x.jpeg" /></figure><p>In the business world, an over-reliance on process can be a double-edged sword. On the one hand, it helps with scaling; but on the other, blind adherence to process is the death of creativity. Steve Blank warns, <em>“As companies and agencies get larger, they start to value the importance of process over the product… The process people dominate management, and the product people end up reporting to them.” </em>Jeff Bezos echoes this sentiment, stating,<em> “A common example is process as proxy… This can happen very easily in large organisations… You stop looking at outcomes and just make sure you’re doing the process right.”</em> Elon Musk criticises big companies where <em>“process becomes a substitute for thinking,”</em> and Steve Jobs succinctly puts it, <em>“It’s not process; it’s content (satisfaction).”</em> These industry leaders caution against letting process overshadow innovation and agility, a trap that many growing companies fall into.</p><p>Now, business process wasn’t something that Nietzsche talked about, but he does posit a fascinating idea regarding the stages the spirit traverses during personal growth, centred around religion, that could help us combat this tendency of falling into the process trap. Transitioning from a passive state to that of a Camel, in this stage, one adheres strictly to beliefs and values derived from external sources. In the realm of software development, this mirrors the phase when product teams recognise the need for a shift in their product practices and decide to adopt new processes like Scrum or Kanban, adhering to them meticulously.</p><p>However, a point may arise where such rigid adherence to these rules becomes counterproductive. Here, your spirit requires the heart of a Lion, the second stage, to challenge and fight against the external rules and “thou shalt’s” imposed by others. Yet, being able to reject these pre-established rules and values is only half the battle. If rejection is the sole action, the creation or discovery of one’s own values remains elusive. This sets the stage for the final metamorphosis into the Child, where the freedom to play, experiment, and create anew resides.</p><p>To not only reject but also to create something new, one needs a structured progression: an understanding and acknowledgment of what has been (the Camel), the ability to identify problems within the current state (the Lion), followed by the willingness to experiment, iterate, and craft something new (the Child). This progression embodies a holistic approach towards personal or organisational growth, nurturing a conducive environment for continuous innovation and self-evolution.</p><h3>Not enough!</h3><blockquote>“It is not enough to prove something, one has also to seduce or elevate people to it. That is why the man of knowledge should learn how to speak his wisdom: and often in such a way that it sounds like folly!”</blockquote><blockquote><em>Friedrich Nietzsche – Daybreak Book IV – Aphorism # 330</em></blockquote><p>While it’s easy enough to talk about philosophical ideas, translating them into real-world action is always the more challenging task. Belief and personal values shape our actions, and it’s up to us to travel through the journey of the spirit. Nietzsche’s magnum opus, “Thus Spoke Zarathustra,” has the subtitle “A book for all and none,” highlighting his belief that his ideas wouldn’t be for everyone. In a similar vein, fighting against a self-satisfied culture can be a lonely battle.</p><p>Though I’m aware I haven’t tackled the complexity of revenue and strategy, trying to shoehorn Nietzschean philosophy into business strategy would stretch beyond my confidence to do justice. One difficulty with Nietzsche’s philosophy is its focus on individuality and independence, contrasting sharply with the top-down or team approach of most organisations.</p><p>I don’t believe eliminating leadership or teams is beneficial, but it’s worth noting that leaders and team members are individuals. Therefore, it’s individuals who require the courage to pursue and enact change to drive value. I hope this article can inspire you to be bold, break up stale processes, and embrace – nay, love – the struggle.</p><p>Further reading:</p><ul><li><a href="https://www.amazon.co.uk/Thus-Spoke-Zarathustra-Friedrich-Nietzsche/dp/0140441182">Thus Spoke Zarathustra, Friedrich Nietzsche</a></li><li><a href="https://www.amazon.co.uk/Inspired-Create-Tech-Products-Customers">Inspired, Marty Cagan</a></li><li><a href="https://www.aboutamazon.com/news/company-news/2016-letter-to-shareholders">Letter to shareholder 2016, Jeff Bezos</a></li><li><a href="https://d1.awsstatic.com/executive-insights/en_US/elements_of_amazons_day_one_culture.pdf">Elements of Amazon’s Day 1 Culture, Daniel Slater Worldwide Lead, Culture of Innovation</a></li><li><a href="https://agilemanifesto.org/principles.html">Agile manifesto</a></li><li><a href="https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/unleashing-the-power-of-small-independent-teams">Unleashing the power of small independent teams, McKinsey Quarterly: Digital Edition</a></li></ul><p>all images created using dall e 3*</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dce3a5f5eb7b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/beyond-habit-and-process-product-thinking-through-nietzschean-thought-dce3a5f5eb7b">Beyond habit and process: Product thinking through Nietzschean thought</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rethinking design: From products to workflows]]></title>
            <link>https://medium.com/design-bootcamp/so-you-got-inspired-by-cheskys-talk-at-config-now-what-1285853c2315?source=rss-aa8c53c0114d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1285853c2315</guid>
            <category><![CDATA[organizational-change]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Benjamiz]]></dc:creator>
            <pubDate>Mon, 17 Jul 2023 19:43:49 GMT</pubDate>
            <atom:updated>2023-11-12T14:10:33.277Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, I found myself inspired by the talk <a href="https://youtu.be/Dkfijg7s76o">Brian Chesky, the CEO of Airbnb, gave at Config 2023</a>. I became interested in the talk because of the <a href="https://twitter.com/kvngao/status/1671658234401398784?s=46&amp;t=gX4nv2Kj1InqiGIYPG999Q">noise the internet was making about it</a>.</p><blockquote>“We removed the classic product management function, Apple didn’t have it. either.”</blockquote><p>Though the idea of a product marketing manager is intriguing, I found their journey back to being a design-led company to be much more interesting. However, the pause Chesky took when asked about how to instigate such a change in an organisation hinted at the complexity of this process.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDkfijg7s76o%3Ffeature%3Doembed%26start%3D877%26end%3D909&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDkfijg7s76o&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDkfijg7s76o%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e7bf674ef80108e9d62cd619403e5b23/href">https://medium.com/media/e7bf674ef80108e9d62cd619403e5b23/href</a></iframe><blockquote>“Let’s say you’re a designer somewhere and you are not the founder of the company…how do you push for a design-led strategy?”</blockquote><p>He takes this long pause, chokes on his words a little, then starts talking about designers curse of self justification. He does go on to talk about what he believes are fundamental principles a designer should follow, but before we get into that, let’s first look at what triggered the change at Airbnb.</p><p>It took a series of significant events to kickstart the change. First, he had an epiphany, realising they were on the wrong path, he communicated his perceived risks to his co-founders. He collaborated with design leaders from Apple who helped him perceive a new way of working. This was happening while he had the pressure of going public, followed by a drop in value due to COVID-19, which put the company in a state of fight or flight. This is when Airbnb seemed as if they were able to “find the nerve” and momentum, to overhaul the entire way that they worked. Gained a “what do we have to lose?” mentality.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDkfijg7s76o%3Ffeature%3Doembed%26start%3D496%26end%3D519&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDkfijg7s76o&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDkfijg7s76o%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d04fb1688f9ba672ee7ee2436ecccd23/href">https://medium.com/media/d04fb1688f9ba672ee7ee2436ecccd23/href</a></iframe><p>So at face value, the answer to can a designer change an organisation? would be no, they can’t. Only an organisational existential crisis and a CEO with an epiphany can lead to organisational change. But this obviously is too absolute and defeatist a claim for anyone to jibe with.</p><p>Let’s shift our focus from products for a moment and delve into how individuals enact their own transformational change. This brings us to the <a href="https://www.hapa-model.de/">Health Action Process Approach (HAPA)</a>, a psychological theory developed by Ralf Schwarzer. HAPA is all about health behaviour change, but it’s not just about swapping bad habits for good ones. It’s a framework that explains and predicts how people change their behaviours, such as quitting smoking or improving physical activity levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*JLlYNf8M7oD_btK8mRsSXg@2x.jpeg" /></figure><p>HAPA is divided into two phases: the motivation phase and the volition phase. The motivation phase is all about forming intentions to change. This could be recognising a risk and wanting to avoid it, or envisioning a world where you’ve made the change and what that means for you. The volition phase is about putting those intentions into action. It involves planning and initiative, maintaining the new behaviour, and recovering when you slip up. This theory, eerily, aligns well with the product development stages.</p><p>In the motivation phase of HAPA, individuals form intentions to change their behaviour, this could be in the form of recognising a risk and wanting to change to avoid it, or in the form of outcome expectation or imaging (outcome expectation) a world where you have made the change and what that means for you. This process is akin to the discovery stage in product development, where teams identify market needs and potential risks, similar to a product vision.</p><p>Self-efficacy, or the belief in one’s ability to achieve the desired outcome, is a critical component throughout HAPA. This component in product development aligns with ensuring that the “product trio” believe in the value, viability, feasibility, and usability of their solution through continuous testing and validation.</p><p>Unlike in the motivation stage where an individual creates an intention to do something, the volition phase in HAPA is putting that intention into action and is made up of three levels: cognitive – the planning of what to do the work, behavioural – how the work will and won’t be done, and situational – what environment the work is done in. By planning and visualising all these levels, one is better equipped to tackle events that get in the way of their goal, which helps them maintain self-efficacy or belief that they can continue.</p><p>This is like the delivery side of the product process where prototypes become shippable software; the work is broken down in a way that delivers value in iterations, as well as establishing and refining how they work, and defining anti-patterns, practices like sprint reviews align with this idea.</p><p>In the context of organisational change, HAPA could prove to be a great framework to use in terms of how do start breaking down the work needed to change an organisation.</p><p>Organisations have to first recognise the risks of maintaining the status quo and visualise a more effective way of operating. Planning can help build confidence in the change process, while effective communication ensures that the outcomes of the plan are understood by the whole organisation.</p><p>One of the most challenging aspects of organisational change is the tendency to revert to old habits, especially under stress or uncertainty. This is where HAPA’s emphasis on anticipating and managing risk behaviours and situations becomes particularly relevant. Organisations need to be brutally honest about their past failures and the poor decisions that led to them. This introspection is not for the purpose of assigning blame, but to learn and create a clear roadmap for avoiding similar pitfalls in the future. It’s about cultivating a culture that not only acknowledges these risks but actively works to mitigate them.</p><p>Continuous reinforcement of the new strategies and behaviours that align with the envisioned future create a resilient environment that is prepared to counteract the pull of old habits and stay the course towards becoming truly design-led.</p><p>If you listen to Brian Chesky’s outline Airbnb’s transformation it does seem to align with the personal change steps outlined in HAPA. However, the narrative he presents suggests that he was the primary source of self-efficacy within the organisation.</p><p>Now we have an idea of how change can happen let’s look at what Chesky’s key principles for designers. From my perspective, his answer essentially says you can be a certain way and hope that will make a change.</p><p>He provides a set of principles that any designer, regardless of their position within the organisation, can adopt to instigate a more design-led approach.</p><h3>Being user-centric</h3><p>This is paramount. This goes beyond aesthetics into the user journey through your design. It’s about understanding the user’s needs and how your design can meet them.</p><h3>Stubbornness</h3><p>Or rather, a strong sense of pride in your work. You should only be willing to ship designs that you’re genuinely proud of. If you don’t take pride in your work, how can you expect others to appreciate it?</p><h3>Simplicity</h3><p>This doesn’t mean stripping away features, but rather gaining a deep understanding of the problems you’re trying to solve and designing solutions that address the root issues and needs of the users. This requires a profound understanding of the problem beyond a list of “requirements”.</p><h3>Importance of craftsmanship</h3><p>As a designer, you should obsess over every detail to ensure the highest quality in your work. Though this relates closely with taking pride in your work but I think there is always room to improve your craft so instead of it being about you being happy with your work, I think it’s about continuing to perfect your craft through continuous learning.</p><h3>Communication</h3><p>Another key principle. You need to articulate your ideas and decisions in a language that your organisation understands, demonstrating how adopting your ideas will benefit them.</p><p>Chesky also makes an interesting point about “growth not being a goal”, but that’s a topic for another discussion.</p><p>Adopting the above principles in one’s work is the first step, but I don’t think it goes deep enough to answer the question of how a designer can instigate organisational change.</p><p>Thankfully though, how Brian concludes the conversation offers a glimpse into how a designer can begin to instigate this change.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDkfijg7s76o%3Ffeature%3Doembed%26start%3D1620%26end%3D1656&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDkfijg7s76o&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDkfijg7s76o%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c0c14f7addb5827fb47ae09c1454d692/href">https://medium.com/media/c0c14f7addb5827fb47ae09c1454d692/href</a></iframe><blockquote>“I think design is not just about how something looks, but how something fundamentally works. And I think it’s one of the most important skills that we are going to need in the 21st century.”</blockquote><p>Chesky sees himself as a designer, but not in the traditional sense. He designs how his company operates and functions as a business. I think therein lies the key.</p><p>If you think similarly to Chesky, a designer’s skill is not on Figma, user personas, UX laws, user interviews, or anything a “product designer” would generally do for a product. They have the ability to soak in the world around them, learn fast and obsess over their craft – developing solutions to problems in creative ways.</p><p>Which finally brings me to my response to the question:</p><blockquote>“How can a designer, who is not the CEO or founder of the company, instigate change within the organisation to make it more design-led?”</blockquote><p>The answer, I think, is rooted in the principles of product development and the Health Action Process Approach (HAPA).</p><p>Identify the risks in your organisation’s current approach and design a vision, communicate the desired outcome, build the outcome expectation within the organisation, test these ideas, fostering a collective desire and belief in the potential for successful change. Develop plans to mitigate risks along the way and implement practices to prevent reverting to old habits. Above all, iterate continually.</p><p>An organisation is akin to an organism. While the CEO may be the head, significant change can occur when enough members of the body embrace a shared vision. When the body moves, the head must follow. The individuals within an organisation are cognitive agents. The more people who are aware of and see the benefits in design-led principles, the more they understand how they can get there, the greater the likelihood that the organisation will transform into a design-led entity.</p><p>As a designer, you have the skills to learn what other colleagues’ issues are within the organisation and how to integrate all your learnings and design a simple solution to solve those problems for your organisation.</p><p>When you can illustrate with your solutions that you have considered your colleagues’ issues and problems, they are more likely to begin to want to live in the world your vision pictures.</p><p>Like Brian Chesky, designers need to be more than just creators of platform interfaces. They need to be integral in designing the way the organisation functions and design solutions that simplify operations. They must design how they communicate these plans with other stakeholders in a language they understand, addressing their problems and needs.</p><p>Whilst going over this article, I’ve started to change my understanding of what it means to be a design-led organisation. I used to understand it within the context of product development, as in making a conscious effort to ensure your product development process was user-centric or incorporated a discovery process, but now I’m starting to think that it actually just means employing some of the same rigour you would within the product development process throughout the entire company’s operations.</p><p>So, just as you would approach a product design problem, apply the same principles and methodologies to solve your organisation’s challenges. Think, test, apply, repeat.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1285853c2315" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/so-you-got-inspired-by-cheskys-talk-at-config-now-what-1285853c2315">Rethinking design: From products to workflows</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your design is only as good as your organisation’s ability to problem solve]]></title>
            <link>https://uxdesign.cc/your-design-is-only-as-good-as-your-organisations-ability-to-problem-solve-a6ea86792803?source=rss-aa8c53c0114d------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6ea86792803</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[editor-picks]]></category>
            <category><![CDATA[design-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Benjamiz]]></dc:creator>
            <pubDate>Thu, 15 Jun 2023 10:50:38 GMT</pubDate>
            <atom:updated>2024-02-01T10:00:44.231Z</atom:updated>
            <content:encoded><![CDATA[<h4>Stifling innovation and wasting talent: the hidden consequences of organisational practices on design potential.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*sZMLstXvHytFnSFF9vWgbw@2x.jpeg" /><figcaption>image generated using Dall•e 2 on nightcafe.studio</figcaption></figure><p>Design in product development is both a science and an art. It has to be scientific because business is a numbers game, but it must also be artistic because usability revolves around the human experience. Even though most people appreciate the benefits of artistic expression, it isn’t usually high on a business’s list of priorities. Designers ensure that the solutions we provide cater to the human beings that use the tools we build. However, businesses rarely recognise their true value because their benefit isn’t immediately felt.</p><p>The feedback from the success of a sales team, for example, is immediately obvious — but that’s not so for design.</p><h3>So what is good design?</h3><p>For me, good design is beneficial not just for the user, but also for the business. It’s easy to learn, helps achieve a goal beyond the tool itself, and evokes positive emotions within its interactions. Unfortunately, because good design creates a seamless experience, it often goes unnoticed.</p><p>Have you ever wondered why your partner is more likely to criticise you for not doing the dishes than to thank you when there are no dirty dishes?</p><p>As humans, we are wired to conserve energy – cognitive energy included. The effort we put into thinking and problem-solving is a drain on this resource, so it’s in our nature to gravitate towards solutions that are effortless and straightforward.</p><p>This intrinsic human tendency is a crucial consideration for designers. To design effectively, they need to deeply understand the desires and intended outcomes of those they are designing for, alongside the business goals.</p><p>They must answer the question,</p><blockquote>“How can we create a solution that not only assists users in achieving their tasks but does so in a way that keeps them engaged and returning to our product?”</blockquote><p>There is no crystal ball to provide these answers. Instead, it takes a process of continuous experimentation and iteration to refine the design and ensure it aligns with both user needs and business objectives. This is the essence of energy-efficient design – minimising cognitive load while maximising user satisfaction and business value.</p><p>But design does not exist in a vacuum. It takes an entire product team to develop a good solution that brings value to customers and users.</p><h3>So, what does a good product team look like?</h3><p>For me, product teams need to cultivate a culture that encourages experimentation, iteration, and challenging assumptions. Regularly talking to users to validate decisions, proactively addressing risks, and focusing on problem-solving and outcomes rather than ticking off a long list of predetermined requirements. Good product development hinges on knowing business goals, understanding users’ and customers’ needs, tackling their problems, rapidly assessing the impact of our solutions, and possessing the resilience to accept failures and the necessity to iterate towards value.</p><h4>Why is it important to work towards?</h4><p>If we accept <a href="https://www.svpg.com/the-inconvenient-truth-about-product/">Marty Cagan’s two inconvenient truths</a> – that more than half of products/features are never used, and achieving business value requires multiple iterations – recognising that no product development methodology – be it waterfall or agile – guarantees that all time spent by a product team directly translates into business value is vital. Yet, a learning-oriented approach focused on rapid experimentation can turn seemingly ‘wasted’ time into valuable insights. Even if every endeavour doesn’t yield immediate business value, it offers learnings that refine our understanding of users and their needs. By adopting this playful, experimental, and iterative approach to product development, we embrace the fact that we don’t have all the answers from the start. Continuously striving for a deeper understanding of our users allows us to efficiently direct our efforts towards what truly works, thereby consistently aiming for business value.</p><p>If we merely build what a customer asks for or stick rigidly to a list of requirements, we’re not only tapping into half of our engineers’ potential but also underutilising the creative and problem-solving abilities of our designers.</p><h3>Bringing it back to design</h3><p>In order for designers to truly make a meaningful and comprehensive contribution, their involvement has to permeate beyond the realm of product development and cut across the entire strategic landscape of the organisation. Designers should not be pigeonholed into just the early stages of idea formation or refinements during agile sprints. Instead, their expertise and insights should be interwoven into all aspects of strategic planning and execution.</p><p>The significant value of design becomes evident when we examine the findings of the <a href="https://www.dmi.org/page/DesignValue/The-Value-of-Design-.html">Design Management Institute’s 2015 Design Value Index</a>. Companies considered “design-centric”, meaning they integrate design practices throughout their operations, showed a staggering 211% return over the S&amp;P 500. This underlines that good design practices can contribute directly to an organisation’s financial success.</p><h3>What drives an organisational shift?</h3><p>Leadership carries a vital role in this context. They need to champion the far-reaching value of user-centric design and experimentation. However, championing this isn’t just about vocalising its value. It’s about ensuring the strategic decisions made by leadership consistently mirror this vision. It’s this coherence between words and actions that will transmit a strong message throughout the organisation, thereby instigating a real shift in the culture towards valuing design’s pivotal role.</p><p>There seems to be a tendency for organisations to prioritise what will earn them money in the short term over what will assist the user in the long term. Just as in life, one must often forgo immediate pleasures for a better future, organisations should do the same.</p><p>Investing in design and agile development will not pay off overnight as perfecting the product and ways of working will take time and iteration. For me, the question is this:</p><blockquote>“Is your organisation prepared to admit they don’t know what will work and are they prepared to invest resources finding out what they don’t know?”</blockquote><p>Because if not, I’d argue none of your designs will ever be as good as they could be.</p><p>Just like users want to reduce cognitive load and shy away from wanting to learn new processes that are hard to understand and navigate, businesses do the same. This shift in thinking and value from revenue-driven decisions to customer and user value decision-making is a big learning curve for established organisations whose processes, ways of working, and mindset have solidified.</p><p>So, as a designer, just like we slowly release design changes to users to not overwhelm them with change, we must also be patient enough to do the same within our organisation. This requires a level of strategic thinking from those within the company that see the value of user-centric product development, which obviously includes designers. If designers are unhappy with their organisation’s design maturity, they cannot pigeonhole themselves into the role of designer, but must have an organisational strategic vision of how they will change the perception of design within the organisation.</p><p>Design in product development is about so much more than aesthetics. It is an intricate dance between science and art, informed by business goals and yet human-centric. It’s about understanding and addressing user needs in a way that creates meaningful experiences and real value for both the user and the business. Achieving this requires not just good design practices, but also a good product culture that values experimentation, iteration, and understanding. An organisation’s mindset is instrumental in fostering this culture. A shift towards prioritising user needs and seeing them as the real drivers of value, not just immediate revenue, is crucial. Good design without a good product culture is simply incomplete. By fostering a product culture that truly understands this, organisations can not only design better products but also create lasting value for their users and themselves.</p><h4>Further Reading and Resources:</h4><p>Here are some resources that should provide some additional insights into the themes I’ve discussed in this article. I’ve found them very interesting and helpful for my own understanding product development and design thinking.</p><p>1.	LinkedIn: <a href="https://www.linkedin.com/in/tmoura?challengeId=AQHvHEQX47ewnQAAAYjTR9qjyjiRFNych0lptt90JsfWSq9YCiN6iRjArRufFmpeLxYCynLrzSj0FKJ8QlR0HPwQpetV3bDe0w&amp;submissionId=16291413-e309-6a17-36d8-ea52fe7c5766&amp;challengeSource=AgG24x81CTw6LQAAAYjTSCVjzscEWp5m2jmYDuOa3NhvzRj_QLgtYWOI93TfNuw&amp;challegeType=AgGWNapFeeaw4wAAAYjTSCVrbsUtVnTyWvxZytU1isl-vFYkjp8AXh8&amp;memberId=AgF6CD-VF2ucmwAAAYjTSCVuCPLf01VbgwhHdRaYf2hYQ9E&amp;recognizeDevice=AgHMXuWmDRcDswAAAYjTSCVx07j9lFwqEDyjHU9fzJpRmHeeSTxn">Tony Moura</a></p><p>2.	Books:</p><p>•	“Lean UX: Designing Great Products with Agile Teams” by Jeff Gothelf and Josh Seiden</p><p>•	“INSPIRED: How to Create Tech Products Customers Love” by Marty Cagan</p><p>•	“Continuous Discovery Habits: Discover Products that Create Customer Value and Business Value” by Teresa Torres</p><p>3.	PDF:</p><p>• “Product Discovery Recipes” by Jeff Patton. <a href="https://jpattonassociates.com/product-discovery-recipes/">Download here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6ea86792803" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/your-design-is-only-as-good-as-your-organisations-ability-to-problem-solve-a6ea86792803">Your design is only as good as your organisation’s ability to problem solve</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting revenue before users get value.]]></title>
            <link>https://medium.com/@benjamin.mizrany/getting-revenue-before-users-get-value-14137da270f9?source=rss-aa8c53c0114d------2</link>
            <guid isPermaLink="false">https://medium.com/p/14137da270f9</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Benjamiz]]></dc:creator>
            <pubDate>Wed, 14 Jun 2023 06:03:04 GMT</pubDate>
            <atom:updated>2023-10-07T09:29:47.739Z</atom:updated>
            <content:encoded><![CDATA[<h2>Balancing Business and User Needs: The Dual-Faced Challenge in B2B SaaS Design</h2><figure><img alt="man on left of balance scale with money on the right, as a crowd looks on" src="https://cdn-images-1.medium.com/max/1024/1*Q2yzhwcnkZp0Kgt9h3ty2A.jpeg" /></figure><p>In any B2B SaaS transaction, an inherent conflict of interest emerges: decision-makers, those with the power to procure new software for a company, often aren’t the ones who actually use the product on a daily basis. Despite this, they offer feedback and critique to the product team, while the actual users – those who interact with the product daily and understand its nuances – are often overlooked.</p><p>The disconnect becomes even more apparent when selling B2B SaaS products. Decision-makers are primarily concerned with business outcomes. They look at products through a different lens compared to that of the end-user, which means they may not necessarily understand or prioritize the usability of the tool or truly think about how the implementation of a product will affect the workload and outcomes of the end users.</p><p>The fundamental objective of any tool or software is to assist users in achieving the desired outcome in the most efficient way. To truly fulfil this purpose, a product must be designed with a user-centric focus. However, the challenge arises when the needs and expectations of the decision-makers do not align with those of the users.</p><p>For users, it’s important that the tools align with their current processes, or, at the very least, are easy to learn and implement a new process to get their job done. This is where a truly user-focused design can make a substantial difference in the efficacy and acceptance of a new tool.</p><p>Consider the example of a time tracking tool. The benefits to the employer are abundant – tracking workforce productivity, identifying bottlenecks, charging clients by hours worked, etc. However, the user’s perspective is different – though they can derive some benefit from tracking their tasks and time to prove a business case for a pay rise or for new hires. What they ultimately want is to do their work as well and as efficiently as possible with personal autonomy. They will most likely resent intrusive surveillance and time-consuming, intricate time-keeping tasks. Only by providing a solution that both enables the user to minimally use the product while maximizing the information gathered will the time-tracking software be successful.</p><p>As a product designer, the challenge is finding a balance between serving the user, who requires a seamless, unobtrusive experience, and satisfying the decision-maker, who demands measurable outcomes. The key to achieving this delicate balance lies in better understanding the needs of both parties and integrating this understanding into the product design process.</p><p>Designers can easily become too narrowly focused on the end-user experience and not take into account the needs of the business and the decision-makers who ultimately choose whether the users use the software or not. Conversely, non-designers can easily forget about the end-users and focus solely on the customer (decision-makers).</p><p>The lesson here is that ultimately, your B2B SaaS product is a tool for the business, but that tool is used by humans with their own wants and desires, so we need to serve both.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14137da270f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>