Wednesday, April 16, 2014

Never belittle the smallest help given..

Asset was part of an Amanah I had a chance to be in charged with. Asset to me when serving the internal IT department is all equipment bought through the company's pocket to assist employee in their attempt to productivity.

An attempt as I put it is far from having a definite purpose of why it needs to be defined.

My definition of productivity at that time was ensuring all asset are in use recorded in a named repository and unused asset disposed according to the equipment disposal process.

Not only I learnt of complying to a process which cut across different department, I learn how to make it easy for other people to work with me and helping them achieve their business objectives. It's a win-win thing with no monetary benefit or appreciation award to either parties. Mission was to happily help each other.

It was made known to me that one colleague identified me as trolley girl. I kind of agree to that as a part of me proud of the experience which if recalled mostly spent with the trolley. It was my small helper but can carry huge things like 2 CRT monitors and 3 to 5 tower desktop.

We served each other an not even once I heard a complaint =) this teaches me to not belittle the small help I receive. If a non living thing deserve such admiration for its services.  What more a human being....

My brain is printing those helpful and inspiring individual names that have helped and not help but taught me life lessons...I pray Allah would honor them in barakah in age and knowledge..

Knowledge is about action too.

Standard Operating Procedure (SOP) : the myth and mistery of producing it.

Some key points that will save you the amount of money, effort, time and health doing SOP.

I share this experience as to not live the same mistake & learn to decide what is best in terms of efficiency & effectiveness. I had experience few events where standard documentation not prepared or cut off from budgeted implementation. Effects of no proper documentation is disastrous. I need to
exaggerate this as I lived to see the effects.

1. Dig out from reliable sources
2. A business type SOP or an end user guide is void of all technical jargon that you can think of
3. Cost in a capable technical writer to ensure digestable content fit for use in the real operational environment.

Reworking on deliverables that are later not used are not only a waste of effort but also resources time and productivity. Worst if the situation is pretty much hostage-like when customer sign off is pretty hard to get. Simply making it difficult or who are we kidding?

Tuesday, April 1, 2014

Of great employer...

http://blogs.hbr.org/2014/04/seven-things-great-employers-do-that-others-dont/

Monday, October 28, 2013

"Why do..Why you"..

Alhamdulillah .. a blessed day to have opportunity listening to unselfish sharing from another of my influencer....

Lots of topics discussed given a span of a year to our last conversation over lunch..this time it was after Maghrib..

I was attracted to the following .. the answer to "Why do, Why you?" is PASSION...
a frequently misuse or misunderstood ...

This passion comes from knowing the true purpose no matter if you are being talked out of it. Do your best and leave Allah the rest.. :)

Friday, October 25, 2013

LINKEDIN article

https://www.linkedin.com/today/post/article/20131025184720-30084557-following-your-gut-when-people-think-you-re-crazy?_mSplash=1

Monday, October 21, 2013

Service Delivery Management vs Project Management (as I see it)

The difference between the two in terms of technical deliverables and approach are different.

Attitude towards each roles varies considering:
1. Money
2. Timeline
3. People strength
4. Technical competency
5. Contractual obligation
6. Customer engagement throughout completion
7. Team work

All deserve to be explained in detail from the experience I have. Some other time perhaps ..

Monday, October 14, 2013

Reminders will only benefit the believer .

Life lesson
1. Customer complaint.
2. Leaders lacking in effective communication.
3. Subordinates estranged from mission & purpose.
4. Failure to uninterrupted service due to ineffective succession plan.

To move forward:
1. Acknowledge issue and risk.
2. Timeline to resolution.
3. Identify service coverage.
4. Identify key project member.
5. Establish plan and team activity.
6. Conduct checkpoint discussion.
7. Organization engagement.
8. Project effectiveness assessment.

Key success factor:
1. Project steering team members with diverse skill background.
2. Commitment to project completion.
3. Trust in one another.
4. Abide by timeline in producing result.
5. Focus on quick wins