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. And the rest is history: Google Maps was a huge success. No vanity metrics should be looked at.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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

JANUARY 15, 2010

Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market. Read the rest here.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

OCTOBER 5, 2008

I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. Lets start with what the product manager does. for Harvard Business Revie.

San Francisco 158

San Francisco Management Software Review Product 158

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

OCTOBER 4, 2008

So if youre new, consider not paying any attention to the rest of this post, and just diving into the archives, if you havent already. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). Im one of those people whos been programming since they can remember.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JANUARY 7, 2010

Read the rest at The Conversation - Harvard Business Review. Read the rest at The Conversation - Harvard Business Review. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. for Harvard Business Revie.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

MARCH 22, 2010

Luckily for the rest of us, he was able to find his path to a green card, and now employs 24 Americans in West Lafayette, Indiana. Read the rest of The New Startup Arms Race at Huffington Post. Luckily for the rest of us, he was able to find his path to a green card, and now employs 24 Americans in West Lafayette, Indiana.

San Francisco 121

San Francisco Indiana Lean Startup 121

YoungUpstarts

JULY 7, 2017

Well designed consumer research will highlight the most valuable customers, and what is motivating them to buy, which is the necessary insight managers need to keep the best products on the shelves and eliminate the rest. All too often media spend is a blanket purchase with little precision and even fewer metrics on returns.

Green 133

Green Demand Dividend Metrics 133

Startup Lessons Learned

AUGUST 2, 2008

but rest assured they would be. 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? Learning is better than optimization (the local ma. for Harvard Business Revie.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

JULY 30, 2009

.&# In 2002 I became exposed to the idea of “agile software development&# and subsequently was a first round investor in Rally Software which is now the market leader in Agile application lifecycle management software. Read the rest. Weve got slides , video , audio and twitter commentary. for Harvard Business Revie.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

AUGUST 24, 2009

But, as any startup can tell you, this opens up a tremendous set of opportunities for the rest of us. 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. The old models are broken, and we do not yet have new models to replace them.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JANUARY 28, 2009

Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time. Instead of waiting for that to happen, make sure there is a mechanism for sharing refactoring lessons with the rest of the team. Why dont they just learn to do it right the first time?

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

JULY 5, 2010

You can easily take from it whatever makes sense for your business, and leave the rest. While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups. You can easily take from it whatever makes sense for your business, and leave the rest.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

NOVEMBER 17, 2008

This technique rests on three things: identifying the kinds of work that need to get done, creating the right type of teams for each kind, and steering the company by allocating resources among them. Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JANUARY 2, 2010

This is just like a startup to me, complete with distribution and product development challenges, ecosystem design and many, many customers. The Lean Startup Cohort program. As you face new challenges, successes and failures - please share what you learn with the rest of us. The Lean Startup Cohort program.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

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. The opportunity was just mind-bogglingly huge.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

MAY 31, 2010

You can read the rest of his posts on his blog : Introduction , Part 1 , Part 2.) You can read the rest of his posts on his blog : Introduction , Part 1 , Part 2.) All I can tell the folks who attended the simulcasts is that I’m not missing either the time or the money. Learning is better than optimization (the local ma.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

NOVEMBER 8, 2008

Ive been guilty of this many times in my career - its just so easy to focus on product and technology instead. True, there are the rare products that have literally no market risk; they are all about technology risk ("cure for cancer"). Our goal in product development is to find the minimum feature set required to get early customers.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JANUARY 2, 2009

For the rest of us, there is an alternative: to create credibility by building a lean startup. At IMVU, we were terrified by how early we shipped (and charged for) our first product. The core of the article is my first attempt to articulate the key metrics (in graph form) that I believe demonstrate customer value.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

NOVEMBER 7, 2008

We run a web development company and we start by creating a splash page very similar to what is describe here. If we don't get a certain amount of signups on that splash page, we don't develop the rest of the site becuase they will not have any customer. June 22, 2009 6:30 AM Anonymoussaid. for Harvard Business Revie.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. for Harvard Business Revie.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 10, 2008

Heres my favorite part: If youve got a team, part of the team should obsess about the backlist, honing it, editing it and promoting it, while the rest work to generate (as opposed to promote) the frontlist. Thoughts on scientific product development Lo, my 5 subscribers, who are you? for Harvard Business Revie.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

AUGUST 1, 2009

Even if SJ has some unique "process" that enables him to come up with killer products (I suspect he is just wired differently from most people and probably has no real idea of how he does it to a point where it is teachable), that doesn't mean that the Lean Startup/Steve Blank's ideas etc have less of a value for the rest of us.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JANUARY 14, 2015

We use the term “Minimum Viable Product” as a reminder to people with product development backgrounds that we’re going to build something. Measure its impact in the marketplace using actionable metrics that help us analyze customer behavior. Clarify what MVPs are and why they’re important.

Stealth 60

Stealth Engineer Leadership Design 60

Startup Lessons Learned

MAY 7, 2009

Starting instead from a position where feedback cycle time is the priority and allowing quality to ratchet up as the product matures provides a more natural lead in to continuous deployment. The rest of the post, which you can read here , discusses the application of these principles to other contexts. I recommend you take a look.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

MARCH 13, 2009

Know what the success metrics are for the launch. The rest can believe what they want. gave us two years of a beta product to build up the service and the brand awareness. When you have a strategy for the launch, which means knowing why youre doing it. If you know what the strategy is, youll know how to tell it was a success.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

JUNE 15, 2009

This cycle repeats for a while, until the team either catches up to all the conflicts or just asks the rest of the team for a general check-in freeze. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

MARCH 11, 2010

Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics Im a little late on the cross-post, but hope youll enjoy it nonetheless. Read the rest: For Startups, How Much Process Is Too Much? - Read the rest: For Startups, How Much Process Is Too Much? - For Startups, How Much Process Is Too Much? -

San Francisco 120

San Francisco Continuous Deployment Lean DC 120

Startup Lessons Learned

MARCH 4, 2009

If you are willing, please take a moment to fill it out before proceeding with the rest of the post; itll mean less biased results, and youll have a better idea what Im talking about later. Before I go any further, heres the link to the new survey. Click Here to take survey As always, I like to start with the NPS question. Amazon PostRank

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

JANUARY 18, 2010

Unneeded features are waste and not only create more work but can needlessly complicate the product and prolong the "customer validation" phase. Build in response to a signal from the "customer", and otherwise rest or improve. Build in response to a signal from the "customer", and otherwise rest or improve.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

maplebutter.com

JANUARY 8, 2013

Written By Dan Martell on February 2nd, 2012 | Category: Hiring LeanStartup Marketing Metrics Startup Life | 6 Comments. Building Product 2. Building Metrics / Usage Reports / KPI 3. Product/Metrics (70%/30% time) * Get your product activation (sign-up + meaningful action) to 60% * then, Get your product retention to 20% weekly.

Technical Review 44

Technical Review Startup Cofounder Software Review 44

Startup Lessons Learned

APRIL 12, 2010

Weve built the Intensive into an all-star program designed to give a comprehensive overview of the methodology, taught by its leading practitioners. Heres an excerpt from the official program: “A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty.&#

Lean 129

Lean San Francisco Web Continuous Deployment 129

Startup Lessons Learned

DECEMBER 30, 2008

When doing the post-interview team meeting, it was common for the first opinion expressed about a candidate to become the prevailing opinion of the rest of the team members. The engineering team varied from 5-8 people, with a variety of skill-sets and personalities. The two rounds of questioning is a good idea for avoiding that.

San Francisco 83

San Francisco Lean Continuous Deployment DC 83

Startup Lessons Learned

OCTOBER 4, 2010

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. Similarly, journalists print vanity metrics because that’s all companies will release. And yet you who are reading this right now have tremendous power.

San Francisco 167

San Francisco Lean PR Metrics 167

Startup Lessons Learned

OCTOBER 11, 2008

Your challenge will be incentivizing your developers to create, and managing the volume of their output. And what do you do with the rest? Yes, I have had to deal with developers on strike. How do you help customers find the best of the best? And you may find yourself at the whim of some pretty unstable people. Amazon PostRank

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 19, 2009

First of all, Dave McClure introduced the idea of modifying an existing immigration program. Unfortunately, this program applies to the investor who holds the capital, and not the entrepreneur who discovers how to put that capital to use. 2gov.org will take care of the rest. 2gov.org will take care of the rest.

San Francisco 150

San Francisco Founder DC Washington 150