Monday, November 10, 2008

2nd Mtg 10th Nov 2pm to 6pm I-studio

ok 2nd meeting was over yesterday. the interesting things to note are abt the ppl. SY and Jas are very competent ppl and makes me feel a little inferior. It will be fun to work with them and flex a bit of competitive muscle

 Project highlights : Sponsor DOD, Agent :DDOR. project will run from nov to Mar. Project agenda and approach was give out yesterday. After the meeting, the sense is that this could just be a lip service project to satisfy a quickwin from SQA.

 meaning...PS21 has highlighted this before as an area where staff engagement can be done. PS21 view is that this is not a KEY driver of doing staff engagement but OE, in search of SQA AFIs have picked up this cause and running this project.

 so....we are not exactly sure of what is the scope, but the sponsor is not a 'big fish' in the ranks of minister or PS. hence, that could limit our scope termendously. 

 But now we have 2 tasks....first is to do the data consolidation from past surverys, and the 2nd is to gather stories from HQ officers. we need to capture as much verbatim notes as possible, might need to use a recorder for this. jacelyn will come out w the draft of letter. SY thinks the purpose of this is to get the team to 'feel' for the pain of the officers when the stories come out

 my targets would then be yee yun SPPD and maybe some of the soccer players that i will be meeting 

some of things discussed during the meetings were

a) middle management and the way they operate could be a reason for inefficency. then how do we tell that to them

b) we shd try to get something that is bite-sized and a quickwin. some solutions that we have no answers can just be highlighted. but most of the solutions we scope out for shd be a quickwin with concrete actions

c) there was some debate when we set out the objective as across divisions. interpretation 1 : that across divisions meant a process that runs across 2 or more divisions that cause inefficiency.
interpretation 2 : replicated within a division, but repeated in other divisions. project team felt it was better to leave it fuzzy for now, then when we have more information, scope it accordingly.

there is a sense that this project is massive and out of our league. but since we have to do it, and likely take over the next part of solutioning, then we have to do our best. good scoping will help a lot. knowing where are the limits of yur influence.