How to come up with a product that is truly unique

How do you come up with a product idea that the whole world is not already selling? This is an interesting question that I think every entrepreneur asks him or herself regularly. I don’t have the answer for it, but I can tell you something about how to end up with the answer.

Ban TechCrunch 
The first step is to stop reading start-up media. Any start up media! That’s over – period. These just promote Groupthink and turns your attention to products and services that everybody is already doing. This is why the world is flooded with instant messaging and photo apps and to-do lists.

Think of it as entrepreneur information detox. You need to get it out of your system. If you absolutely need to read something, read something that nobody else reads. I can recommend Kafka’s short stories, Thomas Tranströmers poems or Mike Tyson’s biography.

If you have special knowledge…
Do you know something that most other people don’t? Have you worked in a niche? If you do then think hard about how to leverage that knowledge for a product or service. Is there some problem that is frequent in this special area you know, preferably a problem that someone would pay to get rid of. If that is the case you have your first lead there.

If for example you work in a cinema you may have noticed that it is a problem to clean chairs quickly enough between showings if somebody spilled something. Maybe the solution is a special coating for the chairs, maybe a cover that can be changed.

A good example of a company that did this is Zendesk | Customer Service Software & Support Ticket System. Zendesk started from the founders’ working with customer support systems, which they found to be too complex and difficult to implement and use.

If you have no special knowledge…
If you don’t have any specialised knowledge, which is often the case if you are fresh out of school or have spent most of your youth playing Fifa, there are several options. Think about stuff that you absolutely wouldn’t like to work with. Stuff that would be really boring, disgusting or socially awkward. It should be something you would lie about it if you were telling about it on a first date.

Think along the lines of condoms for dogs, reading stories for senior citizens, avoiding sewage blockage or code review. Now come up with a product/service that would make this thing easier.

“But why would I do something I don’t want to do?” you may ask. The thing is that this is usually a good indicator of what other people think as well and that is where you have the opportunity.

One of my favourites in this area is the company The Specialists who employ people with autism to do tasks that others find tedious like testing. What is incredibly boring or difficult for other people is something they like to do. Another example is Coloplast who makes products for continence care. Essentially they just make plastic bags, but for a special purpose.

Go datadriven
Another option is to find some way to pick up on a demand that is currently not well served. It could be selling niche stuff on amazon, which can be amazingly lucrative (see this thread on Quora). There are even tools for discovering such opportunities like Jungle Scout (Jungle Scout makes product research on Amazon EASY). But there are also other general SEO tools that can give you the same effect like Moz.

Get out into the world..
Now that you have some vague directions you have to go out into the world to find out how to build a business model around this. This takes research about the users and customers, but also about competitors and suppliers. Strategyzer | Business Model Canvas is a good short hand for figuring out what to think about and where to go.

Lean start up, MVP etc…
I’m not going to go into more detail about this here. A quick search will flood you with quality material on how to build a product from an initial idea and turn it into a success.

Building a Product Strategy for a Backend Product

When you learn and read about product management you will quickly learn how important it is to engage with your customers, be agile and make experiments, but when your product is a back-end system with no end users, but just other applications and it is considered key infrastructure that others depend on to work in a predictable way, it is not so easy to be agile do A/B tests lean start up style experiments and user testing.
This is a classical problem and one very often ignored in product management literature. Here it seems always to be about products that have users that you can sit down and talk to and learn what to do. There are however a few things you can do if you are the product manager of a back end product and need to build a product strategy.


Align Strategy

It is necessary to sit down and look at all the consumers of your product. They are essentially your customers. That means identifying all other products that depend on or will depend on your product. Unfortunately product managers don’t always have a strategy. Then you need to look at other artefacts like road maps, visions, even marketing material. It is also a good idea to talk to them to understand where they are moving. Here you actually don’t need to concern yourself with the end users.

Once this is done find out what the strategy is for their product. Doing this may uncover some contradictory demands. One product may want you to focus on microservices another on batch deliveries another wants a message based architecture. Some may prefer REST/JSON type services, others SOAP/XML and others just FTP/CSV in a scheduled batch. Welcome to the world of Agile development where teams decide inside their own bubble what would be most agile for them.

Unfortunately it is your problem to reconcile these differences with the different consumers. In order to do this you need stakeholder management.

Manage Stakeholders

It is necessary for you to chart the different stakeholders and weigh their importance and actually do a typical stakeholder analysis where you find out what their interests are and how you should communicate with them. Unfortunately most product managers leave it at that and forget the art of stakeholder management. In the best case they will fill out a stakeholder analysis and store it on their harddrive never to be opened again. But stakeholder management is more like politics. Watch Game Of Thrones or House Of Cards for inspiration.
You have to understand the different fractions and their powerbase. Understand the different persons their culture. You have to lobby ideas, be the diplomat, explain the positions of other stakeholders. Look at key persons social network profiles in order to find out what type they were, where they live, what they do in their sparetime. Understand their concerns, apply pressure when needed and yield when it is necessary. Remember politics is all about compromise. But you can only do that once you have a plan.

Draft a plan

All the input you have got from the above points now has to be integrated with your own knowledge about the product. What are the possibilities, the technical limitations, technical debt etc? Given your knowledge of the status of your product and the possibilities and available resources you have to plan for how it should change. Draft a plan on a few headlines. Focus for example on capabilities you would like to develop, data you want to capture or ways of working with consuming products. Find out only a few key goals you have, but have suggestions for more.

Reiterate

Now, start over again, because product strategy, like any strategy takes time and you need to form a coalition behind it if it should succeed. You are not finished until you have that coalition behind you. Not until then will you have a proper product strategy.

Sensor Six is going open source

In 2012 I started my quest to harness the wisdom of crowds in decision-making. I felt that there was a tremendous unused potential in collaborative decision-making applications. Organizations typically had top down decision structures. That did not in all cases result in the best decisions. Research seemed to support that this is not the most efficient way to make decisions. Furthermore many organizations did not do this out of ill will, but rather lacked the proper tools to engage the wider organization in decisions. This is where the journey that became Sensor Six began; I wanted to find a way to tap this under-utilized source of collective intelligence.

With Sensor Six I started designing what an online tool that enabled organizations to engage the collective wisdom could look like. With the collective effort of the entire Sensor Six team we succeeded in building a sweet SaaS tool, if I may say so myself. It is only due to this team effort that Sirius Decisions featured us in the first-ever serious analyst report about product management tools in 2014.

Over the years we have learned so much from customers, partners and our competitors. The key learning that I think runs through these years is that everyone is doing product development in their own way. There simply is no best practice or any widely recognized process that everyone follows. We have very often heard that people felt there was a huge pain, when it comes to building the right thing and very often they felt that Sensor Six addressed that pain, if we could just change this or develop that…

Let’s face it; we can’t make a product tailored to each and every organization. So, instead of chasing after wind we have decided to let the wind chase us. Instead of developing each and every feature our customers need, we will now make it possible to do it by yourself. We have in short decided to release the source code, the result of thousands of hours of work, under the GNU General Public License on Github in the hope that the collective intelligence of the open source community can help us harness the decision power of the crowd.

When you think of it, it is a match made in heaven: our vision has always been to improve decision processes by engaging the wisdom of crowds. Now the crowds can contribute to improve Sensor Six and use it as they see fit.

It will still be possible to use Sensor Six for free at www.sensorsix.com in the standard version, plus we will provide hosting, support and professional services around the Sensor Six tool while also coordinating open source development initiatives.

In many ways I feel that I am back where it started in 2012 when I coined the first motto for Sensor Six: “Together We’re Smarter”

Kind Regards

Anders Lisdorf, Founder

Wyldstyle or Emmet? Lego lessons for product managers

This holiday season offered a chance for me to see the Lego movie once again. Since I had seen it once already, my mind, not so tied up with following the action and intricate plot, was free to see the deeper perspectives in the film and put it into a product management context.
At the core the movie is about two different ways of building with legos. On the one hand we have Emmet, the super ordinary, construction worker and his friends who always build according to issued plans. On the other hand we have Wyldstyle and the master builders, who build innovative new creations from what ever is available.
The master builders are the renegades, “the cool kids”, those that fight the evil president business. They are extremely creative and anarchistic. The prophecy of Vitruvius states that the chosen one, a master builder, will save the universe.
When Emmet becomes the chosen one, a certain friction arises because he definitely does not have much in way of creativity or innovation potential. But he redeems himself in the end, because he is able to make plans and have the everyone work as a team. He gets the master builders to work together to infiltrate the corporate offices etc.

Working as a team
So, what does this mean? we could generalise lego building to any kind of building and therefore also building software. There are two modes of creation: the heroic genius way of the master builder  or the dull plan based of the team. Just as in the movie, we in the tech industry celebrate the master builders: we cheer the work of the lone geniuses: Steve Wozniack, Linus Thorvalds, Mark Zuckerberg etc.
But just as Walter Isaacson’s latest and highly recommendable book “The Innovators” show, the geniuses NEVER made anything entirely by themselves. It was always as part of some sort of team effort.
Further, every day the wast majority of software out there is built by lifeless ordinaries like Emmet, who are just following plans. Maybe it is time for their vindication and time to take seriously that software development is a team effort. It is never the result of the mythical master builder and there is no prophecy that a chosen one will save the universe. The ability to work is just as important as being a genius.

Worth keeping in mind for the product manager
In practise there are three lessons we could learn from the lego movie
1) Don’t frown upon a plan. Even if it might be changed along the way, a plan is not a bad thing in itself. Agile development for example is often pitted against plan based development. There can be different kinds of plans like roadmaps, specifications or project plans. Following your gut and just jumping from sprint to sprint entirely on inspiration and a spur of the moment will not suffice. It will, metaphorically, only let you charge towards the front door, while a plan may take you all the way towards the top.
2) There is an I in team – it’s hidden right in the “A” hole. A team effort is a team effort, and if you can’t control your ego you are an A hole. It is  important to keep egos in check, because the power of a team will always be superior to that of any individual.  Most people are not geniuses, but that doesn’t mean that their effort is less worth. The entire team may loose motivation and coordination will diminish if egos prevail.
3) Master builders are great and necessary. It is from the individuals who dare think differently that new impulses come. Prototypes, drafts, wild ideas are the domain of the master builder. He or she is not sufficient, though a crucial source for innovation. It is therefore also necessary to allow room for the innovators in a team, but not so much that their ego takes over, but enough that they don’t wither and die.
As a product manager or any type of manager it is therefore important to keep these three lessons in mind: have a plan, keep egos in check and give room for the innovators.

Bloatware is a law of nature. Understanding it can help you avoid it

Today software can be churned out with an impressive speed, but few have stopped to ask the question of whether all the features they build were really necessary in the first place. Lean start up, Agile, Dev-Ops, automated testing etc. are frameworks that have made it possible to develop quality software  at impressive speeds. Are all the features they build really used by real users or were they just clever ideas and suggestions. Not too much research exists, but the Standish Groups CHAOS Manifesto from 2013 has an interesting observation on the point.

“Our analysis suggests that 20% of features are used often and 50% of features are hardly ever or never used. The gray area is about 30%, where features and functions get used sometimes or infrequently. The task of requirements gathering, selecting, and implementing is the most difficult in developing custom applications. In summary, there is no doubt that focusing on the 20% of the features that give you 80% of the value will maximize the investment in software development and improve overall user satisfaction. After all, there is never enough time or money to do everything. The natural expectation is for executives and stakeholders to want it all and want it all now. Therefore, reducing scope and not doing 100% of the features and functions is not only a valid strategy, but a prudent one.”

CHAOS Manifesto 2013 

20% of features are the most often used. It looks like the Pareto principle is at work here. The Pareto principle states that 80% of the effect comes from 20% of the causes. Many things have been described with it from the size of cities to wealth distribution  to word frequencies in languages. There has even grown an industry from it based on the bestselling book “The 80/20 Principle: The secret of achieving more with less” by Richard Koch. Other titles expand on this:  “the 80/20 manager”, “The 80/20 Sales and Marketing” and the “80/20 Diet”.

This could seem a bit superficial and you would be forgiven for thinking whether there really is any reality to the 80/20 distribution. It could just as well be a figment of our imagination, an effect of our confirmation bias; we only look for confirming evidence. Never the less, it seems that there is solid scientific ground when you dig a bit deeper.

The basis for the 80/20 principle
The Pareto principle is a specific formulation of a Zipf law. George Kingsley Zipf (1902-1950) was an American linguist. He noticed a regularity in the distribution of words in a language. He looked at a corpus of English text and noted that the frequency of a word is inversely proportional to its rank order. In the English language the word “the” is the most frequent and thus has rank order 1. It accounts for around 7% of all words. “Of” is the second most frequent word and accounts for 3,5 %. If you plot a graph with the rank order as the x-axis and the frequency as the Y-axis you will get the familiar long tail distribution, that Chris Anderson has popularised.

One thing to notice at this point is that the 80/20 distributions is relatively arbitrary. It might as well be 95/10 or 70/15. What is important here is the observation that a disproportionately large effect is obtained from a small amount of observations.

While Chris Anderson’s point was that the internet opened up for businesses opportunities in the tail, that is, for products that were sold relatively infrequent, the point for software development is the opposite, to do as little as possible in the tail.

Optimizing product development
We can recast the problem applying Zipf’s law. Take your planned product and line up all the features you intend to build. The most frequently used will be used twice as much as the second most used, and three times as much as the third most.

In principle you could save a huge part of your development efforts if you were able to find the the 20% features that would be used the most by your customers. How would you do that? One way is the lean start up way which is reaching mainstream. Here the idea is that you build som minimal version of the intended feature set of your product. Either by actually building a version of it or by giving the semblance of it being there and monitoring whether that stimulates use by intended users.

This is a solid and worthwhile first choice. There are however reasons why this is not always preferable. Even working with a Lean start up approach you have to do some work in order to test all the proposed features. That amount of work need not be small. Remember the idea of a Minimal Viable Product is just that it is minimal with regard to the hypotheses about its viability. Not necessarily a small job.

The Minimal Viable Product could be a huge effort in itself. Take for example the company Planet Labs. Their MVP was a satelite! It is therefore worthwhile to consider even before building your minimal viable product what exactly is minimal.

Ideally you want to have a list of the most important features to put into your MVP. That way you will not waste any effort on features that are not necessary for an MVP. The typical way this is done is for a product manager, product owner or the CEO to dictate what should go in to the MVP. That is not necessarily the best way, since their views could be idiosyncratic.

A better way
A better way you can do this is by collecting input on possible features to include from all relevant stakeholders. This will constitute your back log. Make sure it is well enough described or illustrated to be used to elicit feedback. Here you have to consider your target group and the language they use and the mental models they operate with.

Once you have a gross list of proposed features the next step is to find a suitable group of respondents to test whether these features really are good. This group should serve as a proxy for your users. If you are working with personas, you should find subjects that are similar to your core personas. Then you will simply make a short description of the intended product feature or even illustrate it, list the proposed features and ask the subjects in a survey or some similar fashion “If this feature was included in the product how likely is it that you would use it? On a scale from 1-5″

Once you have all the responses for every feature simply calculate the score by adding all the ratings they got. Then you can follow Zipfs lead and rank features from top to bottom. If you calculate the total of all scores you can find the top 20% features. Simply start with the highest scoring and continue until the cumulative score of features approaches 20% of the total score. It is still however a good idea with a sanity check, so you don’t forget the login function or similar (you can trust algorithms too much)

What to do
Now that you have saved 80% of your development time and cost, you could then use the effort to increase the quality of the software. You could work on technical debt, to make it more robust while you wait for results.

You could also use this insight in your product intelligence and look at the top 20% most frequently used features of your product. Once you have identified them optimize them so they work even better. That would be a short cut to getting happier customers. You could optimize response times for these particular features so the most important features work faster. You could optimize the visibility in the user interface, so they are even more easy to see and get to or you could be used the insight in marketing to help focus the positioning of your product and to communicate what it does best.

To sum up, product utilization seems to follow a Zipf law. Knowing the top 20% features could help you focus development effort, but it could also help you focus marketing effort, user interface design and technical architecture.

 

References:

Richard Koch: “The 80/20 Principle: The secret of achieving more with less

Chris Anderson: “The Long Tail

http://www.quora.com/What-is-the-deeper-physical-or-mathematical-logic-behind-the-pareto-principle-of-an-80-20-distribution

http://www.quora.com/Statistics-academic-discipline/What-is-an-intuitive-example-of-the-Pareto-Distribution

http://www.quora.com/Pareto-Principle/In-what-conditions-would-you-expect-a-power-law-distribution-curve-to-emerge

https://en.wikipedia.org/wiki/Feature_creep

https://en.wikipedia.org/wiki/Software_bloat

Photo by flickr user mahalie stackpole under CC license

 

 

is the Apple watch a Telegraph?

The coming of the Apple is the buzz of the moment. Apple is the champion of making things simpler, but have they gone too far with the apple watch and made it too simple.

One click bonanza

The received wisdom in new product development is that you should take out steps, and continually simplify the product. This is what amazon did with one-click and this is what apple did with [insert your favorite Apple product here]. The reason is that it increases usability.

But sometimes the simplification meets a point where it doesn’t improve usability any more. With any product you will have some measure of complexity. Complexity is conventionally conceived as the number of possible states the system can have. So, roughly a measure of complexity is the number of variables a user can choose between and the number of states they can assume.

Some products are the antithesis of the amazon One-Click. Microsofts office suite has heaps of functions that are never used. Other products like SAP have a lot of different screens with a lot of functions, which make them difficult to use. But the reason that these functions are there is often that users actually need these functions, so for them they are necessary. If you take a way that functionality you will make the user interface more simple, but the complexity of the task you wish to do remains, only now, because of the too simple interface, it is even more complex than it was before. This is what we could call residual complexity, that is, the complexity of a task that is not supported by the tool.

Let me give you an example of high residual complexity. We bought a dishwasher called something with one-touch (perhaps inspired by amazon?) where indeed there was only one button. Actually at the face of it good thinking: Simplify to the core of the problem. What do I want to do with a dishwasher? make it wash my dishes. That works very well. Under normal circumstances. That is, until I discovered after it had been installed that, it just didn’t work. Not much you can do with one button then. I called the store and they had me push some sequences on the button to do diagnostics. Suddenly I found that the dishwasher was stuck in Turkish language. A language I am not intimately familiar with. What to do when you have only one button?

Finally it was back to the original language and an operator came on site to fix it and it worked. Now we were happy until the dishwasher had finished its washing cycle. For some reason, the product manager or whoever was in charge thought it would be nice if the dishwasher played “Ode an die Freude” from Beethoven’s 9th symphony. I love that piece and especially the ode, but not when it is played in a  15 second melody sequence with clunky 8 bit soundgenerator and repeated three times. Now I wanted to turn it off, but what to do with only one button?

One click communication

To illustrate it further lets take the simplification to its extreme. Take a keyboard on a computer. It has about 50-60 keys. They can be on or off. That leaves us with a product with 100-120 different possible states (not counting combinations, since a keyboard records only one stroke at a time). If you would like to simplify this maximally you could introduce a One-click concept where the keyboard had only one key that could be on or off. We just reduced the complexity of the user interface with a factor of 100 or more popularly we made it a 100 times more simple.

That, however, has been done centuries ago (literally). It’s called a telegraph. The telegraph illustrates clearly the problem of residual complexity, because in order to carry out the necessary tasks with a telegraph (communication) where there is only one button, it shifts the complexity from the user interface to the task: you need to learn morse code in order to use it!

That means when there is an inherent task complexity you cannot simplify the user interface beyond a certain point if the goal is to increase usability.

Residual complexity and the Apple watch

Now let’s return to the Apple watch. As compared to a watch, the Apple watch is not more simple. Quite the contrary. On the other hand compared to a smartphone it is simpler. And many, including Apple compares it to exactly that. You can do many of the same things on the Apple watch as you can on the iPhone.

For example you can read and reply to messages only, there is no keyboard. So, if you want to reply you have to choose a preconfigured reply or dictate a reply.

You can read an email there, but if it is longer than a short message you will have to scroll incessantly. You can also listen to music, but what if you want to search for a song? You can look at my calendar, but what if the entry is more than 15 characters or you want to move an appointment?

All of these examples are examples of residual complexity. Could it be that Apple just made it too simple? Could it be that Apple just built a new telegraph for your iPhone?

 

Photo by Clif1066 @flickr under CC license

Product Management Maturity And Tool Support

A recent report on product management tools by Sirius Decisions has revealed that 50% of Product Managers are looking for product management specific tools.

There are a number of dedicated product management tools, such as those surveyed by Sirius Decisions, yet when you ask product managers only 13% seem to use such tools. What can be gleaned from another survey,  by Product Hunt  is that no dedicated product management tool seems to be on the radar of product managers. At first I thought it was a mistake, so I contacted Product Hunt to verify. The method they arrived at their list was the following

We came up with the PM tools list by polling leading product managers in the industry and that’s what they selected

Being the supplier of one such dedicated Product Management Tool, we wanted to dig deeper into why there were such discrepancies in the market. Looking at the list by product hunt, the tools are all generic tools or for some single purpose, but none were used for supporting a coherent product management process. At least not such as described in the reference models of AIPMM, ISPMA or similar industry standards.

In the ERP space there are numerous tools that cover for such industry standard processes like Procure-to-Pay or campaign management. So, why don’t we see more tools that support a best practice process, but only tools for either very generic purposes (Trello, Evernote or Excel) or very specific purposes (like KISSmetrics, Streak or Do)?

Maturity

I believe that the reason has to do with maturity. The maturity level a company has is a fairly good indication of what tools will work. If you want to implement SAP in a CMMi level 1 company it is going to be a tough ride, since SAP is wonderful for repeatable processes, and at level 1 you don’t have such. Conversely if you want to implement project management in a CMMi level 5 company with only trello, it might also be a hard sell.

The CMMi model is both loved, hated and misunderstood. Anyhow, given the right understanding and appropriation, I think it is a good framework for conceptualizing maturity.  We have to remember that it is not about any particular process, but a metamodel that stipulates something about the proces that you should follow. therefore it is not a competitor to the ISPMA syllabus or the AIPMM PRODBok. Rather these are particular ways of executing product management process.

Product Management is covered by the Development process in the CMMi model called CMMi-DEV and it should therefore be possible to single out process areas and look at what sort of tool support that fits. In the following I will go through the 5 maturity levels of the CMMi model and describe key processes and give recommendations for optimal tool support.

Level 1 – Initial (Chaotic)

It is characteristic of processes at this level that they are (typically) undocumented and in a state of dynamic change, tending to be driven in an ad hoc, uncontrolled and reactive manner by users or events. This provides a chaotic or unstable environment for the processes. As the CMMi-DEV says:

“Maturity level 1 organizations are characterized by a tendency to overcommit, abandon their processes in a time of crisis, and be unable to repeat their successes.”

There are no particular process areas pertaining to Level 1.

Tool use: Eclectic, Usually Microsoft office suite (Excel, Word, powerpoint)

Recommendation: Select one key part of the product development process to support with a tool (idea management, Bug fixing, development, planning). Find one central place and tool to document. The tool should be tactical and “light weight” and easily customizable

Examples: Trello is light weight and will fit for almost any work proces where you have work items (ie. tasks, features, userstories) that go through phases. Podio is another popular tool where the strength is in its customizability. There are plenty of Apps where one is guarantied to come close to your needs and then you can just adapt it. Uservoice is good if you want to manage the ideation process. Zendesk is for support and will be great if your primary pain is to address and fix users problems.

Level 2 Repeatable

It is characteristic of processes at this level that some processes are repeatable, possibly with consistent results. Process discipline is unlikely to be rigorous, but where it exists it may help to ensure that existing processes are maintained during times of stress.

Here is what the CMMi writes about Level 2:

“Also at maturity level 2, the status of the work products are visible to management at defined points (e.g., at major milestones, at the completion of major tasks). Commitments are established among relevant stakeholders and are revised as needed. Work products are appropriately controlled. The work products and services satisfy their specified process descriptions, standards, and procedures.”

Key Process Areas:

  • PP – Project Planning
  • PPQA – Process and Product Quality Assurance
  • REQM – Requirements Management

Tool Use: Usually one tool is used for part of the process, but often you will see differing tools across different departments in the organisation.

Recommendation: Converge on a common tool to use and focus on lowest common denominator across the people involved in the process. The most important here is that it should be possible to see the status of work products.

Examples: Jira is already used by millions and very good for assuring clarity regarding what is committed and the status of work products, Rally and Version One are similar and flexible. These tools are all good for the above mentioned process areas.

Level 3 – Defined

It is characteristic of processes at this level that there are sets of defined and documented standard processes established and subject to some degree of improvement over time. These standard processes are in place (i.e., they are the AS-IS processes) and used to establish consistency of process performance across the organization.

“A critical distinction between maturity levels 2 and 3 is the scope of standards, process descriptions, and procedures. At maturity level 2, the standards, process descriptions, and procedures can be quite different in each specific instance of the process (e.g., on a particular project). At maturity level 3, the standards, process descriptions, and procedures for a project are tailored from the organization’s set of standard processes to suit a particular project or organizational unit and therefore are more consistent except for the differences allowed by the tailoring guidelines.”

Key Process Areas:

  • DAR – Decision Analysis and Resolution
  • PI – Product Integration
  • RD – Requirements Development
  • RSKM – Risk Management

Tool Use: Usually a suite is used for a part of the process. And use of this is consistent across different departments.

Recommendation: Make sure the tool you have selected is a suite that is tightly integrated with up stream and downstream processes, because when you begin to reap the benefits of being at Level 3 you will usually want to expand the process reach. This is best done if it is already a suite.

Examples: Focal Point is often used for RD and RSKM and is very customizable. Sensor Six is aimed towards DAR and therefore worth considering if you want to focus on that process area. HP Quality Center, Rational Suite are sort of all round and has extensive functionality to support most processes.

Level 4 Quantitatively Managed

It is characteristic of processes at this level that, using process metrics, management can effectively control the AS-IS process (e.g., for software development ). In particular, management can identify ways to adjust and adapt the process to particular projects without measurable losses of quality or deviations from specifications. Process Capability is established from this level.

“A critical distinction between maturity levels 3 and 4 is the predictability of process performance. At maturity level 4, the performance of projects and selected subprocesses is controlled using statistical and other quantitative techniques, and predictions are based, in part, on a statistical analysis of fine-grained process data.”

Key Process Areas:

  • OPP – Organizational Process Performance
  • QPM – Quantitative Project Management

Tool Use: Consistent and mandatory use of a suite for the entire process

Recommendation: Make sure the tool supplies full fledged reporting facilities out of the box and customizable. Visualization is key to success here, because metrics that are not easily visualized are not going to help managemen.

Examples: same products as Level 3, but it is probably necessary to boos reporting: Qlikview, Mixpanel, Gekkoboard are good for visualizations of process trends, but if you need more sophisticated statistical analysis, SPSS, SAS or Rapid miner, to mention an open source alternative, are good options.

Level 5  – Optimizing

It is a characteristic of processes at this level that the focus is on continually improving process performance through both incremental and innovative technological changes/improvements

“ A critical distinction between maturity levels 4 and 5 is the focus on managing and improving organizational performance. At maturity level 4, the organization and projects focus on understanding and controlling performance at the subprocess level and using the results to manage projects. At maturity level 5, the organization is concerned with overall organizational performance using data collected from multiple projects.”

Key Process Areas:

  • CAR – Causal Analysis and Resolution
  • OPM – Organizational Performance Management

Tool Use: The requirements for the tool at this level is that it is “intelligent” and will supply the process with transformative input that is not realized at any earlier levels. It could be intelligent estimation or market analysis.

Recommendation: There are no tools at this level yet, so either it should be integrated with general AI systems or dedicated niche players

Examples: IBMs Watson is an interesting new general purpose AI, that could oprobably be used here. Another example is Qmarkets who supply prediction markets, for improving project delivery by using market dynamics. Employees can “gamble” on what projects or products will succeed.

 Conclusion

There are many options for tool use and many options for process improvement. The best thing is to be very selective and start from the process side. Tools with out a process are like hammers without a nail: they can make a lot of noise. When you know what process areas to focus one you should try to find a tool that suits this area and the maturity level you are aiming for. The tools are all good, but they are built for a particular purpose, so if you use it for something different the result may lack.

 

 

The 60 second business case

We all know the situation: The product manager has multiple inputs to a decision on what product ideas to work on: There are internal stakeholders, the customers, but there are also the market situation or technological developments. The sources of ideas are innumerable, but deciding which to go with often comes down to the HIPPO (HIghest Paid Person in the Office). So, we want to make a more sensible way of deciding which ideas to go with. This is the purpose of Jason Brett’s 60 second business case. You can see Jasons great presentation here:

In the following we will give a quick run through how you can do it yourself in a series of steps.

List the ideas

The size of the idea should be pretty big, not a new feature enhancement like change the style on submit button, but more like “allow import from LinkedIN”. For this demo we will just use Jason’s own:

  • CRMi Rewrite
  • Universal Behavior
  • Enhanced Send Experience
  • Content Creation/WYSIWYG
  • Smart Content
  • Calendar

We don’t know exactly what they refer to but it is clear that it is something substantial that you can’t just do in a couple of hours.

Define your criteria

Here we will just go with the criteria that Jason uses because they are great and very illustrative, but it is of course possible to choose your own since it may differ a lot what is important. For illustrative purposes let’s go through them.

Strategic Alignment. Keeping the product aligned with the existing strategies is always important. Here is how you could rate it on a 5 point scale:

5 – Meets all three of the following:

  • Company Mission
  • Moves Toward Product Vision
  • Correlates to at least one of the specific Strategic Objectives (or  quarterly/annual Goals) as defined by the leadership team

3 – Meets two of the above criteria
1 – Meets one of the above criteria
0 – Meets none of the above criteria.

 

Operational Necessity. Some things you just have to do to stay in business.This is what we evaluate in the dimension Operational Necessity:

5 = Yes – Must Have

  • Something we must do to remain in operation
  • Mostly driven by architecture or operations

0 = No – Is not a Technical or Operational Necessity

New Revenue Impact. Revenue is always important, so somehow gauging the potential for new revenue is a smart thing to do when you evaluate new product ideas.

5 = $1MM per year (or more) of attributable revenue impact
3 = $250K – $1MM per year of attributable revenue impact
1 = Revenue impact expected, but cannot or need not be quantified
0 = No expected revenue impact

Obviously the figures will differ depending on the size and situation of the company, but decide some figure that makes sense.

Retained Revenue Impact. Keeping your customers satisfied and coming back is another way of securing revenue. We can define it along the lines of the new revenue impact criterion, since it is just a mother source for revenue.

5 = $1MM per year (or more) of attributable revenue impact
3 = $250K – $1MM per year of attributable revenue impact
1 = Revenue impact expected, but cannot or need not be quantified
0 = No expected revenue impact

Improve Customer Experience. Keeping the customer experience high is a goal and should be a goal for most tech companies. We can rate the degree to which an idea improves the customer experience along these lines:

5 = Positive experience or satisfaction impact to at least 80% of our customer base
3 = Positive experience or  satisfaction impact to at least 30% of our customer base
1 = Positive experience or  satisfaction impact to a fairly small percentage of our customer base (less than 30%)
0 = No expected impact to experience or  satisfaction

Innovation Value. Being innovative is an imperative for most tech companies, so evaluating how innovative an idea is should be an important part. It is not that simple to say what is or is not innovative, so one suggestion is to look at it this way:

5=  Meets all three of the following:

  • Early (or First) to market with a feature or capability
  • Has high visibility (PR, Marketing or “Buzz”) Value in the marketplace
  • Has a new and positive business impact for our customer

3 = Meets two of the above criteria
1 = Meets one of the above criteria
0 = Meets none of the above criteria

Lowers Cost. Everybody wants to lower costs, so naturally an idea that could lower the costs o should be appreciated as well.

5 = $250K per year (or more) of attributable cost savings. Development/maintenance cost, support, operations, licenses, etc.
3 = $50K – $250K per year of attributable cost savings
1= Cost savings expected, but cannot be easily quantified
0 = No expected cost savings

Again the cost thresholds will vary depending on the size and situation your company is in.

PM Priority. The last criterion may be the most important. This is the art of product management, the subjective gut feeling of the product manager. This is sometimes the only factor when you don’t do any structured prioritisation, but it is a good thing to make transparent.

Weigh the criteria

All these criteria seem important and worthwhile, but they are clearly not equally worthwhile. So somehow it is necessary to weigh them. The exact process of ascertaining such a weight is not described, but the end product should be a percentage point where the weights all add up to 100%

Typically management will be interested in setting these weights. Is it for example more important to create new revenue or hold on to existing? Is customer experience more important than Strategic alignment? these are tough questions, so tough that only a manager can answer them.

If it is not possible to get input on the weights the product manager can serve as a proxy, because he or she will usually have a pretty good feeling for what the priorities are.

Rate the ideas

Now that we have established a list of great ideas, the criteria we want to evaluate them on and how to weigh them, we just need to, well, rate the ideas! The trick here is to have as firm a group as possible for your ratings not to lapse into total subjectivity. Luckily Jason did a great job defining what the different ratings should be given to, so it should be no big problem to do it.

There will still be room for subjectivity which is why it may be an idea to involve some others, wither to give the ratings or to discuss the ratings back and forth. This will dampen the biases of the PM.

Review your list

Now you have a list that is the closest to an objective basis for deciding which ideas to work on. This list should be the starting point of a more informed conversation about what to do.

This is a great way to quickly get an overview and it is fully supported by Sensor Six’ software. Here is an account that features the above example.

Username:  60SecondDemo

Password:  u(m,Y54€l

When Choice Is A Bad Thing – The Marginal Utility of Choice

Being able to choose between different options is a good thing for the user! right? but when you can choose between 65 different kinds of blue, 1122 different fonts and whether a display should only work on Sundays between 11 and 12 for a special group, giving MORE choices to users start to be not so good or, to put it bluntly: bad!

In general most are brought up in a democratic state, where expecting to have a choice is as basic as eating or breathing. This is why choice in all its guises has a positive ring to it. But there are actually situations where limiting your choice is the best strategy. It has worked for artists and musicians to enhance creativity, but it also works for ordinary people. This is important to consider when you are designing and building new products.

 

The marginal utility of choice

In order to understand why and when more choice stops being a good thing I will introduce the concept The Marginal Utility of Choice: “The marginal utility of choice is the perceived benefit that the option of one more choice will offer”.

Let us look at an example. If your product is a car rental service, then increasing the choice of color of cars from 1 to 2 may be a significant increase in utility for the user. Now you can suddenly choose whether you want the car in black or white. Adding blue will also offer great utility. Continuing to do this will continually add some utility to the car rental service as a whole. But when you already have, say, 35 different colors to choose from how much will adding color number 36 improve the utility of the service as a whole?

This example shows that it is not a linear function, that is, adding one more choice will not indefinitely result in the same increase in utility. In the following I will offer a posible explanation based on human psychology that could help explain when having more choice stops is a bad thing.

 

The optimal number of choices

In general the value of an extra choice increases sharply in the beginning and then quickly drops off. Given the choice of apples, oranges, pears, carrots and bananas are great, but when you can also choose between 3 different sorts of each the value of being offered year another type of apple may even be negative. The reason for this phenomenon has to do with the limits of human consciousness.

1-7 

In order to make a conscious choice there is one fact we know with Cartesian certainty: you need to be conscious about it. From half a century of psychological research starting with the seminal article by George Miller from 1956 “The magical number 7, plus or minus 2” we know that our consciousness has some severe constraints on how many things it can work with. It seems to be able to maximally hold 4 to 7 items at the same time (depending on the type of test and training). When the number of choices exceeds 4 to 7 items you can’t hold it in your consciousness anymore and the choices can’t be evaluated against each other. Therefore the marginal utility of choice quickly stops at the other side of 7.

I once got into a discussion with Chris Anderson (author of “The Long Tail”) about this observation. I argued that companies that offered only a very limited number of choices of products and functions of their products would be more successful, contrary to Anderson’s argument that the long tail and infinite choice was the way to go. We never really reached consensus on that though, but consider the following:

How many different phones does the worlds leading phone manufacturer, Apple, produce? 4, iPhone 6, iPhone 6 Plus, iPhone 5s, iPhone 5c

How many different choices does the worlds best restaurant offer their customers? 3 choices: 1 menu, a wine menu and a juice menu

How many car models does the worlds most hyped autoproducer, Tesla Motors, offer to their customers? 2, Model S and Model X

All of these leave the consumer with a number of choices that is below the threshold of our consciousness.

Expressed more formally we can stipulate that “the marginal utility of choice rises sharply between 1 and 7 choices and then decays”

7-49 

Now the question is “what happens after that?” When choice cannot be held inside consciousness, it will try to group them into different segments. That could work well to some point probably around 50 (7 chunks time 7 choices). In this interval a new choice can still be grouped with others with some effort, but it will take mental effort to understand and compare it to all the other choices. This is why adding a new choice will be a bad thing, since it is cognitively costly.

In this range the marginal utility of choice is slightly negative, because the added mental burden of yet another choice detracts more than the utility of it.

More than 50

After about 50 everything will just be a blur because the possibility of comparing it to all the other choices has broken down in our consciousness.  So, adding another choice will not make any difference. The marginal utility of choice is zero.

This means that the aggregate utility might even fall below zero some and then stabilize. This means that if you keep adding choices there might come a time where the utility is lower than having no choice.

 

The marginal utility of choice curve

Please keep in mind that this is a hypothesis, that is based on theoretical observation and some, albeit anecdotal, empirical evidence. I think it aligns well with a lot of observations, but it should be tested more rigorously.

We can now draw a function for the marginal utility of choice. It looks something like the above

We see that the total utility rises sharply in the beginning, we can call this “The climb to enlightenment”. This is the section where adding another choice gives the most marginal utility until the it approaches zero. The curve then evens out and decays which we could call “The slope of attrition” where adding another choice reduces the perceived benefit. The marginal utility of choice is below zero, which means that every new choice added decreases the aggregate utility of the service. The reason is that each new choice adds cognitive friction. Finally it will stabilize “This we can call the plateau of indifference”, this could be above or below zero, because having a lot of choices could very well be more frustrating than having none at all.

 

Case study – SaaS pricing models

It would be interesting to see if we could see this in real life. Let’s examine the case of Software as a Service pricing. SaaS companies live from selling subscriptions. Usually the user can choose between several different plans. This is obviously a case where the number of choices is important. If it were true that there is an optimum of choice between 1 and 7 we should be able to see this in how many tiers are actually offered.

In an excellent report by Price Intelligently “The SaaS Pricing Page Blueprint”, the authors studied 270 SaaS companies’ pricing page. If we look at how many plans the companies have it is overwhelmingly evident that most companies (88%) only let their customers choose between less than 7 options. About half of all companies offer three or four choices (55%). So, clearly SaaS companies have most success with offering less than 7 choices.

This seems to be an indication that there could be evidence for the stipulated rule that the marginal benefit is postitive between 1 and 7 .

Limiting cases

Now, this curve holds under the assumption that the user is doing his choice unaided by anything other than his or her own consciousness. It is important to note that this assumption doesn’t hold in all cases. Today we can often use AI to help us cut down the number of choices. When we look at a book on amazon a number of books are presented below. It is not a list of all books amazon has, but a subset based on what the algorithm thinks is relevant. The utility in this case depends on the precision of the algorithm, which is a completely different problem.

Another condition that should hold is that the choice should be comparative, that is, it should be a choice where the alternatives are compared rather than evaluated one by one. An example is finding a movie on Netflix or iTunes. you may go through a long list but you are not usually comparing every single movie to each other. Either you will create a short list (which will probably not be much longer than 4 to 7 movies) or you will just choose movie by movie: “do I want to see this now?” (a binary choice).

 

So, if you have a situation where the user should be given a comparative choice and there is no way to make AI support for that choice, then the marginal utility curve stipulates that about 4-7 choices is the best from a general point of view.

 

 

A Practical Guide To Doing Cost Of Delay Based Prioritisation

It is often very difficult to prioritise what to build and when. One of the most efficient methods of prioritising features is prioritising according to cost of delay.

Originally invented by Don Reinertsen in “Managing the Design Factory” as a new way of looking at how to build stuff, it has inspired many agile teams to apply this thinking in their sprint planning efforts.

The problem is always how exactly to find out what the cost of delay is. It is notoriously difficult to put a price tag on a feature. This is probably what has discouraged most people from doing it. But the fact that you can’t put a precise price tag on the cost of delaying a feature shouldn’t keep you from applying this kind of thinking.

One very good solution to how you might do this is provided by Dean Leffingwell in his book: “Agile Software Requirements”. He argues that cost of delay can be broken down into three components: User value, Time value and Risk reduction.

How To Break Down Cost of Delay

User value is the potential value of the feature in the eyes of the user. Product managers or product owners usually have a good feeling for this, but other parts of the company like consultants or sales people who spend a lot of time will also have a pretty good understanding this as well. One should not forget that asking the user him or herself is the most obvious solution. The reason why most people don’t so this is probably that it is relatively cumbersome at scale. At Sensor Six however we have seen customers use our product with great success to engage directly with customers to get input on the user value. Often a company will have a customer panel or a mailing list, where it is natural to ask your customers. It doesn’t have to be real value, but something simple as a 10 point scale could easily be used. More sophisticated uses we have seen with our customers is the use of forced ranking, which is an excellent way of measuring if you don’t have too many features to rank.

Time value is based on how user value decays over time. Many features are more valuable if they are delivered to the marketplace early, so they can provide differentiation. This depends very much on an analysis of competitors current state and what is assumed they are working on. This is why it is usually business analysts or product managers who will be able to rate this. Again it is possible to just use a 10 point scale to measure it.

Risk reduction/opportunity enablement describes the degree to which a feature helps us mitigate risks or exploit new opportunities. We live in a world with many unknowns and therfore it is important to be able to guard yourself against the unknowns that are threatening (risks), but also to remain open to the ones that could help us (opportunities). This evaluation will always be very subjective and dependent on the person doing the rating. Since people have very different perceptions of risk it is a good thing to invite several people to ascertain risks.

I would say that these are really good suggestions, but there could be other approaches as well. Leffingwell argues for rating thes on a scale from 1 to 10, but that can also depend on the context. If you have very few features and want a very precise measurement you should use a relative method such as ranking or pairwise comparisons. But in the end it is more important to have some sort of indication, so an easy method like a 10 point scale will be a good place to start.

How to Use the Cost of Delay Calculation For Prioritisation

The cost of delay of a feature is the same as the value it has if it is not delayed, ie. produced. Now that you have this value the next thing you would want to do is hold it up against the effort it would take to produce the feature. Effort can be estimated in the same way with a 10 point scale. If you work in an agile context you may as well use story point if that is possible. Here is where you can get your engineers to look at the features and give some sort of estimate.

Once you have som data on the effort there are several ways you could attack the problem. According to Reinertsen in The Principles of Product Development Flow there are two ways:

Shortest job first is the method to use if you want to look at minimising effort. You simply start with the features that are smallest and work your way through them regardless of the cost of delay. If features all have the same cost of delay, this is the best way to do it.

High Delay cost first is where you simply start with the features that have the highest cost of delay regardless of the effort. This is efficient in producing a high economic output. If features have the same effort this is the best way to do it.

Weighted shortest job first is where you weigh the value against the effort. If features have different effort and value, which is most often the case, this is the most efficient method to use.

How To Do It In Practise

Strangely, given the popularity of this thinking, no tools seem to support this particular way of prioritising, so it is always something that needs to be done in spreadsheets. To our knowledge Sensor Six is the only product management tool that does all of the above out of the box and even makes it possible to engage different stakeholders directly. In the following I will show how you can do exactly what Leffingwell recommends in Sensor Six.

You can see how the above would be set up in Sensor Six by going to our website and logging in with the credentials below or you can follow the step by step guide to prioritise your own features.

https://sensorsix.com/login
 CODdemo
7uJI%1JK

Doing Cost of Delay Prioritisation In Sensor Six

First you set up the different criteria: User Value, Time and Risk Reduction. You configure them as benefits and a 10 point scale. Supply them with a description.

Now you can rate them solo and evaluate everything by yourself. If this is fine and sufficient for your needs you may skip the next section.

If you want the product manager, sales rep or any other stakeholder group who are fit to act as a proxy for the user to evaluate user value simply go to the collaborate section. Here you can configure a workspace that will allow the user to give input to the user value. Simply copy the link to the workspace and send it to a list of people who you think could give you this input. Have the competitive intelligence function whether it is located in marketing or some other division rate the time value to get input on the time cost of delay per feature. Let the business analyst give input on the risk reduction opportunity dimension. Finally you need to know something about the effort. This you will invite your engineering department to work on.

The actual persons or roles can be cut differently, so maybe you will ask the same persons to rate the time and risk reduction domains (typically business analysts), engineering will estimate the effort while sales or support may evaluate user value.

When you have input on the cost of delay, you can plot the total cot of delay on the y axis and the effort on the x axis.  You should then choose those with the best cost of delay/effort tradeoffs first in order to arrive at the most efficient development plan, if your features have varying effort and cost of delay.

So this simple process can save you hundreds of hours and deliver more value to the market place quicker.