230831

End of August and time to review my task tracking experiment. I completed 201 tasks. My three busiest projects had 26, 21 and 17 tasks completed. On my busiest day I did 17 tasks and on my least busy day I did 3. I’m going to reflect on it some more and definitely carry on tracking what I work on.

Most of today was spent on data analysis. It’s a bit complicated as the scoring of each answer has to match with some as-yet vague outcomes, but it’s getting there. I created a heat map, just because it seemed like a good idea at the time, and it looks like it might be the best way to visualise the data. Nice when things turn out like that.

230830

Took multiple attempts to figure out if today was Wednesday or Thursday and whether it was the 29th, 30th or 31st. Not sure what that says about my head.

As the end of the month gets nearer, I’m really looking forward to reviewing my task tracking and whether I’ve achieved what I set out to at the beginning of the month.

Did some slow data analysis on some survey results. What I’m taking from it is that the differences between the survey submissions are more interesting than the similarities.

Took part in a product vision and strategy session. We’re trialling organising work into packages that are small enough to be delivered in a month but still solve whole problems. Hopefully it’ll help us focus on delivering more value.

Sat in the garden, looked up at the moon, drank lemon tea and read more of the unicorn project.

230829

Got a survey up on the website to learn about people donating.

Talked about lots of new work and started organising it for prioritisation.

Chatted about ways of improving value delivery.

Read a bit more of the unicorn project.

Two ways to handle dependencies

The efficient way

Stop work on the thing that is dependent until the dependency is removed. Deliver no value during this time. Learn nothing during this time. Start the work again when the dependency is removed.

This way is efficient as it only does work that will be kept, nothing gets thrown away.

The effective way

Separate the work from thing it is dependent on. Do the work in another way. Deliver value sooner. Learn more. Redo the work when the dependency is removed.

This way is effective as it enables users to get value and the team to learn.