Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. After some trial and error, Ive settled on the Lean Startup. Of course, many startups are capital efficient and generally frugal.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 22, 2008

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. Yet there’s a lot of mystery around pivots, and entrepreneurs ask all the time how you know it’s time to commit to a new direction.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

OCTOBER 4, 2008

(Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) He serves on the advisory board of a number of technology startups, and has worked as a consultant to a number of startups, companies, and venture capital firms. So much for timing.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. are the parts of the Joel Test I think are most out-of-date.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 7, 2008

The basic idea is to extend agile, which excels in situations where the problem is known but the solution is unknown, into areas of even greater uncertainty, such as your typical startup. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own. Talk about waste.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 2, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 2, 2008

This simple feedback loop has proven its worth to me time and again. Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

SoCal CTO

DECEMBER 1, 2010

I continue to collect great content that is the intersection of startups, products, online and technology. aka: An Open Letter to the Next Big Social Network) - 500 Hats , November 1, 2010 I've held off writing this post for a long time, because I couldn't quite get my head around all the issues. but: Something is Still Missing.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 8, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 Waves of technology platforms I still remember the first time I switched to LAMP. I was building a new startup in 1999, and wanted to do it right. So one of the first things we did was to hire an Oracle expert and get to work. Looking back, that was a special moment.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

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?

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 14, 2008

Most of the people building our product werent themselves target customers. So there was simply no substitute for seeing actual customers with the product, live. Today, when I talk to startup founders, the most common answer I get to the question "do you talk to your customers?" The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: continuous deployment 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Steve Blank

JULY 30, 2009

As the (very junior) product marketing manager I got a call from our local salesman that someone at Apple wanted more technical information than just the spec sheets about our new (not yet shipping) chip. That is until I saw that in startup after startup customers come from places you don’t plan on.

Silicon Valley 146

Silicon Valley RSS California Customer Development 146

Startup Lessons Learned

SEPTEMBER 10, 2008

but its really about how to manage your effort between what he calls the frontlist and backlist. Heres my favorite part: If youve got a team, part of the team should obsess about the backlist, honing it, editing it and promoting it, while the rest work to generate (as opposed to promote) the frontlist. But then what?

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

SEPTEMBER 10, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

Startup Lessons Learned

SEPTEMBER 16, 2008

thanks for the mention:) September 17, 2008 11:56 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 6, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 2, 2008

A growing startup with a well-run product team will have a history of steady progress. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 18, 2008

Like gmlk, I usually subscribe the first time I find something useful. I originally thought I might get some development process tips (I manage developers), but I find that Im really enjoying your business tips (SEM, listening to customers, etc.). I want to get an idea of how startup guys think. Dont know yet.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Business Plan Blog

OCTOBER 4, 2013

Aligning the Startup Team Strategy with the Capitalization Strategy. The single most important factor to raising capital for any tech startup is the management team. A bonafide team is the assurance that the idea can be executed and that the business can scale when the time is right. Don’t make everyone a founder.

Part-Time VPE 79

Part-Time VPE Fractional VPE Cofounder CTO Hire 79

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

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. Those who have the endurance are the ones that tend to lead teams and join startups, because you just cant be successful in a startup situation without empathy.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

David Teten

OCTOBER 1, 2015

I’ve been looking for suggestions for an initial deal structure that is appropriate for the theoretical case of a trusted dev shop putting in $100k in market-value of services over a 6 month period in time. How would one set up such a startup to eventually raise capital from outside VCs, who will be wary of ‘dead equity’ (i.e.,

Software Development 60

Software Development Software Developers Software Review Technical Cofounder 60

Startup Lessons Learned

MAY 7, 2009

For people we hired from larger companies especially, this was challenging. When a new engineer started at IMVU, I had a simple rule: they had to ship code to production on their first day. Either way, it had to be a real bug and it had to be fixed live, in production. For some, this was an absolutely terrifying experience.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

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

SEPTEMBER 28, 2008

Lessons Learned by Eric Ries Sunday, September 28, 2008 The lean startup comes to Stanford Im going to be talking about lean startups (and the IMVU case in particular) three times in the next two weeks at Stanford. I struggle to try and make the students actually experience how confusing and frustrating startup environments are.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

Up and Running

MAY 23, 2016

If you want a slice of the pie, there isn’t a better time to get involved. To give you a better idea of what entrepreneurs in this industry are thinking about during each phase of the startup process, I interviewed SaaS entrepreneurs from all over the world, including our own COO Noah Parsons. The business model. or even be a U.S.

Software Review 74

Software Review Software Delaware Forecast 74

techcrunch.com

OCTOBER 23, 2010

Problem was, I seemed to suck at the whole startup thing. Rather, I didn’t have anyone around me familiar enough with startups to tell me that I was doing it all wrong. So for this first post, here’s the best advice I can give you: join an awesome founding team and get your product out the door ASAP. You just can’t do it all.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

Startup Lessons Learned

SEPTEMBER 13, 2008

Only much later did I realize that this was an application of customer development to online marketing. Its now a technique I recommend for any web-based startup. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 18, 2008

April 27, 2009 10:55 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 You dont need as many tools as you think Im always excited to see someone else writing about lessons learned from their startup, and wanted to link today to Untitled - Startup Lessons Learned -- Take it with a grain of salt. While simple, it is easy to manage.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 5, 2008

October 13, 2008 9:44 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 29, 2008

We built and are refining a communications and productivity Web 2.0 It solves the problem of communicating between a small group of managers, say twenty and a large group of users, say ten thousand. Were looking to metrics to determine how users interact with our product. More importantly, it must not create a time sink.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68