Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. 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

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

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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 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. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. I was really overwhelmed this time.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

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

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. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. Expo SF (May.

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. Anyone who has worked in a real-world product development team can tell you how utopian that sounds. Expo SF (May.

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. Expo SF (May. Conference streaming, sponsors, discounted tickets.

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. 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. Expo SF (May.

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. Expo SF (May.

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

A Smart Bear: Startups and Marketing for Geeks

AUGUST 30, 2010

He blogs to 10,000 web entrepreneurs at Software by Rob and co-hosts the podcast Startups for the Rest of Us. More than two years ago, my business partner and I discussed launching a hosted version of our ASP.NET invoicing software, DotNetInvoice. Agile Development, meet Agile Business. Introduction.

Software Review 284

Software Review Startup Technical Review Hosting 284

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

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Eric Names matter. There is a dark side to naming.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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

FEBRUARY 10, 2009

Heck, thats what it says right there in the agile manifesto. 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. If a feature worked, wed keep it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. 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 like this term. great metaphor.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Duct Tape Marketing

NOVEMBER 13, 2019

She is a leading diversity and inclusion expert, keynote speaker, author, and host of The Will To Change Podcast. What you really need is agile thinkers, thinkers who don’t have a conventional background for the role. I’m on Instagram at @jenniferbrownspeaks and then Jennifer Brown Consulting is the name of my company.

Hiring 39

Hiring Community Audience Bandwidth 39

ConversionXL

APRIL 3, 2018

Corporate Agility. Transparency correlates to agility (Does your CEO know how many tests you ran last month?). Map out each lifecycle stage and variations, and name each. Embed blog videos hosted on facebook so you can track consumption and advertise to them. Culture of Innovation. Continuous Optimization. updated footer.

Retention 106

Retention Artificial Inteligence Channel Email 106

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

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? . Expo SF (May.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

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. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

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. Its incredibly simple, and its called joblink.tw. Think of it as a bit.ly Using it to recruit takes less than a minute. Who wants that stuff posted on the internet? Expo SF (May.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

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

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

Startup Lessons Learned

OCTOBER 7, 2008

If necessary, consider doing this under a different brand name than the one you are wedded to using. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

San Francisco 68

San Francisco Lean Retention SEM 68

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

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. Combining agile development with customer developm. Expo SF (May.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. This team had been working for many months in a standard agile configuration: a disciplined engineering team taking direction from a product owner who would prioritize the features they should work on. What a waste. What a waste.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

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 13, 2008

We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down?

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 22, 2008

We had all the tools in place but we didn’t actually practice agile development. No fancy tools needed here — it’s about the mentality, attention to detail, and the actions that foster agile development, not the tools & systems you set up in place to facilitate this. 1 comments: Josh Moore said.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

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

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

YoungUpstarts

MAY 4, 2015

But there’s no guarantee that the places where most social networking happens now will be the same places hosting it in the future. This can help you spot trends more quickly and see search indicators you hadn’t considered before, allowing your brand to react with more agility and better adjust to your users’ needs.

Social Network 100

Social Network Vertical Networking San Francisco 100