Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Ive attempted to embed the relevant slides below. What about a hardware business with some long-lead-time components?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

JULY 29, 2009

Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. 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.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. The book takes its name from Steves theory of the four stages of growth any startup goes through. March 14, 2009 8:34 AM Can Sar said.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

OCTOBER 20, 2008

When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 26, 2009

Lessons Learned by Eric Ries Wednesday, August 26, 2009 Building a new startup hub Last week, I had a unique opportunity to spend some time in Boulder at the behest of TechStars. Accept that many successful companies are going to want to be backed by big-name firms in other cities. Its easy to take Silicon Valley for granted.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

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. March 26, 2009 6:15 PM Will said.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? Now, in some situations, this over-selling would lead to a secondary problem, namely, that customers would realize they had been duped and refuse to re-subscribe. Great post!

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Steve Blank

JUNE 25, 2009

These companies would take our computers and put their name on them and resell them to their customers. He even remembered the names of their wives and kids and some details about schools or events. (I I couldn’t believe it, here we were wasting precious time and the dumb sales guy is talking about other stuff.)

Technology 139

Technology Silicon Valley Fractional VPE Part-Time VPE 139

Startup Lessons Learned

SEPTEMBER 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science? It strokes your ego. Expo SF (May. for Harvard Business Revie.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Steve Blank

APRIL 27, 2009

And 30 years later I was teaching in a building named after him and never knew a thing about him. And in hindsight, we seemed a bit more agile and innovative in WWII.) Yet decades later the military lacked the agility to write a spec in two years, let alone get 10′s of thousands of new systems deployed on aircraft as Terman had done.

Silicon Valley 186

Silicon Valley Technical Review Europe Germany 186

Steve Blank

APRIL 6, 2009

Forty years before Agile Development methodologies became popular, ESL had analysts from its &# customer&# sitting side-by-side with ESL engineers designing new equipment together. The “Good” Student » 14 Responses Shane Rogers , on April 6, 2009 at 1:37 pm Said: The names of ‘secret’ customers is funny.

Silicon Valley 177

Silicon Valley Stealth RSS California 177

Steve Blank

APRIL 9, 2009

But what I wanted was an agile marketing team capable of operating independently without day-to-day direction. This year, marketing need to provide sales with 40,000 active and accepted leads, company and product name recognition over 65% in our target market, and five positive product reviews per quarter.

Silicon Valley 263

Silicon Valley Technical Review RSS PR 263

Startup Lessons Learned

JANUARY 18, 2010

Recently, he was bitten by the lean startup bug and has started writing about his experiences attempting to apply lean startup and customer development principles. Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

OCTOBER 26, 2009

Lessons Learned by Eric Ries Monday, October 26, 2009 A real Customer Advisory Board A reader recently asked on a previous post about the technique of having customers periodically produce a “state of the company&# progress report. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. for Harvard Business Revie.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

JUNE 5, 2009

Lessons Learned by Eric Ries Friday, June 5, 2009 It’s a startup, not a spreadsheet Some people, when they start to realize the power of using data to inform their decisions, become obsessed with optimization. Paul June 6, 2009 8:34 PM Nick Shepheard said. June 8, 2009 1:16 AM Colin said. June 8, 2009 6:11 AM Jason said.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Steve Blank

APRIL 30, 2009

Customers went into the store either looking for the SuperMac product by name (if our demand creation activities had been effective) or went in unsure of which brand of board to buy. Reply Bill Allred , on May 1, 2009 at 10:46 am Said: This is a really common pitfall. That’s 10x what many websites convert.

Sales 120

Sales Silicon Valley RSS Las Vegas 120

Steve Blank

DECEMBER 7, 2010

There are few courses which teach aspiring entrepreneurs the skills (business models, customer and agile development, design thinking, etc.) We’ll build the class around the business model / customer development / agile development solution stack. Deliverable for Jan 18 th : Find a name for your team. to optimize this search.

Wiki 312

Wiki Lean Management Business Model 312

Altgate

SEPTEMBER 16, 2010

When outsourcing, remember that lawyers are like VCs…it matters less who’s name is on the front door than who you work with. … Tom Eisenmann Furqan: Does outsourcing engineering work well when following a lean approach with lots of iterative learning? Again…another nobrainer unless you’re LegalZoom.

Software Review 65

Software Review Offshore Startup Boston 65

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? The first step in a lean transformation is learning to tell the difference between value-added activities and waste. I was giving my first-ever webcast on the lean startup. Eric Names matter. Not so with Kent Beck.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Steve Blank

SEPTEMBER 17, 2009

In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development. Midas Oracle.ORG , on September 17, 2009 at 7:05 am Said: [.] A few successful ones do all these things.

Customer Development 247

Customer Development Developer Customer Silicon Valley 247

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Great post.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Steve Blank

JUNE 22, 2009

It was priced at $22,000 – equivalent to about $140,000 in 2009 dollars. The original Hewlett Packard which made test and measurement products was spun-out and renamed Agilent. The remaining company kept the Hewlett Packard name and focussed on computers. Agilent is a $5.8 However, no markets last forever.

Silicon Valley 170

Silicon Valley RSS California Agile 170

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. July 13, 2009 7:38 AM George said.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Steve Blank

SEPTEMBER 10, 2009

In future posts I’ll describe how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. KC Reply steveblank , on September 10, 2009 at 11:20 am Said: Ken, 1. A couple of quick questions: 1.)

Customer Development 204

Customer Development Developer Customer Silicon Valley 204

Steve Blank

JUNE 8, 2009

Waterfall, Agile, Lean? Building a Chart We realized that if we wrote the names of the vertical markets across the top of the board, and then the startup functions on the left of the board, we could make a chart that could visually compare what differs across the vertical markets. Product Development – How do you engineer it?

Vertical 123

Vertical Silicon Valley RSS Marketing 123

Startup Lessons Learned

FEBRUARY 7, 2010

If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JULY 9, 2009

Lessons Learned by Eric Ries Thursday, July 9, 2009 10 years of entrepreneurship I recently passed my ten-year anniversary of becoming an entrepreneur. All the good domain names were taken, all the good ideas were being implemented. BusinessWeek named me one of the top young entrepreneurs in tech , based on my work at IMVU.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

MARCH 13, 2009

Lessons Learned by Eric Ries Friday, March 13, 2009 Dont launch Heres a common question I get from startups, especially in the early stages: when should we launch? Who doesnt want to see their name in print? March 13, 2009 1:50 PM dan simard said. March 13, 2009 2:14 PM Alan Pinstein said. Founders push for it.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 You buy virtual goods Jeremy Liew has a great piece in the WSJ about the central mystery of businesses that make money selling virtual goods: Why do People Buy Virtual Goods? The same is true of brand-name products in almost every category (and it can be measured ).

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

AUGUST 1, 2009

Lessons Learned by Eric Ries Saturday, August 1, 2009 The Steve Jobs method Image via CrunchBase Its been a long time since I did a post that was primarily a link to another blog with commentary, but I came across something today that I really want to share. Plus, the premise of the question misunderstands the lean startup, too.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. Heck, thats what it says right there in the agile manifesto. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JULY 31, 2009

Lessons Learned by Eric Ries Friday, July 31, 2009 A new way to recruit for (and find) startup jobs In my work, I come across a lot of great startups. lets you post a description of a job without having to reveal the name of the company who is offering it, or the contact information of the hiring manager. Think of it as a bit.ly

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 27, 2010

Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. In fact, we know so much that we already know what they will care enough about (namely, the product’s quality – as opposed to, say, missing features). Even better, this is a falsifiable hypothesis.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Steve Blank

APRIL 20, 2009

When I read the funny names of these microwaves devices… Backward wave oscillators, TWT’s, Magnetrons…long silent memories came back. scott Reply Daily Links #54 | CloudKnow , on April 20, 2009 at 11:42 pm Said: [.] Reply Jamie Varon - techVenture , on April 23, 2009 at 3:05 pm Said: Great post!

Silicon Valley 280

Silicon Valley RSS San Francisco Technical Review 280