Startup Lessons Learned

NOVEMBER 4, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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 18, 2008

At Toyota , they are called Chief Engineer : Toyota realizes that the Chief Engineer job is probably the most important one in the company because the Chief Engineer listens to the customer and then determines what the functions need to do to address the customer’s desires. What is customer development?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

NOVEMBER 17, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

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. Yet its one of those features thats only ever requested by investors and engineers - never by customers.

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. No departments The Five Whys for Startups (for Harvard Business R.

Lean 76

Lean San Francisco Web Continuous Deployment 76

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. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

NOVEMBER 8, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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

AUGUST 24, 2009

Most publishers are still caught up in an outdated “vision vs. metrics&# argument, which is already obsolete here in Silicon Valley. These individuals, possessing talent, experience or real-world networks, will continue to function as ‘virtual gatekeepers’ in the next-generation media industry.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MARCH 4, 2009

If youre used to pitching your company in a startup hub, like here in Silicon Valley, you may suffer from a debilitating disease: the inability to describe your product to normal people. Case Study: Continuous deployment makes releases n. It also gives you insight into their language.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

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. The event is being produced in partnership with Charles Hudson, who puts on many of Silicon Valleys top events, including the forthcoming Freemium Summit.

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

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

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

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. Almost all of them got scooped up by pre-IPO Google this time. That year, right before the IPO, those months mattered a great deal in terms of financial outcomes.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

NOVEMBER 19, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

NOVEMBER 13, 2008

Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day. Let me show you what this looked like after a few years of practicing five whys in the operations and engineering teams at IMVU.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 11, 2009

This is especially true in Silicon Valley. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n.

Software Review 68

Software Review Software Hiring San Francisco 68

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. And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time!

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 17, 2008

For example, should we invest a week of engineering time into making our website more failure-proof (which were pretty sure will pay off right away) or into experimenting with a new technology (that might pay off in months, years, or never)? Case Study: Continuous deployment makes releases n. Lets get to the answers.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

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

MARCH 13, 2009

In fact, we often felt frustrated when new startups with a fraction of our success got terrific write-ups in Silicon Valley-centric venues. And, more often than not, wed watch those companies flame out and die while we continued to grow steadily every month. Case Study: Continuous deployment makes releases n.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

NOVEMBER 22, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

JANUARY 30, 2009

After years of engineering effort, changing these assumptions was incredibly hard. As with many Silicon Valley failures, a flawless PR launch turned into a flawed customer acquisition strategy. Case Study: Continuous deployment makes releases n. We can accurately predict the future.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

NOVEMBER 5, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Campaign 84

Campaign San Francisco Lean Agile 84

Startup Lessons Learned

SEPTEMBER 11, 2009

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Community 158

Community Management Lean Software Review 158