Reduce information friction without creating a new burden
See this course’s project requirements
A paper task-observation study separating frequency, duration, force/posture cues and access constraints, with a low-risk process-change comparison and supervisor questions.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Save task-demand observation record and review questions; include the original-case decision evidence and a separate changed-case result.
- Save exposure comparison without asserting safety benefit; include the original-case decision evidence and a separate changed-case result.
- Save annotated layout proposal with fit/access review needs; include the original-case decision evidence and a separate changed-case result.
- Save information-layout mock up and verification checklist; include the original-case decision evidence and a separate changed-case result.
- Save small trial review with additional fit/condition questions; include the original-case decision evidence and a separate changed-case result.
- Save ergonomic friction packet with bounded implementation brief; include the original-case decision evidence and a separate changed-case result.
Review and revise
Use these criteria to check your work and choose what to improve.
- The final packet uses the supplied task-specific constraints and all six records agree.
- Every result can be traced to an identifier, input, calculation or stated decision rule.
- Changed-case practice updates dependent records and keeps holds or uncertainty visible.
- The packet states the learner role, authority boundary and specific next verification needed before real work.
Want more background?
The idea in everyday life
Original fictional workplace practice; paper or a local document is sufficient. The rules and records below are supplied for this exercise, not asserted universal workplace policy. Yew record cards:label codes P7/P8 look similar in small print; screen reflection reported; worker reads full unrelated history to find one current code. Paper options larger clear code/group current field/minimize unrelated display; actual contrast/accessibility testing not performed.
An ergonomic work-design review can include visual and information demands; proposed changes need accuracy checks as well as reduced unnecessary search.
Reduce information friction without creating a new burden — worked practice
An ergonomic work-design review can include visual and information demands; proposed changes need accuracy checks as well as reduced unnecessary search.
Yew record cards:label codes P7/P8 look similar in small print; screen reflection reported; worker reads full unrelated history to find one current code. Paper options larger clear code/group current field/minimize unrelated display; actual contrast/accessibility testing not performed. Use paper or a local document. Preserve the original case and make a separate changed-case record.
1. Step 1
Separate three friction types.
You should see: Similar codes/visual reflection/unnecessary information search.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
2. Step 2
Design clear paper labels without changing stable codes.
You should see: Keep P7/P8IDs; add readable labels/spacing.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
3. Step 3
Show only task-relevant current code in the mock view.
You should see: Original history retained controlled; not all public.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
4. Step 4
Save information-layout mock up and verification checklist.
You should see: Check code accuracy, readability, privacy and actual screen conditions.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
What to finish
Save information-layout mock up and verification checklist; include the original-case decision evidence and a separate changed-case result.
Watch for this
Solving readability by changing identifiers or claiming a paper layout has fixed actual screen conditions.
How can I tell I understand it?
Using the supplied identifiers, I can save information-layout mock up and verification checklist. My changed-case record names the revised condition and explains which dependent decision it changes.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Occupational task and responsibility context; the exercise policies and quantities are original fictional inputs. Page title and relevant content inspected; no interactive controls or credential process tested.
Access: Readable official page retrieved with the web reader on 2026-10-01.
Reuse: All teaching cases, data, worked steps and questions are original. Link and limited paraphrase for context; no copied source exercises.
Source & access notes · checked 2026-10-01
Public agency or educational context; no source exercises are copied and no simulated threshold is presented as an official rule. Page title and relevant content inspected; no interactive controls or credential process tested.
Access: Readable official page retrieved with the web reader on 2026-10-01.
Reuse: All teaching cases, data, worked steps and questions are original. Link and limited paraphrase for context; no copied source exercises.
Source & access notes · checked 2026-10-01
Public agency or educational context; no source exercises are copied and no simulated threshold is presented as an official rule. Page title and relevant content inspected; no interactive controls or credential process tested.
Access: Readable official page retrieved with the web reader on 2026-10-01.
Reuse: All teaching cases, data, worked steps and questions are original. Link and limited paraphrase for context; no copied source exercises.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.