Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. It usually looks like this: the can-do attitude and high-bandwidth communication that characterized the first few iterations have produced magic. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

MARCH 4, 2009

Your writings are so very thought provoking, and now reading them will take a slice of my ever diminishing bandwidth. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Dear E, so good to come across this.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

ConversionXL

APRIL 3, 2018

Embed blog videos hosted on facebook so you can track consumption and advertise to them. Understand growth accounting – new, resurrected vs churned = net growth (can also look at this at feature level, not only product). Work hard to define meaningful product metrics – enabler of team success. updated footer.

Retention 106

Retention Artificial Inteligence Channel Email 106

Startup Lessons Learned

FEBRUARY 16, 2009

Then we could render the whole site with much less latency, bandwidth usage, and server cost. The system would monitor their data and if it looked within norms gradually offer the release to a small number of new users (who had no prior expectation of how the product should work). Startup Lessons Learned - the Conference (April 23.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68