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.

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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. Speaking of the fall tour, if youre interested in hosting or organizing a lean startup event near you, feel free to drop me a line. For what its worth, I like Silicon Mountain.

Lean 68

Lean San Francisco Continuous Deployment DC 68

conversionxl.com

SEPTEMBER 10, 2013

It’s Not a Conversion Problem, It’s a Customer Development Problem. Not because they have a conversion problem but because they never really nail the product or how to market it. This is a customer development problem. So What is Customer Development? Extra Lucrative Conversion Advice.

Customer Development 60

Customer Development Conversion Developer Customer 60

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 26, 2009

I spent most of my time with TechStars, who were my hosts for the trip. Accept that many successful companies are going to want to be backed by big-name firms in other cities. And do your customer development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. 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.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. a is name, b is address, and c is tax percentage.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. They assume that each person on the team is genuinely interested in testing their work and ideas against the reality of what customers want.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

JANUARY 18, 2010

Recently, he was bitten by the lean startup bug and has started writing about his experiences attempting to apply lean startup and customer development principles. Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009. Things started to slip. Things started to slip.

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R.

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

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

If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. You can read about the latest iteration of the proposal at StartupVisa.com.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. In those cases, the product may stay mostly the same, but the positioning, marketing, and - most importantly - prioritization of features changes dramatically. This is an exciting kind of change, usually. I like this term.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

SEPTEMBER 27, 2010

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. Naturally, we already know the standard of quality that they will use to judge our product.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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. Eric Names matter.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

FEBRUARY 10, 2009

As Ive argued elsewhere , my belief is that startups (and anyone else trying to find an unknown solution to an unknown problem ) have to measure progress with validated learning about customers. In a lot of cases, thats just a fancy name for revenue or profit, but not always. If a feature worked, wed keep it. If it didnt, wed trash it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? This is always true, because modern economies have become increasingly virtual over the years. Take a look and let me know what you think.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

JULY 2, 2009

Pay attention to whether people are comfortable “naming names&# in the meeting. Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? There’s no easy fix to this problem.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? 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

APRIL 7, 2010

There are often counter-intuitive changes in customer behavior that depend on little details. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. When we’re optimizing, product development teams encounter similar situations.

San Francisco 154

San Francisco Lean Metrics Design 154

David Teten

OCTOBER 1, 2015

Customer development would be reduced to a single person exercise that could be repeated in parallel dozens of times over, ultimately yielding 30+ companies a year. Second, the company must eventually own the product development and maintenance functions in-house. Our model at Casual Corp.

Software Developers 60

Software Developers Software Development Software Review Technical Cofounder 60

Startup Lessons Learned

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. Its hosted by Kontagent and sponsored by Intel. You can learn more about the event here.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

AUGUST 1, 2009

Also SJ's obsession with better taste (positively) contributes to the overall product development process. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. Some of these reaffirm that they do indeed validate assumptions through interaction with customers.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

A Smart Bear: Startups and Marketing for Geeks

MARCH 11, 2014

Edwin: Correct, I fully agree and the name MeetingKing already says that my initial focus definitely was on meetings, right? Now what I’ve found is that especially the larger licenses, 10- and 25-user licenses, in the beginning I lost those customers after a couple of months. But we’re just not going to name them as ideal.

Technical Cofounder 220

Technical Cofounder Cofounder Software Review Management 220

Startup Lessons Learned

SEPTEMBER 13, 2008

We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. And then we would use that simple analytics system I mentioned to monitor the conversion rates of customers from each campaign. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

OCTOBER 7, 2008

If necessary, consider doing this under a different brand name than the one you are wedded to using. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Dont do PR upfront, dont put out a press release. Its like knowing the future. Take a look and let me know what you think.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

SEPTEMBER 18, 2008

Even with only a few months of development, third parties have crammed every single category in the store full of apps. All I see is a name, an icon, a price, the developers name, and a review star-rating. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

DECEMBER 14, 2009

Each of these four currencies represents a way for a customer to “pay&# for services from a company. A great product enables customers, developers, partners, and even competitors to exchange their unique currencies in combinations that lead to financial success for the company that organizes them.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

MARCH 13, 2009

Do some Customer Development instead. Who doesnt want to see their name in print? gave us two years of a beta product to build up the service and the brand awareness. Now that were beginning our first marketing, the key partners we need have heard our name long enough to trust us. Help you raise money.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 22, 2008

Simply put, we upload all the tasks and assign a name to each task. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Thoughts on scientific product development Lo, my 5 subscribers, who are you? 1 comments: Josh Moore said. While simple, it is easy to manage.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

JANUARY 4, 2009

Imagine you want to store data about customers, each of whom has "last name" field in your database. The problem should be familiar to anyone who plays Scrabble: not all letter are equally likely to be used as the first letter of someones name. Give each entity a name. For example, lets say you have data about customers.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. Why was a team this smart, this disciplined, and this committed to waste-free product development creating so much waste? Ironically, meetings like this had given data and experimentation a bad name inside this company.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

FEBRUARY 22, 2010

Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin. “Who is this guy?&#

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167