Startup Lessons Learned

SEPTEMBER 15, 2008

This kind of result is typical when you ship a redesign of some part of your product. The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. Ken Yagen (@kenyagen) KenAtYagenDotCom January 3, 2010 1:38 PM Paramendra Bhagat said. November 25, 2009 9:54 AM Danny Wong said. Blew my mind.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

NOVEMBER 7, 2008

So, if youre interested in helping avoid mistakes like that, here are the steps: Get a domain name. It doesnt have to be the worlds catchiest name, just pick something reasonably descriptive. If youre concerned about sullying your eventual brand name, dont use your "really good" name, pick a code name.

Demand 167

Demand San Francisco Lean Continuous Deployment 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.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries.

Agile 111

Agile Customer Development Developer San Francisco 111

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. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

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

NOVEMBER 8, 2008

You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Our goal in product development is to find the minimum feature set required to get early customers.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. Bring your questions.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Thoughts on scientific product development Lo, my 5 subscribers, who are you? April 23, 2010 in San Francisco.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

AUGUST 26, 2009

Accept that many successful companies are going to want to be backed by big-name firms in other cities. And one last specific practice that came up at this session: feverishaaron : UI, design and programmers are all in the same department, all have the same title, and all are evaluated the same.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Steve Blank

SEPTEMBER 17, 2009

This post describes a solution – the Customer Development Model. In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development. This post describes such a model.

Customer Development 253

Customer Development Developer Customer Silicon Valley 253

Startup Lessons Learned

JULY 30, 2009

I want to thank Techstars for putting this event together and giving me a chance to experience the scene, even if it lacks a name. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. Traveling to new startup hubs is one of my favorite things about being able to do this full-time.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Steve Blank

AUGUST 27, 2009

This series of posts is a brief explanation of how we’ve evolved from Product Development to Customer Development to the Lean Startup. The Product Development Diagram Emerging early in the twentieth century, this product-centric model described a process that evolved in manufacturing industries.

Silicon Valley 269

Silicon Valley Product Startup Product Development 269

Startup Lessons Learned

OCTOBER 26, 2009

The key to successful integration of customer feedback is to make each kind of collection part of the regular company discipline of building and releasing products. Anyone who has worked in a real-world product development team can tell you how utopian that sounds. Either way, I hope you’ll share your experiences, too.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Steve Blank

SEPTEMBER 10, 2009

In future posts I’ll describe how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. Market Type also affects the market size as well as how you launch the product into the market.

Customer Development 220

Customer Development Developer Customer Silicon Valley 220

Startup Lessons Learned

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Many people still find this idea challenging, even for companies that operate solely on the web.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

JANUARY 19, 2009

Much of what I have found effective is counter-intuitive, because it requires investing more effort in each hire - all in the name of efficiency. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. This is another sub-optimization caused by incentivizing the wrong metric.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JUNE 5, 2009

We're starting our new business, fanminder.com, to help small merchants instantly communicate with their customers, and I'm increasingly hearing your name and reading your keen insights. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. Bring your questions.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Steve Blank

JUNE 8, 2009

Execution by Vertical Market As the class progressed, students asked how the activities/functions of a startup; (Sales, Marketing, Business Development, Product Development, etc.) How does product development differ in communications hardware versus enterprise software, etc. Theme: Digg 3 Column by WP Designer.

Vertical 125

Vertical Silicon Valley RSS Marketing 125

Steve Blank

OCTOBER 1, 2009

Where are the charitable foundations, business schools and hospitals named after him? Sure one guy got kicked out – which could have been avoided if he ran company well enough to keep financial control – and the other hung in there and got institutions named after him. Yet you never hear who built that company. Who was he?

Silicon Valley 179

Silicon Valley United States RSS Customer Development 179

Hunter Walker

JANUARY 15, 2017

Hunter Walk: DSPTCH started in 2010 as a side hustle out of your apartment. Practically speaking, the burning need was to begin hiring employees so that I could spend more of my day on product development, partnerships and driving sales. and reached out. The majority of my hours was previously being spent on the logistical side.

Marketing 48

Marketing Design Acquisition Bootstrapping 48

Hearpreneur

JANUARY 7, 2022

Since I began in 2010, there have been ups and downs, but I wouldn't have it any other way. By establishing a company dedicated to inventive and speedy product development, I am able to use cutting-edge technologies and consistently innovate faster than competitors. 9- Be a household name. Photo Credit: Omer Reiner.

Entrepreneur 118

Entrepreneur Technical Review Software Review Non-Compete 118

Startup Lessons Learned

SEPTEMBER 27, 2010

Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?) One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

AUGUST 3, 2009

First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. MVP, despite the name, is not about creating minimal products. There is a distinction between product and offering.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 7, 2010

Lessons Learned by Eric Ries Sunday, February 7, 2010 Tell your Startup Visa story Ive been promising big Startup Visa -related news on Twitter for a few weeks. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. Soon, I promise. For now, take my word for it.

San Francisco 118

San Francisco DC Startup Lean 118

Steve Blank

AUGUST 24, 2009

If you’re a startup raising money or just want to see your name online, there’s not a better blog on the web. Theme: Digg 3 Column by WP Designer. Reading this TechCrunch post made me remember the first time I saw someone confront a worldview they didn’t expect. Blog at WordPress.com.

Silicon Valley 210

Silicon Valley PR Technical Review RSS 210

Up and Running

MAY 23, 2016

Another great way to test your idea is to create a minimum viable product, or MVP. This is the simplest version of your product minus the frills and frosting. It’s a particularly popular strategy in the world of product development and is used to quickly and quantitatively test a product or a product feature.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

DECEMBER 16, 2009

As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Eric Names matter. By pulling in a web of associations, names help people quickly assess ideas. There is a dark side to naming. The naming question has been raised about the "lean" in Lean Startups. A/B testing is set-based design.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

JULY 2, 2009

Pay attention to whether people are comfortable “naming names&# in the meeting. Five Whys is designed to avoid these nebulous arguments. Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JUNE 22, 2009

Pivotal Labs doesn't carry "Pivot" in its name by accident. Ajay January 24, 2010 6:15 AM Matthew Ogston said. I'm glad there's a 'name' for this part of the process Eric. February 9, 2010 3:16 PM Anonymoussaid. April 12, 2010 7:45 AM @hankzy said. Thank you for your nice posting.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). Many products derive all of their value from this utility, online as well as off: generic drugs are pretty similar to a number of non-epic consumables in your average MMOG. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

AUGUST 1, 2009

Apple has a track record of creating lots of interesting enabling infrastructure, like Quicktime and Bonjour, which sometimes become key to their products and othertimes not. My guess is they have lots of people constantly working on interesting new tools for their designers to play with. Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

FEBRUARY 22, 2010

Lessons Learned by Eric Ries Monday, February 22, 2010 Why diversity matters (the meritocracy business) Diversity is the canary in the coal mine for meritocracy. I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. “Who is this guy?&#

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JULY 31, 2009

lets you post a description of a job without having to reveal the name of the company who is offering it, or the contact information of the hiring manager. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Its incredibly simple, and its called joblink.tw. Think of it as a bit.ly

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

JULY 9, 2009

All the good domain names were taken, all the good ideas were being implemented. If Id bought just a handful of the "best of the rest" domain names that were available at the time (for a whopping $70 each), I probably could have just retired right then. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 94

San Francisco Lean Continuous Deployment DC 94