Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. Case Study: Continuous deployment makes releases n. He previously co-founded and served as Chief Technology Officer of IMVU.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Unfortunately, its easy to lose track of positioning effects when optimizing for a single metric.

Metrics 88

Metrics San Francisco Lean Viral 88

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. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

MARCH 16, 2009

I think Jim Murphys confusion comes where many peoples did, with the XP term "Customer", which was XPs name for the product management role. That naming issue aside, I think its probably good that Scrum and XP didnt really say much about how to manage products. Case Study: Continuous deployment makes releases n.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

NOVEMBER 8, 2008

The book takes its name from Steves theory of the four stages of growth any startup goes through. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Case Study: Continuous deployment makes releases n.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

AUGUST 26, 2009

Accept that many successful companies are going to want to be backed by big-name firms in other cities. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Case Study: Continuous deployment makes releases n. Then, create an encouraging environment for early-stage companies.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. Now, in some situations, this over-selling would lead to a secondary problem, namely, that customers would realize they had been duped and refuse to re-subscribe. 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 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. It strokes your ego.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JULY 2, 2009

Pay attention to whether people are comfortable “naming names&# in the meeting. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Case Study: Continuous deployment makes releases n.

San Francisco 164

San Francisco Lean Technical Review Software Review 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. Even if it shows improvement in some micro metric, does that invalidate the overall design? That was evident in the metrics and in the in-person usability tests. No one feature is to blame.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

JANUARY 19, 2009

Much of what I have found effective is counter-intuitive, because it requires investing more effort in each hire - all in the name of efficiency. This is another sub-optimization caused by incentivizing the wrong metric. Particularly the Continuous Deployment and Split testing posts. The blog is fantastic as well.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JULY 29, 2009

To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment. So far, this is all an academic exercise in naming - but I think it has an important real-world effect. One last thought.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

FEBRUARY 22, 2010

Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. “Who is this guy?&#

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

MARCH 22, 2010

Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. Case Study: Continuous deployment makes releases n. Startups are the lifeblood of our economy.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

SEPTEMBER 10, 2008

Of the techniques he mentioned, I think four are fundamental and critical for any lean startup: TDD (or the even more politely named TATFT ) Continuous integration Automate your deployments Collect statistics The tools to help you do these things are getting better and better every day, but dont confuse tools with process.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

JANUARY 4, 2009

Imagine you want to store data about customers, each of whom has "last name" field in your database. The problem should be familiar to anyone who plays Scrabble: not all letter are equally likely to be used as the first letter of someones name. Give each entity a name. For example, consider this simple scheme.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JUNE 5, 2009

In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics. Luckily, we also discovered that certain other metrics, like LTV and CPA were much better than we initially projected. Case Study: Continuous deployment makes releases n. June 8, 2009 1:16 AM Colin said.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

JULY 30, 2009

I want to thank Techstars for putting this event together and giving me a chance to experience the scene, even if it lacks a name. Building on this, I’ve recently become fascinated with the notion of continuous deployment , a concept that has been popularized by Eric Ries and others. Read the rest.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

DECEMBER 14, 2009

A business that strives for something like this should absolutely be charging money from day one, in order to establish baselines for their two key metrics: CPA (the cost to acquire a new customer) and LTV (the lifetime value of each acquired customer). Case Study: Continuous deployment makes releases n.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

SEPTEMBER 18, 2008

All I see is a name, an icon, a price, the developers name, and a review star-rating. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Case Study: Continuous deployment makes releases n.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 22, 2008

I used to think a giant flat-panel screen that broadcast our companys key metrics would be what was required to get everyone to pay attention to them. Simply put, we upload all the tasks and assign a name to each task. Case Study: Continuous deployment makes releases n. 1 comments: Josh Moore said.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 13, 2010

Lessons Learned by Eric Ries Monday, September 13, 2010 The Superbowl ad test I am a firm believer in the danger of vanity metrics , numbers that give the illusion of progress but often mask the true relationship between cause and effect. Vanity metrics are generally bigger. Vanity metrics. The solution? Is that really news?

San Francisco 154

San Francisco Metrics Lean PR 154

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. At IMVU it’s a core part of our culture to ship.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

FEBRUARY 7, 2010

If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. Case Study: Continuous deployment makes releases n.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Case Study: Continuous deployment makes releases n.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

OCTOBER 23, 2009

Namely, that they agree to use it free of charge if we deliver it to them and it is capable of X, Y and Z. Namely, that they agree to use it free of charge if we deliver it to them and it is capable of X, Y and Z. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

JULY 9, 2009

All the good domain names were taken, all the good ideas were being implemented. If Id bought just a handful of the "best of the rest" domain names that were available at the time (for a whopping $70 each), I probably could have just retired right then. Case Study: Continuous deployment makes releases n.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

OCTOBER 7, 2008

If necessary, consider doing this under a different brand name than the one you are wedded to using. There will always be far more apps that dont make the top lists, no matter what metric is used. Case Study: Continuous deployment makes releases n. Dont do PR upfront, dont put out a press release.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

JULY 31, 2009

lets you post a description of a job without having to reveal the name of the company who is offering it, or the contact information of the hiring manager. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 27, 2010

In fact, we know so much that we already know what they will care enough about (namely, the product’s quality – as opposed to, say, missing features). The second misunderstanding is a concern for what will happen if things turn out exactly as we originally predicted (namely, badly). No vanity metrics should be looked at.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

AUGUST 1, 2009

In talking with Mary Poppendieck about it, she said that the Chief Engineer role at 3M was called a "Product Champion" The name is less important than understanding the depth of competence that this person has, and what it takes to build it. Case Study: Continuous deployment makes releases n.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

OCTOBER 20, 2008

But we were cutting corners in the development methodology as well as in the code, in the name of increased speed. a is name, b is address, and c is tax percentage. Case Study: Continuous deployment makes releases n. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JUNE 22, 2009

Leading up to a pivot, each cycle, despite our best efforts, the metrics werent good enough. Pivotal Labs doesn't carry "Pivot" in its name by accident. I'm glad there's a 'name' for this part of the process Eric. Case Study: Continuous deployment makes releases n. It was painful.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

MARCH 13, 2009

Who doesnt want to see their name in print? Know what the success metrics are for the launch. Now that were beginning our first marketing, the key partners we need have heard our name long enough to trust us. Case Study: Continuous deployment makes releases n. See if their answer is about tactics or strategy.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

JULY 13, 2009

It moves at a rapid clip, each argument backed up with the relevant math and equations: marginal profit , Littles law , Markov processes , probability theory , you name it. Case Study: Continuous deployment makes releases n. The book is structured as a series of principles, logically laid out and briefly discussed - 175 in all.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

OCTOBER 26, 2009

In previous posts, I’ve mentioned quite a few of these, including these most important ones: having engineers post on the forums in their own name when they make a change routinely split-testing new changes routinely conducting in-person usability tests and interviews Net Promoter Score Each of these techniques is fundamentally bottoms-up.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. Every experiment has to be evaluated based on a single standard report of 5-10 (no more) key metrics. True split-test experiments are easy to classify as successes or failures, because top-level metrics either move or they don’t.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133