Startup Lessons Learned
FEBRUARY 20, 2009
Similar results apply in product management, design, testing, and even operations. Take the example of a design team prepping mock-ups for their development team. Give the dev team your very first sketches and let them get started. Today, I want to talk about the reasons smaller batches are better.
Startup Lessons Learned
OCTOBER 5, 2008
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. Nice write-up.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
JUNE 8, 2009
You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. So the product development team was busy creating lots of split-tests for lots of hypotheses. Each day, the analytics team would share a report with them that had the details of how each test was doing.
Startup Lessons Learned
NOVEMBER 17, 2008
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 Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?
Startup Lessons Learned
NOVEMBER 8, 2008
Our goal in product development is to find the minimum feature set required to get early customers. In order to do this, we have our customer development team work hard to find a market, any market, for the product as currently specified. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?
Startup Lessons Learned
JULY 13, 2009
But it goes beyond that, including techniques for improving the economics of product development. Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet. Wow, great review! percent utilization in the precourse surveys.
Startup Lessons Learned
OCTOBER 20, 2008
The team cant get permission from the business leaders to get "extra time" for fixing. Because there are no tests for new features (or operational alerts for the production code), the code that supports those new features could go bad at any moment. Second was not changing the requirements without full sign-off.
Expert insights. Personalized for you.
161 
Let's personalize your content