Need help going beyond the technology? I research, consult, and write about data access, project management, new media, standards, government transparency, mobile technology, and collaboration. Click or tap my picture for my contact information.
In this paper we define the factors that influence adoption of enterprise social software by organizations and how to interpret them We discuss a set of factors related to people, processes, and technology that impact adoption of collaboration and “web 2 0” applications in the enterprise
We will be emphasizing the “people” and the “processes” factors We also discuss further a “self assessment framework” to help managers plan successful collaboration software initiatives
Our proposed framework groups factors in two categories:
Enterprise level factors that go across the enterprise; these drive overall acceptance and adoption
Process level factors that are more directly related to the particular department, function, or business process that is being addressed.
We’ll be describing how to interpret these factors under the assumption that they are being used in a self assessment by potential enterprise social software users as part of an organization’s overall collaboration planning process
Go here to download a .pdf version of this paper.
Dennis D. McDonald Ph.D. is an independent project management consultant based in Alexandria, Virginia. He has worked throughout the U.S. and in Europe, Egypt, and China. His clients for project planning and project management have included the U.S. Department of Veterans Affairs, the Environmental Protection Agency, the World Bank, AIG, ASHP, and the National Library of Medicine. In addition to consulting company ownership and management his experience includes database publishing and data transformation, integration of large systems, corporate technology strategy, social media adoption, statistical research, and IT cost analysis. His web site is located at www.ddmcd.com and his email address is email@example.com. On Twitter he is @ddmcd.
We’ve always known that you need to engage with target market segments where they live and communicate. It’s also useful to consider, if you’re a project manager, your project’s engagement strategy including how your project’s staff members and stakeholders communicate.
If the “geeks” on your team understand all this that’s great. If not, you need to seek out and involve other areas of expertise, starting with people who understand what enhanced data services can do for your target users and the problems you are trying to solve.
James Kendrick really nails one of the biggest problems with Windows 8 in The disconnect with Windows 8.1: Hiding the Utility. His summary:
My friend Bob Davis, interviewed by Mark Amtower recently on Federal News Radio, talked about the challenges facing small and medium-size government contractors.
The basic ideas behind the DATA Act’s focus on financial data standardization makes such eminently good sense that efforts to weaken such standardization should be carefully and openly assessed. Fundamentally, data standardization if managed well can reduce costs, improve data manageability, reduce errors, and improve communication. Implementing data standards can also improve how date transparency efforts are supported as long as the people who operate the underlying systems want to be more transparent.
Given the likely impact of the coming U.S. DATA Act on access to federal spending data, and continued development of federal “open data” programs, I wanted to “pick the brain” of someone for whom data and metadata standardization is a “meat and potatoes” business.