Process

· 11 minute read

In late 2017 I was asked to write a strategy on how to manage and produce support documentation for the University of Warwick’s web publishing team, which develops web and mobile applications in-house.

The number of web applications had increased since I joined Warwick in 2012. Help pages were in large banks of FAQs (frequently asked questions). Over time, they had become difficult to navigate and keep up to date. After a successful trial to incorporate documentation work with the development cycle for one application during 2016-17, there was a successful model to follow. The challenge was to identify the scope of documentation work in total and how to scale up the trial to a full service of 17 applications.

· 4 minute read

It’s been a heck of a week – one of those where I’ve beaten myself up for not solving particular problems or delivering work I’d committed to doing. I close my eyes and see Chrome’s Developer Tools seared into my eyelids. The toughest part has been not finishing the first draft of an article I’ve been due to write for a while. A combination of writer’s block, imposter syndrome, and disappearing down a code rabbit hole has ended in the inevitable result: no words on the page.

· 4 minute read

I attended a training session recently on how to organise your work and life based on David Allen’s GTD (Getting Things Done) methodology. The trainer covered how to define your own ‘contexts’ or tags – common identifiers for tasks based on type, geographical location, relationships with other people, timeliness and energy level. He then described how to implement this system in Outlook and OneNote. Thinking about how and where I work, and who with, I made the following tags: