Currently, the rota presents the daily check data as "instructions" which have "methods". The choice of language and presentation of these makes it seem like a step-by-step of what to do.
In the original example content the data was structured as:
- An introduction (a what/why for the checks in general)
- A target/purpose/goal of each area being checked
- A procedure for performing checks
With the procedure being flexible in order to guide (not instruct) staff members through areas to check (and then them identifying/discovering new and novel ways of checking those areas) through examples.
It is worth revisiting how the methodologies and examples/references are framed and presented to staff members to best suite the above purpose.
Some ideas for where investigation could occur:
- Naming/wording/general UI for reports
- Only presenting some (of what are currently referred to as) "Methods" at a time in the report submission interface (to encourage staff members to fill in the blanks / find their own ways of verifying the goal of each area)
Likely there are other areas and directions that can be taken to address this!
Currently, the rota presents the daily check data as "instructions" which have "methods". The choice of language and presentation of these makes it seem like a step-by-step of what to do.
In the original example content the data was structured as:
With the procedure being flexible in order to guide (not instruct) staff members through areas to check (and then them identifying/discovering new and novel ways of checking those areas) through examples.
It is worth revisiting how the methodologies and examples/references are framed and presented to staff members to best suite the above purpose.
Some ideas for where investigation could occur:
Likely there are other areas and directions that can be taken to address this!