Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

If you are start-up, think beyond one user!

DZone's Guide to

If you are start-up, think beyond one user!

Free Resource

Discover how to build scalable and maintainable UI tests to optimize your Agile workflow. Brought to you in partnership with TestComplete by SmartBear.

As I am coaching and mentoring a few start-ups in Melbourne and elsewhere, I have noticed common pattern of issues across the board.

  • All start-up founders are really enthusiastic and dream of becoming rich –> Nothing wrong with it
  • All start-up founders have a strong idea in mind ---> Nothing wrong with it
  • Most start-up founders believe that their idea would take over the world, even though they have never tested beyond one user  ---> Something wrong with it

Recently I read a story about start-up failure: “Patient Communicator”. The founder built fantastic features applying an iterative development method, however, it was never tested beyond his father’s medical center.

As the founder shares his experience, PC began as a product for my father’s medical practice.  Plain and simple, I never assessed the market need for a patient portal.  It’s extraordinarily difficult to take a product that was built perfectly for a particular user and commercialize that into a broader market.

If you are on a start-up journey, think beyond one particular user! 

Overcome the weakest link in your automated testing cycle to increase test speed and coverage. Brought to you in partnership with TestComplete by SmartBear.

Topics:

Published at DZone with permission of Venkatesh Krishnamurthy, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}