Perfectionist Tips: Plan and Prioritize

20 January 2017 ·

When I started developing a productivity tool - Whubi - I was so enthusiastic about it and was so motivated to work on it beside my 40-hours-week for another 30-40 hours a week.

But then surprisingly I found myself in a trap that I basically created myself. That led my motivation down and even caused my brain to constantly finding all kinds of excuses to stay at home and try to finish all my stuff.

The Idyll

Initially, I was trying to balance my work: a bit of development, a bit of marketing, a bit of user communication, some development operations, a bit of here and there. Everything was aligned perfectly and I wasn’t overwhelmed with my tasks, so I could easily switch my activities if I feel that I got tired.

I was wearing all the hats and doing a lot of stuff, using my own creation for moving things forward and seeing areas of improvement.

I had all the needed metrics, so I could at least say to myself how well I’m doing.

I had a plan. I was trying to plan for not that far future and still to have high-level goals, which allowed the product to evolve in a more or less predictable way.

And then suddenly things started falling apart.

The Bug

I was so enthusiastic to make everything perfect, that I started doing more work than I planned to bundle more features, fix more bugs and generally make my product even better. And instead of creating a good pressure, which is usually useful for a perfectionist, it created a bad pressure, when nothing in the world could help me to achieve my goals in a given amount of time.

I had a plan and a list of things I wanted to do, but one small bug got my attention and I couldn’t let it get into the final build. Trying to fix this one bug led the other feature to be reworked a bit, what led to two other bugs, which led to reworking some other parts of the application and by the end of the planned time, the whole app was broken.

So all the vital fixes and improvements were not delivered. And this created, even more, pressure and I couldn’t get out of this stuff.

Rule #1 for perfectionists:

Stick to the plan!

Found a bug? See an urgent need for a feature? Plan it. Don’t let it distract your attention!

Everything is relative and sometimes fixing a show-stopping bug will be a better idea than adding a nice-to-have feature.

Still, priorities are the key. In my case, everybody could live with a bug that I was trying to fix. Nobody actually reported about it.


Whubi is alive and is working fine with a few small glitches, however, it’s in a forever-beta stage, which is another topic for the future post(s).

Update - 01.10.2017

Unfortunatelly I couldn’t manage to do all-sides development as quickly as it was required to keep the project alive, so Whubi went to the infinite holiday.


Might also be interesting for you

React Router + Connected Component

A tip on how to fix issue when using connected React Router v4 and Redux in React

Use Elm as a Reducer in Redux

Want to use Elm in your project, but a bit hesitant going cold turkey? In this blog post I'll try to show how you can use the best from both worlds bulletproof Elm logic and ridiculously rich React components library.

Open RSS Reader

I'm starting a new open-source project "Open RSS Reader" that will be modular app so if you don't like the existing clients, you'll be able to quickly build your own. It's gonna be both open source and free to use.

SotM: pet - Awesome Command-line Snippet Manager

`pet` is a simple command-line snippet manager. It allows you to write and store snippets for the command-line, so you don't need to remember all the commands you frequently use in you terminal. It can sync your snippets to the GitHub Gist, so you can always take your snippets with you.


comments powered by Disqus