As I considered how to promote my new book on driving data projects, I wanted to include myths and misconceptions that reinforce their value. I have experienced many of these in teams I’ve worked on or with. Data projects are not a static set of routines. It's a constantly evolving, open-to-innovation process.

Only 54 percent of organizations fully understand the value of project management, according to PMI's Pulse of the Profession™ report. That might explain, in part, why project success rates are so low: Less than two-thirds meet their original business intents.

We often consider digital technologies like data platforms, AI, and copilot features as tools. But if we're rethinking the future of work and the future of careers and companies, it's helpful to think of these things as augmenting our efforts. For a copilot in particular, it becomes a junior coworker or maybe a more senior co-worker as the AI skills get better.

People who work in data management are particularly dedicated problem solvers. They are committed to the mission in a way that makes them want to make the initiative successful. Most examples featured in the book reflect what happens in a specific type of data project -- a team-based project with stakeholders recruited from across the organization, including outside partnerships.

Book Excerpt: Data has traditionally been managed by a combination of information technology (IT), Operations, and Finance. Over the last ten to fifteen years, the chief data officer (CDO) role has come onto the executive scene. While not yet a universal title, the role of the CDO started by reporting through these functions and is beginning to be considered separate.