Access Keys:
Skip to content (Access Key - 0)

Our Methodology

Be sure to read this page before you contribute a case study!

Cases on this site are understood in terms of four basic components:

Business Challenge

We feel strongly that the use of collaborative technology has to be driven by a business challenge. Accordingly, this area encompasses:

  • What was the business challenge that prompted the use of collaborative technology?
  • How did you first identify a mass collaboration platform as a potential solution?

Approach Taken: Implementation Process & Technical Specifications

  • What was the approach taken? Was it a wiki, a blog, a mashup, etc.?
  • Describe the implementation process of the relevant technology. Who were the major stakeholders that participated?
  • What are the technical specifications? What specific platform did you use? Does the technology allow for platform interoperability among relevant stakeholders?

Results: Metrics & Mission Support

  • What were the results achieved? Results could take the form of money or time saved, engagement of new audiences, or simply better service delivery.
  • How do you measure return-on-investment?
  • Is it an innovative use of Gov 2.0 technology in support of the mission? Was the mission successful due to this support? Does it enhance the delivery of citizen services?

Lessons Learned & External Replication

  • What were the lessons learned from deploying this technology? What were the consequences for the organization? How could it have been improved?
  • What specific actions did you take that you feel were pivotal to the adoption of this solution within your target community?
  • Can the approach and results be replicated at other organizations, or easily expanded within your organization?

To begin adding cases, Login or Register!


Adaptavist Theme Builder (3.1.0-SNAPSHOT) Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.4 Build:#809 Jun 12, 2007)
Free theme builder license