New Newtype
February 24th, 2005I have to admit, one of the things I had in mind when I signed on at my job was getting in on some web design action. It wasn’t exactly obvious how I’d be able to do that, but because I had experience in web design for several years, it was something I was interested in. When I found out that there was a separate team working on web development, I was a little disappointed, but figured that was all for the best. Good, let them handle it, I said. At least, that was my initial reaction.
Like most companies who operate under a parent entity, the site was being managed under an umbrella structure, meaning that one team handled design, development and maintenance of ALL corporate sites. Unfortunately for us, there was a time when priorities had shifted and the magazine dropped in both relevance and status within that structure. In turn (at least this is what I was told) each division was given back control of their respective web presence, in order to free up man-hours for other projects. As a result, the magazine’s site quickly grew stagnant. Because it relied on a database-like back end, it became a chore just to update content and almost impossible to get quirks and bugs stamped out.
That’s when, after several months of nudging, I just couldn’t help it anymore. One day, I simply asked, “why don’t we just do this ourselves?” and surprisingly, I didn’t meet with much resistance. Instead, I got the go-ahead to work up some ideas.


