Skip to main content

Posts

Showing posts with the label value proposition

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos...

Competitive Mindshare Maps

Why You Need a Competitive Mindshare Map The core of your product strategy lies in your product's positioning and unique value proposition (UVP). It should drive nearly all product decisions, including the roadmap, feature prioritization, marketing messages, and sales approaches. A sound unique value proposition depends on: Value . It should convey the value of your product. Value is rooted in the problems your product solves. Competitive landscape . It should differentiate your product from available alternatives. Perception . It should acknowledge perceived weaknesses of the product and perceived strengths of competing products. Surprisingly, most companies take the value of their products for granted and don't bother to explicitly formulate a unique value proposition. For others, determining a unique value proposition is haphazard, with little or no process guiding the decision. At best, they focus on the value and pay insufficient attention to perceptions a...

Lean Startup Concepts

Now that you've had a largely buzzword-free introduction to lean startup methods , you may be interested in a bit deeper understanding of the concepts and terminology.  Lean startup methods incorporate scientific methods and principles of agile development to help practitioners learn markets quickly and reliably and deliver successful products.  But lean startup enthusiasts and practitioners throw around a lot of terminology and concepts that may seem alien or not particularly meaningful to you. Let's examine and demystify the basic lean startup terminology with a rich and concise conceptual model . To view the model of lean startup concepts, click the image below: Lean startup concepts fall within four different clusters: hypotheses, learning, market, and product. Hypotheses Forming hypotheses is a component of lean startup methods. The business model represents the strategy driving more tactical product decisions, and it consists of a set of hypothes...

What Is Lean Startup? Here's What You Need to Know

You've probably heard a lot of buzz about "lean startups".  You may wonder if it's mere hype, applies just to tiny bootstrap ventures, or if adopting some lean startup methods might actually benefit your company. One of the top problems companies face as they make product decisions is that the process of learning the market, and learning what makes the product successful, is slow and unreliable . Sometimes they suffer analysis paralysis, swerve from one big deal to the next, allow conventional industry wisdom to stifle innovation, or squabble over uninformed personal opinions. In other cases, they make decisions quickly but fail to learn from their inevitable mistakes until after they've invested exorbitant amounts of time and money. If you find that your organization is facing this problem, it's worthwhile to consider lean startup methods. Just as scientists use the scientific method to learn how the universe works, your product team can apply ...

4 Problems Companies Face in Making Product Decisions

Introduction Why is product management important? Whether or not they employ product managers, companies make daily decisions about how to develop, market, and sell their products. As they make these decisions, companies typically face - or are trying to overcome - four general problems. The Problems   Products don't provide value to prospective buyers and users. Products that don't deliver value generally don't succeed in the marketplace. Value comes from solving problems that prospective customers face. "Cool" technologies and feature-laden products, if they don't help customers solve or avoid compelling problems, don't provide value that lead to usage or sales. Effective product management identifies a set of prospect problems that drive an overarching value proposition, and it empowers the entire product team to deliver and communicate that value.   Developers don't know what to build, and why . Developing ...