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. Last year, I found myself back in Steve Blanks class at Haas, this time trying to teach the students about what its like running engineering alongside customer development. Thats pretty clear.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

OCTOBER 28, 2008

We pitch to potential partners, vendors, publishers, conferences, employees, and even lawyers. whos on the engineering team? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

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

JULY 3, 2009

The same has been true of an unfortunate number of startups, they manage to generate a lot of hype, raise a lot of money, and sometimes make some of their investors, employees, or founders rich. ericries #leanstartup Another new idea in the section on continuous deployment and the cluster immune system. Danger, Will Robinson.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

APRIL 29, 2013

So if you have advice that you think is relevant only to people working in established corporations, or only to government employees, or only to non-profit leaders, or only to innovative educators, or only to engineers, no prob—you can indicate that in your application. That said, we do have room this year for a handful of tech talks.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

MARCH 25, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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

NOVEMBER 8, 2008

I bought a bunch of copies, gave them out to my co-founders and early employees, and then expected the whole companys behavior would radically change the next day. I bought a bunch of copies, gave them out to my co-founders and early employees, and then expected the whole companys behavior would radically change the next day."

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

MARCH 17, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

APRIL 14, 2009

This is an incredible skill, one that most engineers overlook. 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. Case Study: Continuous deployment makes releases n.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

APRIL 26, 2009

That engine of creativity has led to a catalog of something like 2 million virtual goods authored by a hundred thousand developers. 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. Case Study: Continuous deployment makes releases n.

Product Development 88

Product Development Developer San Francisco Product 88

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.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Startup Lessons Learned

MARCH 4, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

OCTOBER 30, 2008

Everyone from the receptionist to engineers is selling. Over-communicate with employees, investors, customers. Ive also used the voluntary salary reduction tool - its particularly useful as a way to get passionate employees who dont have a lot of personal expenses to buy into the mission of the company at a deep level.

Lean 121

Lean San Francisco Continuous Deployment DC 121

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 16, 2013

We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. Here''s the simplest form of that cycle: Week -1 - Planning/End-of-Cycle - Software engineers are planning: writing specifications, doing light prototyping, and experimentation. It wasn’t always this way.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

JULY 2, 2009

For example, I often cite a real example of a problem that has as its root cause a new employee who was not properly trained. I pick that example on purpose, for two reasons: 1) most of the companies I work with deal with this problem and yet 2) almost none of them have any kind of training program in place for new employees.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JUNE 23, 2009

Priority will be given to employees of companies participating in the fbFund REV program, but I am confident that there will be room for members of the general public who want to attend. Case Study: Continuous deployment makes releases n. Pivot, don't jump to a new vision Why Continuous Deployment?

Lean 74

Lean San Francisco Continuous Deployment DC 74

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. Case Study: Continuous deployment makes releases n. Soon, I promise.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

MARCH 23, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

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. In fact theyd cause there to be more jobs for Americans, because the companies they started would hire more employees as they grew. Case Study: Continuous deployment makes releases n.

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

OCTOBER 19, 2009

Then, the company spends no more than a few hundred dollars marketing the product through search engines and to the contacts in its sales database and LinkedIn. 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.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. On the one hand, it gives you insight into what kind of employee the candidate might be. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. I have found this quite rare in engineers.

San Francisco 146

San Francisco Lean Agile Java 146

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. Its why, at my previous job, we were able to get a new engineer completely productive on their first day. why did that code get written?

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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. Case Study: Continuous deployment makes releases n. How can that be part of a startup?

San Francisco 168

San Francisco Startup Lean Continuous Deployment 168

Startup Lessons Learned

MARCH 31, 2009

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, and more ► January (6) Lo, my 18891 subscribers, who are you?

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

AUGUST 20, 2009

Because this radical notion of progress is located firmly in the heads of its employees, and not in any artifacts they produce, the lean startup is employee-centric and knowledge-obsessed. Case Study: Continuous deployment makes releases n. Its unit of progress is that of validated learning about its customers.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

AUGUST 1, 2009

Beyond Apple, we can find examples of the Steve Jobs character at Toyota, in the form of the Chief Engineer. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. The videos are Steve explaining the company's path forward to Next employees. August 2, 2009 9:50 AM Milton said.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

MAY 1, 2009

A: have them deploy code to production on their first day as an employee. Related articles by Zemanta Continuous deployment in 5 easy steps (4cloudcomputing.blogspot.com) The Lean Startup workshop coming soon (startuplessonslearned.blogspot.com) The Lean Startup Talk From Web 2.0 made a big impression. What else?"

Lean 60

Lean San Francisco Startup Continuous Deployment 60

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. Google was not the first search engine, but it's the one that succeeded. Case Study: Continuous deployment makes releases n. And yet, missing out on these trends wasnt the end of the world.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

FEBRUARY 11, 2009

Thats all helpful for recruiting, retaining, and ramping-up a new employee. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. You dont have to guess who their mentor will be.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

OCTOBER 6, 2008

Both are related to a common brain defect we engineers and entrepreneurs seem to be especially prone to. Especially for us introverted engineering types, there is one major drawback to talking to customers: its messy. Its pretty easy to optimize our business to serve one of employees, customers or shareholders.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

MARCH 27, 2009

Customer Development Engineering : techniques for accelerating your product development. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Hire a CTO or VP Engineering.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 17, 2008

For example, should we invest a week of engineering time into making our website more failure-proof (which were pretty sure will pay off right away) or into experimenting with a new technology (that might pay off in months, years, or never)? Case Study: Continuous deployment makes releases n. Lets get to the answers.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

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. Case Study: Continuous deployment makes releases n. How do they know they are making progress?

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

SEPTEMBER 27, 2010

Its easier to believe in a glorious future when you have only zeroes, for everyone: founders, investors, and employees. Its easier to believe in a glorious future when you have only zeroes, for everyone: founders, investors, and employees. Case Study: Continuous deployment makes releases n. Data can undermine this field.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167