What do policy analysts in government do (besides the cheeky definition above offered by Arnold Meltsner [1976: vii])? And more to the point, what do practicing policy analysts think they do, and what do they think they should be doing?
In my recent dissertation research, I came at this question by asking practicing policy analysts (in a web survey and separate interviews) to rank-order five policy analysts archetypes - connector, entrepreneur, listener, synthesizer, technician. These archetypes, and their descriptions, were derived from earlier work by Durning and Osuna (1994), Meltsner (1976) and Morçöl (2001).
The ‘synthesizer’ archetype was ranked consistently high as describing the role and orientation of policy analysts, followed closely by ‘connector’ and ‘entrepreneur’, with ‘listener’ and ‘technician’ rounding out the rankings. For more information on that research and to see the results, a working paper is available.
"All Our Ideas" takes a hybrid approach to gauging attitudes and opinions that combines the quantifiability of a survey and the openness of interviews. As of February 2012, about 1,500 surveys had been created.
As an experiment in using the "All Our Ideas" approach, and to further look at how policy analyst professionals think about their work, an "All Our Ideas" survey has been created. And I think that GovLoop Members are the ideal professional pool to take on this question.
This starts with 18 different terms and definitions that describe what a policy analyst might do (again, derived from the various literatures). Each refresh of the page will present you with two alternative definitions of what a policy analyst does, and you'll be asked to pick one. If you can't decide, that's an option too. And you can also add your own definition.
Thanks for playing. The results from this experiment will be posted here.