ponzi's avatar
ponzi

Jan. 10, 2022

0
Cognitive friction in designing

Main focus when designing to avoid cognitive friction will be to understand my users and how they behave in order to finish some task. I would separate this process into 2 steps:

Before development: It’s really helpful to have user interviews with potential users, create early prototypes and test them as soon as possible. Create IA nad user flows.

During development: Test every iteration with users and iterate.

Corrections (1)
Correction Settings
Choose how corrections are organized

Only show inserted text
Word-level diffs are planned for a future update.

I would separate this process into 2 steps:


Cognitive friction in designing


Main focus when designing to avoid cognitive friction will be to understand my users and how they behave in order to finish some task.


My main focus when designing to avoid cognitive friction will be to understand my users and how they behave in order to finish some task. My main focus when designing to avoid cognitive friction will be to understand my users and how they behave in order to finish some task.

Also, stylistically, I think it would be more natural to say "...in order to complete a given task" instead of "in order to finish some task".

Before development: It’s really helpful to have user interviews with potential users, create early prototypes and test them as soon as possible.


Create IA nad user flows.


Create IA nand user flows. Create IA and user flows.

During development: Test every iteration with users and iterate.


During development: Test every iteration with users and iterate. During development: Test every iteration with users.

"and iterate" is redundant because you already said "test every iteration". Also, "repeat" is a more common word than "iterate" here, so if I hadn't removed "and iterate", I would have changed it to "and repeat".

You need LangCorrect Premium to access this feature.

Go Premium