𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗶𝘀 𝗲𝗮𝘀𝘆. 𝗣𝗲𝗼𝗽𝗹𝗲 𝗮𝗿𝗲 𝗵𝗮𝗿𝗱.

In my experience, organizations often inadvertently flip the '10/90 Rule' — spending 90% of the budget on licenses and leaving only 10% for the people who must use them. Then we wonder why adoption fails.

𝗧𝗵𝗲 𝗦𝗰𝗵𝗼𝗹𝗮𝗿 𝗩𝗶𝗲𝘄 There is a concept in academic literature called the "Socio-Technical Gap." It’s the distance between what the system can do and what the organization knows how to do.

My dissertation research showed that this gap is where BI projects go to die. You can build the perfect dashboard, but if it contradicts the political or cultural habits of the department, it will remain unused.

𝗧𝗵𝗲 𝗣𝗿𝗮𝗰𝘁𝗶𝘁𝗶𝗼𝗻𝗲𝗿 𝗩𝗶𝗲𝘄 In my recent role, the biggest challenge wasn't technical debt. It was cultural inertia. This could not be solved with Python scripts. This has to be solved through "Data Literacy Rounds" — sitting with SMEs and consumers to understand their workflows, not just our data flow.

𝗧𝗵𝗲 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆 A CDO's job isn't just to manage data. It is to manage the anxiety that change creates.

Originally published on LinkedIn

https://www.linkedin.com/posts/malikalamin_changemanagement-dataculture-leadership-activity-7419411058139803649-rA1k?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAGjt7sBL8uj9adPfrG1EfHYraXT1G5wf0s

Previous
Previous

𝗧𝗵𝗲 𝟲 𝗖𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗙𝗮𝗰𝘁𝗼𝗿𝘀 𝗳𝗼𝗿 𝗖𝗹𝗼𝘂𝗱 𝗕𝗜 (𝗠𝘆 𝗕𝗹𝘂𝗲𝗽𝗿𝗶𝗻𝘁).

Next
Next

𝗧𝗵𝗲 𝗠𝗶𝗹𝗹𝗶𝗼𝗻 𝗗𝗼𝗹𝗹𝗮𝗿 𝗠𝗶𝘀𝘁𝗮𝗸𝗲: 𝗧𝗿𝗲𝗮𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝗖𝗹𝗼𝘂𝗱 𝗹𝗶𝗸𝗲 𝗮 𝗗𝗮𝘁𝗮𝗰𝗲𝗻𝘁𝗲𝗿.