<?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 Marcus Castenfors on Medium]]></title>
        <description><![CDATA[Stories by Marcus Castenfors on Medium]]></description>
        <link>https://medium.com/@mcastenfors?source=rss-318d3323fa09------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2T15Yqah-0V1NHPkZGD0RQ.jpeg</url>
            <title>Stories by Marcus Castenfors on Medium</title>
            <link>https://medium.com/@mcastenfors?source=rss-318d3323fa09------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:40:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mcastenfors/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[Building the wrong product: 9 anti-patterns you should avoid]]></title>
            <link>https://uxdesign.cc/building-the-wrong-product-9-antipatterns-you-should-avoid-7dd92c3ddcb1?source=rss-318d3323fa09------2</link>
            <guid isPermaLink="false">https://medium.com/p/7dd92c3ddcb1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Marcus Castenfors]]></dc:creator>
            <pubDate>Mon, 11 Feb 2019 06:07:13 GMT</pubDate>
            <atom:updated>2019-02-22T04:41:38.837Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NMzhN3iG7iQgWvu3NQfMzw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/-p-KCm6xB9I?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">SpaceX</a> on <a href="https://unsplash.com/search/photos/launch?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>It was the day after launch.</p><p>You were so excited to finally have pushed the button. You had been working hard for months and you were thrilled to show the world the fruit of your labor. And then, trouble started. Customers were unhappy, stakeholders were furious, team morale sank.</p><p>This story is not uncommon. Perhaps you have experienced it yourself? Personally, I have definitely been there. It’s not fun.</p><p>The question is: why do we end up in this type of situation? Why do we keep building the wrong products?</p><p>In this article, I have listed <strong>9 antipatterns to building the right product — </strong>lessons that I have learned from the trenches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eAdqKoWkI9p3NnQdx94yHw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/dJdcb11aboQ?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">John Matychuk</a> on <a href="https://unsplash.com/search/photos/stop?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>1. You relied on gut-feeling</h4><p>The solution that you launched wasn’t based on insights around the customers’ problems or a market opportunity. The Product Manager relied on their own gut-feeling and expertise to make decisions.</p><blockquote>“-Steve Jobs never did any user research” —Someone with an inflated ego</blockquote><p><strong>Try this instead:</strong></p><ul><li>Conduct research to find problems that are worth solving for customers</li></ul><h4>2. There was a lack of <a href="https://en.wikipedia.org/wiki/Psychological_safety">psychological safety</a></h4><p>The team knew that there were issues with the solution, but no one dared to speak up.</p><p><strong>Try this instead:</strong></p><ul><li>Empower the team to be involved in every step of the product development process. Let engineers do research, let designers test the code etc. Break the silos, and foster a collaborative environment</li><li>Create a <a href="https://blog.crisp.se/2018/12/05/jimmyjanlen/bootstrapping-a-working-agreement-for-the-agile-team">Working Agreement</a> that captures expectations around collaboration and communication within the team</li></ul><h4>3. You didn’t validate with customers prior to launch</h4><p><em>“- We don’t have the budget”</em></p><p><em>“- We don’t have the time”</em></p><p>These are common statements why testing prototypes and concepts on customers is not prioritized.</p><blockquote>“Testing with one user early in the project is better than testing with 50 near the end.” — Steve Krug</blockquote><p><strong>Try this instead:</strong></p><ul><li>Create a rhythm for conducting usability testing, for instance once every two weeks. Have the mindset of always testing prototypes on real users — early and often</li><li>Make usability testing a spectator sport. Involve the entire team to watch how users are interacting with the solution. This will foster empathy and ground everyone on the main usability issues</li></ul><h4><strong>4. You had </strong><a href="https://en.wikipedia.org/wiki/Confirmation_bias"><strong>confirmation bias</strong></a></h4><p>You tested the solution on customers, but what you were really doing was looking for anything that would support the opinion that you already had.</p><p><strong>Try this instead:</strong></p><ul><li>Be aware of confirmation bias and seek feedback often. Be willing to change your mind</li><li>Take a step back from your role and put yourself in the shoes of customers and other stakeholders</li></ul><h4>5. You only had one core concept</h4><p>You never tested alternating ideas.</p><p><strong>Try this instead:</strong></p><ul><li>During <a href="https://svpg.com/product-discovery/">Product Discovery</a>, explore multiple directions (maximum 3) for the solution. The goal is to learn and you will acquire far more knowledge if you have multiple competing concepts. This approach is more costly but you will gain more insight around the right solution to customers’ problems</li><li>A/B test to mitigate the risk of being wrong</li></ul><h4>6. You were in a time crunch</h4><p>Management forced you to launch because of an important market window or customer. You had to cut corners.</p><p><strong>Try this instead:</strong></p><ul><li>Push back. If the product is not ready, don’t launch. The situation will be far more uncomfortable if you launch a crappy product compared to letting stakeholders wait a bit longer.</li></ul><h4>7. You focused on output rather than an outcome</h4><p>You fell in love with the features and the solutions, rather than the problem to solve for customers. You were thrilled that the team had delivered a boatload of stories.</p><p><strong>Try this instead:</strong></p><ul><li>Understand your customers’ problems using research and define what metrics can measure that you have solved their problems. Focus on those metrics rather than the output of features</li></ul><h4>8. You listened to a vocal high-profile customer</h4><p>The customer wanted a feature that was really important to him or her.</p><p><strong>Try this instead:</strong></p><ul><li>Customers are experts in explaining problems, not solutions. When you receive specific feature requests, use the <a href="https://en.wikipedia.org/wiki/5_Whys">5 Whys</a> to understand the root cause. If the problem is unclear, pick up the phone and interview the customer to gain more clarity</li></ul><h4>9. Only a few team members were involved in <a href="https://svpg.com/product-discovery/">Product Discovery</a></h4><p>For instance, the Product Owner only worked with a Designer and didn’t involve engineers or other stakeholders outside of the core team.</p><p><strong>Try this instead</strong></p><ul><li>Make Product Discovery a team sport. Everyone in the team should be involved in contributing. Having a collaborative approach will gel the team and use the team’s diverse expertise to create a well-rounded solution</li></ul><p>There you have them. Perhaps, you have one to add? If you do, please write a comment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7dd92c3ddcb1" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/building-the-wrong-product-9-antipatterns-you-should-avoid-7dd92c3ddcb1">Building the wrong product: 9 anti-patterns you should avoid</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transformation is about the things that count, not the things that can be counted.]]></title>
            <link>https://medium.com/@mcastenfors/transformation-is-about-the-things-that-count-not-the-things-that-can-be-counted-defba6ab248f?source=rss-318d3323fa09------2</link>
            <guid isPermaLink="false">https://medium.com/p/defba6ab248f</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Marcus Castenfors]]></dc:creator>
            <pubDate>Wed, 01 Nov 2017 10:14:46 GMT</pubDate>
            <atom:updated>2017-11-10T06:12:37.155Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is article is co-written with </em><a href="https://medium.com/u/c5de5c8edcf1"><em>Richard Earle</em></a><em>, Director of Analytics at </em><a href="http://sapientrazorfish.com/"><em>SapientRazorfish</em></a><em>.</em></p><p>In this day and age, there is a lot of chatter about <em>transformation</em>: how incumbent companies can protect themselves against the ascension of nimble startups. Obviously there is no one-size fits all approach. However, there is a small change you can do as an executive that can cause a seismic shift in how you run your business.</p><p>It’s not a new mission statement.</p><p>It’s not a vision for the next 5 years.</p><p>It’s not a fancy strategy.</p><p>It’s about changing the way you view and measure your business.</p><p>It’s about shifting your focus from Financial Performance Metrics to Customer Benefit Metrics.</p><p>This article will give you examples and steps that you can take to drive this change. Customer Benefit Metrics will cause you to be more competitive and create better experiences for your customers.</p><p><strong>The power of metrics</strong></p><blockquote>“What gets measured gets done“ — Tom Peters</blockquote><p>Metrics transcend everything. Every part of an organization adheres to metrics. Designers, marketers, sales, HR, engineering — everyone has a set of metrics they focus on.</p><p>Since metrics are overarching, they also affect everything you do. This can be detrimental if you have defined a poor set of metrics. Bluntly put: if you’re measuring the wrong things, you get the wrong results. The flip-side: if you measure the right things, you get the right results.</p><p><strong>The problem with metrics<br></strong>Typically in business you focus on measuring Financial Performance Metrics such as:</p><ul><li>Conversion</li><li>Retention</li><li>Average Order Value</li><li>Etc</li></ul><p>These variables indicate the lifeblood of a business. However, they’re flawed. Such KPIs only focus on what’s important to your company, rather than what’s important to your customers. Conversion, for instance, doesn’t give a nuanced picture. It’s a blunt instrument indicating that a customer has purchased a product or a service. Sure, the customer has converted, but is he or she happy, and will they come back?</p><p><strong>Enter Customer Benefit Metrics<br></strong>In Clayton Christensen’s latest book <a href="https://www.amazon.com/Competing-Against-Luck-Innovation-Customer/dp/0062435612">Competing Against Luck</a>, he touches upon the idea of <strong>Customer Benefit Metrics</strong>. They are a stark contrast to traditional metrics, since they focus first and foremost on the benefit the customer will receive. To illustrate the concept, he uses Amazon as an example.</p><p>Amazon is governed by a set of three metrics:</p><ul><li>Vast selection</li><li>Low prices</li><li>Fast delivery</li></ul><p>Everything that Amazon does relate to these measurements. Fundamentally, they all connect to the customer.</p><p><strong>Orders delivered, not orders shipped<br></strong>For instance, Amazon doesn’t measure <em>orders shipped</em>, they measure <em>orders delivered</em>. <em>Orders shipped</em> is perhaps a metric that many eCommerce companies use, since it’s the end of their responsibility. They have shipped the good and now the logistics company takes over. Amazon on the other hand takes responsibility for the <strong>end-to-end experience</strong>, measuring that the product has been delivered in a timely manner. By measuring orders delivered, Amazon will not just optimize their internal systems and processes to ship products, they will remove friction and constraints in how orders are delivered, regardless of what’s in their realm of responsibility. The result: a better customer experience.</p><p><strong>Metrics influence innovation<br></strong>As we mentioned earlier, metrics transcend everything in an organization, even innovation. Amazon’s most notable innovations during the last few years can be connected to their metric “fast delivery”: the Dash button, the Prime Air drones and the recent <a href="https://www.amazon.com/b?ie=UTF8&amp;node=17285120011">Key</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EThzAshzHw_UHab7VBcU9w.png" /><figcaption>Metrics drive innovation</figcaption></figure><h4>How to get started with Customer Benefit Metrics</h4><p><em>“These are great concepts, but I have no political clout to change the way we measure our business”</em>, you might say after reading this article. We challenge you on that. You don’t need to be a CEO to change how you measure value for your customers. Start small and trickle up.</p><p>By following the steps below, you can make the shift from Financial Performance Metrics to Customer Benefit Metrics. By doing so, you will not only create better services and products for your customers, it will drive a cultural change, with empathy for customers as a core tenet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VXA73wVSv3fOZprqPj-uAA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@djmalecki">Dawid Malecki</a></figcaption></figure><p><strong>Step 1: Start by talking to your customers<br></strong>It might sound banal, and blatantly obvious, but sadly this is not often the case for a majority of companies. To define Customer Benefit Metrics, you need to understand your customers. You need to get to know <em>how</em>, <em>why</em> and <em>when</em> they use your products and services. You need to uncover the result they want by investing their time, money and effort.</p><p>The essence is about discovering the <strong>job to be done</strong>. What do your customers want to get done in their daily lives? How do they want to improve? The job to be done is greater than your specific product and service, it’s an ecosystem. As <a href="https://medium.com/@stewart/we-dont-sell-saddles-here-4c59524d650d">Stewart Butterfield</a> from Slack eloquently exemplified, it’s not about selling saddles, it’s about selling horseback riding — that’s the job to be done.</p><p>To find your customers’ jobs to be done, you start by interviewing them centered around understanding <em>how</em>, <em>when</em> and <em>why</em>. If you want to learn more about this frame of research, we have added some useful resources below.</p><p><strong>Read more:</strong></p><ul><li><a href="https://jtbd.info/2-what-is-jobs-to-be-done-jtbd-796b82081cca">What is Jobs to be Done (JTBD)?</a></li><li><a href="https://www.intercom.com/books/jobs-to-be-done">Intercom on Jobs-to-be-Done</a></li><li><a href="https://www.amazon.com/What-Customers-Want-Outcome-Driven-Breakthrough/dp/0071408673">What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services</a></li></ul><p><strong>2. Map your customer jobs to metrics<br></strong>After you’ve isolated insights around your customers’ jobs, it’s now time to map them to how they can be measured.</p><p>To make it a bit more tangible, here’s a hypothetical example of how Netflix defined a Customer Benefit Metric.</p><p><strong>Hypothetical example: Netflix</strong></p><p>Netflix conducted a series of customer interviews to uncover underlying jobs to be done. After synthesizing the research, they came across one job that was most pertinent, <em>“Help me unwind from a long stressful day at work”. </em>They discovered that this is the core job of Netflix for a majority of customers. So the question was: how could they translate this job to a metric?</p><p>They formed a hypothesis: when you come home from a long stressful day at work, you want to relax and not make too many choices. You want to sit down on your comfortable couch and be entertained. What’s important in that situation is that the customer A) doesn’t waste time finding a relevant show, and that B) the show is something that fits with their current mood.</p><p>They broke this down into two metrics:</p><p><strong>Job:</strong> Don’t waste too much time finding a relevant show<br><strong>Metric:</strong> Least amount of interactions necessary</p><p><strong>Job:</strong> Find a show that perfectly fits with the customer’s mood<br><strong>Metric:</strong> High rating after viewing</p><p>Low amount of interactions <strong>+</strong> high rating of a show <strong>=</strong> <strong>Customer Benefit Metric</strong></p><p>The above example indicates that combining a set of metrics can form a more extended view of what your customers really want to achieve. However, it doesn’t necessarily need to be a combination, it could be as straight-forward as shifting from a pure Financial Performance Metric to a Customer Benefit Metric.</p><h3>Summary</h3><p>Metrics are powerful tools to drive transformational change in a business, a change to become more empathetic with your customers. As businesses, we need to move away from only measuring what’s important for the business and instead measure what’s also valuable for our customers. The change is measuring <strong>Customer Benefit Metrics</strong>.</p><p>The essence is about uncovering what your customers want to achieve, how they want to improve, and tying those insights back to how you measure success. What’s good for the customer will also be what’s good for your business.</p><p>Applying Customer Benefits Metrics will make you more competitive, and at the same time make your customers more satisfied, a win-win situation.</p><p>Thanks to <a href="https://jtbd.info/@alanklement">Alan Klement</a> and <a href="https://twitter.com/victorlansman">Victor Länsman</a> for their valuable feedback and inspiration. Also thanks to Kurt Beren-Geiger for writing the headline.</p><p>Photo by <a href="https://unsplash.com/photos/fw7lR3ibfpU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dawid Małecki</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=defba6ab248f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#nntech ep 1: with Stefan Krook, CEO of Kivra on happiness, the Poker rule and innovation]]></title>
            <link>https://medium.com/nntech-podcast/nntech-ep-1-with-stefan-krook-ceo-of-kivra-on-happiness-the-poker-rule-and-innovation-751bdb266011?source=rss-318d3323fa09------2</link>
            <guid isPermaLink="false">https://medium.com/p/751bdb266011</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Marcus Castenfors]]></dc:creator>
            <pubDate>Mon, 26 Sep 2016 14:35:58 GMT</pubDate>
            <atom:updated>2016-09-26T14:35:58.062Z</atom:updated>
            <content:encoded><![CDATA[<p>Our podcast on product development, technology and design is back — but — with a twist. We have a new co-host, Tuva Palm, and a new name Nordnet Tech, with the hashtag #nntech 🚀</p><p>In this premiere episode, I’m interviewing Stefan Krook, a serial entrepreneur, venture capitalist and the CEO of <a href="https://www.kivra.com/">Kivra</a>. We have a conversation about a defining moment in his career, product development at Kivra, their process for innovation, his “Poker rule”, and much more.</p><blockquote>“Innovation is just a combination of existing things” — Stefan Krook</blockquote><p>Enjoy and if you have any feedback, please use the #nntech hashtag on Twitter.</p><p>Until next time,</p><p>Marcus and Tuva</p><h4><strong>References</strong></h4><p>Start With Why book: <a href="https://www.startwithwhy.com/">https://www.startwithwhy.com/</a></p><p>Kivra: <a href="https://www.kivra.com/">https://www.kivra.com/</a></p><p>GodEl: <a href="https://godel.se/">https://godel.se</a></p><p>GodFond: <a href="http://godfond.se/">http://godfond.se/</a></p><h4><strong>Listen to the episode</strong></h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F284721439%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fnordnettech%2Fnntech-ep-1-with-stefan-krook-ceo-of-kivra-on-happiness-the-poker-rule-and-innovation&amp;image=http%3A%2F%2Fa1.sndcdn.com%2Fimages%2Ffb_placeholder.png%3F1474548466&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/8b8080c317e7ca4977acdb63d3a7ffe6/href">https://medium.com/media/8b8080c317e7ca4977acdb63d3a7ffe6/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=751bdb266011" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nntech-podcast/nntech-ep-1-with-stefan-krook-ceo-of-kivra-on-happiness-the-poker-rule-and-innovation-751bdb266011">#nntech ep 1: with Stefan Krook, CEO of Kivra on happiness, the Poker rule and innovation</a> was originally published in <a href="https://medium.com/nntech-podcast">#nntech podcast</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[These meetings will make everyone a design leader]]></title>
            <link>https://medium.com/nordnet-design-studio/leadership-could-be-something-you-fear-5c24dc540693?source=rss-318d3323fa09------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c24dc540693</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Marcus Castenfors]]></dc:creator>
            <pubDate>Fri, 12 Aug 2016 11:53:10 GMT</pubDate>
            <atom:updated>2016-08-12T12:21:56.894Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5grZtXO_mFYJjH_MP7JHlQ.png" /></figure><p>Leadership could be something you fear. You fear that it will cause problems. You fear that you have to do things that you don’t enjoy. You have to micromanage. You have to do a lot of admin work. The boring stuff.</p><p>Leadership doesn’t have to be this way. Leadership can be rewarding, inspiring, and <em>simple</em>. What you need is a set of meetings that will<strong> enable your team to lead themselves</strong>. You can focus on the fun stuff, and do less of the boring stuff.</p><h4>The essence of leadership</h4><p>Before we talk about our meeting structure, let’s begin by defining what leadership is. The essence of what a leader should do can be summed up in two bullets:</p><ul><li>As a leader, you <em>define the course</em> for the team</li><li>You also <em>steer</em> team members in the right direction</li></ul><h4>The tools of leadership: meetings</h4><p>The main tools that we use in the Nordnet Design Studio are meetings. You might think: <em>“That sounds about as exciting as having a dentist appointment and, at the same time, reading the terms and conditions for opening a bank account”, </em>but meetings can be meaningful, fun and engaging. Our meetings help us focus on the <em>course</em>, and to <em>steer</em> ourselves in the right direction.</p><p>The old way of thinking is that leadership should be done by one person. Our meetings are run by all of us in the studio, meaning that we collectively lead ourselves.</p><blockquote>The old way of thinking is that leadership should be done by one person.</blockquote><p>The recurring meetings that we have:</p><ol><li>A weekly Goalfest meeting</li><li>A weekly design critique</li><li>A monthly pet peeves meeting</li><li>A quarterly retrospective</li></ol><h3>Goalfest</h3><p>The term Goalfest was coined by <a href="http://joelcalifa.com/">Joel Califa</a> in his article <a href="http://joelcalifa.com/blog/trust-and-product-design/">“Trust &amp; Product Design”</a>. It’s a fest with goals, simple as that. If there is one meeting to take away from this article it would be this one. It’s the key meeting for us. It helps us reflect and look forward.</p><p>The setup is easy:</p><ul><li>You meet once a week on Fridays. We meet at 11 AM for one hour</li><li>You share what you have accomplished during the week, and the goals you have for the following week</li><li>You talk about lessons learned</li><li>The facilitator writes down all notes on a page that’s accessible for everyone. We use Confluence, sort-of an internal Wiki</li></ul><blockquote>Goalfest is what happens when you combine two of the most exciting things the business world has to offer: meetings and spreadsheets. — Joel Califa</blockquote><h4>Goals</h4><p>In any business you have goals. You have company-wide goals, you have team goals, and individual goals. What we wanted to do is to <strong>set up a clear link</strong> <strong>between what we want to achieve as a company to what we want to achieve as a team, and as individuals</strong>.</p><p>The hierarchy that we are using:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RstCpAgvjPIUf7HZoDKXOA.png" /></figure><p><strong>Brand purpose<br></strong>At the top of our Confluence page, we state our brand purpose, why we exist as a company.</p><blockquote>We exist to redefine the financial world by empowering savers of today and tomorrow</blockquote><p><strong>Company-wide goals<br></strong>At Nordnet we have a company-wide priority list of what to focus on as a business. We list each of our goals in order of priority.</p><p><strong>Team goals for the quarter<br></strong>At the end of each quarter, during the quarterly retrospective, we meet and define the team goals for the forthcoming quarter. We typically have 3 or 4 of these goals. We’ll describe more in detail how this works further down the article.</p><blockquote>Example of a team goal: We have consistently contributed to the design community with many articles and open source materials.</blockquote><p><strong>Individual goals for the quarter<br></strong>Same setup here. Each quarter, we individually define a set of goals that we want to achieve during the next three months. They’re all transparent for everyone to see.</p><p><strong>Individual goals for the week<br></strong>This part we update each week. We write a few bullet points of what we want to accomplish next week, for instance: <em>“I want to document graphs in the </em><a href="https://github.com/nordnet/nordnet-ui-kit"><em>UI kit</em></a><em>”. </em>We also look back on the week and rate our individual goals (that we wrote during the last Goalfest) from a scale of 1–5.</p><p>As we share our goals, we have discussions within the team. Maybe someone is struggling with a task and someone else can help. Maybe a team member has learnings to share about a new tool. By discussing our goals, we not only keep ourselves aligned, but we also share knowledge, and help each other.</p><blockquote>By discussing our goals, we not only keep ourselves aligned, but we also share knowledge, and help each other.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lTSZrGj_Mc0JWPiKEuM4xw.png" /><figcaption>The structure of our Goalfest page</figcaption></figure><p><strong>Lessons learned<br></strong>After rating our goals for the week, we also populate a list of lessons learned. We list what we’ve learned and what we can improve. It’s sort of a mini <a href="http://plans-for-retrospectives.com/">Retrospective</a>. It pushes us to reflect on our work.</p><p><strong>Happiness metric<br></strong>As a finale of the meeting, we track our <a href="https://www.scruminc.com/happiness-metric-wave-of-future-2/">happiness metric</a>. It’s a rating system of how happy we are at work, but it’s also a way to increase the happiness of the team.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FblIlUNY0lOR7W%2Ftwitter%2Fiframe&amp;src_secure=1&amp;url=http%3A%2F%2Fgiphy.com%2Fgifs%2FblIlUNY0lOR7W&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FblIlUNY0lOR7W%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="272" frameborder="0" scrolling="no"><a href="https://medium.com/media/4c085be9f5bf7eb3e26ad175e9d2c2ee/href">https://medium.com/media/4c085be9f5bf7eb3e26ad175e9d2c2ee/href</a></iframe><p>We measure happiness by asking three simple questions:</p><ul><li>How happy are you with your current role? (1–6)</li><li>How happy are you with Nordnet? (1–6)</li><li>How can we improve your happiness?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*8Wu0jGMcTLvnwQNpY7Wdag.png" /><figcaption>A screenshot of how we track the happiness metric. The blue shows the team’s score</figcaption></figure><p>The first two questions, you receive a rating, but the third question generates ideas on how we can become happier. Based off of these ideas, we’ve organized team outings, bought equipment, and much more. We track all ideas in a <a href="https://en.wikipedia.org/wiki/Kanban">Kanban</a> board using the columns: todo, doing, done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T9GMjOAijbMt3M0rTc_hLw.png" /><figcaption>A screenshot of the Kanban board</figcaption></figure><p>Tracking the happiness metric is good for business. Scrum Inc, the company who coined the term increased <a href="https://www.scruminc.com/happiness-metric-wave-of-future-2/">their velocity by 500%</a> by tracking their metric.</p><h3>Design critique</h3><p>The design critique is our other weekly meeting. We have these sessions on Wednesdays. The purpose of the meeting is to show your work-in-progress designs and receive feedback.</p><p>How it works: every designer presents their designs in 5 to 10 minutes. The slot is time-boxed for a reason. If we don’t have a set time, the discussions might snowball. Before presenting a design, you must first share the background of the project, and articulate the problem you’re solving.</p><p>After showing the design, the team gives constructive feedback around:</p><ul><li><strong>Simple</strong>: How simple the design is</li><li><strong>Consistent</strong>: How consistent the user experience is, and how aligned it is to our <a href="https://www.nordnet.se/brand/visual-identity/">visual identity</a></li><li><strong>Accessible</strong>: How the design is adhering to our accessibility guidelines</li></ul><p>Facebook has written at length about <a href="https://medium.com/facebook-design/critique-is-an-important-part-of-any-design-process-whether-you-work-as-part-of-a-team-or-solo-ef3dcb299ce3#.yw0my16i0">their setup for design critiques</a>. We’ve “stolen” quite a few bits from them. For instance, they have an excellent way of framing their feedback. We use the following guidelines to give more useful comments:</p><ul><li><strong>Ask questions, don’t judge:</strong> For instance <em>“Why did you choose the color blue for the button?”</em></li><li><strong>Be objective, not subjective: </strong><em>“When I’ve reviewed customer research, I get a sense that they want the overview first, not the details.”</em></li><li><strong>Be concrete, not vague:</strong> <em>“In this case, I would suggest you move the button.”</em></li></ul><p>In addition to the design critique, our lead designer <a href="http://www.curioususer.com/">Can</a>, organizes weekly one-on-one sessions with designers to support with more detailed feedback.</p><h3>Pet peeves</h3><p>We’re firm believers that limitations spark creativity. Instead of starting with a blank slate, we have tools and guidelines to increase the consistency and quality of our designs.</p><blockquote>“Instead of freaking out about these constraints, embrace them. Let them guide you. Constraints drive innovation and force focus. Instead of trying to remove them, use them to your advantage.” — <a href="https://www.goodreads.com/work/quotes/72546">37 Signals</a></blockquote><p>The constraints that we work with are:</p><ul><li>Our <a href="https://www.nordnet.se/brand/visual-identity/">visual identity</a></li><li>A <a href="https://medium.com/nordnet-design-studio/a-closer-look-at-our-atomic-workflow-in-action-by-the-nordnet-design-studio-6e48d6f46c3c#.r9om6y76l">UI kit</a> and a workflow for Atomic Design</li></ul><p>Even though we appreciate working with a design system, we don’t always agree with all of our previous decisions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FRBeddeaQ5Xo0E%2Ftwitter%2Fiframe&amp;src_secure=1&amp;url=http%3A%2F%2Fgiphy.com%2Fgifs%2Fagentm-agent-m-RBeddeaQ5Xo0E&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FRBeddeaQ5Xo0E%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="290" frameborder="0" scrolling="no"><a href="https://medium.com/media/7eae109c5bb4e091bcfea305a755062d/href">https://medium.com/media/7eae109c5bb4e091bcfea305a755062d/href</a></iframe><p>That’s why we have a monthly “pet peeves” meeting, where we can talk about issues and frustrations with our system — ultimately to elevate our design language.</p><h4>A democratic process</h4><p>Pet peeves meetings are held with both the product design and the marketing design teams. It’s a forum where any issue, no matter how large or small can be raised, discussed and documented.</p><p>We begin by going through proposed solutions to previous problems raised in earlier meetings: our “peeves”. We keep track of them using a Kanban board. <strong>The peeves can be as simple as someone disliking a particular icon, or as complex as someone questioning an entire flow within the product</strong>.</p><p>After that, we present new peeves and discuss them with the group. It is a democratic process. Although we may not always reach unanimous decisions, everyone has their say and all points of view are documented.</p><p>If an issue requires a larger amount of exploration than a meeting allows, a designer is tasked with taking the lead on creating a solution. It can sometimes be hard to pick a designer to explore an issue, particularly if opinions are very divided. If that’s the case, we’ll often assign the task to a designer from each “camp” to ensure that we’ve thoroughly examined both sides of the coin.</p><p><strong>Once we’re aligned on a solution within the team, we integrate the end result with our visual identity and our UI Kit.</strong></p><h3>Quarterly retrospective</h3><p>At the end of each quarter, we meet to reflect. We set aside at least two hours. The purpose is to look back on the quarter and learn, as well as, to look forward and to review the goals for the forthcoming quarter.</p><h4><strong>Rate team goals</strong></h4><p>You begin the session with rating the teams’ goals for the quarter. You read each goal aloud and then you ask each member to rate how they feel we’ve accomplished the goal from 1–5. By doing this, we receive a rating for how we have achieved each goal.</p><h4>Retrospective</h4><p>After we’ve reviewed our goals, we do a retrospective of the quarter. We use a structure from the excellent <a href="http://plans-for-retrospectives.com/?id=46-19-20-103-92">Retromat</a> created by <a href="https://twitter.com/findingmarbles">Corinna Baldauf</a>. You can use the Retromat to customize your own retrospective.</p><p>The process we follow:</p><ol><li>Why we do retrospectives</li><li>The good, the bad, the ugly</li><li>Start, stop, continue</li><li>My team is awesome</li></ol><p><strong>Why we do retrospectives<br></strong>We set the stage by asking the question: “Why do we do retrospectives?”. It might sound awkward, but it’s a great question to ask in order to align on expectations.</p><p><strong>The good, the bad, the ugly<br></strong>The next part, we write down on post-its what we felt was “good”, “bad” and “ugly” about the last quarter. After we’ve finished writing, everyone presents their learnings and puts them up on a whiteboard. By doing this exercise, you gather insights, which warms up the brain and tees up for the next step.</p><p><strong>Start, stop, continue<br></strong>Now it’s time to generate ideas on what we should “start”, and what to “stop” and “continue” doing as a team. The same setup as the previous exercise applies, we write down our thoughts on post-its and put them on a whiteboard to discuss. However, as a last step we ask everyone to <a href="https://en.wikipedia.org/wiki/Dotmocracy">dot vote</a> on what they feel are the most important ideas. During the next quarter, we follow up on the suggestions with the most votes.</p><p>Now, we’re almost done. Just one more step is left.</p><p><strong>My team is awesome<br></strong>Retrospectives can sometimes be quite draining. You bring up issues, which can cause frustrations. To end the session on a more positive note, we conclude with a filling-in-the-blanks exercise.</p><blockquote>“My team is awesome because _______________ <br>and that makes me feel __________________”</blockquote><h3>Summary</h3><p>There you have it: our meetings that we use in the studio. Give them a try. We’re certain that you’ll see benefits within your team, such as less micromanagement, more alignment, and more collaboration. Running these meetings will bring out the leader in everyone.</p><p>Thank you for reading,</p><p>The Nordnet Design Studio</p><p>A special thanks to <a href="https://medium.com/u/235d0bf1e974">Ross Malpass</a>, <a href="https://medium.com/u/86dafa99759a">Can Kilicbay</a> and <a href="https://medium.com/u/1c36728f63c3">Gustaf Zetterlund</a> for contributing to the article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c24dc540693" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nordnet-design-studio/leadership-could-be-something-you-fear-5c24dc540693">These meetings will make everyone a design leader</a> was originally published in <a href="https://medium.com/nordnet-design-studio">Nordnet Design Studio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#slowtofast Ep 12 with Alok Alström, the GM of Uber Sweden, on how to scale and adapt a business]]></title>
            <link>https://medium.com/slowtofast-podcast/slowtofast-ep-12-with-alok-alstr%C3%B6m-the-gm-of-uber-sweden-on-how-to-scale-and-adapt-a-business-e1650491d340?source=rss-318d3323fa09------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1650491d340</guid>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Marcus Castenfors]]></dc:creator>
            <pubDate>Mon, 23 May 2016 14:22:11 GMT</pubDate>
            <atom:updated>2016-05-23T14:22:11.609Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5TishRbz7atmICBi-ssf9Q.png" /></figure><blockquote>“Don’t start with what someone else has already done” — Alok Alström</blockquote><p>In this episode, we interview <a href="https://twitter.com/alokalstrom">Alok Alström</a> the General Manager of Uber in Sweden. We get an inside look at how Uber operates, a company that has scaled from nothing 7 years ago to being valued at more than $60 billion dollars.</p><p>The conversation is centered around how Uber is set up for growth and scale. It’s jam-packed with useful insights for any type of business.</p><p>We discuss topics such as:</p><ul><li>Alok’s approach to management and hiring</li><li>Uber’s employee onboarding process</li><li>How Uber uses internal apps in product development</li><li>Successful traits of an adaptive organization</li><li>Uber’s core values, and lots more</li></ul><h4>Listen to the episode</h4><p>Listen on Soundcloud, iTunes, Acast, or any other podcast platform of your choice.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F265499145%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fslowtofast%2Fslowtofast-ep-12-with-alok-alstrom-the-gm-of-uber-sweden-on-how-to-scale-and-adapt-a-business&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000164082611-akuzoc-t500x500.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="500" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/4d2a1c01faa247b7959573b92083c6b0/href">https://medium.com/media/4d2a1c01faa247b7959573b92083c6b0/href</a></iframe><h4>You decide, who should we interview next?</h4><p>Let us know who we should interview next, or which topics to discuss. Write a comment below or use the hashtag <a href="https://twitter.com/hashtag/slowtofast">#slowtofast </a>on Twitter…or send us a fax +46 8 506 33 065.</p><p>Thanks for listening,</p><p><a href="https://twitter.com/dhettema">Dennis</a> &amp; <a href="https://twitter.com/tuvapalm">Marcus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1650491d340" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slowtofast-podcast/slowtofast-ep-12-with-alok-alstr%C3%B6m-the-gm-of-uber-sweden-on-how-to-scale-and-adapt-a-business-e1650491d340">#slowtofast Ep 12 with Alok Alström, the GM of Uber Sweden, on how to scale and adapt a business</a> was originally published in <a href="https://medium.com/slowtofast-podcast">#slowtofast podcast</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#slowtofast Ep 11 (p 2) with Golden Krishna, on our obsession with screens, and the antidote]]></title>
            <link>https://medium.com/slowtofast-podcast/slowtofast-ep-11-p-2-with-golden-krishna-on-our-obsession-with-screens-and-the-antidote-c2420088b35?source=rss-318d3323fa09------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2420088b35</guid>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Marcus Castenfors]]></dc:creator>
            <pubDate>Mon, 09 May 2016 16:37:13 GMT</pubDate>
            <atom:updated>2016-05-09T17:15:44.321Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HyuWzdxQG77zNabgA555nA.png" /></figure><p>This is the second part of our <a href="http://frombusinesstobuttons.com/">From Business To Buttons</a> special. We interview <a href="http://www.goldenkrishna.com/">Golden Krishna</a>, Design Strategist at Google and the author of the book <a href="http://www.nointerface.com/">“The Best Interface is No Interface”</a>. At Google, he works in the Android UX team on shaping the future of the operating system.</p><blockquote>“Our love for the digital interface is out of control…and our obsession with it is ruining the future of innovation” — Golden Krishna</blockquote><p>Golden is passionate about curing our addiction to screens. In his opinion, screens are the pollution of our generation. He urges us to stop focusing so much on designing for user interfaces.</p><p>During this interview, we discuss topics such as:</p><ul><li>Our addiction to apps and “app fatigue”</li><li>The idea of a “screenless” society, just like the notion of the paperless society</li><li>Google Now</li><li>The removal of so-called “digital chores”</li><li>The purpose and issues with chat bots</li><li>The over-saturation of notifications</li><li>A “watch first” design approach</li></ul><h4>Have a listen</h4><p>Listen on Soundcloud, iTunes, Acast, Spotify or any other podcast platform of your choice.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F263235472%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fslowtofast%2Fslowtofast-ep-11-p-2-with-golden-krishna-on-our-obsession-with-screens-and-the-antidote&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000162011341-rps07a-t500x500.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="500" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/b357b32c08d5a82af1304365a954291c/href">https://medium.com/media/b357b32c08d5a82af1304365a954291c/href</a></iframe><h4>Watch Golden’s talk from the #fbtb16 conference</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F9Da7IhgaP2Y%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9Da7IhgaP2Y&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F9Da7IhgaP2Y%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/aa4904b4d780e0caf09f979b0102a3cd/href">https://medium.com/media/aa4904b4d780e0caf09f979b0102a3cd/href</a></iframe><h4><strong>References</strong></h4><p><a href="https://jenson.org/">Scott Jenson</a></p><p><a href="http://www.nointerface.com/book/">The Best Interface is No Interface</a> by Golden Krishna</p><p><a href="http://www.amazon.com/Second-Machine-Age-Prosperity-Technologies/dp/1480577472">The Second Machine Age</a> by Erik Brynjolfsson and Andrew McAfee [Book]</p><p><a href="https://lockitron.com/">Lockitron</a></p><h4>What should we talk about next?</h4><p>Let us know what to talk about next, by writing a comment below or using the hashtag <a href="https://twitter.com/hashtag/slowtofast">#slowtofast </a>on Twitter…or send us a fax +46 8 506 33 065.</p><p>Thanks for listening,</p><p><a href="https://twitter.com/dhettema">Dennis</a> &amp; <a href="https://twitter.com/tuvapalm">Marcus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2420088b35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slowtofast-podcast/slowtofast-ep-11-p-2-with-golden-krishna-on-our-obsession-with-screens-and-the-antidote-c2420088b35">#slowtofast Ep 11 (p 2) with Golden Krishna, on our obsession with screens, and the antidote</a> was originally published in <a href="https://medium.com/slowtofast-podcast">#slowtofast podcast</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#slowtofast Ep 11 (p 1) with Susan Weinschenk, on the brain, dopamine, and the power of…]]></title>
            <link>https://medium.com/@mcastenfors/slowtofast-ep-11-with-susan-weinschenk-on-the-brain-dopamine-and-the-power-of-anticipation-c8bca0704e4e?source=rss-318d3323fa09------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8bca0704e4e</guid>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Marcus Castenfors]]></dc:creator>
            <pubDate>Mon, 02 May 2016 09:00:21 GMT</pubDate>
            <atom:updated>2016-05-02T09:03:45.144Z</atom:updated>
            <content:encoded><![CDATA[<h3>#slowtofast Ep 11 (p 1) with Susan Weinschenk, on the brain, dopamine, and the power of anticipation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6C75aa_pH4k1AsL88zBL1w.png" /><figcaption>Image credit: <a href="https://en.wikipedia.org/wiki/Cerebrum#/media/File:Lobes_of_the_brain_NL.svg">Wikipedia</a></figcaption></figure><blockquote>“The biggest release of dopamine is when you anticipate something that you want” — Susan Weinschenk</blockquote><p>This is the first part of our <a href="http://frombusinesstobuttons.com/">From Business To Buttons</a> special. We interview <a href="https://www.theteamw.com/">Susan Weinschenk</a> a psychologist focusing on the intersection of brain science, behavioral psychology and design. She’s written numerous books on the subject such as <a href="http://www.amazon.com/Things-Designer-People-Voices-Matter/dp/0321767535"><em>100 Things Every Designer Needs to Know About People</em></a><em>, </em><a href="http://www.amazon.com/Neuro-Web-Design-Makes-Click/dp/0321603605"><em>Neuro Web Design: What Makes Them Click</em></a><em> and </em><a href="http://www.amazon.com/How-Get-People-Stuff-persuasion/dp/0321884507"><em>How To Get People to Do Stuff</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/312/1*yxdIXmY1RTALfYq85dILKA.png" /><figcaption>One of Susan’s most notable books</figcaption></figure><p>As you would expect, during the interview we talk a lot about the brain, and what we as designers, product managers, marketers etc, can learn from psychology when we’re designing experiences for customers.</p><p>We discuss topics such as:</p><ul><li>Three nuggets from the book <em>100 Things Every Designer Needs to Know About People</em></li><li>How unconsciousness is affecting our decision-making</li><li>The importance of designing for peripheral vision</li><li>Why you should ask customers for stories, and the benefits of the story format</li><li>Dopamine, and the power of anticipation</li><li>The ethics of data mining</li></ul><blockquote>“We now know that people process information best in a story format” — Susan Weinschenk</blockquote><h4>Have a listen</h4><p>Listen on Soundcloud, iTunes, Acast, Spotify or any other podcast platform of your choice.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F261939795%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fslowtofast%2Fslowtofast-ep-11-with-susan-weinschenk-on-the-brain-dopamine-and-the-power-of-anticipation&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000160852354-bjb59q-t500x500.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="500" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/dc2082c88c26aae69141620cace31469/href">https://medium.com/media/dc2082c88c26aae69141620cace31469/href</a></iframe><h4><strong>References:</strong></h4><p><a href="http://frombusinesstobuttons.com/">From Business To Buttons conference</a></p><p><a href="https://en.wikipedia.org/wiki/Paul_J._Zak">Paul Zak</a></p><p><a href="https://en.wikipedia.org/wiki/Robert_Sapolsky">Robert Sapolsky</a></p><p><a href="https://en.wikipedia.org/wiki/Story_arc">Story arc</a></p><p><a href="http://www.amazon.com/Hooked-How-Build-Habit-Forming-Products-ebook/dp/B00HJ4A43S">Hooked: How to Build Habit-Forming Products</a>, by Nir Eyal [Book]</p><h4><strong>Susan’s presentation from the conference:</strong></h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2FD7RqtOC87POESK&amp;url=http%3A%2F%2Fwww.slideshare.net%2Finusese%2Fsusan-weinschenk-robots-vr-and-ai-the-future-of-human-interaction-with-technology&amp;image=http%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fweinschenkstockholm-160419112807-thumbnail-4.jpg%3Fcb%3D1461065360&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/fac3425e8179aedb3457ffdea237059e/href">https://medium.com/media/fac3425e8179aedb3457ffdea237059e/href</a></iframe><h4>What should we talk about next?</h4><p>Let us know what to talk about next, by writing a comment below or using the hashtag <a href="https://twitter.com/hashtag/slowtofast">#slowtofast </a>on Twitter…or send us a fax +46 8 506 33 065.</p><p>Thanks for listening,</p><p><a href="https://twitter.com/dhettema">Dennis</a> &amp; <a href="https://twitter.com/tuvapalm">Marcus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8bca0704e4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#slowtofast Ep 10— On runways, retrospectives and death by meeting]]></title>
            <link>https://medium.com/slowtofast-podcast/slowtofast-ep-10-on-runways-retrospectives-and-death-by-meeting-9a558b51fddb?source=rss-318d3323fa09------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a558b51fddb</guid>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[podcast]]></category>
            <dc:creator><![CDATA[Marcus Castenfors]]></dc:creator>
            <pubDate>Mon, 18 Apr 2016 14:06:30 GMT</pubDate>
            <atom:updated>2016-04-19T13:26:25.760Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2qn4zuGVGC2rMZiogYS-nQ.png" /></figure><p>A milestone! 🎂 🍾</p><p>We are celebrating 10 episodes. Dennis and I are back in the studio yet again to share what we work on, and what makes us inspired.</p><p>We initially stated that we would record 10 episodes as a test. And…we’ve decided to continue! 🚀</p><blockquote>“Don’t jerk the steering wheel.” <a href="https://medium.com/u/bfa0a6e28398">Dennis Hettema</a></blockquote><p><strong>What we talk about in this episode</strong></p><ul><li>The concept of “the runway”. Whatever you work on has a time limit. Learn how to use this to your advantage. Dennis also shares a story from an exercise he did together with the General Management team</li><li>The Design Studio is moving out to the scrum teams and Marcus shares the reason behind this move</li><li>Dennis talks about a book that he shared with the entire General Management team and the product organization. It’s called “Death by meeting”, and is written by Patrick Lencioni. Dennis sheds light on the topic of the book: how to make your meetings more productive</li><li>Marcus shares a simple framework for doing retrospectives, and also the concept of the “Pet Peeves” meeting, a meeting where the design team talks about little things they get annoyed by</li></ul><blockquote>“Am I still on the path for lift off or is there something I need to tweak?” <a href="https://medium.com/u/bfa0a6e28398">Dennis Hettema</a></blockquote><h3><strong>References</strong></h3><p><a href="http://www.amazon.com/Death-Meeting-Leadership-Solving-Business/dp/0787968056">Death by Meeting</a>: A Leadership Fable…About Solving the Most Painful Problem in Business, by Patrick Lencioni [Book]</p><p><a href="http://plans-for-retrospectives.com/">The Retromat</a></p><p><a href="https://soundcloud.com/slowtofast/slowtofast-ep-01-on-diamonds-and-happiness">Episode 1 of #slowtofast</a></p><h3>Have a listen</h3><p>Listen on Soundcloud, iTunes, Acast, Spotify or any other podcast platform of your choice.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F259671781%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fslowtofast%2Fslowtofast-ep-10-on-runways-retrospectives-and-death-by-meeting&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000158712002-v9npuf-t500x500.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="500" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/1110828e7b1e4a86207a0760b665e3a7/href">https://medium.com/media/1110828e7b1e4a86207a0760b665e3a7/href</a></iframe><h3>What should we talk about next?</h3><p>Let us know what to talk about next, by writing a comment below or using the hashtag <a href="https://twitter.com/hashtag/slowtofast">#slowtofast </a>on Twitter…or send us a fax +46 8 506 33 065.</p><p>Thanks for listening,</p><p><a href="https://twitter.com/dhettema">Dennis</a> &amp; <a href="https://twitter.com/tuvapalm">Marcus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a558b51fddb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slowtofast-podcast/slowtofast-ep-10-on-runways-retrospectives-and-death-by-meeting-9a558b51fddb">#slowtofast Ep 10— On runways, retrospectives and death by meeting</a> was originally published in <a href="https://medium.com/slowtofast-podcast">#slowtofast podcast</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 words I learned at the #FBTB16 conference]]></title>
            <link>https://medium.com/@mcastenfors/4-words-i-learned-at-the-fbtb16-conference-b252e140332e?source=rss-318d3323fa09------2</link>
            <guid isPermaLink="false">https://medium.com/p/b252e140332e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Marcus Castenfors]]></dc:creator>
            <pubDate>Mon, 18 Apr 2016 08:17:14 GMT</pubDate>
            <atom:updated>2016-04-19T17:21:26.021Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*5KmgNl4Eu5NsjtY0o_m26Q.png" /></figure><p>Last Friday I attended the <a href="http://frombusinesstobuttons.com/">From Business To Buttons conference</a> in Stockholm.</p><p>👏 to <a href="http://inuse.se/">InUse</a> for organizing the conference.</p><p>It was a star-studded event with Al Gore as the <em>pièce de résistance</em>.</p><p>I left feeling inspired and bubbling with ideas. To sum up my takeaways from the conference, I’ll share four words that stood out.</p><h3>1. Brobots</h3><p><a href="https://twitter.com/thebrainlady">Susan Weinschenk</a> is a Ph.D. in Psychology, and author of <a href="http://www.amazon.com/Susan-M.-Weinschenk/e/B002BM92ZO">many books</a> on design and psychology. In her talk, she highlighted our future relationships with robots. They will become our friends. If you watch this short video you will understand the human side of our computerized soon-to-be peers.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F99422211&amp;url=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F99422211&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F515439578_1280.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1280" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/a564bc5f3a80a58b321ed294d65934aa/href">https://medium.com/media/a564bc5f3a80a58b321ed294d65934aa/href</a></iframe><h3>2. Anthropomorphism</h3><p>Susan also talked about “anthropomorphism”: How we attribute — how we are as humans — to robots and other inanimate objects.</p><blockquote><strong><em>anthropomorphism</em></strong><em> definition. (an-thruh-puh-mawr-fiz-uhm) The attributing of human characteristics and purposes to inanimate objects, animals, plants, or other natural phenomena, or to God.</em></blockquote><p>This means that we empathize with robots because we believe they are similar to us. We have feelings for them. If they get bullied, for instance, we react.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-Wnp-OOZB34%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-Wnp-OOZB34&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-Wnp-OOZB34%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/5e3746c60dcb3ecd9cf1e3d134856345/href">https://medium.com/media/5e3746c60dcb3ecd9cf1e3d134856345/href</a></iframe><h3>3. Ringxiety</h3><p>Ringxiety is also known as the <a href="https://en.wikipedia.org/wiki/Phantom_vibration_syndrome">“Phantom Vibration Syndrome”</a>. We believe the phone is ringing, but it’s not. The reality is that we are addicted to our phones, and our screens.</p><p><a href="https://twitter.com/goldenkrishna">Golden Krishna</a>, a Design Strategist at Google, and the author of <a href="http://www.nointerface.com/">“The Best Interface is No Interface”</a>, opened the audience’s eyes to our screen addiction. As adults, we spend 8.5 hours per day looking at screens. And, according to a study, children become less empathetic after interacting with screens.</p><p>There is an app for everything. But the world doesn’t need anymore apps.</p><p>The solution: don’t solve design problems by yet another screen. We should instead think how technology can be used to solve problems without a person interacting with an interface.</p><p>One of Golden’s examples is <a href="https://digit.co/">Digit</a>, a service that connects to your bank account and saves money for you, without you needing to do a thing.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F114073586&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F114073586&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F499622346_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/a4a9d562062ef4b5a7ac181c893a30e0/href">https://medium.com/media/a4a9d562062ef4b5a7ac181c893a30e0/href</a></iframe><blockquote>”We serve computers when computers should serve us” — Golden Krishna</blockquote><h3>4. Equanimity</h3><p>Another theme during the conference was design leadership, and how you should act as a design leader. Both <a href="https://twitter.com/veen">Jeff Veen</a>, the former CEO of Typekit, and <a href="https://twitter.com/cgosimon">Simon Bennett</a>, brought up the term Equanimity in their talks.</p><blockquote><strong>Equanimity</strong> (Latin: æquanimitas having an even mind; aequus even animus mind/soul) is a state of psychological stability and composure which is undisturbed by experience of or exposure to emotions, pain, or other phenomena that may cause others to lose the balance of their mind.</blockquote><p>Their talks highlighted the importance of a manager to create a safe environment for the team, an environment where you can handle stress. Jeff Veen brought up the notion that we can control our emotions, and that we need to have a mental buffer when reacting to changes around us.</p><blockquote>“We choose the emotions that we have” — Jeff Veen</blockquote><p>Jeff’s argument is that a team thrives when we have a sense of equanimity, a mental calmness.</p><h3>Summary</h3><p>To sum up all the talks in a few sentences:</p><ul><li>We feel robots are similar to us humans. We have feelings for them. And they will become our friends</li><li>We need to see past screens when designing products and services</li><li>We need to see ourselves as leaders, not just as designers, and create safe environments for teams</li></ul><p>Thanks,</p><p><a href="https://medium.com/u/318d3323fa09">Marcus Castenfors</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b252e140332e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#slowtofast Ep 09 — Introducing our new CTO Tuva Palm]]></title>
            <link>https://medium.com/slowtofast-podcast/slowtofast-ep-09-the-tuva-palm-edition-81073cbc9e?source=rss-318d3323fa09------2</link>
            <guid isPermaLink="false">https://medium.com/p/81073cbc9e</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Marcus Castenfors]]></dc:creator>
            <pubDate>Mon, 04 Apr 2016 12:48:06 GMT</pubDate>
            <atom:updated>2016-04-04T12:48:35.382Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EgWmkVcAGNCnuBT5UXa4sA.png" /></figure><p>In this episode we introduce our new awesome CTO Tuva Palm who joined us a little over a month ago. 👋</p><p>Tuva has an extensive background in engineering and product management from companies such as Oracle and Klarna. She is also the co-host of <a href="https://sthlmtechmeetup.confetti.events/">STHLM Tech</a>, the biggest tech meetup in Europe.</p><h3>Dennis Hettema on Twitter</h3><p>Trying to record a #slowtofast with @tuvapalm pic.twitter.com/v8PEu6Jsnz</p><p>Dennis and Tuva have an intense and entertaining conversation about:</p><ul><li>The startup scene in Sweden</li><li>The BOPS prio list, a prioritization framework used by Spotify, and Klarna</li><li>The key to creating something that customers want</li><li>Trends in technology</li><li>Successful traits of a CTO</li><li>Ingredients to achieve speed in product organizations</li><li>Tuva’s affection for <a href="http://svpg.com/articles/">Marty Cagan</a>’s blog articles</li></ul><h3>Tuva Palm on Twitter</h3><p>@dhettema where I reveal the true story about the BOPS prio list, originally invented @gsaab</p><h3>Have a listen</h3><p>Listen on Soundcloud, iTunes, Acast, Spotify or any other podcast platform of your choice.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F257244662%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fslowtofast%2Fslowtofast-ep-09-introducing-our-new-cto-tuva-palm&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000156375599-t28zxn-t500x500.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=soundcloud" width="500" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/6d49fc0a4166106677decf28f824e38e/href">https://medium.com/media/6d49fc0a4166106677decf28f824e38e/href</a></iframe><h3>What should we talk about next?</h3><p>Let us know what to talk about next, by writing a comment below or using the hashtag <a href="https://twitter.com/hashtag/slowtofast">#slowtofast </a>on Twitter…or send us a fax +46 8 506 33 065.</p><p>Thanks for listening,</p><p><a href="https://twitter.com/dhettema">Dennis</a>, <a href="https://twitter.com/tuvapalm">Tuva</a> and <a href="https://twitter.com/tuvapalm">Marcus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81073cbc9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slowtofast-podcast/slowtofast-ep-09-the-tuva-palm-edition-81073cbc9e">#slowtofast Ep 09 — Introducing our new CTO Tuva Palm</a> was originally published in <a href="https://medium.com/slowtofast-podcast">#slowtofast podcast</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>