The proper PROPER

Note:  This entry has to be read alongside my July 12, 2011 entry.

The D-Day made its second debut today, August 22, 2011.  A lot of effort was put in to really improve PROPER.  This time around, we let the system do the info extraction and have it tabulated for easy viewing, maximising the system's computing ability, and making report presentation a breeze.  This called for a sub-module development - the 'reporting module'.

The earlier PROPER version gave rise to much confusion where there was need to 'click' back and forth or go deeper for information that needed deliberation.  It must be reminded that not everybody, especially in the management, is computer savvy. As it normally is, IT competence goes in inverse relationship with one's position in the organisational hirarchy.  The higher one is in the management, the less computer proficient one is, especially when dealing with systems.  It's easy to be confused, to have the frustration and anger short-circuited putting the whole process in complete disarray.  I can testify to that, as it happened in PROPER's earlier debut on July 11, 2011. I am not particularly proud of that incident, to mention the least.

Our team in the corporate planning and system management got to work immediately after our last debacle.  I must remind all that we had a wash-down from the management for what happened on July 11.  Undeterred and realising the system's short coming, we got to work with gusto.  We mapped out how the M&E is to be approached and the critical info needed to be displayed.  We brainstormed and held discussions after discussions with the system developers.  We tabled dummies to our R&D and Operational Managers' approval.  Satisfied with the alpha tests, we called in the centre directors for workshops.  For best impact, we negotiated the KPIs for the year and have their project leaders submitting their project information and progress achieved to date to the system.  With the system shell filled, we test run the M&E process.  Satisfied, we held a pre-council with the management for a final run before attempting the real M&E.

The show was set and we are more than prepared.

We set the corporate M&E exercise to a two-day session (Aug 22-23, 2011).  Things could never be smoother.  We completed the job scheduled for the two days within a day.  Everybody played their part and the system held through.  We had the normal comments, points in need of clarifications and things to justify/rejustify.  But what matters most is that the system did what it is supposed to do.  The team salute the system developers for translating our needs well. My heartfelt thanks goes to L, Umi, Jariah, Faizah, Ros, Zul, Farah, Chong.....

PROPER will no doubt be further improved as we refine our needs.  As it is, there is already talks about integrating it with other in-house systems.

Guys, let's rewrite our limits and reach for the sky!!!