LinkedIn TwitterFacebook
2x startup Founder & CEO who has gone to the Dark Side of VC. His first company, BuildOnline was sold in 2005, his second, Koral was acquired by and became known as Salesforce Content, while Mark served as VP Product Management. In 2007 Mark joined GRP Partners in 2007 as a General Partner.  He focuses on early-stage technology companies, usually looking at Series A investment, and blogs at the aptly titled Both Sides of the Table.

2 responses to “How to Avoid a Common Product Mistake Many Teams Make”

  1. Paul Calento (@pcalento)

    We can learn a lot about designing a UI for mobile apps. Less functionality can lead to more use … and in an enterprise context higher productivity. I recently looked at a UI for a new(er) company. I immediately asked if any users interacted with it (it didn’t look like it). And that indeed was the case. As for functionality, we need to make sure users actually want it. Sometimes it is added just for the sake of doing so.

  2. Frank Nurock

    It’s accurate to say that making a blunder can be a learning favorable circumstance. But, taking the time to learn how to identify and prevent frequent errors can help you become constructive and prosperous, and deeply esteemed by your team.

    Thanks for the interesting insight.