Remove Development Team Review Remove Lean Remove Metrics Remove Video
article thumbnail

Is This Ex-Googler’s Pre-Product Approach the Fast Track to Product-Market Fit?

View from Seed

He’s dubbed the approach “ pretotyping ,” and it shares many of the same principles as both its similar-sounding (if later-stage) cousin, prototyping, as well as the more well-known lean startup movement. NVV: Lots of entrepreneurs reading this will think about the lean startup movement when they hear about pretotyping.

Product 120
article thumbnail

Lessons Learned: Work in small batches

Startup Lessons Learned

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process. Take the example of a design team prepping mock-ups for their development team. I dont think so.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: The product manager's lament

Startup Lessons Learned

I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. Labels: product development 8comments: Vincent van Wylick said. Expo SF (May.

article thumbnail

Datablindness

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. That’s because many of our reports feed us vanity metrics: numbers that make us look good but don’t really help make decisions. Too much of this data is non- actionable.

article thumbnail

Lessons Learned: What is customer development?

Startup Lessons Learned

Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer Development. This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. Expo SF (May.

article thumbnail

Lessons Learned: The four kinds of work, and how to get them done.

Startup Lessons Learned

Now its time to start to think seriously about how to find a repeatable and scalable sales process, how to position and market the product, and how to build a product development team that can turn an early product into a Whole Product. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. for Harvard Business Revie.

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

I now believe that the "pick two" concept is fundamentally flawed, and that lean startups can achieve all three simultaneously: quickly bring high-quality software to market at low cost. A project usually has an absolute duration and budget whereas the time and money dedicated to development within the project is where the tradeoffs are made.