The opinions expressed by the bloggers below and those providing comments are theirs alone, and do not necessarily reflect the opinions of Ryma Technology Solutions. As they say, you can't innovate without breaking a few eggs...
Now that we've pointed out some background on the problem statement in Part One, and addressed controlling levels on innovation in Part Two, we're ready to look at some Blue Ocean examples.
Products or services that have different forms but offer the same functionality or core utility are often substitutes for each other. Take the example of Intuit’s Quicken. To sort out their personal finances, people can buy and install a financial software package, hire a CPA, or simply use pencil an...
Part one of this series can be read here.
Now given the examples of the problem statement in part one, I need to point out a few principles in part two before I can address how to leverage Blue Ocean Strategy concepts in part three. One thing's for sure, given a sample of market evidence, there are many different problem statements that could be written. In fact, some have criticized the problem statement process because it's not repeatable. In other words, given two product management teams, ...
The Problem Statement should always be written with the least viable product in mind. That's not to say you should be addressing the solution when writing the problem. Before presenting an example, I want to provide a little background into the problem statement so there's no confusion.
I'll start with a Use Case: 'The application processes a customer's credit card when given the correct information.' This same Use Case might have been written as a User Story this way: 'A company can pa...
Yes, we derive the problem statement from the market evidence gathered. Hopefully that evidence has been grouped and categorized. There's nothing more disruptive than having to shift mental thinking back and forth between evidence that hasn't been preprocessed.
The 5-Why is a questions-asking method used to explore the cause/effect relationships underlying a particular problem. Ultimately the goal of applying the 5-Why method is to determine the root of a defect or problem. Other method...
There are those that believe a problem is a gap between the way things currently are, and the way you or your customers believe they should be. The bigger the gap, the bigger the problem. I like the formality of this type of thinking, I mean many people don't even try to define what a problem is. Let's look at a few examples of this:
"I keep forgetting how to view a subset of components within a part structure. I believe this software application should be easier to use."
"Wh...
When we got back we went on the fretful WATERSLIDE! After that we had Dinner. It was Butter Chicken with rice and vegetables. For
