The (slightly delayed) Big Four Oh

I normally strive to get these weekly braindumps sorted by Friday night. However, due to a busy week leading into a very busy weekend I’m writing this on Monday instead.

I’ve been working on…

Normally I jot down what I’ve been working on during the course of the week because of my recycle-bin-like memory. In my infinite wisdom I didn’t do that last week, so this might get a bit sketchy.

Monday was a bit of an Admin-ny day. Pulled some information together to get a hardware order underway. Did my usual trawl of ‘who do I need to cajole to move this project along?’. Urrgh.. project management.

My line manager was heading out the door on holiday for a couple of weeks, so we had a bit of a catch up just to make sure we were both aware of everything that is currently going on or is coming up.

Tuesday was spent diagnosing some weird database problems between two different services. This is one of those times where I’m reminded that integration between systems is often blutack and sticky tape because vendors don’t use open standards.

Also had a quick meeting about a business continuity testing. How do you best simulate a disaster to sanity check your disaster recovery procedures. How much of it can you practically do and how much is a theoretical exercise? Can’t go into too much detail about this because it’s a bit hush hush.. but I think we decided on a sensible halfway house between causing chaos and constructively learning some lessons.

Wednesday was a day off.

Thursday was mostly spent pinging back and forth between hardware suppliers to get an order for hardware sorted. I remember a time when I used to scoff at how little the likes of Apple changed the spec of their hardware.. now I can see very valid reason in not dramatically changing models every 6–9 months. Once you find a good bit of kit that suits your needs.. you really don’t want it changed all that much.

I also did an induction with one of our new board members. Pleasingly, she was really enthusiastic about the way we’re trying to use digital tools with the board.. so that bodes well. 🙂

Friday I had a meeting about a Health & Safety system. I was mostly there in an advisory capacity since (like so many things these days) the system is a service hosted off site.

The rest of the day was spent trying to tidy up any straggling tasks on the kanban board. Quite a bit sat in ‘doing’ this week which was mostly down to waiting for other people to close the loop. Not sure how best to combat that? Something to ruminate on.

I’ve been thinking about…

STILL thinking about that podcast idea (the one about digital/service transformation). I’m rapidly reaching the point at which I need to do something about it or just ditch it and move on. I think some small safe experiments to overcome my procrastination and feel my way into it. I’m currently looking at Anchor as an easy way to delve into the podcasting arena. As is often the case with side-projects, I’m worried about how much time it’ll consume.. and time is a precious commodity at the moment!

What else?

I’ve been thinking about how long I’ll be doing these braindumps for. They’re pretty useful as a reflective tool, but they also require time (there’s that time issue again) to pull together. Sometimes it’s a useful way to wind down the week and take stock. Other times, when I’m feeling particularly frazzled, it feels like it absorbs my Friday evening when I’d really like to be switching off.

I’m thinking of pushing through to 52.. just because it’ll represent a year of braindumps (although not quite a year time wise because I’ve had some weeks off for holidays). Then I’ll stop and see if I need to switch my approach up or do something different.

I’ve been reading…

I’ve been listening to..

Leave a Reply

Your email address will not be published. Required fields are marked *