Startup Lessons Learned

SEPTEMBER 30, 2008

In my roles as CTO for various startups, its been an interesting repeating cycle for the CTO to have to wear lots of hats especially in the early days: from start-up systems architect to code monkey to development manager to ops manager then finally to CTO as the business scales over time and these roles warrant dedicated full-time staff.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

David Teten

OCTOBER 1, 2015

incubators, e.g., the many options in New York. intrapreneurs, e.g., the employee of GE who is tasked with launching a new business. Customer development would be reduced to a single person exercise that could be repeated in parallel dozens of times over, ultimately yielding 30+ companies a year.

Software Developers 60

Software Developers Software Development Software Review Technical Cofounder 60

Startup Lessons Learned

OCTOBER 5, 2009

If not, maybe an investment in that direction would be more warranted. If not, maybe an investment in that direction would be more warranted. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? There are two principal reasons why this second approach is better.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

SEPTEMBER 11, 2009

I agree that listening and communicating is a key to success, but customer development can only do so much. There was also a litany of errors made in determining which developers had in fact passed UFI products into the catalog warranting their punishment. Eric September 13, 2009 11:32 AM Joel Andren said.

Community 158

Community Management Lean Software Review 158