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

APRIL 26, 2009

The net result was powerful: within six months of starting the company, we were able to get a basic version of our product into open beta. Most importantly, there is almost no niche or trend that is unserved by this community. When you participate in an open community like these you take advantage of tremendous amounts of effort.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

NOVEMBER 19, 2008

I would recommend periodic surveys, along with some kind of forum or other community tool where the most passionate customers can congregate. Im Community Manager at VenCorps, co-host of commandN. Case Study: Continuous deployment makes releases n. Either way, Ive been a happy subscriber ever since.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

NOVEMBER 22, 2008

Lessons Learned by Eric Ries Saturday, November 22, 2008 Net Promoter Score: an operational tool to measure customer satisfaction Ive mentioned Net Promoter Score (NPS) in a few previous posts, but havent had a chance to describe it in detail yet. Net Promoter Score NPS is a methodology that comes out of the service industry.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

JANUARY 12, 2009

The number one reason I keep coming back to PHP is that it has overwhelming community support. Ive written elsewhere that success in creating a platform is "becoming a function not of the size and resources of the company that builds it, but of the size of the community that supports it." Lets start with some circular reasoning.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

NOVEMBER 5, 2008

We were building a community, open to anyone who shared its values, and that mission inspired volunteers and staff to try and reach out to as many people as possible. Case Study: Continuous deployment makes releases n. It would have been pretty easy for the volunteers and supporters to slow down, confident in victory.

Campaign 84

Campaign San Francisco Lean Agile 84