Startup Lessons Learned

JANUARY 12, 2010

Lessons Learned by Eric Ries Tuesday, January 12, 2010 Amazing lean startup resources A year ago, there was no lean startup movement. I continue to believe that the explosion of interest in the lean startup has very little to do with me. If you are attempting to apply lean startup ideas in your own business - you are not alone.

Lean 146

Lean San Francisco Wiki Startup 146

YoungUpstarts

OCTOBER 19, 2017

by Steve Owens, Founder and CTO of Finish Line Product Development Services. The lean start-up movement has been based on a single insight – which the purpose of a start-up is to discover a business model that works. Reducing product turn time. The Lean Start-Up Environment. Extending the runway.

Product Development 153

Product Development Lean Developer Product 153

YoungUpstarts

AUGUST 17, 2018

It’s the latter category that’s especially vulnerable to premature marketing, but evolving technology, particularly security issues linked to the Internet of Things (IoT), can create post-market risks for both groups. And for non-FDA track products, there’s no requirement that companies fix technology vulnerabilities.

Software Review 100

Software Review Startup Technical Review Software 100

Startup Lessons Learned

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. Agile software development. Customer development. you get the idea.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. Fundamentally, lean startups do more with less, because they systematically find and eliminate waste that slows down value creation. Another terrific post, Eric.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JULY 30, 2009

Lessons Learned by Eric Ries Thursday, July 30, 2009 Techstars brings The Lean Startup to Boulder Im very excited to announce a pair of events that will kick off a very busy fall speaking tour. The event will include a talk from Eric on The Lean Startup over dinner, followed by moderated table discussion and then final Q&A with Eric.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Professionals Musings

JANUARY 12, 2018

The problem is that professional investors (angels and venture capital) want a proven business model before they invest, ready to scale, rather than early projections and product development. Software apps that once required a 10-person team can now be done with the Lean Development methodology by two people in a couple of months.

Intellectual Property 134

Intellectual Property Technical Review Startup Incubator 134

Startup Lessons Learned

MAY 27, 2009

Lessons Learned by Eric Ries Wednesday, May 27, 2009 Austin: the Lean Startup tour continues Next week I head to Austin, TX for my first visit ever. The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

FEBRUARY 9, 2009

Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo to explain the lean startup concept to a larger audience. The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: It uses principles of agile software development, open source and web 2.0,

Lean 68

Lean San Francisco Web Advisory Board 68

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. That startup didnt turn out so well, but not for lack of technology. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science?

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Professionals Musings

MAY 4, 2016

He nails the current key startup parameters, including the following: Crafting a lean business plan as your road map. Building a minimum viable product, with customer validation. Years ago, it cost a million dollars for a new e-commerce site, one that you can now create for almost nothing with current tools and technology.

Intellectual Property 120

Intellectual Property Startup Angel Groups Social Media 120

Startup Lessons Learned

SEPTEMBER 30, 2008

What does your Chief Technology Officer do all day? 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. Heres my take.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

FEBRUARY 7, 2013

Last May, I shared the news that long-time Lean Startup advocates Brant Cooper and Patrick Vlaskovits were working on a new book called The Lean Entrepreneur featuring illustrations by FAKEGRIMLOCK. LitMotors approach to using Lean Startup to create a new vehicle category. That new book is about to hit bookstores everywhere.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own. Expo SF (May.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 22, 2008

Sometimes we have the attitude that the Product Development team is the one responsible for Activation and Retention (hey, a great product would do that naturally) or that the Marketing team is responsible for Revenue and Referral (hey, go get me some money or free customers already). Expo SF (May. for Harvard Business Revie.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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 previously co-founded and served as Chief Technology Officer of IMVU. I got my start programming on an old IBM XT; it was thanks to MUDs that I first discovered the internet. So much for timing.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

FEBRUARY 20, 2009

I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process. Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. Expo SF (May. for Harvard Business Revie.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 8, 2008

Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer Development. 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.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. He wrote it in 2000, and as far as I know has never updated it.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. First of all, its a myth that cutting corners saves time.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JULY 29, 2009

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. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 2, 2008

The Lean Startup Intensive is tomorrow at Web 2.0. ► April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0 Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

AUGUST 2, 2008

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. The Lean Startup Intensive is tomorrow at Web 2.0. but rest assured they would be. Expo SF (May.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 2, 2008

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. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

JANUARY 7, 2010

So you can imagine how I expected some skepticism when pitching ideas about technology innovation to, say, the U.S. So you can imagine how I expected some skepticism when pitching ideas about technology innovation to, say, the U.S. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. for Harvard Business Revie.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

OCTOBER 23, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference. Analytics spark more questions and discussion than almost any other aspect of the Lean Startup method. Alistair and Ben, co-authors of the book Lean Analytics, will help you sort it out in our next webcast, Lean Analytics for Non-tech Companies.

Analytics 167

Analytics Lean Widget Metrics 167

Startup Lessons Learned

JULY 9, 2010

Typical explanations tend to focus on the well-known anecdotes and larger than life archetypes we have in mind: the twenty-something college dropouts (men, of course) from Stanford inventing some radical new technology. If you’re part of the Lean Startup movement, then you’re actually making it happen. Expo SF (May.

San Francisco 161

San Francisco Management Founder Lean 161

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. for Harvard Business Revie.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Hearpreneur

APRIL 13, 2022

One of the most important lessons entrepreneurs can learn from Dropbox is to adopt the lean start-up methodology and start. As a CEO of a technological startup, I often need to find trustworthy information as quickly as possible. And he is not afraid to take bold bets on new technologies and business models. 2- Dropbox.

Artificial Inteligence 75

Artificial Inteligence Entrepreneur Technical Review Software Review 75

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

Startup Lessons Learned

JANUARY 15, 2010

Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market. Expo SF (May.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

SEPTEMBER 14, 2008

If youre just getting negativity from someone, they are more likely a internet troll - not an earlyvangelist. The Lean Startup Intensive is tomorrow 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.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. There are too many products clamoring for attention. I’ve met a lot of gatekeepers in the past few months.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

OCTOBER 28, 2008

Its different from selling a product, because it is not part of our regular business practice, is not something that relates to our core competence, and tends not to happen in a repeatable and scalable way. Ill exclude those non- lean startups who basically exist for the purpose of raising bigger and bigger sums of money.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. When I was a kid, the way I logged onto the internet for the first time (to play MUDs, naturally) was through an open dial-up console at San Diego State University.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JUNE 17, 2010

The engineering team feels burned too, and feels that they were blamed for deficiencies in the spec as if it was their fault that the technology doesn’t really support what the artists want to do. The Lean Startup Intensive is tomorrow at Web 2.0. Amazing lean startup resources Is Entrepreneurship a Management Science?

Technical Review 164

Technical Review San Francisco Lean Software Review 164