Showing posts with label design. Show all posts
Showing posts with label design. Show all posts

Thursday, 3 September 2009

Data collected

Director has just come in - back from her break. First question she asks of course is if I'd had a good holiday. As I mutter something about it being quiet and I had written something, she asks if I'd collected all my data. Ha! think I, third year looms so she thinks I should have collected all my data and it's ready to code and analyse. What an ideal!

Indeed, I'm going to use the data I've already got , but I'm also going to have to use the ad-hoc data that doesn't fit into the planned design using case studies because I can't get access to big IT projects, I can't get to talk to lots of people on one project. But I have got some access to some projects and I have talked to individuals. I might get the chance to talk to other individuals in sufficient depth to know how engagement happens between clients and consultants.

Tuesday, 9 June 2009

Designing public services

Spent the day at the Government Computing Exhibition, just to wander round the stands, see who are consultants, what services they offer: legal, data, management, IT, training. The talks were interesting. One was on
What if public services were designed the way users want them?
The speakers included:
  • David Brindle, the Guardian, Public Services Editor
  • Alexis Cleveland, Director General Transformational Government, Cabinet Office
  • Joan Saddler, National Director for Patient and Public Affairs, Department of Health
  • Sir Michael Bichard, Chair of the Design Council and Director, the Institute for Government
Sir Michael Bichard started by pointing out how bad the UK public sector is at designing services. At service design in the private sector the UK is a world leader. Design drives innovation, provides tools to create, which leads to profits in the private sector, where we are good at design. These techniques can transfer to the public sector. We need to work collaboratively across bureaucratic boundaries, and integrate IT. He gave an example of LiveWork, which explored and mapped barriers to work. IT found a confused offering from different groups that was rarely understood by the client. Redesign was required.

Alexis Cleveland talked about the cost of error and failure, agreed there was a need for innovation and gave some examples of best practice, empowering citizens. For example, they redesigned a system for receiving phone calls to 18 numbers, thereby reduced calls, but the system meant that funding went down because there were fewer calls. They also noticed that demand peaked on Monday, and discovered it was a reaction to sending letters on Thursdays. So they redesigned when letters went out. The redesign meant a reduction of nearly 50% of staff, the number of compliments went up and complaints went down. Another example was setting up a web site Show Us a Better Way to ask the question. It sounds great, but how do the inarticulate articulate a better way?

What would you create with public information?

They got the public to suggest web sites that would be useful to them, such as how to find a school near where you live. Data mashing produced a school map. The public got a lot of value, and it cost the government nothing because it was designed by those who wanted the information.

Joan Sadler required design to listen to patients and staff. Communication is part of good leadership. For example, Obama referred to "mutual interest and mutual respect" without presuming what is best. She wants to check what staff use, without imposing a solution, but recognising a right to engage effectively with a system, designing around a person. Again though how do those too humble and quiet express what they want?

Questions came from people at Thames Communication, Alexoria, Berkshire Consultancy.

I hadn't thought of design in the context of services, but then I'm neither a designer nor a provider of services. This was an illuminating talk that merited the time and further discussion.

Monday, 22 September 2008

Research design

Following Jennifer Mason I'm matching my research questions to the methods that I intend to use to answer them. For example, if a subquestion is:
How does engagement contribute to an effective project?
then I'll use
  • Observation
  • interview data
  • shadowing
I'm getting a table for each research sub question with headings of data sources, justification, analysis and relationship to theory. I am changing some headings for the ethics proforma that I must submit. That includes practicalities and ethical issues.

The justification for interviews is that they will provide client manager’s accounts of how they and the users engage with each other and with the consultants. Observation will triangulate that data, though I don't know that I will have much opportunity to observe or shadow, depends on the access I get. So another column in my table will be practicalities, like access, time, equipment.



Mason, J. (2002) Qualitative researching, (2nd ed Edn), Sage, London. 973