John Peltier
Agile Product Management, Marketing, and More
Agile Product Management, Marketing, and More
Apr 7th
So I find myself a Product Owner running 3 scrums per day, and I have several vastly different teams (except that all are understaffed). One in particular is a high-performing team in which the developer produces great work, but in which there is some frustration with the practice of meeting daily. So I’m thinking strongly about the idea of moving to twice-weekly scrums. There isn’t enough change between days to warrant a dedicated meeting, and the team is vocal enough to raise blockers when they exist.
In my readings about the practice, many are adherents to every nuance of Agile and Scrum, but I have to question this when I am not convinced of the value obtained from the practice. So, at this point my instinct is to try twice-a-week during the next sprint, and reevaluate during the retrospective.
Thoughts?
Jan 4th
Product managers are the jacks-of-all-trades living behind the great and the ordinary products all around us. They are in charge of the product’s position in the market, its features, and ultimately its profitability. One of the biggest challenges is crafting a product that truly strikes a chord with an audience, immediately feeling comfortable. The authors of Tuned In: Uncover the Extraordinary Opportunities That Lead to Business Breakthroughs describe a six-step process for creating a products that do just that, using several case studies as well as personal experience to illustrate their points.
The six step process is as follows:
1. Find unresolved problems
2. Understand buyer personas
3. Quantify the impact
4. Create breakthrough experiences
5. Articulate powerful ideas
6. Establish authentic connections
The authors are thought leaders with Pragmatic Marketing, a highly-regarded consultancy in the world of product management. They teach a proprietary framework of 37 elements of product management which at a high level describes the process of identifying a market, finding problems in that marketing, developing solutions and bringing them to market. In the framework, while not diminishing the importance of the others, Tuned In focuses on the identification of market problems, requirements, use scenarios and positioning elements to illustrate the point that only by interacting with existing customers and prospects (tuning in) can one identify the problems people are willing to pay to solve. Products that do not solve a problem people are willing to pay to have solved, in Pragmatic’s view, should not be developed.
Tuned In is written in a highly readable style that is short on jargon but long on stories that hit home. A prime example of a “resonator” from the book is Zipcar, which the authors point out solves a need for a market that had not previously been met by any existing car rental company: the urban dweller who needs a car for a short time. In a recent article in Money magazine, stalwarts Ford and Hertz are cited as wanting “in” on Zipcar’s market–one which they had failed to observe and fill at any point in their long history. [It can be argued that companies like Ford and Hertz may have considered a car-sharing market but decided in self-interest NOT to fill it; the article claims that for every shared car, 20 are taken off the road, which is not good for the traditional car business]
This is a very common-sense book that is not hard to understand, but at the same time does not delve into extreme detail on topics such as market-research; academic analysis is not the point of Tuned In. Tuned In is “tuned in” to the fact that product managers need a simple, easy-to-understand process to “tune in” to their markets. And, on that, the authors deliver.
Dec 25th
Merry Christmas!
Enjoying a lazy Christmas provides a bit of time for reflection, so I am taking this opportunity to collect and publish my observations–both good and bad–of life over the last 50-51 weeks. For those of you who don’t know my background, I moved from Atlanta last January after spending 19 years in the Atlanta area. We chose Austin because of its proximity to family, its climate, and its employment outlook. Indeed, the move was exacerbated because my wife found a job here. As a native of New Orleans, I looked forward to a place that was closer in population to my home and that had some of the sense of community I grew up enjoying.
A few months ago, I happened across a similar one-year retrospective published by Alora Chistiakoff, and I recommend reading it for its thoroughness. I share her perspective on a lot of the items she mentioned. With that contrast of Austin and California as a model, I shall share my perspective on moving west from Atlanta after growing up in New Orleans:
To summarize, it’s been an enlightening year. I’m considering ideas for side businesses, which is a massive change of perspective from my life in Atlanta. Atlanta’s mindset is corporate in nature, and while I had a couple of friends who ran their own businesses, they seemed like oddities and I didn’t quite “get” it. In Austin, the entrepreneurial spirit and the sense of place is alive and strong. So although it’s been a separation from friends and family, the move has been fruitful in terms of personal growth.
Now…back to being Merry!
Dec 23rd
For those of us in product management, the drama unfolding in Congress with regard to the healthcare reform package is a too-familiar refrain. Without wading into the merits of the proposal on the table right now, we’ve watched a team set an initial objective to solve a specific problem (provide healthcare for the uninsured) which has morphed over the past year as deals are cut to obtain the approval of hardheaded stakeholders. As further bargaining takes place to get votes and get the solution through Congress, we have a solution coming up for a vote that both major constituent groups are disowning for different reasons.
Take all this within the context of working in different realities (some not acknowledging the problem really exists/defining it differently), with different value systems and beliefs about whether the current forum is even the right one to address the problem, and it’s no wonder that what comes out of such a process is often clumsy and–ultimately–a poor solution. A guest blog on HBR illustrates this point with the “successful” Medicare Part D episode earlier this decade: a solution that many don’t even understand, much less support.
In product management, we advocate that there needs to be one “owner” of a problem space and solution, who makes the decisions about what form that solution takes and avoids feature creep. Those decisions need to be made with a laser focus on the problem being solved and the market itself. What we’re seeing in Congress–with all bills, really, but highlighted in prime time for us now–is the exact opposite: features added and features cut arbitrarily for the purpose of gaining stakeholder support, not because it makes the solution better. The goal of delivering something to market has taken precedence over actually solving the problem.
This is no way to build a quality product.
Dec 23rd
So 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
Dec 22nd
I’m writing to share a couple of observations about ATM machines. As long as they’ve been part of our lives, it’s only in the last few years as a Bank of America customer that I’ve seen those products evolve. Today, I observed a truly revolutionary modification that saves two steps in every cash withdrawl:
The entry of PIN number and selection of fast-cash amount were on the same screen.
In every previous interaction with an ATM, after inserting my card, I’ve been conditioned to (1) enter my PIN number, (2) click a button, (3) click a button for “Fast Cash,” and then (4) select an amount. In today’s interaction, some significant experience design had been applied. Though a single example does not demonstrate a pattern, I’d be willing to bet that my experience is not unusual: 99% of my transactions are fast-cash. So today’s interaction was much much simpler: (1) enter PIN, (2) select fast-cash amount. Choosing the fast-cash amount triggered the ATM to validate my PIN and dispense the cash. That saved 2 steps, or 50% of the work required of the user. Nice!
The only question I’m left with is: Why did this take until the year 2009?
Further, possibly because I was distracted by the unusually efficient interaction, I do not recall being forced to request a receipt. In previous interactions I’ve been annoyed with BoA ATM machines that display a message “Retrieving preferences,” and then immediately ask if I want a receipt. My receipt preference doesn’t change: I want one. I realize the bank would prefer I do not, but their opinion is irrelevant. If you’re going to store my preferences, and you insist upon asking me that question each time, the profile you’ve assembled is incomplete. But as distracted as I was, I cannot swear that I did not have to answer that prompt: and believing I didn’t would be too impressive of an example of interaction redesign for me to handle.
How many more everyday interactions can be made dramatically better?