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 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. ————-.
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.
The program has to be well staffed so it becomes a seamless and well integrated part of your entire growth engine. There are certain predictable mistakes companies make that can derail customer reference programs before they ever get off the ground. She will drive the program from the beginning. For example: 1.
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.).
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.
Their idea is that consumers will want a subscription service for short form entertainment (10-minute programs) for mobile rather than full length movies. They needed to be sure that what they were building was what customers wanted and needed. He just hired Meg Whitman. the ex-CEO of HP and eBay, as CEO of NewTV.
No trade-up program? No tools to transition your customers data to the new and improved but incompatible product(s)? Congratulations, you’ve just fired your existing customer base. No discount for existing users?
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?
A pair of wake-up-call studies by the Fournaise Marketing Group in London in 2011 and 2012 found that more than 70 percent of CEOs think that their chief marketing officers lack business credibility, lack the ability to generate acceptable growth, and lack the ability to explain how their programs will lead to increased business.
On CustomerDevelopment in a growing company, Wyatt offered the following advice: Wyatt: We''ve employed a number of systems in the organization that keep all of us close to the customer. There are 5-10 customers in our office (or remote) per week for developers, product owners and marketers to speak to and validate learning.
The disadvantage is that its methodology was based on the old waterfall model of productdevelopment and not the agile and lean methods that startups use today. It taught lean theory ( business model design , customerdevelopment and agile engineering) and practice. CustomerDevelopment works outside Silicon Valley.
I Love Business Plan Competitions I had a breakfast with a friend who has founded a few companies in Thailand and started the New Ventures Program at one of their universities. I hate business plan competitions. If you’re text averse like i am, try to diagram these key items and then write-up the diagrams.
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?
One of our first customers was a stock trading company in NY that wanted to host live stock chats. Another customer was my alma mater, Carnegie Mellon University, who was using it to host online class discussions for its distance education program. In a nutshell, ProductDevelopment is about building something.
This series of posts is a brief explanation of how we’ve evolved from ProductDevelopment to CustomerDevelopment to the Lean Startup. The ProductDevelopment Diagram Emerging early in the twentieth century, this product-centric model described a process that evolved in manufacturing industries.
Fueled by data driven research that map out the who behind the buying decisions of your products or services, customer personas can help inform everything from more effective copy to productdevelopment. Mindset – Your customers come to the buying experience with expectations and preconceived notions.
But one of the real advantages from a product point of view is that there’s no legacy to drag along, there’s no revenue to preserve, and there’s no reputation to safeguard. However, once your productdevelops to the point that it can sustain a viable business (congratulations!), Protect Employees and Customers.
Business and Financial Knowledge (7) - Does the product owner understand the economics and financial dynamics of his product? Process Skills: Customer Discovery Process (7) - Customer discovery includes customer interviewing skills, opportunity assessments and understanding of customerdevelopmentprograms.
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.
Understand whether the problem is immediately solvable, requires multiple minimum viable products to test several solutions, or needs more R&D. I noticed that with all of the requirements fixed upfront, instead of having a freedom to innovate, the topic area action teams had become extensions of existing productdevelopment groups.
To promote innovation inside the NGA, they’ve staffed an Enterprise Innovation Office (EIO) to coach, educate and advise the entire agency, from core leadership to the operational edges, with methods and concepts of validated learning through rapid experimentation and customerdevelopment.
To promote innovation inside the NGA, they’ve staffed an Enterprise Innovation Office (EIO) to coach, educate and advise the entire agency, from core leadership to the operational edges, with methods and concepts of validated learning through rapid experimentation and customerdevelopment.
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."
Sloan Foundation , the Sloan School of Management at MIT , the Sloan program at Stanford , and the Sloan/Kettering Memorial Cancer Center in New York. Known as the “Inventor of the Modern Corporation,” Sloan was president of General Motors from 1923 to 1956 when the U.S. If you look around the United States it’s hard to avoid Sloan.
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, 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.
Every marketing communication hire couldn’t wait to produce the next great ad or PR program. Every product marketer thought they should help define the product feature set, etc. In an early stage startup, instead of sales being up front, the point departments are likely to be productdevelopment and customerdevelopment.
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?
In a way it did this, but the opportunities didn't really come until nearly 3 months into the program. Learning programming is hard to do alone. I pick my cofounder's brain almost daily about the inner workings of our product, so that I can be better informed about the tech side of things. What do you guys think?
This is a quote from Leander Kahney’s recently published book on Apple design chief Jony Ive: “In the world according to Steve Jobs, the ANPP would rapidly evolve into a well-defined process for bringing new products to market by laying out in extreme detail every stage of productdevelopment.
As an example, the CrossFit community has more deeply embraced the Membership Economy, and its emphasis on long-term relationships both with and among customers, than nearly any other exercise organization. First, CrossFit makes membership easy by offering one program to everyone, in the form of a short but challenging hour-long workout.
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.
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.
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.
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.
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.
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?
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 Labels: customerdevelopment , lean startup 8comments: Amy 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. The Entrepreneur’s Guide to CustomerDevelopment ► June (3) What is a startup?
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.
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.
Also SJ's obsession with better taste (positively) contributes to the overall productdevelopment process. There are some good anecdotes about Chief Engineers in the Toyota ProductDevelopment Book. Some of these reaffirm that they do indeed validate assumptions through interaction with customers.
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