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
CustomerDevelopment is a technique startups use to quickly iterate and test each part of their business model. How you execute CustomerDevelopment varies, depending on your type of business. In my book, “ The Four Steps to the Epiphany ” I use enterprise software as the business model example.
Todd Branchflower took my Lean LaunchPad class having been entrepreneurial enough to convince the Air Force send him to Stanford to get his graduate engineering degree. It was only after returning to Stanford and taking the Lean Launchpad class that I became convinced that a radically different, customer-centric approach was the solution.
Eric Ries was kind enough to invite me to speak at his Lean Startup Conference. In the talk I reviewed the basic components of the Lean Startup and described how we teach it. 3:36 The 3 Components of the Lean Startup. 6:00 Teaching startups & companies Lean: The Lean LaunchPad class.
The Lean LaunchPad Class. You may have read my previous posts about the Lean LaunchPad entrepreneurship class. The class teaches founders how to dramatically reduce their failure rate through the combination of business model design, customerdevelopment and agile development using the Startup Owners Manual.
A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.
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 product development team. Do you fix bugs before writing code? Please leave feedback!)
Over the years Dino and I brainstormed about how Lean entrepreneurship would affect regional development. Success depends on finding startups that have identified acute customer pains in large markets where conditions are ripe for a new entrant. The cloud , open-source development tools and web 2.0
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. Four Steps primarily centers its stories and case studies on B2B hardware and software startups.
It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.
Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.
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. I want to tell you a story about how a team pivoted and succeeded by synchronizing product and customerdevelopment. Filed under: CustomerDevelopment.
Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. If we accept the verdict of customers instead of pundits, I think these claims are easy to dismiss.
Each specialist takes up his part of the spec (UI, middleware, backend) and cranks out code. So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. In exchange, the team agrees to show each piece of working code to the product manager for his approval.
Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. For software, the easiest batch to see is code.
CustomerDevelopment We were starting Epiphany, my last company. I was out and about in Silicon Valley doing what I would now call Customer Discovery trying to understand how marketing departments in large corporations worked. This is the pivot, a crucial tactical maneuver for the lean startup [.] Are These Your Slides?
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. but it is so important to see what your customers do in their daily lives. It was Salesforce.com.
I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. But there is more to technical debt than just the interest payments that come due. Unfortunately, customers hated that initial product.
Today, I want to introduce you to a new concept for starting and growing successful companies: Lean Planning™. Before I dive too deeply into the Lean Planning methodology, it makes sense to talk about its history and where it comes from. Lean Planning is born.
for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development.
Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# This basic pattern is useful in all aspects of product development. The Entrepreneur’s Guide to CustomerDevelopment ► June (3) What is a startup?
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. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric.
Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups.
Kent is a significant figure in the field of softwaredevelopment. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of softwaredevelopment. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Expo SF (May.
Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.
Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.
Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.
I was the junior guy on a project team; I was called in to do some technical duediligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. And like feedback on a simple microphone sound system, this would occasionally boil over into screeching.
When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. He throws off volumes of code, and it works.
Getting features and fixes into hands of users was the greatest priority - a test environment would just get in the way and slow down the validation coming from having code running in production. As the product matured, they were able to ratchet up the quality to prevent regression on features that had been truly embraced by their customers.
Filed under: CustomerDevelopment , Venture Capital | Tagged: Entrepreneurs « CustomerDevelopment Manifesto: Market Type (part 4) CustomerDevelopment Manifesto: The Path of Warriors and Winners (part 5) » 16 Responses Jon Ziskind , on September 14, 2009 at 9:19 am Said: Steve – Great post and really great advice.
Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.
Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. I went to the conference thinking that I was well grounded in the basics of the Lean Startup approach and that attendance would hone the edges of that understanding.
At IMVU , these were quite common (after all, were shipping code 50 times a day). They are collected and reviewed after an appropriate interval (e.g. In response to Sean - Intel still runs a very formal process of setting expectations, evaluating employees and reviewing progress on a quarterly basis. love your openness at IMVU.
Within these applications how did our customers spend their day? And since the card was useless without any application software, what other software products did they use on it? What reviews did they trust? No one remembered our ads, saw our reviews or had read a positive article about us. Which ones?
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? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Can I send you a review copy?
Lean Business: Capacity Management, Overhead, and Your Business – [link]. Bad CustomerDevelopment Questions and How to Avoid My Mistakes – [link]. How You Can Benefit from All Your Stress | Heidi Grant Halvorson – Harvard Business Review – [link]. Ray Fisman-Harvard Business Review – [link].
Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and codereviews more seriously than any other company Ive even heard about. The Lean Startup Intensive is tomorrow at Web 2.0.
I couldn’t write a single line of code, and I didn’t have any clue how to start a business. Four books helped me out a lot over the last few years: Four Steps to the Epiphany by Steve Blank, Running Lean by Ash Maurya, The Four Hour Workweek by Timothy Ferris and Rework by Jason Fried & David Heinemeier Hansson. Learn to code.
Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. Step 1: Start with a lean plan. I started UpKeep after seeing and using traditional enterprise software. Use your knowledge of an industry to solve a problem. “I
Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. This shift allowed us to crank out working software quickly as a service.
His most recent company, Filtrbox, participated in the inaugural Techstars class (Techstars Boulder 2007) and was a win for all parties involved; Filtrbox was acquired in 2010 by Jive Software (NASDAQ: JIVE). One of them used to be a lead developer at [insert hot consumer tech company here]. In startup time, that feels like forever.
And do your customerdevelopment. I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries. These quotes are, as is my custom, straight from twitter.
Each of these four currencies represents a way for a customer to “pay&# for services from a company. A great product enables customers, developers, partners, and even competitors to exchange their unique currencies in combinations that lead to financial success for the company that organizes them.
In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. I believe it is a full, company-wide turn through the OODA loop (for a software business, see especially Ideas-Code-Learn ). CustomerDevelopment Engineering : techniques for accelerating your product development.
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