Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. Hopefully others will find it useful as well.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said.

San Francisco 158

San Francisco Management Software Review Product 158

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. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Up and Running

MAY 23, 2016

“If you can fix a problem for someone and do it better, quicker, and/or cheaper than your competitor, you’re off to a good start.” – Gabriel Kuperman, founder and CEO of CuePin. We created UpKeep to fill this void—a cloud-based solution that was affordable for any size business.” – Ryan Chan, founder of UpKeep.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

FEBRUARY 20, 2009

Similar results apply in product management, design, testing, and even operations. When operating with continuous deployment, its almost impossible to have integration conflicts. Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Small batches reduce overhead.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

During a lull in her practice she got a serendipitous opportunity to shift gears completely and ended up leading software product development teams. In the 90's, y'all, before that was built into all the operating systems!) Even "cool, agile" companies like 37signals are trapped. Our advantage was speed. The Dream Team.

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

Startup Lessons Learned

NOVEMBER 13, 2008

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. For my first time, it was scalability problems and our operations team. Now, everyone is learning together - about your product, process, and team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 17, 2008

Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. If youre making revenue, you should be finding ways to grow it predictably month-over-month; if youre focused on customer engagement, your product should be getting more sticky, and so on.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

NOVEMBER 7, 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? Expo SF (May.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JULY 9, 2010

Lessons Learned by Eric Ries Friday, July 9, 2010 Founder personalities and the “first-class man&# theory of management At any given time, something like four percent of the US population is engaged in some form of new-company-creation. Are we solving the right problem? We can do better by focusing on process instead of personality.

San Francisco 161

San Francisco Management Founder Lean 161

Steve Blank

JUNE 25, 2009

Twenty eight years ago I was the bright, young, eager product marketing manager called out to the field to support sales by explaining the technical details of Convergent Technologies products to potential customers. They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors.

Technology 140

Technology Silicon Valley Fractional VPE Part-Time VPE 140

Startup Lessons Learned

NOVEMBER 17, 2008

Have you met that prickly operations guy who seems to love servers more than people (but would never let them fail on his watch)? ► 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 79

San Francisco Lean Continuous Deployment DC 79

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. ► 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

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Keep the team size small, maybe just two or three people.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

JANUARY 18, 2010

Many people still find this idea challenging, even for companies that operate solely on the web. Ash Maurya is the founder of WiredReach , a bootstrapped startup that he has been running for seven years. Many people still find this idea challenging, even for companies that operate solely on the web. Read on to find out.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

JANUARY 19, 2009

For example, lets say you dont have an operations team, and so youre still getting paged late at night when servers crash. Is it time to make your first operations hire? Returning to our example of the beleaguered founder who still has the pager, before hiring an operations guy, try promoting someone from within to take on the job.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

NOVEMBER 22, 2008

Lessons Learned by Eric Ries Saturday, November 22, 2008 Net Promoter Score: an operational tool to measure customer satisfaction Ive mentioned Net Promoter Score (NPS) in a few previous posts, but havent had a chance to describe it in detail yet. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

JUNE 8, 2009

So the product development team was busy creating lots of split-tests for lots of hypotheses. That’s causing the Product Owner and team to spend more time with each other reviewing the results of experiments, which is allowing them to learn and iterate much faster. They’ve learned to see this waste. Expo SF (May.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. Its likely that the new release will contain new bugs.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

DECEMBER 8, 2008

Maybe two different developers made changes to the same underlying subsystem, but in incompatible ways. Maybe operations has changed the OS configuration in production in a way that is incompatible with some developers change. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

AUGUST 8, 2009

The economics of these process trade-offs are discussed in the Principles of Product Development Flow.) Heres an excerpt: In a previous article, we called Toyota’s product development system the “second Toyota paradox.&# Labels: product development 5comments: new york web development company said.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

NOVEMBER 5, 2008

Obama understood the two concepts that are essential for building a high-performance, highly adaptable, agile organization: 1) rapid iteration and 2) clear values-based objectives. Mission synchronization If an organization is changing on a daily basis how is it that it doesnt look "erratic" yet feels "agile." Expo SF (May.

Campaign 84

Campaign San Francisco Lean Agile 84

Startup Lessons Learned

FEBRUARY 22, 2010

I’ve seen many times what happens when a single department get’s holed-up in its own space, like the terrifying “ operations cave.&# One last suggestion, which is a technique I learned from my IMVU co-founder Will Harvey. One last suggestion, which is a technique I learned from my IMVU co-founder Will Harvey.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JUNE 15, 2009

One large source of waste in development is “double-checking.&# For example, imagine a team operating in a traditional waterfall development system, without continuous deployment, test-driven development, or continuous integration. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

FEBRUARY 22, 2009

Then you set up a web app to co-ordinate volunteers who can wipe a hard drive and install Ubuntu. You can find out more at: manning.com/sande Many thanks in advance, Todd -- Todd Green Manning Publications Co. these devices all need human instruction to enable correct and desired operation. Third, you market it far and wide.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

MAY 7, 2009

The idea was that these two people would operate as a unit, with the mentors job performance during this period evaluated by the performance of the new person. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. Expo SF (May.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

MARCH 4, 2009

Thanks to those of you who were willing to fill out the survey, I learned my net promoter score (about 25) as well as some clear other segmentation insights: about 80% of you are founders of or work at a startup, you read many of the same other blogs, and many of you would like to engage with Lessons Learned in formats and venues beyond this blog.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

DC 90

DC Washington San Francisco SBIR 90

www.vccafe.com

MARCH 11, 2013

.” Hackernews list of “Tools of the Trade” for startups - includes over 150 SaaS tools used by startups, and over 150 comments with interesting insights from founders. Agile project management tool that enables real time collaboration. Great for visualizing work of product development. Agile eLearning.

Software Review 53

Software Review Technical Review Startup 53

Startup Lessons Learned

OCTOBER 21, 2008

Lean startups operate by a different standard. aka "how you get to product/market fit.") Everything else (including a lot of traditional "agile" or "lean" tactics) is waste. Toyota employs something called "set-based product development" where they develop multiple versions of a product at once.

Lean 121

Lean San Francisco Continuous Deployment Startup 121

Startup Lessons Learned

JANUARY 4, 2009

Im talking about the actual data-fetching operation. This information is normally maintained by your operations team. ► 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. Expo SF (May.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

MARCH 23, 2009

Pretty soon you’re chasing your own tail a little bit because you’re not operating against a clear, long-term vision of what you’re trying to accomplish. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Combining agile development with customer developm.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167