Collaboration rarely happens smoothly 100% of the time. You can influence your client’s website vision with factual evidence attached to options you created together, but there will be times when the client’s final preference is his or her original plan. How do you move forward?
Author: Denise Eisner
Denise Eisner is a senior-level web strategist and communications specialist with a passion for creating enhanced user experiences. As a member of the Government Service Excellence practice, Denise’s experience and specializations include web strategy development, information architecture, web analytics (WebTrends and Google Analytics) and web project management. She has led large-scale content audits, developed performance measurement frameworks, and coordinated site updates to meet Treasury Board policies standards and guidelines. Engaged in the evolving spheres of information technology, corporate communications and media for almost two decades, Denise has transformed business objectives into web strategies and information architectures for corporate and government clients in the U.S. and Canada.
Building a collaborative solution
It’s not uncommon for clients to come to us with fairly established web solutions they think will work. read more
Understanding requirements and results
The program lead stops by your desk with a web publishing request: update his entire site with a new tagline and logo, plus new content, a video and a blog, by end of fiscal year. He asks you to also prepare a deck to the senior management committee about the new approach for the site by next week. read more
Is there something more we should think about when planning enterprise IT initiatives when it comes to change management in an agile context? read more
As a content strategist working on Canada.ca, I work with government departments who want to understand how the new site will support their content. They want to know for example which template to use, the best practices for writing page titles, or how to format lists.
Aside from these practical concerns, there’s an equally fundamental issue to consider as departments prepare for the move to a single federal government website. read more
“Don’t dumb down my content.”
“Legal said so.”
“My manager will change it back.”
These are some of the responses I’ve heard in client meetings when we try to promote plain language writing for Web content. This type of writing conveys information easily and unambiguously by:
- using straightforward vocabulary and sentence structures
- organizing and presenting material clearly and logically with the most important facts at the beginning and the less important details toward the end of the content
- avoiding jargon and idioms
So to commemorate International Plain Language Day on October 13, I offer three techniques for countering the anti-plain language arguments and making your existing or future content awesome for Web users.
I’ve heard more than one government client say that he or she didn’t have the time or budget to think about the implications of mobile when developing online content. Getting approved content online in both official languages and in accordance with multiple TBS policies and standards was daunting enough, and it stretched staff and budgets. If considered at all, “mobile” was thought of in terms of mobile applications. read more
A massive migration of content currently sitting on various government department websites is set to culminate in one home for most Canadian federal government information and services: Canada.ca. This new site will let anyone look for content without having to visit multiple websites. read more