By Jenn Vargas (Founder, Accompl.sh)
I'm about 18 months into the journey of taking Accompl.sh (formerly 101in365) from a little weekend project to automate my own annual goal tracking to a living, breathing web application.
Taking the "long way" of being a solo founder, I found working on Accompl.sh as a side project has been a crash course in time management, community building, product development, design, coding, you name it. But the most difficult part of all has been making the big decisions about the direction of the project itself.
Without a co-founder to help rationalize my own thoughts about the future of the product, I was stuck in a bit of a quandary -- Do I stay on the path I originally set out on, potentially limiting the growth of the site, but staying true to my original design? Or should I compromise a bit and open the doors for even more people to use the tool that I built and believe in? The answer may seem obvious, but when you're up until 3 or 4 in the morning working on your pet project in virtual isolation for over a year, it's not as clear.
Decisions, decisions. Over the last few weeks I've made a few major decisions about the future of Accompl.sh -- decisions I’ve been struggling with for well over a year but that I finally took the leap and acted on. I'll share a bit of the process with you all in hopes that it'll help you avoid the traps that I fell into.
Trap #1: Not fixing the things that bother you about your product
I was tired of explaining why I had so many arbitrary rules in my product every time so I shut down physically instead of just fixing the product.
... Read More...