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

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. This is precisely the dilemma that the doctrine of minimum viable product is designed to solve.

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. A/B testing is set-based design.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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. 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

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I dont think so. Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

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. Some designers also hate optimizing (which is why the “41 shades of blue&# test is so famous – a famous designer claims to have quit over it ).

San Francisco 154

San Francisco Lean Metrics Design 154

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

Jeff Hilimire

OCTOBER 8, 2014

My name is Richard Simms and, I am a Cofounder of Tech Talent South. Our mission at TTS is to develop more tech talent in the South through beginner-focused programs teaching web development and computer programming. We actually met taking some web development classes in Chicago. Who are you and what do you do?

Cofounder 68

Cofounder Charlotte Raleigh Atlanta 68

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

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

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

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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

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.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JULY 30, 2009

Traveling to new startup hubs is one of my favorite things about being able to do this full-time. 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. 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

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 Continuous Deployment 113

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

David Teten

OCTOBER 1, 2015

incubators, e.g., the many options in New York. intrapreneurs, e.g., the employee of GE who is tasked with launching a new business. Design, development, and digital media shops, sometimes just a few years old, are doing bigger and bigger projects and come bearing cash flow and that scarcest resource, talent.

Software Developers 60

Software Developers Software Development Software Review Technical Cofounder 60

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

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. Ironically, as PHP has grown up, its designers have been busy "fixing" these shortcomings.

PHP 166

PHP Software Review Ruby San Francisco 166

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. my startup is Blank Label (www.blank-label.com), which is a provider of custom dress shirts that empowers consumers to become the designer of their own product.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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

Hearpreneur

JANUARY 19, 2020

When Tal Chitayat, CEO of Full Circle Brands, was running the New York City Marathon, he got to mile 17 – where hundreds of THOUSANDS of wet sponges are offered to runners looking to cool down. Current product development needs to take into account sustainability. How did you come up with your business name?

New York City 75

New York City New Zealand China Cofounder 75

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

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

bhargreaves.com

MARCH 7, 2010

The reasons why I am not a big fan of development shops are too numerous to go into here. In brief, startups succeed because there is strong alignment of interests among all parties, especially with the people who are actually building the product. 5 Points: You have a development shop that will work for equity.

Hiring 40

Hiring Technical Review Agile Software Review 40

The Next Web

FEBRUARY 3, 2014

The tactic is to place information with intended value (and a bit of brand name-dropping) in the stream. Native advertising evokes an organic experience – one that pays tribute to the design and UX which has and continues to advance the Web. An ad by any other name. Design & Dev Entrepreneur Insider Investigations'

Advertising 139

Advertising San Francisco New York Viral 139

Startup Lessons Learned

FEBRUARY 22, 2010

I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible. “Who is this guy?&#

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

DECEMBER 14, 2009

I had a lot of use for this concept back when I worked on game design and virtual worlds. In order to maintain game play balance, game designers have to take into account the needs of customers who have an excess of four different assets: time , money , skill , and passion. Having a balanced ecosystem is what game designers strive for.

Customer 156

Customer San Francisco Viral Lean 156

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. If new employees are causing problems, that will be a routine topic. Labels: five whys root cause analysis , product development 15comments: Anonymoussaid.

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. 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

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

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

SEPTEMBER 22, 2008

Most engineers are terrible visual designers, but if the designer on their team is struggling, maybe they can help out with an icon or two. And wait until you see a "non-technical" designer writing simple code to try and speed up a release. Simply put, we upload all the tasks and assign a name to each task.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

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