If you think you're building some sort of generic 'toolkit' and using that as an excuse not to check in with the folks who will need to get value out of it, you've failed.

The only places where I've heard this (and I've heard this from plenty of senior engineers over the years) are places where the software is RIDDLED with bugs.

As far as I'm concerned, 'COP' stands for 'cop-out'. Just bin it because it's part of the problem not the cure. #COP28

Massively important point. We often think of "failure demand" as just bugs, issues and support incidents. But demand due to lack of product-market-fit – especially in B2B – is easy to misinterpret as a positive thing. It's why we need to know our strategy and value drivers.

Do things that don't scale in order to learn how to scale. Please don't get things the wrong way round, it'll ALWAYS end in tears.

OK, so I went and did it. For the first time since 1998 I am employed by someone other than myself. Happy to announce that as of today I am Chief Product Office RevLifter. 💪 Wish me luck 🙏

This might feel counter intuitive to many folks but I'm going to say it anyway. Take a breath, think about it, go SLOWER. 🫁🧠🐌 Instead of: running in the wrong direction, causing panic / chaos, doing things too soon or in the wrong order, circumventing quality steps.

This is important if there's some production issue in our code. Don't do panic theater. Take a moment to decide who is going to look at which logs, check recent code changes, check expired certs, check DNS, reproduce the problem, etc.

The Labour Party should be ‘less tribal’, according to Keir Starmer after Elphicke defection. What he really means is the Labour party should accept being more mean spirited, more rightwing and more nasty than it's ever been.