Workweek 02×05: Dance, Dance, Dance

Jumping straight in, Monday started with me organising my week. I sat down and scribbled the usual list of projects and known tasks/aims in my book. This week, for more context, I added in what I did last week and what’s coming up next week. I’m not a big fan of focusing on just what’s happening now. The other stuff is still there, bouncing around.

At some point, I also tried moving my week’s tasks into Trello. So now I’m sort of split between Trello, Wanderlust, and my notebook. Previous efforts have involved post-it notes too. Maybe I can merge them all into some sort of Mega ToDo List X. But on the other hand, it doesn’t really matter if you don’t have a set structure. Do what works. Evolution is all about what works, not what’s “better” or “worse”. Go with your feels.

After the morning weekly lookahead, a few of us talked through our new(ish) product pricing structure which Kim’s done a brilliant job of organising. We agreed we need to establish it with partners, to make sure everyone’s able to put the same information forward. Otherwise Things Go Wrong – changing information or expectations halfway through a conversation is confusing and inefficient.

it was a complex discussion (Tipsy-tip: Always schedule complex or difficult discussions for the start of the week and the start of the day, when you’re fresh) and I wasn’t quite sure what the boundaries of it were to be.

[Related Sideline, Feel Free To Skip, TL;DR: “Listen to the meaning of the words, not the people.”]: Anonymous conversation online is often deprecated as people think participants can say anything, which allows them free reign to be an idiot. In my experience, it’s the setup and culture that determines whether the participants are idiots, anonymous or not. I’ve always enjoyed anonymous conversations because it forces you to focus on the content and the discourse, the balance and interplay between not just the words, but their meaning – what people are trying to get across. I have a theory that anonymous/pseudonymous discussion can make you a better listener and arguer. [Sideline ends.]

Listem to the rhythm.

[A return from the sojourn.] Sometimes a meeting feels like an organism, with opinionated information coming in from everywhere at once to form a common endpoint. I’m finding one of the “arts” of “Management” is to listen to everything, track the threads, act as a sympathetic judge crossed with a documentary curator. I was tired for this meeting, but also relaxed thanks to some simple breathing exercises that had hit my RSS stream the day before, and I ended up staying out of the conversation a bit more than usual, only chipping in to add something I thought was being missed, or move things in a direction.

By the end, everyone else had told me what I needed to do, and it was something I’d been meaning to do for ages anyway. At first I had a bit of resistance to that, but I think that was the tiredness. After a few minutes out of the room and away from the office, I realised the discussion meant I had to do very little thinking for myself (which is probably why I haven’t done it already yet), and that actually I just had to write it down and send an email. Result.

[A second sojourn into “transmission”.] On top of my monitor, a tiny gemstone has been blu-tacked [TM] for a couple of years now. I got it at a company workshop – drew it at the end from a cloth bag as a symbolic takeaway. I forgot what kind of stone it is instantly, but I remember what it symbolises: “communication”.

Communication of what, to whom? Maybe that’s the secret. I suppose “transmission” might be another word – in times like these, I feel like my a key part of my job is to move ideas – and their reasons, their benefits – from one place to another. From one mind to another. Break down silos, from personal ones to departmental ones to company ones and beyond.

From pricing in the morning, we moved on to a meeting on changes to Australian areas, and how they affect us. That’s kind of how an OCSI day rolls (and possibly why I’m knackered by the end of the week). We have a fairly sick (should be “quick” but sometimes, hey, autocorrect wins) chat and think we have a good way forwards. This stuff is What We Do, even if we forget it sometimes.

I’m pretty tired today, and on into the evening. But grumpy, feel like I need a break from things a bit. The to do list has felt a bit incessant and scattered recently, and I keep getting a desire to clear it out and start again, a bit like my desk last week. I’ve never found a good way to do this though, electronically or physically.

I’ve got Tuesday and Wednesday off, so I’m going to give myself a break and check back in on Thursday.

[Curtain falls. Darkness picked out by Emergency Exit signs. Sounds of laughing and bumping from somewhere far away. Curtain up.]

It’s Thursday. I’ve spent two days with kids, messy play and a playground full of school children. Made up stories at bedtime, and a cherubic assembly. It was great.

I get in late after school assembly, a decent coffee, and a sparse train timetable. I arrive halfway through the fortnightly sprint meeting, which is an interesting chance to observe a snapshot of meeting room energy, a fresh perspective on our ritual. I notice how difficult we still find certain aspects of our development process – we’ve put a lot of effort into categorising and estimating well-defined tasks accurately. But we still seem to fall over and muddle through when the definition is yet to be hammered out.

The sprint meeting is the one aspect of our ritual that has survived 100 sprints. It’s evolved ok, along with the sprint itself. But it feels like we need some better structure for the work that leads up to it. And some disruption to happen before that can even happen. Lots of options, but some team buy-in needed first, just to shake the habit. A week’s disruption here is months of confusion saved later. A couple of other team members might be good to talk to here, if I ever make time for it. I’d add it to my list of priorities for the month ahead. But I don’t have that list. Maybe I do now?

I have some important emails to write today. I set aside some time Monday and in the cafe to write up a draft of one. Over lunch, I take a break, and realise I’ve overcomplicated it – the draft email was perfect, but only for getting my own thoughts in order. It’s the throat-clearing piece, the author’s timeline, the working prototype. But it’s not the email to send. I go back, take a copy, and send an email a quarter of the length. It works. I feel like I’ve learnt something important here:

  1. It’s ok to write like you’re going to send (or publish).
  2. It’s ok to throw it away, start again, and send something less than half as big.
  3. It’s ok to help other people to reply. Don’t litter inboxes with cognitive load. KISS. I wish I could put that in my email signature.

We invent a new way for 3 people to play on one table football side. It confuses us. We lose. But, I think, maybe with more practice…

Then have a really good catch up with Luke and Stefan, the other Directors. We talk to each other about what our roles and responsibilities have been over the last few months, as we’ve been developing these fairly ad hocly, and haven’t had a chance to reflect on it yet. It’s good to do, to talk so openly about it with each other.

Personally, it’s a chance for me to look at what I like doing, what I want to do better, and what I want to do less of. Broadly speaking, I enjoy making stuff, so I like the dev work and building the dev team. I’m getting more and more into Product work alongside that – Product Ownership, and in particular product design, and UX. I don’t like working weekends or scrabbling for time, so forward thinking and planning (aka “strategy”) is big on my books.

I could happily drop project management though – maybe I’d enjoy it more if I could dedicate myself to it, but it jars with planning what to make, how to make it, and then making it.

And there are things which glue it all together. That “Communication” stone I mentioned above is maybe just a necessity, the transmission of synchronicity that means the creative process can happen across everyone at once. Communication is about unblocking vision across an organism. Joint understanding. Shared fluidity.

By the end of the meeting, I’ve scribbled some things which I think make a good manager down on a post-it:

  • set targets & expectations
  • support team members
  • make decisions
  • step in when needed (by asking questions)

I start out Friday by helping Alex (dev) with wrapping up his piece of development – it’s good work in some tricky codebase, and he’s really tackled it head on and by himself. And I feel like a senior dev again, which is nice – we delve a bit into re-factoring approaches and class design, although afterwards I wonder if that’s the best way of imparting knowledge; does stuff stick if it’s not part of the core task? How would I know? Can I summarise the advice I’m giving for future reference?

Then there’s some admin stuff in the middle of the day, which I’m trying to get better at on a Friday. Spring out invoices, emails, scheduling 1:1s, getting a haircut, etc. Calendars are full of holiday over the next month and a bit, so it’s difficult to get the important chats in place any time soon.

Then I do a bit of own-time in the afternoon. I’d read about some simple storytelling for website design, and wanted to give it a go. Google Doc open, blank screen, it felt like an hour and half of automatic writing. The challenge – what’s the story about OCSI I would want to tell, and how could I tell it? I tried different approaches, starting with what I know already (how I introduce us to people I just met), and moved on to things like a TV advert, and a newspaper front page. TBH. if you’ve made it this far, you deserve a “treat” – here it is. Don’t judge.

Finished the week well by getting our core library to pass all its unit tests. SMILE.

Workweek 02×04: The Zen Machine

I still read. Curled forms on curled paper, ancient glue in the air, fingerprint grease leaving interminable stains In beige faded margins. I admit it, I read for the experience as well as the content. Each page turn is another step, each paragraph break a little rest on a wooden bridge by a small, inky stream.

Last week I finished reading Zen in the Art of the Tea Ceremony, a book with a backstory embedded in the ramshackle shelves of a crumbling, life-threatening bookshop somewhere just outside Bournemouth. While zen/tao literature already lines many of my bookshelves at home in an ironically physical way, it’s always refreshing to re-immerse myself in that other universe set out within a book.

Real world effects therefore abound this week. I have zen on the brain. Talk of utensils, ritual and symbolism has cleared a few thoughts into focus this week. Forgive me a brief distraction from everyday dust:

1. What we are permeates how we do something, and where we do it. And vice versa – we are our environment as much as our movements. A beautiful plan is let down without equally beautiful implementation in beautiful surrounding – because they are all different aspects of the same underlying beauty.

2. We are always in transition and in context. Fail to pay attention to where you were, and where you’re going, and you’ll be out of alignment. You can know how long a book is, but you can’t read it in the wrong order.

I’m finding that these weeknotes are an increasingly playful way to rewrite my own past, in order to acutely, subconsciously, magickly influence my own future. Last week is just as important as this week. We weeknotes reflect, but we can’t always tell you if the mirror is facing forwards or back.

So this week’s weeknotes are an attempt to catalogue a journey, a trip taking in a rich abundance of routes leading from place to place. A project is not a project, but a vicinity, an area of town. An interaction is a cafe, a temple, a train station.

I’m wandering here.

(p.s. I write up zen-ish thoughts elsewhere if you’re interested.)

Day One

The train meanders between different morning routines, individuals including mee, shaken out of habit. The track wanders between harsh economies and unruly power games, rocks sticking out of the cutting, nettles waiting to be cut back at the height of summer. Three carriages, one for each of the Holy Trinity. Grim rows, fresh encounters.

The shake-up of daily routine deposits me in a new pocket of time, somewhere around where Monday wakes up. I climb into the pocket with a coffee, and draw out a twisted, listed vision of the week ahead. It’s a busy sketch, fragmented and messy, full of spires and troughs and dangerous climbs.

I arrive at my desk, and thinking back to the casual, dedicated simplicity of the Japanese tea rooms etched In my mind last week, decide to clear out all the layers of paper that palimpsest my keyboard. It feels good. I wonder if my desk reflects me, or if I reflect my desk.

The Monday morning team catchup feels relaxed, in among the chaos. The usual round-up of what’s happened and happening elsewhere. Luke runs through a financial update. What link is there between a management presentation, and a Punch and Judy show?

Before lunch I catch up with our Australian client – there’s a bit of tree lying in the road, and there’s some work here to try to think about the best way either to clear it, or find another route. The tree has been there, fallen, for some time. But fresh leaves are growing out, traces of seeds, life beneath the bark.

After lunch I take a step back, into the dirty but fascinating industrial zone. I’ve summoned the developers / engineers / coal-shovellers to gather ideas about error logging and better debugging. There are hundreds of years of cogs and pistons and cranks and strange batteries whirring away behind us, as we draw our circle of salt around us and carve glyphs into whiteboards. I know I want to spend more time here, but I struggle to know if I’m a local, a tourist, or a tourist guide here. Maybe I’m a tourist guide for locals, if such a thing can exist.

There are similar, parallel lands around, and I travel to a sister place to chat to Obi about database keys. These are not like Keys to the City, with a capital K. These keys are more like switches, toggling between pain and pleasure. Calm and despair. I point him at a path and hope it leads home.

Day Two involves B&W and a playground with strange cheese-on-toast, and the Destruction of Weeds. I think about how weeding is actually just a form of curation. Maintenance has the potential to be a gloriously creative process.

Day Three

The early train routine is appreciably different – is it worth an extra few pounds a day to have time to plan out my itinerary more? Perhaps. Another tool to be drawn on when I need it, like sitting in a church to focus focus focus.

I take a deep breath and enter into a strange world this morning, the catacombs of the past. For one reason and another, we’re considering our R&D activities over the past few years. The catacombs contain relics and bones of our reflection, an all-too-real trail of past discretions and victories that, strung together, make it feel like the entirety of my life is now flashing before my eyes. I have to inhale hard, see through the mixture of dust and dots in front of my eyes.

We make it through, and scrape layers of memory from our worn clothes. It was a… slightly weird experience. Neither good nor bad. Disconcerting, perhaps – we’ve been through a lot. I feel awkwardly proud of the journey. Proud of the team that left their relics and their bones.

Exiting the underground vault of the catacombs, I emerge into a dark space which I’ve been away from, but which is all too familiar. The smell of cog grease and electric steam is in the air. Something has gone awry, and the wheels of our data machine are running a little too loosely. A few user support requests have come in, plus there are some internal requests waiting for the great machine to output its value. I roll up my sleeves.

The rest of the afternoon is hazy, lost in a thick fog of database gloop and VM valves.

Day Four

As Flo points out, it feels like the weekend.

The early train provides another opportunity for encounter – I bump into an old Uni friend who is taking time out among the morning commuters, and catch up. We chat about kids and academia and data, and make plans to make plans. I even get time to have a reset of my week’s tasks, to regain some halfway focus. Feels good. Even my inbox feels manageable. Definitely sold on more early starts. (Well, early for me, anyway.)

I’ve cleared my morning to venture back into the Great Machine, armed with weapons and strategies to attack the yesterday with. After stand-up, I assemble our team – Flo is our user liaison, Hon Mond is making sure things don’t grind to a halt, and myself and Obi are donning up our hazmat suits. Some quick SQL provides Flo with a ‘live’ view onto the dashboard, and we use a Google Doc to keep ourselves communicative. In times of fixes, getting your tools set up properly is the first thing you should be doing. Don’t waste time fighting what you don’t have to fight. Your utensils should be an extension of you and of your environment. What you see should make sense.

With that in place, Obi and I work out where the Machine’s weak points – interjection points – are. We devise some plans to get more information and research what we need to. The tourist guide to the Machine is big and often complex or contradictory. It takes most of the morning to dig through it and compare it to what we’re seeing, but we have some ideas to relieve the pressure.

Fortunately or unfortunately, I have a sojourn to the marketing garden after lunch. I leave Hon Mond and Obi with the plans, and excuse myself.

Kim gives us a catch-up on successes and challenges around the garden – it’s amazing to see the work going into it, and I can safely say this is the most amount of thought, effort, planning and attention that this part of the company has ever had. Seeds planted, it’ll be great to watch how this grow over the next quarter.

Some final check-ins with everyone before the day is done. Some code blockers around, but the Great Machine is under control and we’ll discuss more solid improvements Tomorrow. At least we don’t have to deal with fence posts embedded in its guts. Alex has got a solid chunk of functionality for our new extension working, lending the office an air of excited trepidation. Time to leave while things are calm.

Day Five

Reports spread across the region that the fence post has been removed, and we seem to have an infrastructure again, so I’m working from the hills of home today. This is a bit of an outing that I started trying out last week – the non-commute physically is something of a commit spiritually, in that it feels fresh to get away from the office for a while.

In the morning I get time to sit by the pond for a few minutes and clear the edges of my head a bit. This is not a metaphorical pond, at this point. But this moment to reflect, re-target, and remind myself of priorities is fast becoming an essential part of the day.

We have a catch-up with David from HACT this morning as it’s his last day – so after remote stand-up, I meet Stefan in the ether vapour and compare notes, before all three of us we all float around virtually. David has been our closest point of contact for every day work on a lot of our products over the last few years, and it’s safe to say we’ve both learned a hell of a lot about product development in that time. It looks like we’ll be keeping in touch in his new role, and his replacements sound pretty switched on, so it’s an exciting switchover and reshuffle rather than the end of something. Best of luck, David!

I check in to the archive to record my conversations, which seems to be very much part of the OCSI enclave now. I wonder what future virtual corporate archaeologists will make of company transcripts in 100 years’ time.

Then some swanning around town, checking in on venues and events to see how things are going Hon Mond and Obi have made great progress, and next week could be a Big Fat Win if their changes do what they think they’re doing. We should definitely spend more time optimising stuff more. There are some email threads caught in the wind like gossamer, and bits of admin to pick up from under benches and down alleyways. but I leave at 3pm to do the school run, and don’t look back.

Open original in Evernote

Workweek 02×03: “Ew, Hard Copy”

Bit “floaty” this week – I tend to come in on projects when I’m needed, and project herding has recently become a bit more distributed across the team. I seem to have a slight penchant for planning out work, but I’m not so great at hammering it out at the end. There must be tools and frameworks that do this for me. What would I need to do?

  • Set out clear work streams and packages (maybe like Epics?)
  • Decide who’s checking in for each and, importantly, get and keep but-in on status updates
  • Be able to see a clear list of what’s in progress and what’s left (Kanban-type boards have been good for this in the past)
  • Easily see what’s changed – what’s been added unexpectedly, and what’s at risk or been dropped.
  • Have a robot or scrum master to gently prod people to keep things updated.

In writing that up though, I feel like I have a lot of that. So either it’s something else missing, or I’m just really hard on myself (or both). The Tao Te Ching reminds us that we need to preserve our attention towards the end of a journey – 93% of road accidents happen within 5 miles of home. Designate a special ‘clampdown’ phase for a project to stay on target. Have hard timelines. Set aside as much planning time at the end as at the start.


Anyway. Monday we had a quick morning catch up for the week. Loads going on, so I tried resolving my floatiness a bit by checking in with Stefan (Head of Research) about where I might be of help. Decided I could take more charge on project herding (my term) to help lift some of the pressure on him, as he’s delivering a project at the end of the week.

Maybe there’s something there about ‘value’. Maybe I should ask myself things like…

  • Who am I helping?
  • How much am I helping – is this the most effective thing I could do to help?
  • What do they want done by the end of the week?

Spent the morning trying to close off some sprint tasks – there are some fiddly and annoying ones in there this sprint, and I don’t think I was very successful, to be honest. Too many fiddly things going on, too hard to focus, too much decision paralysis. Pick one thing, dammit. Not helped by the fact that I’m out of the office tomorrow. Also not helped by my week planning focusing on other things.

Still, tidied up some code I was looking at on Friday and raised the question of what to do with code maintenance. I do enjoy unit testing, sadly. NO WAIT IT’S NOT SAD IT’S JUST GROWN UP AND AWESOME. Sometimes it’s like tightening up bolts that are a bit loose – sure, it wasn’t technically broken, but now you just feel a lot closer to perfection. OK, a little closer.

A call with our American friends later in the afternoon, and various bits of catchup and preparation with Emma (senior researcher). Trying to untangle all kinds of data thoughts in my head probably isn’t healthy or useful. Wednesday is going to be fun though.

A phone call on my way to the train station, #son1 is being taken to A&E. We’ll see what tonight and tomorrow bring, in that case.



#son1 was fine, it turned out. He just didn’t want to move his arm after falling on it. I’ll teach him about the strain on the NHS one of these days and joked about taking my taxi fare to Eastbourne out of his pocket money. I hope he knew it was a joke anyway.

Random background thought as I was probably wandering around the garden centre with #son2. Should we stop thinking of [Incense Chapter] as a product and think of it as a tool instead? Function wise and applicability wise, what does this change? A tool for what? For engaging with communities? For users? For us?



I’m now writing this on the Monday after, which makes me think about: a) Why didn’t I add notes on the day? Ah, because I was frantic. b) How good my memory is, or rather, how much writing week notes helps me to refresh and refine my memory. c) How determined I am to write up my week notes.

Monday’s phone call had stressed me out a little – nothing major, but I wanted to make sure I hit Wednesday running and really tick off my target. I’d planned to come in early to talk to P- about some potential work, but Stefan is doing a great job on picking up new projects at the moment, and didn’t need me. So I spent a wee while sorting through emails and clearing the decks, then grabbing a coffee, booting the monitor out the way, and getting down to some serious database design.

Realised I can sort of do a lot of (common) database design in my sleep these days, which is useful as a parent. It’s handy to have some skills to draw on under some pressure – I kept thinking back to the films Hackers and Swordfish for some reason, as I pored over bad PDF print-outs of undocumented, un-relationed database schema, and tried to assemble some meaningful structure from it.

All in all, I fired off a draft spec for discussion with the client at 5 minutes to 2pm, which was handy as I’d planned to leave at 2pm to pick up #son1. However, the amazing missus stepped in and managed to get out of her meeting on time, so I got to have some lunch instead.

After lunch there was a New(wish) Meeting of Minds, where Stefan (Product Owner hat), Flo (User Support), Alex (Apprentice Scrum master) and I (also with PO hat on) got together to think through the issues for discussion in our sprint meeting the next day.

We used to involve the scrum master a bit more for these “pre-meets”, as a sanity check on status of issues and priorities, but stopped over time. Then we started bringing in user support and other stakeholders. I think this was the first time we had both, so I was glad to be able to make it.

The meeting went well – it helped us settle priorities and contexts. In retrospect, it also meant it was a lot easier to run the meeting with Stefan absent, so +1 for preparedness! Feels like we’re learning some good stuff about context still.

In fact, I think we even then came out of the meeting, and did the World’s Fastest Roadmap Plan [tm] as we have so much known work on. Instead of the usual month-by-month post-its grid, we went with a very quick-fly “NOW”, “NEXT”, “FUTURE” axis (no gridlines, this is important) and put up post-its for each project. It took us 5 minutes, but gives us a structure for the next 3 months at least. I can’t work out if we’re good at generating ideas, or slow at implementing them. it worked though.

Bonus midweek link for making it this far: Warren Ellis on blogging for yourself:


Thursday was a bit of a weird day because the trains were playing silly-buggers thanks to an ASLEF overtime ban, which meant a revised time table and all my routine being way out of whack. Looks like I’m getting the earlier, more expensive train more while it’s all playing out. but aiming to leave a bit earlier, so interesting opportunities there. More next week.

The morning was sprint-meeting, which is when we find out if a) our planning 2 weeks ago was any cop, and b) whether our planning the day before was any cop.

Stefan was taken up on some urgent work for the [English Hermit] delivery he’s heads down on, so I hopefully did a decent job of stepping in and explaining. We’d done a fair bit of work over the last 2 weeks on working out options and possibilities for various projects, so there was a fair bit of continuation which made my role a bit easier. All ran to time, hooray.

I’d also planned to take Thursday afternoon off to pick up #son1 (it’s academia busy time) but again didn’t need to, so had some more time in the afternoon. Caught up with Kim (Marketing) about some admin stuff, and then had a look into some HTTPS related updates, which I’d pushed for and was very pleased, with my cypherpunk head on, to get out there.


On Friday I opted to try working from home for the morning – getting more time to do admin and catch up on emails is a Thing I’ve identified before as a Thing I’d like to clear some space for.

Fortunately/unfortunately, the first email I replied to made me realise an error with the HTTPS update I’d made, so spent a few minutes fixing that. Boo, error! Yay, encryption!

Replied to lots of emails. The email stats are looking pretty good.

Then jumped on a later train, and got in to the office about midday. Totally forgot about a call with T- from N- about charities and the data ecosystem, but gave her a late call back, and had an absolutely lovely chat – being able to chat about the broader picture is something I’ve actually really enjoyed as I’ve picked up more public-facing streams. And it was great to chat to someone else who was really passionate about making things better, and pushing the data agenda. Hopefully we’ll get to work together in future, and might even be able to get a blog post out of some of the thoughts one day.

In the afternoon we had a few support issues coming in, which I looked at with Hon Mond (Developer). This highlighted a secondary issue with the changes I’d made – can you tell I’m less involved in dev work these days? Anyway, sat down with Lawrence (Developer) to support me, and did some rather handy scp’ing, vimming, and even some sedding to put a nifty fix in place.

BOOM. Went to the pub.


Workweek 02×02: Streets like a sauna

Workweek 02×02: Streets like a sauna
This week the notes are a bit more succinct, with some heavier reflection up top. I like the notion that week notes are a great chance to pick out the threads which have either shone brightly or required more focus this week. Plus shorter notes make continuation more likely.

Things On My Mind

1. Support for R&D has come up as a Thing, which is fine. But it gets me asking two questions – are we “innovative”, and should we be “innovative”? They’re sort of the same question really (perhaps “what is innovation?”) but in the context of what constitutes “Research & Development”, there’s an assumption that our work is somehow new (never done before, anywhere in the world) and then marketable and “successful”.

One of the random memories I take forward from previous jobs was feedback to a sales pitch that the company had put in. “One can be too clever” it went, or along those lines. I think of that a lot when talking to many techies and people keen on having ideas. Ideas are cheap, but implementing them is expensive – not just the cash to put the sustainable market in place, but the cognitive and cultural shift required by users and clients, to shift to that way of thinking. “Obvious” solutions are often the worst, because they’re both subjective and contextless. Too clever.

So should we be innovative and clever? Or should we be focusing on simple stuff – simple product design, simple communication, simple ideas, simple solutions? So far, everything I’ve seen points to the latter being much more useful to people, especially in overly complex, bureaucratic organisations.

But where’s the innovation in that?

2. What do agile and UX look like in a networked organisation, eh? By that, I mean we work with various clients and partners, and how work (sprints, rapid feedback, etc) often requires a bit of explanation, and some time to get used to.

Is buy-in for the processes and the reasons behind them as important as actually demonstrating the value you’re offering? And how can you make that causal link clearer, between how you do something, and why you’re good at something?

3. What’s the strategy for our codebase? Agility is becoming key. Unit tests first, as a safety net for changes – the enemy is complexity. Then what? “Simplify, then add lightness” as says Lotus’ founder Colin Chapman. This feels like something I want to aim for, but how?

Oh yeah – we’re hiring!


Hot, too hot. Monday morning sit-down to see what’s going on across the team. Phone call with Kim and David on sales stuff for [Mirror Street]. Then up to London to see a man about data visualisation – some interesting conversations kicking off some ideas this week, and most of them involve setting up some kind of community scene; something about that is in my blood? But the trains, oh the trains. 3 hours of air conditioning though, so can’t complain too much.


In for a change, swapped days, kept thinking it was Wednesday. Can’t remember what I did, other than it was hot – probably a bit of dev work.

Had to head off early: incident between toddler and trampoline.


Tired after driving to A&E in Brighton and back in the evening (all ok in the end), but a day of chatting today. Caught up with team members. Chatted to another company about potential for collaboration. Board Meeting in the afternoon, which is always nice. I get to talk to some great people, all told.


Day off. Storm. Playground. Garden.


Bit of a relaxing day, some emails to respond to, some admin, lots of dev time (hooray?). Discussed WordPress integration with Lawrence. Discussed Australian boundaries with Hon Mond. Discussed code reuse with Alex. Fixed up a few more unit tests. In between started putting together a proposal to scrape and supply data.

Open original in Evernote

Workweek 02×01: Accidental Purdah

Weeknotes 02×01: Accidental Purdah
I don’t think there are many readers on this stream (say hello if you are following this though…) but if there were, and if they were particularly eagle-eyed, they’d have noticed episode 01×07 hasn’t appeared yet. It hasn’t. I’m late. I’m sorry.

But from missed expectations we get an escape from routine. In liberation we get an opportunity to alter the course of history. So here’s an experiment to justify rinsing my mental hands of last week’s weeknotes. You’ll notice that this is a whole new chapter, that we’re on 02×01, not 01×08.

Theory one: Writing up weeknotes is hard – so hard that one day I’ll fail, give up, move on, step out. My own expectations are too high. Busy weeks are the hardest, but more interesting. Habit is easy to kick once the novelty wears off.

In this case, marking the failure will reveal a downward trend. If I start a new “season” each time I fail, then consecutive seasons will get shorter and shorter. 02×01 is the beginning of the end.

Theory two: Failure is part of routine, and accepting it offers a moment of respite, during which we can learn. 6 weeks of consecutive weeknotes is actually pretty good. God rested on the Sabbath. Downtime. Recoup. Regather. Reorient. Old British TV series were all 6 episodes long.

In this case, I’ve had a pause, and another pause should be due in another 6 weeks. The pause is good, but I don’t know what for yet.

So the critical question is: can I make it to 02×06? And, tangentially, what will change this series as it follows on from series 1?

(… and is this something that all weeknoters go through?)

Monday this week was really good. I think this was because I had a few meetings booked in, and then also managed to structure the rest of my time well around this.

Had a good chat on next stages of our Australian project – it’s been a long time happening, and the focus now is to really avoid things dragging on too long, and be clear on what’s needed. Some good, focused discussion is happening on this, and it really feels like the team involved are coordinating well, including the client. Comms – internal an external – really is a massive chunk of successful work. I’m not even sure you can have too much talking any more. Well. You can. But.

Then went through our sprint backlog with Stefan – which has branched out into a slightly longer term view as we’ve only planned up until June properly, and are very much due a refresh on priorities. But got the hang of this now – post-its, big board, channels for projects, and (most importantly) do not be afraid of forcing a priority. This is the hardest thing when you’re balancing multiple projects each with their own pressures. If relative priorities aren’t clear (ie you’re fudging your immediate timeline, and other symbols), then you either need to stay in the room until the post-its have an order, or get in more stakeholders (or people representing them). Hmm, should blog that separately…

In the afternoon, caught up with Kim on what happened with our Neighbourhood Planning project, and what’s left over after our MVP push last week. Concentrated on what questions we need to ask other stakeholders, ie what feedback we would find useful next. Found it very helpful to start putting together a structure to collate answers into – not necessarily a framework for us to fill in, but a good one to setup the knowledge domain, and where gaps in answers might occur.

Then had a chat with some people about data, that I can’t talk about. And then caught up on emails. Went down the beach late evening to take some long exposure shots.

On Tuesday I was off. I took some more long exposure photos on Eastbourne beach, and ate fish and chips on Seaford beach. The Sea is essential to thinking.

On Wednesday it was very warm. Monday had felt so productive that I took a deliberate few minutes out in between the train station and the office, to put in blocks of calendar time to actually focus on work. (Got a separate, private calendar for this gubbins.) Added bonus effect: weeknote write-up just got 60% easier…

After the usual stand-up I caught up with one of the devs, and then tidied up on a small technical question for [Hive Pixie] – no code change needed, but did highlight a missing step of deployment from some work 9 months ago. Funny how one line of code can come back and haunt you, in a phantom moth sort of way, fluttering at the edge of the light of your attention. Also, still amazed at how easy looking at the past is. Git and Jira (and just tracking software generally) are mind-blowing tools, really.

Then had Alex’s Annual Review in the afternoon so prepared for it and went out to a nearby cafe to talk about the last and next years of his life, which is really scary and really fun when you stop and think about it. We put a lot of effort into Annual Reviews – 360-degree feedback, enough time to chat things through properly, monthly followups. It’d be really strange to go somewhere that didn’t. It’s also not something I’ve ever been trained in – thinking again about how difficult and undersupported the move to senior dev can be (or senior anything, but particularly devs).

Thursday was sprint turnover day (already?). Sprint 101 – “the Office” – wrapped up well. The upcoming stories and tasks feel a bit scattered at the moment, like there are a lot of unknowns floated about. How can you model and measure this uncertainty? What are the ‘danger’ symbols for lack of clarity? Can you automate that, or even make it a simple manual task? One to come back to.

Was forced into clearing out some browser tabs at lunch as my computer was crawling – then realised it says another app causing it, ho hum. Still, good to clear out. Gone are the days of your browser crashing and wiping out all your “to read” tabs.

In the afternoon, something a little different – met with Kim, Flo and Stefan to talk about how we could improve our use of metrics in our products. Only an introductory session and I suspect we were all a bit too warm to think properly, but very good direction and discussion, and really been put off for too long… Will be interesting to see what comes out of it next.

Friday, a fairly quiet and slow day. Spent some time catching up on emails, which is something I’m trying to get better at. After years of trying, I still don’t know if the only real improvement is to do more of it (sit down, check email, respond, move on, repeat until dead) or whether Better = Different. I’ve tweaked my folders and labels over the years, but always stayed away from things like Google’s Priority Inbox, and other innovations. I wish there were better ways to manipulate emails. Maybe filters and actions are a missed opportunity here?

Then a bit of a frustrating day at the dev coalface. Picked up a ticket with a tricky bit of code, but couldn’t reproduce the bug so couldn’t get very far. Then spent the afternoon trying to tidy up our unit tests – I have a personal project to improve our automation and continuous use here, and fixing the fails is the first, key step. Tidied up some (mmm, satisfying) but getting some well weird behaviour with others (grrr). Maybe a lunchtime project next week…

Ok, another week, back on track. Off at Legoland [tm] this weekend, so I’ll either be ecstatic or dead on Monday…
Open original in Evernote