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

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 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. Thoughts on scientific product development Lo, my 5 subscribers, who are you? It strokes your ego. Take a look and let me know what you think.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 15, 2008

If she is, return the name of the hypothesis she was exposed to before. Return the name of the hypothesis chosen or assigned. From the point of view of the caller of the function, they just pass in the name of the experiment and its various hypotheses. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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

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. Traveling to new startup hubs is one of my favorite things about being able to do this full-time. For what its worth, I like Silicon Mountain. Brad Feld also had some thoughts on this event on his blog.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 10, 2009

In a lot of cases, thats just a fancy name for revenue or profit, but not always. This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. It would be hard to argue against this product development strategy, in general.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

SEPTEMBER 13, 2008

We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. Thoughts on scientific product development Lo, my 5 subscribers, who are you? We tried obvious competitors as well as long-shots. Since we were only paying per click, it didnt cost us anything to cast a wide net.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

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

MARCH 22, 2010

Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. Many of these companies are started by entrepreneurs, and are now household names: Google, Yahoo, eBay and Intel. Startups are the lifeblood of our economy. Take the example of Indianas Passageways.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

APRIL 7, 2010

In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. I’m sure other disciplines have their own names for it; even protozoans exhibit this behavior (its called taxis ). I understand and respect why optimizers want to do tests like that.

San Francisco 154

San Francisco Lean Metrics Design 154

VC Cafe

JULY 2, 2012

Girls in Tech London picked the top women in 19 countries – the UK, Ireland, Spain, France, Germany, Italy, Belgium, the Netherlands, Denmark, Sweden, Norway, Finland, Latvia, Lithuania, Poland, Russia, Turkey, Greece and Israel – on the basis of their leadership and excellence in innovation and technology.

Latvia 109

Latvia Lithuania Russia 109

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. Phases of product & company growth. This is a common mistake.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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

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. Take a look and let me know what you think.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

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. He previously co-founded and served as Chief Technology Officer of IMVU. Take a look and let me know what you think.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you? I cant really tell.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

JUNE 22, 2009

Pivotal Labs doesn't carry "Pivot" in its name by accident. I'm glad there's a 'name' for this part of the process Eric. Thank you for your nice posting. I am very happy while reading your blog. August 24, 2009 1:42 AM RubyFocus Groups said. I like this term. September 27, 2009 4:08 PM Patti said.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

JANUARY 6, 2012

His method advocates the creation of rapid prototypes designed to test market assumptions, and uses customer feedback to evolve them much faster than via more traditional product development practices. Its only flaw is its name. For iGAP participants only. To sign up Please register here. See you in Europe!

Ireland 157

Ireland North America Lean Taiwan 157

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. Why didn’t our tests/QA/immune system catch and prevent the problem? Why wasn’t it immediately obvious how to fix the problem?

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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. Then, create an encouraging environment for early-stage companies. You dont need massive amounts of capital available for VC investment - modest amounts will do. Instead, focus on getting them ready for that stage.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

JANUARY 12, 2009

Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. Some of them are probably still cursing my name, because - lets face it - PHP can be pretty painful. The IMVU downloadable client, just to name one example, is written primarily in python.

PHP 166

PHP Software Review Ruby San Francisco 166

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. I really enjoyed this article, my first time reading any of your stuff. Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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, consider this simple scheme.

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

SEPTEMBER 22, 2008

Simply put, we upload all the tasks and assign a name to each task. Thoughts on scientific product development Lo, my 5 subscribers, who are you? 1 comments: Josh Moore said. Our business uses a similar system but using excel (about to move to Google Docs). While simple, it is easy to manage.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

mashable.com

MAY 24, 2011

May 23, 2011 by Christina Warren 20 Share on Tumblr email share Share on Tumblr email share The Mobile App Trends Series is supported by Sourcebits , a leading product developer for mobile platforms. Sourcebits offers design and development services for iOS, Android, Mobile and Web platforms. startupcto

Mobile 90

Mobile Web Social Media Software Review 90

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. Its one of the hardest things to see while its happening, and its one of the hardest mistakes to undo, because of the human and emotional costs of layoffs.

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. I also think you're spot-on with the solution - viewing spreadsheets as big holes to fill in with early learnings.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

MARCH 24, 2009

It then proceeds to list a whole host of cool new features the Warhammer team has added since I last logged in. Take a look and let me know what you think.

Metrics 88

Metrics San Francisco Lean Viral 88

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

Startup Lessons Learned

MARCH 13, 2009

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. See if their answer is about tactics or strategy. Founders push for it.

San Francisco 168

San Francisco PR Lean Early Stage 168

Up and Running

AUGUST 11, 2016

In Cohn & Wolfe’s study (12,000 people participated from Brazil, China, France, Germany, Hong Kong, India, Indonesia, Italy, Singapore, Spain, Sweden, United Arab Emirates, the United Kingdom and the United States), 69 percent of the participants claim customer relations is more important than the brand’s beliefs and environmental footprint.

United Arab Emirates 60

United Arab Emirates Social Media Redemption United Kingdom 60

Startup Lessons Learned

DECEMBER 14, 2009

This attention is valuable to yet another set of people: namely, the traditional businesses (see above) who are using marketing to grow, and are looking to advertise to new prospects. By paying money to content creators (ie writers, producers, talent), the business uses builds up assets that are of interest to other consumers.

Customer 156

Customer San Francisco Viral Lean 156

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. Take a look and let me know what you think.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151