Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

NOVEMBER 17, 2008

Now its time to start to think seriously about how to find a repeatable and scalable sales process, how to position and market the product, and how to build a product development team that can turn an early product into a Whole Product. What is customer development? Using AdWords to assess demand for your new online.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JUNE 8, 2009

Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. That’s because many of our reports feed us vanity metrics: numbers that make us look good but don’t really help make decisions. Too much of this data is non- actionable.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

SoCal CTO

FEBRUARY 13, 2013

Once you build it, they will now ask you about the key metrics that they need proven in order to see if you really are a good investment. Even with these, you will have paper-tested your MVP, but the reality is that customers will not be able to assess the value to them until they actually use it. Review the code being built.

Technical Cofounder 338

Technical Cofounder Technical Review CTO Hire Fractional CTO 338

Startup Lessons Learned

OCTOBER 20, 2008

As I evolved my thinking, I started to frame the problem this way: How can we devise a product development process that allows the business leaders to take responsibility for the outcome by making conscious trade-offs? When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

DECEMBER 7, 2008

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. I am basically a one-man shop.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

APRIL 26, 2009

The idea of leverage is simple: for every ounce of effort your product development team puts into your product, find ways to magnify that effort by getting many other people to invest along with you. It allowed me to assess the market demand for that offline product before I had the final product baked. Expo SF (May.

Product Development 88

Product Development Developer San Francisco Product 88

blog.expensify.com

APRIL 24, 2012

How about reviewing some of the incredible work being done by the likes of Mark Rendle, Ben Vanderveen, Alex Robson, Jon Skeet, Chris Patterson, Glen Block, Rob Eisenberg or Steve Sanderson? I run a.NET development team and before this gig I spent 4 years running a web app written in.Net. March 26, 2011 at 1:15 am.

Java 107

Java PHP Software Review Coder 107