Startup Lessons Learned

SEPTEMBER 6, 2012

This post was co-written by Eric Ries and Sarah Milstein, co-hosts of The Lean Startup Conference. We have a slew of workshops you can choose from—the last two just added: Validate Your Learning Engines with Janice Fraser and Laura Klein. Engineering Your Sales Process with Sean Murphy and Scott Sambucci.

Lean 154

Lean Cofounder Analytics Startup 154

SoCal CTO

JUNE 9, 2010

But founders need to know how to ask for their advice and when to ignore it. Startup Insights From Paul English, Co-Founder of Kayak - OnStartups , May 10, 2010 I’m just wrapping up several weeks of attending conferences across both coasts. They’re deep into Customer Development ,” he said. It says what?!”).

Fractional CTO 248

Fractional CTO Startup Venture Capital Cofounder 248

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. This engineering manager is a smart guy, and very experienced.

Software Review 164

Software Review Engineer Management Technical Review 164

Steve Blank

MAY 29, 2011

The email continued, &# The problem I’m working on is that many founders are either making uninformed decisions or inefficiently learning the new skills they need. The solution I’m exploring is a just in time learning methodology that accelerates founders’ learning curve by aggregating relevant content, peers and mentors.&#.

Technical Cofounder 333

Technical Cofounder Early Stage Startup Silicon Valley 333

Startup Lessons Learned

SEPTEMBER 22, 2008

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. He also has a discussion of how your choice of business model determines which of these metric areas you want to focus on. Choose one.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

The Next Web

MARCH 11, 2014

Ryan Hoover is the co-creator of Product Hunt and EIR at Tradecraft. Even its founders couldn’t quite describe it, let alone foresee what it would become. Then Ben [one of the mobile engineers on the team] suggested a concept around sticking pieces of media to friends and people in the real world. Twitter is confusing.

Silicon Valley 151

Silicon Valley Cofounder Stock Options Mobile 151

Startup Lessons Learned

APRIL 4, 2010

► 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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? The Entrepreneur’s Guide to Customer Development ▼ June (3) What is a startup?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 15, 2008

Focus on the output metrics of that part of the product, and you make the problem a lot more clear. I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. Labels: customer development , split-test 7comments: Editor said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

David Teten

SEPTEMBER 23, 2017

My colleagues Sebastian Soler , Steven Greenberg and I recently launched a new online community, PEVCTech.com , exclusively for PE/VC investors; engineers who work at PE/VC funds; and other technologists who specialize in working on this problem. ” Historically, investing was a manual, artisan process. VC Firm. $ Tech % of workforce.

Private Equity 60

Private Equity Venture Capital Equity Technical Review 60

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. I always assumed I wouldnt manage anybody. They might do anything !

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

AUGUST 2, 2008

Its to everyones advantage to let the world think the founders thought of everything. I say this as a founder: the contribution of founders is always overestimated. The danger here is that new founders, looking at existing founders, will think that theyre supermen that one couldnt possibly equal oneself.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. Yet talent organized improperly can lead to failure. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. Every board meeting, the metrics of success change. This is an incredible skill, one that most engineers overlook. More on that in a moment. And yet, their investors are frustrated.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

MARCH 25, 2010

Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Labels: product development Speed up or slow down? Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Startup Lessons Learned - the Conference (April 23.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

SEPTEMBER 2, 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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Seth Godin: How often should you publish?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JULY 3, 2009

The same has been true of an unfortunate number of startups, they manage to generate a lot of hype, raise a lot of money, and sometimes make some of their investors, employees, or founders rich. bigs : @ericries says Stealth dev is a (undesirable, failure-presaging) customer-free zone. Use some customer development to find out.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

SEPTEMBER 10, 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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Seth Godin: How often should you publish?

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

AUGUST 26, 2009

And do your customer development. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. When they could hear the customers complaints in their own voice, it became clear when it was time to up the quality level. You can learn more about that by reading The engineering managers lament.)

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

SEPTEMBER 14, 2008

It required hearing customers say it over and over again for us to take a serious look, and eventually to realize that social networking was core to our business. Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. Seth Godin: How often should you publish?

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

NOVEMBER 7, 2008

If you cant find any , maybe that means you havent figured out who your customer is yet. And if you dont know who your customer is, perhaps some customer development is in order? Labels: customer development , search engine marketing 13comments: Jim Lindstrom said. What is customer development?

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Steve Blank

JANUARY 21, 2013

Today he is the co-founder and Chairman of Triporati, LaunchPad Central. Jim co-taught classes with me at U.C. My prior journeys were spearheaded by the founder of this school of teaching, Steve Blank. My prior journeys were spearheaded by the founder of this school of teaching, Steve Blank. And Zignal Labs.

Lean 284

Lean Cofounder Dividend Business Model 284

Startup Lessons Learned

SEPTEMBER 12, 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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Seth Godin: How often should you publish?

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 2, 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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Seth Godin: How often should you publish?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. The batch size is the unit at which work-products move between stages in a development process. Every time an engineer checks in code, they are batching up a certain amount of work.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JULY 28, 2010

Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. “Some people weren’t comfortable because it wasn’t as fun, and one senior engineer thought we’d be losing the part of kaChing that was an enabler for anyone who wanted to make it as a pro,&# Rachleff recalls.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

AUGUST 8, 2009

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

NOVEMBER 4, 2008

Customer development. For those interested in getting started with agile or customer development, I thought Id include a few links. For customer development, start with Steves book The Four Steps to the Epiphany or take a look at his recent Entrepreneurial Thought Leader Lecture.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

OCTOBER 5, 2008

The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? For some reason, though, despite the increased buy-in, the final product often doesnt look anything like the original spec.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

FEBRUARY 8, 2010

Lessons Learned by Eric Ries Monday, February 8, 2010 Beware of Vanity Metrics (for Harvard Business Review) The next article in my series on entrepreneurship for Harvard Business Review is live today. Once again, we revisit the topic of Actionable metrics and their nemesis: Vanity metrics. Remember "metrics are people, too."

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

Startup Lessons Learned

JANUARY 15, 2010

Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

OCTOBER 28, 2008

whos on the engineering team? Most important slide: demo (if the product solves an obvious problem), engineering resumes (if the product is nearly impossible to build), " day in the life of a customer " (if neither of the above) Breakthrough technology Key questions: who owns the patents? who is the customer?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

SEPTEMBER 2, 2008

Do the engineers understand what they are building? Of course, its easy to sit outside any team and criticize its failures. ► 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.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

MAY 31, 2010

I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 133

San Francisco Lean Technical Review Software Review 133