The launch gap.
At Happy Cog, the structure and scope of each project is different. Sometimes we architect, design, build and integrate everything into a content management system. Sometimes we only design. Sometimes we only code. Lots of times we hand off templates to our client to implement on their own.
Before we deliver our design and code to a client, it goes through hours and hours of QA. We don't ship something we're not proud of. We may need to make a few compromises here and there that causes the end result not to be exactly how we would prefer, but we're not doing anything that we aren't comfortable standing behind. Not every client agrees with us on every point we try to make, but we do everything we can to make a compelling case.
Sometimes, after we deliver our template code, our clients face their own challenges. Compromises can be made to meet a business objective, or to make code play nicely with a publishing platform. Like making copies of a mix tape in the good ol' days, fidelity can also be lost if something is passed from one person to another. And these actions can have downstream adverse effects on accessibility, usability, findability, and any other '-ability' you can think of. So you have to have a plan.
When we announce that a site we worked on launched, for better or for worse, we're put under the microscope. Our colleagues and critics scrutinize every last detail. Most of it is very positive, and it feels good after such a ton of work. However, if they see something that raises a red flag, breaks a rule or best practice, or is simply misspelled, we hear about it. And frankly, we love it. This feedback helps us tremendously as we perform our post-launch audit and prepare for our post-mortem. We don't see our job as finished once a site launches. We continue to work with our clients to resolve any issues we (or anyone else) finds. When you build a new house and move in, things break. Drywall cracks, lights flicker, pipes leak. Then, the builder comes back with a punchlist and fixes that stuff. You can't anticipate those things in advance.
So, in short, thanks for helping us do our job.






Comments [0]