6 Myths and misconceptions about data projects
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.
4 perspectives to drive effective data translation
When driving data projects, you will encounter business stakeholder challenges that often go unspoken. This is not always because people hold back but because they don't fully know how to vocalize their constraints.
If they can't directly address their requirement, chances are we can't either. To hear others' speech, we start by asking questions from different perspectives.
Countdown: Book Excerpt Chapter 4
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.
Resistance and Mitigation Strategies
Change management wouldn’t be so hard if it weren’t for…the people. Open issues or objections left unresolved today cost time down the road. Suppose work starts before these concerns are mitigated. Stakeholders might get frustrated or begin to hold back their participation. Work produced might have difficulty getting implemented. Buy-in realizes impact.
Countdown: Book Excerpt Chapter 3
Until an organization is willing to invest in its data capabilities, aligning data resources to answer complex business questions will be like riding a bicycle to chase a Formula One racer and never catching up. Scoping project opportunities well is about building enough trust to eventually scale resources. While a single project manager can accomplish some initiatives, most data projects require multi-disciplinary resources to execute.
Countdown: Book Excerpt Chapter 2
While a fully funded budget that supports data as a service is an integral part of a data transformation’s financial picture, few are fully staffed or funded. Three-quarters of executives confirm their organization now has some form of data strategy (however rudimentary), but a paltry 16% say they have the skills and capabilities necessary to deliver it. Even though the average staffing budget is growing yearly, finding the skills and capabilities to execute data projects is becoming harder and harder.
Countdown: Book Excerpt Chapter 1
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.
The Importance of Scope
In driving data projects, I find people underestimate the impact of scoping projects effectively. Too often, you see technology leads with new platforms or tools looking for a problem to solve, or business leads with a unique one-off request from an executive reporting forum carry over to a data team as a priority requirement, whether it is or not.