<?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 Meemo on Medium]]></title>
        <description><![CDATA[Stories by Meemo on Medium]]></description>
        <link>https://medium.com/@JoinMeemo?source=rss-b74cb2ead578------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Jj2OA99C73ha7hqn5U9jug.png</url>
            <title>Stories by Meemo on Medium</title>
            <link>https://medium.com/@JoinMeemo?source=rss-b74cb2ead578------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:52:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@JoinMeemo/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[Design Swarms Week Berlin]]></title>
            <link>https://medium.com/@JoinMeemo/design-swarms-week-berlin-daac549f41cb?source=rss-b74cb2ead578------2</link>
            <guid isPermaLink="false">https://medium.com/p/daac549f41cb</guid>
            <category><![CDATA[design-swarms]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Meemo]]></dc:creator>
            <pubDate>Wed, 18 Jul 2018 09:35:37 GMT</pubDate>
            <atom:updated>2018-07-18T09:35:37.792Z</atom:updated>
            <content:encoded><![CDATA[<h4>How we brought a new design thinking method and the inventor Surya Vanka to the Berlin startup community.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6nYw7pYLulfr2IwzEFgdug.jpeg" /></figure><p>In the beginning of July we hosted Design Swarms Week in Berlin. It was a sold-out week full with events, meetups, conversations, a keynote and a full-day Design Swarms workshop.</p><h3><strong>How it all began</strong></h3><p>Let’s start from the beginning. We were in New York when doing some more research about who we should have in <a href="http://www.joinmeemo.com/">Meemo</a> for our upcoming Design Thinking series. We came across a powerful design thinking process called Design Swarms, and contacted the creator of the technique Surya Vanka.</p><p>Surya Vanka is the Founder &amp; Chief Designer at Authentic Design in Seattle. Previously he was the Director User Experience at Microsoft where he led the corporate design excellence team. He’s multi-disciplined designer who has been an industrial designer and interaction designer, and also a Professor of Design at the University of Illinois. During his time at Microsoft he started experimenting with a new design thinking approaches to unleash the power of what he calls ‘swarm creativity’ — and had now built it into a solid process called Design Swarms. Today it is used by companies like Amazon, Autodesk, Microsoft, and T-Mobile to create breakthroughs for big challenges in as little as a day using the creative the power of a group.</p><p>When we saw the results and the process, we knew immediately we wanted to feature Design Swarms in Meemo to empower the world to learn from Surya. Our missions are very aligned as his is to unleash creativity of every human using the power of the design thinking process, and our mission is to unleash the potential of every human by putting the world’s knowledge in their pocket.</p><p>As we discussed our missions, we were convinced that it would be valuable to the vibrant innovation community in Berlin to learn the Design Swarms technique. We named it Design Swarms week and it was a great series of events and sold-out success.</p><h3><strong>Design Swarms Week</strong></h3><p>We kicked off the Design Swarms Week on <strong>Tuesday</strong> 3rd July with a great Meetup &amp; Conversation at Babbel HQ in Berlin. Surya shared his story of Design Swarms and how it all came about, about his company wide hackathon he was part of organizing at Microsoft, his travels across Africa, Asia and Australia learning about how people were taking on big problems in agile ways, and how he came came to be convinced of the the power of swarm creativity.</p><p><strong>Wednesday</strong> was a day packed with single sessions at companies &amp; a big keynote in the evening. In the morning we were invited by Soundcloud and Surya gave a private class about Design Swarms. That afternoon we were invited to Zalando to give a talk on their Campus.</p><p>The evening was a highlight for us in bigger keynote to a cross-section of innovation communities in partnership with the Factory Berlin, followed by conversation over drinks. It was an evening full of inspiration &amp; great anecdotes where Surya shared stories from his career at Microsoft, and the change management approaches he used to help the company shift from a business focused company towards an experience focused company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fZ7H9-VJOXXrIZ7CUsa8tg.jpeg" /><figcaption>Impressions from the Design Swarms Week Berlin</figcaption></figure><h3><strong>The Design Swarms Workshop</strong></h3><p>We ended the week with a full-day workshop on <strong>Friday</strong> together with Deutsche Bank Innovation Labs &amp; Rays of Sunshine, a fantastic charity in the UK that makes dreams of terminally ill children come true and builds a strong community arounds those kids and their families.</p><p>A Design Swarms workshop starts with a team challenge. Our challenge of that day was to apply design thinking to help Rays of Sunshine to make more wishes happen at a bigger scale. There are more and more kids to serve with the same or little resources.</p><p>We formed 4 teams and started with a group exercise. Team name &amp; logo — but more important: we needed everyone’s super power. A good exercise to focus on your strengths and see who else you got in your team. We had a good mix of designers, product managers, engineers and other creatives, such as filmmakers.</p><p>We focused on 3 core posters out of the 15 which are part of the complete Design Swarms Kit. A Design Swarms workshop runs through 5 phases, from getting to know your team (Orient), to understanding the design brief and creating user journeys (Framing), to then go into Ideation and sketch hundreds of ideas in just a few minutes. You decide on one idea and then move further into the Iterate phase until you finish with delivering the storyboard of your product and bringing it to life.</p><p>The ideation phase was extremely powerful and let us create in those 4 groups over 300 ideas in a time frame of just a few minutes.</p><blockquote><strong>Surya presented amazing techniques such as biomimicry, which helps you think bigger, outside the box to come up with wild ideas.</strong></blockquote><p>It was a fun day, full of action and speed, interesting discussions and amazing outcomes — which interestingly enough could all work very well together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hSM00wDRjM0ebUCozrgyVQ.jpeg" /><figcaption>Impression from the Design Swarms Workshop</figcaption></figure><p>If you’re interested in doing a Design Swarms workshop with Surya Vanka — email him at <a href="/service/mailto: suryavanka@authentic.design">suryavanka@authentic.design</a>. If you’re interested in learning more about Design Swarms — download our Mobile Video Learning App <a href="http://itunes.apple.com/app/meemo/id1247973706?ls=1&amp;mt=8">Meemo</a> and stay tuned for the release of the free Design Swarms classes.</p><p>After the success of this week, we are already planning to bring Design Swarms will return to Berlin soon. If you want to be notified of the next set of workshops in Berlin, please email <a href="/service/mailto: suryavanka@authentic.design">suryavanka@authentic.design</a>.</p><p>A big thanks again for everyone who came to <a href="https://www.joinmeemo.com/designswarms">Design Swarms Week</a> and spread the word about it!</p><p>Thanks also to <a href="http://babbel.com/">Babbel</a> for hosting us, for <a href="https://twitter.com/SoundCloud">Soundcloud</a> &amp; <a href="https://twitter.com/Zalando">Zalando</a> for the private classes, to the <a href="https://twitter.com/FactoryBerlin">Factory Berlin</a> for making the keynote happen and of course <a href="https://twitter.com/DeutscheBank">Deutsche Bank Innovation Labs</a> &amp; <a href="https://twitter.com/RaysofSunshine">Rays of Sunshine</a> for running the workshop together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=daac549f41cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding the right problems to solve]]></title>
            <link>https://medium.com/@JoinMeemo/finding-the-right-problems-to-solve-cd0d4f1e4a38?source=rss-b74cb2ead578------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd0d4f1e4a38</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[customer-interview]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Meemo]]></dc:creator>
            <pubDate>Fri, 02 Feb 2018 15:54:14 GMT</pubDate>
            <atom:updated>2018-02-02T15:54:14.046Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>o</strong>r d<strong>etecting that weak signal</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XJ-Z1LbBu8iisv0zRERKXg.png" /></figure><p>As product managers it’s our job to find market problems and create a solution someone will pay for. One of the most neglected part of this process is actually not finding a problem to solve, but <strong>finding the</strong> <strong>right problem to solve</strong>. Using customer interviews we can start discovering the needs of potential users.</p><p><a href="https://www.linkedin.com/in/nilsdavis/">Nils Davis</a>, Senior Product Manager based in Silicon Valley and author of the book “<a href="http://secretpmhandbook.com/">The Secret Product Manager Handbook</a>” has given us exciting insights on what to focus on for a great customer interview.</p><blockquote>If you want to watch the full course on <strong>“How to build products users love”</strong> download <a href="http://www.joinmeemo.com/">Meemo</a> free <a href="https://apple.co/2nrDRNu">here</a>.</blockquote><h3><strong>Keeping the Customer in Problem Space</strong></h3><p>When trying to find problems, we quickly jump into solution space. Especially as technologist. But it is essential to keep yourself in problem space and also to keep the customer in problem space. The customer can also be a representative or a potential future customer.</p><p>Start with open ended questions around a topic. Use the 5W and 1H questions: What, Where, When, Who, Why and How.</p><p>And then keep digging until you found something interesting.</p><p>Instead of jumping from one question to another keep asking “Ok, and then what” or “What’s next”.</p><blockquote>A great book that we can recommend is <a href="https://www.amazon.com/Find-Out-Anything-Anyone-Anytime/dp/1601632983">“Find Out Anything From Anyone, Anytime”</a> by James Pyle.</blockquote><h3><strong>Detecting a Weak Signal</strong></h3><p>What you are looking for in those interviews is something that comes up a few times. This might be indicating a problem people have. It doesn’t mean it’s worth solving it just yet.</p><p>Highlight those parts that seem interesting and write them all up on post it notes. Put them on a wall and look for themes. This is called <a href="http://gamestorming.com/affinity-map/">Affinity Mapping</a>.</p><blockquote>“If you hear something a couple of times — that might be thing.”</blockquote><h3><strong>Finding a Strong Signal</strong></h3><p>When you found something that a lot of people mentioned — go back to those customers and ask different and more questions. Validate if this problem has a big enough interest and that people would pay for it.</p><p>Nils uses a technique called RWW! Is it Real? is it Worth it? And should We do it. Real — do enough people have that problem and are they willing to pay for it. Worth it — do we get a bigger return instead of doing something else? And should we do it — are we capable of solving that problem.</p><p>More on Product Management and “How to build products users love” on Meemo — download <a href="https://apple.co/2nrDRNu">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd0d4f1e4a38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make a billion dollars on the internet ]]></title>
            <link>https://medium.com/hackernoon/how-to-make-a-billion-dollars-on-the-internet-e2384379f2d1?source=rss-b74cb2ead578------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2384379f2d1</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Meemo]]></dc:creator>
            <pubDate>Wed, 31 Jan 2018 19:38:33 GMT</pubDate>
            <atom:updated>2018-10-17T17:16:32.764Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fUSMHaJ7fx5_YhO_coAv8A.png" /></figure><h4>And the case of Snapchat 👻</h4><p>Many people dream of building the next big thing. Making a billion dollar on the internet is the big goal for many entrepreneurs and makers of this world. But is it really that hard or is it just psychology and looking at how the world works?</p><p>We recently sat down with <a href="https://www.linkedin.com/in/nilsdavis/">Nils Davis</a>, a Product Manager from Silicon Valley. Nils has built products for over 10 years and even built a product for product managers. He just published his new book: “The Secret Product Manager Handbook” you can check out <a href="http://secretpmhandbook.com/">here</a>.</p><p>In Product Management we often talk about solving problems. But the word “problem” is a rather general concept. This can also be an “unmet desire” or something customers might have but not aware of it yet. That’s what we are trying to discover in Product Management.</p><h4><strong>What is the secret formula for building the next big thing?</strong></h4><blockquote>“If you want to make a billion dollars on the internet, take something humans have always done and make a better solution for doing that — using software.”</blockquote><blockquote>Famously said by <a href="https://www.fastcompany.com/3019327/ev-williams-formula-for-creating-billion-dollar-companies">Ev Williams</a>.</blockquote><h3>Unmet Desires: Snapchat</h3><p>Snapchat is a great example, a lot of adults don’t get. It serves that unmet desire of teenagers to always want to check in with each other and touch base. Checking if the group is still here and the conversation is still going. Adults communicate a lot more with purpose and don’t have that need to check in with the group anymore — hence Snapchat often doesn’t make much sense for them.</p><h3>Instant Messaging: Whatsapp, Telegram</h3><p>A similar desire is served by instant messaging apps. Humans have had that desire to talk to other people and get a timely response. Also that need of keeping touch, building relationships — with individuals or groups.</p><p>So think of what humans have always done or how they have behaved and how you can make it better by building a software solution to it.</p><p>If you want to learn more about Product, Design &amp; Entrepreneurship and how to build billion dollar products — check out PLAYBOOK, a mobile video micro-learning app which helps you learn more effective and efficient.</p><p>Get the app <a href="https://apple.co/2Ox7Z9M">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*sbtNrRn3OBPcgaESc-8FHQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2384379f2d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-to-make-a-billion-dollars-on-the-internet-e2384379f2d1">How to make a billion dollars on the internet 💰💰💰</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 5 dysfunctions of a team]]></title>
            <link>https://medium.com/@JoinMeemo/the-5-dysfunctions-of-a-team-ec6a49c25777?source=rss-b74cb2ead578------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec6a49c25777</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Meemo]]></dc:creator>
            <pubDate>Fri, 12 Jan 2018 16:06:37 GMT</pubDate>
            <atom:updated>2018-01-12T16:15:41.498Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>explained by David Posey, Agile Coach at PayPal. Watch the course on <a href="https://apple.co/2CHgy8l">Meemo</a>.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2AYkdGBJ5AxihVqjWmarAw.png" /><figcaption>Photo by <a href="https://unsplash.com/photos/ft7vJxwl2RY?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Olga Guryanova</a> on <a href="https://unsplash.com/search/photos/team?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Everybody has been on a team that had issues and wasn’t performing well. Creating high-performing teams is an art itself. In Scrum &amp; Agile it ultimately boils down to doing work not just as an individual, but as a team. The productivity of individuals can vary from 1 to 25x, but the productivity of teams can vary 1 to 2000x.</p><p><strong>So what is the secret of teams that perform at a higher level?</strong></p><blockquote>“1+1=2 that’s straight up Engineering Management. 1+1=3 or 5 or 7 — that’s Leadership and a very different subject.” David Posey</blockquote><p><a href="https://www.linkedin.com/in/dposey/">David Posey </a>has been coaching engineering teams throughout his career. He has worked alongside great leaders like <a href="https://a16z.com/author/ben-horowitz/">Ben Horowitz</a> and works today at PayPal as an Agile Coach &amp; Director Customer Engagement.</p><p>Teams are mostly defined by their dysfunctions rather than their functions. Here are the 5 dysfunctions of a team.</p><h3>1. Absence of trust</h3><p>Trust is where it all begins and there are two kinds of trust. Predictive trust, which describes an expected behaviour and there is vulnerability trust, which is the trust that makes teams great.</p><p>In Scrum teams we look for that vulnerability trust and the ability to have an honest &amp; open conversation. Transparency means being able to be clear and open about results and also failures.</p><p>Building a high-performing team requires the individuals to spend time with each other and develop that trust. Somebody has to lead the way and make the first step by opening up.</p><h3>2. Fear of conflict</h3><p>The essence of improvement is the inspection of our results and the discussion and disagreements that follow. In a group there are always several viewpoints about the data and the right way of doing something. The effectiveness of those conversations and conflicts is based on the level of trust. If people don’t trust each other — they won’t openly discuss to strive for improvement and it ends up in politics. In functional teams, those arguments are very productive and lead to a consensus.</p><h3>3. Lack of commitment</h3><p>After creating trust and discussing what needs to be improved — the team now has to commit to do the work. We see this by observing how people talk about their work. Without getting commitment you will not be able to get to the next stage.</p><h3>4. Avoidance of Accountability</h3><p>Accountability comes in when a team has agreed to commit to a shared goal. Everybody in the team is empowered to hold everybody else accountable. It’s not a matter of the leaders or the manager anymore. Real accountability comes from team members themselves.</p><blockquote>“Sometimes it feels like someone is appointed or in charge of holding people accountable. That’s nagging. Real accountability comes from team members themselves!” David Posey</blockquote><h3>5. Inattention to results</h3><p>The reason that we have to hold people accountable is because if we don’t they think results don’t matter. And results are relatively rare. Most teams don’t achieve results. This is because the previous dysfunctions are given. Sometimes you also find teams that have all 4 functions but don’t achieve results. Those have mostly systemic issues and it is the Scrum Masters and Product Owners role to find them out and fix them.</p><p>David Posey based his <a href="http://www.joinmeemo.com/">Meemo</a> course on the book from <a href="https://www.tablegroup.com/pat/">Patrick Lencioni</a> <a href="https://www.tablegroup.com/books/dysfunctions">“5 Dysfunctions of a team”.</a></p><p>Learn how to analyze your team, how to recognize high-performing teams or what happens when you split high-performing teams in David Posey’s course on <a href="https://apple.co/2CHgy8l">Meemo</a>.</p><blockquote>“If you ever been on a high-performing team — you know! If you’ve never been on a high-performing team — you know!” David Posey</blockquote><p>Download Meemo for free <a href="https://apple.co/2CHgy8l">here</a> and start learning today.</p><p>We’re on a mission to get the world’s wisdom in your pocket. Learn everyday 10 Minutes with <a href="https://apple.co/2CHgy8l">Meemo</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yNxkHTVPbuhkmQGG-AKdgA.png" /><figcaption>Download <a href="https://apple.co/2CHgy8l">Meemo</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec6a49c25777" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make better decisions using Integral Leadership]]></title>
            <link>https://medium.com/@JoinMeemo/make-better-decisions-using-integral-leadership-7f95389fd090?source=rss-b74cb2ead578------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f95389fd090</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile-transformation]]></category>
            <dc:creator><![CDATA[Meemo]]></dc:creator>
            <pubDate>Thu, 11 Jan 2018 16:26:07 GMT</pubDate>
            <atom:updated>2018-01-12T04:10:51.283Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vUVMrYXLpdNGVWkzAKt3Lw.png" /></figure><p>Making good decisions is one of the most important things for any businesses success. As a business leader you have to gather the necessary information and use it on a strategic level. This is where many leaders make mistakes, as they only consider their perspective for making those decisions.</p><p>Integral Leadership is an emergent theory or philosophy and has been around for a while, says <a href="https://www.linkedin.com/in/sineadcondon2/">Sinéad A. Condon</a>, a Transformation Strategist at CA Technologies. Integral Leadership is about looking at situations and systems in a much broader view than we typically look at them.</p><p>Watch the full course on Integral Leadership on-the-go on <a href="https://apple.co/2CHgy8l">Meemo</a>.</p><h3><strong>Self-Awareness means understanding your thoughts</strong></h3><p>Self-awareness is the necessary foundation to understand other people’s perspectives and opinions. It comes from your own internal view of yourself and your own internal sense making and response to certain things. Our own world view is an essential part of any integral thought process.</p><blockquote>“Self-Awareness comes from your own internal view of yourself and your own internal sense making.”</blockquote><p>Sinead likes to describe it using an acronym called JOBBV — Judgement, Opinions, Biases, Beliefs &amp; Values. Those are things we all have and they have a strong impact on our thoughts and decisions. Sometimes we clash because we make assumptions why we believe certain things. Assumptions which are based on our own experiences and the way we brought up.</p><h3><strong>The 4 perspectives of Integral Leadership</strong></h3><p>Integral Thinking has 4 perspectives. Internal and external views.</p><p>The first perspective is the “I” perspective. It is about what is driving you personally of doing something.</p><p>The “We perspective” is taking the view of the collective. In autonomous &amp; self-organising teams the “I” Perspective is not the only one that matters. The “We” perspective is taking into consideration the lens of the collective viewpoint.</p><p>The “IT” perspective. These are all of the tangible and observable things like data, reports, governance or more. Very important aspects in a business but taking only the “It” perspective into account would narrow our decision making.</p><p>And then there is the “It’s” perspective. This is the environment or also the culture we work in. Creating open and funky workspaces would fall under this category.</p><h3><strong>Integral Leadership helps you make better decisions</strong></h3><p>If you lead your organisation with just your own world view — you will hold yourself and the organisation back. Try building some muscle and become self-aware of your own natural perspective but also step into a new perspective that is a little bit of an edge to you.</p><p>Your decisions will be better as you are using more world views and it will make your business better. Ultimately it will help you transform your organisation to Agile.</p><blockquote><em>“Build some muscle around stepping into a perspective that maybe a little bit of an edge for you. Your decisions will be better.”</em></blockquote><p>Find out how you make teams more collaborative by taking all 4 perspectives into account and why Integral Leadership is essential in today’s world in Sinead’s course on Meemo.</p><p><a href="http://www.joinmeemo.com/">Meemo</a> is a Micro-Learning App for Leadership, Agile &amp; Product Management — available free on iOS. Download <a href="https://apple.co/2CHgy8l">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*txJ5TkD5kX-LRPhqnRUrzw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f95389fd090" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building high-performing teams through communication]]></title>
            <link>https://medium.com/hackernoon/building-high-performing-teams-through-communication-3b23b1eafdd2?source=rss-b74cb2ead578------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b23b1eafdd2</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Meemo]]></dc:creator>
            <pubDate>Wed, 10 Jan 2018 16:01:18 GMT</pubDate>
            <atom:updated>2018-01-10T16:01:18.154Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CJIdoJdQlanA7pYAAcHheQ.png" /></figure><p>Communication is what essentially makes a team come together and become high-performing. But it gets missed frequently. Communication is more than just the words we use or our body-language. It is actually about who we are being when we communicate.</p><p>This is why we created an Micro Masterclass on <a href="https://apple.co/2CHgy8l">Meemo</a> with <a href="https://www.linkedin.com/in/scottforgey/">Scott Forgey</a> on Communication. Watch the full Masterclass <a href="https://apple.co/2CHgy8l">here</a>.</p><p><a href="https://www.linkedin.com/in/scottforgey/">Scott Forgey</a> is an Enterprise Agile Coach and was previously an Agile Coach Program Manager at PayPal. Today he coaches Agile Coaches at PayPal, Salesforce, Oracle, Linkedin and many more.</p><h3><strong>Acknowledging results</strong></h3><p>Acknowledging your team members is what makes a team come more together and is best done in the <a href="https://www.scrum.org/resources/what-is-a-sprint-retrospective">retrospective</a>. The retrospective is a fantastic place for a team to come together and build resilience. The magic of being together as a team is to be known for who you are, what you contribute and the results you have.</p><blockquote><strong><em>“The retrospective is the big opportunity to bring forward who you are for each other.”</em></strong></blockquote><p>Start acknowledging the results you produced as a team and the ones you didn’t. It is the Scrum Master’s role to take the time in each retrospective to have everyone acknowledge each other. For the things what they did this sprint, what worked and what didn’t. Great teams are functions of who people are being — not just what they are doing.</p><blockquote>“When you acknowledge someone for who they are for you. That is the glue that holds the team together.”</blockquote><p>Furthermore take the time to acknowledge <strong>what you didn’t do.</strong> This is an opportunity for the team to jump in an help each other. Shared wisdom in the group is more powerful.</p><blockquote>“There is always something to acknowledge people for. You just have to look.”</blockquote><h3><strong>Lead the way</strong></h3><p>You as the manager, Scrum Master or Agile Coach have to take the first step in acknowledging people. You lead the way and set the tone. Have everyone celebrate acknowledgements.</p><blockquote><strong><em>“Being a leader means I go first.”</em></strong></blockquote><h3><strong>Places of communication</strong></h3><p>There are a number of other great places to use the power of communication. The Daily Standup is a great one to ask your team for help and share thoughts. Pair Programming is another great instance for learning and communicating with your team.</p><p>Give yourself the privilege of being in communication with your team members and the scrum master during the course of the sprint. Mention if there is something on your mind, it helps to remove impediments and issues.</p><h3><strong>High Performing Teams</strong></h3><p>The truly high-performing teams operate with communications at all three of those levels. The level of the results, the level of being and the level of doing. High-Performing teams communicate mostly at the level of results. Their focus on results is always switched on and the communication is very short and commanding.</p><p>High-Performing teams know who they are for each other and acknowledge each other. They have all different roles but one aligned mission: getting to that finish line as fast as possible.</p><p>Learn more about how communication empowers teams to achieve greatness in Scott’s Meemo Masterclass. Download Meemo <a href="https://apple.co/2CHgy8l">here</a> and start learning today.</p><p>We’re on a <a href="http://www.joinmeemo.com/">mission</a> to get the world’s wisdom in your pocket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*44KOjPTCnJhqZDCGJDsIFQ.jpeg" /><figcaption>Download <a href="https://apple.co/2CHgy8l">Meemo</a> &amp; start learning</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b23b1eafdd2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/building-high-performing-teams-through-communication-3b23b1eafdd2">Building high-performing teams through communication</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 steps to become a better leader]]></title>
            <link>https://medium.com/@JoinMeemo/5-steps-to-become-a-better-leader-d25e22ac4997?source=rss-b74cb2ead578------2</link>
            <guid isPermaLink="false">https://medium.com/p/d25e22ac4997</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Meemo]]></dc:creator>
            <pubDate>Tue, 09 Jan 2018 15:30:12 GMT</pubDate>
            <atom:updated>2018-01-10T16:03:09.961Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kdjilfzPcBKPiSN_A1uZ7g.png" /></figure><p>Getting teams to high-performance requires great leadership. Many books have been written about the topic, but when reality kicks in we often forget to apply the great things we’ve learned.</p><p><a href="https://www.linkedin.com/in/dposey/">David Posey</a>, Agile Coach at PayPal, has been coaching engineering leaders for the past 20+ years. Over the years of working with successful leaders like <a href="https://twitter.com/bhorowitz">Ben Horowitz</a> at Loudcloud and many others he has constructed his own 5 step method to help engineering managers become great leaders.</p><p>Watch the full course with David Posey on Leadership on <a href="https://apple.co/2CHgy8l">Meemo</a>.</p><h3><strong>1. Assemble a great team</strong></h3><p>Most people think assembling a great team just means hiring great people. It is pretty important and if all you do is hire well you will be in good shape. Another important aspect in assembling a great team is to fire well. Hiring one more good person adds incrementally, but removing a person, that doesn’t belong has a far greater impact.</p><blockquote>“A key aspect in assembling a great team is to fire well”.</blockquote><p><strong>Hiring &amp; Firing</strong></p><p>If you are hiring 10 people, at least one is not a great fit. The problem you often see is that hiring managers don’t feel responsible for the bad hire. If you hired the person, interviewed them, gave them the work and did a lot more things to onboard them and still they failed then it was your judgement that was poor.</p><h3><strong>2. Set a long-term vision</strong></h3><p>Scrum teams set their own goals but your role as a leader is to set the vision and big goals. Communicate that long-term goal constantly to the team and be crystal clear about it. It is so important as it guides every decision you do.</p><h3><strong>3. Give clear feedback</strong></h3><p>Especially when you are building a new team from scratch — giving clear feedback is essential to a team’s success. Recognize every successful interaction of your team no matter how small.</p><p>You might be at some point ending up with a team that doesn’t seem to be able to get anything right. Don’t blame them. Look for the 1 thing they are doing right. Reinforce the small successes and what’s good. This is crucial to the success of a team.</p><blockquote>“Recognize every successful interaction no matter how small”</blockquote><h3><strong>4. Provide the tools &amp; resources</strong></h3><p>Another key aspect of high-performing teams is to give them what they need to succeed. Do they have the right amount of time? Do they get feedback from customers? The list goes on.</p><p>Give your team the right tools &amp; resources to succeed. Don’t know how? Just ask them: What can I add to your equation that would make you more effective?</p><h3><strong>5. Get out of the way</strong></h3><p>The final step in becoming a better manager is what David calls “getting out of the way”. We still see many young engineering managers doing their best attempt to help the team but often it is actually holding them back. The best thing is to get out of the way and trust them to do the job.</p><p>Your job as an engineering leader is to remove all the impediments and deal with the things your team shouldn’t be dealing with.</p><blockquote><em>“Being an engineering leader is terrifying, exciting and thrilling. It is the hardest job and the easiest job you’ll ever do on the same day”</em></blockquote><p>Find out more why and how to apply those steps in David’s Leadership course on Meemo. Download Meemo <a href="https://apple.co/2CHgy8l">here</a> and start learning today.</p><p>We’re on a mission to get the world’s wisdom in your pocket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*87rib3CkQGGzVfEx9c5Utg.jpeg" /><figcaption>Watch the full course with David Posey on Leadership on <a href="https://apple.co/2CHgy8l">Meemo</a>.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d25e22ac4997" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Rise of Agile and its Ecosystem]]></title>
            <link>https://medium.com/@JoinMeemo/the-rise-of-agile-and-its-ecosystem-d567026251a?source=rss-b74cb2ead578------2</link>
            <guid isPermaLink="false">https://medium.com/p/d567026251a</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Meemo]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 19:55:39 GMT</pubDate>
            <atom:updated>2017-10-04T19:55:39.617Z</atom:updated>
            <content:encoded><![CDATA[<p><em>First generation Agilist &amp; our Advisor </em><a href="https://www.linkedin.com/in/gervaisjohnson/"><em>Gervais Johnson</em></a><em> explains the 4 quadrants of the Agile Ecosystem and talks about rise of Agile over the past years.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Muh9i6PGKXuFj9bGa7GcYQ.jpeg" /><figcaption>Sterling Murmuration, Nature &amp; Agile</figcaption></figure><p>When I started my career in software engineering, we embraced the new structured software development life cycle approach; like the one James Martin and my other fellow IBMers created because we knew what it was like without it. Now it’s labeled Waterfall and not a right-fit for today. We were successful and created some great solutions, but also failed monumentally many times as far as budget and meeting expected completion dates. Waterfall fit our technology, business demands, and human-systems at that time.</p><p>Today technology is pervasive; it is changing our society and way of life profoundly. Most companies depend on it to be in business. Many people depend on it to be productive and happy. Business markets, customer demands, and technology changes and their related impacts are outpacing human consumption and adaptation abilities. Technology and social advances create a symbiotic relationship with Agile, allowing us to deliver faster and sustain <a href="https://hbr.org/2016/05/embracing-agile">customer delight</a> in the digital and interconnected world.</p><p>Agile today consists of: an open mindset, an empowering and safe organization culture, a pragmatic set of practices and tools, and a visionary relationship between internal and external environments. Collectively, these form an open and coherent ecosystem. Waterfall is not relevant for today and is replaced by Agile, mainly due to the constant need to sense, respond, and adapt. Agile is pervasive and changing our organizations and individual interactions as well as our social fabric.</p><blockquote><em>Agile today consists of an open mindset, an empowering and safe organization culture, a pragmatic set of practices and tools, and a visionary relationship between internal and external environments.</em></blockquote><p>I am a first generation Agilist; witnessing, and to some degree, influencing, today’s mass acceptance and adoption of Agile. Over the last 16 years, especially the last five years, Agile has matured via obvious successful outcomes in pure business efforts without a technology enablement component, as well as being applied in the typical software development efforts. We see a continuum of Agile implementations; from startup companies using Lean Agile to large companies using a <a href="http://www.scaledagileframework.com/">Scaled Agile Framework</a>. Many large enterprises are building close relationships with new startup disruptors resulting in the Agile for Innovation movement.</p><p><strong>Agile is an ecosystem and involves four quadrants: the Agile Humanity, the Agile Practices and Tools, the Agile Organization and Culture, and the Agile Environment.</strong> These quadrants need recurring alignment and constant synchronization. The Agile Ecosystem is a human-system that needs <a href="https://www.forbes.com/sites/jasonbloomberg/2016/06/26/bimodal-backlash-brewing/#22deea0a5f82">ethnographic</a> focus to succeed and evolve.</p><h3>The Agile Ecosystem</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FRAMI6R7MvNAzUuD.png" /></figure><h4>Agile Practices and Tools</h4><p>This is where most implementations of Agile focus primarily within the IS/IT departments at the enterprise, and more <a href="https://www.scrumalliance.org/community/articles/2014/june/lean-agile-process">Lean Agile</a> and Design Thinking practices for startups. The focus is on individual and team proficiency so the team and organization becomes high-performing. There is additional focus on the exterior organization to bring in latest practices and tools to be tailored. It is more fluid than the others because many new ideas and vendor solutions are arriving on the market and are concentrated here. The increase of market solutions in the quadrant generally indicates that it is easier to tackle, and this is where Agile started in the software engineering arena.</p><h4>Agile Humanity</h4><p>This is the most commonly neglected with most Agile Adoptions, Transitions, or Transformations. We think humanity is a good name for this quadrant as it expresses an all-inclusive participation of individuals in a human-system. This is where the “Being Agile” starts for each of us, as we reflect on our internal readiness to change. Today we are not seeing increased speed of focus in this area except for leadership training and coaching offerings. Emerging focus on <a href="https://www.forbes.com/sites/jasonbloomberg/2016/06/26/bimodal-backlash-brewing/#22deea0a5f82">ethnography</a>, <a href="https://www.happymelly.com/the-happiness-door-bring-your-own-bottle/">happiness</a>, <a href="https://www.forbes.com/sites/jasonbloomberg/2016/06/26/bimodal-backlash-brewing/#22deea0a5f82">sense-making</a> and stories, crews, competency tribes or communities, high-performing team practices, along with internal self-evaluation and awareness practices and tools, are shaping this area.</p><h4>Agile Organization and Culture</h4><p>This is commonly missing with most Agile Adoptions, Transitions, or Transformations. This quadrant looks at interior organization structure and the organization collective. We are seeing increasing focus in this area especially with newer and high-tech companies. With increasing frequency, we are seeing relevant Social Sciences findings interwoven within Change and Organization Design. In addition, we are seeing some companies use this information to experiment and adopt more purposeful business models. For example, replacing yearly performance reviews with more frequent or continuous feedback or changing our skill concentration to more customers’ needs focus.</p><h4>Agile Environment</h4><p>This is where we have seen focus but rarely outside the IT/IS external software or staffing vendor relationships as we build software solutions. There is some significant movement is this area. For example, the financial services sector is using Agile more as they work with appropriate parties to simplify regulations. The U.S. Department of Defense has mandated that software vendors submitting proposals demonstrate Agile competency, while simultaneously simplifying the contracting and execution processes. Many disrupted companies like Financial Services are determining how to partner or integrate with FinTech companies. Some companies are integrating hardware and software Agile environments aligning practices, tools, and mindset.</p><p>Since 2001, Agile has been successfully implemented thousands of times with real, positive business results and human-system positive outcomes. It’s had some failures, too, but the root cause is not Agile but misalignment with one of the Agile Ecosystem quadrants. Of course, for many of us, when we fail we have a difficult time looking within to learn and adjust. Instead, we tend to point at the external idea as the reason; after all, we are flawed humans. It is easier to look outward, but doing so puts our business, government organization, or non-profit existence in peril.</p><p>Agile is more mature and in hyper-demand. For new ideas there is a common maturity progression. Most think Agile is in the <a href="http://cognitive-edge.com/">“late majority”</a> or “t<a href="http://www.gartner.com/technology/research/methodologies/hype-cycle.jsp">rough of disillusionment”</a> phases, where there is: a plethora of practices and tools, self-identified experts, expert infighting, cottage certification and validation industries, and increased usage complexity. We are left with an ever-complex task to determine the right fit for our needs.</p><p>____</p><p>We at <a href="http://joinmeemo.com/">Meemo</a> help teams develop an Agile Mindset through Micro Masterclasses with leading Agile Coaches &amp; industry experts from around the world.</p><p><em>Download Meemo for free </em><a href="https://itunes.apple.com/us/app/meemo/id1247973706?ls=1&amp;mt=8"><em>here</em></a><em> and connect with Gervais on </em><a href="https://www.linkedin.com/in/gervaisjohnson/"><em>Linkedin</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d567026251a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital transformation means becoming an agile organization]]></title>
            <link>https://medium.com/@JoinMeemo/digital-transformation-means-becoming-an-agile-organization-4efeb71fdab5?source=rss-b74cb2ead578------2</link>
            <guid isPermaLink="false">https://medium.com/p/4efeb71fdab5</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Meemo]]></dc:creator>
            <pubDate>Thu, 28 Sep 2017 13:43:20 GMT</pubDate>
            <atom:updated>2017-09-28T13:43:20.308Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9CFcPxN-IQSGx8CWFg7v8Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/search/photos/shibuya-crossing?photo=xQpkcU2MK9I">Andre Benz</a></figcaption></figure><h4><strong>Why it is more important to change your culture and empower your teams then introducing new technologies.</strong></h4><p>This post first appeared on <a href="http://www.joinmeemo.com/">joinmeemo.com</a></p><p>The Digital Transformation era has arrived and companies are implementing new technologies as fast as they can. They feel the pressure, are afraid of missing out and heavily increase their budgets to keep up with the change.</p><p>A big issue is, however, that becoming a digital leader doesn’t mean to become technology savvy and implementing as many new digital products you can. It is much more about creating an agile organization to be able to respond quickly to change and implement solutions faster.</p><blockquote>Becoming a digital leader doesn’t mean becoming technology savvy — it is about creating and agile organization.</blockquote><p>This is much more a cultural &amp; <a href="https://www.forbes.com/sites/forbescoachescouncil/2017/04/21/why-entrepreneurs-need-an-agile-mindset/#7bf260d24ecf">mindset</a> shift that needs to happen, because if your employees are not <a href="https://www.forbes.com/sites/stevedenning/2015/07/22/how-to-make-the-whole-organization-agile/#76d2783c5841">embracing the change</a>, any new digital strategy will fail. We often see companies doing digital efforts rather ad-hoc and too rushed. They don’t set the scene properly and often think it is done with one managerial decisions at C-Level. We even see many executives talking about Agile not knowing what it actually <a href="https://hbr.org/2016/05/embracing-agile">means</a>. C-Level needs to empower your teams at every level.</p><p>Becoming an agile organization and leading in the digital world is about creating teams that take risks, embrace change and are creative. It is about introducing an agile culture in which everyone has the right to make decisions. Create an organization where people work closer together and give them enough room to try things and test ideas.</p><p>Agile Organizations also require new roles and new skills to create this new way of working. Introducing Agile Methods like Scrum require new roles like a product owner or a scrum master for instance. Companies need to create a continuous learning culture to ensure employees are constantly learning the new skills that are needed. The agile mindset puts users first and emphasizes creating value for the customer. Only if this is in place your digital transformation efforts can be rewarded.</p><p>Who should make the decision to go agile? It is the <a href="https://hbr.org/2017/01/to-lead-a-digital-transformation-ceos-must-prioritize">CEO’s role</a> to empower this change for agile &amp; digital transformation. He and his team need to take down boundaries and create self-organizing teams. Companies need to trust employees to create value and be genius. Empowering them to do more and create good work.</p><p>We at <a href="http://www.joinmeemo.com/">Meemo</a> help companies with this cultural &amp; mindset shift. Our <a href="http://itunes.apple.com/us/app/meemo/id1247973706?ls=1&amp;mt=8">Mobile Learning App</a> helps teams develop an agile mindset and create an agile culture. If you want to find out more go to <a href="http://www.joinmeemo.com/">joinmeemo.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4efeb71fdab5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>