Presentation on theme: "CSU Work Process Improvement (WPI) 2006 A balancing act to survive Understand what we need to do Promote what we do & our outputs Do Stuff / Get."— Presentation transcript:
CSU Work Process Improvement (WPI)
2006 A balancing act to survive Understand what we need to do Promote what we do & our outputs Do Stuff / Get results
Enterprises are complicated and complex Everyone has a different view / perspective / window / frame / ref point How does it ever move ahead ? Should we simply accept that it does? We need something to talk at – a constant
People Committees Events Locations Data Procedures Systems Initiatives Risk Projects Easy wins Regulations Working Parties Rules Stakeholders Hot Spots Strengths Weaknesses Goals Roles Pain Points Strategy Organisational Overlays?
Organisational Constants? Organisation Who Location Where Rules, Controls, Strategy Why Events When Things (assets, programs, subjects, …) What Process How
Why Process? Apps are implementation of process Process is the hub … Map process to data, initiatives, org units, systems, goals, … > get good results We’re using process in enterprise modelling - loosely based on Holcman
This goal impacts on these orgs These orgs are working on these goals These orgs use the same data This data is important to X orgs This org has these systems These orgs have no systems These systems are used by This goal has no data about it This data is impacted by these goals This system helps with X goals These goals impact on these systems This goal has no system These systems use the same piece of data These orgs do these processes These are common processes done by many orgs This goal impacts on these processes These processes do nothing towards goal This process needs this data These processes need same data Data collected no-one cares about The same process uses diff systems This system can do these processes This process is not supported by a system
People Committees Events Locations Data Procedures Systems Initiatives Risk Projects Easy wins Key Dates Regulations Working Parties Rules Stakeholders Hot Spots Strengths Weaknesses Goals Roles Pain Points Strategy Inductions PROCESS
CSU Process Model Preliminary Conceptual Independent Primitive Stable Integrative Useful
Overlay Project bids for 2006
Overlay Approved 2006 projects
Overlay The List???
Provide Services Support customers of those services Provide advice and strategy to CSU wrt their speciality FM, SS, IT (all enablers)
But what are the processes? And how good are they in the first place?
Method Determining and analysing stakeholders and process - loosely based on Burlton Collection by org unit (not ideal) Some reverse engineering of stakeholders
Burlton in 7 lines Consider your strategy Understand your stakeholders in that context Est interactions > core & enabling processes Using your strategy and the above Determine which process has the most pain Determine which process has the most impact (gain) Map Pain vs Gain > To get initiatives & priorities
NB This is the initiatives and priorities that process is informing you about You then need to consider this with all the other things that EA has thrown up – eg data, technology, roles, … Add them to “The List” – you are finding solutions to deep root causes and issues that need to be prioritised
WPI Mid 2005 Business Process Improvement Worked with OD – “please let us help” Became a project with CSU wide steering committee and a DVC Sponsor
What are the key interactions between the Faculty/Division and internal and external stakeholders ? How effective are Core processes in managing those interactions ? What contribution do enabling processes make and how effective are they ?
Project Resources Concepts & Kick Off –Contracted process analyst, DB and Org Devel P/T for 4-6 months Collection & Analysis –Contracted PM / lead process analyst –Contract BA –Internal trainee BA –P/T admin support –Est months
Work Products Stakeholder models / Interaction tables Process models (core, enabling, planning, governing) Core process health checks Issues ID and narratives Contributor matrices Process profiles / EA data collection Org unit summary reports
Issues Delays in getting access to senior staff in sectional areas. Competing strategic and tactical initiatives has drawn on peoples time (The List!!!) Workshop logistics – multi-campus etc
Issues Expectation mgmt –Collect process and leaving them with own initiatives –It’s not about procedures Independence from Org structure Keeping momentum going over 12 months Conversion into the Enterprise Model
Process Organisation Owner Expert Stakeholder Goals Risk Services Issues Data Initiatives Controls Systems Events
Spin Offs – Interim Report “Process reviews generating improved understanding within org unit as to internal and cross org processes” “Some org units are undertaking quick wins triggered by workshop engagements” “Growing appreciation that process improvement efforts should consider impacts across the org”
Spin Offs The patterns Services > Central help > Service Cat Strategic Plan Invites to other units for reviews / advice Application sharing Application Portfolio
Tips Use skilled facilitators – someone who knows process, done it, communicator Do your homework Prepare straw models Start with the advocates Make the connections to EA all the time It’s not about BPEL/SOA/… for ages