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 Wednesday, December 23, 2009 Why vanity metrics are dangerous In a previous post, I defined two kinds of metrics: vanity metrics and actionable metrics. In this post, Id like to talk about the perils of vanity metrics. My personal favorite vanity metrics is "hits."
We did a quick overview of the product. That earned us the right to ask questions of fact about their department’s mission, goals, operations, volumes, tools, methods, and success metrics. We followed that with an hour-long design review, including disclosure of product limitations. Changes were minor.
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!
We have to manage to learn something from our first product iteration. In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Great Post - could not agree more.
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.
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.
Focus on the output metrics of that part of the product, and you make the problem a lot more clear. I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. Whatever its purpose, try measuring it only at the level that you care about.
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.
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. Startup Lessons Learned - the Conference (April 23.
Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. What good are these metrics if they dont help guide product or business decisions?
This is the first post that moves into making specific process recommendations for productdevelopment. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Labels: productdevelopment Speed up or slow down?
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.
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.)
At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. In fact, the curse of productdevelopment is that sometimes small things make a huge difference and sometimes huge things make no difference. For example, I’m a big believer in split-testing.
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. He wrote it in 2000, and as far as I know has never updated it.
Every board meeting, the metrics of success change. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. And what of the productdevelopment team? Time-to-complete-a-sale is not a bad metric for validated learning at this stage.
Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Take a look and let me know what you think.
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.
I used to think that investments in metrics were a form of waste. Customers dont care if you have good metrics, only if you have a good product. The only reason we learned the art of metrics-based decision making at IMVU was out of necessity. Labels: productdevelopment 4comments: Doug said. Thank you Eric.
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?
Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.
Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Take a look and let me know what you think.
Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. You can even read a cool paper one of our engineers wrote on this approach).
Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Take a look and let me know what you think.
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. Startup Lessons Learned - the Conference (April 23.
Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.
Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Read the rest of The Five Whys for Start-Ups. Speed up or slow down? Speed up or slow down?
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.
dalelarson : "Metrics are people, too." leanstartup ericnsantos : #w2e #leanstartup Metrics should be Actionable, Accessible and Auditable. Metrics are a key questions startups face. Metrics are people too" is a reminder I constantly needed when I was a manager. ericries s talk on Lean Startups absolutely fantastic.
Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.
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.
In order to give people the data they need to apply the strategy, we were very open with our company metrics, making all reports generally available and easy to run. When you think a certain feature will give a 50% boost to a given metric, and it only eeks out a 5% boost, you cant spin that as failure. March 9, 2009 8:35 AM Eric said.
Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.
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.
As a shoestring entrepreneur with a SaaS (well, not really, but sort of) offering that we present to very large companies (think 10K+), I love your common sense suggestions about metrics and testing. My background isnt metrics, but we came to it as a matter of practicality. 4) More posts about metrics, scaling, and online games.
Labels: five whys root cause analysis , productdevelopment 15comments: Anonymoussaid. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Leave your thoughts in a comment. I’ll do my best to help.)
Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Growth - when you have existing customers, the pressure is on to grow your key metrics day-in day-out. And if you neglect maintenance, you may not have a business left at all.
Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Take a look and let me know what you think.
Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Take a look and let me know what you think.
Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Articulate, inspirational. Learned a lot and enjoyed the discourse.
Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.
Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Take a look and let me know what you think.
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.
Despite all the energy invested in talking to authors about the size of their platform, very few gatekeepers have a rigorous set of metrics for measuring it. When I reviewed a recent productdevelopment book, it immediately shot up to Amazon sales rank 300. My blog has over 14000 subscribers, for example. Is that a lot?
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