I think this is *extremely* useful, but frustrating to implement this process. I don't have great feedback on this except to say that I wish this was something we could do (and we could, and have done parts of it with the informatics roadmap), but it's larger than the eCR piece I'm working on and utterly outside the scope of my work. It's upstream to eCR, if that analogy makes sense.
Doesn't mean it's not important, but I think this process might be better suited to an 'informatics roadmap' or 'developing a surveillance system' level of project, not eCR. (But maybe I'm thinking too small for eCR, I'm not sure).
I'd like to (and hope to be!) talked out of that opinion, because it feels shortsighted to me, so I'm really hoping other folks disagree and have been able to implement this for eCR or ELR or similar projects! If you have - who were your stakeholders?
(I added folks who I know are rocking and actively working on eCR -- because I'm hoping y'all will disagree with me. ;-) )
Notified 8 people
Kelley Chester
Thanks Crystal... I hope the group that you added will chime in on this one.
Stakeholder Analysis Guide.pdf
(488 KB)
Doesn't mean it's not important, but I think this process might be better suited to an 'informatics roadmap' or 'developing a surveillance system' level of project, not eCR. (But maybe I'm thinking too small for eCR, I'm not sure).
I'd like to (and hope to be!) talked out of that opinion, because it feels shortsighted to me, so I'm really hoping other folks disagree and have been able to implement this for eCR or ELR or similar projects! If you have - who were your stakeholders?
(I added folks who I know are rocking and actively working on eCR -- because I'm hoping y'all will disagree with me. ;-) )