Action research Science or bullshit?
May 2002© Per Flensburg2 Who am I? Per Flensburg, Professor Växjö University Started as mathematician, ended as humanist Thesis about End User Computing Doing research in cooperation with users and trade unions Following “The scandinavian School” – at least one of them
May 2002© Per Flensburg3 Action research - what is it? 1. Helping weak part to help themselves 2. Doing free consultancy for weak parts 3. Research in cooperation with users 4. Empirical, qualitative research
May 2002© Per Flensburg4 Key concepts Facilitator Catalyst Intervention Change Process Help to help yourself
May 2002© Per Flensburg5 Change process Change in power, increased power to a weak group Increased quality of working life Self-steering groups Either with trade unions or Socio Technique with the employer
May 2002© Per Flensburg6 Facilitator & Catalyst Shall not do anything herself, but encourage other to do things Shall absolutely not make any decisions Shall keep the change process going Something between a teacher and headshrinker
May 2002© Per Flensburg7 Intervention Will always cause a lot of turbulence both in the participating organisation and the researchers Outcome is not possible to predict Middle management often work against the change
May 2002© Per Flensburg8 Help to help yourself Means working at a meta level The facilitator should not do anything within the domain Encourage without doing
May 2002© Per Flensburg9 Problems in AR Choosing participants Those who not participate Middle management Different opinions of the catalysts Uncertainty of the outcome
May 2002© Per Flensburg10 Result of action research Result describes in terms of a typical case. In such a case every company should recognize itself in certain respects, but probably will no company recognize itself in all respects.
May 2002© Per Flensburg11 An example A foundry in middle Sweden The users constructed a production planning system based upon spread- sheets The following is a collection of some presentations I made in the middle of the 90’s
May 2002© Per Flensburg12
May 2002© Per Flensburg13
May 2002© Per Flensburg14
May 2002© Per Flensburg15
May 2002© Per Flensburg16
May 2002© Per Flensburg17
May 2002© Per Flensburg18
May 2002© Per Flensburg19
May 2002© Per Flensburg20
May 2002© Per Flensburg21
May 2002© Per Flensburg22
May 2002© Per Flensburg23
May 2002© Per Flensburg24
May 2002© Per Flensburg25
May 2002© Per Flensburg26
May 2002© Per Flensburg27
May 2002© Per Flensburg28
May 2002© Per Flensburg29
May 2002© Per Flensburg30
May 2002© Per Flensburg31
May 2002© Per Flensburg32
May 2002© Per Flensburg33
May 2002© Per Flensburg34
May 2002© Per Flensburg35
May 2002© Per Flensburg36
May 2002© Per Flensburg37
May 2002© Per Flensburg38
May 2002© Per Flensburg39
May 2002© Per Flensburg40
May 2002© Per Flensburg41
May 2002© Per Flensburg42
May 2002© Per Flensburg43
May 2002© Per Flensburg44
May 2002© Per Flensburg45
May 2002© Per Flensburg46
May 2002© Per Flensburg47
May 2002© Per Flensburg48
May 2002© Per Flensburg49
May 2002© Per Flensburg50
May 2002© Per Flensburg51
May 2002© Per Flensburg52
May 2002© Per Flensburg53 What happened The production planning system was developed, but was never taken in use, since the users (=the project leader) did not trusted it. The report system was developed with help of an external user hired consult. It was taken in use and worked very well. The users continued making there own support applications The IT-manager was fired
May 2002© Per Flensburg54 Traditional planning system Production ordre Production report
May 2002© Per Flensburg55 Planning at the foundry Core factory Moulding Melting Snagging Cutting edges Core odre Iron odre Casting odreCustomer odre