Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. Take a look and let me know what you think.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

OCTOBER 4, 2008

Without those open and yet expert-filled channels, it might have taken me many years more to correct my naivety and fill out my understanding of core topics. Of course its much harder to judge and select based on skill and inherent value rather than track record, but I think its worth trying. Take a look and let me know what you think.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

AUGUST 8, 2009

One of the topics that raised heated debate was whether I had conflated technical design with product design , because I made the admittedly counter-intuitive claim that sometimes good technical design actually leads to increased technical debt. Take a look and let me know what you think.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

NOVEMBER 8, 2008

The theory of Product/Market Fit is one key component of customer development, and I highly recommend Marcs essay on that topic. Marc Andreeson also took a stab , calling it "a very practical how-to manual for startups. a roadmap for how to get to Product/Market Fit." Still, I feel the need to add my two cents.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 18, 2008

Another thought would be to outline who the intended audience for your blog is and the topic areas you will focus on. I agree with the other comments, more information on yourself and what topics youll focus on would be helpful. You might offer some background on yourself just to help readers get better oriented. Hacker News 3.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

MARCH 29, 2010

Then, well talk case studies in each area, presented by practicing entrepreneurs who have actually grappled with the topic at hand. Then, well talk case studies in each area, presented by practicing entrepreneurs who have actually grappled with the topic at hand. Were in pursuit of the truth, not orthodoxy.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

SEPTEMBER 10, 2008

Joel himself has written about this topic, in the context of doing root cause analysis to provide excellent quality of service without SLAs. I hope to write at a future date about how to build your application so that A/B tests are just as easy as not doing them. Do you practice Five Whys? Take a look and let me know what you think.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JANUARY 19, 2009

For additional thoughts on that topic, see Lean startups vs lean companies. For more detail on this second point, I recommend The Goal: A Process of Ongoing Improvement. In any event, in order to hire effectively, you have to have a strong understanding if what the unit of progress is for your company.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JUNE 9, 2009

For anyone interested in this topic, I highly recommend reading Toyota Production System: Beyond Large-Scale Production. After some discussion, it seemed like what I was hearing was that Japanese companies like Toyota have been so successful that many people have forgotten the entrepreneurial roots of those same companies.

Lean 60

Lean San Francisco Japan Continuous Deployment 60

Startup Lessons Learned

MARCH 4, 2009

If they are willing to pay big bucks, for example, to attend a conference on a certain topic, that bodes well for your ability to sell them a product related to that topic. But beyond the obvious, its also important to know where customers go to get answers to pressing questions. Take a look and let me know what you think.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 8, 2010

Once again, we revisit the topic of Actionable metrics and their nemesis: Vanity metrics. Once again, we revisit the topic of Actionable metrics and their nemesis: Vanity metrics. Any entrepreneur with a decent reality distortion field can find metrics that make it look like theyre being successful.

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

Startup Lessons Learned

AUGUST 24, 2009

And as we consider specialized niche topics, like business, technical or educational content we can get even more precise. If a previously unknown title has a higher-than-average customer engagement across a wide demographic, it might merit additional investment – even if the total number of units sold is quite small.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MARCH 23, 2009

Here are some topics and excerpts of what we covered, edited lightly for how I wish Id said it at the time. Lessons Learned by Eric Ries Monday, March 23, 2009 Venture Hacks interview: "What is the minimum viable product?" I recently say down with Venture Hacks for an interview. Is "release early, release often" enough?

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

AUGUST 24, 2010

They use crowdsourcing to figure out which speakers to invite and what topics are of interest to their audience. They use crowdsourcing to figure out which speakers to invite and what topics are of interest to their audience. Because were getting a very late start on the other panels, our submission is way behind.

San Francisco 127

San Francisco Lean Continuous Deployment DC 127

Startup Lessons Learned

SEPTEMBER 19, 2009

In a previous post , I asked readers for suggested topics that the US government needs to know about startups and entrepreneurs, and got some really interesting responses. In a previous post , I asked readers for suggested topics that the US government needs to know about startups and entrepreneurs, and got some really interesting responses.

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

JANUARY 1, 2009

What topics would you like to see here on Lessons Learned? As for a topic Im particularly interested in, Id be curious about partnerships: the type of formal or informal relationships one tech co has with another in terms of either cross marketing or integrating each others products. What do you expect for 2009?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

AUGUST 20, 2009

I get asked regularly to do guest posts, and Im quite often at a loss for topic ideas. Ive struggled to come up with topics that work in the shorter-form world of traditional and news-oriented blogs. So, if you have a topic suggestion, please post it as a comment. August 20, 2009 9:39 AM Alan Peters said.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

YoungUpstarts

SEPTEMBER 7, 2011

The objective of the site is not to compete with TED or the LinkedIn community, but to collect material, views and content related to this topic of leadership in the digital generation in one place. I say this because Finland, where I come from, is really bad at this.

Leadership 164

Leadership Singapore Finland China 164

Startup Lessons Learned

MARCH 31, 2009

But look for a future post on the topic using the data you all help me collect. And if you know those principles, you may notice that I am trying to pass from the "customer discovery" phase to the "customer validation" phase. I wont say any more, for fear of ruining the data. See you at the Expo ! Labels: events 3comments: Hazem Awad said.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

JANUARY 11, 2009

The difference is intent: when youre searching for a specific topic, ads have a chance to fulfill your interest in that topic. This model has not translated well to the world of social networking, because customers of social networks engage sites in a different way than customers of search engines.

San Francisco 68

San Francisco Social Network Lean Continuous Deployment 68

Startup Lessons Learned

MAY 5, 2009

Thanks for sharing more details about some of the topics you talk about consistently. In their own MBAey kinda way. link] May 6, 2009 10:20 AM Eric Santos said. Just listened to your interview at Mixergy. Great stuff there! BR, May 6, 2009 7:38 PM Lincoln Nguyen said. Great stuff, the guys at 37signals would be proud.

San Francisco 68

San Francisco Video Lean Customer 68

Startup Lessons Learned

NOVEMBER 29, 2008

When I train someone to participate in a technical interview, the primary topic is what were looking for in a good candidate. The best candidates have managed to teach me something about a topic I thought I already knew a lot about. The six key attributes spell ABCDEF: Agility. Communication. Take a look and let me know what you think.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

MAY 22, 2009

The insights on customers and deployment methodologies have been fascinating, and I would like to hear your thoughts on co-founders & their relationships playing in to the other topics (for example, do you have the same 'no lone founders' rule that many of the incubators seem to adhere to?).

Lean 76

Lean San Francisco Continuous Deployment Startup 76

Startup Lessons Learned

MAY 7, 2009

Returning to the topic at hand, I think this example illustrates the tension required to reduce fear. As a result, we had a pretty decent curriculum for each mentor to follow to ensure the new employee got up to speed on the most important topics quickly. I recommend you take a look. These two practices worked together well.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

JUNE 22, 2009

There's nothing wrong with promoting post like this, which explains insight of #leanstartup topic. April 12, 2010 7:45 AM @hankzy said. Thanks, Old post, but essential to newbie like me. Don't take anything that annoy-nymous said. Take a look and let me know what you think.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

JULY 2, 2009

For example, at IMVU we had masters appointed for topics like site scalability or unit test failures. If new employees are causing problems, that will be a routine topic. Always explicitly identify the person running the meeting. Some organizations like to appoint a “Five Whys master&# for a specific area of responsibility.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

FEBRUARY 28, 2009

The question of why the original concept, an IM add-on for 3D chat, doesnt make sense is a topic for another post (hint: it has something to do with Bowling Alone ). None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

FEBRUARY 11, 2009

If youre interested in that topic, let me know in a comment. Of course, if youre the target of one of these hiring calls, and not the company doing it, the perspective is pretty different. How do you evaluate a startup as a potential employer? As I promised over at Hacker News , Ill try and tackle that question in a future post.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. Take a look and let me know what you think.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

MARCH 27, 2009

Expo , for those that are interested in discussing these topics in depth. A checklist of practices in the new Joel Test for Startups. Work in small batches. And, of course, theres the Lean Startup session at the upcoming Web 2.0 As a reminder, you can come to the session (and a lot more) for free, courtesy of web2open.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Both Sides of the Table

JUNE 29, 2017

Boston, Finland and Paris). We also bring speakers on the topic every year to talk to the VCs who attend our Summit. We’ve had billion dollar exists in Chicago, Baltimore, London, San Francisco and Los Angeles an well as enormous winners also in New York and Las Vegas. Yet clearly we must do more.

Los Angeles 287

Los Angeles Las Vegas Venture Capital San Francisco 287

Startup Lessons Learned

JUNE 24, 2020

I grew up in Finland. I grew up in a small town in Finland as an outsider geek, one way to make friends was to essentially dungeon master or game master role playing games. So I wanted to start with this, with how you think about these more abstract topics before we get into what I hope you can give us a briefing on the science itself.

Founder 60

Founder Technical Review Leadership Software Review 60

Startup Lessons Learned

DECEMBER 8, 2008

Still, my experience working with startups has been that too much time spent talking about advanced topics can lead to inaction. At IMVU, we eventually built out a system that preserved the speed feedback, but had finer-grained effects on each persons productivity. So dont sweat the details - jump in and start experimenting. Great article.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

OCTOBER 5, 2009

Most of the advice I’ve heard on this topic has been a kind of split-the-difference approach. Most of the advice I’ve heard on this topic has been a kind of split-the-difference approach. Take a look and let me know what you think.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

SEPTEMBER 8, 2009

Amen to this topic! Of course, the real thanks should go to a startup - Gogo Inflight Internet - that I was lucky enough to meet at a recent workshop. Thanks guys!) 16comments: Jared Goralnick said. I think the first three items on your list are top on my agenda. Take a look and let me know what you think.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

MARCH 24, 2009

if you are over-optimizing your viral loop, you may be trading away important engagement benefits (see the original engagement loop article for more on that topic) In any event, even in the case you cited above, where customers don't ever directly respond to notifications, I think they are still important.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

DECEMBER 30, 2008

Let me briefly summarize the part of the book I find most helpful (leaving a few out, which arent germane to todays topic). You dont have to buy the argument, but the facts and citations are worth the price of admission. Not all crowds are wise. Take a look and let me know what you think.

San Francisco 83

San Francisco Lean Continuous Deployment DC 83