Thursday, December 20, 2007

Passed and awarded

They accepted my dissertation. I got it all sewn and bound by Abbey binding, delivered it to the office so the library now has a copy. I received a letter acknowledging it and telling me that I've been awarded the degree in absentia.
:)

Wednesday, October 17, 2007

Moving on

I'm leaving here. I said it was a one-year blog and it is. I'm starting a new blog on the doctoral experience at http://phd-ejh2.blogspot.com/ but I might pop back to post any final news on the results of my dissertation, if there is any.

Tuesday, October 02, 2007

Viva

Viva done yesterday and it went better than the interview for the PhD. This time I did feel like there was a conversation at one time rather than an inquisition, though the director of studies this time realised how nervous I was.

The first question was about how the philosophy influenced the choice of methods and collection - and I can't remember the whole question.

They also wanted to know what I'd have done differently in the light of the last excitement of negotiating access and having the interview data withdrawn on the last day. What had I learned?

We had a discussion about transaction costs and differences in procedural and outcome accountability. Transaction costs is something to investigate further.

And there was a question about the theory that overlapped both accountability and consultancy - I couldn't remember the different types of literature on consultancy nor the words - but they wanted me to talk about agency theory and the model that I used to show the chain of accountability.

I was a bit disappointed to discover that the examiner had a list of corrections to the references. How could I have missed these! And the director wanted me to remove the use of the first person where I'd reflected on methods. Okay.

Incidentally, they congratulated me on my use of diagrams and tables, which they said helped to show the concepts. Just as well as I'm so low on my verbal reasoning skills that I have to use these other skills.

Sunday, September 09, 2007

Constantantly negotiating access

"Finished!"
said I on Friday morning around 11.30. I had written what and how I wanted, and taken all the latest 60-80 comments from my supervisor into account. I'd sorted the print layout. I'd practised binding. All I had to do after lunch was tweak the abstract, print and bind three copies. So I went to lunch.

As I came back from lunch, the secretary handed me some post - a self-addressed envelope - and slightly surprised, I thought,
"Oh, good! Someone has returned me a consent form."
It read:
"I don't want you to use any of the information that I gave you."
Director and supervisor #2 came to my rescue, checking that I had had ethics approval, and everything was anonymous. Then the director helped me to put together a fax to the participant in which I assured her of her anonymity, of her service, of her organisation. Director and supervisor #2 said that my dissertation wouldn't be published but be labelled special confidential.

So it was kind of sorted. But I wasn't happy because I want to be able to publish so, Friday evening I took my draft and a bottle of good wine round to the chap who'd given me access in the first place. He was incredibly sympathetic, and practical. He made three suggestions, which I've implemented, and he's sent me an email saying that I can publish!


Hurrah! :) smileys :)

The methods theory that goes with this comes up in a story from Buchanan, Boddy and McCalman about constantly having to negotiate access. They describe similar experiences and one of those 80 comments from my supervisor was to reference them. Good supervisor - aren't I lucky?



[1] Buchanan, D., Boddy, D., McCalman, J. (1988), "Getting in, getting on, getting out, getting back", in Bryman, A. (Eds),Doing Research in Organisations

Friday, September 07, 2007

Final abstract

The aims of this study are to find how public sector authorities account for the use of consultants and how client-consultant relationships affect public accountability.

The media frequently accuse the public sector of profligate expenditure on private consultants. This research examines public accountability for the management of external consultants looking for justification of use. Research literature on consultants refers to client roles, relationships between clients and consultants, and discourses that vary with relationships. Literature on accountability refers to types, chains of relationships, discourses, procedures and outcomes. The study applies agency theory to client roles and relationships to identify problems of different perceptions of accountability between multiple decision makers and stakeholders.

A social constructionist perspective is taken that leads to a qualitative analysis of a single case study of the use of external consultants in a council service review project. Data was collected through semi-structured interviews supported by documentary evidence.

Emerging issues of public accountability include transparency of processes. Different perceptions of accountability revealed unconscious enactment and possible gaps. Findings confirm the literature on accountability and begin to extend research on some types of client-consultant relationships, suggesting public accountabilities in which managers of consultants account proactively and users account reactively. Further research might investigate the institutional pressures that influence accountability and client-consultant relationships.

Sunday, September 02, 2007

Activities that are difficult to do

"Things like 15000 word woffles was what made me chose engineering!"
emailed one of my computing students after we'd compared notes on banging our heads against walls. I didn't mean to do anything that involved so many words, but I did want to study for a doctorate - this gives me the first step, but our director of research says it's the hardest thing I'll ever do.

It is difficult to do because abstract and creative. I have to identify the (invisible) gaps in the literature and research on my topic, generate new approaches / ideas / methods to fill in those gaps and explain it logically and coherently to those already well experienced in the field.

See M256 Unit 12 2.2. Table 1 for difficult-to-do activities.

Saturday, September 01, 2007

Rewrite

My overworked #1 supervisor keeps me on my toes. At half past five yesterday evening, he emailed me to warn me that I have more work to do yet. I think it's the coherence between sections that I need. He says:
  1. check I've answered the research questions
  2. check I used concepts from the literature in the analysis
I may have done so, but it's not very clear or explicit.

And in the conclusions, I have to explicitly link back to the research questions and literature to say how the research sheds new light on them. And there I was thinking I'd done this, but evidently not clearly enough for my reader.

Thursday, August 30, 2007

Dissertation nearly there

I've been checking my work against the marking scheme. I reckon it passes, but I can't tell the quality of the pass; I don't think it's a distinction. How can you assess yourself against clearness? What is clear to me has not been clear to my supervisors. The marking scheme for a band that is 84-70% wants

"clear articulation of research questions that are derived from a critical review of the literature."

I can find problems with that - what's "clear"? What's "critical"? and have my questions come from the literature? Do I show that they have, or do they seem to come from the top of my head!

Friday, August 17, 2007

Restructuring

I've reordered material from the draft dissertation so that the analysis covers roles and application of agency theory to the data. That takes out loads of material from the chapter that has to be called interpretation. What's the difference between analysis and interpretation?

I think the analysis bits are where I've applied ideas from Miles and Huberman, used codes, rich picture (Checkland) and drawn up a role-ordered matrix.

That's quite helpful because it shows where the roles match Schein's concepts of client types. Then I put that analysis on to my agency theory diagram so I can see the chain of links, and back stitch links between various accountors.

The interpretation bit needs a bit more thought. I've linked it from the analysis by occasionally picking up ideas in the analysis and suggesting they are new to this case. For example, the analysis identified incidents of accountability despite that participant saying he/she couldn't think of one or didn't understand the question, so I thought that was unconscious acting of accountability and something to follow up in the interpretation.

Funny how writing helps you think. It seemed to me that that unconscious acting was a reaction to a situation, so the participant demonstrated reactive accountability, and that meant I realised that the other planned accountability was proactive. And that leads me to my last, not yet properly written chapter on findings.

Wednesday, August 15, 2007

Relooking at the literature

I've gone back over the literature review chapter- it's quite depressing because now I think I don't really have incisive research questions, and am not clear how I get any questions from the review at all. If I haven't set a question, then what is my research answering.

I've rewritten the section on accountability again. And again. My supervisors want a definition, but I'm not sure that a definition is good enough, because that makes it sound like you can get a grip on accountability but it's too nebulous to grip.

I've talked about Sinclair's discourses of accountability, and Bovens analysis of accountability in the public sector and Siegel-Jacobs and Yates research comparing outcome and procedural accountability seems important. Agency theory matters and I've drawn diagrams to show how I'm applying it to multiple accountors and accountees.





And that moves me on nicely to discussing consultants, clients and relationships.



Bovens, M. 2005 Public Accountability in The Oxford Handbook of Public Management, draft, L. Lynne C., Pollitt (eds.), Oxford, Oxford University Press
Siegel-Jacobs, K and Yates, J.F., (1996). "Effects of Procedural and Outcome Accountability on Judgment Quality" Organizational behavior and human decision processes 65 (1): 1–17.
Sinclair, A., 1995, The Chameleon of Accountability: forms and discourses, Accounting, Organizations and society 20(2/3.): 219-237

Tuesday, August 14, 2007

What do you do when..?

Suppose the consultant advises something, and it's bad advice. Who's responsible? The consultant for giving bad advice? Well, he won't get more work from that company. But it's not a company, it's a public service and it's public money that's been spent to get that bad advice. So why did someone in the service get bad advice? Through bad management. There are ways of preventing the situation arising:
  • Write a brief,
  • Get the contract right.
  • Require progress reports
  • Withhold payment.

Look at briefs. This is what the consultant said:
“Because you need to be very clear what does the client want actually get out of this, because you’ll never be able to give them the right recommendations if you have a misunderstanding or a misinterpretation of what their goals are.”
Get the contract right. Look at contracts:
"So there are contractual agreements between the council and the consultancy and there are certain agreed outputs."
Progress reports warn the managers before it goes wrong.

And if it still goes wrong, look at withholding payment:
“I can think of one, where one of our IT contracts to implement an upgrade to a social services system where the consultants failed to deliver what we wanted, and we got into a contractual negotiation where we withheld a considerable sum of payment.”
If the project gets to the stage where there’s a contractual negotiation and withholding of money, then the process has gone a long way down the wrong road. But who is ultimately responsible?
Some say one thing:
“The person that decides that they should be brought in and sets the brief”
Others look at something wider:
“I think the county needs to be more transparent to its council taxpayers, in terms of the use that is made of consultants.”
Some say the public elected leader of the council.

So it looks as if there is some sort of process to prevent and to deal with bad consultancy advice, and for the lines of public accountability that must answer for that poor advice.

Monday, August 13, 2007

The story

The case study story is about a small project in an English county council where consultants were brought in to develop an approach to a county council service.

For those who don't know, county councils are run by the public servants and the elected members or councils represent the electorate. County councils provide services such as


  • education including schools and art galleries,

  • care services such as adoption, social services and may be care homes,

  • development services such as waste disposal,

  • community services such as parks or libraries,

  • resources such as estate management, encampments, transport and roads.

The basic brief was to consider the future of the service but was driven by budget problems.

The consultants visited all the branches of the service, listened to the service assistants and then produced an internal report. The operations managers incorporated the consultants’ advice into a long technical document that became the county council’s report. Some components of the report had repercussions, for instance one component advised closing eight branches, which would save over £200,000.

The elected members took the review to public consultation. People objected to losing the service and they found a totally different approach to the way those branches were run and consequently kept five of them.

The consultants’ recommendations were not totally implemented; the political process changed the outcome.

Thursday, August 09, 2007

Last supervision meeting

Having spent an intense hour discussing my draft dissertation with my supervisors. As always, they've read my ramblings and courteously and logically point out the errors and lacunas of my writings. But this is the last formal submission so is the last time they get to comment on my work and my last chance for advice. I've got six weeks to ruin it by myself. It has to be handed in 10th September. The supervisors don't mark it, but some third party who knows nothing about it.

However, S#1 volunteered to take a look at it when he gets back from holiday, and has even arranged to meet to discuss it, just one week before it is due in. :) S#2 might have time to comment on an electronic copy, but is back from a longer holiday even later than S#1.

I've allowed husband to book us a trip away after submitting the dissertation, but then today they started talking about the viva. Viva! When? Talk to people about it? Oh dear, not another interview. But it's only with two people not a whole board of them and I suppose I might manage.

Wednesday, August 08, 2007

Asymmetry of information

Agency theory talks about asymmetry of information. The principal and agent have different information and different information needs. That's relevant to explaining a perspective of this project. One person saw that it 'petered out' rather than coming to a clear conclusion. At the final stage, operation managers were able to continue to call the consultants for advice, who therefore billed for extra days. If the principal /Operations Manager perceived a need for information & lacked confidence in own ability to carry on and implement the changes, but perceived the consultant / agent had that information, then contact was continued, and the billing.

Keil, Mann and Rai discuss this escalation in their paper on why software projects escalate [1]; I think it is irrelevant whether or not the project is a software one. There seems to be a lot of research on software projects and at least some of it must be transferable to non-software projects. Keil et al's quantitative study found that two constructs associated with agency theory, were associated with projects that could be predicted to escalate. The concepts are:
  • goal incongruency

  • information asymmetry

Goal incongruency is where there is potential conflict between the principal and the agent, such as the agent acting for his own best interests rather than that of the principal.

Information asymmetry is where
"the agent is assumed to have private information to which the principal cannot costlessly gain access." Baiman[2]

Implications for good practice were the importance of good communication and monitoring of projects to avoid information asymmetry. They also suggested management should implement early warning systems to detect escalation.

Good communication is something the participants have mentioned in my case study – they require transparency. A combination of monitoring mechanisms and good communication seem to have made this project successful from the perspective of most of the participants.



[1]Mark Keil; Joan Mann; Arun Rai, Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models, MIS Quarterly, Vol. 24, No. 4. (Dec., 2000), pp. 631-664. http://links.jstor.org/sici?sici=0276-7783%28200012%2924%3A4%3C631%3AWSPEAE%3E2.0.CO%3B2-2
[2]Stanley Baiman, AGENCY RESEARCH IN MANAGERIAL ACCOUNTING: A SECOND LOOK, Accounting Organizations and Society Vol 15.No 4 p.p . 341-371.1 990.

Monday, August 06, 2007

Finding gaps

Gaps so far:
  1. mechanisms of accountability missing towards the end of a project
  2. potential lack of brief & timescales
  3. lines of accountability that might involve an intermediate client
  4. lines of accountability missed in a complex project than involves more than one service, (not in this project). Where a project involves two services then someone has to realise and communicate its existence to both of the relevant elected members.

Sunday, August 05, 2007

Points of view

I have five different people, all talking about the same project.

They seem to have overlaps of their perspectives of accountability, but also there are two different views. One is absolutely sure accountability existed all the way through this project and can immediately indicate lines and mechanisms of accountability. Another sees gaps. How do I reconcile these two views? I suspect that they are both right; that there was accountability but that accountability was only clear for the first phases of the project and not in later parts.

Agency theory suggests that information asymmetry between agent and principal means the principal wants information that the agent possesses. So if there is a public-sector manager who doesn't yet feel confident that she/ he knows what he /she wants to know, then the temptation to prolong the contract must exist.

Friday, August 03, 2007

Interviewing

I have this wonderful digital audio recorder that the department has lent me to do my interviewing. It's an Olympus DM-10 and apparently costs a small fortune. At Amazon, it's nearly £200, no, £300. But it records well over the speaker phone - I haven't got to meet any of my interviewees yet. It's small and fits into my hand and it's unobtrusive. I like it so much that I might get myself one. I suppose I could justify it if I am going on to do the doctorate and I do interviews again. And it would also be useful for one of my hobbies- recording what my older relatives say about family history. I'm convincing myself...

Thursday, August 02, 2007

Don't shoot the advisor

In the August copy of Management Today, Richard Reeves wrote this. He argues that it's up to the public-sector officials to make sure consultants' advice is of high quality. There's a balance needed between the cost of permanently hiring or training specialists that the service might need for only a few months, and bringing in the external expertise, but consultancies are profit making businesses, and must make money to survive. I like Reeves metaphor:
"If the public sector is handing out sweets, they can hardly be blamed for the resulting sugar high."
However, he does also accuse civil servants and politicians of deifying those in the private sector, and I don't know what evidence he has for that. It is not what I'm hearing from my interviewees. What I am hearing is that consultants earn their money by:
  • providing expertise that is not in-house,
  • moving organisations that wouldn't otherwise be moved and
  • saving the organisation more than they cost.
And if the lines and mechanisms of accountability are in place, then there won't be many undeserved sweets.

Wednesday, August 01, 2007

Draft in

The draft is in, and I await the verdict. Nevertheless, I know there were more additions and refinements, not least the extra perspective from the interview due on Friday. But there was also the feeling that it wouldn't matter if I didn't use quite the right language, or if I experimented with diagrams, which I have done when examining the number of relationships.

Tuesday, July 31, 2007

Discussion for supervisors

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.

Saturday, July 28, 2007

Supportive family

Isn't it wonderful what questions your children can ask? At lunch table my 17 year old asked me how I was analysing the data and I was explaining that I'd transcribed the interviews and then had devised some codes to put against chunks of speech, but that when I came to apply them they didn't work so I created other codes of climate, process and structure and subdivided those when I came across ideas that reminded me of something in the literature, like conflict suggesting political elements. I didn't know I could verbalise what I was doing.

Then the 17-Y-O, who is a mathematician was saying something about "but that's only opinion, not facts" and 19-year-old scientist got into debate of researching opinions and facts.

I'm so glad they're interested. They are going to have three more years of me doing this, and someone has to read my work before I give it to my supervisors.

Thursday, July 26, 2007

Analysing vs interpreting

The instructions say that chapter 4 should be about analysing the data, and chapter 5 interpreting the data. Well, some might say that those words are a bit similar in meaning, so I have to work out where they separate. I'm taking the analysis to be a description in the light of the codes that I've applied. The interpretation is more about explaining what the data reveals, and I'm structuring that interpretation against the roles and what they suggest in answer to the research questions.

Tuesday, July 24, 2007

Nerves

Our Director of Research Studies tells me that I did really badly at the PhD interview and he had to dig me out of it. I'm not surprised because I have often have done badly at interviews despite having an excellent CV, appropriate for the position and a suitable covering letter written well enough to get on the short list. So what am I doing wrong?

DoRS suggests I'm answering too quickly without first working out what the question is getting at. He gave some suggestions:
  1. take a few deep breaths - well I used to do that when gliding and ended up hyperventilating at the top of a launch and about to faint, so no, that won't work for me.
  2. ask the questioner to repeat the question
  3. write it down. I like that suggestion, so I was thinking about, when I had gone there prepared mentally to write down questions, why I didn't. It was because there was so much stuff in front of me, the laptop, my notes and a mug of water, that I would have had to move, but I couldn't move them because I would have knocked over the water.

Which brings me to a physical problem - why would I have knocked over the water? Because my hands shake when I'm nervous. I probably couldn't have read my handwriting if I had written the questions, because my hands would have shaken too much! My mother has trembling hands, only noticeable when she pours the tea, and tells me it is a familial tremor. Well, it hits me when I have emotional stress. In order to take up the DoRS's advice, I'm first going to have to deal with the tremor, so no caffeine, nor ginseng which also makes me shake. I do like the comment that apparently alcohol reduces the tremor, but at interview perhaps no glass of wine.

The DoRS's fourth suggestion was that I practise over the next year, that my supervisors get me to offer seminars on my research. That way I'll reduce the stress through familiarity with the process of discussing and defending it.

Monday, July 23, 2007

Writing the draft dissertation

The draft dissertation is due 1st August. I have heaps of issues to discuss in it:

  • the scapegoating or buck-passing that Harmon mentions, in a public environment where risk taking is avoided, and perhaps I have an example that manifests the avoidance or the fear of blame. I must look for alternative interpretations of the data.
  • reflect on limitations, what I would do differently and what I would do if I had more time
  • write on the unit of analysis for this project as sets of relationships around any one issue of accountability and multiple cases of relationships - I'm not sure what I'm trying to say here.
  • the psychological contract might be another perspective to emphasis
  • the principal-agent relationship is informal between the parties
  • reflect on the difficulties of anonymising in a single case study
  • debate the term transparency - what did it mean to those participants who used it, but I didn't follow up.
  • delimitation on the consulting project - when was the work completed (Werr, 2002:63)

Saturday, July 21, 2007

Analysing

I thought I might analyse the discourse from interviews against Werr et al's [1] two types of discourse: bureaucratic and network. I started out with a table:





Role Management of Consultants Example of discourse
CEO talked about process & strategy & outcomes"It's the funding which is something usually discussed with the individual and the cabinet member" and "there are contractual agreements"

Then I checked Miles and Huberman [2] had a role-ordered matrix, which in 15 minutes gave me a useful one page table of roles in the job, as primary,ultimate, intermediate clients. I've still to work out anything useful about recognising the types of discourse though.



[1]Werr, A, Styhre, A. 2002, Management Consultants – Friend or Foe? Understanding the ambiguous client-consultant relationship, International studies of Management and Organization, vol. 32, no. 4, winter 2002-3 pp43-66
[2] Miles, Huberman, 1994. Qualitative Data Analysis: an expanded source book, 2nd edition, Sage

Friday, July 20, 2007

Doing the Masters in Research

If a reader is interested in following this full time course, there's a document at
http://intranet.open.ac.uk/studentservices/publications/documents/research-degrees/MRes.doc
that gives the details.

Thursday, July 19, 2007

Ingredients collected

It seems as if I have a set of ingredients, the data I've collected from interviews, and a recipe book, the Miles & Huberman [1], but how I put them together is up to me, both in what I choose to do with the ingredients and how I mix them, so I come out with, not definitive results, but what I want to present, or rather, not necessarily what I want to present but what I'm able to present, depending on how I analyse and write.

I remember when I was little how I would have paints and paper, and want to represent a wonderful picture through my painting, but my paint would be too watery and I'd produce something horrid, not what I meant at all. I was disappointed because I couldn't show and share with other people what was in my mind.

So I must hone skills to use the tools and to communicate what I find.

Son's just been reading something from this week's New Scientist[2] on finding a mathematical proof after 7 years. Once a useful alternative view of the problem revealed a solution, it took days, hours to compress the proof to a few lines. Son said that he too could see this at his lower level of maths, where having realised the answer he wanted, he could say, "irrelevant, irrelevant, irrelevant" and strike out much, leaving the last succinct and correct two lines.

That's what I want to do too with this analysis - must be my mathematical background, but it's going through all the irrelevancies first before finding the points that you want and need.



[1] Miles, Huberman, 1994. Qualitative Data Analysis: an expanded source book, 2nd edition, Sage
[2] New Scientist, Proof and Beauty, page 48, 21 July 2007

Wednesday, July 18, 2007

Draft analysis

Coding is impossible. I started with codes on accountability, relationships and client types, but when I introduced structure, processes and climate I had a table of nine cells, each with six or more codes. I turned for Miles and Huberman for help, and ended up doing
  • contact summary forms
  • a role ordered matrix
  • rich pictures

Tuesday, July 17, 2007

Metaphors

Whilst analysing what people have told me, I'm enjoying the metaphors they use. Personally I cope better with visual metaphors, such as "walking through treacle", though some people use metaphors of taste such as "palatable promises". On reflection, I see the walk through the treacle, but perhaps someone else would feel the viscosity, and someone else would taste the treacle.

My colleague has just asked me if I'm transcribing everything, including the "erms" and "ers". But the ums and ers, and the "you knows" tell me something about the speaker in the same way as the metaphors do. One person used a lot of visual metaphors, another used only a few metaphors but more mechanistic, or I can't see the metaphors. One person used a lot of ums and ers whilst thinking about what the next word would be, or how to express something, whereas another had so many 'you knows' that I had to think there was an expectation that I understood, would agree, could encourage a somewhat perhaps shy or diffident character.

Monday, July 16, 2007

Literature

Supervisors' comments on my literature review for the last submission were that it was still a bit sparse. They suggested that I used references to methodological literature to help pad it out a bit; so I'll use such as Miles & Huberman and Gummersson and Yin.

However, I have been reading more on agency theory, pyschological contracts and clients, so may refer also to Eisenhardt, Conway & Briner as well as Rousseau and Miller.

Yeah. I know - that's just a list of stuff, but they are relevant in that they have theories that apply to what I'm doing.





Kathleen M. Eisenhardt, Agency Theory: An Assessment and Review The Academy of Management Review, Vol. 14, No. 1. Jan., 1989), pp. 57-74.

Gummesson E, 2000, Qualitative methods in management research, 2nd ed, Sage

Harmon, M. M. (1995). Responsibility as Paradox: a critique of rational discourse on government, Sage

Miles, M. B., Huberman, A. M. (1994). Qualitative Data analysis: an expanded sourcebook, Sage.

Miller, E. (1993). From dependency to autonomy: studies in organization and change, Free Association Books.

Rousseau, D. M, 2005, Developing psychological contract theory, in Great Minds in Management: The process of theory development, Eds. Smith & Hitt, Oxford.

Yin, R. K. (2003). Case study research: design and methods, Sage.

Friday, July 13, 2007

Data access

How odd! From waiting for weeks for the first interview that would set me off on this project, I suddenly get two more, with no or almost no notice.

I'd emailed someone on Friday, having found the email address through Google, so I didn't know if it would get through, but could find no other contact details. On Monday morning I delayed reading my email till 10.25, when I found a reply saying to ring at 10.30, or wait for two weeks. I was rushing round the office - fortunately had the digital recorder with me - looking for a phone with a loud speaker, in privacy. Our research degrees secretary was, as usual, helpful and I was suitably ensconced within 10 minutes, and able to do the interview.

Similarly, I'd sent an email to someone that was obviously waiting to speak to me and rang me at home the next day. Again, I was rushing around, trying to make sensible conversation, find my questions and switch on the recorder. Again, though it was a useful interview.

Now I'm still waiting, still negotiating via a secretary for access to another interviewee whose perspective is really important, and people keep telling me that interviewee will be pleased, delighted and eager to talk to me, but I don't know when.

Then there's a final interviewee who is someone I know already. I think I'll try to make contact there later in the summer, after the draft dissertation is in, so I don't distracted from the writing by the interview and the time that transcribing takes.

Thursday, July 12, 2007

Practical progress

Collecting data from real interviews is much more interesting than reading the literature. Now I've got to make sense of it.

Thursday, July 05, 2007

I'm in

I've just had an email suggesting that I

"might be pleased to know that we will be making you an offer to stay with us for another 3 years."

Might
!
I can't think of anything else I want to do.

No news

Despite feeling quite positive about my research question, and having an enthusiastic supervisor #2, and a calm supervisor #1, there is still no news about my acceptance or rejectance on to the doctorate programme.

Monday, July 02, 2007

Dispirited

It wasn't too good a week last week, waiting to hear the results of the interview as well as hoping to collect data from interviews, but with no interviews planned for another two weeks yet.

However, maybe things will fall into place this week. My contact has emailed me in reply to a query about contacting two more people, and is supportive. :)

Supervisors think we should still meet despite no data.

May be July will be good.

Friday, June 29, 2007

Unit of analysis

I'm rethinking my unit of analysis in view of:
  1. the questions that the interviewing board asked
  2. reading Eisenhardt [1]
Eisenhardt points out that both the positivist and the principal-agent streams share a unit of analysis that is the contract between the principal and the agent. Now if this unit governs the relationship between the principal and the agent, and I'm looking at how the relationship between the client and the consultant influences accountability, then my unit of analysis is the contract between the client/principal and the consultant/agent.

I had thought my unit of analysis was the project, and thought that we'd discussed that at a supervisory meeting, that the Master's would then extend into the doctorate by investigating other projects, but now I'm rethinking.



[1] Eisenhardt, K.M., 1989, Agency Theory: An assessment and Review, The Academy of Management Review, Vol. 14, No. 1. pp 57-74

Monday, June 25, 2007

Interview debrief

Some of the Phd application interview went okay, and some didn't. I don't know which bits were which and what will count to get me a funded place in the OUBS.

The presentation went as I planned it, so I'll not complain; it's the questions that were hard to anticipate, and indeed none were questions that I had thought they'd ask.

The four interviewers, 2 men, 2 women were all people I've met before.

Questions included:
  • What's your unit of analysis? (Female interviewer#1)
  • How are you going to theorise this?(FI#1)
  • Have you thought about value - I can't remember the exact question.(MI#1)
  • How are you going to get access? I'd have thought it would be fraught with ethical problems? (MI#1)

After the question on unit of analysis there was something else, I can't remember what but her response to whatever I said, was "but that's just descriptive" so I inferred that description wasn't good enough. Yes, okay. But if you compare descriptions you'll have a better idea of what's going on - she used the term 'cause and effect'. Yes.

The question on theory is phrased in a manner that means I don't immediately know what she wants and in fact, nearly freeze, thinking that I haven't got any theory, till I remember that although I haven't expected this question, I've anticipated it and jotted notes on structuration, complexity theory, Foucault and actor-network systems. I just don't know which way to go yet. From what she said, I'm afraid that not knowing might be a fault and that I should already know.

What was a success was that the research question is interesting, relevant and topical.

MI#2 asked me to describe my journey over the last year - he wanted reflection, so I said something about at least being able to be here and that I couldn't have coped with this interview last year, and that my marks initially were low, but have got better all year, and that I've learned to write, made contacts in the DTWs and in PACE sessions, and that I can now find research papers on the Internet. FI#1 said something about the 'tools'. Was that good or bad? I don't know.

I think that FI#1 & FI#2 said quite a lot, and I felt I just had to nod and say yes. Does that augur well? Or should I have said more?

There are five or 6 places, and at least six interviewees, though I thought ten had been invited to interview. We won't know the decision for a few days...

Friday, June 22, 2007

Adverse effects of Accountability

Lerner & Tetlock [1] wrote about experimental work that indicated accountability could produce inefficient decision outcomes. Under resource scarcity, decision makers would be inefficient but fair. I wonder if that works in the public sector, where people often suggest there is a scarcity of resources.

Later Siegel-Jacobs & Yates [2] distinguish between procedural and outcome accountability, and I wonder which is of greater relevance to using consultants in the public sector. I suspect, especially after having just read the 31st report of the Commons Public Accounts Commitee, that outcome accountability is what the media and MPs ask for, but if the procedural accountability exists, assuming that means a need to justify one's actions, then the project stages that use consultants will each be accounted for. Perhaps procedural accountability is less visible than outcome accountability. Perhaps there are more gaps in procedural accountability than the MPs and media realise.



[1] Lerner, J.S., Tetlock, P.E., 1999, Accounting for the Effects of Accountability, Psychological Bulletin, Vol 123 no 2 pp 255-275
[2] Siegel-Jacobs, K, Yates, J.F., 1996, Effects of Procedural and Outcome Accountability on Judgment Quality, Organizational Behavior and Human Decision Processes, Vol 65, No 1 pp 1-17

Thursday, June 21, 2007

31st report : Central Government's Use of Consultants

There's this report that criticises the public expenditure on consultancy. The one that the Public Accounts Committee published this week is a critique of the report on the Government's Use of Consultants that was published in November 2006. The committee took evidence from Mr John Oughton, Chief Exec of the Office of Government Commerce. He mentions accountability and some of what he says indicates the gaps that exist in accounting for consultants, so is pertinent to my research. For example,
  • Q49 Annette Brooke: Can you just tell us a bit more about applying lessons across departments?.. What is it that is the barrier to sharing good practice and making progress on all fronts, as it were?

  • Mr Oughton: The Chairman invited me to a reflective session at some stage before the end of March. One reflection now, if I may? There is still quite a strong resistance to ideas that come from elsewhere and this is not just a public sector issue, it is a private sector issue as well. Other people’s ideas are never treated as warmly as one’s own; that is just human nature. Breaking through those barriers and encouraging the sharing of good practice and the adoption of good practice is a big issue. It is slightly reinforced by the system of, and this is very much a personal view, accountability that we have here, where each department is accountable for its own delivery and feels, rightly, very strongly that it must do the best job it can. That rather discourages them from looking at other people’s ideas and other ways of undertaking business. ..
So this civil servant is talking about the public servant's accountability, yet the report says that:

"clients need consultants to show ownership and accountability to implement their work"

It seems to me again, that the MPs and media take away the requirement to account from the public servant client of the consultant and put the requirement on the consultant, despite the evidence that the public servant should account.

At Q127, Mr Oughton again refers to accountability of the accounting officers, not the consultant:
  • My own view however is that the sense of accountability that accounting officers and those who report to them have actually means that it is really not in our style, it is not in our fashion to be putting the blame elsewhere. You may not believe this but the sense of accountability that we have, both in responding to the work that the NAO do and to the work of this Committee, is a real one. I do not try to push that off on others by saying I have taken advice from someone and I am going to disown that advice. If I have paid money to secure advice, then I stick by that.
Accountability came up again from Mr Williams in Q136. Government departments had been asked for progress reports, but two did not respond to the request. Mr Williams remarked:
  • It would be interesting to know which the departments were, when it was and at what level there was any accountability in relation to this.
And although a footnote identifies the culprits, there is no explanation of accountability.

Finally, at Q142 from Mr Bacon compares the situation in the UK with the USA.
  • What is wrong with and what is contrary to greater openness and accountability—and I accept the points you make about accountability—in having a more statutory Clinger-Cohen type approach? Why can you not go down that route?

I don't know about this Clinger-Cohen approach so must find out.

Monday, June 18, 2007

Reviewing qualitative readings

I wish I'd found this blog that reviews the qualitative readings earlier. It's really useful. It is written by an OU student who was studying E835.

Saturday, June 16, 2007

Consultant interview questions

It would seem sensible to interview the consultants in the relationship too, to get their perspective on the relationship and how they see the client's accountability for using consultants. But what questions should I ask in order to elicit this?

Thursday, June 14, 2007

Client interview questions

To find out where each interviewee fits into the organisation, ask about job title.

To find out about the project ask about:
  • Original intention of the project
  • Name of consultancy
  • Type of consultancy
  • Money – cost and expected savings
  • Days
  • Number of people – client side & consultants
  • Reasons for use
  • Outcomes expected
  • Outcomes delivered
  • What worked well?
  • What was problematic?

To find out about client-consultant relationships ask:

  1. At what stage(s) of the project did you work with consultants, (thus identifying client type in Schein’s suggested type: contact, intermediate, primary, unwitting, indirect, and ultimate.)
  2. How did you work with consultants?
    What did they do and what did you do? What are your positive and negative experiences of the use of consultants on this project? (cf Werr et al, 2002, image 1)
  3. What has been successful in the management of consultancy on this project? (cf Werr et al, 2002, image 2) and what has been difficult or problematic?
  4. Do you think in general the problems to which consultants are called to solve are the really important ones? Why do you think that? Who should account for consultants that are called to solve these problems? How should their use be accounted for? (From Gattiker & Larwood’s 10th question)


To find out about accountability as perceived by the interviewee ask:

  1. What is your understanding of accountability with respect to consultants?
  2. Who do you render account of yourself to, with respect to the consultancy, and about what, or in which terms?
  3. How was accountability put into practice and monitored?
  4. What impact do the mechanisms of accountability have on: a) quality of the consultancy work done b) outcome of the consultancy work (See Ezzamel et al, 2007) Did they have any other impacts or effects from your perspective?
  5. Can you recall a particular incident in which you were aware of accountability? Describe it. Explain it.
  6. Who do you regard as having the main accountability for the effective use of consultancies in general? And also with respect to this particular project?

Finally:

  1. Who else could or should I talk to?
  2. Do you have any other advice or comments for me?

Wednesday, June 13, 2007

Planning data collection

What's an interview schedule? Supervisor #2 wants one. I guess it must include times and names of interviewees, but I can't do that yet. I can describe the project, guess some interviewees, have two contacts and have some thoughts for questions.

He can't have seen the appendices that I added to the proposal, which is where I wrote some people and some questions.

Tuesday, June 12, 2007

Latest literature

I have been reading something very recently published on accountability as discursively constructed in the field of education.

Saturday, June 09, 2007

Positive progress

"General direction and focus is encouraging"
wrote Supervisor #2 on my recent proposal. He even thought that I could get some papers from the research. So I feel a lot happier than I did when he returned my last B852 TMA. He and S#1 were extremely helpful yesterday showing me how to tighten up wording, pointing out and rewriting bad research questions, avoiding the wrong arguments or stands. I have to:
  1. revise the draft proposal
  2. start collecting data
  3. read Miller [1] on the different versions of clients
  4. and write S#2 a couple of pages on the project, people and accountability that I'm asking about, together with an interview schedule.
I must remember that a constructionist view is, I think, that of a single person, rather than the social constructivist perspective that builds together.

They pointed out my research questions were ontologically social constructionist, and therefore a wording 'to what extent..?' was wrong because it implied a quantitative approach, and they should read 'How', and be descriptive.

Then, when I asked if they thought I should apply for the doctorate they even looked slightly surprised that I was considering asking, as if it had been an expectation, rather than the nightmare I was suffering.




Miller, Eric, 1993 From Dependency to Autonomy: studies in organization and change, Free Association Books, London

Thursday, June 07, 2007

Collecting data

I've managed to record two interviews, one only 20 minutes on the phone and awful sound quality and the other face-to-face. The short one should lead, I hope, to a case study, and I'm already finding documents to go with it and some interesting relationships between consultants, clients and accountability. The longer interview was more about getting practical background but led to some themes. For example:
  1. there's a mass of written or electronic evidence available for public projects.
  2. more projects work in teams rather than hierarchical now than some years ago, so accountability might be a team duty rather than pass up the hierarchy.
  3. but OTH, some public organisations will still be hierarchical.
  4. therefore, although I might expect to find network discourse expressing accountability in a team context, I might find hierarchies in the public sector, a concern with control and consequently the discourse on accountability will be bureaucratic.

Saturday, June 02, 2007

Data collection

I need some data. I need someone who has used, tasked, managed, selected, worked with consultants in the public sector to talk to me and let me record what they say.

Friday, June 01, 2007

Research questions from the literature

I'm pleased, and slightly surprised to find that my initial questions, months ago, have developed into something researchable. I had thought those initial questions were researchable but perhaps they weren't and anyhow, I had a less clear idea of how I'd research them than I do now. From the literature I have evidence that both accountability and relationships are discursive constructions, which means that research needs a constructionist perspective, a qualitative approach to data collection and either grounded analysis or discourse analysis. I think the questions are:
  • To what extent do public sector managers account for their use of consultants?
  • What do different public sector managers do to demonstrate their accountability for managing consultants?
  • To what extent does the kind of client-consultant relationship, influence the expression of accountability in a public sector organisation?
  • Are there gaps in public accountability?


It's the third one that is researchable and most interests me.

Thursday, May 24, 2007

Four important papers

Four research papers particularly interest me:

  1. Appelbaum, S. H. and A. J. Steed (2004). "The critical success factors in the client-consulting relationship." Journal of Management Development 24(1).
  2. Kaarst-Brown, 1999, Five symbolic roles of the external consultant: Integrating change, power and symbolism, Journal of Organizational Change Management, Vol 12, no 6. Accessed 15/4/2007
  3. Sinclair, A., 1995 “The Chameleon of Accountability: forms and discourses.” Accounting, Organizations and society 20(2/3.): 219-237
  4. Werr, A, Styhre, A. 2002, Management Consultants – Friend or Foe? Understanding the ambiguous client-consultant relationship, International studies of Management and Organization, vol. 32, no. 4, winter 2002-3 pp43-66

How to use them best?

  1. The Appelbaum et al is a quantitative analysis of critical success factors in the client-consulting relationship.
  2. The Kaarst-Brown is a qualitative analyis, again of the client-consulting relationship, interesting & amusing but perhaps too subjective, not sufficiently validated to be useful, and a retrospective self justification for a project that had gone wrong.
  3. Sinclair's article is important for the light she sheds on the discursive construction of accountability by public sector managers.
  4. Werr et al similarly qualitatively analyse the discursive construction of the client-consultant relationship.

I think that the Sinclair and the Werr et al articles are the most important because they both identify discursive constructions of the aspects that interest me. Perhaps my research must look at the discursive construction of accountability and the relationship of that construction to the client-consultant relationship.

Tuesday, May 22, 2007

Accountability for the apple

I can imagine a scene in Paradise, the walled garden surrounding the apple tree, the core lying on the grass, the serpent slipping away, while Adam and Eve account to God for their decisions and actions.

"She did what the consultant told her."
"The consultant advised me to do it."

You see, an interaction exists between these components:
  • Paradise to be lost on accounting for the wrong actions,
  • the stakeholder eye of God watching the actions,
  • the two client managers and
  • the consultant.
It looks to me like a system, but that's because I went to John Martin's seminar on Emergence, and this idea struck me when he was describing gardens as systems like the one at Bagh-e-Shahzadeh at Mahann in southern Iran. The surprise is even when they exist in the middle of a desert,

Monday, May 21, 2007

Cross

Well today I'm more cross than glum. I read marker's comments on last TMA, then looked at the breakdown, but it is odd because the individual scores add up to more than the given score. I scrape on to the PhD, depending on interview and competition. I look between the lines, knowing tutors mark to encourage or to discourage. A tutor should have checked the overall mark was indeed right for this TMA for this student. If it was, then he should have adjusted the individual marks, so the message came across clearly; if it wasn't he should have gone back and re-added them.

I spent yesterday evening looking at a couple of web sites, at universities that research the web, business and governance. I'm too late to apply now; e.g.The Oxford Internet Institute applications had to be in by 18 May but as some of our PGs came in January, it may be possible to get somewhere else in the new year, like De Montefort or Brunel, both of which research areas that interest me.

So now I've gone from very, very glum, to being cross, and then being sulky. Yes, I've learned loads, and at least I won't have to go through that part of the process again, if anywhere will take me with my inability to explain, justify, consider, discuss or write clearly. And I did enjoy writing that TMA. :(

Sunday, May 20, 2007

Glum

I'm not doing well enough at this. I'm good in some areas but not where things get assessed, so I had better be looking for something else to do in October.

Friday, May 18, 2007

The really important problems

The problems consultants are called upon to solve are often not the really important underlying ones [agree (1) – disagree (7)][1]

This question involves the direction of the organisation, its mission and how it functions because you are looking at change and can’t ask people there to think of a different way of delivering the service. I anticipate the answer to this question will be different according to the relationship with consultants. Gattiker & Larwood designed the question in order to examine the political dimensions of the client-consultant relationship. The political dimension might be hiring a consultant in the belief that a consultant could lend meaningful weight to support a particular position, especially when bringing about change. So they anticipated finding that consultants might not know the important underlying issues behind their being hired. What the research found was that clients & consultants response to this question didn’t vary significantly from the expected chance value, so evidence for political hiring was mixed.

But that question need not be interpreted as about politics, but rather about choosing to consult on the right issues for the right reasons, and there is a need to account for that choice, isn’t there?



Secondly, G&L examined data from top-level personnel and it may be that lower level personnel have different perspectives on those reasons, and require different accountabilities. G&L suggest that “lower-level personnel have less need for influencing changes in organisational direction”, which might be true, but OTH if such personnel want to keep their jobs after change, then they would have different interests, different accountabilities and different responses from the executives. And public sector employees have different forces acting on them from corporations.


The weltanschauung of accountability to public is not the same as that of protecting jobs. Here, the accountability is for improving service not about change, but less cost and fewer people. But employing fewer people again implies that jobs are lost, and there is accountability for loss of jobs. (In a British society – a democratic society requires accountability, but an American culture will be less concerned with loss of jobs than a British one. Stakeholders in a British culture will include the workers and their union reps)




[1] Gattiker, U. E. and L. Larwood (1985). "Why do clients employ management consultants?" Consultation 4(Summer 8756-6508): 119-129.

Thursday, May 17, 2007

Methodology

If that CEO lets me, then I'm going to do a single organisation case study. The intention is to get information from and about a number of client representatives (cos Schein identifies different kinds of clients) and find out how they express accountabilities (different kinds of accountabilities) for their use and management of consultants. I should be able to map accountabilities to the different client stakeholders. So the data should match the theories I've read from Schein, Werr, Sinclair, Bovens, etc.

Analysis may be discourse analysis from interviews (takes ages to transcribe :() and stakeholder analysis and soft systems analysis (Checkland).

You see, that's my summary of my research proposal, which is supposed to be thousands of words and I'm assuming all the bits that I have not written. What else must I write about? Ethics - I'm stuck again. Access - okay. I have to write about the limitations of the research and why it's a good idea to do it this way - i.e. justify my approach, which I suppose also includes discussion of validity, generalisability ( a bit difficult with case studies).

Wednesday, May 16, 2007

PhD recruitment interview

In June the OUBS interviews us and external candidates for the six funded places on the PhD. I have 15 minutes to present to the panel:
  1. my ongoing research project for MRes (max 2 slides)
  2. how that research might be extended into a PhD project (max 2 slides)
Then the panel will ask questions on the presentation and "related issues" whatever that might mean. I also have to give in a clean copy of my first dissertation module assignment - it was okay, but I don't have a mark - and talk to my supervisors about their willingness to supervise me . I hope they both do.

And I wonder how the external candidates manage these hurdles.

Tuesday, May 15, 2007

Research progress

We are moving on from literature review to collecting data and some of us are having problems.

My Neighbouring Student emailed:

"I feel as if I am going around in circles with the research proposal. There are a number of ways I could do the research and I am struggling to explain why my prefered route is best."

Student from Hampshire is balancing home, health and study, about to take the family on a holiday, followed by an operation, but she hasn't yet collected data and has no participants to observe.
" Pressures of trying to get everything done before going away really - just not enough hours in the day and need to prioritise."

NS also has a family with a son that was off school yesterday so she had to stay home but has managed to get in for today's doctoral workshops conference presentations.

And I'm dead chuffed that I've had an encouraging email from a CEO whose organisation I'm hoping to use as my unit of study.

Friday, May 11, 2007

Accountability and tofu

Accountability is an abstract concept that is variously and metaphorically described as a social and political process (Day and Klein, 1987; Sinclair, 1995) with dimensions (Day and Klein), functions (Bovens, 2005), forms and discursive constructs (Sinclair, 1995).

And as a chameleon, a chimera, links in a chain, and tofu. Tofu? Yes - go and download Dubnick's draft paper, as he says not to quote it yet.

Thursday, May 10, 2007

Clients and accountabilities

Had a supervisory meeting with S#2 today. Brilliant idea. Schein has identified several different types of client, and various writers describe different kinds of accountabilities. There may be research questions about how these accountabilities match to clients. Perhaps they could be mapped...

Sunday, May 06, 2007

Why blog? why write?

At last week's Curriculum, Teaching & Student Support Conference at the OU there were reports from people who are investigating the use of blogs as learning tools. It seems an area ripe for research though I worry that some are saying "we've got a tool; how can we use it?" in the way that they say, "we've got a hammer; what can we hit?"

However, I agree with Miranda who wrote,


"it’s like I have a running commentary in my head that just goes on and on, and it’s so abstract that writing is like the only way to make sense of what’s happening. Some days I write over fifteen pages straight, and still have no idea of what I’m trying to say, just that I haven’t said it yet."


She is right; writing reflectively is what helps to make sense of what's in my head though I can't say that I'd write 'over fifteen pages straight'. I'm surprised how much I do write if I make the tiniest effort. And there's something about blogging that is better than writing a diary. There is this possibility that someone will read it because you do publish it in the hopes that there might be someone who wants to comment, so it's more than just reflective. And I also find it useful to go back to when I get to certain points in my study. Thoughts I had had come in useful later.

Thursday, May 03, 2007

Aporia

When supervisor#2 to me last week that perhaps I was being too perfectionist in discarding possibilities, that he was being kind. Perhaps I am suffering from aporia. Do you know this term? I think this pertains to my lack of philosophical rhetoric. Apparently, aporia means:

"a state of puzzlement resulting from philosophical objections to proposed courses of action whilst simultaneously lacking any alternative solution." [1]

But Wikipedia also says it is an expression of doubt. I came across it in the context of performance appraisal, which is either “lauded” as central to organisational effectiveness or “denigrated” as a ritual. I suppose the state arises from such conundrums or dilemmas.

I suspect aporia applies in some way to accountability and might also relate to stakeholders and contracts. Supervisor#1 mentioned relational contracts. Contracts are usually thought of as legalistic and there are psychological contracts. Perhaps analysis of legalistic and relational contracts would reveal some aporia.

How would a stakeholder approach enable effective governance?





[1] Simmons, J., Eades,E., 2004,
Challenging aporia in the performance appraisal of consultants: a stakeholder systems reponse, Clinician in Managment 12:153-63

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:

  1. a relationship of accountability

  2. 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

Monday, April 30, 2007

B852 ECA

Submitted in time! (ECA=Examinable Component of Assessment)

Now it's gone in - the most I've written for 14 years and I'm quite pleased, not only because of the quantity (6000 words) but I think I've written a coherent argument for the research that I'm suggested.

Having said that, I'm not now sure that I can remember what I wrote! :( For instance, I reviewed Gable's research on success factors when engaging consultants, but cannot think of much wrong with it as a piece of quantitative research. Then, I suggested qualitative research using Forster's suggestion of a hermeneutic approach using documents together with interviews, yet now I wonder what research question I was proposing. And I spent so looong choosing a paper to critique. The part-time students get told a paper, but choosing one is a learning process in itself.

Finding sophisticated research questions is what I'm now supposed to be doing for the first tutor marked assignment (TMA) of the dissertation, the literature review, which is due 1st May. Any and all research questions are eluding me.

Friday, April 27, 2007

Conversation

I spoke to a Civil Servant about consultants. CS had herself been a consultant and had recently joined the civil service in a senior position. She argues that accountability is not an issue, that red tape is a nuisance and that civil servants need to take more risks but also that some projects need not go wrong if the civil servant clients do the right things, manage the project, use NAO and OGC guidelines.

Sunday, April 22, 2007

Tracking an accountability writer

One of my readings on accountability is by Melvin Dubnick. After finding his web page from a link on a paper of his, I've also found his blog. I notice that he keeps track of his readers by using Technorati at Technorati Profile so I shall try it too.

Saturday, April 21, 2007

Hermetic paranoia

What a lovely term! Hermetic paranoia! Perhaps it means that I've got too many ideas coming at me.

"Most intellects are honed, not blunted, by use. Too frequent a resort to argument by analogy can lead to a hermetic paranoia in which everything is seen as part of a vast and secret conspiracy."
Fisher, 2004: 80

I think I've got it from reading too much for my literature search and attempt to write the second draft of the literature review for my supervisors.

Fisher, C, 2004, "Researching and writing a dissertation", FT Prentice Hall

Thursday, April 19, 2007

Nebulous clouds, wise owls, and frogs

I'll follow up my PACE presentation (See Weds April 18) and add photos here with the props that I used to explain my story and my slides. Here's a start:

  • Clouds of accountability
  • Owls who give consultancy advice, at a price
  • Frogs? We'll come to that later. For now, the frog represents the public service manager.
Feedback included:
  • that the topic seemed political, so I must rethink my wording.
  • that it would be useful to have a slide that states a definition of accountability or develop a conceptual framework of relationship between accountability and consultants in the public sector.

Wednesday, April 18, 2007

Professional and Academic Communication in English presentations

The PACE course culminated in our presentations. There were six of us who presented:

ET: 'Globalisation and international adoption'
LW: 'Internet-mediated intercultural foreign language education - access and opportunities within and beyond the classroom in China’
SB
: 'Ethical decision making in designing products'
MB
: 'Teleporting'
GC: 'How can language creativity be incorporated into the classroom in universities in China?'
me: 'Accountability in the public sector for the use of external consultants'
VS:
'Plasma Crystals'

When we walked into the room, we immediately saw strangers, and a TV camera. NO! Two TV cameras. Aagh! and another person with a sound boom. So we were a little uncomfortable, nervous, and found any excuse to delay starting at all. Our stalwart tutor BM, led us round the room saying the alphabet all in one breathe. Or trying to say it in one breathe. The idea was that when we stopped walking around, just the speaker would carry on to the front of the room, the cameras would roll and BM would introduce the speaker. An alternative to this exercise was to say

me-me-me-me-me-me-me-me-me-me-me-me-me-me-me

on one long breathe, the idea being that this would reverberate in the nose and energise us ready to speak. Perhaps.

We all mastered the technology, using the computer and PowerPoint, despite one file or USB stick not quite working initially. It is a shame but relevant that the news today links to "No point to PowerPoint" though this was also last week's news. In fact, it's not PowerPoint that should be ditched, but the way that the tool is used.

But it was a most useful and interesting session. I love knowing what other people are researching and how they are doing it. Research seems a fascinating occupation.

Another thing that I've really enjoyed about these PACE sessions is the input from the ESOL speakers, because they've shared their culture and experience of English. Their standard of English is very high, and although I can speak and work in one other European language, I couldn't say that I could research and write at this level. They are admirable.

Tuesday, April 17, 2007

U501 workshop on presenting

This was one of the more useful workshops. One of the exercises involved groups putting together answers to:
  1. What makes you nervous about giving presentations?
  2. And how do you deal with your nerves?

The various groups came up with the following answers to the first question.
Things that make us nervous are:
  • timing
  • fear of failure
  • argument
  • blank mind
  • sounding stupid
  • stage fright
  • embarrassment
  • getting the words out, the volume right, stumbling, speed, ESOL
  • being exposed as a fraud or charlatan or lazy and someone else knowing more
  • fear of questions or of lack of questions
  • personal appearance
  • overwhelmed by too much stuff
  • too little stuff and ten minutes left empty
  • the person that you are quoting being in the audience
  • terminology, concepts and theories that you are not aware of

Answers to the second question were fewer.
How do you deal with your nerves?
  • admit ignorance
  • stick to the story
  • breath
  • be well prepared, practise, have a script
  • get to the venue early
  • encourage your self
  • google the experts who might be in the audience
  • joke
  • have alternative equipment
  • prepare answers for awkward questions e.g. "yes, that's fascinating and I intend to look further at it"
  • body language and posture
Categories from the above could be:
  • Me
  • My material
  • Equipment
  • audience & questions



Me

Problem

Advice


Fear of failure


Encourage your self


Blank mind.

Getting the words out, the volume right, stumbling, speed, ESOL

Have a script.

.

Sounding stupid. Embarrassment

Body language and posture

Stage fright

Breathe

Personal appearance

Dress appropriately



The material

Problem

Advice

Timing

Rehearse

Too little stuff and ten minutes left empty

Prepare & practise.

Overwhelmed by too much stuff

Be well prepared. Practise.


Equipment

Problem

Advice

I can’t use equipment, or it won’t work with my data

Take an alternative form.

E.g. take transparencies as well as keeping them on a USB stick.

Unfamiliar equipment

Get to the venue early



Audience

Problem

Advice

Argumentative person in audience

Stick to the story

The person that you are quoting being in the audience

Google the experts who might be in the audience

Being exposed as a fraud or charlatan or lazy and someone else knowing more

Admit ignorance


Terminology, concepts and theories that you are not aware of.

Fear of questions or of lack of questions

Prepare answers for awkward questions e.g. "Yes, that's fascinating and I intend to look further at it"

Sunday, April 15, 2007

Accountability: the word and the concept

Melvin Dubnick makes the distinction [1] between accountability as a word and as a concept.

As a concept it is really difficult to explain, which is why I used a cloud of cotton wool as a metaphor for it in my presentation last week. Accountability seems to change to suit the way the context blows it, who the person in the context is who has to account, and the person being accounted to.

As a word, it is fascinating. Dubnick is right that there isn't a common language to translate it. My French is reasonable, so I tried to translate it and thought it might be "responsibilité " as my old Collins Robert doesn't give accountability, but only accountable, which translates to "responsable". But then I found a French Canadian paper that uses the word "imputabilité". I discussed it with our Spanish lodger who suggested "responsabilidad" and I've found in the Collins Easy Learning Spanish "to be accountable to someone" is "responder ante alguien", which don't seem quite the same. One of my Chinese colleagues looked thoughtful and said that she couldn't think of an exact translation in Chinese. I don't know if she was looking for the word "accountability" or a way of expressing the concept.

If it is so difficult to catch the meaning, then how much more difficult is it to enact accountability, particularly when there are so many people in an organisation who must account for a decision and actions, and so many stakeholders?




[1] Dubnick, 2002, Seeking Salvation for Accountability

Saturday, April 14, 2007

Symbolic roles for consultants

Kaarst-Brown (1995) together with a fellow consultant set up what was to be a five-year consultancy project with a client. However, at the end of the first year, the chief executive terminated the project even though there was much work outstanding. Nevertheless, the client expressed satisfaction with project, progress, cost, behaviour and relationship. It was Kaarst-Brown’s perception that the project had failed, and she set about a retrospective participant observation and analysis. As a result she found that consultants had a symbolic role to play and that these roles matched Lewin’s stages of unfreezing, transition and refreezing (Lewin, 1951. So, for example, just the arrival of a consultant was symbolic of change yet to come. If the wrong symbolic role was played, then the consultant might give out signals inconsistent with the stage of the project. Kaarst-Brown concluded that at one stage the two consultants had played a symbolic role that implied the project was coming to a successful conclusion, which the CEO had perceived as success and so had concluded the consultancy.

The research questions that I would want to follow up are:
  • Are the consultant’s symbolic roles to be found in project documentation?
  • Is there evidence of Kaarst-Brown’s symbols at various stages of the project?
  • Can these symbols be seen in the project documentation or heard in the discourse?
  • Do the symbols reveal existence of project governance?


Kaarst-Brown, 1999, Five symbolic roles of the external consultant: Integrating change, power and symbolism, Journal of Organizational Change Management, Vol 12, no 6.

Friday, April 13, 2007

B852 ECA progress

Progress is slow. I have the structure, but that is given by the format of the question. I know the content for both sections, but need to put it together. To my surprise I can see a logic forming that links the two sections.

In the paper I'm reviewing, there is x, but it could be y and z isn't dealt with. Therefore in my proposed research I'm going to use y and deal with y in the light of z.

That is, the research (by Gable) is a statistical analysis in the positivist paradigm of the factors that predict success when engaging external consultants, which means that Gable believes it is possible to measure success factors. Therefore my proposed research will take the view from the opposing paradigm, that is from the constructivist perspective, that as it isn't possible to measure what makes for a successful project, then I'll research projects by collecting and analysing data that comes from project documentation, supplemented with interviews. Analysis will use the hermeneutic method. (See Forster[2]))

How does that sound?


[1] A multidimensional model of client success when engaging external consultants. By: Gable, Guy G.. Management Science, Aug96, Vol. 42 Issue 8, p1175
[2]
Forster, N, The Analysis of company Documentation in Cassell, Symon, (Eds) 1994, Qualitative Methods in Organizational Research: a practical guide, Sage