The Web Designer’s Gambit
At Capulet, we do a lot of small, ad hoc web maintenance for our clients. While we’re doing their PR or writing their brochure, a client asks “hey, can you upload that press release, too?” We do it because no one in-house can.
In 80% of cases, the original site designer is long gone. They’ve created the site, delivered it, and gone on to the next project. I can understand why designers do this–maintenance is tedious, uncreative work. However, this phenomenon has two unfortunate results:
- The designer is unmotivated to design an a site that’s easy to maintain. They’re unlikely to touch it again, so they build the site the way they want, with little view toward extensibility and code re-use. So what if there’s three nested tables? It looks right today.
- The designer’s site slowly morphs into something else as we implement client requests. The web designer gets dismayed as their portfolio piece gets less and less like what they originally designed.
This is the designer’s gambit: they don’t want to update the site, but it’s the only way to maintain the quality and purity of their design.
Apparently few designers are actually worried about this gambit, though. For every new site we’ve designed (and we’re not really a web design company), we’ve maintained four. I’m surprised this is the case, because you’d think designers would want some reliable, recurring revenue.
While I’m on the subject of our design work, I’ve been meaning to link to CoastalTrek.com, a site we did for a health resort near Comox. It’s a Bryght site.
