This is a description of the application itself: what it does, what a break is
actually like, how much of it a person can change, and how it decides when not to
interrupt somebody. It describes rather than sells, because the people
who ask for it are usually assessing the software rather than choosing it.
It is written for occupational health teams, DSE assessors, professional bodies and
researchers, and it is meant to be forwarded and filed without anybody having to edit
it first.
What is in it
- Why break reminders get switched offThe failure these products
actually have. Not that the advice is wrong, but that a reminder lands during a client
call and the software is uninstalled within a fortnight.
- What it doesHow the application behaves alongside everything else on
screen: tracking working time, signalling a break, guiding it, and returning to the
background.
- The break experienceWhat the twenty seconds are like, and why the
break screen asks for one thing and then stops.
- Powerful underneath, legible on the surfaceWhy the machinery is
visible to the person using it. Software that pauses for reasons it will not explain
is not helpful.
- User controlWhat a person can change, and the fact that the defaults
are a starting point rather than a policy. Usually the section that matters most to an
assessor.
- Setting it upThe four questions at first run, and why the presets
exist for people who do not want to configure anything.
- How the pausing actually worksThe four conditions that hold a
reminder back, each one's awkward case, and the position the design takes on
it.
- Evidence and positioningWhat the 20-20-20 rule is supported by, and
what this document deliberately does not claim.
- Try itHow to install it, from the Microsoft Store or directly. It
runs offline and needs no account.
If you are looking at this for an organisation
This document covers the application. Central licensing, silent deployment,
configuration your people cannot override, and the reporting question are a separate
document: the workplace overview, which is written for
employers and for the security review that follows.
There is also a security and IT reference, a single page
written to be forwarded to whoever manages your endpoints.
Anything this does not answer goes to
hello@20-20-20-vision.com.
If you are assessing the software for a workplace, say so and we will send the workplace
material with it.