Serving the body wholeheartedly today our software design

We are here to manage the current target platform, the platform's web-side effect is also slowly improving.

But the other thing that I feel most deeply is their digging to the user's demand.

This is the thought that comes after our system goes online: whether the user likes your software. It's not up to your software technology how cow B. How advanced is the architecture, but whether you have grasped their hearts.

We do an employee scoring system for a company when it comes online. Found the next few questions:

1. When users come in, they don't know what to do.

2. There is no difference between the scoring options, very easy to dazzle

3. There is no difference between the excessive and the not-too-beaten options.

4. After the score, the staff will ask you, I finished the points, and then why, this is our fault

Now look at the above several, which one is our technical matter?

No. These are definitely not technical things. Because when I found out about this. The solution to these problems is already there, and why did we not think of them at the beginning?

Plainly speaking, is not standing in the user's point of view to design software, not the user's psychological feelings into account.

This kind of system, people used once. I'm sure I'll think about it and never let me use this software again.

A software that does not have a real user. There is no vitality. The wealth created is also limited.

And this morning. Our head has given us an announcement on this goal because of the institutional requirements, we need to comment on each announcement. Lest you should say something in the future that you did not see.

And sometimes we need to do a job. is to find the person who has not made the announcement. Then see if he did as advertised. This is actually a small amount of work, so we just check it out.

< Span style= "font-size:18px" > & nbsp       Just this morning, when I saw that announcement, I accidentally found this:

< Span style= "font-size:18px" > < Span style= "font-size:18px" >                 

You see this, certainly think this is not difficult, is to make a record. But here's the problem. You don't think it's hard.

But why didn't you do it? Is it not necessary to have a record for sending notifications through announcements?

We have 2 or 3 years to use this goal. Despite the shortcomings of this goal. But this goal is really getting more and more progress. The user experience, needs to do more and more in place.

< Span style= "font-size:18px" > < Span style= "font-size:18px" >        In this regard. We should learn from it when it comes to software. We really need to think about it, maybe the user is really because of one of your function points become the loyalty of your software users, anyway I was because this morning to see this point has become the goal of the user today.

< Span style= "font-size:18px" > < Span style= "font-size:18px" >         CSDN, when can you support markdown? Do you know how many people have an urgent need for this?

Blog Park Support This, typesetting is also better than csdn, csdn really should be improved.

About Markdown is, the next article to introduce you.

Serving the body wholeheartedly today our software design