Startup Lessons Learned

SEPTEMBER 13, 2008

Thanks so much for sharing this information. There is much work that I need to do (the only developer so far) before we have something customers can use. Case Study: Continuous deployment makes releases n. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

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. Case Study: Continuous deployment makes releases n. Slides are below: The Lean Startup fbFund Edition View more documents from Eric Ries.

Lean 115

Lean Video San Francisco Continuous Deployment 115

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

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 8, 2008

True, there are the rare products that have literally no market risk; they are all about technology risk ("cure for cancer"). 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. Lots of good usable information.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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 result is a profound democratization of the digital means of production. The result is a profound democratization of the digital means of production.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

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. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.)

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JUNE 8, 2009

Sometime later, a guide would rattle off useful information, like the density of cars in the immediate vicinity, how that density compares to historical averages, the average mass and velocity of recent cars. So the product development team was busy creating lots of split-tests for lots of hypotheses. It required two things.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

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 result is a profound democratization of the digital means of production. [.] The result is a profound democratization of the digital means of production. [.]

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

APRIL 9, 2009

Well be discussing in greater detail the three techniques I highlighted at the Expo: continuous deployment, split-testing, and five whys. Heres the promo; more information is available on their site. Both informative and inspiring! Case Study: Continuous deployment makes releases n.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. If you cant close the deal, maybe your company is at the wrong stage of its development, and its time to try a different tack.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

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

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

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. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Ill be there!

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

AUGUST 1, 2009

Figuring out whether and how to incorporate that new information into your vision is your job. Also SJ's obsession with better taste (positively) contributes to the overall product development process. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 24, 2009

Because of the incredible array of information available, we have a desperate need for filtering mechanisms. Or follow all of the New York Times columnists equally? The key tools of this new marketing are: targeting, filtering, and customer insight. There are too many products clamoring for attention. Is that good?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

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! Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 18, 2008

They cant present much information, unless you take the box off the shelf and look at it. The store determines which products sit on which shelves, and which yours sits next to. As with services like Yelp, reviewers can tend to be the subset of people who were disappointed by the product, not those who liked it or even loved it.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

APRIL 7, 2010

In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. When we’re optimizing, product development teams encounter similar situations. I mean, here we are, paying them to be there, and they won’t use the product!

San Francisco 154

San Francisco Lean Metrics Design 154

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. Case Study: Continuous deployment makes releases n.

Software Review 164

Software Review Engineer Management Technical Review 164

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. Case Study: Continuous deployment makes releases n. Whats that you say?

Employee 146

Employee San Francisco Lean Software Review 146

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. Most importantly, I encouraged the leaders of the company to bring awareness of the business challenges to the product development team. Great post, Eric.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

SEPTEMBER 18, 2008

I originally thought I might get some development process tips (I manage developers), but I find that Im really enjoying your business tips (SEM, listening to customers, etc.). I agree with the other comments, more information on yourself and what topics youll focus on would be helpful. More of the same.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. For more information see [link] September 10, 2009 9:53 AM John Seiffer said. Take a look and let me know what you think.

DC 90

DC Washington San Francisco SBIR 90

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

JANUARY 4, 2009

You need to store two kinds of information. This information is normally maintained by your operations team. Whenever they want to brng new capacity online, they simply add a row to the appropriate table. hi, your artical and information is able to help me. Case Study: Continuous deployment makes releases n.

San Francisco 151

San Francisco Architecture Startup Database 151

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

DECEMBER 30, 2008

In order to make an informed decision, the team needs a process of gathering and combining their opinions without having anyones voice stifled. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 83

San Francisco Lean Continuous Deployment DC 83

Startup Lessons Learned

MARCH 24, 2009

In short, I think this metric is "too composite" and hides, rather than illuminates, useful information. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

JANUARY 12, 2009

Add onto that the incredible amounts of infrastructure code that we reused, and we were able to bring our product to market months earlier. I like your style of posting and useful information Which you always provide. what a great site and informative posts, I always look forward to new posts. YMMV, of course :).

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

NOVEMBER 5, 2008

Observe At the end of each day, wed laboriously enter data, updating the campaigns voter database with information about every voter contact we accomplished that day. Orient And then the voter data would be crunched, by someone at statewide HQ, and each night wed start the process of creating new packets of instructions for the next day.

Campaign 84

Campaign San Francisco Lean Agile 84

Startup Lessons Learned

APRIL 26, 2010

Lean mindsets and methods for innovation in any company a free webinar featuring: Eric Ries April 28, 2010 at 2:00 PM EDT The "Lean Startup" is the application of lean thinking to the process of innovation in startup companies — defined as a type of business where both the problem (customer need) and the solution (product) are unknown.

Lean 113

Lean San Francisco Continuous Deployment DC 113

Startup Lessons Learned

JANUARY 24, 2010

And, in the survey that was attached, I learned a lot of useful information about how to make this blog better. And, in the survey that was attached, I learned a lot of useful information about how to make this blog better. Case Study: Continuous deployment makes releases n. Welcome to the latest installment.

San Francisco 104

San Francisco Continuous Deployment Lean DC 104