Skip to main content

My user manual


A couple of years ago, one of my colleagues introduced the idea of a personal user manual to the design team. It didn’t really take hold as a ‘thing’, but I quite liked the idea.

I think it came from Cassie Robinson’s post, where you can also find some templates to go from.

The aim is to give your colleagues an easy to scan overview of what makes you tick:

  • The conditions you like to work in
  • The hours you prefer
  • The best ways to communicate with you
  • The ways to give you feedback
  • Things that you need
  • Things you struggle with
  • Things you love
  • Other interesting stuff

The key is, at least for me, that it’s all about soft skills. Or soft stuff, as it’s not always about skills, per se.

If nothing else, it’s a nice bit of self-analysis, which is something I should probably do more often.

Anyway, here’s my user manual. I hope it gives you a bit of an insight into how I like to work, and maybe it’ll prompt a bit of an activity within your team so you can understand each other even better.

Get them delivered!

If you enjoyed this and want all the latest articles delivered to your inbox every month, pop your email in the form below.

I don’t collect any data on when, where or if people open the emails I send them. Your email will only be used to send you newsletters and will never be passed on. You can unsubscribe at any time.

More posts

Here are a couple more posts for you to enjoy. If that's not enough, have a look at the full list.

  1. The difference between strikethrough and del

    Just like <em> and <i>, and <strong> and <b>, the distinction between <s> and <del> is subtle, but it’s worth knowing.

  2. Git restore to discard changes

    I no longer use git checkout to switch branches; I’ve also stopped using it to discard uncommitted changes: let me introduce git restore!