{"id":801802,"date":"2017-09-15T05:17:53","date_gmt":"2017-09-15T12:17:53","guid":{"rendered":"https:\/\/medium.com\/p\/8232c9e900ea"},"modified":"2017-12-26T17:52:11","modified_gmt":"2017-12-27T01:52:11","slug":"you-need-to-know-this-new-pioneering-approach-to-crm","status":"publish","type":"post","link":"https:\/\/customerthink.com\/you-need-to-know-this-new-pioneering-approach-to-crm\/","title":{"rendered":"You Need to Know This New, Pioneering Approach to CRM"},"content":{"rendered":"<p>I\u2019ve been working in and around <em>traditional<\/em> Customer Relationship Management (CRM) for over 20 years. As the Farmer\u2019s insurance guy says \u201cI know a thing or two, \u2018cuz I\u2019ve seen a thing or two.\u201d I\u2019ve been on a long struggle to understand my customers, and in doing so realized that the tools and platforms we\u2019re using need to be <strong>blown up and thrown out with the\u00a0trash<\/strong>!<\/p>\n<blockquote><p>No, I\u2019m not \u201creally\u201d\u00a0kidding<\/p><\/blockquote>\n<p>I started all this nonsense talk on <a href=\"https:\/\/medium.com\/u\/4d6070a6bd09\">Paul Greenberg<\/a>\u2019s ZDNet blog about 4 years ago in a post entitled <a href=\"http:\/\/www.zdnet.com\/article\/reinventing-crm-mike-boysen-says-its-time\/\">Reinventing CRM<\/a>. If you have time, I hope you\u2019ll have a read. I\u2019m ready to get more prescriptive than I was then. Well, some of that will need to come with another post for everyone\u2019s sake!<\/p>\n<h4>A Quick Look at CRM\u2019s Ugly\u00a0Past<\/h4>\n<p>Let\u2019s first identify the constraints that old-timers like me <strong>used as excuses for CRM project failures<\/strong> over the years. We need to get these out of the way since they\u2019re no longer\u00a0valid.<\/p>\n<ul>\n<li><strong>We had to manage a complex technology stack<\/strong>. Every time one of the many components of that stack (OS, hardware, 3rd party software, CRM) changed, there was a ripple effect that potentially (always) caused problems. Getting them installed properly in the first place was a feat in and of\u00a0itself<\/li>\n<li><strong>We had to custom develop methods to eliminate steps for our customers<\/strong>. This software was mostly plain vanilla. Since we didn\u2019t speak a common language, and many of the early consultants were accountants and salespeople bored with their careers, this was messy (I made some money fixing this kind of stuff over the years). Writing custom client-side code made it extremely difficult to integrate end-to-end workflows (cross-functionally) and typically ended up as a plate of spaghetti. I wore a bib to work some\u00a0days.<\/li>\n<\/ul>\n<p>Then there are the constraints that haven\u2019t changed, even in the age of the cloud (our\u00a0savior).<\/p>\n<ul>\n<li><strong>CRM platforms were (and are) designed functionally, which means the linkage between business groups is artificial and fragile<\/strong>. We\u2019ve made strides in the age of the cloud; but the pieces we are stringing together were not designed from the ground-up as an integrated architecture. They\u2019re pieced together from acquisitions; and we all know how that ends up going. I won\u2019t name\u00a0names.<\/li>\n<li><strong>Salesforce automation puts salespeople in the field where they can sell<\/strong>. Even if that\u2019s true, efficiency is not a growth driver. At best, it\u2019s an enabler. But, do salespeople (closers) actually spend more time in the field closing qualified prospects, or do they spend there time drumming up their own leads because the marketing team is driving junk to their\u00a0inboxes?<\/li>\n<\/ul>\n<p>We\u2019ve seen the evolution toward cloud-computing and it has been heralded as a major disruptive innovation. It was, but it disrupted the technology world, not so much the CRM world. CRM software looks fundamentally the\u00a0same.<\/p>\n<ul>\n<li><strong>The pitch is that CRM will make your marketing more agile because there is so much more data available<\/strong>. The truth is that marketers don\u2019t know what to do with the data they had, let alone a new pile of unstructured <em>big data<\/em> that\u2019s backward-looking and data scientists who will never find a way to predict much with\u00a0it.<\/li>\n<li><strong>\u201cHey Customers, you can configure it any way you like!\u201d<\/strong> Which is true, and one of the reasons large consultancies make so much money setting up Centers-of-Excellence once that fails miserably.<\/li>\n<li><strong>Mobile-first is a logical next step for cloud platforms; but that\u2019s just convenience and context<\/strong>. It gets people away from their desk. But, does it generate more qualified leads, or does it somehow help you understand your customers\u2019 needs better?<strong> No.<\/strong> It makes playing golf more convenient and guarantees more distractions while trying to build in-real-life relationships (the sticky kind of relationship).<\/li>\n<\/ul>\n<p>I\u2019m not going to drain this topic any further because deep down, we all know that <strong>more<\/strong> <strong>businesses <\/strong>(like yours), did <strong>not <\/strong>start <strong>growing more<\/strong> (which is what they want) because of some evolution of CRM technology. <strong>The vendors don\u2019t get it<\/strong> and you are the lucky beneficiaries <strong>who are not having your needs fulfilled<\/strong>.<\/p>\n<blockquote><p>New product launches continue to fail at the same rate, and will continue to do so. Regardless of what I say. It\u2019s inevitable. Sorry.<\/p><\/blockquote>\n<h4>Pioneering a New Way\u00a0Forward<\/h4>\n<p>OK. That last sidebar was a little harsh and disheartening. Let me try to frame this up a little bit differently for you. Here are the opportunities we should be seeking as businesses:<\/p>\n<ul>\n<li><strong>We want to find markets where there is real, tangible opportunity.<\/strong> In other words, we only want to invest our capital in initiatives that have a high probability of success. Those could be products, services or new business\u00a0models.<\/li>\n<li><strong>We want to minimize our exposure to wild-goose chases<\/strong> (products and services no one wants) or poorly design offerings (products and services people want, but which didn\u2019t properly or completely address unmet needs in the\u00a0market.<\/li>\n<li><strong>We want to make sure that when we unearth a winning concept in the market<\/strong> that product <em>designers<\/em> understand why it\u2019s a winning concept so they can design a winning solution.<\/li>\n<li><strong>Marketing, Sales, Fulfillment, Logistics,Training, Support, etc. also need to understand why<\/strong>, so they can each understand the language that resonates with their customers at the various life-stages where interactions between customers and the brand take place (<strong>call this the customer experience<\/strong>; but please note that if you don\u2019t get bullet one and two right, it won\u2019t\u00a0matter).<\/li>\n<\/ul>\n<p>The bottom line is that while the percentage of winning solutions probably won\u2019t change much, we have an opportunity to dramatically reduce wasted capital, and the amount of value-destroying messaging consumers must sift through on a daily\u00a0basis.<\/p>\n<blockquote><p>The focus of strategy and product development can move-on to the <strong>acceleration of innovation<\/strong> and not the iterative processes that waste capital and try to put lipstick on\u00a0failure<\/p><\/blockquote>\n<p>Imagine a world where the only messaging you received was relevant. Or, imagine a world where businesses no longer invest in product development that has an unknown outcome. If we could do either, or both, wouldn\u2019t it be a much better world? We could spend our time leap-frogging instead of fast-following and\/or fast-failing.<\/p>\n<p>Actually the percentage of successes would go up, just not the number of companies involved in them\u00a0\ud83d\ude42<\/p>\n<figure><img decoding=\"async\" alt=\"\" src=\"https:\/\/cdn-images-1.medium.com\/max\/1000\/1*i-Mo6QsDVeByKVgSuei2Kg.jpeg\" \/><\/figure>\n<h4>How is CRM helping us? Is it time to move\u00a0on?<\/h4>\n<p>One of things that I pointed out in my \u201cReinventing CRM\u201d piece is that vendors have given us a one-size-fits-all option <strong>where we can feel that we\u2019re differentiating ourselves<\/strong> with the same tools as our competitors. Let\u2019s face it, the vendors out there are doing no better at finding growth\u200a\u2014\u200aprofitable growth\u200a\u2014\u200athan the rest of\u00a0us.<\/p>\n<blockquote><p>So why do we keep hiring them? Profitable growth is what every business is after\u200a\u2014\u200agive or take\u200a\u2014\u200aright?<\/p><\/blockquote>\n<p>I then said\u00a0that\u2026<\/p>\n<blockquote><p>The context must shift from products, tools and features to a framework using a customer\u2019s job-to-be-done as its focal\u00a0point.<\/p><\/blockquote>\n<p>The reason I said this was simple: businesses are hiring CRM software to help them achieve their goal of <strong>sustained, profitable growth<\/strong>. Yet, we all know that this <strong>takes more than marketing, sales and support<\/strong>\u200a\u2014\u200aor do\u00a0we?<\/p>\n<p>As we\u2019ve cycled through all the new terms like Customer Experience Management (CEX), Customer Success, Customer Engagement, and Digital Transformation, we\u2019ve dramatically failed to see that while we have a lot of new toys, we aren\u2019t really accomplishing our long-standing goals.<\/p>\n<p>Can I share with you what I\u2019ve\u00a0learned?<\/p>\n<h4>My Journey of Discovery<\/h4>\n<figure><img decoding=\"async\" alt=\"\" src=\"https:\/\/cdn-images-1.medium.com\/max\/1024\/1*sXERBS-gXHRO-4kDWxFSjw.jpeg\" \/><\/figure>\n<p>I started my journey just over 10 years ago. I won\u2019t bore you with the details, but at one point I was writing highly technical blog posts about some cool stuff I had done with CRM software. It was cool for developers; but my passion had been migrating more toward customers and what they were <em>really <\/em>struggling with.<\/p>\n<p>I was encouraged to share this journey by Bob Thompson over at <a href=\"http:\/\/www.customerthink.com\/\">CustomerThink<\/a>. It was clearly my one-way journey and I haven\u2019t looked back since. It has been a rather lonely\u00a0journey.<\/p>\n<h4>I wanted to focus on what customers needed<\/h4>\n<p>I\u2019ve studied and iterated through many approaches to uncovering <strong>customers\u2019 needs.<\/strong> The realization that they didn\u2019t need CRM software took awhile to seep into my thinking. So, I was like everyone else, framing up needs bounded by the solutions we had to work\u00a0with.<\/p>\n<p>I enjoyed designing ways to make the user experience better; based on what I learned in interviews and observation. But there was still something extremely dissatisfying about it. Probably much like the dissatisfaction felt by whomever came up with Material Design. I mean <em>come on! <\/em><strong><em>How did that make my life\u00a0better?<\/em><\/strong><\/p>\n<blockquote><p>It didn\u2019t, and that shouldn\u2019t be the objective, either<\/p><\/blockquote>\n<p>Here are some baseline observations that you\u2019ll have to embrace if you\u2019re going to continue with my journey. <em>It\u2019s about to be like that first time you swallowed a non-candy-coated aspirin as a\u00a0kid.<\/em><\/p>\n<ul>\n<li><strong>Requirements are not customer needs<\/strong>. Neither are specifications, wants, desires, pains, delighters, benefits, etc. Any of this mish-mash of inputs must trace back to real customer needs; or they are just ideas, guesses, or contained within the boundaries of current solutions (product-centric).<\/li>\n<li><strong>Customer needs are not variables<\/strong>. They don\u2019t change over time. It is the <strong>unmet needs of today<\/strong> that will determine the <strong>successful solutions<\/strong> <strong>of tomorrow<\/strong>. If you don\u2019t know them, you\u2019re guessing and (statistics show) you\u2019re failing. Unmet needs are a subset of <strong>all<\/strong> customer needs, as are over-served needs and table stakes needs. This population rarely changes (unless context changes). This is no different in product development than it is in the implementation of CRM software; or so-called customer experience strategies.<\/li>\n<li><strong>All customer needs can be known<\/strong>. Customer needs are stable over time. They are directly related to a goal or objective of a customer; which is also stable over time. This objective is known as the customer\u2019s <strong>Job-to-be-Done<\/strong>.<\/li>\n<li><strong>To reliably create winning concepts in the market,<\/strong> you must understand the customer\u2019s Job-to-be-Done, the steps they take to accomplish it, and the metrics they use to measure\u00a0success.<\/li>\n<li><strong>Customer needs are in reality forward-looking customer success metrics<\/strong>. When developed and used properly (it only takes once) they provide a roadmap to predictable success over\u00a0time.<\/li>\n<li><strong>All aspects of customer success can be measured this way.<\/strong> This includes winning product and service concepts, winning concept designs, winning demand generation (messaging) and winning in the consumption chain jobs (what we typically label as <strong>customer experience<\/strong>).<\/li>\n<\/ul>\n<h4>So one day I found myself in this group of CRM\u00a0experts<\/h4>\n<p>I thought social media was a complete waste, but in the early days, I <em>did <\/em>have some time on my hands and took a dive. While it has continued to be a broader waste of time, it did help me network within the CRM community in ways that went beyond my current <em>partner channel <\/em>(that\u2019s systems integrator talk!).<\/p>\n<p>I was fortunate enough to be following my least favorite subject, Social CRM. I won\u2019t go into it. But, I did meet a great group of friends that mostly disagreed with me\u00a0:). I think we all agreed that CRM was not about software and that the vendors had hijacked the term. But, frankly, <strong>we were not all in agreement<\/strong> that the easy path was the worst path. I mean, we had careers to think\u00a0about!<\/p>\n<blockquote><p>I was searching for real answers (I told\u00a0myself)!<\/p><\/blockquote>\n<p>We all bantered about a lot and got to know each other, and then this <em>other guy <\/em>got invited into the group. He (and they) know who he is. He completely corrupted me, and it took me awhile to see that he had been on a similar journey (different starting points). Once I realized this, I took the <strong>red pill<\/strong> he offered and <strong>stayed in Wonderland to see how deep the rabbit hole\u00a0goes<\/strong>.<\/p>\n<figure><img decoding=\"async\" alt=\"\" src=\"https:\/\/cdn-images-1.medium.com\/max\/798\/1*EnNqxjvgYcgP3qcvceEeHg.jpeg\" \/><\/figure>\n<h4>And the Deep Dive\u00a0Began<\/h4>\n<p>What I learned was that I had been focusing on the wrong thing my entire career\u2026and so had nearly everyone else. Product and service concepts came from some mysterious land that I had never been to and knew nothing about. What I did know is that companies invested a lot of money in their attempts to find <strong>gullible buyers for what they <em>did<\/em>\u00a0offer<\/strong>.<\/p>\n<p>And with this desperate desire to sell their wares, they become victims of the vultures circling above: software vendors (who have something to sell), consultants (who have new phrases to say), and executives who wrap it all up into shiny resumes that turn into short-lived \u201cair biscuits.\u201d<\/p>\n<p><strong>There are so many moving parts to our world that it\u2019s extremely difficult to see what\u2019s really changing. <\/strong>What had to happen (for me) was a simplification to a point where I had a stable platform from which I could detect the change\u2026reliably.<\/p>\n<h4>Customer Jobs Are Stable Over\u00a0Time<\/h4>\n<p>I learned that customers have jobs they are trying to get done, and when doing so, they hire solutions. This is not a new concept, but in the rush to be relevant, people seemingly choose to change their language; perhaps in a reaction to the constant change going on in their peer\u00a0groups.<\/p>\n<blockquote><p>What they need is a means to determine when to lead, when to follow, and when to wave goodbye. After all, we are all trying to make the best choice, not simply the most popular\u00a0choice<\/p><\/blockquote>\n<p>To make these choices requires a stable platform and <strong>stable inputs into the equation of innovation<\/strong>. And lest you think innovation only happens in the \u201cInnovation Dept.\u201d, think again. We are all innovators. However, in the context of a business that is serving customers, everyone in the business needs to speak the same language of innovation. Otherwise our current world\u00a0happens!<\/p>\n<h4>Improvement Happens When We Help Customers Get More Steps Done on a Single\u00a0Platform<\/h4>\n<p>Think of a job as a process. If we (the job executor) are <strong>hanging a painting<\/strong>, there are things we need to do prior to hanging the painting, and there are things we need to do after we hang the painting. While there are many ways to go about hanging a painting, the job (as a process) does not change because it does not prescribe <strong>how to hang the painting<\/strong>. The job is a stable platform.<\/p>\n<figure><img decoding=\"async\" alt=\"\" src=\"https:\/\/cdn-images-1.medium.com\/max\/692\/1*EkdL-l4AHXOlCu2UrSe9xg.png\" \/><\/figure>\n<p><strong>Consultants map-and-gap all day long<\/strong>. While they are generally fixated on the constraints of a business process (how we do it) and technology (how we want to enable it), mapping is powerful because it provides boundaries. The boundaries make sure we don\u2019t wander; but just as importantly they help us ensure that there no holes in our logic. It\u2019s very easy to spot a step that has not been adequately addressed.<\/p>\n<p>So, improvement lesson number one focuses our attention on the <strong>job<\/strong>, not the <strong>solution. <\/strong>As a result, we will almost always find that <strong>different solutions<\/strong> are hired to get <strong>different steps<\/strong> done. Which leads us\u00a0to\u2026<\/p>\n<blockquote><p>If your solution helps a customer get <strong>more steps done <\/strong>than another solution, they will value your solution over the competitor\u2019s solution<\/p><\/blockquote>\n<blockquote><p>CRM Note: If customers hire your CRM software or services, which steps are they trying to get done in the job \u201cAchieve Profitable Growth?\u201d<\/p><\/blockquote>\n<h4>Improvement Happens When We Help Customers Get More Jobs Done on a Single\u00a0Platform<\/h4>\n<p>While the ultimate job for a CRM customer is highly likely to be <strong>Achieve Profitable Growth,<\/strong> that\u2019s a pretty broad scope. Too broad to be of use (but don\u2019t forget it). So, if we were to chunk this down we would look at jobs that are generally considered drivers for growth; such\u00a0as:<\/p>\n<ul>\n<li><strong>Acquire new customers\u200a<\/strong>\u2014\u200ahow do we target a market of interest, understand needs, identify winning concepts, design winning concepts, price it profitably, go to market successfully, etc?<\/li>\n<li><strong>Grow existing customers<\/strong>\u200a\u2014\u200ahow can we help customers get more steps done in their core job, or how can we help them get more, related jobs\u00a0done?<\/li>\n<li><strong>Retain existing customers\u200a<\/strong>\u2014\u200ahow do we ensure that we are continually the best solution, and how do we design and measure experiences that take place during the \u201cconsumption\u201d of our solution; e.g. purchasing, learning, using, maintaining, troubleshooting, etc.<\/li>\n<li><strong>Leverage existing customers\u200a<\/strong>\u2014\u200ahow do we encourage customers to talk about us and suggest our solutions to their friends and colleagues? How do we locate brand ambassadors?<\/li>\n<\/ul>\n<p>Now, these would only be some of the steps in <strong>Achieve Profitable Growth<\/strong>. There are far more boring steps that we must evaluate just like we did in <em>Hang a Painting<\/em><strong><em>. <\/em><\/strong>The point of it all is that there is a hierarchy of jobs, and such a hierarchy allows us to see two simple\u00a0facts:<\/p>\n<ul>\n<li>customers are trying to get many related jobs done,\u00a0and<\/li>\n<li>local optimization leads to global suboptimization<\/li>\n<\/ul>\n<p>Yes, I stole that from the process world. But it\u2019s true! If we make crappy products while focusing on improving our marketing capabilities; we\u2019ll be perceived as spammers. If we make marketing super efficient at generating leads that <em>Closers<\/em> don\u2019t value, our <em>Closers<\/em> will focus on generating their own leads. When this happens, marketing becomes a money pit, and sales doesn\u2019t close the high-quality deals they\u2019re expected to close\u2026because they don\u2019t\u00a0exist!<\/p>\n<p>Customers generally hire different solutions to get different related jobs done. Which leads us\u00a0to\u2026<\/p>\n<blockquote><p>If your solution helps a customer <strong>get more jobs done<\/strong> than another solution, they will value your solution over the competitor\u2019s solution<\/p><\/blockquote>\n<blockquote><p><strong>CRM Note:<\/strong> If customers hire your CRM software or services, which jobs are they trying to get done that are related to \u201cAchieve Profitable Growth?\u201d<\/p><\/blockquote>\n<h4>Please God, tell me he\u2019s not going into this Jobs-to-be-Done thing\u00a0again!<\/h4>\n<p>Well, lucky you. Since the focus of this is not on product innovation, or any other specific area of interest within the customer realm, I\u2019m not going to get <em>that<\/em> prescriptive here. I want anyone that reads this to come away with these simple truths (that can be improved):<\/p>\n<ul>\n<li>Software and technology vendors in the \u201cCRM\u201d space are falling victim to the innovator\u2019s dilemma. <strong>All of them<\/strong>. None of them can demonstrate their own consistent and profitable growth\u200a\u2014\u200amore than a few months or years\u200a\u2014\u200ayet will tell us that they are the answer to our wildest\u00a0dreams.<\/li>\n<li>There are <strong>emerging technologies<\/strong> that are <strong>starting to get it <\/strong>and will be become a layer of abstraction (where our current vendors will no longer be a distraction) designed to better understand customer behaviours: at least the what, when and how part of the equation.<\/li>\n<li><strong>There are still major gaps\u200a<\/strong>\u2014\u200asuch as our forward-looking capability\u00a0, <strong>the why<\/strong>\u2014 which can only be filled by new thinking; and I don\u2019t mean big data. I mean what I\u2019m talking about in this\u00a0post!<\/li>\n<\/ul>\n<h4>CRM\u200a\u2014\u200aif we decide to accept this term\u200a\u2014\u200ais more than the technology we have\u00a0today<\/h4>\n<p>The future of CRM is uncertain. There is a constant search for new terms as customers, vendors, analysts, consultants and futurists seek to be seen as different. But they keep cooking up the same stuff and serving it with a different sauce. Then they fight over definitions. We have no common language or capability to build the next, higher-order of solutions. Think of it as a standard innovation protocol.<\/p>\n<blockquote><p>Until we do, we will never make\u00a0progress<\/p><\/blockquote>\n<p>We need to stop looking backwards, understand what jobs customers are attempting to get done, and define the metrics they use to measure <strong>their<\/strong> success; not your company\u2019s success. You will never predict the latter until you understand the former. CRM solutions will never achieve their rightful place in history until they help us do\u00a0it.<\/p>\n<p>With such a system, and common language, we can then focus on successfully integrating\u2026<\/p>\n<ul>\n<li><strong>Strategy<\/strong>\u200a\u2014\u200aDefining markets around people trying to get a job done, and determining winning concepts for these\u00a0markets<\/li>\n<li><strong>Design\u200a<\/strong>\u2014\u200aCulling requirements that satisfy unmet needs in the market which drive concept designs that are guaranteed to\u00a0succeed<\/li>\n<li><strong>Build<\/strong>\u200a\u2014\u200aEnsuring that the product and long-term roadmap trace back to marketing understanding and the evolution of customer needs: from unmet, to met, avoiding overmet. Yea, and all that testing and QA\u00a0stuff.<\/li>\n<li><strong>Demand<\/strong> -Using the language and understanding of unmet needs an offering solves and educating the market to drive demand (Marketing)<\/li>\n<li><strong>Revenue<\/strong>\u200a\u2014\u200aAccelerating the demand and converting it into revenue efficiently; e.g. without introducing erroneous or conflicting language\u00a0(Sales)<\/li>\n<li><strong>Experience<\/strong>\u200a\u2014\u200aExtending the system to address customer interaction needs during the life-stages involved in owning a solution; including customer\u00a0support<\/li>\n<li><strong>Efficiency<\/strong>\u200a\u2014\u200aOnce an enterprise has been organized around a market (or markets) comprised of certain customers and the jobs they are trying to get done, optimization of the integration between functional groups can\u00a0ensue.<\/li>\n<\/ul>\n<p>That last one is where the vendors need to rethink things because <strong>CRM <\/strong>platforms will not look like contact managers anymore (and they still do!). Today we focus on functional efficiencies first, cross-functional efficiency next, and overall effectiveness never!<\/p>\n<blockquote><p>Oh, they talk about business intelligence, but it\u2019s really an obfuscation because they are just looking backward better than everyone\u00a0else<\/p><\/blockquote>\n<h4>The Journey is still continuing<\/h4>\n<p>I will continue to take what I\u2019ve learned and integrate it into the work I do each day. One day that could mean providing a more integrated link between strategy and discovery (business\/functional\/etc. requirements). The next day that could mean introducing a more meaningful approach to journey mapping. Other days it could be getting marketing and sales to work off the same playbook as strategy and product development.<\/p>\n<p>I\u2019m looking forward to the platform that gets more steps and jobs done that I know my customers are struggling with, and I\u2019ll gladly pay your ridiculous price when you get\u00a0there.<\/p>\n<blockquote><p>Side Note: Please don\u2019t send me literature or communications about your CRM product\u200a\u2014\u200ait doesn\u2019t do what I\u2019m talking\u00a0about<\/p><\/blockquote>\n<h4>Further reading that will will explain where I\u2019m coming\u00a0from<\/h4>\n<p>I\u2019ve based my thinking on a theory and approach that has evolved over the past 25+ years. It is used in many Fortune 500 companies; and unbeknownst to my clients, it has also been used with them as\u00a0well.<\/p>\n<p>Maybe one day our CRM vendors will stop doing what\u2019s right, and do what\u00a0works.<\/p>\n<ul>\n<li><a href=\"http:\/\/jtbd.one\/customer-centered-job-map\">The Customer-Centered Innovation Map.pdf<\/a><\/li>\n<li><a href=\"http:\/\/jtbd.one\/customers-fair-hearing\">Ulwick_Giving_customers_a_fair_hearing_MIT_Sloan_2008.pdf<\/a><\/li>\n<li><a href=\"https:\/\/jobs-to-be-done.com\/what-is-jobs-to-be-done-fea59c8e39eb\">What Is Jobs-to-be-Done?<\/a><\/li>\n<li><a href=\"https:\/\/jobs-to-be-done.com\/outcome-driven-innovation-odi-is-jobs-to-be-done-theory-in-practice-2944c6ebc40e\">Outcome-Driven Innovation: JTBD Theory in Practice<\/a><\/li>\n<\/ul>\n<p><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/medium.com\/_\/stat?event=post.clientViewed&#038;referrerSource=full_rss&#038;postId=8232c9e900ea\" width=\"1\" height=\"1\"\/><\/p>\n<hr \/>\n<p><a href=\"https:\/\/mikeboysen.com\/you-need-to-know-this-new-pioneering-approach-to-crm-8232c9e900ea\">You Need to Know This New, Pioneering Approach to CRM<\/a> was originally published in <a href=\"https:\/\/mikeboysen.com\/\">Effective CRM\/CEX through JTBD<\/a> on Medium, where people are continuing the conversation by highlighting and responding to this story.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I\u2019ve been working in and around traditional Customer Relationship Management (CRM) for over 20 years. As the Farmer\u2019s insurance guy says \u201cI know a thing or two, \u2018cuz I\u2019ve seen a thing or two.\u201d I\u2019ve been on a long struggle to understand my customers, and in doing so realized that the tools and platforms we\u2019re [&hellip;]<\/p>\n","protected":false},"author":6796,"featured_media":93334,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[128,84,107,14,117,9],"tags":[],"_links":{"self":[{"href":"https:\/\/customerthink.com\/wp-json\/wp\/v2\/posts\/801802"}],"collection":[{"href":"https:\/\/customerthink.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/customerthink.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/customerthink.com\/wp-json\/wp\/v2\/users\/6796"}],"replies":[{"embeddable":true,"href":"https:\/\/customerthink.com\/wp-json\/wp\/v2\/comments?post=801802"}],"version-history":[{"count":0,"href":"https:\/\/customerthink.com\/wp-json\/wp\/v2\/posts\/801802\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/customerthink.com\/wp-json\/wp\/v2\/media\/93334"}],"wp:attachment":[{"href":"https:\/\/customerthink.com\/wp-json\/wp\/v2\/media?parent=801802"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/customerthink.com\/wp-json\/wp\/v2\/categories?post=801802"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/customerthink.com\/wp-json\/wp\/v2\/tags?post=801802"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}