<?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 Johannes Dornisch on Medium]]></title>
        <description><![CDATA[Stories by Johannes Dornisch on Medium]]></description>
        <link>https://medium.com/@dorsch500?source=rss-192e181c92a4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-eaaOJme-jef0yUzaqHYaw.jpeg</url>
            <title>Stories by Johannes Dornisch on Medium</title>
            <link>https://medium.com/@dorsch500?source=rss-192e181c92a4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:38:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dorsch500/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[Designers, Stop Over-Specializing: The Future Belongs to Generalists]]></title>
            <link>https://dorsch500.medium.com/designers-stop-over-specializing-the-future-belongs-to-generalists-02a704447f24?source=rss-192e181c92a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/02a704447f24</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Johannes Dornisch]]></dc:creator>
            <pubDate>Wed, 27 Nov 2024 08:24:00 GMT</pubDate>
            <atom:updated>2024-11-27T08:24:00.310Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2yyZdfgfk2VygFvG_Gl13g.png" /></figure><p>The design world is evolving rapidly. As businesses face challenges like economic instability, technological disruption, and climate change, designers who rely on narrow specialization are struggling to keep up.</p><p>Today’s problems require adaptability, breadth, and systems-level thinking. The future belongs to generalists — designers who can connect disciplines, solve complex challenges, and think holistically.</p><p><strong>Why Specialization Falls Short</strong></p><p>Specialization once thrived in predictable environments, where designers focused on usability, interaction, or prototyping within stable workflows. But today, the challenges are messier and interconnected.</p><p>For example:</p><ul><li>Designing hybrid experiences that seamlessly merge physical and digital spaces.</li><li>Aligning product design with operational workflows.</li><li>Connecting design solutions directly to business strategy.</li></ul><p>These aren’t challenges for specialists. Solving them requires designers who see the bigger picture, adapt quickly, and bridge gaps between disciplines.</p><p><strong>Generalists as V-Shaped Thinkers</strong></p><p>Generalists are often misunderstood as being shallow or unfocused. But today’s generalists are V-shaped thinkers (a concept introduced to me by Jeroen Kraaijenbrink): experts with deep knowledge in one or more areas, complemented by broad, adjacent knowledge across disciplines.</p><p>This combination of <strong>depth</strong> and <strong>breadth</strong> makes them uniquely capable of addressing complex problems. For example, a V-shaped designer might:</p><ul><li>Pair UX expertise with behavioral psychology to create experiences that resonate emotionally and functionally.</li><li>Combine knowledge of business processes with design to align products with organizational workflows.</li><li>Use data analysis alongside design strategy to deliver evidence-based solutions.</li></ul><p>Unlike T-shaped thinkers, whose broad knowledge often remains shallow, V-shaped thinkers continuously deepen their adjacent skills. This enables them to bridge disciplines, thrive in multidisciplinary teams, and drive innovation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*NW5Jn9XaAFR01hyIxn7hrA.jpeg" /></figure><p><strong>AI Is Elevating Generalists, Not Replacing Designers</strong></p><p>And the good thing is: Becoming a v-shaped generalist has never been easier, due to the rise of AI. Tools like ChatGPT, Perplexity, Gemini, MidJourney, Notion AI, and Miro’s integration with Uizard ease tasks like research, ideation, wireframing, usability testing, and persona creation. Even Figma’s anticipated AI capabilities hint at even more disruption.</p><p>But AI isn’t replacing designers — it’s amplifying generalists’ strengths. By helping to automate repetitive tasks or get much information with ease, AI allows designers to focus on higher-order challenges, such as:</p><ul><li>Aligning design with strategic business goals.</li><li>Focus way more on identifying the crucial problems. (no more thinking how to create a component, yay!)</li><li>Crafting systems-level solutions that connect multiple disciplines.</li></ul><p>Generalists thrive in this environment. They use AI as a collaborator, not a competitor, leveraging automation to think critically, adapt, and deliver innovative solutions.</p><p><strong>Building the Future: Generalists Lead the Way</strong></p><p>The challenges of today demand designers who can adapt, think holistically, and work across systems. While specialists excel in narrow, well-defined tasks, the greatest impact comes from generalists who bridge disciplines and embrace complexity. Generalists aren’t just the future — they’re the key to solving the design world’s toughest challenges today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=02a704447f24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tools vs. Needs: A Lesson in Inefficiency]]></title>
            <link>https://dorsch500.medium.com/tools-vs-needs-a-lesson-in-inefficiency-63c96804df54?source=rss-192e181c92a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/63c96804df54</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[notetaking]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Johannes Dornisch]]></dc:creator>
            <pubDate>Fri, 04 Oct 2024 10:58:36 GMT</pubDate>
            <atom:updated>2024-10-04T10:58:36.727Z</atom:updated>
            <content:encoded><![CDATA[<p>Designers often dive deep into mastering tools — absorbing every Figma trick, perfecting auto-layouts, and now using AI to automate tasks and boost efficiency. But there’s one critical question we frequently overlook: are we solving the right problem?</p><p>I remember my early coding days, trying to build reusable frameworks to be more efficient. In the end, much of that effort was wasted because I hadn’t clearly defined the problem. I was efficient, but at the wrong thing.</p><p>It’s easy to mistake efficiency for effectiveness. We assume that better tools and flawless techniques lead to better outcomes. But without understanding the real problem, all that craftsmanship can be pointless.</p><p>Efficiency only matters when applied to the right work. Instead of asking, “What’s the best way to build this?” ask “Why?” or “What deeper problem does this solve?” As Abraham Lincoln wisely said, “Give me six hours to chop down a tree and I will spend the first four sharpening the axe.” The key to effective solutions is taking the time to understand the problem thoroughly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Jc7DMjqBqUkMAnVF" /><figcaption>Photo by <a href="https://unsplash.com/@convertkit?utm_source=medium&amp;utm_medium=referral">ConvertKit (Soon to be KIt)</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>An earlier boss once told me to start with note-taking. I thought, “Seriously? Take notes?” But it turns out, he was right — sometimes the simplest habits make the biggest difference. Or maybe I’m just getting older and need notes to remember things!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63c96804df54" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Craftsmanship to Co-Generation: The New Era of Design with AI]]></title>
            <link>https://dorsch500.medium.com/from-craftsmanship-to-co-generation-the-new-era-of-design-with-ai-b469218057ee?source=rss-192e181c92a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b469218057ee</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Johannes Dornisch]]></dc:creator>
            <pubDate>Thu, 01 Aug 2024 10:35:46 GMT</pubDate>
            <atom:updated>2024-08-01T10:36:20.098Z</atom:updated>
            <content:encoded><![CDATA[<p>The world of design has evolved dramatically, transitioning from crafting fundamental artifacts to focusing on user experience. Its impact has been far-reaching, reshaping numerous industries, such as technology, healthcare, education, urban planning, transportation, and financial services, to name a few. A myriad of methodologies, including the Double Diamond, Design Thinking, normed Human Centered Design ISO Processes, the Google Ventures’ Design Sprint, and many others, have guided this evolution, each with unique stages but sharing the same ethos of understanding user needs and problem-solving.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Lm-X_vwltiB6JZiu" /></figure><p><em>Various Design Processes — Screenshot</em></p><p>However, the inherent constraints of these methods, such as human bias, time constraints, and resource limitations, have opened the door to the groundbreaking potential of generative AI. Generative AI can revolutionize each design stage, enhancing user research through vast data analysis, supporting ideation with infinite design variations, creating rapid, high-fidelity prototypes, and refining designs through user interaction simulations.</p><h3>AI’s Broadening Influence on Design and Beyond</h3><p>Generative AI’s influence reaches far beyond traditional design parameters. Its capacity for seamless integration with traditional user interfaces and conversational AIs opens up new realms of intuitive and immersive experiences. Specialized interfaces are becoming essential in areas like world building and generative science, while agent models are automating increasingly complex tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OYTLRUcImDrJmE0V" /></figure><p><em>Photo by Mojahid Mottakin on Unsplash</em></p><p>The integration of generative AI is transforming various sectors. For instance, in addressing the climate crisis, AI-aided designers can create systems for better climate data visualization, leading to more effective solutions. In healthcare, design and AI together facilitate personalized health interventions. Similar impacts are seen in education, urban planning, agriculture, financial services, transportation, social justice, e-commerce, and mental health.</p><h3>Embracing the Co-Generative Future</h3><p>However, the unpredictability of AI outcomes necessitates the careful implementation of robust governance structures. The rapidly changing landscape requires designers to continuously adapt and acquire new skills. And while AI introduces efficiencies, designers will still play a critical role, focusing their attention on the bigger problems facing humanity and leaving tasks such as creating patterns and a vast number of buttons to AI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kY7_4CNSDYxE83q_" /></figure><p><em>Photo by Franz Harvin Aceituna on Unsplash</em></p><p>In conclusion, the integration of generative AI into design methodologies is a transformative leap that redefines the field. I perceive generative AI not as a replacement, but as a co-pilot in the design process, leading to a co-generative approach. This co-evolution enhances our ability to tackle the big problems humanity faces, combining human creativity and AI for efficient and innovative solutions. The future of design is here, and it’s co-generative — a journey as exciting and transformative as the path that led us here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b469218057ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating complexity by design]]></title>
            <link>https://medium.com/intive-design/navigating-complexity-by-design-6b8f3c9afefc?source=rss-192e181c92a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b8f3c9afefc</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Johannes Dornisch]]></dc:creator>
            <pubDate>Tue, 27 Apr 2021 07:21:53 GMT</pubDate>
            <atom:updated>2021-04-27T07:43:16.050Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ozI10Da_rKKGinV-YcjuYA.jpeg" /><figcaption>Adomas Aleno on unsplash</figcaption></figure><p>If you’ve ever had anything to do with creating digital products, whether it’s apps, building a B2B platform, or developing a connected device, you’ll probably agree that the process from »falling in love with the problem« to research, prototyping, iterating, and launching is a complicated and complex one. Wait, why »complicated« AND »complex«? Don’t these words mean one and the same thing? Even my dictionary suggests using them interchangeably as synonyms. Well, in fact, there’s a significant difference between the two terms.</p><h3>Complicated or complex?</h3><p>»Complicated« refers to something with easily observable connections between various elements (people, milestones, deadlines, tasks etc.) and has a clear correlation between cause and effect. For example, if you want to plan recurring project meetings, you need to invite the product team, ask the stakeholders, coordinate everyone’s calendars, set the date, and so on. Depending on the size of the business organization, this task can get very complicated. But it’s not complex. You can complete all the necessary steps using easily available knowledge to find time slots suitable for all, contact the participants who need to be present, and master online meeting software.</p><p>»Complexity«, on the other hand, is something that can’t be handled with knowledge only. Complex tasks are unpredictable, especially in ever-changing environments, and don’t manifest clear or obvious connections between elements. Have you ever had a product launch where everything went exactly as — logically and reasonably — planned? I think I know the answer to that one. Sure, agile principles and project management tools help, but they tend to focus mainly on effective execution. When you throw into the mix new user insights, a dynamic competitive landscape, often vastly different environments in which your product is to be used, or a global pandemic threatening existing revenue streams — that’s not something agile project management can handle with ease. Dealing with complexity calls for different strategies and tactics.</p><blockquote>The best way to approach complexity is to rely on our intuition.</blockquote><p>To quote German Professor Peter Kruse, an expert in the field of organizational psychology, the best way to approach complexity is to rely on our intuition. Intuition is about making the right decisions based on experience, a feeling. It’s mostly about creating mental patterns and is rooted in long-standing and constantly updated practices. It’s about experience combined with knowledge, where new contexts, people, and situations continually interconnect. Sounds good, right? But the question arises, how do we apply these theoretical foundations to the daily practices of product executives? Here, the digital product and service design discipline comes into play.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fi9a0TWCUBBA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Di9a0TWCUBBA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fi9a0TWCUBBA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a1b07b204e4e51fa6901dbc3732bf4dc/href">https://medium.com/media/a1b07b204e4e51fa6901dbc3732bf4dc/href</a></iframe><p><em>Video: </em><a href="https://www.youtube.com/watch?v=i9a0TWCUBBA"><em>How do people react to growing complexity</em></a></p><h3>Intuition — guidance by design</h3><p>Design Thinking and Doing means establishing connections between several domains, investigating user behaviors, observing market trends, and collaborating with product managers, developers, and business owners — embedded in various contexts. These tasks have always been complicated and complex. And, since it’s in every designer’s actual job description, design has developed processes, methods, and tools to navigate through this overwhelming amount of ever-changing information.</p><p>For instance, what do you think is easier to communicate and understand: An incomplete, yet tangible product prototype where people can imagine what will happen, or a document 10 pages long struggling to describe every possible product scenario? Well, the answer seems to be a no-brainer.</p><p>A tangible prototype is one perfect example of how design helps to navigate in complex environments. It allows to integrate information originating from multiple perspectives. It synthesizes user research, technological possibilities, branding perspectives, and more. It helps to move forward when stakeholders voice their definite opinions. It’s also a great starting point for iterations and handoffs. It empowers people to take the right actions based on their intuition by imaging a final product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*R4O13Ur4WVgiuC5X" /></figure><p><em>Prototype: xarvio Scouting App | intive</em></p><h3>Future-oriented? Design-driven!</h3><p>Design isn’t just about thinking and doing. If you incorporate a design-driven mindset (Design Being) in product creation, you’ll navigate complexity even better — on many more levels. With a design-driven attitude, people — and organizations accordingly — can empathize with users and customers better, integrate build-measure-learn practices to iterate permanently, adapt to new insights or circumstances more quickly. Again, design gives people the tools to interconnect, stay current, and rely on their intuition.</p><p>New technologies and the VUCA world (Volatility, Uncertainty, Complexity &amp; Ambiguity) are here to stay. Dealing with unpredictable environments and lots of unknown unknowns, also in the field of <a href="https://intive.com/services/product-service-design">digital product creation</a>, will become even more critical. That’s why integrating and using design practices now will give you the perfect navigation tool to adapt and update intuitions — for whatever future may come.</p><p>This article appeared first here: <a href="https://www.linkedin.com/pulse/navigating-complexity-product-creation-design-johannes-dornisch/">https://www.linkedin.com/pulse/navigating-complexity-product-creation-design-johannes-dornisch/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b8f3c9afefc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/intive-design/navigating-complexity-by-design-6b8f3c9afefc">Navigating complexity by design</a> was originally published in <a href="https://medium.com/intive-design">intive Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuous discovery and delivery for digital products]]></title>
            <link>https://medium.com/intive-design/continuous-discovery-and-delivery-for-digital-products-449158713721?source=rss-192e181c92a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/449158713721</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Johannes Dornisch]]></dc:creator>
            <pubDate>Sat, 19 Jan 2019 14:15:41 GMT</pubDate>
            <atom:updated>2021-05-03T14:24:22.311Z</atom:updated>
            <content:encoded><![CDATA[<p>Creating a great digital product in today’s world largely depends on product teams mastering two processes: discovery and delivery. But while traditional workflow approaches tell us that delivery should always come after design, new wisdom tells us that this no longer rings true. Instead, the discovery and delivery processes both need to be happening constantly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bLfWwrdDEZfJskhC" /><figcaption>Photo by <a href="https://unsplash.com/@arstyy?utm_source=medium&amp;utm_medium=referral">Austin Neill</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Successful musicians have long been aware of this logic. In order to be successful, musicians can’t rely on just writing new music or just touring the world to play concerts. The most accomplished and celebrated musicians are the ones who are constantly doing both. It’s a life of continuous discovery and continuous delivery.</p><p><em>The same goes for product development…</em></p><p>If you want to deliver the best products to your customers, you have to be constantly learning and evolving your thinking about your products and — even more importantly — the people who are using them. Rather than end the design process (better yet: <em>the discovery process</em>) or delivery process at any moment, the best approach is to work on both in parallel tracks at all times. Not only is this a natural way to adopt a truly agile mindset, but most importantly it allows you to develop products that are most beneficial and intuitive for the end user.</p><h3>Why it works</h3><p>Working on discovery and delivery in parallel tracks helps integrate all perspectives of product development — the business, the technology perspective, and the user — and keep each perspective grounded. Better yet, with each iteration in this approach, the process of creating a product gets faster and more efficient, and teams become more effective at responding to change and unexpected challenges at every stage of the process.</p><h3>Don’t deliver with your designers on the bench</h3><p>Whether you segment your team to be working on “discovery” and “delivery” separately, or you prefer to organize it so that everyone spends time and energy on both of these processes is entirely up to you. In either case, communication and visibility between these two functions are of the utmost importance — especially if your team is segmented. Every team member should be present and contributing to scrum meetings, and also taking part in development sprints, which generally last for about two weeks.</p><p>Experienced designers need to be included in the delivery process in order to support developers to fulfill the vision they have laid out. This might include presiding over design Q&amp;As, performing what is referred to as ‘guerilla testing,’ or making design changes on the go as needed. Further, designers are always preparing for the “next” development sprint at least a week or two in advance.</p><h3>John Cutler on Twitter</h3><p>ux / #prodmgnt often describe themselves as being assigned to work *with* a &quot;DEV&quot; team. No. That&#39;s your team. You&#39;re on it. It is not a &quot;DEV&quot; team. It is a product team. Not they. We.</p><h3>Dynamic product creation that never stops</h3><p>In order to be most effective and efficient as well as to constantly anticipate the needs of your users, discovery needs to happen within its own “swim lane,” parallel to that of delivery. This approach gives product teams the best opportunity to tackle technological problems as they emerge throughout the product creation process.</p><p>Discovery tasks include such things as intensive research to discover and fully understand what problems exist — both from a technical standpoint as well as practical ones that users face — and how to address them. Another task might be something like a “design sprint,” in which solutions to problems are developed, or perhaps new prototypes are created to evaluate new ideas or think about a new software architecture that addresses the need of a rapidly growing product.</p><p>By ensuring that discovery tasks like these are continually happening, the delivery segment (whether the same people or not) always has access to new information about the product and the technology, as well as (perhaps most important of all) new insights about the customer.</p><p>No other approach will give you a more constant inflow of insights that support ongoing product development and helps implementing a truly agile and empathic mindset. Just like the musician who is constantly creating new material and sharing it with the world, the approach gives product developers something that ultimately benefits the end user most of all: a more flexible product creation process that never stops.</p><p>This article appeared first on our company blog at <a href="http://www.intive.com/">intive.com</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=449158713721" width="1" height="1" alt=""><hr><p><a href="https://medium.com/intive-design/continuous-discovery-and-delivery-for-digital-products-449158713721">Continuous discovery and delivery for digital products</a> was originally published in <a href="https://medium.com/intive-design">intive Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we improved knowledge sharing at our company]]></title>
            <link>https://medium.com/intive-design/how-we-improved-knowledge-sharing-at-our-company-cd9875eb4778?source=rss-192e181c92a4------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd9875eb4778</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[knowledge-sharing]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[talks]]></category>
            <dc:creator><![CDATA[Johannes Dornisch]]></dc:creator>
            <pubDate>Fri, 05 Oct 2018 13:22:23 GMT</pubDate>
            <atom:updated>2018-10-05T17:30:22.276Z</atom:updated>
            <content:encoded><![CDATA[<p>At intive we do a very good job in consulting clients, adopting insights and shipping tangible solutions. We also improved our internal knowledge sharing through initiatives like the intive Academy, internal newsletters with profound articles or by introducing collaboration and knowledge sharing platforms.</p><p>Despite these initiatives we figured out that there’s no quick and easy way to share, teach or tell stories to people outside of our work area. During lunch you might ask? Of course, but to be honest, not everyone wants to talk about work related stuff during the break.</p><p>So our goal was to create a format which has the spontaneity of a chat with a co-worker explaining things, but reaches a broader audience; it needed to be flexible, but not too long lasting and there shouldn’t be much effort to organize it. After a few creative iteration rounds we came up with a pretty good solution: The <em>Lightning Talk Format</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UDuUKNUXxSte7Lbg" /><figcaption>“person taking selfie in front of mirror during night time” by <a href="https://unsplash.com/@maxwbender?utm_source=medium&amp;utm_medium=referral">Max Bender</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The idea behind the <em>Lightning Talk Format </em>is to create an open space to share knowledge about random topics, to train presenters’ storytelling skills, receive feedback to iterate on ideas and — of course — get together with co-workers informally.</p><p><a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=3&amp;cad=rja&amp;uact=8&amp;ved=2ahUKEwjsioLP1u_dAhUMfBoKHXxACFsQFjACegQICxAK&amp;url=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FLightning_talk&amp;usg=AOvVaw06SjA9fuiqtYTKCWH1xS_v">Lightning talks</a> themselves were first introduced at the <a href="https://en.wikipedia.org/wiki/Lightning_talk#cite_note-3">YAPC conference in 1997</a> and are short presentations without many letters, lots of images and — in the best case — with a funny story. The shortness of the talk guarantees full focus of the audience, it is flexible to arrange and the preparation time is usually shorter than giving a talk at the intive academy.</p><p>We introduced it the lean way in our office in Regensburg. Without involving many people, setting up Skype calls or sending invitations via Outlook. There’s a limit of three presenters each time. Every one of them is allowed to talk for a maximum of 15 minutes and everyone can give a talk or join spontaneously.</p><p>The format is highly frequented even if it takes place at friday afternoon in our company office. That’s proof for us, that sharing interesting short stories in an easy and uncomplicated way improves knowledge sharing on the fly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd9875eb4778" width="1" height="1" alt=""><hr><p><a href="https://medium.com/intive-design/how-we-improved-knowledge-sharing-at-our-company-cd9875eb4778">How we improved knowledge sharing at our company</a> was originally published in <a href="https://medium.com/intive-design">intive Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>