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. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. To help find the right keywords, Ive written an article on my blog Web Startup Help that details How to Do Keyword Research for startups. The Lean Startup Intensive is tomorrow at Web 2.0.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

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. Expo SF (May.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JANUARY 12, 2009

Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. Or, perhaps theyll create an opening for another web platform to start a new cascade. But by the time I was building my first websites for commercial use , PHP had taken over.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 13, 2008

Its now a technique I recommend for any web-based startup. Thanks so much for sharing this information. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n. I just came across this post.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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

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. Expo SF (May.

Agile 111

Agile Customer Development Developer San Francisco 111

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. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Expo SF (May.

Lean 115

Lean Video San Francisco Continuous Deployment 115

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

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. "Spy satellites produced far more raw information than the government's battalion of overworked analysts could handle.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

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. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

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

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. The Lean Startup Intensive is tomorrow at Web 2.0. 2comments: King of the Herd said.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

SEPTEMBER 30, 2008

Was it an important or irrelevant fact that most of our web code was procedural and not object-oriented? Very good and informative. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

AUGUST 1, 2009

Figuring out whether and how to incorporate that new information into your vision is your job. If they were an unknown web 2.0 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

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. This is true of most web application servers, caches like memcached, and all of the network infrastructure that connects them. You need to store two kinds of information.

San Francisco 151

San Francisco Architecture Startup Database 151

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. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

Employee 146

Employee San Francisco Lean Software Review 146

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

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, The presentation was informative, insightful, and humorous - as you pointed out the many ridiculous assumptions we make as entrepreneurs! The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

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. Labels: product development 5comments: new york web development company said. The Lean Startup Intensive is tomorrow at Web 2.0.

Software Review 87

Software Review Design Software San Francisco 87

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. Expo SF (May.

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. The Lean Startup Intensive is tomorrow at Web 2.0. Here’s why. Here’s why.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

APRIL 1, 2009

Lessons Learned by Eric Ries Wednesday, April 1, 2009 Web 2.0 Expo session followup The room was utterly packed today at Web 2.0 I had brought a stack of fliers with me with one of the "Ideas-Code-Data" feedback loop infographics on one side, and information about the upcoming workshop on the other. Expo SF (May.

Web 60

Web San Francisco Continuous Deployment Lean 60

Startup Lessons Learned

APRIL 14, 2009

Now that Im in a web based company Im finding a difficult match the framework, culturally. In short: Id love to read your take on a web version of customer development. Very thorough and informative post. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

Customer 167

Customer San Francisco Lean Hockey Stick 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. First, I really find it hard to imagine a circa 2009 web start-up that doesn't start with a huge technical date. One last thought.

Technical Review 168

Technical Review Software Review San Francisco Lean 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. Lean Start-up SlideShare prez at Web 2.0 The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

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 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. Expo SF (May.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

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. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Expo SF (May.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

MARCH 24, 2009

And most web applications do their positioning right in the first few screens of the app. In short, I think this metric is "too composite" and hides, rather than illuminates, useful information. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Metrics 88

Metrics San Francisco Lean Viral 88

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. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

JANUARY 28, 2009

In my opinion there are too many examples where people in the industry use the word "refactor" to justify their work, but what they really do is re-enginering, redesign, unstructured/informal code cleanup or even complete rewrites. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

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. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n.

San Francisco 83

San Francisco Lean Continuous Deployment DC 83

Startup Lessons Learned

APRIL 7, 2010

Testing the parts simply gives us information that can help us refine the vision – like a sculptor removing just the right pieces of marble. Even better, when it is time to pivot , you’ll have actual data that can help inform where you want to head next. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

OCTOBER 20, 2008

I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. By shipping software early, you give them continuous feedback about how it well its working. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Software Review 164

Software Review Engineer Management Technical Review 164

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. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Expo SF (May.

Campaign 84

Campaign San Francisco Lean Agile 84

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. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

San Francisco 104

San Francisco Continuous Deployment Lean DC 104