Actions have consequences

“Actions have consequences.” I say wishing I didn’t have to explain this to an adult (resisting the internal eyeroll). 🫥

“What do you mean – it’s just a field. If we make it mandatory, then people will put rubbish data in.”

“But if you don’t make this key date field mandatory, the required reports will not yield the information you need to make decisions!” 🙈

“Yes – but at least the marketing teams won’t complain about how long it takes them to create the campaigns.”

“Good systems require both well architected and designed systems as well as processes outlined in strong governance models AND #ChangeManagement to embed proper data hygiene and good behaviour.” – boy that’s a mouthful to say! 😬

Sigh.

I get it – we are forever fighting against human nature, which tends towards ‘least resistance’ 🙄

The thing is – very few people are approaching problem in a thoughtful way, with design thinking in mind which helps us build things that are feasible, viable and desirable.

“OMG THERE’S A PROBLEM HERE!! QUICK GET ON IT WITH A FIREHOSE!”

🚒🧯

When we should be asking: “Is that really a fire? Oh. It’s just a beacon that’s been left on. What outcome do we want? How should we fix it so that we get what we want?”

😬 Lizard brain is in charge when it should be our more rational, calm and quiet problem solving pre-frontal cortex. 🧠

What seems like a small and inconsequential decision will compound over time, and I wish I had a time machine that can quickly show the impact of those bad decisions and the sufferingness that comes with trying to tackle it. 😒

Double sigh.

Oh well.

At least this just means that there will always be work for me. 🤷🏻‍♀️

But I’d rather not be fighting fires on technical/operational poo debt mountains though. 😣

#TechnicalDebt

#DesignThinking

#WellArchitected

#OnThePeiroll