On May 1 — while sacrificing yet another shirt to a hotel iron — I had an epiphany of sorts, which I immediately tweeted:
“Legacy isn’t the big IT problem. Entrenchment is. Entrenched investments, mindsets, skills, business process & information wiring. -me, now”
Shortly afterwards, I followed up with:
“what we have isn’t a technology problem, it’s a thinking problem.”
Based on the huge (positive) response from the community on twitter, I shared that I was inspired to elaborate my tweets to an Entrenchment essay.
So far though, the time for long-form thinking and writing alludes me. [Not to mention good hotel irons].
In the interim, I’ve been tweeting under an #entrenchment hashtag, and more recently, scribbling entrenchment bursts.
Convincing myself these bursts could be considered micro-essays, I’m going to share them on elemental links, under a new entrenchment category.
Someday, they may evolve into a cohesive essay, or daresay something longer. But for now, I’m going micro.
I hope they provoke some re-thinking. Feedback encouraged.
Series starts with On enterprise blueprinting
