Writing Verifiable Requirements should be a rule that does not need to be written. Everyone reading this has seen or created requirements that can not be verified. The primary reason for writing requirements is to communicate to the team what they need to accomplish. If you can’t verify that what […]
Business Analysis / Product Management / Requirements
Posted on:
Writing Unambiguous Requirements
Writing unambiguous requirements is about understanding what is written, and what is read. Without a clear understanding of your market, you can’t write unambiguously. Even when you understand your market, you risk writing something that is ambiguous to your readers. Documenting requirements is about communication. Don’t break this rule, or […]
Product Management
Posted on:
Innovation and Transparency
Accept has invited me to participate in their webinar series on Transparency and Innovation – this Wednesday, July 28, 2010 (10AM Pacific, 1PM Eastern). Join us and join in!
Business Analysis / Product Management
Posted on:
Rupert Murdoch – Zero; John Nash – One
vs. What happens when billionaire media magnate, Rupert Murdoch, pits his idea against a Nobel-prize winning idea from the beautiful mind of economist and mathematician John Nash? When you act on what you hope your market will do, instead of what you predict your market will do – you’re in […]
Business Analysis / Product Management / Requirements / Requirements gathering
Posted on:
The High Costs of Building the Wrong Product
As product managers, we talk about creating the right solutions with our products. Understanding the very real problems our customers face, understanding the very real opportunities our markets present, and manifesting that understanding in a product roadmap. Other than being “not as good,” how expensive is it to build the […]
Product Management / Uncategorized
Posted on:
Don’t Listen to Your Market
Most companies ignore their markets – and they will struggle to survive. Some companies listen to their markets – and they have an opportunity to succeed. You have the opportunity to understand your market, and transform it into your market – but you can’t get there just by listening. Don’t […]
Agile / Kano Analysis / Product Management / Requirements Models / Software development
Posted on:
The One Idea of Your Product
“For what one idea do you want your product to stand in the mind of your customer?” I heard Roger Cauvin ask that question at the most recent ProductCamp Austin [correction – he said it here – thanks Roger], and the quote has been jumping to the front of my […]
Business Analysis / Product Management / Requirements
Posted on:
Consistent Requirements
Consistency in writing requirements is important on two levels – strategic and tactical. Tactically, you need to write your requirements with grammatical consistency, so that potentially ambiguous statements will be interpreted similarly. You also need to write requirements that are logically consistent, so that you avoid “impossible” requirements and gaps […]
Kano Analysis / Marketing / Product Management / Requirements / Requirements Models
Posted on:
Minimum Market Acceptance
April Dunford just presented Startup Marketing 101 at DemoCamp Toronto. Great ideas from the ‘marketing and your startup’ point of view. I’ve often said that product managers and product marketers care about much of the same market data, they just do different things with it. The idea of minimal feature […]