Piloting plan

From Responsible Data Wiki
Revision as of 10:39, 1 October 2014 by 193.225.200.92 (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

What are we talking about? Pilots, or another way to put it, closed-loop iteration. Sometimes "pilots" are where projects go to die.

What is the criteria for needing more iteration?

Find where there is energy - ready to go, want help. Have a contract ("Learning contract") with them: here are the tools, give is input back on how it was used, how it worked, etc. Explain the context and reason for moderation.

"Learning Contract" - teacher and student agrees to commitments - wha tdo they want, objectives, and what will they give back?

Incentive structure - would it make sense to identify support organization and involve them in the process of piloting/testing these resources? These support orgs are invested in the general resource and want to see how it can be customized and used.

Min requirements for the pilot:

Who are the ideal people to pilot with?

What are some of the channels and mechanisms that a group like this could use for this pilot process? For each Buda output, we need description, audience, sign-up list (commitment to pilot). Here are some steps to think about.

Ex: atomized dig sec for orgs - each iteration (phone calls, etc) produces different outcomes, not sure how to bring it all together