Valuable Lessons Learned From Building a New Website

I know what you’re thinking … this is going to be another article about how to build a website. While I could have given you a Website 101 primer, I think our time is better spent telling you what I learned when I recently built a website for a client.

In full disclosure, 1) the client is SWK Technologies, Inc., a Sage software reseller and developer in New Jersey that also brings its clients custom programming, network services, HR counsel and several other offerings; and 2) I didn’t actually build the site myself. We had help from an outside provider. What I provided was counsel on all aspects of the website, from the initial concept to turning it on. I also had lots of help from the executive team at SWK.

The bottom line: This was not something I did all by myself, but I did learn a few valuable lessons along the way in what is now the time of “Web 3.0.” Here are my observations:

Expect change. Yes, I know that change is constant. But when you’re putting together a new website, the number of changes in the concept, content, navigation, execution and just about anything else occurs at a very rapid pace. It’s okay to change the game plan along the way as long as it makes sense. In other words, don’t change your plans just because someone wants to control a certain situation, which leads me to the second lesson.

Establish your ground rules from the start. Sure, everyone should play nicely in the sandbox, but as the consultant, I made my point crystal clear that I was not in the business of playing games just to feed someone’s ego. As a result, the changes we made — and many of them were very significant — occurred because there was a business case involved. I have to give kudos to the SWK team for sticking to this resolution.

Choose a provider you trust, but don’t expect miracles. I’m not going to tell you who the provider was. Overall, the experience was positive, but I walked away from this project understanding that what I may think as “customer service” isn’t always the same for the provider offering the service. My lesson? There are no stupid questions. What you may think is a stupid question probably either hasn’t been thought of by the provider or the provider may believe you already know the answer to the question. My advice is to ask as many questions as you want; after all, you’re paying for service, so you can, at the very least, expect answers. This leads to the next point.

Set deadlines for your own milestones and for the provider, as well. Hopefully, you are creating a website with a plan in mind for the site, but I think it’s equally as important to set firm deadlines so you can hit your milestones. If the end result of turning on the new site is scheduled to occur 12 weeks from now (that’s really fast), then you’ll need to structure your plan accordingly. If you’re running behind (which certainly happens — and it happened here), then adjust as needed.

When I say to set deadlines for the provider, you need to talk with the provider about a reasonable response time to get your questions answered and the work accomplished. What the provider may think is reasonable may not sync with your own requirements. Make sure you are in agreement with this; it won’t be nirvana every time you need something, but you can at least strive to expect a certain kind of response.

There IS life outside WordPress. We wanted a Content Management System (CMS) we could use ourselves rather than rely on the provider to make changes (while we were working on the site, and once it was turned on). On the advice of the provider, we used Drupal, a system similar to WordPress that was reportedly more robust. These days, when folks manage their own CMS, WordPress seems to be the de facto choice. It’s easy to use, easy to manage, and comes with page after page of built-in help and lots of other help via simple Google searches.