Startup Lessons Learned

SEPTEMBER 22, 2008

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. He also has a discussion of how your choice of business model determines which of these metric areas you want to focus on. Choose one.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development 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 product development. We didnt think wed able to compete with that.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

JUNE 2, 2010

Five Whys has its origins in the Toyota Production System. And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Speed up or slow down?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

APRIL 4, 2010

Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Take a look and let me know what you think.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Both Sides of the Table

MARCH 25, 2016

So when Sam Rosen came to me with the idea of disrupting storage with a product that is priced cheaper than existing incumbents and he could build a product that is a better service I was intrigued. The metrics were good but we wondered how much better they would be when we expanded our product.

Startup 150

Startup Seed Money DC Software Review 150

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. So dont just kill the feature - iterate.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Everyone was in the flow; the team was hyper-productive. In many cases, they did the impossible, building a new product faster, cheaper, and better than anyone could have predicted.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

FEBRUARY 28, 2009

I used to think that investments in metrics were a form of waste. Customers dont care if you have good metrics, only if you have a good product. The only reason we learned the art of metrics-based decision making at IMVU was out of necessity. We set sales targets from day one, $300 the first month.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. My belief is that these lean startups will achieve dramatically lower development costs, faster time to market, and higher quality products in the years to come. July 15, 2009 11:18 PM markmontgomery said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

JANUARY 30, 2009

Build a truly mainstream product. Build the product in stealth mode to build buzz for the eventual launch. The whole company and board play-tested the product to see its new features first hand. Everyone had fun; the product worked. This is why agility is such a prized quality in product development.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 12, 2010

Some of the most active: SF , New York , DC , Chicago - but there are many more listed here. Some of the most active: SF , New York , DC , Chicago - but there are many more listed here. Rich also organized the first Lean Startup Meetup right here in San Francisco. Theres probably one in a city near you.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. This kind of result is typical when you ship a redesign of some part of your product. Without split-testing, your product tends to get prettier over time. First of all, why split-test? One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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. They are on-schedule and on-budget, but their gross metrics are way off.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

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. Nothing made any difference.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Each five whys email is a teaching document. and so forth.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. Almost everything we know today about how to build quality products in traditional management has its origins with W.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

OCTOBER 11, 2009

Lessons Learned by Eric Ries Sunday, October 11, 2009 Innovation inside the box I was recently privy to a product prioritization meeting in a relatively large company. The team spent an hour trying to decide on a new pricing strategy for their main product line. It was fascinating. The whole process had taken.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

SEPTEMBER 2, 2008

Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

AUGUST 2, 2008

Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Take a look and let me know what you think.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

FEBRUARY 8, 2010

Lessons Learned by Eric Ries Monday, February 8, 2010 Beware of Vanity Metrics (for Harvard Business Review) The next article in my series on entrepreneurship for Harvard Business Review is live today. Once again, we revisit the topic of Actionable metrics and their nemesis: Vanity metrics. Remember "metrics are people, too."

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. If you can build cars with it, Im pretty sure you can use it to add agility and flexibility to any product development process.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? In a mature company with a mature product, the goal is to pay for lots of people to come to your website. SEM is a simple idea. chatted once?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

APRIL 7, 2010

At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. For example, I’m a big believer in split-testing.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

JUNE 8, 2009

Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. That’s because many of our reports feed us vanity metrics: numbers that make us look good but don’t really help make decisions. Too much of this data is non- actionable.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

APRIL 9, 2009

But that team may also include product marketers or other in-house customers who can give insight into the impact that solution trade-offs might have on customers. Its not good enough to hit product milestones and conduct usability tests. dalelarson : "Metrics are people, too." Metrics are a key questions startups face.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

MARCH 16, 2009

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. But, over the years I’ve realized that the toughest problem - the one that matters most and was consistently the most challenging - was figuring out what the product backlog should be.

Agile 111

Agile Customer Development Developer San Francisco 111

Seeing Both Sides

MAY 19, 2019

Graduating students hungry to dive into the startup community around the world (aka StartUpLand ) often struggle to select the right, specific opportunity where they can productively start their career. DC : MapBox, Optoro, Sonatype, Vox Media, WeddingWire.

Startup 24

Startup DC India Software Review 24

Startup Lessons Learned

JANUARY 7, 2010

Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Take a look and let me know what you think.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

JUNE 22, 2009

As Steve writes in the Four Steps to the Epiphany , we always seek to find a market for the product as currently specified , not conduct a focus group to tell us what the spec should be. It gave the whole company license to go heads-down building product as fast as possible during the development cycle, acting as a solution team should.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

OCTOBER 4, 2008

Every startup has a chance to change the world, by bringing not just a new product, but an entirely new institution into existence. my startup is Blank Label (www.blank-label.com), which is a provider of custom dress shirts that empowers consumers to become the designer of their own product. November 25, 2009 9:54 AM Danny Wong said.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

JULY 28, 2010

It’s common, perhaps the norm, for startups to pivot like that—to discover that a product is catching on in unintended ways worth pursuing. With 21 employees today, kaChing is devoted to recruiting professional managers and finding product/market fit , first for money managers, then for consumers.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 10, 2008

Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

JULY 5, 2010

The results of the Customer Development process may indicate that the assumptions about your product, your customers and your market are all wrong. They tell them to persist in their dream of building a great product and/or company, no matter what the odds are or what the market might be telling them – success is just around the corner.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

DECEMBER 16, 2009

The foundation of TPS ( Toyota Production System ) is that people need to be (and feel) productive and society needs people to produce value. We are all engaged in creating valuable (we hope) services for society in some form or other and simultaneously meeting our own need to feel significant and productive.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

AUGUST 26, 2009

Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Articulate, inspirational. Learned a lot and enjoyed the discourse.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 12, 2008

Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

Audience 119

Audience San Francisco Continuous Deployment Lean 119