Librarian Joss sets a printout on the lab table. "The builder ran SH-1 for one demo week in another school's library. Here is every request."
Comet skims it. "Thirty requests. I bet most of them were Check. Students love being told they are right."
Wren clicks his pen. "What does the evidence say? Let's tally before we decide."
Nova draws an empty bar graph on the wall with three bars waiting to grow. "Would you like a hint?" she asks. "Count one day at a time, then add the days."
Comet writes her guess in the corner of her notebook and circles it.
Wren hands you the printout. "Reviewer, you count. We will check."
USE-30 is the builder's list of 30 SH-1 requests from one demo week. It is a made-up example.
You will tally the requests by feature, then by kind of task. Then you will design two changes that make less new text.
Everything you need is on this page. You need no device.
USE-30, the demo-week requests (made up for the story). Each day had six requests.
| Day | Request 1 | Request 2 | Request 3 | Request 4 | Request 5 | Request 6 |
|---|---|---|---|---|---|---|
| Monday | Ask | Check | Ask | Quiz | Ask | Check |
| Tuesday | Ask | Ask | Check | Ask | Quiz | Check |
| Wednesday | Quiz | Ask | Check | Ask | Check | Ask |
| Thursday | Ask | Check | Quiz | Ask | Check | Quiz |
| Friday | Check | Ask | Ask | Quiz | Check | Ask |
The crew wants SH-1 to make less new text without hurting students.
Here are two ideas they wrote. A quiz bank: teachers keep the quizzes they have already checked, and students reuse them.
A paper option: every task can also be done on paper, so nobody has to use SH-1 for practice.
Your job is to design one more change of your own.
Excellent counting, reviewer. Tomorrow the crew traces everything SH-1 is built from.