So that writing these posts up would be less of a chore, I've started keeping a Zettelkasten document every week to make notes about what's happening every day. (I started using the Zettelkasten module for Sublime Text back in 2018 and I've been intermittent about my commitment to it and let me tell you, it's a mess of book reviews and notes for blog posts and various medical diaries and dream logs, you really don't want to know, but I still like it).
I've also been thinking about how information flows around a small-ish team, because ours had to pull together a monthly report and a quarterly review meeting, a process which seemed to take more of my week than it ought to, and we're also aware that our old team's website is not as up-to-date as it should be. And without wanting to build a CMS or anything, it should be possible to have some sort of system where people put notes about stuff they've done into an inbox, and then it be someone's weekly job to go through those and work some of them into outward-facing blog posts, others to internal reporting documents, and some to both.
I don't have time to do this, and nor do any of the rest of us.
I took the solution design or proto-design I was working on last week to the committee to socialise it, as we say, and the people who objected to parts of it were the people I expected to object to parts of it. But there was also some constructive feedback, and I can see a couple of ways forward to a solution which keeps the enterprise-minded people happy without pulling the rug out from under the functionality the current users have.
Thanks to reaching out to a contact at the ARDC, I'm now hooked into the planning process for ResBaz 2021, an annual unconference for researcher skills sharing and development which we'll be involved in towards the end of the year.
This morning I spent a couple of hours in a workshop demonstrating how to spin up an Oni on a laptop to index a moderately-size cultural collection about criminal convictions in 19th-century Victoria which worked better than I expected, and got some good ideas bounced around about how to handle geolocations.