Startup Lessons Learned

JULY 6, 2009

Lessons Learned by Eric Ries Monday, July 6, 2009 Lean Startup fbFund slides and video As a follow-up to my previous post on my talk for fbFund at Facebook , there was enough interest in watching video of the talk that I have finally uploaded it using Apples MobileMe. If you want to see the original video, use the link above.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

JULY 5, 2010

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Hearpreneur

SEPTEMBER 22, 2021

It drives media attention and fosters customer retention rate, which is why most companies strive to have it in their mission statement. It seeks to solve customer problems in a better and modern way and helping such companies edge the competition. Before the COVID-19 epidemic, this platform was a great video conferencing tool.

Technical Review 120

Technical Review Entrepreneur Software Review SEO 120

Startup Lessons Learned

OCTOBER 26, 2009

Lessons Learned by Eric Ries Monday, October 26, 2009 A real Customer Advisory Board A reader recently asked on a previous post about the technique of having customers periodically produce a “state of the company&# progress report. Many companies seek to involve customers directly in the creation of their products.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. They are gaining valuable customer data.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

AUGUST 3, 2009

Below youll find the video of my remarks as well as the full slides embedded below. First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. But I wanted to say a few words first. Thank you.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 14, 2008

Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Youll know when the person youre talking to is not a potential customer - they just wont understand what youre saying.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Labels: customer development , lean startup 8comments: Amy said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Hearpreneur

JANUARY 15, 2021

Bespoke by definition means made for a particular user/customer. If you don’t, Google “cats in boxes” and you’ll get about 121 million hits, mostly goofy photos and videos of cats squeezing into boxes they clearly have no business squeezing into. 19- As suggested by a customer. Thanks to Danny Pollack, Bespoke Extracts !

Naming 123

Naming Entrepreneur Mexico Cofounder 123

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." How to listen to customers, and not just the loud.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

DECEMBER 14, 2009

Lessons Learned by Eric Ries Monday, December 14, 2009 Business ecology and the four customer currencies Lately, I’ve been rethinking the concept of “business model&# for startups, in favor of something I call “business ecology.&# Let’s begin with the four customer currencies. And this is true outside of games.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. Customer development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Hearpreneur

SEPTEMBER 15, 2021

Restaurant owners and employees are being treated extremely poorly by many customers since service has changed with the lack of staffing. It requires instant customer service through social media and chatbots. The customer service industry is also bound to experience abrupt change. Photo Credit: Tyler Rice. 11- Cyber security.

Artificial Inteligence 105

Artificial Inteligence Entrepreneur Technical Review Security 105

Startup Lessons Learned

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. The Entrepreneur’s Guide to Customer Development ▼ June (3) What is a startup?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you. Love to get feedback from authorities.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JANUARY 30, 2009

Here are a few: We know what customers want. By hiring experts, conducting lots of focus groups, and executing to a detailed plan, the company became deluded that it knew what customers wanted. But that was two full years before any customers were allowed to use it. Stealth is a customer-free zone. We can skip the chasm.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

MAY 31, 2010

Sean Murphy has an excellent and comprehensive roundup of resources about the conference: all of the slides, videos, summaries, notes and write-ups are listed on his blog here. All video from the conference is available for free at Justin.tv If not, youd better watch video of his talk ASAP. And then you can buy a t-shirt.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. Some startups avoid getting customer feedback for precisely this reason: they are afraid that if early reactions are negative, theyll be "forced" to abandon their vision. One such practice is to pivot from one vision to the next.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

NOVEMBER 7, 2008

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. We finally settled on a $1.99 Setup a simple website.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 10, 2008

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. . Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

MARCH 25, 2010

Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did). Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did). Firefighting was part of the fun of living on the edge. Expo SF (May. .

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

AUGUST 26, 2009

If you watch the video/audio below, youll get to see some of the questions I was asked after my presentation. And do your customer development. These quotes are, as is my custom, straight from twitter. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time). Read the rest. Expo SF (May.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. Customers dont care if you have good metrics, only if you have a good product. I used to think that investments in metrics were a form of waste.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

APRIL 9, 2009

Rather than use boring section headers, I thought Id just quote from actual customers, in their own words. Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

JUNE 9, 2009

Lessons Learned by Eric Ries Tuesday, June 9, 2009 The Lean Startup Tokyo edition I had a blast speaking at Startonomics Tokyo , which was organized to foster ties between the startup cultures in Japan and Silicon Valley. benjaminjoffe : early adopters of buggy product are visionary customers, sometimes smarter than founders!

Lean 60

Lean San Francisco Japan Continuous Deployment 60

Startup Lessons Learned

NOVEMBER 17, 2008

Lessons Learned by Eric Ries Monday, November 17, 2008 The four kinds of work, and how to get them done: part one Ive written before about some of the advantages startups have when they are very small, like the benefits of having a pathetically small number of customers. Talking to potential customers and competitors customers.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

SEPTEMBER 22, 2008

The law of large numbers (of customers) says you cant help but make at least some money - your valuation is determined by how well you monetize the tidal wave of growth. Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , listening to customers 3comments: hauteroute said. Wouldn't it make more sense to Learn (customer discovery) then proceed to ideas,code, data, implement and measure? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Great points Eric. Expo SF (May. .

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. I went through some of this in bringing agile methodologies to my current firm - except that I am the product manager in question at this case. October 6, 2008 12:17 AM r& said. Expo SF (May. . Expo SF (May.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

AUGUST 1, 2009

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 tells customers what they want, and he gets it right. When a customer tells you how they feel about your ideas, that doesnt tell you anything about your ideas.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

FEBRUARY 10, 2009

Heck, thats what it says right there in the agile manifesto. As Ive argued elsewhere , my belief is that startups (and anyone else trying to find an unknown solution to an unknown problem ) have to measure progress with validated learning about customers. But, unfortunately, startups cant afford to adopt that standard. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

AUGUST 2, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? ► April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0 Expo SF (May.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

OCTOBER 4, 2008

Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. It uses principles of agile software development, open source and web 2.0, The trade-off, though, is a more structured presentation format. Expo SF (May. .

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

NOVEMBER 27, 2013

Eric’s chat with Kent Beck was among our most entertaining webcasts ( video ; iTunes ; SoundCloud ). Kent, a veteran programmer, a founder of the Agile method and the creator of Extreme Programming, came armed with anecdotes and lessons from his own experience, as well as a few questions for Eric. Just, you know, with my bare hands.

Lean 165

Lean San Francisco Cofounder Programming 165