Startup Lessons Learned

NOVEMBER 6, 2008

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Ive attempted to embed the relevant slides below. Talk about waste.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

YoungUpstarts

MAY 30, 2014

After all, Gmail wasn’t taken out of beta until 2009 — five years after it was originally released. Automated testing assesses the designed boundaries of your product. Beta testing highlights where potential gaps in technology may develop and gives you a chance to bridge these gaps before going public. Shorter development time.

Customer 231

Customer Development Team Review Cofounder Agile 231

Steve Blank

APRIL 20, 2009

Berkeley Haas Business School was courageous enough to give me a forum teach the Customer Development Methodology. 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! Very informative.

Silicon Valley 297

Silicon Valley RSS San Francisco Technical Review 297

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer 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

Steve Blank

APRIL 10, 2009

Customer Development ) to help you quickly recognize and reverse any incorrect decisions. That’s why startups are agile. Startups that are agile have mastered one other trick – and that’s Tempo – the ability to make quick decisions consistently over extended periods of time.

Silicon Valley 307

Silicon Valley RSS Startup Agile 307

Startup Lessons Learned

JULY 5, 2010

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

MARCH 25, 2009

Lessons Learned by Eric Ries Wednesday, March 25, 2009 The Lean Startup at Agile Vancouver April 21st A surprising number of respondents in the latest Lessons Learned survey hail from one of the flourishing startup hubs in Canada. March 25, 2009 4:44 PM Dan McGrady said. March 25, 2009 5:04 PM j pimmel said. Expo SF (May.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Steve Blank

NOVEMBER 2, 2009

For those of you who have been following the discussion, a Lean Startup is Eric Ries ’s description of the intersection of Customer Development , Agile Development and if available, open platforms and open source. The Customer Development process (and the Lean Startup) is one way to do that.

Lean 260

Lean Silicon Valley Startup RSS 260

Steve Blank

JUNE 11, 2009

Posted on June 11, 2009 by steveblank When my students ask me about whether they should be a founder or cofounder of a startup I ask them to take a walk around the block and ask themselves: Are you comfortable with: Chaos – startups are disorganized Uncertainty – startups never go per plan Are you: Resilient – at times you will fail – badly.

Cofounder 229

Cofounder Founder Silicon Valley Technical Cofounder 229

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

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. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

crowdSPRING Blog

FEBRUARY 4, 2010

These posts and videos are about design, startups, entrepreneurship, small business, leadership, social media, marketing, and more! 100+ Truly Stunning Skateboard Designs - [link]. 10 Great Tips for Using Twitter as a Designer - [link]. 10 Great Tips for Using Twitter as a Designer - [link]. – [link].

Social Media 92

Social Media Small Business Design Media 92

Steve Blank

MAY 15, 2009

Designing the Perfect Building Once the commitment to fix everything wrong was in place, we were off and running on the design phase. We hired an interior designer and a great facilities person to manage the process. The exec staff started meeting about the design of the new building. I was great at “office wars.”)

Silicon Valley 230

Silicon Valley RSS Lean Agile 230

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. August 3, 2009 10:52 AM Chris Hopf said. August 3, 2009 11:49 AM Jason Brownlee said. August 3, 2009 8:08 PM William Mitchell said. Great post.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. The batch size is the unit at which work-products move between stages in a development process. Similar results apply in product management, design, testing, and even operations.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Steve Blank

OCTOBER 12, 2009

Because of the vagaries of how floating point units in computers were designed, your average IBM mainframe of the day would take forever to run a simulation application. Reply Twitter Trackbacks for Ardent 3: Supercomputer Porn « Steve Blank [steveblank.com] on Topsy.com , on October 12, 2009 at 1:08 pm Said: [.] What Markets?

Silicon Valley 167

Silicon Valley RSS Software Review Technical Review 167

Steve Blank

MAY 9, 2017

Defense and Intelligence organizations drove the pace of innovation in Silicon Valley by providing research and development dollars to universities, and defense companies built weapons systems that used the Valley’s first microwave devices and semiconductor components. and there were no books, blogs or YouTube videos about entrepreneurship.

Restful 243

Restful Silicon Valley Puerto Rico San Jose 243

Steve Blank

NOVEMBER 12, 2009

After these slides, these VC’s recognized that this company had dramatically reduced risk and built a startup that was agile, resilient and customer-centric. The presentation didn’t have a single word about Lean Startups or Customer Development. The VC firm delivered a term sheet for an 8-digit second round that afternoon.

Venture Capital 239

Venture Capital Silicon Valley RSS Hockey Stick 239

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. Labels: customer development , lean startup 8comments: Amy said.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Steve Blank

JUNE 25, 2009

Their engineering teams didn’t have the expertise using off-the-shelf microprocessors (back then “real” computer companies designed their own instruction sets and operating systems.) They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors.

Technology 143

Technology Silicon Valley Fractional VPE Part-Time VPE 143

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Its a key lean startup concept.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

JANUARY 30, 2009

Lessons Learned by Eric Ries Friday, January 30, 2009 Achieving a failure We spend a lot of time planning. Insist on high levels of usability, UI design, and polish. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. Focus on quality. Great post!

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# This basic pattern is useful in all aspects of product development. The same process works in Interaction Design. Expo SF (May.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

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

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. For one, capacity development. August 1, 2009 7:39 AM Ravi Mohan said.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Steve Blank

MAY 18, 2009

We agreed that all her founding CEOs seemed to have the same set of personality traits – tenacious, passionate, relentless, resilient, agile, and comfortable operating in chaos. These damn models weren’t designed right so we’re fixing them on the line.” It’s our hood alignment station,” the plant manager said proudly.

Founder 310

Founder Silicon Valley RSS China 310

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Steve Blank

APRIL 6, 2009

If you are a practitioner of Customer Development, ESL was doing it before most us were born. Not surprising with a CEO with a PhD in Math, at ESL the engineers ran the company, pursuing bleeding-edge designs in antennas, receivers and microwaves – at times hand in hand with Stanford’s engineering department.

Silicon Valley 194

Silicon Valley Stealth RSS California 194

steveblank.com

JULY 8, 2011

signup, upgrade, trial pricing Zuora – online subscription management FeeFighters – find the cheapest credit card processors HealPay – Collections made easy Customer Support Tender – support, knowledgebase tool for your site GetSatisfaction - conversations between companies / customers.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

Steve Blank

APRIL 27, 2009

So I started to read all I could find on the development of microwaves. So they systematically designed electronic devices called “jammers&# to shut down each part of the German air defense system. This post makes a lot more sense if you look at the earlier posts as well as the video and slides. Just a quick history refresher.

Silicon Valley 203

Silicon Valley Technical Review Europe Germany 203

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. And this was a huge product, which took years to develop.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. A/B testing is set-based design.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

SEPTEMBER 30, 2008

When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. Your CTO might be a great architect, evangelist, interface designer or incredible debugger.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

The Next Web

SEPTEMBER 8, 2013

I also want to explain that it is possible to have a truly agile work environment based on small, autonomous teams. Wooga was founded 2009 with a vision that by 2020, everyone will be playing games. They develop a prototype that can be reviewed and most importantly, play tested. Being agile. Wooga – now and then.

Software Review 146

Software Review Agile Analytics SCRUM 146