Startup Lessons Learned

JULY 5, 2010

While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups. While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

MARCH 29, 2010

Tactics were discussed out of context, and there wasnt an overarching framework for figuring out what works for what kinds of companies, industries, and stages of growth. Doesnt the communication overhead of a large team lead to chaos of overlapping experiments and continuously-deployed bugs?" "If Is design important to lean startups?

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

MARCH 25, 2009

It will probably be the first time Ill be able to take extensive Q&A on some of the new frameworks Ill be debuting at Web 2.0 Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.) Customer Development is itself an example of SBCE.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. I am continuously coaching people to get out and see what is really going on.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. Case Study: Continuous deployment makes releases n.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

MAY 1, 2009

LIKED: Y startups fail, cont deployment vs waterfall vs agile, small batches & learn fr biz metrics #leanstartup As concise a summary as Ive ever seen. Q: Does the Lean Startup framework work efficiently within a company of 2-3 people (think small)?" Case Study: Continuous deployment makes releases n.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

JUNE 22, 2009

Leading up to a pivot, each cycle, despite our best efforts, the metrics werent good enough. Instead of these dead-ends, use the problem and solution team framework and then: pivot, dont jump. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment?

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

OCTOBER 16, 2013

But we couldn''t have identified this without having clear metrics (that high bug count) to assess our development process. As Shutterstock has grown, there are a few key elements to our continued development speed: Small, autonomous teams: The more a team can do on their own, the faster they can go.

Lean 167

Lean Startup Software Engineering Agile 167

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. What can you do about it?

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

OCTOBER 5, 2009

In this framework, we’ll tend to either invest in the proposed prevention or do nothing. If we’re practicing continuous deployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems. How upset will those customers be?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

AUGUST 1, 2009

The only efforts a new product team should be expending are those that lead to validated learning about customers. In the meantime, I hope some of you will find the lean startup a helpful framework. Also SJ's obsession with better taste (positively) contributes to the overall product development process.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

MARCH 13, 2009

Know what the success metrics are for the launch. You create an entire framework of understanding and action based on your product/idea that sets it in motion in a self-sustaining way. Case Study: Continuous deployment makes releases n. If you know what the strategy is, youll know how to tell it was a success.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 22, 2008

It also has the nice side-effect of driving down the batch size of work, but thats for another post) This framework for making progress evident applies to more than just scheduling, of course. I used to think a giant flat-panel screen that broadcast our companys key metrics would be what was required to get everyone to pay attention to them.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

DECEMBER 7, 2008

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. Does this sound familiar?

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

DECEMBER 16, 2008

Many viral products have flamed out over the years, able to capture large numbers of users, but proving transient in their value because they failed to engage customers for the long-term. Our goal is to understand the metrics, mechanics, and levers of engagement. Some of those affected customers decide to return to your product.

Viral 140

Viral San Francisco Lean Continuous Deployment 140

Startup Lessons Learned

DECEMBER 7, 2008

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. A few days ago I open-sourced a framework for split-testing, A/B testing or continous optimization. Case Study: Continuous deployment makes releases n.

San Francisco 132

San Francisco Lean Continuous Deployment DC 132

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 (and a call for he.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89