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. You might get a bunch of inbound emails from other press and partners, and all of these things can contribute to a feeling that you’re on your way to getting tons of traffic. It strokes your ego.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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. The book takes its name from Steves theory of the four stages of growth any startup goes through. Phases of product & company growth.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. Then, create an encouraging environment for early-stage companies. I was really overwhelmed this time.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 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. Sounds very similar to agile development which is the way. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Im a huge fan of small batches as well.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

OCTOBER 20, 2008

When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. 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 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. Check if the currently logged-in user is part of this experiment already.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

APRIL 14, 2009

Now, in some situations, this over-selling would lead to a secondary problem, namely, that customers would realize they had been duped and refuse to re-subscribe. Go on an agile diet quickly. With a product development team that is not shipping, any agile methodology will surface major problems quickly. Great post! Expo SF (May.

Customer 167

Customer San Francisco Lean Hockey Stick 167

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. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. Reconciling these principles requires a little humility.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

OCTOBER 26, 2009

In previous posts, I’ve mentioned quite a few of these, including these most important ones: having engineers post on the forums in their own name when they make a change routinely split-testing new changes routinely conducting in-person usability tests and interviews Net Promoter Score Each of these techniques is fundamentally bottoms-up.

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. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Keep them coming. Expo SF (May.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JANUARY 18, 2010

Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009. My transition to Continuous Deployment Prior to adopting continuous deployment, I used to release software on a weekly schedule (come rain or shine) which I viewed as pretty agile, disciplined, and aggressive. Expo SF (May.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

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

www.smashingmagazine.com

MAY 5, 2011

Ask for a User Name After The User Has Signed Up Sign-up forms typically ask users to create a name that is unique to the website. However, coming up with a unique user name that’s not taken could take trial and error and, thus, time. Give users the option to log in with their email address as well as a user name.

AJAX 104

AJAX Security Design Naming 104

Duct Tape Marketing

JUNE 20, 2023

He is co-leader of the McKinsey Digital Practice, a senior partner based in New York, and a member of McKinsey’s Shareholders Council, the firm’s board of directors. Duct Tape Transcript Email Download New Tab John Jantsch (00:00): Hey, did you know that HubSpot's annual inbound conference is coming up? Like this show?

Technical Review 66

Technical Review Silicon Valley Generative AI Arizona 66

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. Some caveats right off the bat. August 3, 2009 8:08 PM William Mitchell said.

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

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

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you. This is not for the faint of heart.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

MAY 25, 2020

44:25) Parallels between the pandemic and previous crises, and Carl's thoughts on some of the new norms that will arise. (45:28) And then from there, I was running a fitness company on the west coast by the name of 24 Hour Fitness, which was private equity backed and quite a bit of debt. Stanley McChrystal's Team of Teams. (29:34)

Technical Review 148

Technical Review Balance Sheet Texas Austin 148

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

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 actual exchange of information occurs in private, in email. Just write a few words about them, set their email address as the private recipient, and tweet about it.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

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? (a

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

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. Labels: agile , continuous deployment , lean startup , product development , Test-driven development 4comments: Nivi said. But, unfortunately, startups cant afford to adopt that standard.

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. If you're interested please send me an email. Great post! Expo SF (May.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

OCTOBER 7, 2008

Do you have a way to notify them by SMS or email when something notable happens? If necessary, consider doing this under a different brand name than the one you are wedded to using. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF.

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

MARCH 13, 2009

New York Times, Wall Street Journal, CNN, the works. Who doesnt want to see their name in print? Now that were beginning our first marketing, the key partners we need have heard our name long enough to trust us. I wrote a little bit about the epic launch we had at a previous startup in my post Achieving a failure.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 27, 2010

Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. In fact, we know so much that we already know what they will care enough about (namely, the product’s quality – as opposed to, say, missing features). However, a commitment to quality alone is not enough.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

bhargreaves.com

MARCH 7, 2010

Plus, most decent dev shops can point to at least a couple names of well-known previous clients. Actually any shop that does agile development with daily and weekly releases should. Scissor.com is another agile option. Agile dev shops should bring discipline and quicker results. I’m talking to them.

Hiring 40

Hiring Technical Review Agile Software Review 40

Startup Lessons Learned

MARCH 24, 2009

A few days ago, I received a great email from Warhammer Online. And yet, WoW never sends me emails. 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?

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

JULY 2, 2009

Pay attention to whether people are comfortable “naming names&# in the meeting. 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?

San Francisco 164

San Francisco Lean Technical Review Software Review 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. While simple, it is easy to manage.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 18, 2008

All I see is a name, an icon, a price, the developers name, and a review star-rating. 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?

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

AUGUST 1, 2009

In talking with Mary Poppendieck about it, she said that the Chief Engineer role at 3M was called a "Product Champion" The name is less important than understanding the depth of competence that this person has, and what it takes to build it. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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

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. And who can blame them?

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

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. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF.

Customer 156

Customer San Francisco Viral Lean 156