<?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 Custellence on Medium]]></title>
        <description><![CDATA[Stories by Custellence on Medium]]></description>
        <link>https://medium.com/@Custellence?source=rss-fe90e577cea2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qNycpzrhkonjcbCUj9vmvw.jpeg</url>
            <title>Stories by Custellence on Medium</title>
            <link>https://medium.com/@Custellence?source=rss-fe90e577cea2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:58:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Custellence/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[How to build a business case for investing in Customer Experience]]></title>
            <link>https://medium.com/@Custellence/how-to-build-a-business-case-for-investing-in-customer-experience-b28c54440140?source=rss-fe90e577cea2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b28c54440140</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-journey-mapping]]></category>
            <category><![CDATA[cx]]></category>
            <category><![CDATA[customer-journey]]></category>
            <category><![CDATA[roi]]></category>
            <dc:creator><![CDATA[Custellence]]></dc:creator>
            <pubDate>Thu, 05 Jul 2018 12:43:16 GMT</pubDate>
            <atom:updated>2018-07-05T12:43:16.578Z</atom:updated>
            <content:encoded><![CDATA[<p>How do you convince your boss that customer experience is something worth investing in? Can you prove the business effects and value of improving the customer experience? How do you get buy-in from colleagues, your manager, or the board?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v_bY-A2-jfEt3kf--AKupQ.jpeg" /><figcaption><em>Photo by </em><a href="https://unsplash.com/@rawpixel"><em>Rawpixel on Unsplash</em></a></figcaption></figure><h3>Linking the customer experience to tangible value</h3><p>There is a reason for the saying “what gets measured gets managed”. And this is extremely relevant when it comes to customer experience, whose effect on business value still gets questioned. Or considered to be too vague. And vagueness is not a winning concept when arguing for resources in a boardroom.</p><p>You need to be able to show the economic outcomes of the differences in customer experiences, by linking to figures like key performance metrics, efficiency and profitability. In short, you need to build a business case that connects your customer experience efforts to value for your organization.</p><h3>The business case</h3><p>The business case for investing in Customer Experience differs from one organization to another, and yours should be based on your organization’s conditions, challenges and objectives. Here are some aspects to guide you on how the case can be built.</p><p>The first thing to define is what measurable business critical outcomes will be affected by improving the customer experience in your organization: is it cost reductions, increased revenue, market share or other?</p><p>A common starting point is the costs. In the public sector for instance, the case is most often about increased value for the citizens at a lower cost. But increased revenue or market share are also common starting points.</p><h3>Three key steps in creating the business case</h3><ol><li>First you need to understand the costs that really matters. What metrics are important in your organization? What costs are actually a problem? What performance figures are on the agenda of the management? Check the list (A) below as inspiration.</li><li>Next step is to understand the cost drivers of a good or a bad customer experience. Below is a list of customer benefits (B) as inspiration. What is the connection between A and B now? What relationships can be indicated? Be aware that all business cases contain guesses and assumptions. Can the connection between A and B be made and accepted internally?</li><li>The third step is to make sure that you can measure and follow up the improvements in the list (B). You have connected them to your figures in list (A). For instance, can a reduction in the amount of calls to customer service be measured? Will the improvement reduce the cost, and if so, how? Will improvement increase revenue, and if so, how? Can the relationship between the cost of the amount of calls to customer service and customer satisfaction rate be clearly demonstrated?</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*hipUngxM-8ul2oA55uv-TA.png" /><figcaption>Visualize the connection between the customer experience, the costs and the revenues. Copyright: Custellence</figcaption></figure><p><strong>A: What figures are business critical in your organization right now?</strong> Of all the performance figures that is measured in your organization, which are the ones that matters?</p><ul><li>Revenue and growth</li><li>Costs</li><li>Operating profit</li><li>Market value</li><li>Variation in cash flow</li><li>Risks and the number of failed initiatives</li><li>Employee commitment and employee satisfaction</li><li>Recruitment</li><li>Confidence in management and organization</li><li>Process Efficiency</li></ul><p><strong>B: Customer benefits of Customer Experience-leading organizations</strong></p><ul><li>Customers show greater confidence</li><li>Customers prefer that organization’s services to others</li><li>Customers stay longer</li><li>Customers invest more in services and products</li><li>Customers return and upgrade more often</li><li>Customers are less price sensitive</li><li>Customers speak positively and recommend</li><li>Customers praise staff</li><li>Customers do not talk badly and do not discourage others</li><li>Customers understand the service and rarely ask</li><li>Customers show greater patience when mistreated and complain less</li><li>Customers are cheaper to serve</li></ul><h3>Further reading on how to build your Customer Experience case</h3><p><a href="https://www.gartner.com/smarterwithgartner/five-steps-to-a-robust-customer-experience-business-case/">Gartner’s five steps to a robust Customer Experience business case</a></p><p><a href="https://www.mckinsey.com/business-functions/marketing-and-sales/our-insights/linking-the-customer-experience-to-value">McKinsey on Linking the Customer Experience to value</a></p><p><a href="https://hbr.org/2014/08/the-value-of-customer-experience-quantified">Harvard business revue on The Value of Customer Experience, Quantified</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b28c54440140" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 6 biggest Customer Journey Mapping mistakes and what to do instead]]></title>
            <link>https://medium.com/@Custellence/the-6-biggest-customer-journey-mapping-mistakes-and-what-to-do-instead-d0ede674346c?source=rss-fe90e577cea2------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0ede674346c</guid>
            <category><![CDATA[customer-journey-map]]></category>
            <category><![CDATA[customer-journey-mapping]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-journey]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Custellence]]></dc:creator>
            <pubDate>Sun, 11 Mar 2018 23:00:00 GMT</pubDate>
            <atom:updated>2018-03-26T12:54:13.499Z</atom:updated>
            <content:encoded><![CDATA[<p>Customer Journey Mapping is not only great fun to do, it is an essential activity when creating great customer experiences. But it’s easy to get lost when working with Customer Journeys. Not just when mapping the journey, but also when implementing the customer centric changes in the organization. Here we have listed 6 of the most common mistakes people do when mapping the Customer Journey, and what to do instead.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aEQAE4uXYHAMrb3P.png" /><figcaption>6 Biggest Customer Journey Mapping mistakes and what to do instead</figcaption></figure><h3>Mistake no 1: to focus on touchpoints instead of the customer activities</h3><p>If you focus on mapping the touchpoints, i e the points where the customer have an interaction with your company, its’ products or services, then you are on thin ice. By doing this you will miss the customer’s reality and perspective. And you will end up with a false map. Instead, start by mapping the customer’s activities and situations, and be aware — many if them happens outside your company. Once you have done that, then you can add your organization´s touchpoints, channels and everything else that happens on the inside.</p><h3>Mistake no 2: to wait until you have collected enough customer insights</h3><p>To wait until you have collected enough insights from field studies, interviews and other customer research, before you start mapping, might be the kosher way of doing customer journey mapping. But the drawback is that you loose precious time, and it will make it harder to get started.</p><p>So, instead of stalling, just start mapping the assumptions that you have about what the customer goes through. By doing so you will not only get a good starting-point for further mapping, you will also help your colleagues to get into a customer mindset, which is of great value.</p><h3>Mistake no 3: mixing up and acting on the wrong stuff</h3><p>As you know by now, It’s ok to put customer true insights and assumptions side by side in a journey map. It can be of good use when you need to visualize an overall journey. But make sure that you know what´s what. Otherwise you might fall into the trap of acting on and investing money in a problem or a solution that is not true customer centric and based on reality.</p><p>Also, remember that there are two important aspects of the customer journey mapping. One is obviously the experience and needs of the customers, but equally important is the business challenges you want to solve. Therefore, make sure that you put your mapping efforts into the areas that are important to your business. And in those areas, it is crucial that you have true customer insights. In other areas, you might well go along with a few assumptions, as it will save you time and lets you focus on the more critical areas.</p><h3>Mistake no 4: getting stuck in between the ASIS and TOBE</h3><p>Avoid getting stuck in between the ASIS-map and the TOBE-map. Many professionals start by creating a customer journey map that visualises the current state, the ASIS-map. To achieve change, you also want to create a future scenario, i e the TOBE-map. This map is also called Service Blueprint. But as you can imagine, having to juggle two maps, and updating them and adding insights can be confusing. It´s very easy to get lost.</p><p>Instead, for you to be able to act on the insights and to drive the change, it is better to create a journey map that works more like a change plan: still firmly based in customer and business insights and needs, but more actionable and agile. So instead of creating two maps, stick with one map that functions both as an ASIS- and the TOBE- version. That way you have map that will give you an overview of where you are today, and where you are heading. In this combined map, it is both easy to visualize the progress and to change and update the map when change has been made.</p><h3>Mistake no 5: keeping the Customer Journey Map exclusive to a small group</h3><p>A mistake we see frequently, and one that is sure to hold you back, is to keep the customer journey map exclusively to a small group of people. And this is another sure way to fail, especially when trying to implement changes.</p><p>Success will come to you much sooner if you share the map with as many as possible. Be transparent and encourage collaboration and remember to start by implementing the Customer journey Map before you start implementing the results of the journey map. By doing so, not only will you create the customer centricity that’s crucial, you will also be able to spur engagement, acceptance and co-operation. Try it, it will work as rocket fuel for your transformation!</p><h3>Mistake no 6: treating the Customer Journey Map as a project delivery</h3><p>Some professionals think of the Customer Journey Map as a project delivery, something that finishes off a project. Nothing could be more wrong. If you have this mindset, the customer journey map will surely end up in a folder somewhere, and all your efforts will be wasted.</p><p>Instead, as we have written earlier, the journey map should be seen as a starting-point for a customer centric change, and as a tool for implementing the changes founded in customer insight and business needs. So pick up that map and start using it right away. And make sure to keep the change plan updated and current in your daily work!</p><p>By Daniel Ewerman — March 12, 2018</p><p><em>Originally published at </em><a href="https://custellence.com/blog/the-6-biggest-customer-journey-mapping-mistakes-and-what-to-do-instead.html"><em>custellence.com</em></a><em> on March 11, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0ede674346c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Webinar: Make Customer Journey Mapping easier, faster and more collaborative]]></title>
            <link>https://medium.com/@Custellence/webinar-make-customer-journey-mapping-easier-faster-and-more-collaborative-b428350e3586?source=rss-fe90e577cea2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b428350e3586</guid>
            <category><![CDATA[customer-journey-map]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[cx]]></category>
            <category><![CDATA[customer-journey]]></category>
            <dc:creator><![CDATA[Custellence]]></dc:creator>
            <pubDate>Thu, 14 Sep 2017 06:38:27 GMT</pubDate>
            <atom:updated>2017-09-14T06:40:17.258Z</atom:updated>
            <content:encoded><![CDATA[<h4>Want more happy customers, lower your churn, raise your Customer Satisfaction Index? Take Customer Journey Mapping to the next level by using the cloud based tool <a href="https://custellence.com/">Custellence</a>.</h4><p>Register for this webinar and learn how Custellence helps you to spend more time delivering a better customer experience and less making customer journey maps. <a href="https://my.demio.com/ref/iJhdk6r515bqtuOF">Sign up form</a></p><p>September 28th, 2017 at 8:00PM CEST</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*YkXYhdxYzCDHtgk6ZUQbHw.png" /></figure><h3>This webinar will be hosted by</h3><p><strong>Daniel Ewerman | CEO, </strong><a href="https://custellence.com/"><strong>Custellence</strong></a></p><p><strong>Marc Fonteijn | Co-founder </strong><a href="http://www.31volts.com/"><strong>31Volts</strong></a><strong> | host of the</strong><a href="https://www.youtube.com/channel/UCYpyoyI0DiujtiRuN-VgxWg"><strong>ServiceDesignShow.com</strong></a></p><h3>What will you learn</h3><ol><li><strong>The map</strong>: How to take your Customer Journey Mapping to a more professional level. How assumption based can they be? As-Is or To-Be maps, pros and cons? Which customer journeys should we start with? How detailed do they need to be?</li><li><strong>The tool:</strong> What are the <strong>benefits</strong> of a tool like Custellence? Step by step, how do you succeed with it. You will learn <strong>best practices and different ways to structure maps</strong>.</li><li><strong>The organization: </strong>How do you organize yourself in the best way around Custellence to ensure that customer needs are not lost in the management, development or maintenance. We discuss ways to keep the maps up-to-date over time and make it to the governing plan.</li></ol><h3>Register</h3><p>Please go to this <a href="https://my.demio.com/ref/iJhdk6r515bqtuOF">Sign up form</a>.</p><p>Hoping to see you there // Marc and Daniel</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b428350e3586" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Webinar: Make Customer Journey Mapping easier, faster and more collaborative]]></title>
            <link>https://medium.com/@Custellence/webinar-make-customer-journey-mapping-easier-faster-and-more-collaborative-4f0cc93537fc?source=rss-fe90e577cea2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f0cc93537fc</guid>
            <category><![CDATA[customer-journey-map]]></category>
            <category><![CDATA[customer-journey]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-journey-mapping]]></category>
            <category><![CDATA[webinar]]></category>
            <dc:creator><![CDATA[Custellence]]></dc:creator>
            <pubDate>Fri, 05 May 2017 08:10:51 GMT</pubDate>
            <atom:updated>2017-05-05T08:10:51.019Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Want more happy customers, lower your churn, raise your Customer Satisfaction Index? Take Customer Journey Mapping to the next level by using the cloud based tool </strong><a href="https://custellence.com/"><strong>Custellence</strong></a><strong>.</strong></h4><p>Register for this webinar and learn how Custellence helps you to spend more time delivering a better customer experience and less making customer journey maps. S<a href="https://goo.gl/zT7s93">ign up form</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rqpIDz8GPAnPivZQyI8ibQ.jpeg" /></figure><h3>This webinar will be hosted by</h3><p><strong>Daniel Ewerman | Founder and CEO, </strong><a href="https://custellence.com/"><strong>Custellence</strong></a><strong> and </strong><a href="http://transformatordesign.se/"><strong>Transformator Design</strong></a></p><p><strong>Marc Fonteijn | Co-founder </strong><a href="http://www.31volts.com/"><strong>31Volts</strong></a><strong> and host of the </strong><a href="https://www.youtube.com/channel/UCYpyoyI0DiujtiRuN-VgxWg"><strong>ServiceDesignShow.com</strong></a></p><h3>What will you learn</h3><ol><li><strong>The map</strong>: How to take your Customer Journey Mapping to a more professional level. How assumption based can they be? As-Is or To-Be maps, pros and cons? Which customer journeys should we start with? How detailed do they need to be?</li><li><strong>The tool:</strong> What are the <strong>benefits</strong> of a tool like Custellence? Step by step, how do you succeed with it. You will learn <strong>best practices and different ways to structure maps</strong>.</li><li><strong>The organization: </strong>How do you organize yourself in the best way around Custellence to ensure that customer needs are not lost in the management, development or maintenance. We discuss ways to keep the maps up-to-date over time and make it to the governing plan.</li></ol><h3>Register</h3><p>Please go to this S<a href="https://goo.gl/zT7s93">ign up form</a> and choose the time that works best for you.</p><ul><li>Wednesday the 31st of May, 9:00–10:00 (CET)</li><li>Wednesday the 31st of May, 14:00–15:00 (CET)</li><li>Wednesday the 31st of May, 20:00–21:00 (CET)</li></ul><p>If you can’t attend live? You should still register! We will be sending out slides and recordings after the webinar to all the registrants.</p><p>Hoping to see you there // Marc and Daniel</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f0cc93537fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Custellence Case: How a service company within the field of pension and insurance uses the Customer…]]></title>
            <link>https://medium.com/@Custellence/custellence-case-how-a-service-company-within-the-field-of-pension-and-insurance-uses-the-customer-aea6ff84ac8d?source=rss-fe90e577cea2------2</link>
            <guid isPermaLink="false">https://medium.com/p/aea6ff84ac8d</guid>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[customer-journey]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[digitalization]]></category>
            <dc:creator><![CDATA[Custellence]]></dc:creator>
            <pubDate>Tue, 25 Apr 2017 13:42:07 GMT</pubDate>
            <atom:updated>2017-04-25T13:49:02.935Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Custellence Case: How a service company within the field of pension and insurance uses the Customer Journey to Digitalize!</strong></h3><h4><strong>Many organizations have the ambition to improve their customer experience while at the same time facing challenges in their digital transformation. The use of customer research, user journeys and digitalization maps help the service company Fora in bridging those challenges and create a base for decision-making and more accurate prioritizations.</strong></h4><h3><strong>The Challenge</strong></h3><p>Fora is a non profit service company whose main task is to handle the flow of collective insurance premiums and fees between companies and insurance providers. They also have the liability to provide impartial information and tools to employers and their personnel concerning collective insurance and SAF-LO Collective Pension Insurance.</p><p>In the transformative process that Fora has been in during the last couple of years, they turned to the service design agency Transformator Design to obtain a deeper customer understanding. Fora wanted help in visualizing their customers’ journeys to create a more relevant service offering and clearer customer communication. They also wanted the customers’ needs to become top of mind, in order to prioritize, make decisions and plan for future platforms catering to those needs.</p><blockquote>Fora faced the classic challenge that organizations face when undergoing large scale changes — how to stay familiar and relevant here and now, while at the same time incrementally provide new solutions.</blockquote><p>The objective of the new customer experience, for the individual was to ensure simplicity as well as a sense of security for individual errands. Fora wanted to find a better interface for companies by providing a clear path to an extensive network of insurance providers. In addition to this Fora faced the classic challenge that organizations face when undergoing large scale changes — how to stay familiar and relevant here and now, while at the same time incrementally provide new solutions to meet future needs and customers.</p><blockquote>“We now have a deeper understanding of our customers — their needs and behaviors. The customer journeys and the detailed digitalization map based on those, help us see how it’s all connected. We use them in daily short term work as well as in long term prioritization and decision​ making.”</blockquote><blockquote>— Christina Schiller, Head of Communications at Fora</blockquote><h3><strong>An enabler in the development process</strong></h3><p>Transformator Design’s method prioritized the early discovery of customer needs and insights which could then guide development. In order to ensure successful routing based on empathy for the customer, experienced service designers conducted in-depth interviews in order to discover why customers needed a specific service, and to design the experience with those needs in mind. This is a step which is easily overlooked, but which is a critical part of being able to easily prioritize measures later in the process.</p><p>Tranformator Design used the customer journey mapping tool Custellence, to systematically categorize customer insights and enable traceability and readability at different levels. Two digitalization maps were created, which were based on the customer journey, one for companies and one for employees. The maps answered the questions on why and where development should be done from a customer perspective. The maps made it possible to develop insights into activities and be able to track how different levels of change are affected by the customer needs.</p><blockquote><strong>An important aspect that the tool contributed to was to enable prioritization, to break down the big picture into components that were accurate from a customer perspective.</strong></blockquote><p>The tool provides possibilities to toggle the levels of detail, i.e. to be able to zoom in on a detail of a digital interface, or zoom out for an overview of an operational perspective.</p><p>An important aspect that the tool contributed to was to enable prioritization, to break down the big picture into components that were accurate from a customer perspective.</p><h3><strong>The Solution — Digitalization Maps</strong></h3><p>The solution became an unconventional customer journey map. In Fora’s digitizing map the customer moves vertically from the top down rather than horizontally, from left to right. The reason for this is that Fora’s customer journey consists of a few major areas of events occurring independently of each other without any chronological order. This structure was chosen in order to show a deep level of detail and still maintain a good overview.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*qt7uROcRtYyFREy9ODnFpA.png" /></figure><p>Fora digitalization maps contains the following:</p><ul><li><strong>Use case description: </strong>Connected to each life event or corporate event is a description of a use case which summarizes customer objectives and what would be required for the customer to reach the objective. Here you describe, for example, preconditions and success factors, i.e. the needs and interests that are fulfilled. It also describes the content / features Fora can provide, what is required of Fora, as well as what could be requirements in platform changes.</li><li><strong>Flowcharts: </strong>As a concretization of the Use Case and the insights flowcharts were made, i.e. charts in detail showing flows and decision logic and which routes the user can take to attain an objective. These are basis for the next step in the development process and allows for specification of requirements for the new platform without losing the customer perspective.</li><li><strong>Key pages:</strong> Shows how activities in a flowchart can be visualized and gives an example of how a significant point in a flowchart may look like. Key pages are sketches and not final solutions.</li><li><strong>Outputs from Fora’s digital customer experience:</strong> Outputs where the customer leaves Fora with information to complete the task. Shows what the customer is doing, in which channel and to which stake holder the customer moves on from Fora.</li></ul><h3><strong>The Result</strong></h3><p>The material compiled in Custellence formed the base for the final insight delivery that was handed over from Transformator Design to Fora. That material is being used on many levels of the company, from strategic work to actual development of touch points. The various ongoing development areas are now kept together by means of the customer’s perspective and prevent them from becoming silos. The insights delivered serve as a knowledge bank in overall customer understanding within the company.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aea6ff84ac8d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SKL / Swedish Association of Local Authorities and Regions (SALAR) choose Custellence]]></title>
            <link>https://medium.com/@Custellence/skl-swedish-association-of-local-authorities-and-regions-salar-choose-custellence-553588c6ca8b?source=rss-fe90e577cea2------2</link>
            <guid isPermaLink="false">https://medium.com/p/553588c6ca8b</guid>
            <category><![CDATA[customer-centricity]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[refugees]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-journey]]></category>
            <dc:creator><![CDATA[Custellence]]></dc:creator>
            <pubDate>Tue, 31 Jan 2017 08:10:18 GMT</pubDate>
            <atom:updated>2017-01-31T08:14:53.845Z</atom:updated>
            <content:encoded><![CDATA[<h4>Today, around 60 different public authorities, municipalities and stakeholders have to coordinate their efforts in order to make the lives of unaccompanied minors seeking asylum in Sweden as good as possible. Co-lab Sweden (Förnyelselabbet) is run by the <a href="http://www.svid.se/en/">Swedish Industrial Design Foundation (SVID)</a> with direction from the SKL / <a href="https://skl.se/tjanster/englishpages.411.html">Swedish Association of Local Authorities and Regions (SALAR)</a>. Together, they have chosen <a href="https://custellence.com/">Custellence</a> as a primary customer journey tool to help them coordinate efforts and systematically improve the lives of unaccompanied minors.</h4><blockquote>– This project’s success is determined on how well we, as a system, can deliver solutions that make a positive impact in the unaccompanied minors lives and respond to their needs. We’ve got four challenges in this initiative: to create an overview, set up new collaborations, innovate with the target group in mind and simplify implementation. In order to meet these challenges we must work systematically with our challenges and that is why we chose to use <a href="https://custellence.com/">Custellence</a> as our digital tool, says Pia McAleenan at Co-lab Sweden.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*Orkj6GlBZ9ouXDvH0H6OWQ.png" /></figure><p>Using the customer journey as a starting point ensures that the improvements and concepts that come out of the process will be in line with the minor´s dreams, situation and needs. <a href="https://custellence.com/">Custellence</a> provides a digital structure for collaboration when planning the development and implementation of new concepts.</p><blockquote>– Engaging people, keeping the bigger picture in mind and collaborating without having to be in the same room are important aspects in this project. We hope to find and solve uncovered spots in the customer journey and fuse new collaborations leading to a better situation for refugees’, says Pia McAleenan.</blockquote><p><a href="http://transformatordesign.com/">Transformator Design</a> is the Custellence Partner that coaches Co-lab Sweden in using Custellence. Custellence Partners make up a network of experts who help organisations to succeed with their customer centricity. Both Custellence and Transformator Design are very proud to be able to contribute in an engaging and important social challenge as the Co-lab.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=553588c6ca8b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The invisible process]]></title>
            <link>https://medium.com/@Custellence/the-invisible-process-b2695059d812?source=rss-fe90e577cea2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2695059d812</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Custellence]]></dc:creator>
            <pubDate>Thu, 31 Mar 2016 14:22:34 GMT</pubDate>
            <atom:updated>2016-03-31T14:22:34.493Z</atom:updated>
            <content:encoded><![CDATA[<h4>Doing the right stuff at the right time, for the right reason.</h4><p>Google “Scrum + process”, you get 11 200 000 hits. “Agile + process”, 65 400 000 hits. <strong>65 millions! </strong>Clearly, there is a lot of information out there on how to work and get stuff done. But how can you keep track of that?, and does it really reflect the meaning of <a href="http://agilemanifesto.org/">The Agile Manifesto</a>? We could say that we have a Scrummisch-Kanban-Kaizen-Jugaad process, but a far more accurate name is actually The Invisible Process.</p><p>So, what does the invisible process look like?</p><h3>The only good process is an alive and working process.</h3><p>This means that no process is better then how good it is working for us right now. This is where the invisible part comes in.</p><blockquote>It has to be so good that we hardly notice it, and when we do notice it, it’s because it’s time to change it.</blockquote><p>This also means that a reflective approach needs to be in place to effectively discover whether the process creates value or not. Questions we ask ourselves include Are we using meeting time efficiently?, Is every stakeholder engaged and if not, why?, Can we improve/speed up our development process?. For example, as a result of this we don’t spend our weekly meetings discussing last week, instead an email goes out at the end of the week describing if what we said to be done during the week was done, and if not, why. This resulted in a on average 30-min time save during meetings. An email can look like this (we love <a href="https://mixmax.com/">MixMax</a> as this email structure is saved as a template, and re-used).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fxQQJIzB3LKAFCAWi7j99A.jpeg" /><figcaption>Our color-coded weekly “what has happened during the week” emails.</figcaption></figure><p>When do we do this? Every Monday meeting! The only permanent thing on the agenda.</p><blockquote>When activities are truly value-based, they don’t need to be formalized. They are so value-worthy that you’re naturally inclined to do them.</blockquote><h3><strong>Everything that is product-related is integrated in one Trello board.</strong></h3><p>Trello is not the issue here, any tool that does the equivalent job will do (even though we really like <a href="https://trello.com/">Trello</a>). The issue is to mix both product design, visual design and development in one flow. It makes re-prioritization easy, and there is never an issue of not having an overview. We do it like showed in the image below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IWo9HEmn1kTeqIzm5O2KKQ.jpeg" /><figcaption>How our design-development integrated Trello board is structured.</figcaption></figure><ol><li>Starting with Product design, this column contains user tasks and stories of product features, intermixed and of various complexity. Sometimes features are divided into smaller tasks as they progress through the flow, but we always (try) to start with the user story as it helps us to see things from the right perspective.</li><li>Next up is Feature upgrades. This column contains user task flows that needs to be improved, or tasks that are a part of our Incremental feature design approach (see We ship product features incrementally for a more thorough description).</li><li>Bugs. Need we say more?</li><li>The Engineering column contains mostly backstage activities. What do we mean with backstage activities? Well, simplified it’s activities that enable front-end and backend to work the right way. This includes to set up testing, maintenance and refactoring.</li><li>Next up — this is where our weekly planning ends up. Moving items from columns 1–4 into this column is what we call weekly planning. The designer never moves items further than this, and notify the developer that she-he is good to go by simply changing the assigned person.</li><li>What the developer is working on ends up in Doing, and moves to</li><li>Ready for test when it’s done. When it’s pushed to the test server, it ends up in</li><li>QA, Quality Assurance, to be tested by the product designer.</li><li>Done.</li></ol><p>(Yes, we do have a backlog. It’s on another board, and contains all our Next Big Things, and Maybe Later ideas.)</p><h3><strong>Balancing onstage and backstage activities.</strong></h3><p><a href="http://inuseexperience.com/impactmapping.php#impact-mapping">Impact mapping</a> is an excellent technique to build understanding for both business and user goals, creating soft requirements that bring management and development together. But it’s equally important to get a nice workflow in the product design team on a day-to-day basis, balancing onstage, backstage, refine&amp;repair and new feature activities. In small teams this can especially important, as it allows design och code to cartwheel activities efficiently. It’s also a good way of emphasizing the importance of backstage below-the-surface activities and not only onstage stuff that your colleagues will notice (the top of the iceberg). This can be especially challenging in organizations that isn’t used to working with web and software development. We have discovered that for us it works nicely to balance activities with a four-quadrant grid, as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t7Mn45wJKyAslNmj_gjaAw.jpeg" /><figcaption>The Onstage — Backstage quadrant grid.</figcaption></figure><h3>We ship product features incrementally.</h3><p>When developing large and/or very complex features, it’s easy to get caught in the complexity of it all. We try to identify the core of the feature and develop that, gathering valuable input and insights from users BEFORE we move on and add more complexity. It helps us to focus on the right stuff, and can be seen as live user co-design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/646/1*4hrtxdb4s61gHUsYknCuVg.jpeg" /><figcaption>Our process for complex features. Develop — Learn — (Iterate) — Develop — Learn — (Iterate).</figcaption></figure><h3>Strategy and planning is based on value creation for customers.</h3><p>Lastly, but not the least — we base our strategy on customer insights. It’s one of our strongest core values, as we are building a SaaS designed to help organizations become more customer-centric. Although we of course as any other become infatuated and entangled with advanced product features, we always return to basics. By being surrounded with people who are our users, we are constantly exposed to what their main gains and pains are. By letting our product designers handle the customer support, we don’t risk loosing important customer insights in company silos.</p><h3>To summarize,</h3><p>we constantly challenge our process, and it will change during different phases of the service life-cycle. We maintain a good overview by keeping the team working integrated around the product design, focusing on creating user value.</p><h4>So, who are partaking in this invisible process, and how do we work to maintain a customer-centricity in the team? Well, we’ll talk more about that in our next post, including the responsibilities of a customer-centric product owner.</h4><p><em>Custellence is a dynamic customer journey tool that enables organizations to unite around customer needs. </em><a href="http://custellence.com/"><em>Try our beta.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2695059d812" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making great customer journeys]]></title>
            <link>https://medium.com/@Custellence/making-great-customer-journeys-37b6995551d2?source=rss-fe90e577cea2------2</link>
            <guid isPermaLink="false">https://medium.com/p/37b6995551d2</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Custellence]]></dc:creator>
            <pubDate>Tue, 09 Feb 2016 13:17:12 GMT</pubDate>
            <atom:updated>2016-02-09T13:17:31.595Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*owgxwWhCiMxLuEPidhyIGg.jpeg" /></figure><h4>A customer journey is a great tool to capture the total experience of a business / organization from the customer’s point of view.</h4><p>As implied by the name, a customer journey describes a story of how customers move through and interact with a business. It typically includes customer activities that happens before, during and after using the service, touchpoints with the service organization, but also feelings and attitudes — revealing how and where your business is doing great, and where there is room for improvements. Simply put, it teaches companies and organizations about their customers.</p><p>So how do you make great customer journeys? The service and business designers at Transformator Design share their best tips and customer journey ingredients here.</p><h3>Define the purpose</h3><p>Why are you making the customer journey, and how will you use it? These are questions that are good to think about at the beginning of and throughout a project. Do you want to map the current customer journey or the ideal customer journey? Do you want to use it to communicate something, or co-create? From our experience, there are two ways of doing it. First you start by mapping out today, and identify opportunities, problems and what’s just running smoothly. This gives you a great overview of what to adress and what to enhance. The other way of doing it is to go for the vision, map it out and backtrack what needs to be done in order to achieve the vision. Just remember to create the vision based on customer needs, and not on internal or sales goals.</p><p>(And naturally you can change purpose throughout the project. Often we find that companies use the two approaches interchangeably.)</p><h3>Talking to customers</h3><p>Think about where the customer start his/her journey? Usually, long before you have them inside your doors(!). Who do they talk to? What information do they search for? Where do they (try to) find it?</p><p>Create the customer journey from real insights. Talk with customers! Listen, and ask “why do you….?”, “how does that make you feel….?” and “why?”.</p><p>If you have the opportunity, do a service safari, or observe customers in real life. Some activities happens without us really noticing them.</p><p>Talk to customers both in recent and more past contact with your service. The experience can feel differently depending on time past.</p><h3>Creating the customer journey</h3><p>Include real customer quotes for most impact. The more specific the customer journey is, the more customer empathy you will build within your organization. Pictures? Great, add them too.</p><p>Add their experiences and feelings — (joy, excitement, frustration, relief…) This further builds customer empathy and understanding in your organisation.</p><p>Separate activities that occurs before, during and after using a service. Be specific. Making an online purchase for instance consists of multiple steps.</p><h3>Keep it alive and make it happen</h3><p>A customer journey is a living asset to help the organization offer the best service. Map out what needs to be done in order to create customer excellence. What is the vision, the current customer journey, obstacles to overcome? Remember to update it with your improvements and new customer experiences.</p><h4>All of these tips are circling around one theme — talk to real customers, do real-life observations. Customer excellence happens together with your customers.</h4><h4>If you want to read more about different types of customer journeys, we recommend <a href="http://kerrybodine.com/customerjourneymaps/">this article</a> by Kerry Bodine.</h4><p><em>Custellence is a dynamic customer journey tool that enables organizations to unite around customer needs. </em><a href="http://custellence.com/"><em>Try our beta.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37b6995551d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A prototype of change management]]></title>
            <link>https://medium.com/@Custellence/a-prototype-of-change-management-3044e32a431c?source=rss-fe90e577cea2------2</link>
            <guid isPermaLink="false">https://medium.com/p/3044e32a431c</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[Custellence]]></dc:creator>
            <pubDate>Wed, 11 Nov 2015 09:52:22 GMT</pubDate>
            <atom:updated>2016-01-29T15:07:29.463Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Custellence is a dynamic customer journey tool that enables organizations to unite around customer needs.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*lChbKSIWiMzappo7f011KA.jpeg" /></figure><h4><strong>Change is good. We all know that. But how do we approach and manage change in customer-centric organizations?</strong></h4><p>From user interactions with our clients we have understood that you all have a mixture of approaches. Some people work with change based on a greater vision, that describes where the organization aim to be and deliver on in the future, and then work step by step towards that vision. Other people start by identifying touchpoints that are working bad or suboptimal, and systematically work to remove sub and arrive at an optimal customer experience.</p><p>These approaches are often applied interchangeably, depending on your customer and business needs. We understand that, and have no preferences. Different situations require different tools. It’s all for the greater good of your customers and your business. However, there are some common denominators to change management regardless approach. Change management requires a shared understanding of what is going to happen, and the process to get there. It involves the inside of the company; both the change agents and the change recipients.</p><h3>Change management in Custellence</h3><p>So, how do we facilitate this in Custellence? Based on our users’ feedback, we have created a way of managing different change approaches in the customer journey map. It works both with a greater vision, and touchpoint-specific changes.</p><p><strong>How it works</strong></p><p>A customer journey consists of a number of activities. If we look at the activities from the perspective of change management, all activities have a status: They might be on their way out, on their way in, or they might just remain as they are. When working with delivering on a future scenario, all touchpoints are on their way in. To define the process to arrive at the vision, several intermediate customer journeys might be necessary, comprising a mixture of touchpoints of different status. When working with improving a customer journey, there will be touchpoints that are to be removed, and possibly new touchpoints to replace suboptimal ones.</p><p><a href="http://app.custellence.com/#/public/12810">See an example of the approaches here.</a></p><p><strong>What else is required?</strong></p><p>In any company setting, change is most often associated with a roadmap. Projects. Things to do. We don’t aspire to handle your project management, but we do believe you will want to see the change progress and accountability in Custellence. That is why we have created a process section, where information about who’s responsible can be added, possible relations to other projects and other information.</p><p>The change feature is an early prototype so please let us know what you think. Really. We do want to know, because our development process involves you at every corner.</p><p>How do you manage change? Share your stories with us at #custellencechange.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3044e32a431c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Done testing (customers as product owners)]]></title>
            <link>https://medium.com/@Custellence/done-testing-customers-as-product-owners-d9dd660d28ce?source=rss-fe90e577cea2------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9dd660d28ce</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[service-design]]></category>
            <dc:creator><![CDATA[Custellence]]></dc:creator>
            <pubDate>Fri, 03 Jul 2015 12:11:06 GMT</pubDate>
            <atom:updated>2015-08-11T12:48:29.737Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>or Co-developing digital services together with your clients</strong></h3><p>Co-designing services with clients and customers has become best practice in service design. However, digital services are often excluded from the early stages of co-efforts, and are instead subjected to user testing.</p><p>Whereas a co-design process focuses on developing and refining ideas together with clients and customers using curiosity and empathy, user testing is mainly focused on verifying concepts and functions late in the development process. It puts a prototype in the hands of the user to like or dislike, understand or not understand — but not answering the fundamental question. Will they use it? Or do they even need it?</p><p>By involving customers early on, you get to focus on doing and building the right services from the start. The process of developing a new (digital) service becomes much more cost efficient, because the service will be hitting the mark for your customers, truly creating value. But there is more. By involving your customers early on, they become natural ambassadeurs for the service. You can put less effort on persuading your customers to start using your service, because they have already built it together with you as they want it. And ingrained in your organization will be a natural customer-centric approach.</p><p>To start using a new service, a behavioral change is always involved. To avoid that your service becomes this fantastic piece of highway in the forest no one is finding or using, it’s essential to find out what is needed for your customer to change that behavior and start using your service. You need to understand your customer’s needs and incentives, by listening to them and letting them explain to you what the service should be doing. Those insights will help you figuring out what it is your customer truly needs and wants.</p><p>At Transformator Design we are currently co-developing a digital service together with our clients, <a href="http://www.custellence.com/">Custellence</a> (Customer Experience Excellence), a dynamic service map tool. The idea for the service came about when we understood that our clients was using our deliveries (service and customer journey maps) as a starting point for change implementation. They where asking for a tool that would allow them them to lead their organisation’s work of implementing customer insights, that would help them set priorities and road maps. What they wanted was a systematic approach to customer experience management.</p><p>So we started concepting and building <a href="http://www.custellence.com/">Custellence</a>, a platform for customer experience strategies and implementation work. A platform that facilitates a customer-centric company culture, and enables the organisation to reach customer experience targets.</p><p>We did so by asking them to explain. “Why do you need it?” What would the service do for you?” “How is that?” “Tell us more!” By analyzing the answers, we could draw a first rapid prototype. We showed other clients these simple sketches in order for them to develop the concept further, very much similar to the process we use in our service design projects. We always go through iterative cycles of customer interactions, insight analysis, idea generation and prototype generation, showing the prototype to a new set of customers and again gathering insights, analyzing them and generating new ideas for prototypes. After a number of cycles depending on the scope of the project, we reach a customer-centric definition and set-up of the service. What was unique at this point about Custellence, was that after a number of iterative cycles together with our clients, we had developed a high-end prototype that needed to enter our client’s organisations.</p><p>We selected a number of customer experience managers from client organisations (Arbetsförmedlingen (government), SJ (public transportation) and Landshypotek Bank (financial services)) to be our beta phase developers. It was important for us to call them developers and not testers, to emphasize the focus of their effort. Our clients themselves represented both small, mid-sized and large organisations that where either advanced or beginners in terms of customer experience. After a short introduction and equipped with a brief manual (and our continuous support), they got to use Custellence for six weeks. Every week we met with them to discuss ideas, thoughts, problems and needs; capturing their ongoing thoughts from using the system. After the development phase, we brought them all together for a gathering where we talked about not only the details of the service, but also business models, possible software integration and much more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*H2ldxwHYCiJaArHI." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*158iiQGgHtoZx-8m." /><figcaption>Closed beta wrap-up</figcaption></figure><p>The co-development phase with a beta service was extremely valuable to us. We understood that Custellence in its current form is best suited for organisations that have gained some experience in their customer experience management teams. We also discovered that Custellence was lacking some functions that could manage the need to track and prioritize implementation of customer experience strategies. Furthermore, our clients really appreciated coming together to be inspired and learn from each other. These were insights that we wouldn’t have gained with conventional user testing.</p><p>Next milestone in our development process is to release a public beta the 1st of October. Then everyone can participate in using and developing <a href="http://www.custellence.com/">Custellence</a> further. Do you want to co-develop <a href="http://www.custellence.com/">Custellence</a> or are you simply curious about our process or <a href="http://www.custellence.com/">Custellence</a> itself? Contact us directly at hello@custellence.com or talk to someone from the development team. You can contact me (Susanna) or Emma Lindahl, Maria Björklund, Olof Bendt and Anders Landström.</p><p>Do you want to share examples of other digital services that have been developed with the customer at the heart of the process, or do you want to share experiences? We would love to hear about them. Continue the discussion on Twitter, #custellence #beyondusertesting.</p><p>Susanna Nissar, Business Innovation, Transformator Design</p><p><strong>Update 11th of August 2015</strong></p><p>We will hopefully! talk more about this at SXSW Interactive! Vote for our proposal <a href="http://panelpicker.sxsw.com/vote/47101">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9dd660d28ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>