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 Monday, July 13, 2009 The Principles of ProductDevelopment Flow If youve ever wondered why agile or lean development techniques work, The Principles of ProductDevelopment Flow: Second Generation Lean ProductDevelopment by Donald G. Reinertsen is the book for you.
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."
HR processes, legal processes, financial processes, acquisition and contracting processes, security processes, productdevelopment and management processes, and types of organizational forms etc. In government agencies process versus product has gone further. By then the company has lost the ability to compete as an innovator.
Lessons Learned by Eric Ries Sunday, February 22, 2009 Please teach kids programming, Mr. President Of course, what I really mean is: let them teach themselves. See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding?
The inspection- system GM decided to use it for his fourth-generation system, an 18-month program. Though development was already underway, I kicked-off SyncDev in early November. We did a quick overview of the product. We followed that with an hour-long design review, including disclosure of product limitations.
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.
Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. He also has a discussion of how your choice of business model determines which of these metric areas you want to focus on. Choose one.
In the quest for optimization, A/B tests, metrics, and funnels, we're in danger of losing the fun and value of creative work. When we demand overwhelming customer outcry before committing to the slightest product change, we're in danger of losing the value of creating a cool feature that takes too much effort but people just love.
And this year, we’re going to talk not just about business and productdevelopment, but we’ll be exploring one of the Lean Starutp movements next big frontiers: the role of design. No BS, no vanity metrics, no launches, no PR. And those are just our keynotes! We also have an awesome lineup of case studies. Hope to see you there.
I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. I also owe a great debt to Kent Beck, whose Extreme Programming Explained: Embrace Change was my first introduction to this kind of thinking. (So Learning is better than optimization (the local ma.
Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Unfortunately, positioning our product as an "IM add-on" was a complete mistake.
Their idea is that consumers will want a subscription service for short form entertainment (10-minute programs) for mobile rather than full length movies. Tech IPO prices exploded and subsequent trading prices rose to dizzying heights as the stock prices became disconnected from the traditional metrics of revenue and profits.
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.
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.
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.
Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. 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.
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?
He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content.
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. New channels.
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. Please teach kids programming, Mr. President Work in small batches Continuous deployment with downloads What is a market? .
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.
One of the sayings I hear from talented managers in productdevelopment is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. No vanity metrics should be looked at. No vanity metrics should be looked at.
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their productdevelopment process. Whats wrong with this picture? I can relate to his experience all too well.
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? for Harvard Business Revie.
Its why, at my previous job, we were able to get a new engineer completely productive on their first day. We had a great on-boarding process, complete with a mentoring program and a syllabus of key ideas to be covered. Most engineers would ship code to production on their first day. for Harvard Business Revie.
If done right, a programming interview serves two purposes simultaneously. The technical interview is at the heart of these challenges when building a productdevelopment team, and so I thought it deserved an entire post on its own. Still, a startup productdevelopment team is a service organization.
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.
Today, brands are hiring social media specialists for customer support, crowdsourced productdevelopment, promotions and even leads generation. According to a report released today (embedded below) by Altimeter Group's Jeremiah Owyang, "only 23 percent of social strategists have a formalized program with long-term direction".
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.
Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in productdevelopment. Consider the classic project that was essential to the creation of extreme programming , the Chrysler Comprehensive Compensation System.
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.
Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. for Harvard Business Revie.
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.
This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. It would be hard to argue against this productdevelopment strategy, in general. On an absolute scale, pair programming is probably the most continuous of all feedback loops.
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. Giving rise to three verbs: Implement (programming!) for Harvard Business Revie.
These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. I pick that example on purpose, for two reasons: 1) most of the companies I work with deal with this problem and yet 2) almost none of them have any kind of training program in place for new employees.
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.
Have you developed any vision of a productdevelopment strategy? And keep in mind that the best option is to develop at least 5 domain names connected to your brand’s name to find an unoccupied domain. Discuss the suitable tools with your development team. Think of your domain name and get hosting. Working hours.
Stage 1: Target the right metrics for an effective long game. In today’s market ( 8,000 martech products alone ), it’s easier to attract the right customer with material they value than it is to chase down and convert a prospect who isn’t ready to buy. Metrics for your demand generation funnel. Demand generation is no exception.
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. Learning is better than optimization (the local ma.
Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Learning is better than optimization (the local ma. for Harvard Business Revie. Take a look and let me know what you think.
I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible.
Leading up to a pivot, each cycle, despite our best efforts, the metrics werent good enough. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? It was painful.
Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Learning is better than optimization (the local ma. for Harvard Business Revie. Take a look and let me know what you think.
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