Startup Lessons Learned

JULY 5, 2010

I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. I used to give copies of Four Steps out to my employees, in the hopes that it would instantly indoctrinate them into the methodology of Customer Development.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

OCTOBER 4, 2008

Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) That institution will touch many people in its life: customers, investors, employees, and everyone they touch as well. Eventually, I came to summarize these themes with the phrase " the lean startup."

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

MARCH 16, 2009

In the case of C3, that was to run payroll for 87,000 employees, who were presumably receiving payroll before the project began. Notice that the unit of progress changes as we move from waterfall to agile to the lean startup. The Lean Startup Intensive is tomorrow at Web 2.0. Thats pretty clear. Just a thought. Expo SF (May.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

SEPTEMBER 30, 2008

When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. The Lean Startup Intensive is tomorrow at Web 2.0. Massive proprietary databases?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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 Lean Startup Intensive is tomorrow at Web 2.0. When I first encountered this book, my first impulse was as follows. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JUNE 17, 2010

Not to be outdone, the technologists on the team had also brought their big guns, and the meeting was packed with employees of every level – from VP’s all the way down to me. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

OCTOBER 28, 2008

We pitch to potential partners, vendors, publishers, conferences, employees, and even lawyers. Ill exclude those non- lean startups who basically exist for the purpose of raising bigger and bigger sums of money. How does a lean start-up find the all-star team worthy of pitching? 2comments: King of the Herd said. Expo SF (May.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

OCTOBER 26, 2009

Every two months, the company would have a big end-of-milestone meeting, with our Board of Directors, Business Advisory Board, and all employees present. Every two months, the company would have a big end-of-milestone meeting, with our Board of Directors, Business Advisory Board, and all employees present. Expo SF (May.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

OCTOBER 20, 2008

I now believe that the "pick two" concept is fundamentally flawed, and that lean startups can achieve all three simultaneously: quickly bring high-quality software to market at low cost. A new employee is more likely to make a mistake than an experienced one, but everyone makes mistakes. August 29, 2009 1:24 PM The Caretaker said.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

APRIL 14, 2009

This is why companies often get out-competed by former employees (Palm vs Handspring to name just one), even though the upstart lacks all of the familiar resources, tools, processes, and support they used to have. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

Customer 167

Customer San Francisco Lean Hockey Stick 167

SVPG

NOVEMBER 22, 2013

Protect Employees and Customers. In addition to protecting revenue and brand, we also need to protect our employees and our customers. Again, most changes and tests are non-issues, but it is our responsibility to be proactive with customers and employees and sensitive to change. See Assessing Customer Impact. It’s not.

Product 67

Product NDA Continuous Deployment Reputation 67

Startup Lessons Learned

OCTOBER 16, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference. As Lean Startup methods have been used now for a number of years, we’ve become increasingly interested in how companies use them to sustain growth. Continuous deployment: A key component of speed is to keep pushing out work.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

APRIL 26, 2009

Its a key lean startup concept. Its an amazing thing when you can hire an employee who knows more about your code base than you do, and this turned out to be a big source of advantage. For example, I recently created a customer validation exercise around the Lean Startup Workshop. Expo SF (May. for Harvard Business Revie.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

OCTOBER 30, 2008

Lessons Learned by Eric Ries Thursday, October 30, 2008 John Doerrs 10 lean startup tips I just saw video of John Doerrs talk yesterday at VentureBeat’s “How to manage your start-up in the downturn&# roundtable event. Over-communicate with employees, investors, customers. The Lean Startup Intensive is tomorrow at Web 2.0.

Lean 121

Lean San Francisco Continuous Deployment DC 121

Startup Lessons Learned

JUNE 23, 2009

Lessons Learned by Eric Ries Tuesday, June 23, 2009 Join the lean startup discussion at Facebook on Thursday I recently agreed to join Facebook s fbFund incubator as a mentor. Part of that includes giving a presentation for the fbFund companies on the lean startup methodology. The Lean Startup Intensive is tomorrow at Web 2.0.

Lean 74

Lean San Francisco Continuous Deployment DC 74

Startup Lessons Learned

MARCH 4, 2009

The Lean Startup Intensive is tomorrow at Web 2.0. ► April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0 Expo SF (May.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

AUGUST 20, 2009

Lessons Learned by Eric Ries Thursday, August 20, 2009 The Promise of the Lean Startup Im honored to have a guest post on GigaOm to introduce the concept of the lean startup to their audience. The ultimate goal of a lean startup is to identify where its vision intersects with what reality can accommodate.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

MAY 1, 2009

Lessons Learned by Eric Ries Friday, May 1, 2009 Lean Startup webcast post-game Wow, what an incredible turnout for webcast this morning, right on the heels of a phenomenal crowd at startup2startup last night. Its been a great twelve hours for the lean startup! wogsland : Still not understanding the "lean" aspect. What a thrill.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

MARCH 31, 2009

Lessons Learned by Eric Ries Tuesday, March 31, 2009 The Lean Startup workshop coming soon I am currently gearing up for my talk tomorrow at the Web 2.0 And today I am excited to announce a new experiment: the Lean Startup workshop. The Lean Startup Intensive is tomorrow at Web 2.0. Readers get an early sneak peak. Expo SF (May.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

MAY 7, 2009

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

MARCH 23, 2009

April 8, 2010 5:02 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

FEBRUARY 7, 2010

Whether youre a US citizen or an immigrant, entrepreneur or investor, founder or employee, theres something you can do. Whether youre a US citizen or an immigrant, entrepreneur or investor, founder or employee, theres something you can do. The Lean Startup Intensive is tomorrow at Web 2.0. Soon, I promise. Soon, I promise.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

SEPTEMBER 19, 2009

In fact theyd cause there to be more jobs for Americans, because the companies they started would hire more employees as they grew. Its actually part of a lean startup story. For more on his lean startup journey, you can take a look at this slide presentation. Its actually part of a lean startup story.

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

JUNE 21, 2010

Yet, the real stories of successful startups are full of activities that can rightly be called institution-building: hiring creative employees, coordinating their activities, and creating a company culture that delivers results. I emphasize this point because it is necessary to motivate large amounts of the theory of the lean startup.

San Francisco 168

San Francisco Startup Lean Continuous Deployment 168

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

MARCH 3, 2009

Lessons Learned by Eric Ries Tuesday, March 3, 2009 Employees should be masters of their own time Every startup should have a culture of learning. The rule is simple: every employee is 100% responsible for how they spend their time. The suggestion is that you implement one single company-wide rule. I asked why.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

OCTOBER 19, 2009

We do not develop a product until we get a paying customer," says Orit Pennington , who co-founded the six-employee company with her husband in 2002. This article is part of a trend that has taken me a bit by surprise: the adoption of lean startup techniques outside the traditional domain of high-tech startups. Read the rest.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

NOVEMBER 29, 2008

On the one hand, it gives you insight into what kind of employee the candidate might be. It amused me because I knew that these things rarely matter and my answer conveyed very little of my value as an employee, but it frustrated my interviewer. The Lean Startup Intensive is tomorrow at Web 2.0. I use the circle question, too.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

SEPTEMBER 27, 2010

Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. Its easier to believe in a glorious future when you have only zeroes, for everyone: founders, investors, and employees. I won’t apologize for this aspect of the Lean Startup methodology. Pivot or persevere?

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

NOVEMBER 13, 2008

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Instead, five whys kept leading to problems caused by an improperly trained new employee, and wed make a small adjustment. why did that code get written?

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JULY 9, 2009

Then I wouldnt have the chance to work with the incredible employees and mentors from whom I learned so much. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

MARCH 13, 2009

They spend so much of their time trying to convince everyone around them that their idea is great and the company is doing well: employees, investors, partners, friends, family, significant others - its a long list. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" Plus, the premise of the question misunderstands the lean startup, too. And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

FEBRUARY 11, 2009

Thats all helpful for recruiting, retaining, and ramping-up a new employee. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Expo SF (May.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

MARCH 27, 2009

In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. And, of course, theres the Lean Startup session at the upcoming Web 2.0

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

MARCH 24, 2009

March 26, 2009 12:18 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

Metrics 88

Metrics San Francisco Lean Viral 88