On speed — I fully agree, but with a nuance.Right now everyone talks about “faster delivery” as if speed alone is the strategy. I’m not going to name organizations, but I keep hearing the same call in townhalls and public speeches: “deliver twice as much, twice as fast.”And teams do. They ship more, they ship faster—yet reality shows something uncomfortable: customers aren’t paying for what was delivered. We produced two tools in the time it previously took to produce one, and revenue still didn’t move. With the current obsession with speed, the market is going to be flooded with features and products no one asked for. The real leverage is not to deliver more or faster—it’s to deliver the right thing. Meaning: - something a customer is ready to pay for, or - an improvement that makes them keep paying for what they already use. Speed matters after clarity.If you know what the customer actually needs, then yes—execute fast.But speed without relevance is just accelerated waste.

@Nauman Mithani thank you! Yes, I like to mix different frameworks and created RADR a while ago, by experimenting with RACI and a few other frameworks to reshape it specifically for decision-making, not role documentation.

let's do the hard skills this time :)

Agreed. This really speeds up the evolution of our profession

Hey Gerard, did you find anything? I don't know much about compliance, so would love to learn more

I like using Miro board for this. I play different games but my favourite is a skill marketplace. At first people choose skills they are good at (experts). Then they receive coins and shop for skills they wish to have. Then we talk about actions on how to get these missing skills. We might also start talking about skills we need for this team/project at first and then see what we already have and what we need to "shop"