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
I was in New York last week with my class at Columbia University and several events made me realize that the CustomerDevelopment model needs to better describe its fit with web-based businesses. In it, I got asked a question I often hear: “What if we have a web-based business that doesn’t have revenue or paying customers?
Chasing funding versus chasing customers and a repeatable and scalable business model, is one reason startups fail. ProductDevelopment – Getting Funded as The Goal In a traditional productdevelopment model, entrepreneurs come up with an idea or concept, write a business plan and try to get funding to bring that idea to fruition.
CustomerDevelopment is all about gathering a list of what features customers want by talking to them, surveying them, or running “focus groups.” As the engineers were busy rearchitecting the original Stanford MIPS chip into a commercial product, one of my jobs was to find out what features customers wanted.
Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customerdevelopment? When we build products, we use a methodology. But too often when its time to think about customers, marketing, positioning, or PR, we delegate it to "marketroids" or "suits." a roadmap for how to get to Product/Market Fit."
I was talking with an early-stage founder who has a product vision and wants to get it built. He wanted to get input from me on what he's doing, and he wants to begin to ask developers what it would take to build his product. Me : Product definition, use cases, feature list, wireframes, comps, really whatever you have.
Lessons Learned by Eric Ries Sunday, September 7, 2008 CustomerDevelopment 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.
I believe it is the best introduction to CustomerDevelopment you can buy. As all of you know, Steve Blank is the progenitor of CustomerDevelopment and author of The Four Steps to the Epiphany. You can imagine how well that worked. On the minus side, that has made it a wee bit hard to understand.
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.
Not because they have a conversion problem but because they never really nail the product or how to market it. This is a customerdevelopment problem. So What is CustomerDevelopment? The core idea behind customerdevelopment is that the assumptions you make about a target market are only guesses.
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."
Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customerdevelopment 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.
Long before there was the Lean Startup, Business Model Canvas or CustomerDevelopment 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.
What if we could increase productivity and stave the capital flight by helping Life Sciences startups build their companies more efficiently? Quite a few of the teams were building biotech, devices or digital health products. Filed under: CustomerDevelopment , Lean LaunchPad , Science and Industrial Policy , Teaching.
I was having coffee with a former student who was complained that my idea of building a first product release with a minimum feature set was a bad idea. One of the principles of CustomerDevelopment is to get out of the building and understand the smallest feature-set customers will pay for in the first release.).
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.
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.
The cloud , open-source development tools and web 2.0 Startups still need capital to scale once they find good product-market fit and a repeatable-scalable business model.). Filed under: CustomerDevelopment , Lean LaunchPad , Science and Industrial Policy , Venture Capital. Valley-sized VC funds don’t work.
Once upon a time every great organization was a scrappy startup willing to take risks – new ideas, new methods, new customers, targets, and mission. If they were a commercial company, they figured out product/market fit; or if a government organization, it focused on solution/mission fit. Process Versus Product.
Reading the NY Times article “ Jeffrey Katzenberg Raises $1 Billion for Short-Form Video Venture, ” I realized it was time for a new startup heuristic: the amount of customer discovery and product-market fit you need to find is inversely proportional to the amount and availability of risk capital. ” Fire, Ready, Aim.
Founders that learn are more successful : Startups that have helpful mentors, track metrics effectively, and learn from startup thought leaders raise 7x more money and have 3.5x more likely to successfully scale with sales driven startups than with product centric startups. Startup Genome Report. Some of their key findings : 1.
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 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.
The application of agile development methodologies which dramatically reduce waste and unlock creativity in productdevelopment. See CustomerDevelopment Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the CustomerDevelopment process.
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?
The other departments in marketing gave the same answers; the product-marketing department said their job was to write data sheets. To do that we will create end-user demand and drive it into the sales channel, educate the channel and customers about why our products are superior, and help Engineering understand customer needs and desires.
He’s a founder of Andreessen Horowitz, which has backed Facebook, Skype, Jawbone, and dozens of other companies whose products you use. And the whole site was developed in just 9 weeks. Ben Horowitz ’s book The Hard Thing About Hard Things is driving the conversation around startup management this year. Eric Ries will interview him.
Vinod Khosla Founder Dave McClure Founding Partner Eric Ries Author Steve Blank Serial Entrepreneur & Professor Todd Park CTO Travis Kalanick CEO & Co-Founder Joe Zadeh Director of Product Sam Shank Co-Founder & CEO NEW! Seth Sternberg Co-Founder & CEO Scott Chacon CIO Kevin Hale Senior Product Manager NEW!
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.
It’s Not a Conversion Problem, It’s a CustomerDevelopment Problem. Not because they have a conversion problem but because they never really nail the product or how to market it. This is a customerdevelopment problem. So What is CustomerDevelopment? Change who your product is for.
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.
Metrics – Mine is Bigger Than Yours The first thing SuperMac needed to do was to change how our potential color desktop publishing customers viewed our products versus our competitors’ products. Over the years marketers have found that using numbers to compare yourself to other products works well.
Each has its own iterative process: customerdevelopment and agile development respectively. As Steve writes in the Four Steps to the Epiphany , we always seek to find a market for the product as currently specified , not conduct a focus group to tell us what the spec should be. It was painful.
Instead of making a few dollars per sale and hoping for thousands of sales, you sell to only a few customers, and charge much higher rates. My Obsession With The Product - Feld Thoughts , May 3, 2010 For some reason I’ve been doing a lot of interviews lately. They’re deep into CustomerDevelopment ,” he said. Here’s why.
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.
Before setting out on his own, Dan held various product, research, and operations roles at Salesforce , SurveyMonkey , Forrester Research , and The Ladders. Additionally, he has an extensive background in building and launching consumer products at Seen, Clearwish (founder), and Woods Industries. If you can’t hear the clip, click here.
Was SuperMac attempting to introduce radically new products and create a new market ? Was the company attempting to be a low cost provider by introducing cheaper products to an existing market? Was the company attempting to introduce faster and better products to an existing market? No, not really.
Palantir is a deep technical play and we had a lot of code to write just to fill out the product vision that we had already validated with potential customers; it took us two straight years of development to go from early prototypes to software that could be used in production. So what was going on?
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. This is precisely the dilemma that the doctrine of minimum viable product is designed to solve.
At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. Instead, we try to accelerate with respect to validated learning about customers. There are often counter-intuitive changes in customer behavior that depend on little details.
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. What’s going on?
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.
When I try to unpack what people mean by the question, heres my best take on what they are asking: "Look, Steve Jobs doesnt go out and ask customers what they want. He doesnt put out crappy, buggy products and then ask for feedback. He tells customers what they want, and he gets it right. We stopped production for five months.
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?
This means being really conservative with your cash burn early on until you have clearly found product/market fit. But the best founders I know almost always operate as though they have much less money in the bank, and won’t scale burn until they are super confident in their product/market fit. Experienced founders: B2B.
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