Strategic planning
It’s important to properly define your strategy before tackling your site redesign. What we recommend is to perform an inventory and fairly deep analysis of your digital ecosystem (including your site, your mobile application if you have one, CRM, chatbot tool, newsletter platform, etc.). This will enable you to identify its existing strengths and weaknesses, but also determine its underlying opportunities and threats.
Start by studying your Analytics data—they’re full of revealing insights. It’s important to go beyond the default reports in the platform—you need to segment and cross-reference your data, and also take context into consideration. This way you can easily identify the site’s current pain points and better understand your users’ journey.
An analysis of your site’s content and branching structure can also give you more context on your offering as well as potential shortfalls considering your current priorities.
Don’t waste time performing a UX analysis of every page of your site—remember that you are going to rebuild it. Instead focus on key pages (which should be determined based on your goals, your content and your data) and functionalities. It’s important to take a step back if you are performing your own site analysis, because although doing your own analysis may not be a problem for you, it could be for 90% of your audience.
Talking about audiences, do you really know who your users are? Your redesign work must align with your personas. Your analysis will allow you to update your personas or uncover new, interesting targets. Don’t forget to listen to your users, since their voice is essential for ensuring your hypotheses are valid. Remember that your personas can be based on existing ones, but also on market opportunities.
Since you’re on a roll, continue your investigations by looking at your customer journeys. They are your best allies for orienting your digital strategy and tactics to reach your audience, but also for responding to your customers’ needs at each key step.
Tips: Integrate a final line into your customer journey by adding objectives and their related KPIs to each step.
With your analysis of the existing site, consumer input and market trends, strategic directions can be defined (if they haven’t already started to emerge during the analysis) and tactics can be dissected. Don’t forget to define your measurement metrics for each tactic.
Specifications
It’s time to put down on paper exactly what you want. Writing up your specifications isn’t a must, and the content will vary depending on the amount of precision you want.
If you are using a third-party provider, it’s advisable to materialize the site and its functionalities on paper using a spec sheet. In this way you ensure you are precisely describing the requirements to be respected during development. The spec sheet should also echo the digital strategy you’ve already defined.
If we return to our e-commerce sales site example, we wanted to increase our conversion rate of 5%, so one of our strategic pillars will probably be related to the experience of using the site. We therefore decide to integrate a new chatbot tool to enrich customer experience and reach out to visitors who need advice or reassurance. You must therefore stipulate in your specifications sheet that you want this functionality.
Depending on your project, the spec sheet can be fairly dense and complex. We recommend creating 2 categories:
- Technological and technical requirements: This section refers to the ecosystem and technologies (CMS) you intend to use. Don’t forget to include your requirements on who owns the code developed, security criteria, speed, hosting, the content delivery network (CDN), Google Analytics implementation, etc. If you are doing a redesign, this is the time to clean up and/or improve your technological infrastructure, so don’t be shy.
- Required functionality: This refers to all functionality that is “visible” to the user that you want to include on your new site. This can range from simple things like leaving your site’s header on top while scrolling to more complex functions like real-time delivery tracking. We recommend listing all your functionalities so you are sure not to forget anything, then prioritize them if your budget does not allow all of them to be set up.
Depending on your project, you can add other categories like design or content requirements, for example.
This document is essential for requesting bid submissions from suppliers that provide estimations of costs and timelines.
Tender process
Will the designer be able to infuse the site with the sensibility you require? Are the developers comfortable with the technology you’ve asked to be implemented? Will the agency be able to properly manage the project?
These are questions you should ask yourself at this stage of the process. It’s important to take the time to properly choose your external resources for the project. With your call for tenders and specifications sheet in hand, you can be sure to weed out those suppliers that do not correspond to your criteria.
After receiving the submissions, plan to interview your top 3 to learn more about their approach, work methodology, the timeline, budget, and also to ensure there’s good communication between both parties.
The selection criteria are up to you, but don’t just look at the price—take the entire offer into consideration. Sometimes it’s better to set aside a bit more budget than planned to produce something that is truly top of the line. Ask yourself again, What kind of experience do you want to offer your customers?
Development
Congratulations! You’ve chosen a partner!
Now the real work is just getting started, since you’re about to go through a long, crucial step: development.
Depending on the scope, site development can take anywhere from 3 months to 1–2 years. Luckily you should now have access to a web project manager that will help you complete your site redesign.
This person will serve as a bridge between you, the developers, the designers and the marketing specialists in order to keep work within deadlines and satisfy the requirements laid out in your specifications.
Overruns
Unfortunately, unforeseen issues are common and can upend the smooth roll-out of website delivery. A non-functional API, a delay in integrating visuals, a bug that’s hard to fix, etc. You should also be aware that the more involved you are and the more of a perfectionist you are, the greater the risk of experiencing overruns.
Healthy communication between you and your project manager will allow you to reduce these risks.
SEO referencing
Involving an SEO resource is highly recommended to ensure you obtain a website that respects indexing standards and promotes easy discoverability for your future website.
An SEO specialist will also limit the risk of losing traffic that is often associated with complete redesigns.
Before development, the SEO resource can frame these requirements (functional or technical). Depending on the CMS used, they can also recommend extensions. For example, on a WordPress site, I would recommend an SEO extension (like Yoast) and improve compression and the distribution of images.
During development, various questions can be directed to this resource. These questions generally regard requirements, best practices for indexation or keywords/content. During this period the SEO specialist should be working on a redirect plan.
After development, the SEO specialist needs to perform quality assurance with regard to the initial requirements. They will deploy and test the redirects in a testing environment. The objective is to deploy the redirects at the same time the site is launched.
Following the site launch, the specialist will follow up, ensuring that users aren’t landing on error pages and that Google can properly access the new website.
A reduction in organic traffic is generally normal for 3 to 6 months after a redesign. Your site could lose between 20% and 30% of its sessions during this period. A temporary increase in your SEM budget might compensate for these losses.
Analytics
During the creation phase (wireframe or visual model), take the time to isolate the elements that you want to track in Analytics to obtain a richer range of data. Remember that we recommended integrating KPIs into your customer journeys—this will help you begin the work of creating a tagging plan.
The tagging plan enables you to determine the metrics (supporting your KPIs) that you should integrate into your pages. For example, you should want to know whether the chatbot is used and how it is used. Therefore, you should indicate that you want to track when the chatbot is opened (GA event on click). You can add a multitude of data depending on your objectives and the depth of information you intend to have. As you know, here at Adviso we’re data gluttons, so go crazy!
Consider using Google Tag Manager for tracking, since this will facilitate the integration of new events, objectives and metrics over time.