You give your requirements to the engineering team, and they look complete. The team builds your product, you launch it and the market soundly rejects it. Why? Because your requirements weren’t complete – they didn’t actually solve the problem that needed to be solved.
Category Archives: Business Analysis
Most Engaging Articles of 2009
Engagement – that’s what this whole product management blogging thing is about. Check out what Tyner Blain readers found to be the most engaging articles in 2009.
Read the rest of the article …
Why Cross-Selling Works
Why does cross-selling, the process of selling something additional to someone who is already making a purchase, work? This article explores some of the theory and rationale behind cross-selling – from qualification to motivation and profitability.
Read the rest of the article …
Posted in Business Analysis, Product Management, eCommerce
Tagged cross-sale, cross-selling, eCommerce, ecommerce product management
13 Comments
Foundation Series: Substitutes and Complements
Do you know about substitute goods and complementary goods? If you’re doing any eCommerce, and are thinking about cross-sell and upsell, you should understand the basics about substitutes and complements.
Attainable Requirements
Unless you live in a world filled with unicorns and rainbows, writing realistic requirements is critical. When you set unattainable goals, the best result you can hope for is a frustrated engineering team. Write requirements that are attainable, and your team will surprise you with what they can achieve.
Read the rest of the article …
SEO Product Management
SEO, Search Engine Optimization, is an area that every online website needs to think about. The idea is that the more traffic you can get to your website, the more products you’ll sell. Just because you can lead a horse to water doesn’t mean you can make him drink. What a great opportunity to product manage your website and ask why about SEO.
Read the rest of the article …
Design-Free Requirements
Design-Free requirements are important for two reasons, and hard for two other reasons.
Design-free requirements are hard because you “know what you want” when you should be documenting “why you want it.” Writing design-free requirements can be hard when you don’t trust your development team to “do the right thing” even though it is not your job to design the solution.
Read the rest of the article …
Foundation Series: Cross-Selling and Upselling
You have an eCommerce site. You sell products online. Do you cross-sell additional products? Do you upsell to better products? This article explains the difference between cross-sell and upsell, and looks at some real-world data about the effectiveness of both.
Read the rest of the article …
Posted in Business Analysis, Foundation series, eCommerce
Tagged cross-sell, crosssell, up-sell, upsell
6 Comments
Modeling User Competency
Perpetually intermediate (competent) users. Users who briefly exist as novice users and never become experts. Most of your users are competent, and you should design for them. Competent users have different needs and different expectations than novice or expert users. How do you know your user’s competency levels, so you can design for them?
Concise Requirements
Concise requirements give your team a useful, easy to read and easy to change understanding of what must be done. Great requirements exist to do three things:
- Identify the problems that need to be solved.
- Explain why those problems are worth solving.
- Define when those problems are solved.
Latest Articles
Comments on all Articles
