Business901 Book Specials from other authors on Amazon

Thursday, October 31, 2013

Our Decisions Need to be Co-created

When we approach sales we typically think of how we will address the customer’s problem. What needs we need to address and how we will do this in an engaging way? We are in The Experience Economy says authors Pine and Gilmore. Though many of us dwell on the Experience Economy, I think we are moving past that at an accelerated rate. This movement has its foundation in Service Dominant Logic, where the fundamental belief is that value is co-created with customers. The value is in the use of the product or service. This type of thinking is awkward to many organizations. In my latest book CAP-Do: Connecting Demand to the Lean Supply Chain, I begin the journey discussing sales and marketing from a perspective of being systemic, emergent, and participatory.

My latest thinking has been a result of spending time with stakeholder and customer journey maps and building user personas. These processes have assisted me moving from inside-out thinking to an outside –in perspective. It also helped my clients build better customer experiences. What I realized working with customers was that many of common problems they encountered became rather standard to deal with and many even automated. When we addressed sales issues we found a striking number as either straight-forward or responding to “opportunities” we had little chance of winning. If you would like more information on my sales perspective, read the blog post, Lean Salespeople are Challengers, not Problem Solvers.

The world of sales is on the edge of a collaborative way of selling. We no longer can just sell to a customer; we have to understand our customers’ business and our customers’ customer’s business. This can be done through scenario planning and from a perspective of being systemic, emergent, and participatory or The Cap-Do process.

From the book ' target=_blank>' target=_blank>' target=_blank>' target=_blank>Solving Tough Problems, author Adam Kahane classifies problems. His definitions: 

  • A problem has low dynamic complexity if cause and effect are close together in space and time.
  • A problem has high dynamic complexity if cause and effect are far apart in space and time.

 

  • A problem has low generative complexity if its future is familiar and predictable.
  • A problem has high generative complexity if its future is unfamiliar and unpredictable.

 

  • A problem has low social complexity if the people who are part of the problem have common assumptions, values, rationales, and objectives.
  • A problem has high social complexity if the people involved look at things differently.

When any of the problems exist that are coded in red, they are fairly simple problems to address and most organizations know the answers and their preferred vendors. They may make a decision with preferred vendors or research other vendors just to confirm their decision (The dreaded request for proposal we often receive).

The other set of problems, not in red, we struggle with as organizations. They are often described as messy or wicked problems.  The latest inbound marketing programs that are “social” in nature fail to deliver. They are simply built from our old thinking of a marketing funnel, responders, and workflows. We guide and manipulate the customer down some arbitrary path to arrive at the correct (our) decision.

As Kahane says,

Simple problems, with low complexity, can be solved perfectly well—efficiency and effectively—using processes that are piecemeal, backward looking, and authoritarian. By contrast, highly complex problems can only be solved using processes that are systemic, emergent, and participatory.

We as an organization do not have solutions to problems of high generative complexity. They cannot be calculated in advance, in a journey map, based on our past thinking, but have to be worked out as the situation unfolds. Seldom are they miraculously worked out by “single experts” but rather by a team of highly involved people. A coalition or a team made up of customer(s) and vendor(s)  must accept the fact that there is not one right answer. It must emerge from doing or working towards the problem. Just as value is co-created in use our decisions need to be co-created.

We always equated the experience economy to a theater with actors being the customer facing people, the back stage the supporting cast and the audience the customer. I think that is a broken metaphor. A better metaphor may be a race team where the product/service is the car, and the driver (customer) is using it. The pit crew (vendor) is in constant communication and in support of its use. There is no backstage, we are completely transparent and, in fact, the customer’s own support might be part of the pit crew.

Do you have an analogy that might work?

Thursday, October 24, 2013

Stop Looking for Mister Right

They simply don’t exist. I see people building Persona after Persona targeting that Ideal Customer. The problem that exists is that ideal customers are few and far between. In a recent blog post, A Persona Board deserves a Place at the Table, I described creating User Personas from your existing customers and then grouping them into quadrants based on product/market fit or relationships. The purpose of this is not so much to learn about customers as it is to learn about yourself and your core capabilities.

A fun exercise once you have created customer (user) personas, you can segment them according to how they fit in the quadrants mentioned in the above post. Then start asking these questions and others you may think of.. 

Relationship Customers:

  1. Which customers buy from you because they dislike the relationship they have with your competitor?
  2. Which customers buy from you because they like the relationship they have with you?

Product/Service (I will only use Product going forward) Customers:

  1. Which customers buy from you because you have a better value proposition (price/function) than your competitor?

Relationship Prospects:

  1. Which prospects buy from your competitor because they like the relationship they have with your competitor?
  2. Which prospects buy from your competitor because they dislike the relationship they have with you?

Product Prospects:

  1. Which prospects buy from your competitor because your competitor has a better value proposition (price/function) than you?

Marketing is in the business of creating customers. If we want to create a customer, we must take a divergent view versus a convergent view. Most marketing schemes, funnels and all that stuff are great at telling you how to manipulate a customer through the process to create a buyer, but few of them tell you how to create targeted prospects. A simple process is to use existing Customer Personas and create Prospect/Competitor Personas based on Relationship or Product groups.

When we look at the existing differences, we start identifying key points that we can address to gain access to others. In the Lean world, we call these opportunities gaps. We identify these gaps, and create different scenarios on how to close the existing gaps. We seek to understand why prospects may or may not move towards a target.

When viewing this from a structural tension metaphor, we will notice resistance as we try to coerce the customer towards the new target or condition. See my blog post, A New Approach to Lean with Robert Fritz.. We will oscillate between these two positions unless we can find common agreement of purpose. I like using the Theory of Constraints Evaporating Cloud (How to See the Other Side of a Conversation) as the way to resolve the difference. If we can find an overall purpose that will become a shared understanding – it resolves the conflict, it creates an opportunity for us to give an opportunity for prospects to move from one particular state to a different (closer to our thinking) state. It is the shared understanding that must exist to create the change in state.

SD-Logic way to Partnerships

When I first started in consulting, I spent a lot of time going to network meetings in town. It was the thing to do at the time. What I came to realize is that everyone had a product/service for my customer. Few of my services fit their companies. So, what happened is that I had two choices. One, spend a lot of time selling someone else’s product/service with little return for myself. Two, stop going to network meetings and go find a customer. 

This is not meant as a slam on the other networkers. It is even common in the business world. We always see opportunities in how we can partner with others. Mostly on how they need our product/service. They are weak in the area we excel in. The reason most of the time it is not that they are weak or lack expertise; it is more about the energy they are willing to spend on that portion of their business. First, they have not found it profitable or second, they have not found enough demand for developing it.

We view other product/services as not competitive products, but complementary products. I always think that is BS - We are competing for not only the same wallet, but more importantly the time or resources to implement the process. Whoever has the greatest burning platform,and the easiest to implement is usually the winner. If you are depending on your new partners, to sell it for you, you may be mistaken. The time and energy will be spent on their product/service. In this case, few of your products/services are sold and market is a t best minimal or about the same amount you could have created yourself.

If we cannot lead our new partners into acquiring more customers (not retention and up-selling) with fewer headaches; we may not be a good match. I believe the power has to come from acquiring new market-share based on the new synergies. If it only about add-on sells, the efforts are typically very minimal. And with that said, I have not even discussed pricing strategies and how they have to fit in.

Many will say that I may have too many negative thoughts about this. However, I think on a larger scale it is why so many acquisitions struggle for success. Matches are difficult for small companies and large companies. I have found that the correct fit evolves more so than is created. We need the market to drive the synergy not try to create it. Look for partners that you find yourself having a coffee together at a customers. Find them in places where your product/service is being used. In this manner, the customer or market has created the synergy. I liken this to using Service Dominant Logic thinking. Your thoughts?  

Wednesday, October 23, 2013

Boundaries of Kanban

Markus Andrezak is speaking at the upcoming Lean Kanban Central Europe Conference (It is Hamburg, Germany, Nov 4-5, 2013) about Boundaries of Kanban - Disruptive Innovation. An overview of Markus’s talk sums up our conversation in the podcast quite well.

Lean Kanban Central Europe Conference: Kanban is fantastic in the support the flow of product development and self improvement of teams in that area. However, at each time the process defined through Kanban poses an impediment to work in the creative field. While Kanban may very well fit to work in the domains of product maintenance and iterative, feature by feature innovation, it does not support evolutionary or disruptive innovation. These types of innovation dip slightly or even more into chaos and are completely non linear processes which simply do not fit the Kanban board and process. The talk will show how to protect innovation from delivery and how to create the necessary level of communication between these areas w/o creating silos.

An excerpt from the podcast:

Joe: I've struggled when I’ve applied Kanban to sales and marketing because it is similar thinking, it is very non-linear. The way I view it is that it's not this linear progression as much as it’s an iterative circle within a certain column. That group could be always there until they come out of the loop somewhere. They could either go backwards or forward. Is that similar type thinking to what you have done or do you have a better way?

Markus: I think it's very interesting what you said because I had this discussion last week with the great guys of TLC Lab in New York, Jabe and Simon Marcus. They came up with the similar idea because they tried to use Kanban in the way that you described it.

What I said to them is that you can put that work on the Kanban board and put a container around it and just ignore that it’s on the Kanban board. What will still happen is that people will look at the container that’s protecting this design work from the production constraints so to speak and somehow feel like it has been a stranger on the board. Now you could have a very great company culture and everybody will tolerate that stuff on the Kanban board. On the other hand, if it's on the Kanban board the Kanban system should be helpful of this work otherwise you would not put it on the Kanban board.

Again, this process is completely non-linear and going on and on as you say, my question would be of what help word Kanban be for the designers and I think of no help. If you look at what's going on in the gaming industry, how they’re coming up with new ideas for the games is in very small prototyping teams which are not working in any method. Maybe Design Thinking or maybe Design Studios, but they’re not working on any development-like or production-like methodologies. Rather what they do is something which Toyota might call set base design, so highly parallel work in very small teams to come up with lots of new ideas for a similar problem. I think this is good but you can't organize it on a Kanban, at least not that it would help so you could do Kanban but I think it would be of no help for anybody.

About Markus: Markus Andrezak has been active in different contexts as Product and Development Manager for high traffic and high revenue web sites. During the last years his main focus has been transitions towards Lean and Kanban product management and development practices across his portfolio. With Arne Roock, he also co-authored 'Replenishment', a free eBook on Kanban. His Blog: Portagile and Twitter: @markusandrezak. You can find more information at his company website: http://ueberproduct.de/en/.

Tuesday, October 22, 2013

Lean Service Design Slidedeck

At the ASQ 2013 Service Conference, this week, I had the honor of giving a sixty-minute presentation on Lean Service Design. All the participants of my presentation received a CD that contained my Lean Service Design Program. This is the slidedeck from the presentation.

I also introduced CAP-Do (More Info) to the audience. CAP-Do is a systematic way to address the problems (pain) or opportunities (gain) from the use of our products and services.

Purchase the Lean Service Design Program!

Or, purchase the 130 page PDF for download, Lean Service Design

Sunday, October 13, 2013

Kanban Thinking with Andrezak

@markusandrezak aka Markus Andrezak has been active in different contexts as Product and Development Manager for high traffic and high revenue web sites. During the last years his main focus has been transitions towards Lean and Kanban product management and development practices across his portfolio. With Arne Roock, he co-authored ‘Replenishment’, a free eBook on Kanban. His Blog: Portagile and Twitter: @markusandrezak. You can find more information at his company website: http://ueberproduct.de/en/.

Markus is one of thought leaders of the Kanban Movement and is  speaking at the upcoming Lean Kanban Central Europe Conference (It is in Hamburg, Germany, Nov 4-5, 2013) about Boundaries of Kanban – Disruptive Innovation.

A written excerpt  from our conversation was posted last week, Boundaries of Kanban in Sales and Marketing.

Download MP3

Business901 iTunes Store.

Mobile Version

Android APP

Lean Sales and Marketing: Learn about using CAP-Do

Saturday, October 5, 2013

The Starbucks Way of Connecting with Customers

It is a lesson in strategic marketing that few books meant for that purpose can even come close. After reading, most of Joseph Michelli’s books, and doing a podcast with him several years ago, I concluded after reading Joe’s latest book, Leading the Starbucks Way: 5 Principles for Connecting with Your Customers, Your Products and Your People, that it is his best work to date.

From the forward of the book:

Each of Dr. Joseph Michelli's books offers a learning laboratory that's rich with examples from leaders as they address the aforementioned challenges and opportunities. They provide information, insights, and analysis on how leaders seek to create a high-performance organization that operates through the lens of humanity. This book demonstrates both the setbacks and the breakthroughs that the Starbucks leadership has encountered as it has attempted to position its products and people to deliver consistent, engaging, and loyalty-enhancing experiences.

Herve Humler
President and Chief Operations Officer
The Ritz-Carlton Hotel Company, L.L.C.

I have another compliment for Joe. There may not be a better interviewee that can make an interviewer feel that good about himself. At times, I had to remind myself who the “star” was. – My hat goes off to Dr. Joseph Michelli. 

P.S. When you find out Joe’s next book subject, you will be anticipating the arrival for the next two years.

Download Podcast: Click and choose options: Download this episode

or go to the Business901 iTunes Store.

Mobile Version

Android APP

Lean Sales and Marketing: Learn about using CAP-Do

Tuesday, October 1, 2013

Using Scenarios for Current Applications

This video does an excellent job of explaining Scenario Planning. The most common application of is for futuristic thinking and considering the different scenarios that may play out. In the video, it will comment on how this method is used in lieu of forecasting or maybe even when Predictive analytics, no longer work (Podcast,  The Power to Predict Who will...).

When you view this video take a different approach. Instead of looking at the limiting perspective of Scenario Planning for the future view it from a perspective of building Customer Scenarios along the Customer Journey. Instead of assuming a customer was going to react a certain way, we match them to the Scenarios that may happen as a result of being in this position.

 

If we view the Customer’s Journey as a Scenario Journey does that cause a different reaction? Would that help us to seek to understand first?