With web development becoming more user-friendly and accessible yet more complex, it’s important to remind myself of the importance of the user experience – that is, the elements that make visiting & using a site so much easier and enjoyable.
I’ve put together a quick, non-inclusive list of five questions to ask myself when adding a feature to a web community. Read the rest of this entry »
Tonight I’m closing rozzo.org, which I created 2 years ago not only to create something for my family but also to improve my skills for Joomla-third-party software integration. In deciding that the time had passed for this domain, I thought it useful to suggest several reasons to stop development of a site – and turn off the lights.
The most obvious: no traffic. If your site is not generating “sufficient” traffic by “core” users in your target audience – all terms that are subjective and that have been defined at the outset of your project – then you either need to work to generate traffic & use, or to stop investing your time, money & sweat.
Another not-so-obvious reason, and one that even I resist admitting: some has built a better mousetrap. Yes, it’s possible that a similar site exists, and if you cannot compete or cannot develop a unique selling propositin that distinguishes your site from others, then admit defeat and move on.
The web and technology render many sites, domains, business models and pricing obsolete. Although it’s essential to constantly update, redesign and/or evolve your site, it may be untenable or just plain exhausting to maintain competitive.
In the case of rozzo.org, it’s been a case of all three: only a dozen family members registered, no one (me included) desired to create and maintain an online genealogy, online services are free and really good (!), and although I considered re-inventing the site for anyone with the family surname (quite a bit bigger, international, multi-lingual responsibility), in the end I decided to pull the plug on this project. The domain expires next January.
I think it’s good to do a post-mortem: try to comprehend the causes that do and don’t make your site work, take the lessons that you’ve learned, and move on.
