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, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. MVP, despite the name, is not about creating minimal products. We have to manage to learn something from our first product iteration.
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."
In other parts of the world, innovators often need to develop both the ultimate product or service, as well as the enabling infrastructure that underpins it. With a singular focus on building unicorns, very rapid growth has been a key metric. Build for sustainability and resilience, as well as growth.
Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. The product manager was clearly struggling to get results from the rest of the team. Lets start with what the product manager does.
In other parts of the world, innovators often need to develop both the ultimate product or service, as well as the enabling infrastructure that underpins it. With a singular focus on building unicorns, very rapid growth has been a key metric. Build for sustainability and resilience, as well as growth.
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. We didnt think wed able to compete with that.
Building a minimum viable product, with customer validation. Minimum viable products (MVPs) are recommended for validating the market, with iterative enhancement to quickly meet market feedback. Building your public image and presence should start even before productdevelopment, through your website, logo, and blogging.
Long before there was the Lean Startup, Business Model Canvas or Customer Development there was a guy in Santa Barbara California who had already figured it out. Frank Robinson of SyncDev has been helping companies figure out their minimum viable product and pivots since 1984, long before I even knew what it meant. Massacre at IBM.
New technologies emerge daily and bring ingenious products to the world. It’s generally accepted to praise developers and designers for bringing these products to life but there is usually someone else behind the concepts and ideas. Product managers should also understand the company’s goals. necessary product.
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.
If you buy into the argument that a strong board can actually help you then this post will lay out how to help you have more productive meetings by preparing properly in advance. Often board members themselves don’t do the work to say “what metrics would we like to see.” This is part of a broader series on Board Meetings.
Creators of new products in environments of extreme uncertainty, startups face enormous risks. Through rapid experimentation, short productdevelopment cycles, and rigorous measurements of the right metrics, they can ascertain what customers really want. As a startup owner, what can you do to improve your chances?
Inconsistent startup outsource 4-5 times as much of their productdevelopment than consistent startups. In discovery phase 60% of inconsistent startups focus on validating a product and 80% of consistent startups focus on discovering a problem space. Startup Genome Compass.
In this period (less than 2 years) he has brought on incredibly talented senior execs is sales, marketing, product management, client services, finance, vp engineering and more. By being so metrics driven we can have a lot more quantifiable and objective discussions at board meetings and at mid-point reviews. . Further Reading.
A new product launch is never easy, even if you’re a well-known marketer or entrepreneur. Product Hunt, if used properly, can be an effective way to launch a new product in a crowded market. If you’ve chosen—or are thinking about choosing—Product Hunt as your platform, here are the steps to improve your chances of success.
Building a minimum viable product, with customer validation. Minimum viable products (MVPs) are recommended for validating the market, with iterative enhancement to quickly meet market feedback. Building your public image and presence should start even before productdevelopment, through your website, logo, and blogging.
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.
In my experience, the majority of changes we made to products have no effect at all on customer behavior. This kind of result is typical when you ship a redesign of some part of your product. Without split-testing, your product tends to get prettier over time. First of all, why split-test? One last note on reporting.
This will include the first version of many critical processes that can be split out later, including market opportunity, requirements, product definition, business model, sales process, and organization. Productdevelopment process. If you are contracting or outsourcing, this is even more important. Funding process.
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. (See
Over 13 years ago, in March of 2000, I wrote a blog post titled “ The Most Powerful Internet Metric of All. ” The key thesis was this: if an Internet company could obsess about only one metric, it should be conversion. As such, it is time to pound the table again – conversion is by far the most powerful Internet metric of all.
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. Its the ultimate high-engagement product. You can learn more about the event here.
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.
It outlines four major growth strategies: market penetration , market development , productdevelopment , and diversification. The goal of market penetration is to leverage new tactics to increase product sales , including existing customers and new customers within existing markets. Productdevelopment.
Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Each five whys email is a teaching document. and so forth.
This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. 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?
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.
If the CEO wants to completely change the product in order to serve a new customer segment, you need someone in the room who can digest the needs of the new (proposed) business, and lay out the costs of each possible approach. Labels: productdevelopment 15comments: mukund said. Have you worked with or for a great CTO?
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.
Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. We know some products succeed and others fail, but the reasons are complex and the unpredictable. a roadmap for how to get to Product/Market Fit." Whats wrong with this picture?
Most industries have touched their peak, matured, and there is little room to improve in the world of homogenous products, similar marketing, and standardized, efficient processes. Capturing and analyzing data enables companies to get insights that benefit their companies in cost-saving, relevant marketing, productdevelopment, etc.
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. Unfortunately, customers hated that initial product.
Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. Nothing made any difference.
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. Similar results apply in product management, design, testing, and even operations. For software, the easiest batch to see is code.
This is the first post that moves into making specific process recommendations for productdevelopment. Everyone was in the flow; the team was hyper-productive. In many cases, they did the impossible, building a new product faster, cheaper, and better than anyone could have predicted.
Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.
If you don’t understand your key financial metrics, you have no way of monitoring your business’s health—and you risk mingling assets, incurring penalties for filing taxes late, overlooking expenses, and running into difficulties paying bills and employees, just to mention a few! Each article will give you: A brief definition of the metric.
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. We set sales targets from day one, $300 the first month.
Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? In a mature company with a mature product, the goal is to pay for lots of people to come to your website. SEM is a simple idea. chatted once?
Without producing physical goods, every entrepreneur now can succeed in selling other manufacturers’ products online. 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.
Eric has talked often about recognizing a startup as an organization designed to create a new product or service under conditions of extreme uncertainty. Most commonly, that’s uncertainty about whether you can build the product at all (what MBAs call “technical risk”) or whether anybody will use or buy it (“market risk”). in ten years?
It slows productdevelopment. The key is to connect user research to an improved user experience and, in turn, an increase in customer retention, leads, or any other metric for which C-suite members are accountable. A non-scientific approach that bases product decisions on the opinions of one or two users is useless.
At NextView Ventures we have written many pieces about venture capital — how to raise it, build your business, engage with investors, iterate your product, navigate expanding industries, etc. Rethinking the Standard Fundraising Deck “I’d make it crystal clear what your product actually does. VCs sure do love writing.
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. One of those is an over-emphasis on split-testing.
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