I have a couple of issues to discuss with supervisors:
1. ways of analysing and interpreting
2. anonymity of design
Tomorrow the draft dissertation must be in. The new chapters are:
Chapter 4 - data collection and analysis
Chapter 5 - interpreting the data
Chapter 6 - findings
I have chapter 4 and some attempt at chapter 5, but would like to add more to it. I've structured it round answering the research questions, but am also thinking of an alternative structure that works round the concepts of power, autonomy and collectivity that came out of the analysis.
That is something to discuss with my supervisors.
The second issue to discuss is the one of anonymity. I now realise that having just one case study, and a small case study, although I can anonymise the source, because I'm looking at relationships, the participants can recognise each other. That makes it difficult to use all the data. For instance, if one participant, as a consequence of his or her relationship, perceives something that might be a critique from the perspective of another participant, then, there could be repercussions in the organisation if they read what I write. So I have limited my publishable data. Interesting, and something that I just hadn't worked out before the research, or hadn't worked out far enough. That was partly lack of experience, partly lack of forethought, but also I couldn't have told how many participants I was going have until I found the project. Obviously, there would be only one CEO, but I might have expected more directors, and more managers and more assistants, in which case there would have been anonymity in numbers.
An alternative design would be to have had a number of cases either within this organisation or in more than one organisation. The unit of analysis would still be the project and the relationships in it.
Showing posts with label design principles. Show all posts
Showing posts with label design principles. Show all posts
Tuesday, July 31, 2007
Tuesday, May 01, 2007
Designing accountability
Power states [1] "Accountability and account giving are part of what it is to be a rational individual” (page 1). In order to audit, there must be:
Is accountability in the public services sufficiently complex that the principals are hardly known personally. So who verifies? Which principal can verify the action of the management agent in a public service? In the EDS case, it must have been vertical accountability from lower management up to Sir Nick Montague but was he so distant that audit would have been required? And would it have helped?
Power goes on (p123) to ask:
"What does accountability mean when it is operationalised by auditing?"
He relates themes of risk, trust, democracy and surveillance.
Page 127 the audit requires trust in experts; it is the dead end of the chain of accountability (Day & Klein: 244 [2]). Power states (p127):
“Audit expresses the promise of accountability and visibility”, which makes me think beyond visibility. Visibility is a design principle along with affordance, structure, consistency and feedback. So what other design principles apply to audit? Do they apply?
Day & Klein conclude (p249) that “accountability must be seen… as a system which is woven into the fabric of political and social life as a whole”
If accountability is a system, then somewhere it will show these design principles, even if they emerge naturally rather than be deliberately man designed.
Look for visibility, affordance, consistency, structure and feedback in systems of accountability.
[1] Power, M., 1997, The audit society: rituals of verification, Oxford
[2] Day, P., Klein, R., 1987, Accountabilities: five public services, Tavistock Publications
- a relationship of accountability
- the relationship must be complex so that the principals are distant from the action and are unable personally to verify them.
Is accountability in the public services sufficiently complex that the principals are hardly known personally. So who verifies? Which principal can verify the action of the management agent in a public service? In the EDS case, it must have been vertical accountability from lower management up to Sir Nick Montague but was he so distant that audit would have been required? And would it have helped?
Power goes on (p123) to ask:
"What does accountability mean when it is operationalised by auditing?"
He relates themes of risk, trust, democracy and surveillance.
Page 127 the audit requires trust in experts; it is the dead end of the chain of accountability (Day & Klein: 244 [2]). Power states (p127):
“Audit expresses the promise of accountability and visibility”, which makes me think beyond visibility. Visibility is a design principle along with affordance, structure, consistency and feedback. So what other design principles apply to audit? Do they apply?
Day & Klein conclude (p249) that “accountability must be seen… as a system which is woven into the fabric of political and social life as a whole”
If accountability is a system, then somewhere it will show these design principles, even if they emerge naturally rather than be deliberately man designed.
Look for visibility, affordance, consistency, structure and feedback in systems of accountability.
[1] Power, M., 1997, The audit society: rituals of verification, Oxford
[2] Day, P., Klein, R., 1987, Accountabilities: five public services, Tavistock Publications
Labels:
accountability,
audit,
design principles,
risks,
system,
trust
Subscribe to:
Posts (Atom)