Category: Project Management


I’ve been using the free, old version of activeCollab for years and was pretty happy with it, except for one major problem – there’s no way to save a project template. So every time I created a new project, I would spend 1-2 hours setting up all the milestones and tasks.

That was getting very time-consuming, so I started looking for other solutions. Basecamp was pretty good but seemed expensive with its monthly payments – $24 to $49 per month depending on how busy things were. Then I looked at the paid version of activeCollab.

It looked good -very similar to what I had, but quite enhanced from that level. I bought a $10 hosted demo that was fully functional for 30 days, and used it for three projects. I loved the fact that I could now create a project template (or as many as I wanted) – that was the biggest thing for me.

So my demo expired and I was ready to buy. activeCollab comes in two versions – Small Biz ($199)  and Corporate ($399). Two of the main differences were that the Corp had both the calendar and time tracking. I could live without those, so I bought Small Biz.

Today they sent me my hosted demo database so I could import my projects into my new install. That worked flawlessly, but when I logged in and started working on one, I kept getting an error.

I went back to their site and discovered that managing tasks, which I would consider to be a crucial, default-level function in any project management applications, apparently  is not important for small business users.

I spent quite a lot of time researching my options, then actually using this software in the last month. I like AC a lot – but if I’d read the list of differences more carefully I would probably have not even considered this product.

Now I’m not sure what I’m going to do.  Should I fork over the additional $200? That really rubs me the wrong way, paying for something that IMO should be included as a very basic feature. But if I spend more time going out and looking for something else, would I just be better off giving in and buying this upgrade? Ack ack ack.

The beginning of the year seems like a great time to get on top of some business issues that have been dragging along more or less unattended to for awhile.

In 2005, when I started my web design business, I wrote a process document that was really a stab in the dark, with tasks pulled from a few books. In 2006 I rewrote it, using information gleamed for the most part from a really good book by Kelly Goto and Emily Cotler – Web ReDesign 2.0: Workflow that Works (2nd Edition) (VOICES)“>Web ReDesign 2.0. This was a really helpful book for me but it’s written for those redesigning existing sites that are a lot bigger than my clients’ sites.

Last weekend I revisited my 2006 version again. It was not bad, but my process has changed as I’ve gotten better at, well, everything. Some parts are not there anymore, or fused into others. I also noticed that there are some things that I was doing early on that I haven’t paid much attention to lately, and that’s not good.

So I rewrote it again, borrowing from the Gogo/Cotler book, a few design articles I’ve read recently, and my own experience. The final document (Red Kite Creative Formal Design Process) is lean, simple to follow, yet thorough, and reflects both what I’m doing well and the things that I need to focus on more closely. Mostly those things are the pre-visuals, like writing a full project plan and wireframing. I sitemap thoroughly, but I don’t wireframe that much. In some cases I should be doing that more.

The process document isn’t a set of rules, but a record of the workflow that works well for me right now. It will continue to change, I’m sure. But I know that if I eventually have a partner or employee, I want this document ready to be used as an outline for the way I develop websites.

I won two jobs this week – one doing maintenance and content updating for a medical office, and the other translating a new graphic layout into a functional web template for the local university. I’m really excited about the academic work – I spent a lot of time in upper-level academia and enjoy working with researchers as I have in the past on other projects. Plus, the university has a working style guide and strict ADA requirements. I always make an effort to address accessibility issues on the sites I design, but have never actually had to do it before. I think that will be a good learning experience for me. View full article »

© 2012 position: relative; All rights reserved. Powered by WordPress.