Common pitfalls
4 Common pitfalls
Prioritizing wow-factor over substance
Yes, PowerPoints can feel sterile, and well-designed websites are sexy. But while there’s real value in style, don’t disassemble a slide deck and convert it to a microsite only because you’re looking for “cool” points. Often, slides are an incredibly effective form of presenting information, like when you have a story you want to move through linearly.
In a case like that, if you take out all that content and re-assemble in a web page, it might be less focused.
However, you might want to include your set of slides inside a microsite, so you benefit from the power of digital—but be intentional with your communication choices.
Overloading your microsite with too much content
Among the benefits of microsites is flexibility. You can pretty easily add anything you want, and there are very few parameters. That introduces tremendous possibilities.
But that same flexibility also puts you at risk of adding too much. With something like a slide deck, it starts to become very obvious if you have overloaded the deck with too many pages, or pages that are too dense. The microsite doesn’t have that same page counter, so you might end up adding too much content if you’re not mindful. Overdoing it can not only create a confusing user experience, but also make things very difficult on your design or development team.
Now, there are times that including a lot of content is a requirement. An example of this would be if you have a section on research, and you need to include links or downloads for 12 different papers. To avoid this pitfall here, you must organize that content, or giving it enough space for the user to be able to scan, interpret, and assess the information available to them.
Lacking proper security
You might have scoped all the design, development and content elements to get the page to function properly, but security and visitor authentication are no simple task.
It’s important to make sure you have the capability, and it’s executed in such a way that it makes for a smooth client experience. Is a password sufficient security? If you need more, like token-based authentication, are you sure the system you’re using to develop the microsite has the capabilities, or performs such authentication in a way that’s clear and reliable to your visitors?
To avoid unnecessary delays, get these details resolved early in the process.
Letting your microsites become too costly
Launching a microsite means putting the page through a design and build process. Your site must be also be deployed and hosted on the Web, and in some cases, it will need to be updated as well.
While microsites can be resource or time intensive, they don't have to be. With the right process and technologies, effective microsites can be produced and managed with a very reasonable amount of investment.