Startup Lessons Learned

OCTOBER 4, 2008

Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) 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. Looking forward for your future posts.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

NOVEMBER 8, 2008

Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer Development. This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

AUGUST 26, 2009

As a result, for a lot of these companies, Boulder is just a gateway to San Francisco. Accept that many successful companies are going to want to be backed by big-name firms in other cities. We also had the benefit of many lean practices that break out of the "time, quality, money - pick two" paradox.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

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. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? It strokes your ego. Expo SF (May. for Harvard Business Revie.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 26, 2009

The key to successful integration of customer feedback is to make each kind of collection part of the regular company discipline of building and releasing products. Anyone who has worked in a real-world product development team can tell you how utopian that sounds. The Lean Startup Intensive is tomorrow at Web 2.0.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

JANUARY 18, 2010

Recently, he was bitten by the lean startup bug and has started writing about his experiences attempting to apply lean startup and customer development principles. Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009. Expo SF (May.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

JUNE 5, 2009

This model of joint accountability is at the heart of the lean startup, and is just as applicable to venture-backed, bootstrapped, and enterprise startups. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? Paul June 6, 2009 8:34 PM Nick Shepheard said.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? The first step in a lean transformation is learning to tell the difference between value-added activities and waste. I was giving my first-ever webcast on the lean startup. Eric Names matter. Not so with Kent Beck.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups. Expo SF (May.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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. Naturally, we already know the standard of quality that they will use to judge our product.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). All gifting-type products are influenced by this source, as Hallmark has long understood. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science?

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

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. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

FEBRUARY 10, 2009

In a lot of cases, thats just a fancy name for revenue or profit, but not always. 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.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? Its incredibly simple, and its called joblink.tw.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" He doesnt put out crappy, buggy products and then ask for feedback. So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

OCTOBER 7, 2008

If necessary, consider doing this under a different brand name than the one you are wedded to using. The Lean Startup Intensive is tomorrow at Web 2.0. 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 Retention SEM 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. The work product is a more realistic test, although it requires much more work on the part of the candidate. “Who is this guy?&# None of these are impossible.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

MARCH 13, 2009

Who doesnt want to see their name in print? gave us two years of a beta product to build up the service and the brand awareness. Now that were beginning our first marketing, the key partners we need have heard our name long enough to trust us. The Lean Startup Intensive is tomorrow at Web 2.0. Founders push for it.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 18, 2008

Even with only a few months of development, third parties have crammed every single category in the store full of apps. All I see is a name, an icon, a price, the developers name, and a review star-rating. The Lean Startup Intensive is tomorrow at Web 2.0. And what distinguishes a good app? I cant really tell.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. That’s the local maximum.

San Francisco 154

San Francisco Lean Metrics Design 154

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. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? Thoughts on scientific product development Lo, my 5 subscribers, who are you?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

DECEMBER 14, 2009

This attention is valuable to yet another set of people: namely, the traditional businesses (see above) who are using marketing to grow, and are looking to advertise to new prospects. One clue that you don’t have product/market fit – you’re trying to evaluate your business to see if you have it. Expo SF (May.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. Why was a team this smart, this disciplined, and this committed to waste-free product development creating so much waste? Ironically, meetings like this had given data and experimentation a bad name inside this company.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

MARCH 24, 2009

March 26, 2009 12:18 AM 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?) Expo SF (May.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

SEPTEMBER 22, 2008

If you read Lean Thinking , you can enjoy numerous examples of companies that replaced multi-million dollar MRP systems with a simple white board. The lean manufacturing guys call this visual control and its very powerful. Simply put, we upload all the tasks and assign a name to each task. 1 comments: Josh Moore said.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Duct Tape Marketing

NOVEMBER 1, 2017

The one side, I think it’s a really interesting point you bring up, which is does it immediately lean toward to creating new products and services? They’ve created maybe one of the most valuable events in the world called DreamForce, 175,000 people in San Francisco every year.

Cost 37

Cost Marketing Audience Media 37

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

SEPTEMBER 13, 2010

Or take a recent TechCrunch article about a startup I wont name: “X billion messages sent since June 2009.&# Or take a recent TechCrunch article about a startup I wont name: “X billion messages sent since June 2009.&# The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. for Harvard Business Revie.

San Francisco 154

San Francisco Metrics Lean PR 154

Startup Lessons Learned

OCTOBER 23, 2009

Mainstream customers don’t have enough motivation to buy an early product, and so building in response to their feedback is futile. The lean startup methodology is based on enlisting customers as allies, which requires honesty and integrity. The following was written an actual lean startup practitioner.

San Francisco 144

San Francisco Customer Wiki Lean 144