Error message: Major rewrite required. Volunteers?
On arrival in the office this morning I went through the usual routine of starting up my PC, opening MS Outlook and checking my email. With offices throughout the world this slightly mundane activity is my way of ensuring my To Do list is up to date with what has happened overnight. This morning I was taken aback by the error message below:
“Why isn’t that documented?”
Just before Christmas I was asked to write a post for the company’s blog. You can read it here. At its heart is how we used web 2.0 methodology to ensure that our users never asked, “Why isn’t that documented?”
“We don’t need a usability expert, we’ve got you.”
There I was minding my own business when one of the Programme Managers came to talk to a colleague about a project they are working on. During the course of the conversation questions of a more strategic nature came up and I was asked to get involved. At the end the Programme Manager gave me a compliment. “You’re the nearest thing we have to a usability expert” he said.
When developers are correct but get things wrong
Earlier today I found myself discussing issues with usability in applications. A couple of hours later I was documenting a feature in an application that demonstrated the real value of getting Technical Writers involved in the development process and the issues that can occur when they’re not. Take the example below.
Meetings, meetings everywhere
Something strange has started happening of late. Developers have started asking me to meetings! Whether they are to discuss UI design or progress meetings to see what is likely to be included in the weekly builds, I’m getting invited to them all. What is more, I don’t mind.
