Managing Those Pesky “Unexpected” Problems


The neat thing about running your own small startup and app is that you can determine the timeline for rollout for new features – there isn’t anyone that’s telling you to do anything that you want to do.

At the very same time, though, it can be a complete  stress ball as things that should be fairly objective and easily considered and calculated are now fraught with a massive mix of emotion and psychological warfare.

In other words, what might be a really simple solution ends up being something much more complex – and it’s your own damn fault!

For instance, over the last few weeks I’ve been gathering a ton of feedback from the community via our (new!) Community & Support site and I’ve isolated the bugs and the features that I want to roll out in version 1.1.

I don’t have a definitive timeline yet but I know I want to get it into the hands of our awesome users and community sometime next month, especially before the App Store closes down on December 22nd of this year.

Does this mean that I should work my tail off for the next week and burn the midnight oil? Probably not. Could I? Yes, I “could” do that. Do I want to do that? I’m not sure. Will it give me enough time to squash bugs? Probably. Should I do it earlier just in case? That’s a good idea. How much time will be enough time? I don’t know. What about that vacation you wanted to take with your girls and wife? Wait… what?

It all becomes a mental heap of confusion!

Many of you are probably better than me at scheduling and planning and could probably offer me tons of tips – as far as I can tell my so-called strategy is just working as best as I can with the limited time that I have and hoping for the best.

This is how I managed the “unexpected” problems and move toward solutions. It’s less reactionary than it sounds and it’s been working for me for years.

So, what about you? How do you do it?