This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Lessons Learned by Eric Ries Sunday, April 26, 2009 Productdevelopment leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in productdevelopment. Its a key lean startup concept. Great post!
Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific productdevelopment I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific productdevelopment. I agree with the less is more productdevelopment approach, but for a different reason. Now that is fun.
These can be research tasks, like finding every tech blogger who blogs about cats, repetitive tasks like creating 100 affiliate links for products in a Word document, or ongoing tasks like monitoring a handful of job boards and posting new jobs to your website. After your product launch. Point #1: Developing a Proof of Concept.
The application of agile development methodologies which dramatically reduce waste and unlock creativity in productdevelopment. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.
Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in ProductDevelopment/Management - a common misinterpretation of the Toyota Production System.
In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes productdevelopment in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.
Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in productdevelopment. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries.
But first I think we need to save the product manager from that special form of torture only a waterfall productdevelopment team can create. Labels: productdevelopment 8comments: Vincent van Wylick said. This post has been removed by the author.
Own the development methodology - in a traditional productdevelopment setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: productdevelopment 15comments: mukund said.
If you watch the video/audio below, youll get to see some of the questions I was asked after my presentation. I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries.
I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software productdevelopment team. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you?
It outlines four major growth strategies: market penetration , market development , productdevelopment , and diversification. Productdevelopment. Productdevelopment allows you to expand your existing market share by developing a new product for that audience.
Luckily, I now have the benefit of a forthcoming book, The Principles of ProductDevelopment Flow. Labels: five whys root cause analysis , productdevelopment 11comments: Peter Severin said. Its really helped me articulate my thinking on this topic, and includes an entire chapter on the topic of reducing batch size.)
This is the first post that moves into making specific process recommendations for productdevelopment. Labels: productdevelopment Speed up or slow down? This is the first post that moves into making specific process recommendations for productdevelopment.
Startups especially can benefit by using technical debt to experiment, invest in process, and increase their productdevelopment leverage. The biggest source of waste in new productdevelopment is building something that nobody wants. Leverage productdevelopment with open source and third parties.
Last, Ive tried to keep this blog updated with events , slides , audio , video and books that are helpful as well. Last, Ive tried to keep this blog updated with events , slides , audio , video and books that are helpful as well. Have a favorite who I overlooked? Please share in a comment. Did I miss anything? Did I miss anything?
This gets me into trouble, because it conjures up for some the idea that productdevelopment is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product.
Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software productdevelopment team. There are three stages: We start with ideas about what our product could be. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you?
Customer development is a parallel process to productdevelopment, which means that you dont have to give up on your dream. Our goal in productdevelopment is to find the minimum feature set required to get early customers. This is a common mistake.
Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their productdevelopment team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.
Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.
Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ► January (10) ► 2008 (59) ► December (6) ► November (14) ► October (10) ► September (27) (..)
However, when it comes to MLM productdevelopment, marketing ideas and compensation plan strategy, being a creative copycat could be a legal and ethical shortcut to achieving your business goals for your new MLM, party plan or direct selling company. The same goes for new MLM productdevelopment.
Best of all, Nivi from Venture Hacks was recording, so these slides have synchronized audio, too. So without further ado, let me share the slides with audio. Productdevelopment leverage Validated learning about customers Built to learn Web 2.0 Here are some of my top takeaways. Those are only symptoms. Expo, never fear.
Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.
The product manager's lament About the author ► September (27) ► August (2) Labels agile (8) audio (3) case study (5) continuous deployment (10) customer development (12) engagement (3) events (35) five whys root cause analysis (6) hiring (5) iPhone (3) lean startup (12) listening to customers (10) minimum viable product (4) product (..)
Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.
Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile productdevelopment , low-cost (fast to market) platforms , and rapid-iteration customer development. I think Drucker said it best.
None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or productdevelopment milestones. Labels: productdevelopment 4comments: Doug said. Everything else, including anything that optimizes any other goal, is waste. Thank you Eric. March 2, 2009 1:58 PM programiTV said.
Labels: five whys root cause analysis , productdevelopment 15comments: Anonymoussaid. Leave your thoughts in a comment. If you’ve tried Five Whys, please share your experiences so far. I’ll do my best to help.) Great article as always, Eric.
In fact, the curse of productdevelopment is that sometimes small things make a huge difference and sometimes huge things make no difference. When we’re optimizing, productdevelopment teams encounter similar situations. I mean, here we are, paying them to be there, and they won’t use the product!
Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.
Eric, Any thoughts on how forum feedback fits into customer development and agile productdevelopment? Youve probably addressed this in the past, but I continue to be blown away by how fast Blizzard reacts to noise in their forums and rapidly makes fixes to the product. . =) November 4, 2008 10:58 PM IMVU said.
Weve got slides , video , audio and twitter commentary. Read the rest. And for those of you who are in Colorado but dont know what my speaking events are like, please take a look at some previous posts. That way, you can know what youre in for in advance. As usual, if youre a reader and can attend, please come say hello.
Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ► January (10) ► 2008 (59) ► December (6) ► November (14) ► October (10) ► September (27) (..)
Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? Q&A with an actual reader The lean startup comes to Stanford You don't need as many tools as you think The three drivers of growth for your business mode.
Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ▼ July (8) A new way to recruit for (and find) startup jobs Techstars brings The Lean Startup to Boulder Embrace technical debt The Principles of ProductDevelopment Flow 10 years of entrepreneurship Lean Startup fbFund slides and (..)
The economics of these process trade-offs are discussed in the Principles of ProductDevelopment Flow.) Heres an excerpt: In a previous article, we called Toyota’s productdevelopment system the “second Toyota paradox.&# Labels: productdevelopment 5comments: new york web development company said.
Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. As the company grows, this kind of work generalizes into "executing the companys current strategy."
This basic pattern is useful in all aspects of productdevelopment. Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# The basic idea is to avoid building something based on what you think it might need to do in the future.
Lessons Learned by Eric Ries Tuesday, October 6, 2009 A large batch of videos, slides, and audio Ive been trying very hard to avoid turning this blog into a travelogue. Labels: audio , events , slides , startup visa , video A large batch of videos, slides, and audio Ive been trying very hard to avoid turning this blog into a travelogue.
Why vanity metrics are dangerous ► November (1) ► October (7) ► September (9) ► August (8) ► July (8) ► June (7) ► May (8) ► April (5) ► March (11) ► February (10) ► January (10) ► 2008 (59) ► December (6) ► November (14) ► October (10) ► September (27) (..)
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content