Difference between revisions of "Managing the consultation process"
From E-Consultation Guide
m |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This is not a communication activity, but every consultation has to be managed, and some IT can help. | This is not a communication activity, but every consultation has to be managed, and some IT can help. | ||
| + | <graphviz>digraph manageclass { | ||
| + | size = "8, 8"; | ||
| + | rankdir = "TB"; | ||
| + | node [fontsize = "12", fontname = "Arial"]; | ||
| + | edge [fontsize = "9"]; | ||
| + | overlap = "scale"; | ||
| + | |||
| + | contacts [label="Managing contacts"]; | ||
| + | caqdas [label="Qualitative analysis\n(CAQDAS) packages", shape="box"]; | ||
| + | caqdaseg [label="Nudist, Transana\n(video), PC Pack,...", shape="none"]; | ||
| + | crm [label="Citizen\nRelationship\nManagement", shape="box"]; | ||
| + | crmeg [label="customized SugarCRM,\npublic sector CRM,...", shape="none"]; | ||
| + | data [label="Type of data?", shape="diamond"]; | ||
| + | grouping [label="Individual\nor group?", shape="diamond"]; | ||
| + | manage [label="Managing the\nconsultation process"]; | ||
| + | newsletter [label="Newsletters", shape="box"]; | ||
| + | newslettereg [label="PHP List,\n...", shape="none"]; | ||
| + | responses [label="Analyzing responses"]; | ||
| + | stats [label="Statistics\npackages", shape="box"]; | ||
| + | statseg [label="survey tool reports,\nSPSS,...", shape="none"]; | ||
| + | writing [label="Collaborative\nwriting", style="filled", color="lightgrey"]; | ||
| + | |||
| + | manage -> contacts -> grouping; | ||
| + | grouping -> crm [label="1:1"]; | ||
| + | crm -> crmeg; | ||
| + | grouping -> newsletter [label="1:M"]; | ||
| + | newsletter -> newslettereg; | ||
| + | manage -> responses -> data; | ||
| + | data -> caqdas [label="qualitative"]; | ||
| + | data -> stats [label="quantitative"]; | ||
| + | caqdas -> caqdaseg; | ||
| + | stats -> statseg; | ||
| + | manage -> writing; | ||
| + | }</graphviz> | ||
==[[Managing contacts]]== | ==[[Managing contacts]]== | ||
| − | |||
Any consultation involving a large number of participants needs some way of managing all the contacts with them. First they need to know about the consultation, then brought in, kept informed and engaged during the process, and given feedback at the end. There is software for Customer Relationship Management, but most of it is designed for sales, not for the relationships in public consultation. There are also tools for keeping in touch with groups of people (by e-mail lists, text messages, ...). | Any consultation involving a large number of participants needs some way of managing all the contacts with them. First they need to know about the consultation, then brought in, kept informed and engaged during the process, and given feedback at the end. There is software for Customer Relationship Management, but most of it is designed for sales, not for the relationships in public consultation. There are also tools for keeping in touch with groups of people (by e-mail lists, text messages, ...). | ||
| − | |||
==[[Analysing responses]]== | ==[[Analysing responses]]== | ||
| − | |||
Policy makers will not read everything produced in a consultation. They needs summaries and analses of responses. Tools for analysing quantitative data (e.g. from surveys) are well-known. But there is also software that can be used to analyse qualitative data (e.g. from focus groups and discussion forums). CAQDAS is well-known to academic researchers, but less so among consultation practitioners. | Policy makers will not read everything produced in a consultation. They needs summaries and analses of responses. Tools for analysing quantitative data (e.g. from surveys) are well-known. But there is also software that can be used to analyse qualitative data (e.g. from focus groups and discussion forums). CAQDAS is well-known to academic researchers, but less so among consultation practitioners. | ||
| − | |||
==[[Writing documents]]== | ==[[Writing documents]]== | ||
| − | |||
The same software that helps groups of consultees put together submissions can be used by a group of consultation analysts when preparing their reports. | The same software that helps groups of consultees put together submissions can be used by a group of consultation analysts when preparing their reports. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 00:19, 7 December 2006
This is not a communication activity, but every consultation has to be managed, and some IT can help.
Managing contacts
Any consultation involving a large number of participants needs some way of managing all the contacts with them. First they need to know about the consultation, then brought in, kept informed and engaged during the process, and given feedback at the end. There is software for Customer Relationship Management, but most of it is designed for sales, not for the relationships in public consultation. There are also tools for keeping in touch with groups of people (by e-mail lists, text messages, ...).
Analysing responses
Policy makers will not read everything produced in a consultation. They needs summaries and analses of responses. Tools for analysing quantitative data (e.g. from surveys) are well-known. But there is also software that can be used to analyse qualitative data (e.g. from focus groups and discussion forums). CAQDAS is well-known to academic researchers, but less so among consultation practitioners.
Writing documents
The same software that helps groups of consultees put together submissions can be used by a group of consultation analysts when preparing their reports.
