Attitudes toward logic errors in products


After installing MS Office 12 (marketing name is Office 2007) for the first time, the first thing that stood out to me was that the text was marked with a paragraph mark.

In both the July 2005 build version and the October 7 build pre-release version, the default display of the editor was to display a paragraph. Paragraph marks appear in all editors of the body of Word as well as mail, tasks, and schedules in Outlook.

outlook 2007 mail

If you click the File menu in the preferences, there is a button where you can click options. In the case of Word 12, it is called Word Option, and if you click the File menu of Outlook mail, contacts, or calendar, it says Editor Option.

To hide the paragraph mark in the text, click View in the left menu and uncheck the Paragraph Mark in the right panel.

However, there is a strange phenomenon because it is still in pre-beta.

If you click View in the Application Setting window that appears after clicking the Outlook option, Mail, and Task Editor Option, the Paragraph Mark part is disabled, so you cannot select it.

However, you can select it by clicking the Editor Option of the calendar and contacts in Outlook.

Also, if you uncheck Paragraph Mark in Editor Option of Calendar or Contacts in Outlook, the paragraph mark will not be visible in Word.
However, on the contrary, if you check or uncheck the Application Setting window entered through Word Option of Word, only Word is affected, and Outlook is not affected.

I'm sorry

When you see this article, the product team may think, “There is no error” or “It is because it hasn’t been opened yet” and “What can I fix?” However, the user thinks like this, saying, “I’m glad~” like me.

This does not give an execution error, but it is a logical error. So it is clearly an error and a bug.

Yahoo! When usability testing the finished product there, the participant muttered a bit strangely while performing the task, but we didn't know why. Suddenly, the programmer in the observation room gave a serious expression and clicked the keyboard. I asked what he was doing, and when he clicked on a category, he said that the data was a bit strange. In the end, I searched the program source on the spot and found that the algorithm was wrong.

Although the participant did not see the error page, a logical error occurred. Other planners, researchers, and visual designers were observing the participant's actions while following them, and the programmer was thinking in his head that the program rotates whenever the participant clicked, and he was also checking the data.

If the programmer didn't talk about it, I had to find out through the participants' think-ahead or post-interview, but thanks to the programmer, I was able to find out the reason quickly. Although finding bugs is not the purpose of usability testing, it is often possible to find systematic errors or logical errors during usability testing.

That programmer, whom I nicknamed bachelor there (now doing other things), was head-headed right in the observation room. (Actually, I just pretended to hit my head against the wall)

Office 12 is not open to the public and is for beta testers, so it is a pre-beta that is distributed to related companies.

While dealing with the same phenomenon, he said, “Oh, that’s right. It seems that the integrated design between various applications is still insufficient.” "I'm still thinking about it", "It's a bug, I'll have to fix it soon," and I think we should take it seriously.

 







Recommendations





0 If you like the article, please click the heart~ It will be a strength to bloggers (SNS/login/advertising is not related)



Articles you might like







108 times Jeoldong-jeom-jeom-jeom site
4.9
108 times counter that automatically recognizes and counts by voice












Add a Comment

Email addresses are not disclosed. Required items *is indicated by

























This posting is part of Coupang Partners' activities, and a certain amount of commission is provided accordingly.