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
After 20 years of working in startups, I decided to take a step back and look at the productdevelopment model I had been following and see why it usually failed to provide useful guidance in activities outside the building – sales, marketing and business development. So what’s wrong the productdevelopment model?
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.
Finally, I’ll write about how Eric Ries and the Lean Startup concept provided the equivalent model for productdevelopment activities inside the building and neatly integrates customer and agile development. Part 4 of the CustomerDevelopment Manifesto to follow.
I asked Tsutsumi-san to write a guest post for my blog to describe his experience with CustomerDevelopment in Japan. After waiting for a week or so for the book to make it to Japan, I was very much shocked how impressed I was by the CustomerDevelopment Model detailed in the book. ————-.
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 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."
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. Its a nice complement on the product engineering side to his customerdevelopment methodology.
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. Its trying to do way too many things at once. I think theyve succeeded.
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.
This is a customerdevelopment problem. By the end of this article, you should have a better understanding of how to develop new products or tweak your existing offerings by working with existing or prospective customers to incorporate their feedback to create viable solutions to their problems, and clearly communicate their value.
I know that this all seems obvious now with the movements started by Steven Blank ( Four Steps of Epiphany ) with the whole CustomerDevelopment processes / Lean Startup movements also popularized by people like Eric Ries. They had decided to take a Digg style approach to productdevelopment. Back then it seemed foreign.
For those of you who have been following the discussion, a Lean Startup is Eric Ries ’s description of the intersection of CustomerDevelopment , Agile Development and if available, open platforms and open source. The CustomerDevelopment process (and the Lean Startup) is one way to do that.
If this is your attitude, your conception of tech support is completely backwards and you're missing out on important channels for marketing, productdevelopment, and sales. Yes, I'm flagrantly paraphrasing the legendary Kathy Sierra , but the idea applies as much to tech support as to productdevelopment.).
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.
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.
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.
New strategic direction in companies with loyal customers have different consequences then when you had no customers Acquiring new customers are a lot more expensive that converting existing ones. on July 9, 2010 at 12:50 pm Said: [.] Reply Leave a Reply Click here to cancel reply. Order Here. To Order Outside of the U.S.
It’s Not a Conversion Problem, It’s a CustomerDevelopment Problem. 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. Website Analysis.
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.
Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.
Sometimes we have the attitude that the ProductDevelopment team is the one responsible for Activation and Retention (hey, a great product would do that naturally) or that the Marketing team is responsible for Revenue and Referral (hey, go get me some money or free customers already).
If you cant find any , maybe that means you havent figured out who your customer is yet. And if you dont know who your customer is, perhaps some customerdevelopment is in order? Labels: customerdevelopment , search engine marketing 13comments: Jim Lindstrom said. What is customerdevelopment?
I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customerdevelopment process. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. Check your assumptions, what went wrong?
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.
Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. I hope you take something of value from this blog. Eric, love the blog. Thanks for your professional blog. So thats me, your author.
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. Ive written about it on our developmentblog at [link] October 6, 2008 3:34 PM Chris Hondl said.
Lessons Learned by Eric Ries Saturday, August 1, 2009 The Steve Jobs method Image via CrunchBase Its been a long time since I did a post that was primarily a link to another blog with commentary, but I came across something today that I really want to share. Plus, the premise of the question misunderstands the lean startup, too.
Each has its own iterative process: customerdevelopment and agile development respectively. In those cases, the product may stay mostly the same, but the positioning, marketing, and - most importantly - prioritization of features changes dramatically. I am very happy while reading your blog. I like this term.
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.
Next, you have to deal with the daily crisis of productdevelopment and acquiring early customers. And here’s where life gets really interesting, as the reality of productdevelopment and customer input collide, the facts change so rapidly that the original well-thought-out business plan becomes irrelevant.
This post describes a solution – the CustomerDevelopment Model. In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for productdevelopment activities inside the building and neatly integrates customer and agile development.
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.
Your blog post has provided a lot of useful insights for me which I’ve been implementing. Blog at WordPress.com. I was between my 7th and 8th and final startup; licking my wounds from Rocket Science, the company I had cratered as my first and last attempt as a startup CEO. Would you mind sharing them?
If you’re a startup raising money or just want to see your name online, there’s not a better blog on the web. Blog at WordPress.com. Reading this TechCrunch post made me remember the first time I saw someone confront a worldview they didn’t expect. Discovering that your worldview is wrong or mistaken can be a life-changing event.
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.
This post describes how the traditional productdevelopment model distorts startup sales, marketing and business development. The meaning of alpha test , beta test, and first customer ship are pretty obvious to most engineers. Here’s what the productdevelopment diagram looks like from a sales perspective.
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. The Entrepreneur’s Guide to CustomerDevelopment ► June (3) What is a startup? Interesting post.
Market Risk vs. Invention Risk - Click to Enlarge For companies building web-based products, productdevelopment may be difficult, but with enough time and iteration engineering will eventually converge on a solution and ship a functional product - i t’s engineering, not invention.
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. Good luck, engineering manager. It was painful for a lot of people.
How To Land a Job at Google (or elsewhere) - FairSoftware's Blog , November 9, 2010 It’s been 11 years now that the obvious hit me: the best way to land a job is to do the job , not talk about it. few years ago I also started following Alexander Osterwalder in his blog about his Business Model Generation -mantra. Give yourself a month.
They couldn’t keep up with the fast productdevelopment times that were enabled by using standard microprocessors. So their management teams were insisting that they OEM (buy from someone else) these products. The answer depends on your answer to two questions: which step in the CustomerDevelopment process are you on?
Balancing competing objectives is a recurring theme on this blog - its the central challenge of all management decisions. 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. What is customerdevelopment?
Those rates gave us a map that told us a lot about our customers; insights that proved stable even when the company grew orders of magnitude bigger. Only much later did I realize that this was an application of customerdevelopment to online marketing. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you?
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. The Entrepreneur’s Guide to CustomerDevelopment ► June (3) What is a startup?
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