Weeknotes #242

What I did this week:

Rescope and replan

Another change. Such is the nature of offering a service that has many dependent and tight-coupled aspects. We re-scoped and re-planned to come up with a version of the product that still meets the user needs but it much simpler to build in the time we have available. Thinking about the changes over the past few weeks has helped me realise that a product being minimal and viable isn’t enough. It also needs to be acceptable. It needs to meet some stakeholder’s expectations to continue to get support. One of the positives of the changes and increased pressure is that it seems to be forcing us to work more closely as a team, especially design and development. It has also helped me see more clearly where we have mis-alignments that need to be resolved.

Agile Project Management

I wrote up some of my thoughts about agile project management not being the project management of agile software development but about how project management can adopt some of the ideas of agile to produce iterative project plans that help to identify gaps in the schedule.

Revising convergence

I’ve been revising the concepts from the New Media and Digital Creativity module I’ve been studying, including the idea of convergence which describes how media used to be in separate forms, for example print on paper and music on radio waves, but through digitisation technologies has converged into a single media of 1’s and 0’s. McMullan talks about how this digitisation creates the ‘proto-affordance’ of computability that fundamentally shapes our culture. There’s no going back.

Writing day notes

I’m still writing a short pre-formatted status post every day as part of an experiment in reflective learning. I think it needs some form of review trigger that makes me look back over the week, or to this time two weeks, etc., to reflect on whether things have improved, are issues persisting, what am I learning, etc.

A few things I thought about this week:

Charities shouldn’t be trying to put themselves out of existence

Do businesses try to put themselves out of existence? Do they ever say, ‘We’ve made enough money now, lets stop.’? Do governments try to put themselves out of existence? Do they look for ways of devolving power to the people? No. Why not? Because both businesses and governments have a place in society. They serve a role larger they just the benefits they seek for themselves.

Charities are the same. I know our assumptions about charities as organisations are closely tied to the cause they are tackling, and that’s why it’s easy to fall into the idea that if the cause didn’t exist then charities wouldn’t need to either, but I say this is false logic. A charity builds up lots of expertise in some fairly unique capabilities and to throw all that away because they we’re so good they achieved their mission would seem to me to be very wasteful and a great loss of all the other benefits charities create for our society, like volunteering and prompting people to make change.

Oblique strategies for alertness

Brian Eno’s oblique strategies, random instructions printed on playing cards, are reputed to have been responsible for some very cool music. Following the instructions forced musicians out of their comfort zone and made them pay attention. They disrupted the complacency of expertise. I’m interested in what the benefits of this kind of thinking might be in digital work, whether it might help us deal with uncertainty better. So many of the tools and techniques we use convince us that they are all we need to have certainty about things, and I’m not convinced that’s a good thing.

What does it mean to be a product-led charity

What might a product-led charity look like? How might it differ from a non-product-led charity, and how would you tell the difference? To be clear, when I talk about ‘product’ in this sense I don’t mean the technology. It’s very likely that a product-led charity would make use of technology in their products but a product is more than the tech. A simple example is Hullo. Their product is the offer of a conversation with a friendly stranger, not the phones they use to have those conversations.

I think it might require a move away from idea of charities providing value as one-way stream (from funders, through the charity, to service users). Being truly product-led might mean recognisjng a mutually reciprocal value exchange along the lines of how service-dominant logic explain it. I’m pretty sure it means repositioning the IT/Technology department to no longer be seen as a support function for fixing your laptop. And I’m certain it’ll bring all kinds of funding challenges where income is usually associated with delivering projects.

Some stuff I read this week

Where do good ideas come from

Chance favours the connected mind.

New product development body of knowledge

All the right answers.

OCVA Digital Needs Survey

I read the results of the OCVA Digital Needs Survey. Apart from the very un-digitalness of embedding a pdf on the webpage, it’s a interesting survey. Some of the responses includes things like how to better meet the needs of people who are digitally excluded, procure digital products, make the most of Microsoft 365 and use video meetings software better. These are all things that large charities seem to struggle with too, so it seems it’s a general lack of digital knowledge across the sector rather than being specific to a certain size of organisation.

A while ago I started a blog post on how small charities can assess and procure digital products so maybe I should finish that, but I also had a quick look around for ideas about how I might be able to help small charities improve their digital skills. I found a charity mentoring organisation but as all of their mentors were white, middle-class and middle-aged it didn’t look like somewhere I would fit in. I wonder how oblivious organisations are to this kind of stuff of if it’s implicitly intentional.

210319

What went well?

Did a bit more work on project planning.

Did some revision for my exam next week.

What didn’t go so well?

Didn’t get my weeknotes written.

What could I do differently in the future?

Stick to schedule better.

210318

What went well?

Made some progress on project planning.

Wrote a blog post about my thoughts on agile project management.

Went out for a dance/walk.

Did some service design course assignment.

What didn’t go so well?

Emotional day.

What could I do differently in the future?

More detachment.

What is agile project management?

If you search online for ‘agile project management’ you get video of people talking about project managing an agile development process. Well duh. I think we can do better than that.

Project management that had agility would be adaptable, accepting of uncertainty and responding to change, would deliver value at the earliest opportunity, and would bring people together to share knowledge and shape the plan.

How might this approach show itself in something like a project plan? Instead of starting with a high fidelity plan that has unknown gaps, maybe the plan would start in low fidelity, defining the big chucks of the project so all those involved get some immediate value from the plan. Maybe the big chunks are things like scope, time, budget, people. And then as more information becomes available the plan is iterated upon to reach a slightly higher degree of fidelity, and again to even higher fidelity, all the time delivering value.

Fidelity increases with each iteration

This kind of approach acknowledges that there are unknowns in the plan and would fuel conversations as people fill the gaps, meaning people have to work together to develop the knowledge. The plan is the output of those conversations but it’s the collaboration that makes the plan a reality.

“I love it when a plan comes together”

Colonel John ‘Hannibal’ Smith

210317

What went well?

Sent a good update on a project.

Set up a password manager.

What didn’t go so well?

Didn’t get any revision done.

What could I do differently in the future?

Really need to prioritise my revision and service design assignment.

210316

What went well?

Adapting to the latest range of scope changes.

Had a good chat with a team member about the changes and appreciating their approach to work.

What didn’t go so well?

Didn’t get any revision done.

What could I do differently in the future?

Get some revision done.

210315

What went well?

Refining the scope of work to better fidelity.

Work with the team of understand how we’ll approach delivering on that scope.

What didn’t go so well?

Worked all evening and didn’t get any revision done.

Didn’t get the answers I need to make a decision about where to focus our efforts.

What could I do differently in the future?

Do it myself?

210314

What went well?

Went for a nice walk and talked about all kinds of things from the role charities play in society to what problem the education system is trying to solve.

Wrote my fourth ‘Things I’ve Read Recently” Twitter thread.

What didn’t go so well?

Didn’t get any revision done.

What could I do differently in the future?

Nothing. Just not enough hours in the day.