My Life With IT

I’ve done my share of IT projects for years. Throughout the years, I’ve often learnt some techniques from different teachers along the way. The different users I meet also gave me the opportunities to improvise despite being angry about the ways that things just change at their whims.

The Indecisive User

This user kept changing the requirements at every meeting. Likes to pick on things that aren’t functional. Is unable to decide if this function is more important than that function despite the impeding deadline.

Alternative: Give them the low down of the thing and confirm which are the important features to be rolled out 1st phase. Subsequent changes can be rolled out in the 2nd phase. This alternative may be time consuming but mention the word: budget in the communication tools and you’ll see miracles.

The Picky User

This user likes to pick on the colours, layout, functions, features and more. Even after massive overhaul based on the changes said, everything changes back to version 1 for the layouts, colours, functions and more.

Alternative: Backup every design for each phase and show them the demo upon the decided UAT date. Mentions keywords like user interface, budget and more. Hope for miracles.

The Forgetful User

This user likes to talk to you and forgets about it after that. Claims non-ownership even if the idea came from this user in the first place.

Alternative: Always follow up with an email listing the requirement changes and CC to the bosses who are involved. This way, you save yourself a major headache.

The Haughty User

This user has all the requirements laid out and likes to wait for you to fetch them to the UAT environment. Does not like to be delayed but will always be late for the testing. Prefers to talk to the higher authority than someone who is of a lower status.

Alternative: Send reminder emails about the date and venue. Include the test case. Let the higher authority know that you will be fetching them to the test environment. In the event the user wants the higher authority, let the higher authority know too.

The Know-it-all User

This user usually has some IT background and will instruct you how to develop, code and how the layout should look like. Sometimes, does not know what he/she wants. See The Indecisive User.

Alternative: Design a prototype and asked for more specifics as the requirements are often vague except for the programming portion.

The Want-it-all User

This user wants everything to work for the system. Likes the system to be 100% bug free. Prefers to have just 1 click and the system will do its magic. Expects the developers to be able to produce it in the shortest time possible when the requirements are not fully discussed. May be a little like The Haughty User.

Alternative: Give them the lowdown and explain that the system is unable to achieve everything if the deadline is too short to be able to fully test for 100% bug free launch. Send emails to confirm to prevent disputes. Documentations should include what the system is and isn’t able to perform.

I am not a project manager but I’ve seen mine using ways to calm down the users. There were times when I had to manage some projects on my own and recall how to handle it. While I’m not perfect, I learn them along the way.