RT @celia: (via @StephenFleming) Steve Blank: "The golden age of Silicon valley is over..." m.theatlantic.com/business/archi… @sgblank
Uncategorized
The Strategy Canvas
0I recently read a copy of the book Blue Ocean Strategy: How to Create Uncontested Market Space and Make Competition Irrelevant. As many have observed previously, this is a great source of inspiration and food for thought, and well worth the investment of time from product managers.
Blue Ocean strategy, in summary, involves examining the value proposition of a value or service to identify whether every item included is truly valued or could be eliminated, and whether any additional items adjacent to the offering could be included as a way to expand the footprint of the offering to serve additional parts of the market.
The most valuable tool I found in the book is the Strategy Canvas. The strategy canvas is a graphical tool that represents the key value elements included in an offering, and comparing how multiple competitors position themselves to satisfy each of those key elements. By including a “Red line” one can show where the current industry value curve sits, to provide additional perspective. I’ve immediately found the technique useful in visualizing and describing how an already-specified product will compete and keeping focus on where to invest resources. I look forward to applying this visualization technique to new-product development.
One of the book’s frequent criticisms is that the book doesn’t validate that commonly-cited trend-setters like Southwest Airlines or Cirque de Soleil achieved their success as a result of applying Blue-Ocean analysis and strategy, or whether they are simply easily illustrated using the book’s approach and techniques. Scott Sehlhorst has suggested that the way to design a winning product in the Blue Ocean framework is to apply the same type of measurement to personas: measure the value each persona places on each value element, and from there design your offering around the value elements that concern the persona you are building your product for. I recommend reviewing Scott’s post as a primer on how to apply this strategy framework proactively.
The anecdotes that illustrate the book’s key points are memorable and useful–one can easily use the stark contrasts between Cirque and its competitors, for example, as an analogy when discussing competitive strategy. Since I was immediately able to put the book to use in my day-to-day work, before even finishing the last chapter, I can do nothing but recommend this title to other product managers.
Why am I here?
3So why would I take the time to move a blog from WordPress.com to my own domain?
Ultimately, it came down to learning about WordPress unconfined by the limitations of a WordPress.com blog. I wanted to improve the presentation with a fresh new template, better focus on my career direction and challenge myself to write more frequently. Most everything we encounter from day to day is a product of someone’s work–I frequently examine things from the perspective of product management when considering what problems it solves and how well, and the perspective of marketing when considering how awareness is delivered to its target audience. My background includes quality assurance, and I certainly look at products in terms of how well they meet their goals (validation) and objectives (verification) so I occasionally include observations about that as well.
As I contemplate 2010, I realize that I enjoy writing, and I want to experiment with what moves my (small) audience and what does not. I want to interact with fellow bloggers a bit more. I have a few ideas for things I’d like to accomplish with my writing in the future, and I believe this can be a beginning and a platform with which to explore.
Comments? Questions? Complaints?
Please ignore this token: NXK36VHMX2TP
Is innovation really that simple?
1I’m reading an interesting book by Denis Hauptly called Something Really New, which purports to boil innovation down to 3 simple steps:
1) What is your product used for?
2) What are the steps that compose that task, and can any of them be removed?
3) What is the next thing the cusotmer will do after using your product?
Hauptly points out in the book that there are two types of innovation, essentially incremental and wholesale, and this type of three-step process is more applicable to incremental innovations. The small (incremental) innovaiton is not necessarily less valuable to a company, and it is more likely to be teachable. By honing one’s focus on the purpose of products and the specific steps of the tasks they enable, attention is being focused on workflows and on looking for opportunities to optimize.
How does one reach life-changing innovation? Is it the same as incremental, but just a better target for optimization? Or is it something existential that may only happen to people in a hightened state of mind or with higher skills? I suppose if I truly knew the answer, I’d be a more successful innovator! That said, while I think creativity and skill plays a great part in it, innovation is probably not as likely if one doesn’t focus attention on the steps required to accomplish tasks, and the tasks which come before and after a task–which is what this book helps to do. For communication of that mindset, I find it valuable.
Can Palm come back from the Dead?
0By now, everyone has heard about the hype of Spring 2009, the Palm Pre. The release is finally confirmed to be taking place on June 6. Many are asking, can the device possibly live up to the glowing reviews?
Let’s look at this from a slightly different angle–I think it’ll be fascinating either way. Look at the amount of brand publicity Palm has gotten out of this device! For a company that became a household name ten years ago with the Palm Pilot line of products, it’s been a rough ten years watching that name fade in its influence until it was practically swallowed whole by Apple when the iPhone was released. I think this is one of the contributing factors to why the Pre is getting so much pub, but there are a couple of others:
- people who think Apple needs a solid competitor in the consumer space
- perceived quality of the WebOS “card” UI
- need for a new “story” to fill the pages of technology blogs
- Palm loyalists who want to get away from Windows Mobile
- everyone loves an underdog
Yes, I’m stretching here. I’m not exactly sure what is really motivating all this attention. I really think it’s blog filler–I’ve had two Palm devices over my lifetime and own one now (the 800w), which sadly I’m contractually committed to until June 2010, but I’m definitely a late adopter. I’m still waiting to see if that whole “computer” thing is going to take off.
One thing Palm is actually doing right is involving developers early, to jump start the “app store” concept. Palm recruited a bunch of developers to have a look at the OS and got impressive feedback. Developers are already organizing BarCamp-like PreDevCamp events to collectively organize and learn to develop for the new OS. So part of the seed behind the hype is winning over the geek squad.
Still, this won’t succeed if it only wins over the technical folks. Simply put, this product must win over the consumer–and that battle starts June 6. has already begun.
Twitter overestimates itself on the diffusion curve
1Twitter posted news on its blog today, and briefly on the service, that they are removing one of the settings for @replies.
Based on usage patterns and feedback, we’ve learned most people want to see when someone they follow replies to another person they follow—it’s a good way to stay in the loop. However, receiving one-sided fragments via replies sent to folks you don’t follow in your timeline is undesirable. Today’s update removes this undesirable and confusing option.
What Twitter reads as “most people” is clearly not the power users, who are using Twitter actively to build networks and reach out to people. That group of power users–a persona, perhaps–is distinctly vocal, and so within moments of this change being announced, blog posts from heavyweights like TechCrunch to personal (but busy) blogs from industry veterans like Whitney Hess all lambasted the move immediately.
How can a company with a clearly scoped, profitable product like Twitter not understand this? (oh, wait..) I believe Twitter is victim of its own hype, and doesn’t know its own location in the product lifecycle. In terms of the diffusion curve, I would estimate Twitter is somewhere in the “early adopters” stage. Until about 6 months ago, it was used innovators only–and heavily dominated by the power user persona who would be offended by a setting like this being removed. As a few celebrities and news networks have jumped on board, the media thinks Twitter is now “mainstream,” but try this test: Go ask 10 of your non-technology friends whether they use Twitter. Even better, whether they understand it, and whether they access it from a mobile device. I bet you get less than 2 who answer yes to the last 2. Twitter is NOT mainstream.
Given that, Twitter should be focused on those power users who make up the innovator and early adopter group–people who like to tweak the experience to their tastes. Instead, they chose to not only remove a useful option, but even worse phrased the rationale as removing an “undesirable and confusing” option. Way to talk down to your user base!
Very bad move, guys.
UPDATE: Turns out there was a technical limitation, so the rationale given was bogus to begin with. So not only did they insult their most technical users, but they lied to them about a technical problem.
John Peltier’s Writing Portfolio
0Welcome to my portfolio. My intent here is to share samples of my writing, both published professionally and published on blogs, so as to expand my freelance opportunities. I am a software product manager with skills in the written word. I am interested in writing assignments I can take on during evenings and weekends.
For your review, links to several samples of my writing:
I have begun a blog that focuses on challenges in software development and specifically my career, product management.
In graduate school, I co-wrote a case study about CyberGold.com, which was published in the Annals of Cases on Information Technology.
While working in software quality assurance, I wrote a review of Managing Software Requirements which was published on Stickyminds.com.
While blogging for BlogCritics, I wrote an article advocating and explaining the use of RSS.
While writing for BlogCritics, I wrote this album review of Black Holes and Revelations by the band Muse.

Recent Comments