Startup Professionals Musings

NOVEMBER 28, 2020

But for founders who do their homework, the cost of entry is lower and the opportunity is higher than ever. 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. The cost of social media done well is low.

Intellectual Property 404

Intellectual Property Startup Angel Groups Social Media 404

Steve Blank

NOVEMBER 13, 2012

To celebrate the debut of the Japan edition of “The Startup Owner’s Manual” and to express great thanks to Steve and his co-author Bob Dorf, I would like to reflect back what first drew me to this book and offer Steve’s worldwide readers a look at the progress of Customer Development and the Lean LaunchPad class in Japan.

Japan 305

Japan Customer Development Developer Customer 305

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.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

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

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

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. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 30, 2008

Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard. In my mind, theyre racking up costs (one month for that part, two months for that other part, uh oh). Massive proprietary databases?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. Although it costs to pay down the principal, we gain by reduced interest payments in the future.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Professionals Musings

SEPTEMBER 16, 2023

But for founders who do their homework, the cost of entry is lower and the opportunity is higher than ever. 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. The cost of social media done well is low.

Intellectual Property 261

Intellectual Property Entrepreneur Angel Groups Social Media 261

Startup Lessons Learned

NOVEMBER 7, 2008

We spent weeks working on this new product, racing the clock so it would be done in time for the real presidential debates. We had endless arguments internally about what features it should include, how the avatars should look, and how much it should cost. Just load them all in and choose a low cost-per-click. I used to use $.05,

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. Who will ultimately bear the cost of their mistakes? How severely is failure punished? Expo SF (May.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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

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

YoungUpstarts

DECEMBER 7, 2017

Two conditions that do matter to your startup’s out-year viability are the cost and length of its product development cycle. Startup founders counting the days until break-even or actively seeking outside capital must focus on streamlining their development cycles. Stay Lean and Low.

Cost 100

Cost Developer Small Business Administration Marketing 100

Startup Lessons Learned

NOVEMBER 13, 2008

This approach is a the heart of breaking down the "time/quality/cost pick two" paradox , because these small investments cause the team to go faster over time. Great related post by John Shook at the Lean Enterprise Institute about technical vs. social sides of problems. The Lean Startup Intensive is tomorrow at Web 2.0.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

MARCH 25, 2010

(for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JUNE 17, 2010

And lastly, it removes the engineering team’s ability to find breakthrough solutions that might deliver most of the value at a fraction of the cost. And lastly, it removes the engineering team’s ability to find breakthrough solutions that might deliver most of the value at a fraction of the cost. Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Steve Blank

MAY 6, 2015

I am always surprised when critics complain that the Lean Startup’s Build, Measure, Learn approach is nothing more than “throwing incomplete products out of the building to see if they work.”. It’s time to update Build, Measure, Learn to what we now know is the best way to build Lean startups. Waterfall Development.

Lean 120

Lean Agile Business Model Customer Development 120

Startup Lessons Learned

SEPTEMBER 13, 2008

We ran ad campaigns against every single product we could think of in an adjacent market space to ours. Since we were only paying per click, it didnt cost us anything to cast a wide net. We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. Expo SF (May.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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

Feld Thoughts

SEPTEMBER 16, 2011

Since SayAhh is in the pre-launch development stage, the company doesn’t have any revenue yet. They also haven’t launched a product, so there is no corresponding “cost of goods sold” – the direct cost of delivering their product. The default Quickbooks setup uses “Income” to refer to “Revenue”.

Balance Sheet 129

Balance Sheet Fractional CTO Burn Rate Salary 129

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. I think Drucker said it best.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Steve Blank

MAY 9, 2017

The second thing that’s changed is that we’re now Compressing the Product Development Cycle. In the 20 th century startups I was part of, the time to build a first product release was measured in years as we turned out the founder’s vision of what customers wanted. The founders. China has simply become the factory.

Restful 249

Restful Silicon Valley San Jose Puerto Rico 249

Startup Lessons Learned

JULY 3, 2009

Lessons Learned by Eric Ries Friday, July 3, 2009 Lean Startup fbFund wrap-up Last week I had a real blast meeting with the companies at the fbFund incubator at Palo Alto. The Lean Startup fbFund Edition View more documents from Eric Ries. Use some customer development to find out. Without further ado. Now for the feedback.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Both Sides of the Table

FEBRUARY 27, 2019

Very few people turn up with a strong sense of “what we should be doing” or ready to lean into a productive conversation The financials were prepared by the VP of Finance / CFO. This can include: Fund raising, product development choices, sales, marketing effectiveness, competition, business development, M&A … whatever.

Stock Options 226

Stock Options Metrics Stock Valuation 226

Startup Lessons Learned

MAY 7, 2009

May 25, 2009 4:31 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.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

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 Startup 60

Startup Lessons Learned

FEBRUARY 28, 2009

Lessons Learned by Eric Ries Saturday, February 28, 2009 Throwing away working code Lean startups work by systematically eradicating waste. This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. I was told that this project had been in development for a couple of years and was currently integrating, and had been integrating for several months. The Lean Startup Intensive is tomorrow at Web 2.0.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

NOVEMBER 14, 2013

Guest post by Lisa Regan, writer for T he Lean Startup Conference. We’ve posted the full program for The Lean Startup Conference , and it includes more than three days of events for Gold pass holders and six days of events for VIP pass holders. On the evening of December 8, Ignite Lean Startup kicks off the conference.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

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

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MARCH 27, 2009

While some cost-cutting measures reduce that number, others increase it. In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. Otherwise, cutting costs just leads to going out of business a little slower. A crisis is sometimes needed to force that reexamination.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

JANUARY 2, 2010

Lessons Learned by Eric Ries Saturday, January 2, 2010 Towards a new entrepreneurship When I started writing about the lean startup , my aspiration was to do more than just share a handful of tips and tricks that work for consumer internet startups. This belief led me to the lean startup, and to an amazing 2009.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122