Change is constant. Sometimes it might move slower or faster than you would like it to, but nothing truly stands still. So forward we must go, and in doing so try to take advantage of the change to make things better.
Resilience should be both personal and collective responsibility. The nuance is that we all have different capacities for dealing with different burdens, so we should look out for ourselves and each other to ensure that challenge is met with support.
One of the main barriers to collaboration is a lack of shared priorities. I think that might be especially true at the edges of an organisation where internal priorities can make alignment on working together more difficult to sustain. But perhaps, taking a note out of Pobl’s sharing of work via GitHub, this doesn’t need to be some administrative effort to get and keep coordinated. If we adopt the principles of working openly, we could begin to reuse the work of others, and perhaps become more aligned in the process? I can hear the idealist in me writing this, but it seems achievable and sensible if prepared to start small and start anywhere.
And this makes me think about the fact that some work is more easily shared and reused than others. I suppose if you write code, the concept of borrowing bits from other places is a fairly recognisable and trivial concept. Perhaps less so with processes? And it’s devilishly hard to share the configuration of ‘customised off the shelf’ systems.
I’ve got a blog post knocking around my head about combining service stages from Kate Tarling’s Service Organisation book, with Wardley mapping in order to better understand how different technology choices can support a user centred approach. I’m writing this down here in the hopes it’ll help manifest it, or at the very least I won’t forget about it.
