Startup Lessons Learned

NOVEMBER 6, 2008

All of the incentives described in the article focus on making it easy and highly desirable to launch your product: [He] claimed that launching projects is the natural state that Googles internal ecosystem tends towards, and its because they pump so much energy into pointing people in that direction. Focus on launching.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

FEBRUARY 22, 2009

Im not offering extensive studies or research to support this conclusion; the evidence from my peers right here in the innovation capital of America, Silicon Valley, is absolutely overwhelming. Asked to help, I am confident that Silicon Valley and every other innovation center will step up. They are nerds.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Combined with the technology trends above, it also enables rapid deployment strategies like just-in-time scalability.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

NOVEMBER 8, 2008

When we build products, we use a methodology. We know some products succeed and others fail, but the reasons are complex and the unpredictable. a roadmap for how to get to Product/Market Fit." The theory of Product/Market Fit is one key component of customer development, and I highly recommend Marcs essay on that topic.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 17, 2008

If you dont have customers, a product, investors, or a board of directors, you can pretty much stay focused on just one thing at a time. Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Case Study: Continuous deployment makes releases n.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JUNE 9, 2009

Lessons Learned by Eric Ries Tuesday, June 9, 2009 The Lean Startup Tokyo edition I had a blast speaking at Startonomics Tokyo , which was organized to foster ties between the startup cultures in Japan and Silicon Valley. benjaminjoffe : early adopters of buggy product are visionary customers, sometimes smarter than founders!

Lean 60

Lean San Francisco Japan Continuous Deployment 60

Startup Lessons Learned

MARCH 17, 2009

The problem is that the most authentic innovators and entrepreneurs are in the Valley. I want more than anything to come to Silicon Valley after I graduate and join the vibrant ecosystem. Case Study: Continuous deployment makes releases n. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

AUGUST 24, 2009

And once you have a relationship with an author, musician, or journalist, it will be quite easy for them to offer new products and services – and for you to give them feedback that helps them shape ever more interesting (and ever more profitable) offerings. There are too many products clamoring for attention. Is that a lot?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

NOVEMBER 18, 2008

I believe its important that product teams be cross-functional, no matter what other job function the product champion does. At IMVU , we called this person a Producer (revealing our games background); in Scrum , they are called the Product Owner. about what their function needs to do to fully support the product.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

MAY 14, 2009

Using examples drawn from his own experiences in the startup hub of Silicon Valley, Eric Ries unravels the myths and misconceptions that guide most startups, and paints a picture of a new way forward for the industry. This workshop presents a new methodology that will allow you to bring new products -- and companies -- to life.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

MAY 20, 2010

Heres an excerpt: Philosophy Helps Start-Ups Move Faster - WSJ.com Silicon Valley entrepreneurs and venture capitalists often churn out how-to business books and fancy themselves as management gurus, but few see their methodologies adopted. Case Study: Continuous deployment makes releases n.

Lean 153

Lean San Francisco Arlington Continuous Deployment 153

Startup Lessons Learned

MARCH 4, 2009

Every product ultimately is satisfying a need in the customers who buy it or use it. Products that dont solve satisfy any need for any customers tend to die out quickly. The more painful curse for startups is the product that satisfies a need or solves a problem - but that problem is not very important. Thats an early adopter.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

JULY 15, 2010

His posts are born of tremendous research into the secret history of Silicon Valley , and if you haven’t read those essays, you should. My belief is that the root cause of the IPO shortage is that successful startup companies cannot find productive ways to invest large amounts of money to scale anymore.

IPO 166

IPO San Francisco Lean Silicon Valley 166

Startup Lessons Learned

MARCH 9, 2010

The event is being produced in partnership with Charles Hudson, who puts on many of Silicon Valleys top events, including the forthcoming Freemium Summit. If you are working on new product development in any sized company, you are welcome to attend. Case Study: Continuous deployment makes releases n.

San Francisco 151

San Francisco Lean Continuous Deployment Startup 151

Startup Lessons Learned

FEBRUARY 7, 2010

This is especially true if you live outside the echo chamber of Silicon Valley. This is especially true if you live outside the echo chamber of Silicon Valley. Case Study: Continuous deployment makes releases n. There are four ways to get involved below. There are four ways to get involved below.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

NOVEMBER 5, 2008

Youd better be able to speak their language and translate what your product does into benefits that they understand. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

NOVEMBER 19, 2008

This wasnt an education product - it was a pretty surprising group to find using it. What all these teachers had in common were two things: they were technology early adopters that were willing to take a chance on a new software product, and they all had similar problems organizing their classes and students.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Each five whys email is a teaching document. and so forth.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 11, 2009

Although he didnt know much about our app when he started, he was able to be productive from day one, because we immediately put him to work extending our applications use of the library in question. This is especially true in Silicon Valley. Case Study: Continuous deployment makes releases n.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

JULY 9, 2009

And then, at my first Silicon Valley startup , I watched friends get laid off in successive waves as it started to fail. All my products and ideas focus on early cash and a business model that works from the first day. Ultimately your product must be useful. Case Study: Continuous deployment makes releases n.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. For a marketing job, for example, its reasonable to expect that a candidate will have done their homework and used your product (maybe even talked to your customers) before coming in.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

MARCH 13, 2009

Announce a new product, start its PR campaign, and engage in buzz marketing activities. Marketing launch) Make a new product available to customers in the general public. Product launch) In todays world, there is no reason you have to do these two things at the same time. Establish credibility with potential partners.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 8, 2009

Much of what makes the USA, and Silicon Valley in particular, such a great place to start a company is the result of good government policy. This line in your article stood out to me: "Much of what makes the USA, and Silicon Valley in particular, such a great place to start a company is the result of good government policy."

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. The "just fix it" mentality is counter-productive here. Its more like creating a space for other people to work in.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 17, 2008

But they are often counter-productive when placed in a management role for other kinds of work. Successful products and features have a natural lifecycle. The problem is that people who were essential to the product in a previous phase can get carried along and find themselves stuck downstream. What is customer development?

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

usersknow.blogspot.com

APRIL 30, 2010

Is this feature usable, and is the UX reasonably consistent with the rest of my product? The more features your overall product has, the harder it can be to support all of them well and the more complicated your product can get, so this is not a question that should be treated lightly. What is the expected ROI for this feature?

Software Review 40

Software Review Agile San Francisco Advisory Board 40

Startup Lessons Learned

NOVEMBER 22, 2008

You could conduct an in-person usability test, which is very useful for getting a view of how actual people perceive the totality of your product. The tracking survey asks one simple question: How likely are you to recommend Product X to a friend or colleague? Case Study: Continuous deployment makes releases n.

.Net 158

.Net Operations San Francisco Lean 158

SoCal CTO

JANUARY 5, 2011

Some really great stuff in 2010 that aims to help startups around product, technology, business models, etc.

Silicon Valley 378

Silicon Valley Startup Term Sheet Venture Capital 378

Startup Lessons Learned

JANUARY 30, 2009

Build a truly mainstream product. Build the product in stealth mode to build buzz for the eventual launch. The whole company and board play-tested the product to see its new features first hand. Everyone had fun; the product worked. This is why agility is such a prized quality in product development.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

NOVEMBER 5, 2008

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. The four kinds of work, and how to get them done: The four kinds of work, and how to get them done: Five Whys Where did Silicon Valley come from?

Campaign 84

Campaign San Francisco Lean Agile 84

Startup Lessons Learned

SEPTEMBER 11, 2009

Lessons Learned by Eric Ries Friday, September 11, 2009 The cardinal sin of community management Once you have a product launched, you will the face the joys – and the despair – of a community that grows up around it. It took me a long time to understand that benefit of our product. This probably sounds illogical.

Community 158

Community Management Lean Software Review 158