Startup Lessons Learned

JULY 13, 2009

He shows how the actions of people inside traditional systems are motivated by their rational assessment of their own economics. Reinertsen does not speak about startups specifically - his book is meant to speak broadly to product development teams across industries and sectors. Wow, great review!

Product Development 153

Product Development Developer San Francisco Product 153

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

OCTOBER 5, 2008

I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. Labels: product development 8comments: Vincent van Wylick said. Expo SF (May.

San Francisco 158

San Francisco Management Software Review Product 158

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

dontbesoanalytical.blogspot.com

MAY 13, 2012

The CTO should not manage developers. The head of development spends his or her time working to keep the development team on track against a set of product plans. Inside the development organization, this Director attends to staffing, training, workload and productivity metrics, budget, and scheduling.

CTO 40

CTO Technical Review Technology Software Review 40

Startup Lessons Learned

NOVEMBER 8, 2008

VentureHacks did a great summary , which includes slides and video. The theory of Product/Market Fit is one key component of customer development, and I highly recommend Marcs essay on that topic. Our goal in product development is to find the minimum feature set required to get early customers. What is customer development?

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. Still, a startup product development team is a service organization. What is customer development? Using AdWords to assess demand for your new online.

San Francisco 146

San Francisco Lean Agile Java 146

www.forentrepreneurs.com

FEBRUARY 2, 2010

Business model viability, in the majority of startups, will come down to balancing two variables: Cost to Acquire Customers (CAC) The ability to monetize those customers, or LTV (which stands for Lifetime Value of a Customer) Successful web businesses have long understood these metrics as they have such an easy way to measure them.

Acquisition 103

Acquisition Cost Customer Entrepreneur 103

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. Expo SF (May. Try About the author.

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

Startup Lessons Learned

OCTOBER 20, 2008

Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors. A project usually has an absolute duration and budget whereas the time and money dedicated to development within the project is where the tradeoffs are made.

Software Review 164

Software Review Engineer Management Technical Review 164

trada.com

APRIL 7, 2010

Notably VentureBeat cited that five of the 26 companies that presented at Y Combinator Investor Day were still in stealth mode. With ZenDesk you can front your email with a “support@” address and with Google Voice you can front your account management team’s cell phones with one consistent phone number and voicemail. Great post!

Stealth 40

Stealth PPC Advertising Conversion 40

Occam's Razor

NOVEMBER 1, 2006

These paper prototypes, sometimes called wire-frames, approximate what a user might otherwise see on a computer screen, but save the development team from having to produce an on-screen product. Often times lab usability tests are also recorded on video for later review and also to present to a larger audience in a company.

Analytics 85

Analytics Web Software Review Customer 85

Occam's Razor

JANUARY 7, 2007

9: Don’t forget Flash, Flex, RIA, RSS, Videos etc. Best practice is to run this nice little program, or your own equivalent, once a week and send a report to your web development team with a list of pages missing the tags. # 9: Don’t forget Flash, Flex, RIA, RSS, Videos etc. 7: Redirects, be aware of them. #

Technical Review 93

Technical Review Analytics Web Software Review 93