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. I am continuously coaching people to get out and see what is really going on. Tom Peters called the Management By Walking Around - MBWA.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

AUGUST 8, 2009

This simple three-part framework underlies almost all discussions about technical design today, and it was clearly on display in the recent debates over technical debt. This includes the designers as well as the engineers and product managers. 1] For more on SBCE, see this MIT Sloan Management Review article.

Software Review 87

Software Review Design Software San Francisco 87

www.subelsky.com

FEBRUARY 25, 2010

Mike Subelskys Blog Wednesday, November 11, 2009 Lean startup tools for Rails apps A few months ago I was invited to dinner with the Geeks on a Plane crew when they stopped in Washington, and had the opportunity to meet one of my heroes, Eric Ries , author of the Startup Lessons Learned blog. Email This BlogThis!

Lean 41

Lean Baltimore Ruby Maryland 41

Startup Lessons Learned

APRIL 14, 2009

These founders have not managed, to borrow a phrase from Steve Blank , to create a scalable and repeatable sales process. Eric, I have Steves book and wish I had it for 1 couple of my earlier startups where the framework would have helped our team get on the same page. The Lean Startup Intensive is tomorrow at Web 2.0.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 16, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference. As Lean Startup methods have been used now for a number of years, we’ve become increasingly interested in how companies use them to sustain growth. The new process let us manage the velocity of change in the codebase low, keeping the resistance manageable.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

APRIL 26, 2009

Its a key lean startup concept. It has to be found and managed. Personally, the framework Ive found most helpful is MTVs "create, share, validate" feedback loop. For example, I recently created a customer validation exercise around the Lean Startup Workshop. The Lean Startup Intensive is tomorrow at Web 2.0.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

MAY 1, 2009

Lessons Learned by Eric Ries Friday, May 1, 2009 Lean Startup webcast post-game Wow, what an incredible turnout for webcast this morning, right on the heels of a phenomenal crowd at startup2startup last night. Its been a great twelve hours for the lean startup! wogsland : Still not understanding the "lean" aspect. What a thrill.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

FEBRUARY 11, 2009

Having had a number of years to try and answer this question at cocktail parties and social gatherings of all kinds, I thought Id try and expand on his framework a little, and then try and use these answers to help make suggestions for those who are trying to get people to buy virtual goods. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

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. Thats not the goal of a lean startup. Your writing is certainly not lean.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

OCTOBER 5, 2009

Managing these situations is hard for any company, but potentially lethal for a startup. The theory is that there is some truth in both camps, and the right way to manage the disagreement is to sprinkle a little bit of both into our plans. To the people being managed that way, it feels like the boss is being capricious or arbitrary.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" Plus, the premise of the question misunderstands the lean startup, too. And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

MARCH 13, 2009

We didnt manage todo that yet. I think it comes down to managing risk. You create an entire framework of understanding and action based on your product/idea that sets it in motion in a self-sustaining way. The Lean Startup Intensive is tomorrow at Web 2.0. Its just impossible. we are never ready. Expo SF (May.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. So, both split-testing and customer feedback have their drawbacks.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. The last thing you need is a manager telling you how to do your job. If youve ever been abused by a bad manager in your career, its easy to become traumatized.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

SEPTEMBER 22, 2008

If you read Lean Thinking , you can enjoy numerous examples of companies that replaced multi-million dollar MRP systems with a simple white board. The lean manufacturing guys call this visual control and its very powerful. While simple, it is easy to manage. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

DECEMBER 16, 2008

But I think the value in this framework is that it can help make overall business decisions that require thinking about the whole rather than just one of the parts. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. For example, lets say you have a viral ratio of 1.4.

Viral 140

Viral San Francisco Lean Continuous Deployment 140

Startup Lessons Learned

JANUARY 12, 2009

PHP can do what no other language or framework can (albeit django). The proliferation of high quality, best practices frameworks - such as CakePHP (rails for PHP), Zend Framework (my personal favorite), Simfony and Seagul just to name a few. and Rails as a web framework. Keep HTML HTML and Javascript Javascript.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

FEBRUARY 12, 2009

a guide for hackers) (This post was inspired by a conversation with Nivi from Venture Hacks , but is otherwise not his fault) There has been a proliferation of frameworks and metaphors lately that are designed to help startups avoid the all-too-common fatal mistake of failing to find a market. Expo SF (May. for Harvard Business Revie.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

DECEMBER 7, 2008

Split-testing, like almost everything in a lean startup , requires judgment. Each experiment is like a little mystery, and if you can get into a mindset of open-mindedness about the answer, the answers will continually surprise and amaze you. The Lean Startup Intensive is tomorrow at Web 2.0. Its an art, not a science.

San Francisco 132

San Francisco Lean Continuous Deployment DC 132