Stormberry on Nostr: The pattern repeats every fifteen years. New technology arrives. Vendors sell it. ...
The pattern repeats every fifteen years. New technology arrives. Vendors sell it. Companies buy it. Two years later the system sits half-used while the team works around it.
ERP in the 1990s. CRM in the 2000s. Cloud in the 2010s. AI now.
Every time, the failure mode is the same: the technology was treated as a procurement decision, not an operating-model decision. Tools were chosen before workflows. Pilots ran in isolation from the actual business. Rollouts stalled when the org chart did not change to match.
What works for AI in 2026, just as it worked for ERP in 1996: pick one workflow that matters, change the operating model around it first, and only then bring in the tooling. Measure adoption, not licence count.
Most of my conversations with SME leaders this year follow the same arc. They have bought tools. They want help making them load-bearing. The bottleneck is rarely the model. It is the workflow it sits inside.
Published at
2026-07-08 10:56:18 UTCEvent JSON
{
"id": "d9ff94db723a96e6aa672f07b52f0be7b03d549468e17c0c9e745977246f429b",
"pubkey": "108aef782a95a65a2df059578e67a71366a65a697e163711b54574e8da0e6e30",
"created_at": 1783508178,
"kind": 1,
"tags": [
[
"t",
"ai"
],
[
"t",
"strategy"
],
[
"t",
"changemanagement"
],
[
"r",
"https://stormberry.as"
]
],
"content": "The pattern repeats every fifteen years. New technology arrives. Vendors sell it. Companies buy it. Two years later the system sits half-used while the team works around it.\n\nERP in the 1990s. CRM in the 2000s. Cloud in the 2010s. AI now.\n\nEvery time, the failure mode is the same: the technology was treated as a procurement decision, not an operating-model decision. Tools were chosen before workflows. Pilots ran in isolation from the actual business. Rollouts stalled when the org chart did not change to match.\n\nWhat works for AI in 2026, just as it worked for ERP in 1996: pick one workflow that matters, change the operating model around it first, and only then bring in the tooling. Measure adoption, not licence count.\n\nMost of my conversations with SME leaders this year follow the same arc. They have bought tools. They want help making them load-bearing. The bottleneck is rarely the model. It is the workflow it sits inside.",
"sig": "15ccd49fa91239d2a53ae1ef6b80633afc6481557f182b37f10d50fe4948c055d536b73ae375c8b141e7c6b1520e968bce8efeb7b80afa0e45dd4dae6b527352"
}