Systems thinking summary - check, plan, do

I've just found this helpful summary of what systems thinking is and I've copied and pasted it below. You can find the original on the University's system thinking pages, there are also some pages on containing information and resources from last week's Why systems thinking conference (that I blogged about here).

We've done 1 and 2 of check but there's still plenty more to (plan and) do...

Check

This involves the following stages:

1. Identifying purpose of the system (e.g. admissions) from the student's perspective ('Make me a student')
2. Analysing demand, e.g. value demand - 'I want to find out more about a course' and failure demand - 'I can't apply online', to identify what matters to the student
3. Looking at our capability to respond to that demand
4. Studying the flow of work; identifying value work and wasted work (e.g. duplication, handoffs)
5. Identify what are the system conditions which prevent us from doing value work (e.g. process design, IT system, training)
6. Look at the thinking behind the system conditions

Plan

This includes:

1. Identifying the value steps (against what matters to a student)
2. Identifying new operating principles and measures

Do

This involves an experiment. The team who did the check will take a small number of students out of the current system, and using the newly identified operating principles will try and test new ways of working, solving problems along the way. The experiment allows a clean flow of work to be established. More will be rolled into the experiment and tried and tested. The experiment allows us to be clear about what capacity is required for a new way of working, what resources, roles and structures. At this point decisions are made about further roll-in.

Purpose

Systems thinking requires you to define the purpose of the service in the customers own words. Here's my attempt at refining our original stab.

"Advise and support me to develop the skills and experience I need to gain graduate work or study"

Update

We've now simplified the purpose to:

"Help me get the graduate work or further study that I want" 

Quick reflections on yesterday's system's thinking conference

This is one of those 'notes to self' posts rather than something for the benefit of anyone else (although comments still very welcome). I really need to start to organise my thoughts more on systems thinking and I'd also like to get back into the blogging habit. So here are my quick reflections on the University of Leicester's Why systems thinking conference that took place yesterday, particularly in relation to what we need to in the Career Development Service.

• We need to pull in systems thinking expertise (there are now two members of staff in Corporate Service whose roll is to act as internal consultants).
• I think that our system is more complicated than the case studies I heard about in one of the sessions on distance learning (though I may be wrong). The case study involved a team of less than two FTEs, they were able to pull in a eight people for the initial 'check' stage over a six week period, and the flow seemed relatively simple (I enquire, I apply, I pay, I study, I graduate).
• As a Service we need to devote more time to this (demand analysis in the hub has been running now since the end of November last year and is now begin recorded and categorised routinely). The next stages, I think, are to review the demand on a regular basis and also to establish what our 'flow' is.
• We also need to re-establish our purpose in the customers own words and more precisely. Perhaps: "work with me to gain the advice, experience, skills and opportunities I need to gain a graduate job or graduate study" (something like that).
• Resolve how employers and staff fit into the system.
• Also need to figure out how to capture demand at all points of transaction, not just the hub (Unitemps, TARGETconnect, individual staff etc.).
• Need regular and cumulative reviews of demand in order to identify what  is normal variation in the system and what are the genuine peaks that need addressing (need to be careful not to just tamper with the system).

And if we can do all that we'll be laughing! I think I might second myself to the project. And I really must finish reading that book!