The work I keep putting off
I find it easy to make a product more complicated. There is always something to add, and adding it gives me the pleasant feeling that I am getting somewhere. Whether it helps anyone is a question I can put off while I work.
Over the past eight years, I’ve started six companies, sold two, and watched one grow fast. I’ve built ten products with varying degrees of success and advised dozens of ambitious entrepreneurs. I still have to remind myself to ask people whether they want the thing I’m building.
Even that question can come too late. Sometimes I haven’t understood the problem well enough to propose a solution. A mockup, a design study, or a landing page can help me find out before I spend weeks writing software. I like building things. It takes some effort to admit that building may not be the work I need to do yet.
I’ve become wary of “let’s see what happens.” It sounds open-minded, but it leaves a team with very little to learn from. I’d rather write down what we believe and what would convince us we’re wrong. People can work separately or together; at least we’ll know which questions we’re trying to answer. Later, I want to be able to compare what I expected with what actually happened.
There are plenty of other ways to stay occupied. Metrics, marketing gimmicks, a promising partnership. Before product-market fit, any of these can take over the day. I have a fairly uncomfortable test for a vanity metric: I want to brag about it, and I know it has no bearing on whether the business makes money.
Then there is the feature we haven’t finished. I can make a convincing case for waiting until it’s ready. But what if it never is? Does growth depend on that feature as much as I’ve persuaded myself it does?
Some of this hesitation comes from how I talk about my work. I’ve played the humble card too often and apologized myself out of opportunities. If I believe in the product and the people building it, I owe them a better explanation of why it should exist. A clear vision helps with that. It also helps everyone decide what deserves their time when the work becomes a grind.
The unfinished work isn’t going away. There will be users to find, money to raise, people to hire, vendors to pay, and a team that needs help. I’m trying to get more comfortable with choosing what can wait. A roadmap needs room for us to discover that an idea was wrong. A small founding team needs time to find its center, without spending so much time thinking about itself that nothing gets made.
I keep coming back to a personal ambition: I want to help and empower people. One way I’d like to do that is to help 1,000 people build a home or pay for their housing. I also want to help people learn how to learn. Those are useful things to remember when I’m deciding which problems to spend my time on.
They were part of why I supported our acquisition by OpenCoin (the company that built the Ripple token). Its goal of “distributing wealth on a global scale” appealed to me. I believed that lowering the cost of sending money and removing layers between transactions could help people keep more of what they earned, including in Africa. I could see a connection to housing, and to people becoming more self-sufficient.
That is a large ambition. The next decision is usually much smaller: what to build, whom to ask, what to leave unfinished. I’d like to get better at remembering the people I meant to help while I’m making it.
My work at the time included I Can Has Cheezburger?, I Has a Hotdog!, MyChamberApp, and simplehoney, which was acquired by Ripple. More of that story is on my About page.