This week the team was invited to present to a prospective customer. To impress the prospect we came up with a "wow-factor" feature and then jumped on building it.
Turns out the feature did the trick, impressing the prospect. In the office, there were high-fives all around. It's a small, but clear-cut win. It would be churlish not to enjoy it.
Small Win or Big Mistake?
As good as it feels, it's crucial to realise what made it a small win and not a big mistake.
It certainly was not the idea for the feature. In fact, it was actually the dangerous part.
We gave ourselves an opportunity to "over-promise but under-deliver" by rushing to ship wrong or broken feature.
Know the Difference between the Two
Without side-stepping an over-engineering landmine with a help of quick and clear white-board session we would have blown our tight deadline.
Without quick way to test the feature, out in the field the day before, the whole thing could have fell flat on the face.
Instead of kicking ourselves for doing too much and coming up short, we're feeling good about it.
Which is fine. As long as we know what made it, what could have broken it and what fine margins stand between the two.