Ebookmakr Failure: The Fallacy of Knowing What to Build – The Post Mortem

Executive Summary – Lessons Learned from Ebookmakr’s Failure:

  1. Love the problem more than your solution.
  2. Don’t push too far your dreams of China in your hand.
  3. Use prototyping tools such as Marvel when running user interviews. (More here: Four Lessons Learned From Making Customer Value Your Priority.)
  4. Be careful with the selection process for user interviews: You might end up picking those that will support your vision – it’s a self-fulfilling prophecy trap.
  5. Beware of false positives in user interviews.
  6. Never start writing a single line of code before an appropriate number of customers signed up. (For clarification: Customers are paying users.)
  7. Never spend money on developing a prototype when you’re not working full-time on growing the user-base and increasing customer value.
  8. Be patient and give your product the time it needs.
  9. Always make branded t-shirts and wear them later regularly to preserve the recollection of the disaster. (See below.)
Continue reading Ebookmakr Failure: The Fallacy of Knowing What to Build – The Post Mortem

Food for Thought #12: Holacracy, Customer Value, What Is Success, The Feed

Age of Product’s Food for Thought on October 25th, 2015 on: Holacracy w/ Tony Hsieh of Zappos, customer value driven product design, what is “success” w/ Jerry Colonna & Brad Feld, slaves of the feed, how Bigcommerce started, 2015 Pacific Crest SaaS Survey, Software Eats Healthcare and how Expensify doubled its customer base.

Continue reading Food for Thought #12: Holacracy, Customer Value, What Is Success, The Feed

Four Lessons Learned From Making Customer Value Your Priority

Building a valuable, useable and feasible product does not happen overnight. These are my four core learnings from focusing on customer value, looking back at the projects I have been pursuing over the years.

Lessons Learned #1: Customers Don’t Know What They Want. And You Cannot Just Ask Them.

It’s really hard to design products by focus groups. A lot of times, people don’t know what they want until you show it to them.
Continue reading Four Lessons Learned From Making Customer Value Your Priority

Food for Though #11: MVP, Agile Failure Patterns, Notifications, Definition Of Success

Age of Product’s Food for Thought on October 18th, 2015 on MVP best practices, agile failure patters in organizations, the rule of notifications, success and being yourself, the Failure of Everest, bubble talks and what it takes to build an entrepreneurial ecosystems:

Continue reading Food for Though #11: MVP, Agile Failure Patterns, Notifications, Definition Of Success

Agile Failure Patterns in Organizations

Why Agile is Simple and Complex at the Same Time

Who wouldn’t agree that the four core principles of the Agile Manifesto

  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

— aren’t derived from applying common sense to a serious problem?

That the application of those principles might be suited to fix numerous organizational dysfunctions and reduce an error-prone and complex social setting to maybe just a complicated one?

Continue reading Agile Failure Patterns in Organizations

Food for Thought #10: End of the Unicorn, Bubble, Great Teams, Hardware Marathon

Age of Product’s Food for Thought on October 11th, 2015 on the end of the Unicorn, bubble in Silicon Valley, how to build great teams (by building a great culture), and lessons learned from building a hardware startup:

Continue reading Food for Thought #10: End of the Unicorn, Bubble, Great Teams, Hardware Marathon