<?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 Noah Fang on Medium]]></title>
        <description><![CDATA[Stories by Noah Fang on Medium]]></description>
        <link>https://medium.com/@kingofark?source=rss-495036b10f88------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bT0W7E1Cc82otgNp_mWUug.jpeg</url>
            <title>Stories by Noah Fang on Medium</title>
            <link>https://medium.com/@kingofark?source=rss-495036b10f88------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:14:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kingofark/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[Why Your Org Can’t Succeed at Digital Transformation]]></title>
            <link>https://medium.com/@kingofark/why-your-org-cant-succeed-at-digital-transformation-97767722f76d?source=rss-495036b10f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/97767722f76d</guid>
            <dc:creator><![CDATA[Noah Fang]]></dc:creator>
            <pubDate>Thu, 18 Mar 2021 14:00:15 GMT</pubDate>
            <atom:updated>2022-08-05T02:07:09.003Z</atom:updated>
            <content:encoded><![CDATA[<h3>Digital transformation urges a transfer of power that powerful people never intend to do.</h3><p>If digital transformation is really as awesome and game-changing as some claim or agree with, then we’d expect it to be so much more than adopting digital technologies without deep impact on the purpose, culture, structure, process, and function of an organization.</p><p>You can’t have it both ways, can you?</p><p>You can’t, on one hand, sing the praises of how awesome, innovative, or disruptive digital transformation is, while, on the other hand, making excuses when it comes to actually doing it.</p><p>So what’s the use of digital technologies in the context of digital transformation?</p><p>Perhaps at least two things: automation, and making better decisions.</p><p>Automation is for tactical effectiveness and efficiency.</p><p>In digital transformation, instead of having humans laboriously and manually handle some computation-intense processes, we make use of digital technologies to do it for us. The role of humans shifts from labourer to curator, by curating and working with machines to streamline and optimize the automation.</p><p>Making better decisions is harder. In digital transformation, we need digital technologies to augment our capability and capacity for computation, since we humans now, paradoxically, create far more information than we can process.</p><p>And on top of that, we need “smart” technologies like advanced analytics and artificial intelligence to meaningfully support how we make decisions, when we can no longer afford doing it manually and alone.</p><p>Both automation and making better decisions demand something you might not realize: clarifying how we make decisions. For automation, we need to clarify the logic of the process and human judgement’s role in it. For making decisions, we need to clarify the power structure we rely on doing so.</p><p>Decisions about logic is relatively easy to make, while decisions about human judgement is a lot harder.</p><p>A lot of non-logical stuff goes into human judgement.</p><p>In an organizational context, cultural norm, team dynamics, economic situation, or political circumstance is tightly coupled with how decisions are made.</p><p>When there’s a hierarchy of authority, as in the case of most organizations, power structure is the one factor that influences all other factors.</p><p>That’s where digital transformation hits the impenetrable barrier.</p><p>Because people in power don’t like to clarify the power structure they rely on for making decisions.</p><p>Powerful people have many ways to act out their power. One particularly effective way is through the power of discretion. With exactly the same factual context around the same issue, different people in different organizations may make very different decisions, depending on the context. And that context is often power structure.</p><p>More often than not, it’s one thing for executives (or other people in power) to show their unanimous support for digital transformation, and it’s quite another for them to actually contribute to implementing it along the way:</p><p><em>“Absolutely I fully embrace digital transformation! In fact, at the core of my leadership and my leadership team is our digital transformation strategy! Oh man, you have no idea how serious I am about it! Our organization’s survival and future success depend on it! … what? You want me to clarify how I make decisions? Well, I’m afraid I can’t really do that! Not that I can’t rationalize it, but, you know, there are a lot of things going into making decisions at the strategic level. You know that, don’t you? It’s not as simple as if-then, and-or! It’s not simple logic! For God’s sake, we’re humans!”</em></p><p>Let that sink in the next time you think about digital transformation.</p><p>But, you might ask, algorithms and AIs can’t possibly replace all human decision-making, can they?</p><p>Of course not, but the implication of digital transformation is not so much in that machines are the receiving end of the power transfer, but in that the transfer reconfigures the organizational politics, from emotional politics to computational politics.</p><p>{END}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/196/0*DYy3t5EHk-Exrb8N" /></figure><p>Working on design, strategy, and organizational transformation. Design practitioner, author and interactive storytelling pilgrim. Was creative director, user experience manager, product manager, visual designer, editor, translator, software developer and more.</p><p><a href="https://kingofark.com/author/kingofark/">View all posts by kingofark</a></p><p><em>Originally published at </em><a href="https://kingofark.com/2021/03/18/why-your-org-cant-succeed-at-digital-transformation/"><em>http://kingofark.com</em></a><em> on March 18, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97767722f76d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Road to Transformable Enterprise: Reflective Conversations on Writing and More]]></title>
            <link>https://medium.com/@kingofark/the-road-to-transformable-enterprise-reflective-conversations-on-writing-and-more-33438365520b?source=rss-495036b10f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/33438365520b</guid>
            <dc:creator><![CDATA[Noah Fang]]></dc:creator>
            <pubDate>Fri, 12 Mar 2021 02:57:19 GMT</pubDate>
            <atom:updated>2022-08-05T02:06:19.438Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>NOTE</strong>: <em>The following post is a conversation between Andrey Milchman and Noah Fang, long-time collaborators and authors, on their new book, </em><a href="https://www.amazon.ca/dp/B08YPBCGXK/"><em>The Transformable Enterprise: Enterprise Architecture in a New Key</em></a><em>, which “challenges current enterprise architecture practices, which are mostly inspired by engineers seeking freedom from constraints of science, art, and architecture in both structure and style.”</em></h3><h3>The Road to Transformable Enterprise: Reflective Conversations on Writing and More</h3><p>By Andre Milchman, Noah Fang</p><p><strong>NOAH</strong>: Our conversations on enterprise architecture and the transformable enterprise date back to 2015, when I had the honor of working with you in the same company. I think I’m always on the learner side, and I’ve learned so much from you over the years. Even though you and I have been working on and off on the basic writings around those topics for quite a while, I realized, upon finishing this book, that we have never talked about the origin stories of that theoretical universe. So, I really think this is a good chance for us to chat about it.</p><p><strong>ANDRE</strong>: Absolutely. Collaborating with you and complementing our skills and efforts was a true joy, and I’m so honored to have worked with you.</p><p><strong>NOAH</strong>: Obviously, my first question is, when and how did the concept of the transformable enterprise come about?</p><p><strong>ANDRE</strong>: With age and 17-year professional software development experience, I gradually developed a taste for enterprise architecture, which is now my greatest professional passion. During the past 20 years, the software industry has made progress in so many directions, and the best minds have been busy developing and improving so many new technologies and solutions that nobody was available to answer the big-picture questions that mattered to me. In 2017, I self-published <em>Enterprise Architecture Reimagined,</em> which was my first attempt to understand and shape the big-picture enterprise architecture strategy-something that the best industry minds, immersed deep in various technologies, didn’t have a chance to formulate. Now, it’s time to crystalize the concept, back it up with theoretical arguments, find interesting metaphors, and refine the language.</p><p><strong>NOAH</strong>: What is wrong with that language right now?</p><p><strong>ANDRE</strong>: The only problem with the language that describes the next-generation enterprise is that it simply doesn’t exist. Dutch architect, writer, and theorist N. John Habraken wrote, “Unlike other symbiotic organic phenomena, the built environment escapes rigorous scrutiny, because humans live as an integral part of it. We engage the built environment not to observe from a distance but to act on it, as an object. In judging it and projecting values onto it, we are not accustomed to simply watching it, to learning how it behaves.”</p><p>The same applies to the built digital environment, with one small difference: it is invisible to us. We know what a city looks like, but we don’t even know what an enterprise looks like. We use the digital environment, but don’t talk about it. As far as I know, Jay Forrester and John Zachman were the only two people concerned, the only two people who formulated metaphors for the current state of affairs.</p><p>It was Jay Forrester who said, “Organizations built by committee, by intuition, and by historical happenstance often work no better than would an airplane built by the same methods.” It was John Zachman who said, “The enterprises of today have never been engineered.”</p><p>We need the language for formulating and solving problems, the language that would help us reimagine the enterprise.</p><p><strong>NOAH</strong>: Metaphor has been a persistent topic of ours. I vividly remember debating with you about what metaphors work and what don’t. Why is the metaphor for the concept of enterprise is important?</p><p><strong>ANDRE</strong>: This question was best answered by Gareth Morgan in <em>Images of Organization: The Executive Edition</em>, where he proposed using multiple metaphors to understand organization and management, because</p><ol><li>“In approaching the same situation in different ways, metaphors extend insight and suggest actions that may not have been possible before.”</li><li>“The insights generated by metaphors are not just only theoretical, but also incredibly practical.”</li><li>“Metaphors lead to new metaphors, creating a mosaic of competing and complementary insights.”</li></ol><p>The right metaphor enables us to take advantage of language, knowledge, structures, patterns, breakthrough insights, best practices developed not only in adjacent and related industries, but also in unconventional or unexpected places. I think we were lucky to discover a deep and effective root metaphor for the enterprise-the metaphor that will inspire great enterprise designs.</p><p><strong>NOAH</strong>: If a metaphor is meant to inspire, to what extent can it prescribe? Or can anything prescribe enterprise design?</p><p><strong>ANDRE</strong>: Every metaphor comes with its own set of constraints, accordances, entailments, and ideological associations that help designers change their perspective and think differently about a topic. On the other hand, many metaphors come with their own problems and heavyweight conceptual, practical, and emotional baggage. Metaphors do not prescribe; they invite designers to take advantage of the appropriate knowledge they carry along in the form of rules, roles, scripts, and themes, while avoiding mental traps and side effects.</p><p><strong>NOAH</strong>: Now that we have the perfect metaphor, as the book describes, what is next? If I’m an enterprise architect-obviously a targeted reader-then what is next for me?</p><p><strong>ANDRE</strong>: The book’s target audience consists of people responsible for organization, architecture, engineering, and operations, which means that we are talking about four main groups of readers. Because the book provides only general principles and general guidance, readers should use the fleet metaphor as a source of inspiration and decide for themselves how to organize, architect, engineer, and operate their enterprise as a fleet.</p><p><strong>NOAH</strong>: Change of topic (laughing). We constantly fight each other in our co-writing process. You and I are clearly very different types of people when it comes to creative exploration. How do you perceive that difference?</p><p><strong>ANDRE</strong>: Comparing us is like comparing two artists: an impressionist whose paintings are mindful, dimensional, and sophisticated, and an abstractionist whose works are straightforward, concise, and incomplete. Nevertheless, we somehow manage to take advantage of our strengths and complement our weaknesses.</p><p><strong>NOAH</strong>: I read an article saying that we are in the age of “entanglement,” where “[o]ur communication technology allowed us to build enterprises of unimaginable scope and capability.” So, the enterprise of the future will be very different from what we have now. Besides being transformable, what other qualities a future enterprise would need to have?</p><p><strong>ANDRE</strong>: First, future enterprises must be effective-do the right thing-that is serve the right needs of both customers and employees. Second, they must do it well, which translates into quality of service requirements, such as security, performance, reliability, responsibility, and so on. The third groups of required characteristics are life cycle properties: adaptability, transformability, reconfigurability, flexibility, and so on. Although enterprises of today meet both functional and quality of service requirements, only a few-if any-can quickly adapt to new realities.</p><p><strong>NOAH</strong>: My impression is that when people think about an enterprise or enterprise architecture, they generally think about rather large organizations. What is your take?</p><p><strong>ANDRE</strong>: It depends on the vision, mission, the extent of global reach, and sizes of markets that the enterprise serves. Most companies strive to both expand and optimize by increasing the number of employees and revenue per employee respectively. The latter is an indicator of overall productivity, which usually depends on the technology used.</p><p><strong>NOAH</strong>: I have seen too many organizations taking digital technology stack as enterprise architecture. Any other misfortunes you have seen in the field?</p><p><strong>ANDRE</strong>: An interesting approach to enterprise architecture is described in the book <em>Enterprise Architecture As Strategy</em>, wherein the first chapter is entitled <em>To Execute Your Strategy, First Build Your Foundation</em>. A foundation for execution, according to the authors, is “the IT infrastructure and digitized business processes automating a company’s core capabilities.” The sixth chapter is called <em>Build the Foundation One Project at a Time</em>; the eighth chapter, <em>Now-Exploit Your Foundation for Profitable Growth</em>. This highly popular book links Enterprise Architecture with an abused subject- <em>strategy</em>-and takes advantage of an abused metaphor- <em>foundation</em>.</p><p><strong>NOAH</strong>: What is the problem?</p><p><strong>ANDRE</strong>: While it is often acknowledged that a camel is a horse designed by a committee, if we could suddenly make all enterprises visible, the difference between what they look like and what they should look like would be way more striking than the difference between a camel and a horse. Why? Because committees know what a horse looks like, whereas enterprise architects do not. They do not think the word <em>enterprise </em>should evoke a clear mental image; imageability of an enterprise is not considered important. The result? Enterprises are built “by intuition and by historical happenstance,” as was noticed by Jay Forrester.</p><p><strong>NOAH</strong>: I guess the concept of “enterprise” has lost quite a lot of meaning in recent decades, just like “user experience” does?</p><p><strong>ANDRE</strong>: The Open Group Enterprise Architecture Framework (TOGAF) views four architecture domains-Business Architecture, Data Architecture, Application Architecture, and Technology Architecture-”as subsets of an overall enterprise architecture, all of which TOGAF is designed to support.” This is exactly where the notion of <em>enterprise </em>is lost. Applying it to the horse/camel situation, this is exactly where both the notion of horse and a chance to build a camel are lost.</p><p><strong>NOAH</strong>: This book is the second incarnation of <em>The Transformable Enterprise</em>. I remember the first incarnation was a manuscript written in a fashion very similar to your first book. Then, you had this idea of presenting it in a more conversational tone. I was so surprised-and delighted-when you showed me the revamped draft. Why conversations and presentations? Where did that idea come from?</p><p><strong>ANDRE</strong>: <em>The Posthumous Papers of the Pickwick Club</em>, a.k.a <em>The Pickwick Papers</em>, Charles Dickens’s first novel, which remains one of my favorite books of all time, inspired me to write a book in a similar vein. I wanted it to be less formal and more Canadian. Thank you for supporting the idea 🙂</p><p><strong>NOAH</strong>: Both of us agreed that we wanted to publish this book as fast as possible, even though we have disagreements and regrets about certain topics, opinions, and details. If we were to work on an updated version, what would you change or add?</p><p><strong>ANDRE</strong>: We did two things in the book.</p><p>First, we brought enterprise design to the extreme, reinforcing the real meaning of the word “emergence.” If we remove ships, there will be no fleet. Likewise, if we remove units, there will be no enterprise. An enterprise emerges as a network of units. Units are tangible; networks are intangible. Why are units networked? To make coordination between them possible.</p><p>Second, the book was written in an unconventional, experimental format, which we hoped would help readers understand the theory and motivation behind it. I think only after receiving readers’ feedback on both theory and format will we be able to decide on what should be changed or added.</p><p><strong>NOAH</strong>: The speaker characters in the book have interesting names. Could you provide a behind-the-scene look at them?</p><p><strong>ANDRE</strong>: There is not much behind the scene, because I simply took names from the list of members of Southern Ontario Elite Club of Exotic Sports Historians (SOECESH) who are prohibited to use real names by the club’s statute. So, I simply picked the pseudonyms that I liked and gave them to the event’s speakers.</p><p><strong>NOAH</strong>: Your first book, <a href="https://www.amazon.ca/Enterprise-Architecture-Reimagined-Constructing-Artificially-ebook/dp/B06XDFFW9Z/"><em>Enterprise Architecture Reimagined: A Concise Guide to Constructing an Artificially Intelligent Enterprise</em></a><em> </em>(EAR), has got some frank, negative comments about it being abstract and useless. And I remember us arguing about it, as, frankly, I had similar comments. We also argued about it in writing this book. How can this time be different? I have my answer, but I’d love to hear yours.</p><p><strong>ANDRE</strong>: The book has two negative reviews. Greg D. gave the book 2 out of 5 stars saying, “Thoughtful, very abstract and promotes abstraction but then places everything in the context of manufacturing which sort of blows up the whole abstraction thing, at least as far as the business is concerned.”</p><p>And my intention was exactly that: first, reimagine the architecture, and then show how it can be implemented.</p><p>Then, Richard Foster gave it 1 star arguing, “This book has words, sentences, and diagrams. There is no value for the material beyond that,” which only means that Richard’s expectations were not met. The title of his review-”nonsensense”-likely signifies that the content is even worse than simply nonsense; the reviewer had to invent a new word to express his negative reaction to the book.</p><p>A little bit of history. In 2013, I created a website, , which was my first attempt to introduce a vision of unit-oriented architecture to the world. Although I am a hands-on software architect, not a scientist, I slowly refined the concept and, in 2017, published <a href="https://www.amazon.ca/Enterprise-Architecture-Reimagined-Constructing-Artificially-ebook/dp/B06XDFFW9Z/"><em>Enterprise Architecture Reimagined</em></a><em> </em>(EAR), which was an attempt to build a more solid foundation for further research. Based on readers’ reviews, you can see that the idea to explicitly and transparently align software architecture with human architecture (an operating model) with the aim to provide business units with ownership and control over their digital assets still seems foreign to most architects. Things haven’t changed much today, because the majority of architects still predominate at the Engineering side of the Architecture-Engineering continuum. Consider the title of the book, <em>Fundamentals of Software Architecture: An Engineering Approach,</em> written by leading industry experts Mark Richards and Neal Ford and published by O’Reilly Media in 2020. Our book could be titled “ <em>Basics of Enterprise Architecture: An Architecture Approach</em> “. Yes, we must go back and revisit the basics before progressing further. We have been swimming against the current.</p><p>Nevertheless, I think this book has higher chances for success for two unrelated reasons. First, it is the result of our productive collaboration over several years. Second, it covers the basics of enterprise architecture from four perspectives-science, art, design, and engineering. What do you think?</p><p><strong>NOAH</strong>: I’m definitely seeing a progressive, maturing stream-of-thought from your first book to this one. What I cannot resist mentioning is that, after your first book but before this one, we had actually been working on a derivative work called <em>88 Moments of Enlightenment</em> (88MoE), whose creation saw through a few life-changing events such as my leaving the company we both worked for and relocating to Ottawa. We had heated discussions on how to visualize some of the most important ideas in your EAR book and ended up expanding and maturing some of them. I was inspired all the way through.</p><p>So, that brings back my opinion: some books are for thinking, others are for doing. The former belongs to what I often call thinking tools; the latter, doing tools. Perhaps what everyone should ask is not whether a book is abstract or concrete but whether it is a thinking tool or a doing tool. Just like some people are more of visual learners while others find themselves more effective in learning by texts, perhaps being abstract and being concrete are different in style more often than in a book’s utility.</p><p>To me, your first book is abstract indeed, but more importantly, it is a great thinking tool that inspires me to think further, even though that means it probably wouldn’t help me much in figuring out how to do it. This book is a continuation of that vein, but the ideas have become much more developed since your first one. Are you angry at me now?</p><p><strong>ANDRE</strong>: Certainly not, I highly appreciate our productive collaboration and wish that you co-authored the first one with me. I have two questions for you, too. First, how would you estimate the probability of this book getting 1-star “nonsensense” type of feedback? In my opinion, the probability is rather high, considering we are not singing the same song as the majority of enterprise architects. We see them as wolves in sheep’s clothing-engineers masquerading as architects. Second, how do they see us? Do they even see us?</p><p><strong>NOAH</strong>: Negative feedback is our friend, and I’m sure we will get it, which is good. Hopefully, our book could inspire future architects, designers, engineers, artists, and scientists to write something that is more concrete. But, for now, I think we need to challenge the foundation of the discipline by remaining at a high level. It is probably irrelevant how they end up seeing us. I do not care, and I bet neither do you.</p><p><strong>NOAH</strong>: So, now, our dear readers have our book in their hands. What is next? In my case, I will start planning on translating both your and our books into Chinese, and I also want to write something about design. What is next for you?</p><p><strong>ANDRE</strong>: I think we now have an environment in which the birth of a coordination revolution is inevitable. Although currently, the Internet successfully takes care of global connectivity and communication, coordination is still done implicitly. A company that will build explicit coordination structures on top of connectivity and communication has the best potential to become the next Google. I will collaborate with the New Key Club on that.</p><p><strong>NOAH</strong>: It has been a pleasure chatting and collaborating with you! I sincerely wish we could write together in the future!</p><p><strong>ANDRE</strong>: Thank you! I have no doubts that we will.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2Gn_Nrib3tKPzCss" /></figure><p><a href="https://www.amazon.ca/dp/B08YPBCGXK/"><em>The Transformable Enterprise: Enterprise Architecture in a New Key</em></a> is now available on Amazon.</p><p>Andrey and Noah have started working on a new book on organizational politics.</p><p>{END}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/196/0*9DUZXfmoR9eM5-12" /></figure><p>Working on design, strategy, and organizational transformation. Design practitioner, author and interactive storytelling pilgrim. Was creative director, user experience manager, product manager, visual designer, editor, translator, software developer and more.</p><p><a href="https://kingofark.com/author/kingofark/">View all posts by kingofark</a></p><p><em>Originally published at </em><a href="https://kingofark.com/2021/03/11/the-road-to-transformable-enterprise-reflective-conversations-on-writing-and-more/"><em>http://kingofark.com</em></a><em> on March 12, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33438365520b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design, Acting, and the Fourth Wall]]></title>
            <link>https://medium.com/@kingofark/design-acting-and-the-fourth-wall-24ced4c0953b?source=rss-495036b10f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/24ced4c0953b</guid>
            <dc:creator><![CDATA[Noah Fang]]></dc:creator>
            <pubDate>Sat, 06 Feb 2021 03:25:53 GMT</pubDate>
            <atom:updated>2022-08-05T01:57:27.506Z</atom:updated>
            <content:encoded><![CDATA[<h3>A conversation regarding <a href="https://www.imdb.com/name/nm0078746/">an actor</a> prompted me to revisit a few thoughts on the similarities between design and acting.</h3><p>I always think that, screen acting is a bit like product design, stage acting is a bit like service design.</p><h3>Screen Acting is Like Product Design</h3><p>Screen acting attends to the camera, and the camera is the ultimate representative of the audience. The camera is the audience’s eyes.</p><p>All that matters is how it looks, sounds, and feels from the camera’s angle — that of the audience. It doesn’t matter how it looks, sounds, and feels from any angle other than that of the camera. Every single detail on the screen is designed to attend to the camera.</p><p>You probably can’t get any more user-centric than that.</p><h3>Stage Acting is Like Service Design</h3><p>Stage acting, on the other hand, deals with interactivity in an intimate way.</p><p>Both the stage and the performance are designed to provoke reactions from the audience, right then right there. When the actor on the stage talks, she’s always talking to or for the audience. More often than not, the stage actors need to react to the audience in an improvised manner in every show. That’s why no two shows of the same play are really the same. And perhaps every stage play fan knows exactly where the excitement comes from — an unparalleled level of interactivity and intimacy.</p><p>You probably can’t get any more servitude than that.</p><h3>Digital Interface Has a Fourth Wall</h3><p>Digital products and services have a <a href="https://en.wikipedia.org/wiki/Fourth_wall">fourth wall</a> issue, while physical ones often don’t.</p><p>Digital interface is designed to impersonate. Users intuitively regard it as if it’s a living entity, who prompts, reacts, and asks back.</p><p>When does an interface talk to the user? When should it do so? When can it pose as if talking to itself? And when could it love you back?</p><p>Perhaps the fourth wall is what designing and acting share in a profoundly allegorical way.</p><h3>Further Reading</h3><p>The intersection of computer and storytelling is a fascinating topic. Here are a few worthy reads to expand your thinking:</p><ul><li><a href="https://www.goodreads.com/book/show/31850799-hamlet-on-the-holodeck-updated-edition"><strong><em>Hamlet on the Holodeck</em></strong></a> explores the eye-opening innovations of digital storytelling.</li><li><a href="https://www.goodreads.com/book/show/19313005-computers-as-theatre"><strong><em>Computers as Theatre</em></strong></a> captures the synergy between human-computer interaction and drama.</li><li><a href="https://www.goodreads.com/book/show/981377.The_Art_of_Interactive_Design"><strong><em>The Art of Interactive Design</em></strong></a> deepens your understanding on the concept of interactivity like no other.</li></ul><p>{END}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/197/0*mae7H7q_6M7463sY" /></figure><p>UX/Service Designer. Interactive Storytelling pilgrim. Translator. Was Creative Director, Product Manager, Programmer, Layout Designer, Editor &amp; more…</p><p><a href="https://kingofark.com/author/kingofark/">View all posts by kingofark</a></p><p><em>Originally published at </em><a href="https://kingofark.com/2021/02/05/design-acting-and-the-fourth-wall/"><em>http://kingofark.com</em></a><em> on February 6, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24ced4c0953b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hubbub Weekly #3]]></title>
            <link>https://medium.com/series/hubbub-weekly-3-37e5314fd996?source=rss-495036b10f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/37e5314fd996</guid>
            <dc:creator><![CDATA[Noah Fang]]></dc:creator>
            <pubDate>Fri, 06 Mar 2020 20:38:00 GMT</pubDate>
            <atom:updated>2020-03-06T20:38:00.724Z</atom:updated>
            <content:encoded><![CDATA[<h3>From the Editor</h3><p>I’ve been reading about power and organizational change for some time.</p><p>The concept of power is like sex: it’s very easy to grasp, but very difficult to understand.</p><p>It’s complicated:</p><blockquote>Everything is about sex. Except sex. Sex is about power.</blockquote><p>- <em>Francis Underwood</em> in <em>House of Cards</em></p><p>I’m specifically interested in how power is created, utilized, weaponized, sustained, deprived, and obsoleted in an organization.</p><p>It’s a road that leads to many branches, none of which I’ve fully explored.</p><p>My heart is not in design this week, thanks to some crunchy reads that followed.</p><p>~Noah</p><h3>Crunchy Reads</h3><h3>Paul Graham: How to Write Usefully</h3><p>It appears that my writing is more correlated with my reading than with my work.</p><p>There were distinct periods of time when I managed to read, and therefore learn, a lot, and thoughts and ideas seemed endless, that I had to frequently take out my phone and take notes lest I forget.</p><p>I haven’t published anything on my website for about 3 months. And I still don’t think I have anything I’d like to publish.</p><p>I do have many unfinished drafts. And that’s how <a href="http://paulgraham.com/useful.html">Paul Graham’s article</a> makes a lot of sense to me:</p><blockquote>…if you write a bad sentence, you don’t publish it. You delete it and try again. Often you abandon whole branches of four or five paragraphs. Sometimes a whole essay.</blockquote><p>I just don’t like any of my drafts enough. They’re going to be revised until I do.</p><p>There are quite some resonant points and insightful delights <a href="http://paulgraham.com/useful.html">in the article</a>:</p><blockquote>…it’s not enough merely to be correct. It’s easy to make a statement correct by making it vague.</blockquote><p>Maybe writing is not always about being correct. Provoking thought doesn’t have to be about affirming truth.</p><p>Here’s something resonant:</p><blockquote>Precision and correctness are like opposing forces. It’s easy to satisfy one if you ignore the other.</blockquote><p>And this should be the standard for writing a blog post:</p><blockquote>Useful writing tells people something true and important that they didn’t already know, and tells them as unequivocally as possible.</blockquote><p>Interesting, but I don’t agree:</p><blockquote>You need humility to measure novelty, because acknowledging the novelty of an idea means acknowledging your previous ignorance of it.</blockquote><p>Agree, but it’s not interesting:</p><blockquote>…we just have to face the fact that elegance and curtness are two names for the same thing.</blockquote><p>This is so spot-on:</p><blockquote>…people who disagree with you rarely disagree with what you’ve actually written. Instead they make up something you said and disagree with that.</blockquote><p>And THIS (!) cuts into the challenges of organizational change:</p><blockquote>People are as ingenious at misrepresenting you when you say something they don’t want to hear as they are at coming up with rationalizations for things they want to do but know they shouldn’t. I suspect it’s the same skill.</blockquote><p>You deserve <a href="http://paulgraham.com/useful.html">such a great read</a>!</p><h3>The Evolution of Revolutions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/341/1*NhZwxA4NiFJmTKUZBVcjTQ.jpeg" /><figcaption><a href="https://www.amazon.com/dp/B005EER0B4/">The Evolution of Revolutions: How We Create, Shape, and React to Change</a></figcaption></figure><p>My dear friend Andre, who bought me the book, told me that it’s one of his recent favorite books.</p><p>Not all popular or bestselling books are great. In fact, most of them aren’t.</p><p>Some hidden gems simply rest somewhere, in a book store or library, as a mere digital record, or, in my case, as a birthday gift, in hardcover that could only be purchased through 3rd-party sellers on Amazon.</p><p>Base on my friend’s impeccable track record of book recommendations, I doubt it’s going to be a bad read.</p><p>Its table of content is appealing.</p><h3>The End of Power</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/333/1*7EWpwSTNeCk-JcF6pqCshA.jpeg" /><figcaption><a href="https://www.amazon.com/End-Power-Boardrooms-Battlefields-Churches-ebook/dp/B00IXQQ6GU/">The End of Power</a></figcaption></figure><p>“Isn’t what it used to be” is rather vague, so I’m not convinced by its basic premise. Let’s see what I can learn from the book.</p><h3>Worthy Bites</h3><h3>Scott Berkun</h3><blockquote>The main cause of tension between designers and other roles (PM/dev/VP) is the lack of shared goals. “This experience is bad” vs “that’s low priority.” It’s a bad/uphill tactical situation.</blockquote><blockquote>The wise play is to avoid lost causes. But invest instead in changing the landscape.</blockquote><blockquote>Good leaders pave the way for goodness. They identify mismatched goals early and resolve them so people in different roles can easily work together.</blockquote><blockquote>Bad leaders fly behind the plane. They try to deal with strategic problems too late and at the tactical level.</blockquote><p><a href="https://twitter.com/berkun/status/1233105891152412672?s=21">Source</a></p><h3>Lisa Cormier</h3><blockquote>Let’s talk about the role of design in government discourse around disruptive tech experimentation. ☕️ Experimentation needs to be hypothesis-driven. And that’s the importance of having a discovery phase, to allow the team time to formulate hypotheses.</blockquote><blockquote>Experimentation isn’t just “quickly building something”. One of the designer’s roles is to ask key questions. For example, when a team is asked to do a proof of concept, it’s important to ask the question: what are you being asked to prove?</blockquote><blockquote>Is the question… 1) Can we build this? Is it technically feasible? 2) Does it solve or improve problem X ? By how much? 3) What are the potential effects of solution Y on population Z? 4) Does the organization have the capability to support this?</blockquote><blockquote>Depending on the question we’re trying to answer, a proof of concept some questions could be answered by a low-fi prototype, it may or may not need to be “live”; until we have a clear question and hypothesis, we can’t “commit” to specific deliverables or timelines.</blockquote><blockquote>And once timelines and deliverables are set in stone, there is very little working-level folks can do to change the directions of a project. This isn’t agile, and it also isn’t in the spirit of experimentation.</blockquote><blockquote>To formulate a hypothesis, before building, we need to understand: what research currently exists that can help answer the research question? Maybe someone has already done the same research.</blockquote><blockquote>To answer 2, 3, and 4, along with experimentation, you need to do some contextual research to understand potential or existing users, the business problem, and the organizational capacity. Without that, you can’t formulate a hypothesis.</blockquote><blockquote>From what I’ve seen, many disruptive tech projects, if they even have defined a question, the focus tends to be more on 1) Can we build this? (purely technical feasibility), which I think misses a lot of other opportunities.</blockquote><p><a href="https://twitter.com/lisauxstories/status/1235903045835411456?s=21">Source</a></p><h3>Mike Monteiro</h3><blockquote>Some people say that good design is invisible. That when it’s done right you shouldn’t notice it. I say they’re looking in the wrong place. Turn around. Good design is very visible. It’s visible on the face of every person who’s ever used a well-designed service. The slightly raised eyebrow that says, ‘huh, I expected that to be a lot harder’, followed by a recognition that they just reclaimed some time to read a book, or play with their kid, or walk their dog — whatever it is they actually want to do. That’s good design. It’s pretty visible. You just have to know where to look.<br> <br> We don’t design for screens. We don’t design for organizations. We don’t design for shareholders. We design for people.</blockquote><p>— Mike Monteiro, Foreword for <a href="https://www.bispublishers.com/good-services.html">Good Services: How to Design Services That Work</a></p><h3>Hubbub Weekly</h3><p>Issue 3</p><p>6 March 2020</p><p>Editor: Noah Fang</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37e5314fd996" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hubbub Weekly #2]]></title>
            <link>https://medium.com/series/hubbub-weekly-2-eab9bc2e3117?source=rss-495036b10f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/eab9bc2e3117</guid>
            <dc:creator><![CDATA[Noah Fang]]></dc:creator>
            <pubDate>Wed, 26 Feb 2020 14:05:13 GMT</pubDate>
            <atom:updated>2020-02-26T14:05:13.678Z</atom:updated>
            <content:encoded><![CDATA[<h3>From the Editor</h3><p>Do designers dream of falling stickies?</p><p>Does an Agile team dream of orgasmic sprints?</p><p>There seems to be always a sin behind a buzz.</p><p>Noah</p><h3>Best Readings</h3><h3>Are Design Sprints Absurd?</h3><p>In <a href="https://link.medium.com/JuPm9PKP83">a thought-provoking post on the absurdity of Design Sprints</a>, Jeff Davidson points out three reasons:</p><blockquote>First, it lacks any scientific rigor. Second, it creates social tension, leading to hurt egos and learned helplessness. Lastly, it is just too hasty and rudimentary for massive, multi-million dollar decisions to be made.</blockquote><p>Besides lots of quotable insights, to me it shows just how coupled a practice is with the culture of the practicing team – sure, Design Sprints may actually work in some teams. But how much of it is due to following a generalized method?</p><p>In scientific communities, you’d have to publish your method of research and other teams would have to be able to replicate your research results, in order for your findings to bear any scientific value.</p><p>If a practice is not scientific, then how do we tell it from snake oil?</p><p>That, dear reader, is the burning question few would like to answer.</p><p>-</p><h3>Jon Kolko: Drawing doesn’t present knowledge. It creates it.</h3><p>In his characteristically approachable style, <a href="http://www.themoderniststudio.com/2020/02/18/drawing-doesnt-present-knowledge-it-creates-it/">Jon Kolko reiterates the profound value of design making</a>.</p><h3>Do You Eat Garbage For a Living?</h3><p>In <a href="https://www.vulture.com/2020/02/spread-of-corporate-speak.html">a mildly entertaining article</a>, its author reflects on how garbage language thrives in corporate culture.</p><h3>New Book: How Design Makes the World by Scott Berkun</h3><p><a href="https://scottberkun.com/how-design-makes-the-world/">Scott Berkun’s upcoming book</a> is easily one of the most anticipated books in 2020.</p><h3>Worthy Bits</h3><h3>Jonathan Lupo</h3><blockquote>It’s not engineering-led or design-led, its customer-led. The one perspective that cuts across the complex dimensions of a service ecosystem is the customer’s perspective.</blockquote><p><a href="https://twitter.com/userexperience/status/1229199312145412098?s=21">Source</a></p><h3>Dan Brown</h3><blockquote>Some people think the opposite of collaboration is “working independently”.</blockquote><blockquote>But actually, the opposite of collaboration is being an asshole.</blockquote><p><a href="https://twitter.com/brownorama/status/1230132973904842753?s=21">Source</a></p><h3>Anonymous</h3><blockquote>If we avoid responsibility to try to avoid blame, we will get no responsibility, but still get the blame.</blockquote><h3>Pavel A. Samsonov</h3><blockquote>Design practice has evolved outwards towards the user, but done a fairly poor job of evolving inwards to control its own role in an org.</blockquote><blockquote>Design a semantic environment where design makes sense.</blockquote><p><a href="https://twitter.com/pavelasamsonov/status/1232657669942632451?s=21">Source</a></p><h3>Hubbub Weekly</h3><p>Issue #2</p><p>26 Feb. 2020</p><p>Editor: Noah Fang</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eab9bc2e3117" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hubbub Weekly #1]]></title>
            <link>https://medium.com/series/hubbub-weekly-1-1a548619dfaf?source=rss-495036b10f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a548619dfaf</guid>
            <dc:creator><![CDATA[Noah Fang]]></dc:creator>
            <pubDate>Mon, 17 Feb 2020 01:02:54 GMT</pubDate>
            <atom:updated>2020-02-17T01:02:54.679Z</atom:updated>
            <content:encoded><![CDATA[<h3>From the Editor</h3><p>Hubbub Weekly is a place to reflect, share, and learn.</p><p>I sincerely hope that this is the start of a beautiful friendship.</p><p>Noah</p><h3>Recent Readings</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/210/1*Yk72YzeUu0C7-xynoMqqCQ@2x.jpeg" /><figcaption>Designing the Invisible: An Introduction to Service Design</figcaption></figure><p>Concise, broad, and defining, <a href="https://www.bloomsbury.com/uk/an-introduction-to-service-design-9781472572585/">the book</a> is probably the best single-volume entrance to the world and discipline of service design.</p><p>Well, that’s not to say the field-defining <a href="http://thisisservicedesignthinking.com/">This is Service Design Thinking</a> and <a href="https://www.thisisservicedesigndoing.com/">This is Service Design Doing</a> are not as good. The latter can be a great second book and reference at hand.</p><h3>Alan Cooper talks about the invention of persona.</h3><p><a href="https://link.medium.com/84BvteQ613">In a recent medium post</a>, Alan Cooper sheds light on his personal history of Persona.</p><p>Even though there’s abundant evidence that persona works, it appears that it’s also widely misunderstood and misused.</p><p>When is a good time to dig deeper and truly understand it?</p><p>The answer: anytime, but better sooner than later!</p><h3>The Missing Point</h3><p>Is everyone a designer?</p><p>Does everyone design?</p><p>There seems to be an obsession there, the obsession of entitlement.</p><p>Fortunately <a href="https://link.medium.com/tUJbawq713">this post settles it</a>.</p><h3>The Shirky Principle</h3><blockquote>Institutions will try to preserve the problem to which they are the solution.</blockquote><p><a href="https://www.theifod.com/beware-the-shirky-principle/">Never too late to learn</a>. That should answer quite some burning questions about your work experience in a bureaucracy.</p><h3>Worthy Bits</h3><h3>Scott Berkun</h3><blockquote>“What’s in the manager’s best interest [for communication/collaboration tools] may not be in the interest of the people who work for them and therefore not used.”</blockquote><blockquote>– Grudin’s Paradox</blockquote><p><a href="https://twitter.com/berkun/status/1227747412447391744?s=21">Source</a></p><h3>Jared Spool</h3><blockquote>I’ve come to believe that ‘alignment’ is a business code word for ‘getting everyone else to stop arguing with me.’</blockquote><p><a href="https://twitter.com/jmspool/status/1227758663647055872?s=21">Source</a></p><h3>Pavel A. Samsonov</h3><blockquote>“Designer” is a rich role. You’re not just producing outputs, but running a produce-act-revise cycle to map the path from outputs to outcomes.</blockquote><blockquote>There’s another word for people who go “hey, can you build me a thing, and I want it to do this and this”.</blockquote><blockquote>Everyone is a definer.</blockquote><p><a href="https://twitter.com/pavelasamsonov/status/1225118665441521666?s=21">Source</a></p><h3>Lisa Cormier</h3><blockquote>…instead of counting sheep to help fall asleep, designers count the post its they used during their last design thinking workshop.</blockquote><p><a href="https://twitter.com/lisauxstories/status/1224504132037414912?s=21">Source</a></p><h3>Editor</h3><p>Noah Fang</p><p>Hubbub Weekly Issue #1</p><p>15 Feb. 2020</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a548619dfaf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Debunking The Myth of Design (Thinking) Process]]></title>
            <link>https://medium.com/@kingofark/debunking-the-myth-of-design-thinking-process-a0a6fdd1ee87?source=rss-495036b10f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0a6fdd1ee87</guid>
            <dc:creator><![CDATA[Noah Fang]]></dc:creator>
            <pubDate>Thu, 08 Nov 2018 13:30:56 GMT</pubDate>
            <atom:updated>2022-08-05T01:53:25.875Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>“The correct regulative principle for anything depends on the nature of that thing.”</em></blockquote><blockquote>– John Rawls</blockquote><h3>Design Process is Not a Process</h3><p>The biggest misconception about design process is perhaps that we interpret it too literally.</p><p>Design process is not a “process” per se.</p><blockquote>The act of designing doesn’t have a universal “process”. It’s highly coupled with the cultural and organizational environments of the practitioners, and with the peculiarities of the actual project.</blockquote><p>Designing is a very dynamic act of creative exploration and problem solving. Describing it as a process sacrifices, understandably for communicative clarity, the core practice that makes design different from a mechanical process.</p><p>We borrowed the word “process” because it’s the easiest to understand, not because it’s accurate.</p><p>The act of designing doesn’t have a universal “process”. It’s highly coupled with the cultural and organizational environments of the practitioners, and with the peculiarities of the actual project.</p><p>Every team adapts a unique process of their own to play to the strengths of <a href="https://kingofark.com/2018/08/07/whats-driving-design-in-your-org/">their design capabilities, especially in creativity, insight, and data</a>.</p><h3>Design Phases</h3><p>We can, however, identify what I call “ <em>design phases</em> “ in an overarching temporal logic. Design phases don’t specify what we do. They signify what we aim to understand and/or achieve.</p><p>We wouldn’t aim to verify the feasibility or viability of a specific product or feature before we even have any understanding of what the stakeholders are trying to address.</p><p>However, during the pre-project planning and early discussions, nothing prevents us from coding interactive presentations or creating visionary mockups, with agility, as handy techniques to communicate ideas, explore themes in problem space, or appetize up everyone’s taste. Likewise, nothing invalidates our using empathizing methods during later phases of development and deployment, to further refine or catch mistakes we can’t afford to miss out, or to probe visions for future iterations.</p><blockquote>A design practitioner may do anything in any step of a prescribed process, but often with very different goals in different steps.</blockquote><p>A design practitioner may do anything in any step of a prescribed process, but often with very different goals in different steps.</p><p>In other words, we do everything we can to address the non-mechanical dynamics and emergent uncertainties during a creative effort (which is usually meant to solve problems), and creatively use existing techniques and methods in new contexts, depending on the particularities of the respective effort (often in the form of a project).</p><p>Now imagine we literally stick to the canonical design thinking process that prescribes “empathize” as the first step of that process- does that mean we don’t empathize in later steps? After all, by conventional understanding, isn’t a “step” something we don’t get back to after we arrive at the next step? No wonder <a href="https://link.medium.com/8ouaOXL0CR">design thinking sounds like bullshit</a>.</p><h3>Repeatable Processes in Design Phases</h3><p>The implication is that, there are many repeatable design processes that are useful in the overarching, overlapping, while temporally sequential design phases.</p><p>Those phases can’t be defined by what we do in each, but by what we hope to achieve, especially in terms of understanding.</p><p>But, some may argue, whatever we call it, process or phase, isn’t it meant to prescribe actions? Otherwise how do we know what we should do to get things done and have problems solved? Some may ask, if design phases don’t specify what to do, then how do we practically follow through without inducing outrage in project planning and risk management? After all, modern management and operation rely on people being able to follow well-defined processes with actionable best practices.</p><p>The notion of design phases is nothing new. We all know how it works. Some of us know better. Think about it: the agile and lean practices already embody the notion of repeatable design (and development) processes.</p><blockquote>The grave mistake we make about adopting design process is that we assume creative effort can, in the triumphant analytical tradition, be divided into smaller steps.</blockquote><p>The grave mistake we make about adopting design process is that we assume creative effort can, in the triumphant analytical tradition, be divided into smaller steps, where we tend not to revisit a previous step when we’re at the current step. By framing a design process this way, it makes it much easier to accommodate the design effort to the existing risk management framework, which was established in a period when industrialization focuses more on mechanical automation than scaling creativity and innovation.</p><p>But that’s just not <a href="https://www.amazon.com/Designerly-Ways-Knowing-Nigel-Cross-ebook/dp/B000SNUQ7Q/">how a designer works</a>.</p><h3>The Designerly Way of Doing</h3><p>In his book <a href="https://www.amazon.com/Design-Thinking-Understanding-Designers-Think-ebook/dp/B005GZL8Z0/"><em>Design Thinking: Understanding How Designers Think and Work</em></a>, Nigel Cross describes how the renowned product designer <a href="https://en.m.wikipedia.org/wiki/Philippe_Starck">Philippe Starck</a> came about the idea of his famous lemon squeezer design:</p><figure><img alt="Juicy Salif lemon juicer by Philippe Starck. Designed for Alessi (1990)." src="https://cdn-images-1.medium.com/max/662/1*ihQqdEaCmbwgMWkoMWfi1Q.png" /><figcaption><em>Juicy Salif lemon juicer by Philippe Starck. Designed for Alessi (1990).</em></figcaption></figure><p>Photo by Niklas Morberg [ <a href="https://creativecommons.org/licenses/by-sa/2.0">CC BY-SA 2.0</a>], via Wikimedia Commons</p><blockquote>“Alessi invited Starck to offer a new product in the ‘designer’ series, a lemon squeezer. Starck went to Italy to visit Alessi and discuss the project. He then took a short break on the small island of Capraia, just off the Tuscan coast, and went to dine in a pizzeria restaurant, Il Corsaro. He was obviously already thinking about the lemon squeezer project, because, as he waited for his food, he began to sketch on the paper place mat. At first, the sketches were just very rough images of a fairly conventional form of lemon squeezer (see the centre-right area of the place mat, Figure 1.3), but then something happened to inspire a leap to making sketches of something quite different -his anti-pasto plate of baby squid had arrived, and Starck began to get his ‘vision of a squid-like lemon squeezer’! His sketches on the place mat now became images of strange forms with big bodies and long legs, and eventually (bottom left in Figure 1.3) something emerged that is now recognizable as the Juicy Salif concept.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uHPF0xWpHWioLhGOMH7HDg.png" /><figcaption><em>Screenshot of Nigel Cross’s book, Design Thinking: Understanding How Dedigners Think and Work</em></figcaption></figure><p>A well-defined design process that prescribes actions would probably never lead Starck to such a design, because how could we possibly take the creative influence of seafood into consideration when drafting a supposedly universal process?</p><p>However, we can still identify a phase in Starck’s creative effort. In that early phase of creative exploration, he tried to synthesize many things, including the client’s prescribed vision, his own perception of the client’s existing products, and also his inspiration. As a designer, he strived to understand both the client’s problem space and himself for that synthesis. And, nothing prevented him from sketching on a paper place mat.</p><h3>Design Synthesis is Not a Step-by-Step Process</h3><blockquote>Process precribes techniques and methods based on best practices. But the process alone is too far away from codifying the creative power of designing.</blockquote><p><a href="https://www.amazon.com/Exposing-Magic-Design-Practitioners-Interaction-ebook/dp/B005OLBEVE/">Design synthesis</a> happens whenever and wherever a designer needs it to. No “steps” in “processes” can frame its internal dynamics. And if we don’t understand that, <a href="https://kingofark.com/2018/10/24/why-agile-projects-fail-and-other-misconceptions/">we’d simply become more likely to fail no matter what “process” we choose to adopt</a> in our own design practice.</p><p>Perhaps, the real teaching of design, or design thinking upon popular demand, is not that we can “follow steps”, but that we should understand the nature of the practice and organically absorb it into our own way of doing things.</p><p>Process precribes techniques and methods based on best practices. But the process alone is too far away from codifying the creative power of designing.</p><p>Not that phases can. Nothing can codify creative power.</p><p>However, we can learn. And then facilitate it.</p><h3>Understanding the Creative Practice</h3><p>The first step (the wonderful, mythical “step”!) is to acquire <a href="https://kingofark.com/2018/02/06/2x2x2-six-books-you-deserve-as-a-designer/">a basic but foundational understanding of the design practice</a>.</p><p>Without that understanding, we can’t <a href="https://kingofark.com/2018/08/01/design-in-business-and-business-in-design/">make informed decisions</a> about how we can adopt a prescribed design “process” in the first place. And through that basic understanding, we aim to identify the design phases necessary and applicable in our own context, be it work culture or project specifics.</p><p>{END}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/197/0*dGm3tkzFnnxYkVjN" /></figure><p>UX/Service Designer. Interactive Storytelling pilgrim. Translator. Was Creative Director, Product Manager, Programmer, Layout Designer, Editor &amp; more…</p><p><a href="https://kingofark.com/author/kingofark/">View all posts by kingofark</a></p><p><em>Originally published at </em><a href="https://kingofark.com/2018/11/08/debunking-the-myth-of-design-thinking-process/"><em>http://kingofark.com</em></a><em> on November 8, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0a6fdd1ee87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Chain of Intentions in Interaction Design]]></title>
            <link>https://medium.com/@kingofark/the-chain-of-intentions-in-interaction-design-9994e1b27f2e?source=rss-495036b10f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/9994e1b27f2e</guid>
            <dc:creator><![CDATA[Noah Fang]]></dc:creator>
            <pubDate>Wed, 05 Sep 2018 12:30:54 GMT</pubDate>
            <atom:updated>2022-08-05T01:46:38.519Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design is purposeful. Interaction is intentional.</h3><p>There’s a chain of intentions in Design. They are connected by interactions and justified by purpose. Structuring the flow of those intentions is a critical part of design.</p><h3>Intention Vs. Purpose</h3><p>For clarity, let’s first differentiate intention from purpose. We can loosely define <em>intention</em> in design as the goal of the immediate actions taken by a user, while <em>purpose</em> narrowly as the eventual goal in business or user sense, such as solving a business problem or meeting a user need. Although the actions realize the serving of purposes, they don’t necessarily and directly reflect them — they reflect intentions.</p><p>Saving a record of transaction by tapping the “Save” button is an intention, while keeping the transaction on record for verification or as evidence is the purpose business-wise.</p><p>What you want to do doesn’t necessarily reveal what you want to achieve. And vice versa.</p><h3>Two Types of Intentions: Functional and Purposeful</h3><p>You click a “Read More” button with both the intention of opening a view of some details, and that of reading more of it.</p><p>When you press the pedestrian crossing button at a traffic light, your intention is to make sure the button is pressed, while your purpose is to cross the road safely.</p><p>When a user searches for “return policy”, his intention may be to know more about it, while his purpose might just be to decide whether it’s worth the hassle to return that annoyingly loose pair of gloves.</p><p>We never can tell with common people. <em>Some intentions in design are more equal than others.</em></p><p>So it helps a lot if we differentiate two different types of intentions:</p><ul><li><strong><em>Purposeful Intentions</em></strong>: directly relevant or related to the purpose of the design, which usually directly reflects business goals or user goals.</li><li><strong><em>Functional Intentions</em></strong>: indirectly relevant due to the nature of the technology. They are derived from the limitations of the technology used for the purpose.</li></ul><p>Purposeful intentions are like the main plot of a story — their twists and turns push the drama forward. Functional Intentions are like style, genre, subplots, or visual effects — they are meant to enable or enhance the dramatic and narrative design in both an artistic and a practical way.</p><p>There’s a fine line between the two types of intentions. Sometimes an identified intention is both purposeful and functional. The whole point of the dichotomy is not to draw an absolute line, but to provide a thinking tool for us to elaborate and make design decisions.</p><h3>Functional Interaction and Purposeful Interaction</h3><p>Interaction with functional intention is Functional Interaction. That with purposeful intention is Purposeful Interaction.</p><p>Consciously or not, users have different expectations on those two types of interactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*-9t6Z0iGijdGjHf6" /></figure><p>As listed above, the differences between functional interaction and purposeful interaction are straightforward.While there are two thing to note here:</p><ul><li>In a purposeful interaction sequence, the expected time spent can be minimal or maximal. Sometimes users enjoy the moment more when it lasts longer, especially when the purposeful interactions signals the achievement of something.</li><li>The effort taken should usually be minimal. However, in purposeful interactions, the effort should, at times, be significant enough for users to justify the outcome as well as a sense of achievement. Sometimes achieving too easily brings less satisfaction.</li></ul><h3>Planning the Chain of Intentions by Sequencing Interactions</h3><p>There are often likely much more functional interactions than purposeful ones, so the sequencing of interactions usually aims to keep the users on track, avoiding confusion and interaction failures, or engage them in a dramatic way.</p><p>Here are some common patterns:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*tUBNyJGJ8NK1e8ac" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*3kG3R6likszmCDFP" /></figure><p>There could be problematic chain of intentions/interactions that lead to interaction confusion or failure.</p><p>Here are a few questionably bad patterns:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*8DjXaamAxOwkFPA8" /></figure><p>Most of the questionable patterns can be easily fixed by a mindful and elaborate designer. Perhaps the challenge lies in identifying the problems rather than coming up with the solutions. Fortunately, careful user test should often be enough to identify those interaction issues.</p><h3>What Does That Mean to Designers</h3><p>As a framework, the functional-purposeful dichotomy is first and foremost a thinking tool. It’s meant to be used for elaborating design situations and for making design decisions.</p><p>It helps us decide when, where, and how much to:</p><ul><li>Optimize on effectiveness and efficiency</li><li>Focus on fluency, pace, or engagement throughout and across the user flows</li><li>Provide assurance</li><li>Reward user actions</li><li>Reduce or promote distractions</li></ul><p>A decent interaction design always goes with elaborate planning of the chain of intentions. And when done well, the experience delights the users with senses of achievement and meaning.</p><p>Design is purposeful. Interaction is intentional. Intention is full of influence, which designers are responsible for.</p><p>{END}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/197/0*EE-ZnG7muLOyxbWA" /></figure><p>UX/Service Designer. Interactive Storytelling pilgrim. Translator. Was Creative Director, Product Manager, Programmer, Layout Designer, Editor &amp; more…</p><p><a href="https://kingofark.com/author/kingofark/">View all posts by kingofark</a></p><p><em>Originally published at </em><a href="https://kingofark.com/2018/09/05/the-chain-of-intentions-in-interaction-design/"><em>http://kingofark.com</em></a><em> on September 5, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9994e1b27f2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Reasoning and The Innovation of Meaning]]></title>
            <link>https://medium.com/@kingofark/design-reasoning-and-the-innovation-of-meaning-5538e47db89a?source=rss-495036b10f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/5538e47db89a</guid>
            <dc:creator><![CDATA[Noah Fang]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 12:30:30 GMT</pubDate>
            <atom:updated>2022-08-05T01:45:21.771Z</atom:updated>
            <content:encoded><![CDATA[<h3>What’s peculiar about the relationship between design and innovation? Why are they so related in the rhetorics of the past decades? How does design lead to innovation (if at all)? When and where do design and innovation overlap?</h3><p>The clues might just be here, right in the understanding of design and the perspective on innovation.</p><h3>Design As a Form of Reasoning</h3><p>Let’s start from Kees Dorst’s formulation of design as a form of reasoning in his brilliant book <a href="https://mitpress.mit.edu/books/frame-innovation"><em>Frame Innovation</em></a> (here’s <a href="https://kingofark.com/2015/12/03/book-review-frame-innovation-2/">my review</a>).</p><p>The initial framing is that <em>What</em> and <em>How</em> lead to an <em>Outcome</em> (plus an additional context of <em>Why</em> embedded in the meaning of that outcome).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*yl-TO8muUF2YKNXQ" /></figure><p><em>What</em> is about the elements or topics involved. <em>How</em> is about patterns of relationships, or approaches. The <em>Outcome</em> is often an observed phenomenon, something we can measure.</p><h3>Deduction</h3><p>In that framing, deduction is easy to follow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*YnXbftM7RtZWC78D" /></figure><p>Building a website is almost such a case: we know what it is (say, personal site for branding purpose) and how to build it (WordPress), and we can be pretty precise on the outcome. It’s all well established practices. No alarms and no surprises.</p><h3>Induction</h3><p>Induction is just as understandable:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*HLuG1zmPMQx2XKu4" /></figure><p>Sciences make use of induction: we observe a phenomenon about something, and we propose hypotheses to try to explain how things work. When the results derived from a hypothesis match what we observed, we become more confident in the appropriateness of our formulation of How.</p><p>When your business releases a successful new product, some of your competitors may be hard at work along the induction path: how did they do it? Can we do something similar or better? They don’t know how you did it, but they figure out their own version of How.</p><h3>Normal Abduction</h3><p>When we go into the realm of abduction, things get tricky:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*xzgHmhHxznP6y5n3" /></figure><p>Sometimes we have related practices and past experiences and we also have an outcome in mind, but may not know what, or which part of the problem, to attack. Traditional problem solving falls largely in normal abduction: we use the trial-and-error approach to figure out solution, largely based on our past experiences of problem solving (How).</p><p>A city’s police department often has lots of best practices and past experiences on addressing complex social problems like crimes. When the violent crime rate goes up, they have to rely on those experiences (How) to figure out where to start (What) to achieve the outcome of preventing and suppressing violent crimes.</p><p>When a business try to build a new product based their well-established experiences and practices of existing products, they tend to fall into the normal abduction approach. The limitation is obvious: few new concepts can be generated if the ideation is purely based on the past.</p><h3>Design Abduction</h3><p>And design abduction reflects the triumph of human creation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*VscWWUPlhVBRzHOP" /></figure><p>Design abduction is the kind of creative problem solving that we all want. We only know something about the kind of outcome we want, but we lack both the direction and the means to achieve it.</p><p>Design abduction goes far beyond the analytical tradition that’s dominant in previous three forms of reasoning (deduction, induction, and normal abduction). Design abduction not only requires analysis, but also synthesis. It requires a holistic viewpoint from which we find the subtle balance and synergy between What and How, especially because, in this case, there are often much more than one combination of the two that can potentially yield the desired outcome.</p><h3>Innovation of Solution and Innovation of Meaning</h3><p>When I was reading Roberto Verganti’s <a href="https://www.amazon.com/Overcrowded-Designing-Meaningful-Products-Thinking-ebook/dp/B01NAYSQ13/"><em>Overcrowded</em></a>, which elaborates on the difference between <em>innovation of solution</em> and <em>innovation of meaning</em>, it occurrred to me that design abduction is often the underpinnings of the former:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*u3HpyK9Ywk7HuOQq" /></figure><p>According to <a href="https://www.amazon.com/Overcrowded-Designing-Meaningful-Products-Thinking-ebook/dp/B01NAYSQ13/"><em>Overcrowded</em></a>, innovation of solution <em>“concerns better ideas to solve established problems. It’s a new how, a novel way to address the challenges that are considered to be relevant in a marketplace. A novel solution may introduce incremental or even radical improvements, but always in the same direction: they are ‘more of the same’ innovations.”</em></p><p>While innovation of meaning often comes from yet another paradigm:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*7XTmatTU4e1q2iCY" /></figure><p>Accordingly, innovation of meaning <em>“concerns a novel vision that redefines the problems worth addressing. It takes innovation one level higher-not only a new how but especially a new why: it proposes a new reason why people use something. A new value proposition, i.e., a novel interpretation of what is relevant and meaningful in a market. A new direction.”</em></p><p>When other companies were hard at work thinking about how to create a thermostat that help the users better control it, Nest proposed a new meaning around their thermostat: here’s how you can NOT use it and spare all the hassle of having to control it.</p><p>With sleek touchscreen technology and a platform approach, Apple’s iPhone proposed a new meaning: instead of a dedicated phone-calling device (where the customers shall be grateful for any additional features other than making phone calls), here’s a powerful computing device that, by default, can do so many non-trivial things of your life, including making phone calls.</p><p>Innovation of solution and innovation of meaning is not a clear-cut dichotomy. It’s meant to provoke deeper thoughts that lead to better decisions.</p><h3>So What?</h3><p>Those are the thinking tools that you, and everyone in your org, can make good use of.</p><p>The operation, survival, and success of your org is all about priorities. Sometimes you can’t rely solely on analysis, even though the whole spectrum of modern organization and management is based on that traditional analytical approach.</p><p>To innovate, you need far more than analysis and solutions.</p><p>Facing the unprecedented volume, velocity, and variety of challenges and opportunities, you always want to ask:</p><ul><li>What is the best approach?</li><li>How do we do that?</li><li>What do we expect?</li><li>What are the risks?</li></ul><p>While you can also ask:</p><ul><li>What form of reasoning do we need for it?</li><li>Is this likely analysis-heavy or synthesis-intense?</li><li>Are we trying to innovate the solution or the meaning? Or both?</li><li>What kind of help may we need from design thinkers?</li><li>Who, for that matter, are the designers and design thinkers in our org?</li></ul><p>You can’t escape those questions when you want to prioritize and address risks.</p><h3>Nothing New Here</h3><p>All the above are not new ideas. Design researchers and practitioners have been onto those for decades.</p><p>The problem is how many people in your org understand them and how much.</p><p>Sometimes, helping your employees better understand design is far more important than hiring shiny new designers. Design thinkers are often right there, inside your org. And you need to better understand design to spot them.</p><p>{END}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/197/0*wt7bWZeW8fG4W8IE" /></figure><p>UX/Service Designer. Interactive Storytelling pilgrim. Translator. Was Creative Director, Product Manager, Programmer, Layout Designer, Editor &amp; more…</p><p><a href="https://kingofark.com/author/kingofark/">View all posts by kingofark</a></p><p><em>Originally published at </em><a href="https://kingofark.com/2018/08/13/design-reasoning-and-the-innovation-of-meaning/"><em>http://kingofark.com</em></a><em> on August 13, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5538e47db89a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Fine Lines of Our Lives]]></title>
            <link>https://medium.com/@kingofark/the-fine-lines-of-our-lives-78ccbf78c34f?source=rss-495036b10f88------2</link>
            <guid isPermaLink="false">https://medium.com/p/78ccbf78c34f</guid>
            <dc:creator><![CDATA[Noah Fang]]></dc:creator>
            <pubDate>Mon, 13 Nov 2017 05:06:27 GMT</pubDate>
            <atom:updated>2022-08-05T01:42:26.912Z</atom:updated>
            <content:encoded><![CDATA[<h3>There are fine lines in our lives that form the basis of our decisions.</h3><p>At first, there’s the Affordability Line:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*y9mF9VLdsrTHxA0m" /></figure><p>When life is not even affordable, we struggle for mere survival. There’s barely a choice of what to do or how to live.</p><p>When circumstances become better, we cross the Affordability Line and start to become affordable. We have work to do and a life to live, while still worrying about the long term sustainability. We have work but not job. We do work for both survival and passion. Whatever work that is, it’s not yet sustainable for us to cross another fine line.</p><p>Which is the Sustainability Line to cross:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*D57cGLX2Ueo-Keo1" /></figure><p>When what we do becomes sustainable, it becomes a job.</p><p>The difference between work and job is subtle yet profound: there’s work doesn’t mean there’s job; there’s job doesn’t mean there’s work. You could have some work to do while falling short of a job to make ends meet (unsustainable); you could also have a well-paid job while hating the very work you do in it. Working is a way to survive but not necessarily to sustain, while work brings about values that may or may not appear in a job.</p><blockquote><em>…’the job’ is an artificial construct, in which work is managed and parcelled out by corporations and other institutions, to which individuals must apply to participate in doing the work.</em></blockquote><blockquote><em>Tim O’Reilly, </em><a href="https://www.amazon.com/WTF-Whats-Future-Why-Its-ebook/dp/B01N34IDU6/"><em>WTF?: What’s the Future and Why It’s Up to Us</em></a></blockquote><p>So when we cross the Sustainability Line, we have a job to sustain ourselves. And if we’re lucky or brave enough, that job could derive much work that we are willing to do for passion or happiness, in which case the job is well aligned with the work.</p><p>And finally there’s the Happiness Line:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*8HmUI7AQmsXuqc2d" /></figure><p>Happiness is a very subjective notion, while what we can say about crossing the Happiness Line is that, when job, work, and life form a dynamic balance (priorities aligned among them) and/or synthesis (lines blurred among them), it’s likely we’d find the values that go into happiness.</p><p>The three fine lines of affordability, sustainability, and happiness can be many things. They simply represent the values you hold onto and the criteria for life choices. Money, achievement, experience, responsibility, ethics, or some or all of them.</p><p>Maybe even for different things or issues in life, we can be on the way to cross different fine lines.</p><p>However, that’s merely the status quo.</p><p>In the near future, the fine lines might look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*deplUqNqcUjGNSEU" /></figure><p>Machines take over most jobs while humans, enhanced and augmented by technology, devote much more effort to meaningful work. Job is much less important than meaningful work. The notion of job might even become obsolete.</p><p>And in the far future, affordability might not even be a concern:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*69VAGNtiNH3bxz5h" /></figure><p>Survival is not a concern. However, the ability of being is partially and subtly determined by the extent of a person’s augmentation by technology. That ability draws a fine line between sustainable and unsustainable. Meaningful work is the way to happiness, while unimaginable synthesis of human, nature, and technology may eventually lead to a singularity we can’t possibly envision and understand.</p><p>{END}</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/197/0*kkqtpT_4ImX5LV-F" /></figure><p>UX/Service Designer. Interactive Storytelling pilgrim. Translator. Was Creative Director, Product Manager, Programmer, Layout Designer, Editor &amp; more…</p><p><a href="https://kingofark.com/author/kingofark/">View all posts by kingofark</a></p><p><em>Originally published at </em><a href="https://kingofark.com/2017/11/13/the-fine-lines-of-our-lives/"><em>http://kingofark.com</em></a><em> on November 13, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78ccbf78c34f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>