Need someone to lead product management at your software company? I build high-craft software and the teams that build it. I'm looking for my next opportunity. Check out my resume and get in touch.

This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.

Milestone payments

Freshness Warning
This blog post is over 17 years old. It's possible that the information you read below isn't current and the links no longer work.

That hiring post of Frank Demmler’s drifts into some discussion about milestone-based funding. An entrepreneur agrees to funding terms that in order to get the next round, certain milestones must be met. Hire a VP of sales by Q3. Land 40 advertisers by December 15th.

Frank says...

In the beginning of my career working with early stage businesses, I believed in milestones and tying investments to their achievement. Conventional wisdom was (is?) that milestones help to keep the management of early stage ventures focused.

That assumes that the milestones agreed to at the closing remain the company’s priorities.

In my experience, though, that’s rarely the case.

Things change. Priorities shift. In some cases, strict adherence to the milestones may hurt the company. The conflict between the specifics of the milestones and the company’s needs are often difficult to resolve.

If you’re a first-time entrepreneur, all you know is that getting the next round of funding depends on hitting the milestones. The fact that things have changed is troubling, but you can’t tell your investor that you were wrong (even if the changes had absolutely nothing to do with anything you said or did). You fear that if you try to change the milestones, it will be seen as a sign of weakness. Instead of admitting and addressing the important issues, you play ostrich and forge ahead with meeting the milestones.

Twice I’ve agreed to milestones and been burned. The priorities did indeed change and we moved along with the changes. We shifted our efforts to meet the new realities of the business, but when it came time to collect the money, we had some problems. The milestones hadn’t been met. The contracts all pointed to hitting milestones.

We eventually worked it out, but it was a tense time and caused a lot of distrust between the parties. In one case, it nearly ruined the business.

Recently Written

Think Systems, not Symptoms
Dec 15: Piecemeal process creation frustrates teams and slows work. Stop patching problems and start solving systems. Adopting a systems thinking approach helps you design processes that are efficient, aligned with goals, and truly add value.
Your Policies Aren’t Your Culture
Dec 13: Policies guide behavior, but culture is the lived norms and values of your team. Policies reflect culture -- they don’t define it. Netflix’s parental leave shift didn’t change its culture of freedom and responsibility. It clarified how to live it.
Lighten Your Process Burden
Dec 7: Everyone hates oppressive processes, but somehow we keep managing to create them.
Product Add-Ons Are An Expansion Myth
Dec 1: Add-ons can enhance your product’s appeal but won’t drive significant market growth. To expand your customer base, focus on developing standalone products.
Protecting your Product Soul when the Same Product meets New People.
Nov 23: Expand into new markets while preserving your product’s core value. Discover how to adapt and grow without losing your product’s soul.
Building the Next Big Thing: A Framework for Your Second Product
Nov 19: You need a first product sooner than you think. Here's a framework for helping you identify a winner.
A Framework for Scaling product teams
Oct 9: The people, processes, and systems that make up a product organization change radically as you go through the stages of a company. This framework will guide that scaling.
My Networked Webcam Setup
Sep 25: A writeup of my network-powered conference call camera setup.

Older...

What I'm Reading