• Customer Feedback

    This Harvard Business Review article is a great follow-up to the last blog posting where we talk about how getting customer feedback is critical to ensuring a successful product.


    The article mentions how people often spend too much time in development rather than getting  minimum viable product available to users and then iterating based on their feedback.  Startups should perform the proper planning upfront by documenting and planning for features down the road, but the features should be released in small, quick releases.  If users unexpectedly dislike or demand a new feature not yet available, then it is much easier to update your roadmap and tailor your release schedule to what users are asking for then if you have to completely change the back or front-end solution that is already built.

  • 3 Huge Technology Mistakes Tech Startups Make

    1. Developing a solution that isn’t scalable. We get it…you can’t wait to get your hands dirty. You’re excited about your idea and now that you’ve found a web or mobile developer, you just want to start coding right away. Plus, the more you delay, the more time the competition has to rear its ugly head. Well, hold on. We’ve spent far too much time cleaning up other people’s mistakes or starting over from scratch. Startups often forget that developers aren’t technical architects (most of the time). And in their hastiness to get a product going, founders often think they can cobble together some basic requirements and end up with a product that’s exactly as they envisioned. Without the proper planning, it won’t happen. The truth is if you spend the time upfront to put together a roadmap that defines all the features your startup team can brainstorm, this will save you time in the back end. By clearly understanding, documenting, and prioritizing all the features for at least the next 3 releases, your technical architect can create a technology solution for you that is scalable and work with you to create a schedule that works for your startups’ needs. (more…)