Startup Lessons Learned

APRIL 25, 2011

The Lean Startup movement has made tremendous progress in the past year. If you recall, around this time last year we were still fighting various myths , such as “ lean means cheap ” or that we don’t support having a big, world-changing vision. This year, the word pivot has become over-hyped ( even on TechCrunch ).

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Startup Lessons Learned

SEPTEMBER 15, 2008

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. Expo SF (May. for Harvard Business Revie.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Both Sides of the Table

AUGUST 17, 2014

Feedback driven product development versus visionary (Steve Jobs) driven development. In this clip we discuss why Nanea is a proponent of a lean startup and data driven development methodology. She combines gathering: Quantitative data – data hook implementation, click tracking, A/B testing.

Technical Review 315

Technical Review Leadership Engineer RSS 315

Startup Lessons Learned

JULY 29, 2009

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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

A Smart Bear: Startups and Marketing for Geeks

APRIL 5, 2010

When we demand overwhelming customer outcry before committing to the slightest product change, we're in danger of losing the value of creating a cool feature that takes too much effort but people just love. We're "lean" but we're not stirring hearts. Leave a comment and join the conversation. We're effective but not playful.

Software Review 226

Software Review Metrics Lean Agile 226

Startup Lessons Learned

MARCH 25, 2010

(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. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

MARCH 17, 2009

Lessons Learned by Eric Ries Tuesday, March 17, 2009 Join the Lean Startup discussion at Web 2.0 Expo for free Im honored to announce that my Lean Startup session at the Web 2.0 Everyone else can register to come to both sessions for free, including the Lean Startup talk in the main conference. What does this mean for you?

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. Split-testing is great for figuring out which is which.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Notice that the unit of progress changes as we move from waterfall to agile to the lean startup. The Lean Startup Intensive is tomorrow at Web 2.0.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development 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.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 13, 2008

We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. And then we would use that simple analytics system I mentioned to monitor the conversion rates of customers from each campaign. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

MAY 7, 2009

He summarized that conversation well, so rather than re-tread that material, Ill quote it here: One thing that I was surprised to learn was that IMVU started out with continuous deployment. They were deploying to production with every commit before they had an automated build server or extensive automated test coverage in place.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

JULY 3, 2009

Lessons Learned by Eric Ries Friday, July 3, 2009 Lean Startup fbFund wrap-up Last week I had a real blast meeting with the companies at the fbFund incubator at Palo Alto. The Lean Startup fbFund Edition View more documents from Eric Ries. The Lean Startup Intensive is tomorrow at Web 2.0. Without further ado. Expo SF (May.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. I think Drucker said it best. Expo SF (May.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

JULY 5, 2010

Brant and Patrick undertook a difficult challenge: to provide a generally accessible introduction to Customer Development, without diluting its impact or dumbing-down its principles. It is written in a conversational tone, doesnt take itself too seriously, and avoids extraneous fluff. I think theyve succeeded. I think theyve succeeded.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

MAY 31, 2010

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.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Five Whys has its origins in the Toyota Production System. Five Whys has its origins in the Toyota Production System.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Both Sides of the Table

FEBRUARY 27, 2019

Very few people turn up with a strong sense of “what we should be doing” or ready to lean into a productive conversation The financials were prepared by the VP of Finance / CFO. This can include: Fund raising, product development choices, sales, marketing effectiveness, competition, business development, M&A … whatever.

Stock Options 226

Stock Options Metrics Stock Valuation 226

Startup Lessons Learned

NOVEMBER 14, 2013

Guest post by Lisa Regan, writer for T he Lean Startup Conference. We’ve posted the full program for The Lean Startup Conference , and it includes more than three days of events for Gold pass holders and six days of events for VIP pass holders. On the evening of December 8, Ignite Lean Startup kicks off the conference.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

Startup Lessons Learned

JANUARY 7, 2010

Id be honored to have you join the conversation. The Conversation - Harvard Business Review For most of us, the phrase management science conjures up a decidedly non-entrepreneurial image, and for good reason. Read the rest at The Conversation - Harvard Business Review. Id be honored to have you join the conversation.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

MAY 14, 2009

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. I have a lot of good news to report on this front. You can click here to learn more.

Lean 60

Lean San Francisco Software Review Continuous Deployment 60

Startup Lessons Learned

AUGUST 8, 2009

Lean methods present a third option: to invest in our process so that our design gets more feedback sooner and is more adaptable to changes in purpose. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.) Customer Development is itself an example of SBCE.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

MARCH 29, 2010

Traveling the past year, I have heard loud and clear that its time for the Lean Startup movement to enter its next phase. The way forward requires getting everyone together in a room, and having a conversation about where were headed. Is design important to lean startups? I know one thing for sure: I dont have all the answers.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

OCTOBER 28, 2008

Its different from selling a product, because it is not part of our regular business practice, is not something that relates to our core competence, and tends not to happen in a repeatable and scalable way. Ill exclude those non- lean startups who basically exist for the purpose of raising bigger and bigger sums of money. Expo SF (May.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

AUGUST 24, 2009

So I generally feel right at home in these conversations. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. If they don’t, there are a new breed of lean startups who understand this deep in the bones ready to take their place. Is that a lot? Is that good?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

YoungUpstarts

APRIL 14, 2014

Not too long ago, German software giant SAP blew up the management framework for its 20,000-person development department and replaced it with “mini-teams” of roughly 10 people. As a result, product development time was cut nearly in half in a three-year period.

Agile 196

Agile Leadership Architecture Product Development 196

Steve Blank

JUNE 25, 2009

They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. So their management teams were insisting that they OEM (buy from someone else) these products. The Customer is a Genius Then instead of talking about our products he segued the conversation into their products.

Technology 146

Technology Silicon Valley Fractional VPE Part-Time VPE 146

ConversionXL

FEBRUARY 3, 2022

This philosophy comes from The Lean Startup methodology , which relies on testing hypotheses to better understand your customers’ pain points and goals. It outlines four major growth strategies: market penetration , market development , product development , and diversification. Product development.

Marketing 115

Marketing Framework Metrics Channel 115

Startup Lessons Learned

JANUARY 15, 2010

Two Ways to Hold Entrepreneurs Accountable - The Conversation - Harvard Business Review Way back when the money was doled out, the team made a compelling pitch about the large market that was going to adopt their new innovative product or service. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

JUNE 5, 2009

For example, say that your business model calls for a 4% conversion rate – as ours did initially at IMVU. After a few months of early beta at IMVU, we discovered that our actual conversion rate was about 0.4%. That’s not too surprising, because our product was pretty bad in those days. Expo SF (May.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

ConversionXL

JUNE 14, 2021

Your product or service is likely built of many features or components, but which of those do your customers truly value? Use these conversations to understand the needs and desires your customers are struggling to fulfil. When inviting them to a conversation, tell them you want to hear both the good and the bad. three to five).

Software Review 158

Software Review Audience Differentiation Framework 158

ConversionXL

OCTOBER 7, 2021

These are the four stages of a product we’ll be focusing on. . However, on a more granular graph, the introduction phase would be preceded by a product development stage. This stage is used to determine the viability of your product and confirm when it should go to market. It also gives you a product to market.

Product 142

Product Marketing Software Review Social Media 142

Startup Lessons Learned

DECEMBER 6, 2008

Thats OK; like all lean transformations , you need to undertake this one in small steps. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Expo SF (May.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 8, 2009

Beyond just those who will be hearing about the lean startup for the first time, Im expecting to shake a lot of hands and have a lot of interesting side conversations. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May.

DC 90

DC Washington San Francisco SBIR 90

Steve Blank

MAY 7, 2009

I love business plan competitions (and with my valley-centric bias, I think Berkeley and Stanford have two of the best.) If you are outside of Silicon Valley, you ought to jump into them with both feet. You’ll learn a lot. If you’re text averse like i am, try to diagram these key items and then write-up the diagrams.

Business Plan 160

Business Plan Silicon Valley RSS Venture Capital 160

Startup Lessons Learned

MARCH 24, 2009

Each of those levers -- conversion rate, action/user, msgs/action, etc. -- are important when thinking about how and why users engage with your product. Its the roll-up into one all-encompassing number that guides your product decisions that Im skeptical about, but I see that thats not what youre interested in at all.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

OCTOBER 2, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference. On October 8 at 10a PT, we’ll be talking about bringing Lean Startup methods to established companies, precisely the kinds of businesses that are most resistant to experimentation, even as they desperately need it. That''s hard. That’s Eric Ries’s job.

Lean 167

Lean Startup Agile Leadership 167