Difference between revisions of "Defining the problem"
| Line 20: | Line 20: | ||
issforumeg [label="Minnesota,\nBrighton, ...", shape="none"]; | issforumeg [label="Minnesota,\nBrighton, ...", shape="none"]; | ||
knowledge [label="K acquired?", shape="diamond"]; | knowledge [label="K acquired?", shape="diamond"]; | ||
| − | learning [label=" | + | learning [label="Learning from\nthe public"]; |
measure [label="Measuring needs\nand preferences", style="filled", color="lightgrey"]; | measure [label="Measuring needs\nand preferences", style="filled", color="lightgrey"]; | ||
newsletter [label="Newsletters", shape="box"]; | newsletter [label="Newsletters", shape="box"]; | ||
Revision as of 22:55, 7 December 2006
Exactly what is the problem or issue to be discussed in a consultation? Can all the participants and the organisers come to a mutual agreement on what is involved? If not, they will be talking at cross-purposes, and no one will be satisfied with the outcome.
Telling the public
Often it is necessary to give the participants some information about an issue, or a proposed policy, before starting a consultation (as in a downloadable discussion document, or a web site). This is a form of one-way communications, like most of those seen on http://www.consultationni.gov.uk/ .
Identifying issues, collecting stories
What issues concern participants? What problems should the consulting body be looking at? What can we learn from participants experiences? These are questions often asked at some stage during a consultation (often, but not always, at the beginning). There are technologies to help collect these stories and issues, from e-mail addresses for complaints and compliments to story-telling blogs.
