Startup Lessons Learned

SEPTEMBER 15, 2008

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. The designers might be telling you that the new design looks much better than the old one, and thats probably true.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Steve Blank

OCTOBER 5, 2009

A Phone Call After I left MIPS Computers I was in New York tagging along with a friend (a computer architect whose products at Apple a decade later would change the shape of personal computing) who was consulting for a voice recognition startup. I worked at Multiflow, a name you’d recognize, ending up running the OS group.

North Carolina 125

North Carolina Silicon Valley Fractional VPE Part-Time VPE 125

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.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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 do your customer development. 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

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. Yet there is one silver lining when it does happen: we wind up throwing out working code , debt-riddled and elegantly designed alike.

Technical Review 168

Technical Review Software Review San Francisco Lean 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.

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

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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

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

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

APRIL 14, 2009

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. In fact, this company hasn’t shipped any new products in months. And yet their numbers continue to grow, month after month.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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

OCTOBER 20, 2008

But we were cutting corners in the development methodology as well as in the code, in the name of increased speed. For many projects, customer approval and sign off was required as well. It might be more precise to categorize them of two kinds of flaws: flaws in implementation, and flaws in design.

Software Review 164

Software Review Engineer Management Technical Review 164

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

Advisory Board 151

Advisory Board Customer San Francisco Lean 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

Steve Blank

OCTOBER 1, 2009

Sloan Foundation , the Sloan School of Management at MIT , the Sloan program at Stanford , and the Sloan/Kettering Memorial Cancer Center in New York. Where are the charitable foundations, business schools and hospitals named after him? If you look around the United States it’s hard to avoid Sloan. There’s the Alfred P.

Silicon Valley 156

Silicon Valley United States RSS Customer Development 156

Steve Blank

MARCH 22, 2016

Joining me in SiriusXM’s studio in New York were. because there’s something going on over here that you’d love to be involved and have your name next to it … may not be as important as another hour kind of vetting the design with someone you’ve been through it with a hundred times already. Nigel Caldon.

Entrepreneur 120

Entrepreneur North America Cofounder Silicon Valley 120

Gust

AUGUST 8, 2012

That’s two free drinks on this particular one-way trip from New York to California, a $10 value (although not worth suing over ). I’m no UI/UX designer or product manager, but I do work with entrepreneurs daily. On a customer satisfaction scale of 1–10, this experience scored a zero.

Customer 143

Customer Southern California San Jose Marketing 143

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

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. Revisiting the Software Design Manifesto (and what.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. When people start using quality, reliability, or design as an excuse to delay, it used to make me nervous, even when these suggestions were well intentioned. Rules of thumb can be infuriatingly unhelpful. And it’s really hard.

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

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

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). Perceived value - This is the extra value a customer perceives as a result of good marketing, product design, product quality, or exception product/market fit. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

JULY 13, 2009

It moves at a rapid clip, each argument backed up with the relevant math and equations: marginal profit , Littles law , Markov processes , probability theory , you name it. Its goal is to help us recognize that every artifact of our product development process is really just a proxy variable. This is not for the faint of heart.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

DECEMBER 14, 2009

I think this concept is necessary in order to answer the truly vexing startup questions, like: “Should startups charge customers money from day one?&# Let’s begin with the four customer currencies. I had a lot of use for this concept back when I worked on game design and virtual worlds.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

AUGUST 1, 2009

My guess is they have lots of people constantly working on interesting new tools for their designers to play with. Those new capabilities must translate into a constant stream of prototypes - most of which turn out to be utterly bad ideas. Discover whats in customers heads, and tackle problems where design is a differentiator.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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

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

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

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

MARCH 13, 2009

Do some Customer Development instead. New York Times, Wall Street Journal, CNN, the works. The product didnt convert well enough, the mainstream customers we were driving werent ready for the concept, and the event fed expectations about how successful the product was going to be that turned out to be hyper-inflated.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

APRIL 7, 2010

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 ). After you’ve spent months on a painstaking new design, who wants to be told what color blue to use? It takes some getting used to for most designers, though.

San Francisco 154

San Francisco Lean Metrics Design 154

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

San Francisco 164

San Francisco Lean Technical Review Software Review 164

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

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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