Startup Lessons Learned

OCTOBER 16, 2013

But we couldn''t have identified this without having clear metrics (that high bug count) to assess our development process. As Shutterstock has grown, there are a few key elements to our continued development speed: Small, autonomous teams: The more a team can do on their own, the faster they can go.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

JUNE 8, 2009

That’s because many of our reports feed us vanity metrics: numbers that make us look good but don’t really help make decisions. Yet even among those who have access to good actionable metrics, I’ve noticed a phenomenon that prevents taking maximum advantage of data. Case Study: Continuous deployment makes releases n.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

JANUARY 12, 2010

I continue to believe that the explosion of interest in the lean startup has very little to do with me. Recent economic events, technological change, and the rapid diffusion of information about the old models have combined to help us all realize just how important entrepreneurship is - and just how little we really know about it.

Lean 146

Lean San Francisco Wiki Startup 146

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

JUNE 5, 2009

Lessons Learned by Eric Ries Friday, June 5, 2009 It’s a startup, not a spreadsheet Some people, when they start to realize the power of using data to inform their decisions, become obsessed with optimization. In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

OCTOBER 4, 2008

Your blogs are full of rational thoughts and has nuggets of information. It is encouraging to know someone with your reputation and connections is evangelizing truly valuable information for start-ups. Case Study: Continuous deployment makes releases n. Looking forward to more of these. Is ShareThis really necessary?

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JULY 13, 2009

Armed with that information, we can make rational trade-offs. What may be less obvious is that fast feedback also increases the efficiency with which we generate information and learn new things. Team New Zealand completed many more cycles of learning, and they generated more information in each cycle.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

AUGUST 24, 2009

Because of the incredible array of information available, we have a desperate need for filtering mechanisms. Mass blasts of information are ineffective, because the broadcast channels are suffering from information overload (even in social media). I used to be skeptical of all this talk of “personal brand.&#

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MARCH 16, 2009

As it was, if you followed the XP practices, which included frequent releases, most people in the product management hot seats quickly realized that the users and (real) customers were the often-unwitting source for a lot of information key to product success. Brilliant insights, advice and information on your blog.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

MARCH 3, 2009

And if youre giving them all of the information they need to understand the companys strategy, customers, and processes, you can be confident that theyll be able to apply that understanding to their current responsibilities. I continue to believe youre reading more claims into my post then I have made. Whats that you say?

Employee 146

Employee San Francisco Lean Software Review 146

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

MARCH 22, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an Internet connection. The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an Internet connection.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

NOVEMBER 7, 2008

Depending on the type of product, postings on forums, classifieds and emails could give enough information to help gauge potential response. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 13, 2008

Thanks so much for sharing this information. 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. May 8, 2009 2:39 PM VictusFate said.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

JULY 6, 2009

Before I close, let me quote just one additional bit of twitter feedback from one of the video beta-testers: bmeschke : @ ericries This is such GREAT information. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

MARCH 17, 2009

It wont even get passed the registrant information screen to even get to selecting what you want to register for. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. March 19, 2009 6:11 PM Anonymoussaid.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

JANUARY 2, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an internet connection. The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an internet connection.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

OCTOBER 28, 2008

I have come to believe that there is a hierarchy of pitches, and that understanding where your pitch falls on this spectrum can assist in making decisions about what information to highlight. Great information on the hierarchy of pitching. Case Study: Continuous deployment makes releases n.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

NOVEMBER 8, 2008

For the rest of us, we need to get some facts to inform and qualify our hypotheses ("fancy word for guesses") about what kind of product customers will ultimately buy. You can start to think through the consequences of this information before its too late. Lots of good usable information. I plan to pick up this book though.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 18, 2008

I agree with the other comments, more information on yourself and what topics youll focus on would be helpful. As a shoestring entrepreneur with a SaaS (well, not really, but sort of) offering that we present to very large companies (think 10K+), I love your common sense suggestions about metrics and testing. More of the same.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 30, 2008

Very good and informative. 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. April 21, 2009 4:51 PM Geethan said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

APRIL 29, 2013

Last year, the co -founders of B ack to the Roots talked about their innovation accounting and how they were ignoring sales metrics in order to grow. Our talks range from five minutes to three hours, and we structure them based on the information you have to share, so don’t worry too much about length. 3) Cool—advice is key.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. Time-to-complete-a-sale is not a bad metric for validated learning at this stage. Very thorough and informative post. The key to making progress as a startup is validated learning about customers; defining the customer both in terms of interests and also metrics.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

AUGUST 8, 2009

During the course of implementing a design, new information will arise, which many times will change the original design. The kinds of "new information" in the quote above are implementation details. Case Study: Continuous deployment makes releases n. These principles are every bit as true today as then.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JANUARY 28, 2009

I would also suggest, and the engineers will almost certainly hate this suggestion, that the decision-maker asks for hard metrics to justify the refactoring effort in the first place. Only one occasion was a substantial rewrite justified based on performance metrics. And we all know what the success rates of rewrites are! Homer said.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

MAY 27, 2009

The presentation was informative, insightful, and humorous - as you pointed out the many ridiculous assumptions we make as entrepreneurs! Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

AUGUST 1, 2009

Figuring out whether and how to incorporate that new information into your vision is your job. I do hope that someday more information about the _real_ internal process comes out, so we can get some answers to our open questions: - how much internal (secret) iteration goes into each product? -

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 18, 2008

They cant present much information, unless you take the box off the shelf and look at it. Im on the team that released one of the Taxi apps, and we agree that the "SEO" and placement on the App Store can sometimes leave users with insufficient or inaccurate information to make decisions. Hey Eric, very interesting post.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

JUNE 17, 2010

But scope negotiations between departments are an example of an “iterated prisoner’s dilemma&# situation, where the same parties repeatedly negotiate, and rely on their previous experience to inform their choices in the current round. Case Study: Continuous deployment makes releases n. Here’s why.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

SEPTEMBER 22, 2008

Accurate - if youve ever been managed by task-tracking software, youll relate to the feeling that you either have to spend ludicrous amounts of time posting updates or the information goes stale. Case Study: Continuous deployment makes releases n. I never tried it, but I recently got to meet a startup who did.

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

MARCH 4, 2009

Today, Id like to spend some time on two techniques: the problem presentation and learning what channels of information reach customers. If this was a startup, Id be asking it of a sample of customers even more often, because getting a regular tracking result is helpful for informing your decision loop.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

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

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. Case Study: Continuous deployment makes releases n. One last thought. Two Ways to Hold Entrepreneurs Accountable (for Ha.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JANUARY 4, 2009

You need to store two kinds of information. This information is normally maintained by your operations team. hi, your artical and information is able to help me. Your post is helpful and informative April 19, 2009 10:49 PM Jerry said. Case Study: Continuous deployment makes releases n.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

SEPTEMBER 8, 2009

For example, the New Zealand government has been calling for RFIs (Request For Information) for health care IT solutions that engage the citizen. For more information see [link] September 10, 2009 9:53 AM John Seiffer said. Case Study: Continuous deployment makes releases n.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

OCTOBER 4, 2010

Lessons Learned by Eric Ries Monday, October 4, 2010 Stop lying on stage Entrepreneurs crave information about successful startups, and they should. This is the same issue we see with vanity metrics : companies are giving the appearance of sharing information while actually engaging in spin or outright deception.

San Francisco 167

San Francisco Lean Metrics PR 167