Startup Lessons Learned

MARCH 25, 2009

In keeping with my recent theme of blogging about upcoming events, Im happy to announce that Ill be speaking at Agile Vancouver on April 21. For those of you who subscribe to the blog for substantive content and whatnot, I promise to get back to more regular posts soon. Case Study: Continuous deployment makes releases n.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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. I would love to see some blog posts on any experiences you have had with set-based design.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

MARCH 17, 2009

Ill do my best to match deserving people up with appropriate sponsors, and Ill be glad to recognize those that give on the blog and at the conference itself. I am wondering if your event will be streamed live (or at least you will blog about it) as I will not be able this summer to visit the US (i am currently in Canada).

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

OCTOBER 28, 2008

We pitch to potential partners, vendors, publishers, conferences, employees, and even lawyers. 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 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

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.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

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. Case Study: Continuous deployment makes releases n. Startup Lessons Learned season one : Every post from the blogs first year in print form.

Technical Review 164

Technical Review San Francisco Lean Software 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. Looking forward to more of your posts, this blog is a favorite of ours right now! Great post!

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

APRIL 26, 2009

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. Doing the market test required this blog, a SurveyMonkey account and a PayPal account - and nothing else. Case Study: Continuous deployment makes releases n.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

OCTOBER 20, 2008

A new employee is more likely to make a mistake than an experienced one, but everyone makes mistakes. Of course, we wouldnt have a new employee write a huge new feature on their first day - usually wed start with a simple cosmetic change or bug fix. Case Study: Continuous deployment makes releases n.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

MARCH 4, 2009

Thanks to those of you who were willing to fill out the survey, I learned my net promoter score (about 25) as well as some clear other segmentation insights: about 80% of you are founders of or work at a startup, you read many of the same other blogs, and many of you would like to engage with Lessons Learned in formats and venues beyond this blog.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

MAY 7, 2009

To illustrate this point, I want to excerpt a large part of a recent blog post by Owen Rogers, who organized my recent trip to Vancouver. 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.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

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

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

Lean 121

Lean San Francisco Continuous Deployment DC 121

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

Hi Eric, Just came across an interesting MVP - listed as a comment on the 37 Signals blog. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. May 23, 2009 12:07 PM Dan Hodginssaid.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

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

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

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

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. Each is described in separate essays on this blog, but let me say a few words about how they work together – especially for companies with big ambitions.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

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. I know the audience on this blog, and Ive become comfortable writing in the long-form style I normally use here.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

MARCH 31, 2009

April 2, 2009 5:41 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?) Haha good point.it

Lean 68

Lean San Francisco Continuous Deployment DC 68

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

MAY 1, 2009

One big idea that I havent had a chance to write about on the blog yet is answering the question "What is a startup?" A: have them deploy code to production on their first day as an employee. Case Study: Continuous deployment makes releases n. Much of the content is shared with the Web 2.0 made a big impression.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

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

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. Great blog BTW, adding this to my favourites. OH>>> they can, since i have an ezine and blog, too.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

JULY 9, 2009

Much of what Ive learned over the years has been invested in this blog, and that makes creating a sweeping summation challenging. Then I wouldnt have the chance to work with the incredible employees and mentors from whom I learned so much. Great post - I learned about your blog as you answered my question at Aardvark.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

NOVEMBER 29, 2008

On the one hand, it gives you insight into what kind of employee the candidate might be. Balancing competing objectives is a recurring theme on this blog - its the central challenge of all management decisions. Case Study: Continuous deployment makes releases n. I use the circle question, too.

San Francisco 146

San Francisco Lean Agile Java 146

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

As Shutterstock has grown, there are a few key elements to our continued development speed: Small, autonomous teams: The more a team can do on their own, the faster they can go. Continuous deployment: A key component of speed is to keep pushing out work. Over a thousand people work here now.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

AUGUST 1, 2009

Lessons Learned by Eric Ries Saturday, August 1, 2009 The Steve Jobs method Image via CrunchBase Its been a long time since I did a post that was primarily a link to another blog with commentary, but I came across something today that I really want to share. The videos are Steve explaining the company's path forward to Next employees.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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

Startup Lessons Learned

MARCH 27, 2009

This post has been removed by a blog administrator. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Startup Lessons Learned season one : Every post from the blogs first year in print form.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

NOVEMBER 17, 2008

It has to balance competing goals of establishing clear ownership, while avoiding talented employees getting stuck. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

OCTOBER 6, 2008

Its pretty easy to optimize our business to serve one of employees, customers or shareholders. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. I think Drucker said it best.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

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?)

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

DECEMBER 7, 2008

Our online media company is small, we have 6 employees, great proven leaders, great talent, great cashflow. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94