There are 7 content items that the Visionaries/Advocates should provide to the Technician(s) for them to get started on the Mapping Phase of a project.
You COULD leave some of this to the Tech, but you'll rarely find it's the best use of your collective time and strengths. Through the
first 2-3 iterations (at least) of a Social System Mapping project, the Technician Hat wearer will clock in many more hours by far than anyone else. You, as the Visionary, may not see how much time they spend, but trust when we say that it's generally not fair to leave fine-tuning the content to them (even when wearing both hats, I like to separate content development and sumApp set-up into two separate steps).
Plus your true Technician generally just doesn't care enough about word-smithing, or have the understanding of the verbal nuances your network requires to do a job you'll be satisfied with anyway. So just plan to work this stuff out beforehand and give the tech your best shot at each:
These are the most important things to develop in collaboration with your Advocate Group - if the time they have to contribute to the project is minimal, make sure it goes into the following:
- Survey Questions (On this one, be sure to check with the Technician to ensure the field types you use will work best in Kumu)
- Connection Questions (ditto about field types)
- Defining Segments
These you can draft on your own, but be sure to have your pilot testers read through everything and tell you if it's all clear enough, concise enough and helpful.
- The 3 email templates
- The Welcome Text
- The Data-Usage Text
And lastly, you'll need to gather, clean up, and segment the: