To appreciate some of the implications of the recent proposal by the International Committee of Medical Journal Editors (ICMJE) to make consideration of journal article acceptance contingent upon the author’s agreement to share de-identified clinical trial data with other researchers, as reported by NPR, some context is appropriate.
My interests: Project, program, and data management; market research, digital strategy, and program planning; change management; technology adoption; books, movies, & photography. Currently I’m focusing on big data project planning & management.
My contact information is here. A complete index to this web site’s technology related articles is here or use the search engine located here. This site also includes occasional book and movie reviews.
Entries in Collaboration (164)
There’s a lot more to collaboration than just providing a technology platform.
These days, still, when you read about big data or if you attend conferences or webinars you’re much more likely to read about products and tools. You don’t hear as much about “back room” management issues you need to address to make sure all the members of the project team are sharing information and marching in the same direction.
It is also impossible for the project manager to ignore how data management and data governance are handled in the organization as a whole. An individual project cannot be expected to change how the organization manages data overnight. Part of the project planning process must therefore include an assessment of the organization’s ongoing data management and governance practices and how they overlap with the goals of the individual project.
Anyone who practices project management for a living will recognize this list. It’s certainly not unique to big data analytics project. It is however reasonable to ask whether “big data” projects are unique in some way that exacerbates the probability of failure.
It’s good to see the Federal government and private sector working together to create value from data that might not be realized were its use restricted only to specifically funded and legislated programs.
I’ve seen too many instances of “bottom-up” or “middle out” innovation where groups of people got together, grabbed the tools at hand, and started working together without waiting for senior management or central IT to show the way.
We want systems and processes to be more effective and transparent, we want to be able to take advantage of improved standards and technologies when they make sense — but we also need to balance the cost benefits of change in a fiscally austere and change resistant environment.
You do need to avoid adopting standards and processes developed by other organizations without first understanding how and why they were developed. That requires research, communication with the other organization, and thoughtful planning.