Startup Lessons Learned

FEBRUARY 22, 2009

Lessons Learned by Eric Ries Sunday, February 22, 2009 Please teach kids programming, Mr. President Of course, what I really mean is: let them teach themselves. 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?

Programming 143

Programming San Francisco Lean Continuous Deployment 143

ConversionXL

APRIL 3, 2019

There are tons of metrics you can monitor: Conversion rate; Bounce rate ; Click-through rate ; Pageviews; Lead captures; Purchase conversion rate. Setting up your experiments for success: Define success metrics. Stefanie Lambert: “Real Talk: Tough Lessons Learned When Building an Optimization Program”. Do your research!

Artificial Inteligence 114

Artificial Inteligence Technical Review Metrics SEO 114

Steve Blank

MARCH 3, 2015

The disadvantage is that its methodology was based on the old waterfall model of product development and not the agile and lean methods that startups use today. Great entrepreneurs are on a search for the truth, no matter how wrong their initial conception is. An important distinction is that these programs are accelerators.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

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 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

ConversionXL

AUGUST 30, 2018

It slows product development. The key is to connect user research to an improved user experience and, in turn, an increase in customer retention, leads, or any other metric for which C-suite members are accountable. Include notes from your internal team that explain how insights are influencing product development.

Design 111

Design Framework Product Development Technical Review 111

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Pretty soon, a soul-searching meeting ensues. 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

APRIL 4, 2010

Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. for Harvard Business Revie.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Unfortunately, positioning our product as an "IM add-on" was a complete mistake.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 15, 2008

I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. I also owe a great debt to Kent Beck, whose Extreme Programming Explained: Embrace Change was my first introduction to this kind of thinking. (So Learning is better than optimization (the local ma.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

AUGUST 3, 2009

We have to manage to learn something from our first product iteration. In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Great Post - could not agree more.

San Francisco 168

San Francisco Product Lean Continuous Deployment 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 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

ConversionXL

OCTOBER 19, 2017

They are responsible for guiding the direction of the program, facilitating the needs of various departments through focused optimization efforts, and perhaps most importantly, serving as a diplomat for CRO to the broader organization. Even if it’s just one metric, the veracity of everything else is immediately thrown into question.

Chad 90

Chad Analytics Technical Review Framework 90

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? Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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? Read the rest of The Five Whys for Start-Ups. Speed up or slow down? Speed up or slow down?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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. Use pilot programs. What’s happening?

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

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

OCTOBER 4, 2008

He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). 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

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. Consider the classic project that was essential to the creation of extreme programming , the Chrysler Comprehensive Compensation System.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JANUARY 30, 2009

Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in product development. As far as I know, there are no products that are immune from the technology life cycle adoption curve.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

OCTOBER 11, 2009

Every experiment has to be evaluated based on a single standard report of 5-10 (no more) key metrics. Any team that creates an experiment must monitor the metrics and customer reactions (support calls, forum threads, etc) while the experiment is in-progress, and abort if something catastrophic happens. It promotes rapid iteration.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

SEPTEMBER 2, 2008

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Thoughts on scientific product development Lo, my 5 subscribers, who are you? for Harvard Business Revie.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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. Giving rise to three verbs: Implement (programming!) for Harvard Business Revie.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. Much better is to infer the right toolkit by searching for commonalities among actually-built experiences. 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.&#

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

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

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. 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.

San Francisco 158

San Francisco Management Software Review Product 158

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

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. No vanity metrics should be looked at. No vanity metrics should be looked at.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

FEBRUARY 10, 2009

This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. It would be hard to argue against this product development strategy, in general. On an absolute scale, pair programming is probably the most continuous of all feedback loops.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

MARCH 28, 2010

Lessons Learned by Eric Ries Sunday, March 28, 2010 Two new scholarship programs for lean startups Thanks to the generosity of sponsors, Im pleased to be able to announce two scholarship programs for upcoming lean startup events. TechWeb has decided to expand this program to provide scholarships for the whole Web 2.0

Lean 109

Lean Programming San Francisco Continuous Deployment 109

ctotodevelopers.blogspot.com

JULY 11, 2012

decide on success metrics, measure, and then decide if additional investment is warranted. If the innovation is successful, then the metrics should help drive the enhancement into the top/right "agile happy place" quadrant. Shifting to a Market, Program, and Platform Organization. agile software development. (46).

Agile 40

Agile Architecture Offshore Software Developers 40

Startup Lessons Learned

AUGUST 8, 2009

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Firmness: A program should not have any bugs that inhibit its function. We owe a lot to this seminal document.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

NOVEMBER 4, 2008

For those interested in getting started with agile or customer development, I thought Id include a few links. My path to lean startups began with Kent Beck and extreme programming. The best resources there are his book Extreme Programming Explained: Embrace Change and the gentle introduction at extremeprogramming.org.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 10, 2008

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Thoughts on scientific product development Lo, my 5 subscribers, who are you? for Harvard Business Revie.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 7, 2008

And if you dont know who your customer is, perhaps some customer development is in order? Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. Seems like a fairly low-cost method of gauging customer interest for a would-be product. Eric -- This is a pretty interesting idea.

Demand 167

Demand San Francisco Lean Continuous Deployment 167