What’s the purpose of the
collaboration?
The collaboration is a very efficient
way to measure what key stakeholders know (or
think) about an upcoming implementation project.
The data we collect helps quantify the
“collective wisdom” of the organization about
risk factors and implementation pitfalls in more
than 40 different areas of vulnerability.
Who should take part in the
collaboration?
We recommend the you invite at
least a dozen participants, specifically
including all the project stakeholders--the IT
department, the end-user group, finance, support
and training representatives, and others. We'll
discuss the makeup of the collaboration group with you
in more detail when we start the assessment.
How will you contact the
participants?
We'll create an e-mail
invitation that explains what we’re doing, with
a private URL that provides more details.
Generally, participation is better if the
invitation is sent out over the signature by a
company insider who’s already involved with the
implementation project.
What if some of the
participants don't know much about the project?
Our analysis software lets us easily add and
subtract groups (or individuals) from the statistical
base on a question-by-question basis. In fact, very few
project participants will be able to answer all the
survey questions, and that's fine.
Will
the collaboration capture longer comments?
Yes. Every question has a text
entry area that lets participants expand on
their answers or offer in-depth insights.
How long will the collaboration survey stay
online?
About ten days. After a week
we'll send a reminder notice to anyone who
hasn't responded.
Can we see individual responses?
We strongly recommend that
collaboration survey responses should be anonymous.
What are the factors you look at
in analyzing responses?
First, we look at the average
risk-assessment score for each question, which
gives us a basic measure of the project's
vulnerability in a specific area. Then we look
at the degree of consensus about this
score--that is, do most people agree that a risk
exists, or is there significant disagreement. We
also look at the percentage of people who feel
able to answer each question, because that's a
good indicator of communication and involvement.
And finally we look at how respondents rate the
importance of each question.
In addition, we roll up the
responses from all the questions into
higher-level "risk drivers"--that is, broad
vulnerability factors (such as a general lack of
management support for IT investments or
inadequate end-user involvement in planning).
Can we add our own questions?
Yes, though we try to limit
customization to preserve base-line comparisons. |