The platypus has often been described as being “designed by a committee.” Many demos suffer similar challenges as they try to embrace the needs of too many players and options.
If your demo attempts to satisfy the needs and interests of multiple job titles and disparate sets of needs, you’ve got a Platypus Demo! You’ll end up satisfying no one and making your product look confusing, complicated, and even user hostile.
Instead, take a page (OK, it’s a chapter!) from Great Demo! and organize your multiple-player, multiple-solution demos so they align delightfully with your audiences’ specific interests.
How? Break your demo into “chunks,” bite-size pieces focused on one job title at a time.
And consider: The more user types or job titles your software serves, the more this principle applies! Typical CRM systems, for example, seek to embrace the needs of (at least!) 13 different job titles (can you name them?).
Back to the platypus… The "designed by a committee" label is because of the animal’s patchwork appearance that combines features from multiple animals: it is a venomous, egg-laying mammal with electroreception capabilities, a duck's bill, otter-like feet, and a beaver-like tail, leading 18th-century scientists to believe it was a stitched-together hoax.
Personally, I’m a platypus fan – they are fabulous creatures (but I’m not a fan of Platypus Demos)!
See Chapter 16 “Multi-Solution, Multi-Player Demos” here:
https://www.amazon.com/dp/B0C9SNKC2Y/
And learn more about the platypus here!
No comments:
Post a Comment