Pain Points – Treasure Map to Sweet Spots

Pain Points are the parts of a process, product or functionality that annoy or even block users.  By definition, they are not fulfilled by Competitors and are desired by Users.  Those are 2 of the 3 ingredients of Sweet Spots.  The only thing missing is your capability to ease the pain.  So take a look at what the pain points are for your customers and find a way to solve them and you’ll have a differentiating offering, or Sweet Spot.

Headache

One of the pain points for free web-based email was the full inbox due to limited storage.  Google saw that pain point and found a Sweet Spot with a 1gb inbox (256 times larger than the 4mb standard at the time), which made Gmail massively successful and saw people paying upwards of $100 for an invite when it launched.  Netflix solved the pain point of driving to the store to rent and return movies on time by dropping return dates and late fees and using prepaid envelopes so customers didn’t have to leave their home to send and receive movies.  Paypal saw the pain point of transferring money to people online and made it easy to send money to anybody who had an email address.

For most industries it is easy to see the pain points; if not, just ask your customers.  Sometimes pain points can’t be easily solved, but sometimes it just takes a little innovation to give big relief to users.  Perhaps the last time solutions to a pain point were considered the technology, economics or other factors prevented a solution from being built but maybe now those factors have changed, opening up the door for a sweet spot innovation to provide a competitive advantage.

8 Responses to “Pain Points – Treasure Map to Sweet Spots”

  1. […] Sweet Spot Strategy User Needs + Competitor Gaps + Our Capability = Competitive Advantage « Pain Points – Treasure Map to Sweet Spots […]

  2. […] identified a pain point and figured out an elegant solution to eliminate or alleviate the pain.  So you get to work […]

  3. […] from them before you even write a line of code.  If you are creating a new website to soothe a pain point, then create just that functionality and don’t worry about the other standard functionality […]

  4. […] will ‘get it’ and use it.  If you are breaking new ground rather than solving a known pain point or building an online version of an offline solution, then you may need to first bridge the gap […]

  5. […] is a pretty easy way to ease the above pain points: integrate lifestreams into the profile.  Let a user share their facebook and twitter feeds on […]

  6. […] If a product doesn’t properly solve a problem, or solves a problem that isn’t really a pain point for anybody, then it won’t usually gain many early […]

  7. […] majority of consumers are not power users.  If your solution to a pain point is complicated, or different from the normal methods, then most of your users may have trouble […]

  8. […] far ahead of the many competing word games out on retail shelves.  However, it is not without its pain points, which lessen the enjoyment of the game for many.  Some of the pain points are: time spent waiting […]

Leave a Reply