I'm an old-school developer. I got my start in the 1980s. I have fond memories of handing in an IBM punch card deck, 2 inches thick, then waiting until the next day to see if my class assignment ran as expected.
We're now in an age where our servers are virtualized and rented by the hour from Amazon.
The point is, everything changes.
For the past few years, I've been communicating with our clients by emailed screen shots. I take a capture of a new screen, type out what's changed and how to use it, and what button to click. Then a new screen appears, so I take a capture of that screen and type out what to do next. Lather, rinse, repeat.
Recently I tried switching to video documentation, and so far it's been a positive experience all around.
To accomplish video documentation, I used a tool that I'd already subscribed to – GotoMeeting. In addition to the meeting functionality, GotoMeeting allows you to record your meeting, which includes video of your application and audio from your computer microphone. I'm sure there are better ways, but this was available and easy.
I start a meeting, show my screen, and start the recording. I talk for a few minutes, clicking and talking out loud to describe the what/why/how. If I need to wait for an operation to finish, I can stop recording for a bit, then resume where I left off.
The result is an MP4 file that I save to the MBI web server. This gives me a link I can publish by email, which I then send to my client. The email is short and sweet … "Hi, here's the new proposed feature, take a look at the video and let me know what you think."
So far, client response has been positive. It communicates the point of the change far better than screen shots, including far more detail, and it takes about the same amount of time to do.
I think it's a keeper. At least for a few years.