Archive for Value-Stream-Mapping
Lean Sales and Marketing, the Value Stream Manager
Posted by: | CommentsOverview: The Value Stream Manager is responsible for maximizing return on investment (ROI) through his particular value stream of customer identification, customer value, customer acquisition, customer retention and customer monitoring (Value Stream Mapping Customer Value). He translates this value stream and assigns it in conjunction with the team coordinator to particular teams similar to how a typical sales manager would to his salespeople. The VSM and the team coordinator will routinely evaluate the outcomes to determine best fit. The VSM may work with multiple teams for his value stream. The VSM has profit and loss responsibility for the product/service. The VSM represents the Voice of the Market, which may be thousands of individual clients, distributors, brokers and agents. As with Scrum’s product owner, the VSM has the final authority.![]()
Again building on familiar ground you may want to equate this position to the Product Owner in Scrum, the Champion in a Six Sigma Project, Product Manager in Marketing or the Value Stream Manager in Lean. The short summary of their responsibilities: They assume the business interest of the product, service or value stream. They are the product/service owners and are held accountable for the commercial success of the product/service.
In Lean Sales and Marketing, the Value Stream Manager is held accountable for their Value Stream that is described in the 5Cs of Driving Market Share; Customer Identification, Customer Value, Customer Acquisition, Customer Retention and Customer Monitoring. In addition, the VSM has profit and loss responsibility for the product. Different than a Product Owner in Scrum, the VSM does represent the needs of the client in a project but is typically in contact with the client through the project team. The lean sales team actually performs the activities with the customer.
The VSM interacts with the team offering the priorities and reviewing the results with the Team Coordinator at each control point. It is important to note that as in Scrum there are two important principles. During iterations, the sales team has complete autonomy and should only be interacted with through the team coordinator. The other similarity is that the VSM is the one and only one person who has the final authority.
The VSM will prioritize the backlog or the iterations in the marketing value stream. These needs are best expressed or written in the form of User Stories. Depending on the size and complexity of the organization, the Sales Team, the Team Coordinator and the Value Stream Manager may meet to discuss an iteration or an entire marketing cycle. During the meeting the user stories are prioritized and discussed by all involved in the process. The sales team then takes these stories and breaks them down into activities and create single, multiple iterations that may be completed in a linear or parallel fashion. When these stories are completed, a control gate review occurs where the results are accepted or rejected by the Value Stream Manager. The VSM, the Team and the Team Coordinator discuss improvements, the next stage or coordinate a handoff to another Team. This process should have a very strong focus on where the customer is in their decision making process and what the best way is to support them at this time.
Whereas the team concerns itself around the Voice of the Customer (VOC), the VSM must look at both VOC and Voice of Market (VOM). Following the 5Cs of Driving Market Share outline, the VSM must:
- Identify specific products/markets that offer organization best options for growth.
- Create a value model for each of targeted product or market.
- Clearly state the organization’s competitive value proposition.
- Identify the direction needed to enhance that value proposition.
- Monitor competitive value proposition.
The Value Stream Manager can be one person or an entire department. However, for the VSM to be effective, they have to have control over setting the priorities not only for the sales and marketing teams but many times for product development. Their decisions should be visible to the entire organization. As I like to put it, they hold the gold within the company: knowledge of both VOC and VOM. This visibility makes the role of VSM both demanding and a very rewarding one.
Related Information:
Identifying your Lean sales and marketing teams
What will your workplace be like in 2020?
What’s behind Collaboration and Value Networks?
SALES PDCA Framework for Lean Sales and Marketing
Improve your Sales Cycle, Work on your Feedback Loops
Posted by: | CommentsWhen I start talking about speeding up the sales cycle the initial reaction is that the sales cycle is controlled by the customer and there is just not much we can do about that. I usually counter with, most companies understand that there is an average sales cycle time and if we just agree that there is than there is room for improvement.
My next discussion point is asking, can you describe the typical sales cycle based on the decision making criteria of your customer. At this point, I am again met with resistance saying that they are all different. I once again counter with let’s just take empirical view of a well-known market segment or even if we have to a well-known customer who we would consider “typical.” I do not do this too intentionally classify a customer as average or typical but to establish a base line on how we respond to our customers’ needs. ![]()
With that being said, I next ask what the average deviation from the sales cycle is there and if there are common decision making steps that get added or subtracted when this happens. That highlights the variability and creates awareness on how little active management of the process is going on. Further discussion generates reasons for excessive wait times by both parties and considerable rework that we call “fine tuning”.
Why change this? In my experience, the longer the process the more likely the criteria will change as a result of other influences rather than the actual need changing. The length of time does not necessarily equate to a better choice. The choice is based on the conditions, the influencers, the knowledge and if the problem increases substantially. The objective is not to have the customer buy your product.
The objective is for the customer to make the best informed and knowledgeable decision possible. The fundamental goals of your sales cycle should be one of discovery, learning and adaptability with a shared responsibility for a successful outcome. Your ability to generate the required knowledge effectively and efficiently in your customer decision making process will ultimately make you the preferred supplier. The question of course is how do you do that?
In most cases, unless you have already mapped your process (Value Stream Mapping), you will have cycle times that are highly variable and more than likely long. Developing a more consistent pattern with less variability will allow sales teams and customers to develop a higher degree of trust in each other.
One way of reducing cycle time is to create faster feedback loops. First, take one of the stages of the customer decision making process and break it down into multiple loops or cycles. Prioritize the loops and define the work that needs to be done within the first cycle through the use of a user story. The result of this is that you generate fast feedback by offering the customer smaller parcels of information to see if you are on the correct path or gain buy-in of a smaller step of the process.
Early customer feedback results in a better focus on the problem. As a result less work is done on superfluous tasks and more work is done on the required objectives. Little waste is generated because the feedback is so quick that obvious deviations are discarded.
Faster feedback can result in increased quality. There are number of reasons for this. Shorter cycles result in better fit since the feedback can be gathered and applied frequently. Also, faster feedback means that the team can minimize the work required to meet the objectives. Less rework is required (you are constantly tweaking) and this is very advantageous when compared to large time consuming proposals that are many times generated.
Another advantage of this process is that you only do the iterations that are you are comfortable doing. You don’t have to start every task in order. The flexibility of being able to put off some decisions to the last possible moment does not distract from the overall objective. By doing other cycles first, you will have increased knowledge of the cycle that will add better definition to the most difficult tasks.
Putting order into your sales cycle you will find that most of the time spent before is waiting on decisions or task that others are doing. Wait time is significantly reduced because of the smaller cycles are much easier to complete and easier handoffs are created which may simplify the task of others.
Working on the basics, makes a difference. To improve your football team, you need to work on blocking and tackling. To improve your sales cycle, you need to work on your feedback loops.
Related Information:
The Role of PDCA in a Lean Sales and Marketing Cycle
The Little PDCA Sales Loop
The 7 step Lean Process of Marketing to Toyota
Marketing Kanban: Marketing Kanban
Value Stream Mapping
7 Habits, Getting Things Done and now, Personal Kanban
Posted by: | CommentsI started practicing and finding Personal Kanban an answer to many years of frustration in looking for a time management system that allowed me to manage it rather it managing me. ![]()
How I started with Kanban:
Each year, I take one subject matter that I am going to concentrate on. I started doing it many years ago when a friend of mine told me he took one president every year and read about him. He is getting to an age now that he should be getting close to finishing.
In the latter part of 2009, I had become intrigued by Kanban and how I could use it for managing work flow and especially work in process. Trying to use a Value Stream Mapping process with sales and marketing people was a huge hurdle that I could not get over. The theory of the Kanban was closely related to Value Stream Mapping and through the use of post-it-notes I simply transferred a Value Stream to a Kanban board. I assigned numerous values from a budget perspective to the number of clients/prospects in a pipeline and so on. People seemed to understand that approach must better. As a result, I made Kanban my 2010 project of the year.
I have to admit, I did not get as far with it as I wanted. I was unable to attend a David Anderson workshop or pick-up a Lean Software Kanban client but I was able to learn a great deal about it and further engrained it into my Lean Marketing teachings. In fact, my next book, Marketing with PDCA has a chapter on Kanban.
However, these efforts led me into working with it on a personal level and that is how I became familiar with the Personal Kanban teachings of Jim Benson & Tonianne DeMaria Barry co-authors of Personal Kanban. In fact, the podcast Kanban too simple To be Effective? with Jim Benson led to others.
David Anderson, author of the recent book, Kanban appeared on the Business901 podcast and added 50 minutes of Kanban discussion. David covered a lot of ground in this discussion and answered a lot of questions for me that his book raised. David is a thought leader in managing highly effective software teams. He is President of David J. Anderson & Associates, based in Seattle, Washington, a management consulting firm dedicated to improving leadership in the IT and software development sectors. Related Podcast: Kanban, could we call this podcast anything else?
Bandit Software is the maker of an electronic Kanban tools for Lean Software and Systems development teams called Lean Kit Kanban. Related Podcast: Lean Kanban lessons from a Software Developer
Eric Landes is an Agile Project Manager who has been using Kanban for software development since 2007. He has worked with Scrum, XP and other agile methods for over the past 5 years, and has been managing software projects for over 10 years. Eric has his own blog, Corporate Coder which can be found at http://EricLandes.com. He is also a frequent contributor to http://developer.com. Related Podcast: Scrum + Kanban = Agile Discussion with Landes
Though this was not directly related to Kanban, one of my favorite podcast all year was Creating Flow with Don Reinertsen. Don Reinertsen is president of Reinertsen & Associates, a consulting firm specializing in improving the product development process. I have followed Don’s writing for many years and recognize him as THE leading expert in the field of Flow. His writings are insightful, packed full of information and readable. When editing the podcast, I could not bring myself to cut hardly a word out of it.
Each and everyone gave me a deeper appreciation for Kanban and it has been a great experience. This Tuesday I will have Patty Bielderman of Layers of Love discussing how she uses her Personal Kanban in her Nonprofit and in a grade school classroom. The following week, I will host Pascal Pink and the discussion of his use of PK as a Strategic Collaborator.
Enjoy the Book: Personal Kanban by Jim Benson & Tonianne DeMaria Barry
Related Information:
Kanban Cadence
Marketing Kanban
Marketing Cycle

