(1 votes, average: 5.00 out of 5)
Loading ...
One of my colleagues got into a debate with one of his colleagues about the differences between goals and requirements. His opponent fired the following salvo: “[That] is not a business requirement in any company of the world…”
What you call your requirements is less important than how you communicate them.
(3 votes, average: 4.00 out of 5) Loading ...
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.
(3 votes, average: 5.00 out of 5) Loading ...
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.
(2 votes, average: 5.00 out of 5) Loading ...
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.
(2 votes, average: 5.00 out of 5) Loading ...
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.
(5 votes, average: 5.00 out of 5) Loading ...
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.
(3 votes, average: 5.00 out of 5) Loading ...
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.
(2 votes, average: 5.00 out of 5) Loading ...
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.
(1 votes, average: 5.00 out of 5) Loading ...
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.
(9 votes, average: 4.89 out of 5) Loading ...
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?
Free RSS subscription
(more...)
Subscribe to comments RSS for free
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Feb | ||||||
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | 31 | ||||
 |
These articles are written primarily for business analysts and product managers. Hopefully they help with thinking, doing, and training. Welcome aboard and let us know what you think!
