Framework for getting customer feedback actionable towards a market oriented product development. By Michael Sippey. Most important rule: speak to your customers every day. Literally! Every. Single. Working. Day. Speak with them. Learn from them. 3 key lessons: #1: Have a minimum of 30 meetings, otherwise the product won't be good enough. Michael even shared … Continue reading Customer feedback & product development
1. Don’t let your eyes be larger than your stomach…at first. 2. Assuming you have your beta/version 1 product, the fist step is to understand exactly who your clients are. 3. The second step is to understand how the clients operate and get some initial feedback on the product. 4. Don’t go whale hunting with … Continue reading Large companies using startup’s software – how to
The save or not to save, that is the question! Should you cut fat and preserve your startup's capital or maintain a high burn rate and grab as much market as you can? Ben Horowitz shares his opinion in a long but great article. Definitely a must read! Read Article - All things D
5 Ways To Break Through Innovation Bottlenecks "Citi conceived a highly disruptive new business model for a core banking franchise. This new model blended new technology, user-centric design principles, and process innovation to strengthen the bond between banker and client. But the new business model ran the risk of running into several of the bank's … Continue reading Bottleneck buster
Found great source of Apps UI inspiration: Patterns It has lots of screenshots of Apps, each featuring a specific detail of interest. Screenshots identifies App, category and page/step (login, registration, checkin, dialpad, etc). Some examples:
(I stole this answer from Michael Wolfe at Quora - it is so great I couldn't resist. If you work in software development, you'll understand how awesome it is) " Let's take a hike on the coast from San Francisco to Los Angeles to visit our friends in Newport Beach. I'll whip out my map … Continue reading Software development: why are task estimation so wrong so often?