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. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

APRIL 25, 2011

And this year, we’re going to talk not just about business and product development, but we’ll be exploring one of the Lean Starutp movements next big frontiers: the role of design. For readers of this blog, Steve needs no introduction. No BS, no vanity metrics, no launches, no PR. And those are just our keynotes!

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Startup Lessons Learned

SEPTEMBER 15, 2008

Focus on the output metrics of that part of the product, and you make the problem a lot more clear. I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. Whatever its purpose, try measuring it only at the level that you care about.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 6, 2008

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. I hope you take something of value from this blog. Eric, love the blog. Thanks for your professional blog. So thats me, your author.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

OCTOBER 5, 2008

But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said. Ive written about it on our development blog at [link] October 6, 2008 3:34 PM Chris Hondl said.

San Francisco 158

San Francisco Management Software Review Product 158

abovethecrowd.com

OCTOBER 1, 2013

Over 13 years ago, in March of 2000, I wrote a blog post titled “ The Most Powerful Internet Metric of All. ” The key thesis was this: if an Internet company could obsess about only one metric, it should be conversion. As such, it is time to pound the table again – conversion is by far the most powerful Internet metric of all.

Metrics 93

Metrics Conversion Internet Acquisition 93

Startup Lessons Learned

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. What good are these metrics if they dont help guide product or business decisions?

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development 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: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. And what of the product development team? Time-to-complete-a-sale is not a bad metric for validated learning at this stage.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development 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.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. Startup Lessons Learned season one : Every post from the blogs first year in print form. Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

NOVEMBER 7, 2008

This is one of the blog we posted about how some company is doing SEO to promote the website. To help find the right keywords, Ive written an article on my blog Web Startup Help that details How to Do Keyword Research for startups. This post has been removed by a blog administrator. What is customer development?

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 10, 2008

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. He wrote it in 2000, and as far as I know has never updated it.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. A book I am looking forward to read after reading you blog. This is a common mistake.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 13, 2008

Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. What is customer development?

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JULY 28, 2010

Lessons Learned by Eric Ries Wednesday, July 28, 2010 Case Study: kaChing, Anatomy of a Pivot (The following guest post is a new experiment for this blog. And if you’re a regular reader of this blog, you may know that IMVU started out as an instant messaging add-on. kaChing has been very active in the Lean Startup movement.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

MARCH 3, 2009

In order to give people the data they need to apply the strategy, we were very open with our company metrics, making all reports generally available and easy to run. When you think a certain feature will give a 50% boost to a given metric, and it only eeks out a 5% boost, you cant spin that as failure. March 5, 2009 8:56 AM Eric said.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. Labels: product development 4comments: Doug said. Thank you Eric.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

APRIL 4, 2010

blog comments powered by Disqus Newer Post Older Post Home Subscribe via email Blog Archive ▼ 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Startup Lessons Learned - the Conference (April 23.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 18, 2008

And since I have a blog, I have a way to ask questions directly to you. Heres what I want to know: First of all, the NPS question : On a scale of 1-10 (where 10 is most likely), how likely is it that you you would recommend this blog to a friend or colleague? Eric, great blog. Im keeping your blog. How annoying!)

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

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

APRIL 29, 2013

Or you could work with the writer to create a blog, see if it can attract a readership, and then test whether those readers will pre-order a book—which you can do before you’ve put ten seconds of effort into creating a print volume. You can give advice about applying Lean Startup ideas to business areas other than product development.

Lean 165

Lean Technical Review Startup Software Review 165

Up and Running

FEBRUARY 20, 2015

If you don’t understand your key financial metrics, you have no way of monitoring your business’s health—and you risk mingling assets, incurring penalties for filing taxes late, overlooking expenses, and running into difficulties paying bills and employees, just to mention a few! Each article will give you: A brief definition of the metric.

Metrics 60

Metrics Burn Rate .Net Churn Rate 60

Startup Lessons Learned

APRIL 9, 2009

Answering that question is what Im striving to do on this blog (and at future webcasts and workshops ). dalelarson : "Metrics are people, too." leanstartup ericnsantos : #w2e #leanstartup Metrics should be Actionable, Accessible and Auditable. Metrics are a key questions startups face. No engineering team. Great post.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

SEPTEMBER 13, 2008

There is much work that I need to do (the only developer so far) before we have something customers can use. 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.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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

JUNE 2, 2010

Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Startup Lessons Learned season one : Every post from the blogs first year in print form.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

YoungUpstarts

JULY 16, 2019

Have you developed any vision of a product development strategy? And keep in mind that the best option is to develop at least 5 domain names connected to your brand’s name to find an unoccupied domain. At least 6 team members should participate in your product development. What slogan do you see there?

eCommerce 113

eCommerce Software Developers Software Development Hosting 113

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

AUGUST 24, 2009

Despite all the energy invested in talking to authors about the size of their platform, very few gatekeepers have a rigorous set of metrics for measuring it. My blog has over 14000 subscribers, for example. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. Is that a lot?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

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.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

JANUARY 12, 2010

Beyond my own efforts on this blog ( and more ), there is now an amazing variety of resources for lean startup practitioners. When I first started blogging, the startup blogging mafia immediately came to meet me and find out who I was: Dave McClure , Andrew Chen , Sean Ellis and Venture Hacks. Have a favorite who I overlooked?

Lean 146

Lean San Francisco Wiki Startup 146