Weeknotes 302

This week I did:


I’ve been working on how we might use website analytics to help people think more about data and use it in decision-making. The shift from UA to GA4 has been a good prompt for creating useful dashboards that everyone can see.

What happens when we stop telling stories?

This week’s Irregular Ideas was about how the digitisation of media has changed how we understand and tell stories.

Ambivalent MBA

I’ve been slowly working on an idea for creating my own MBA using Agile Education and Andragogy ideas where I’d build a curriculum of topics I want to learn about, read about each and then complete some kind of assignment or project.

Read this week:

How to talk about agile to non-digital decision makers

A few things to consider when talking about agile to non-digital teams.

Blogging for teams

This cool website about blogging for teams by Giles Turnbull

Idea machines

Tech as a system of values, and not just an industry, is heavily driven by its subcultures and their ideologies. Where do these ideologies come from, and how do they influence what’s accomplished?

And thought about:

Failure is a funny thing

The rhetoric around failure is that it’s a good thing, something to be accepted and learned from. But we all still seem to spend so much time trying to avoid failure. If it’s good, if it’s an effective way to learn, shouldn’t we be expecting and encouraging failure?

Problem levels

It seems every problem has another level of problem beneath it. Choosing the right level to look at the problem from is half way to understanding it. Choosing the right level to intervene at is half way to fixing it.

Going to the source

There’s nothing new under the sun. Every idea has influences, a history and sources. Product managers should know this and go to the source to understand things. If you’re building a learning management system and you don’t understand pedagogy and andragogy then you’ll have to learn all that knowledge, ineffectively, through the product.