Startup Lessons Learned

JULY 30, 2009

I want to thank Techstars for putting this event together and giving me a chance to experience the scene, even if it lacks a name. Building on this, I’ve recently become fascinated with the notion of continuous deployment , a concept that has been popularized by Eric Ries and others. Read the rest. Expo SF (May.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 10, 2008

Of the techniques he mentioned, I think four are fundamental and critical for any lean startup: TDD (or the even more politely named TATFT ) Continuous integration Automate your deployments Collect statistics The tools to help you do these things are getting better and better every day, but dont confuse tools with process. .

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

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

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 15, 2008

.) == "control" ) { // do it the old way } else { // do it the new way } The call to setup_experiment has to do all of the work, which for a web application involves a sequence something like this: Check if this experiment exists. If she is, return the name of the hypothesis she was exposed to before. Buy a higher quantity 2.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

MARCH 16, 2009

I think Jim Murphys confusion comes where many peoples did, with the XP term "Customer", which was XPs name for the product management role. That naming issue aside, I think its probably good that Scrum and XP didnt really say much about how to manage products. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

MAY 9, 2012

Two to four times a year, large clothing companies release products to the world and eventually the make their way online, but it's an old-fashioned industry that moves at old-fashioned speed compared to the ways people interact with companies on the Internet. Not an online clothing catalog, mind you, but a clothing company.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

NOVEMBER 8, 2008

The book takes its name from Steves theory of the four stages of growth any startup goes through. 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. Phases of product & company growth.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JANUARY 19, 2009

Much of what I have found effective is counter-intuitive, because it requires investing more effort in each hire - all in the name of efficiency. Particularly the Continuous Deployment and Split testing posts. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JUNE 5, 2009

We're starting our new business, fanminder.com, to help small merchants instantly communicate with their customers, and I'm increasingly hearing your name and reading your keen insights. 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 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

OCTOBER 26, 2009

In previous posts, I’ve mentioned quite a few of these, including these most important ones: having engineers post on the forums in their own name when they make a change routinely split-testing new changes routinely conducting in-person usability tests and interviews Net Promoter Score Each of these techniques is fundamentally bottoms-up.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

APRIL 14, 2009

Now, in some situations, this over-selling would lead to a secondary problem, namely, that customers would realize they had been duped and refuse to re-subscribe. 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.

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

OCTOBER 20, 2008

But we were cutting corners in the development methodology as well as in the code, in the name of increased speed. a is name, b is address, and c is tax percentage. 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.

Software Review 164

Software Review Engineer Management Technical Review 164

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

MVP, despite the name, is not about creating minimal products. Alan mentions above what I believe is the critical learning element your team needs to gain insight into via the Minimum Viable Product, Compelling Product Offering or other named approach. Definitely highlights the beauty of the web. Some caveats right off the bat.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). 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. Expo SF (May. Expo (and a call for he.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

DECEMBER 16, 2009

As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Eric Names matter. By pulling in a web of associations, names help people quickly assess ideas. There is a dark side to naming. The naming question has been raised about the "lean" in Lean Startups. Eric Names matter.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

JUNE 22, 2009

Pivotal Labs doesn't carry "Pivot" in its name by accident. I'm glad there's a 'name' for this part of the process Eric. 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 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

JULY 13, 2009

It moves at a rapid clip, each argument backed up with the relevant math and equations: marginal profit , Littles law , Markov processes , probability theory , you name it. Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JULY 9, 2009

Id been on the internet since I was playing MUDs as a kid, but by 1999 I felt Id already missed the boat. All the good domain names were taken, all the good ideas were being implemented. BusinessWeek named me one of the top young entrepreneurs in tech , based on my work at IMVU. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

OCTOBER 7, 2008

This is completely analogous to the situation elsewhere on the internet, where launching a new website, product, or service with PR is getting harder and harder. On the web, we have many of these channels: SEM, SEO, world of mouth, PR and viral. The Lean Startup Intensive is tomorrow at Web 2.0. Its like knowing the future.

San Francisco 68

San Francisco Lean Retention SEM 68

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. Who wants that stuff posted on the internet? The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

OCTOBER 11, 2010

On the other extreme, modern web-based applications face almost no technical risk, and are governed by high market uncertainty. The key to understanding Lean Startup is to recognize two things: Lean Startup techniques confer maximum benefit in the upper-right quadrant, namely high market uncertainty coupled with fast cycle time.

Continuous Deployment 164

Continuous Deployment Technical Cofounder Cofounder San Francisco 164

Startup Lessons Learned

JULY 2, 2009

Pay attention to whether people are comfortable “naming names&# in the meeting. 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. There’s no easy fix to this problem. .

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 27, 2010

In fact, we know so much that we already know what they will care enough about (namely, the product’s quality – as opposed to, say, missing features). The second misunderstanding is a concern for what will happen if things turn out exactly as we originally predicted (namely, badly). I understand this fear. Expo SF (May.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

MARCH 13, 2009

Who doesnt want to see their name in print? Here was our experience at IMVU, which I have seen replicated at many other consumer internet startups. 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.

San Francisco 168

San Francisco PR Lean Early Stage 168

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. Today, many of these businesses are suffering because the ecosystem no longer balances thanks to the Internet. Sorry about that.) As soon as possible!&#

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

SEPTEMBER 18, 2008

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. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Case Study: Continuous deployment makes releases n. And what distinguishes a good app? Expo SF (May.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

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. Its now a technique I recommend for any web-based startup. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, I just came across this post.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

AUGUST 1, 2009

If they were an unknown web 2.0 In talking with Mary Poppendieck about it, she said that the Chief Engineer role at 3M was called a "Product Champion" The name is less important than understanding the depth of competence that this person has, and what it takes to build it. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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 24, 2009

And most web applications do their positioning right in the first few screens of the app. 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. Join the Lean Startup discussion at Web 2.0

Metrics 88

Metrics San Francisco Lean Viral 88

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. Give each entity a name.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. Ironically, meetings like this had given data and experimentation a bad name inside this company. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

SEPTEMBER 22, 2008

Simply put, we upload all the tasks and assign a name to each task. 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. 1 comments: Josh Moore said. While simple, it is easy to manage.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

APRIL 7, 2010

I’m sure other disciplines have their own names for it; even protozoans exhibit this behavior (its called taxis ). I’m sure other disciplines have their own names for it; even protozoans exhibit this behavior (its called taxis ). The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 154

San Francisco Lean Metrics Design 154

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.

San Francisco 154

San Francisco Metrics Lean PR 154