A Quantum Immortal

Several years ago, back at Delver (Sears Israel nowadays), I learned from the great Moti Karmona the term Feature Owner (I think it was him, could have been Oren Ellenbogen as well, memory is fuzzy). One useful term I learned for Feature Owner. We’re using this quite extensively in Mastercoin, and I’d like to elaborate what this means.

A Feature Owner is just what it sounds – one person that owns a particular feature. The same can be extended to Product Owner, Release Owner, Domain Owner etc., but I’ll focus on Feature Owner in this post.

Features need love and attention to grow. They start off as an idea, and then go through some process of development, going through brainstorming, spec, implementation, debugging, deployment etc.

For progress on a feature to happen, someone needs to push that feature onward through the above stages. There are various walls to tackle – some of them are technical (how do we scale this to 1 billion people), some of them are political (how do we get head of Ops to approve it), and there are other types. The point is there has to be someone that cares enough about the feature to make it happen.

In Mastercoin, everything is done via Feature Owners. Sometimes they elect themselves in order to win a bounty. Other times, we actively seek out someone to own a particular feature. Even if a coding contest is not happening, you can just create your own feature and own it. In Mastercoin and other DACs, you can just decide on a feature, get approval for its funding if needed, and get paid when you deliver.