First and Foremost contd..

Imagine a process where a third party provides you the data, a function in the native system process those and display the details. As a matter of fact, user does not have a much of a saying to the three parts mentioned. So how are we going to establish the confidence ?

Since we have designed it, we dictate the users to accept the result as valid and trust worthy. As long as IT says and takes the responsibility and be in sight, users will wok on it. But they have not taken the responsibility and whole process will be a cat and mouse race.

Instead, we improve the visibility, users see what is been uploaded, and what are the output of the process. Any error in the will be pointed out by user, even though will be little embarrassing for the IT, yet users are tempted to get the ownership of the process and be leads.

Rather than, hiding the details we have opened them up, so that the system will be a users' and not of IT.

First and foremost

The first and foremost step when it comes to interface design, is the confidence building. it is the confidence that users' affection is decided upon. Systems are designed to execute a process where a user intended to do so. Connection with the system grows if the user has the confidence in the system, that as the end result, anticipated result is achieved.
Confidence is improved on two aspects.
1. Extended usage and time proven
2. Transparency

Clearly the first one takes time and current context does not give you that much of a flexibility. So we are left with the second option, transparency.
How we are going to improve the transparency ? Better way to answer and realize the question, is to understand why transparency matter when comes to building the user confidence. Now let us see that shall we ?

Begining ....!

I was not sure about anything, when i have started my career as a developer in 2005. After spending 5 years of my life, I have started to like, somethings about Software engineering. What caught my attention was system design and its applicability and capability to adopt and change a system which users are made to fall in love with.

Systems should be with users, not with developers. Since developers have to create systems for users, it is developers has to leap forward and design systems for users, so that systems will last long to serve.

This is an effort to share thoughts and ideas from my side, for better and improved system designing, more like human interface design.