Startup Lessons Learned

JULY 9, 2010

And that narrow definition of entrepreneurship doesn’t count all of the managers inside established companies who are effectively engaged in the same process of building an internal startup (see What is a startup? for my more expansive definition). for my more expansive definition). What motivates all these entrepreneurs?

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

AUGUST 26, 2009

Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. You can learn more about that by reading The engineering managers lament.) leanstartup We organized our engineering team at IMVU to try and maximize cross-functional collaboration. Case Study: Continuous deployment makes releases n.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

JULY 29, 2009

We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. The human tendency to moralize about debt affects engineers, too. It definitely can be useful to judiciously take on small amounts of debt. One last thought.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

OCTOBER 28, 2008

Now there was nothing wrong with their analysis: anyone who invents a technology as sophisticated as The Transformers is definitely going to make a lot of money. whos on the engineering team? Case Study: Continuous deployment makes releases n. They even included a slide with The Transformers on it.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

JULY 3, 2009

Yet, I think this definition is too important to leave out. davemcclure : amazing concepts on Continuous Development => "Cluster Immune System" @EricRies #LeanStartup @fbFund [link] dalelarson : Because most features take longer to argue and prioritize than to build. Nothing is more demoralizing to an engineering team.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

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. This is an incredible skill, one that most engineers overlook. Stories like these are what has led me to this definition of progress for a startup: validated learning about customers. Great post!

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

APRIL 29, 2013

The Lean Startup Conference is an event by entrepreneurs for entrepreneurs—except that our definition of “entrepreneur” may be different from the one you have in mind. So if you’ve got advice to share on implementing a continuous deployment framework, for example, we’re all eyes. 1) Can you tell me more about your audience?

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

JUNE 5, 2009

I think this idea is particularly appealing to those of us from an engineering background. Unfortunately, most decisions that confront startups lack a definitive right answer. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

NOVEMBER 17, 2008

Your comment about the Innovation/R&D phase that it's hard to predict has definitely proven true in my experience. The irony is that while dates early on are unreliable, continuing to create and reach for deadlines seems absolutely necessary from a motivational/productivity standpoint. 1 comments: Andy Lawrence said.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

MAY 14, 2009

Through case studies, exercises, and discussions, Eric Ries will guide entrepreneurs of all stripes through the key areas that determine success for startups: product, engineering, QA, marketing, and business strategy. I would definitely be interested any scholarship opportunities that might be made available. Cash is tight.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

NOVEMBER 8, 2008

Thanks for this post, I was going to buy the book anyway after reading Stevens blog but this post definitely made me get it faster (just ordered). Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

AUGUST 24, 2009

So let’s turn our attention from what may happen in the future to what is definitely happening in the present. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JUNE 21, 2010

So let’s begin with a definition of a startup that captures its essential nature, and tries to leave behind the specific associations of the most famous startups. Isn’t the word human redundant in this definition? And yet the newness of a startup’s product or service is also a key part of the definition.

San Francisco 168

San Francisco Startup Lean Continuous Deployment 168

Startup Lessons Learned

OCTOBER 21, 2008

Basically, the definition of waste is different when you know less about your customer. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Labels: lean startup 3comments: Nivi said.

Lean 121

Lean San Francisco Continuous Deployment Startup 121

Startup Lessons Learned

SEPTEMBER 19, 2009

By definition these 10,000 founders wouldnt be taking jobs from Americans: it could be part of the terms of the visa that they couldnt work for existing companies, only new ones theyd founded. Case Study: Continuous deployment makes releases n. They wouldnt all grow as big as Google, but out of 2500 some would come close.

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

AUGUST 3, 2009

First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. Second, the definitions use of the words maximum and minimum means it is decidedly not formulaic. Definitely highlights the beauty of the web.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

OCTOBER 19, 2009

Then, the company spends no more than a few hundred dollars marketing the product through search engines and to the contacts in its sales database and LinkedIn. Then, the company spends no more than a few hundred dollars marketing the product through search engines and to the contacts in its sales database and LinkedIn.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

SEPTEMBER 15, 2009

Given the time constraints, I organized my presentation around two simple ideas: STARTUP = EXPERIMENT FASTER STARTUPS = MORE EXPERIMENTS PER DOLLAR I tried to make clear my usual definition of a startup, one that has nothing to do with size of company or sector of the economy. Case Study: Continuous deployment makes releases n.

San Francisco 92

San Francisco DC Washington Lean 92

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. I have found this quite rare in engineers. Many of us engineers are strong introverts, without fantastic people skills.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

APRIL 9, 2009

No engineering team. But where it makes sense, that team may also include engineers building new experiments or prototypes to try with customers. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. You need a problem team and a solution team."

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

JULY 31, 2009

Know someone whod make a great engineer at a startup? I'm finding many people coming to me with jobs, not to offer to me necessarily, but to say, "hey do you know any good designer/engineer/product person looking for a new opportunity?" I'll definitely try this out. The same process works for job candidates.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

MAY 1, 2009

Heres the working definition Ive started using: A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty. In a future post, Ill attempt to unpack this definition in detail. Case Study: Continuous deployment makes releases n.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

AUGUST 1, 2009

Beyond Apple, we can find examples of the Steve Jobs character at Toyota, in the form of the Chief Engineer. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. Maybe Steve Jobs just has a different definition of "viable"? August 2, 2009 9:50 AM Milton said. 1) RE: 'At Pixar.We

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JULY 9, 2009

And speaking of Facebook, I definitely didnt think it was a good idea when I first heard about it. Definitely one of the best posts from you. Google was not the first search engine, but it's the one that succeeded. Case Study: Continuous deployment makes releases n. Heck, Id already seen Friendster flame out.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

FEBRUARY 28, 2009

But lean startups cant afford to be satisfied with just that definition, because there are situations where working code is itself a form of waste. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

FEBRUARY 11, 2009

Definitely interested in the perspective of the open-source contributor solicited with a job offer. Im definitely curious about your thoughts on how to present the company right. Case Study: Continuous deployment makes releases n. Labels: hiring 4comments: deskin said. Excellent post all around. Thats some awesome advice.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

DECEMBER 14, 2009

Some companies definitely should. Others definitely shouldn’t. Here’s the original definition I proposed for MVP: “the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.&# are nonsensical.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

OCTOBER 11, 2009

Now they first had to go through a ritual that involved complex math, reached no definite outcome, and then proceeded to have a battle of opinions anyway! The first few changes, like a price change, may not require a lot of engineering effort. The first few changes, like a price change, may not require a lot of engineering effort.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. As a last disclaimer, please consult the definition of the word hacker if youre not familiar with the controversies surrounding that term.) Hire a CTO or VP Engineering.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

SEPTEMBER 27, 2010

Which takes us right back to the original definition of minimum viable product : the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning with the least effort. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

SEPTEMBER 13, 2010

I choose the “preceding month&# definition in order to give us a sense for individual people’s behavior. I choose the “preceding month&# definition in order to give us a sense for individual people’s behavior. Case Study: Continuous deployment makes releases n.

San Francisco 154

San Francisco Metrics Lean PR 154

Startup Lessons Learned

OCTOBER 23, 2009

BUT it definitely does NOT have the super-duper-hyper-ultra-cool Web 2.0 We have seen our competitors whose feature sets are very rich, to say the least, but we think in some cases, are as over-engineered as they are feature-rich. It definitely explores ethical boundaries. It definitely explores ethical boundaries.

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

DECEMBER 16, 2008

You definitely brought clarity around the engagement loop re: A-B-C-D makes perfect sense and can be mapped against any flow that has the possibility to go viral. Case Study: Continuous deployment makes releases n. Labels: engagement 10comments: Gustaf Alstromer said. very cool post Eric! December 17, 2008 7:56 PM dmartell said.

Viral 140

Viral San Francisco Lean Continuous Deployment 140

Startup Lessons Learned

NOVEMBER 22, 2008

In fact, there were some definite skeptics about whether they measured anything of value at all, since it is always dismaying to get data that says the changes youre making to your product are not affecting customer satisfaction one way or the other. Case Study: Continuous deployment makes releases n.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

JANUARY 28, 2009

I was told they werent sure, because all of their engineers were currently busy refactoring. The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

FEBRUARY 12, 2009

One definition of a market I like comes from Geoffrey Moores Crossing the Chasm: "a high tech market is a set of actual or potential customers, for a given set of products or services, who have a common set of needs or wants, and who reference each other when making a buying decision." Case Study: Continuous deployment makes releases n.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

JANUARY 12, 2009

At IMVU, when wed hire a new engineer, we could get them to ship code to production on their first day, even if they had never programmed in PHP before. But today I believe that ruby and python, with RoR and Django are most definitely the best ways to go for a startup business that wants to get productive. Enough about that.

PHP 166

PHP Software Review Ruby San Francisco 166