Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to evaluate empirically: student critiques #31

Open
amyjko opened this issue Feb 12, 2018 · 0 comments
Open

How to evaluate empirically: student critiques #31

amyjko opened this issue Feb 12, 2018 · 0 comments
Assignees

Comments

@amyjko
Copy link
Owner

amyjko commented Feb 12, 2018

This might depend on the reading style of the reader, but I think that if there was a bullet list in the beginning that provided quick definitions of the 3 methods, it would add to the clarity of the article. To me, it was difficult to see how the title of "how to evaluate empirically" was connected with the 3 different methods. It wasn't clear until after I reread the introduction a few times that evaluating empirically refers to testing/observing a design in a real-life situation.
Break it down into smaller paragraphs! For an article like this, breaking the content down into maybe just 3 sentence chunks really helps get the point across--almost like writing in blog-style. For example, breaking apart the "Technology Probes and Experience Sampling" paragraph at "It's also possible to use experience sampling…". Also, adding a paragraph break before "Note that a 'representative user' is….". Overall this will break down the content better and also make it less visually overwhelming at first glance.
Use more numbered lists and bullet points! I think the core content is overall a lot of steps/requirements that would work very well in list form. For example, the steps to running a usability test could be broken down in this format:

@amyjko amyjko self-assigned this Feb 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant