Startup Lessons Learned

OCTOBER 21, 2013

So we spent some time iterating--leanly, we thought--on the revenue model. Lastly, we used to track deploys to production because we were so proud of our continuous deployment practice, but past a certain threshold (we are somewhere north of 200 deploys a month) this is a vanity metric. Challenge #2: Technical Debt.

Lean 152

Lean Startup Metrics Silicon Valley 152

Startup Lessons Learned

NOVEMBER 17, 2008

If youre making revenue, you should be finding ways to grow it predictably month-over-month; if youre focused on customer engagement, your product should be getting more sticky, and so on. Case Study: Continuous deployment makes releases n. And if you neglect maintenance, you may not have a business left at all.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

NOVEMBER 8, 2008

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. The four kinds of work, and how to get them done: The four kinds of work, and how to get them done: Five Whys Where did Silicon Valley come from?

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

AUGUST 24, 2009

Most publishers are still caught up in an outdated “vision vs. metrics&# argument, which is already obsolete here in Silicon Valley. What is the right revenue model? Second, mass-marketing will continue to play an important role in creating awareness of products and services. Thanks again for a great post.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JULY 9, 2009

We were focused on revenue, but we didnt understand that revenue is not important for its own sake in an early stage company. And then, at my first Silicon Valley startup , I watched friends get laid off in successive waves as it started to fail. Case Study: Continuous deployment makes releases n.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

usersknow.blogspot.com

APRIL 30, 2010

It’s not enough to just launch a feature and see if your revenue increases. You need to have some sort of plan for testing to see how it’s affecting key metrics , whether those are revenue, retention, registration, user happiness, or some other number you care about. How Am I Going to Get Feedback on this Feature?

Software Review 40

Software Review Agile San Francisco Advisory Board 40

Startup Lessons Learned

NOVEMBER 22, 2008

The whole episode cost us hundreds of thousands of dollars in lost revenue. In fact, it was the revenue trends that eventually alerted us to the magnitude of the problem. Unfortunately, revenue a trailing indicator. Its a great time to increase revenues without spending money on acquiring new customers.

.Net 158

.Net Operations San Francisco Lean 158