MétaCan
Menu
Back to cohort
Record W3011508484 · doi:10.1145/3380961

Countdown Timer Speed

2020· article· en· W3011508484 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueACM Transactions on Computer-Human Interaction · 2020
Typearticle
Languageen
FieldDecision Sciences
TopicPersonal Information Management and User Behavior
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsCountdownTask (project management)RecallAffect (linguistics)PerceptionComputer sciencePsychologyPaceCognitive psychologyHuman–computer interactionCommunicationEngineering

Abstract

fetched live from OpenAlex

We face delays in a variety of situations. They are either inevitable, e.g., due to system limits, or are intentionally added, e.g., advertisements. In many situations, a visual feedback is provided during the delay to manage expectations. This feedback is usually provided through progress bars, percentages, or countdowns, depending on design limitations such as screen size. In this article, we use 15-second delays and examine (a) how delays affect users’ decision-making and task satisfaction, and (b) how to manipulate time perception to reduce the negative consequences of delays. Experiment 1 ( N =421) shows that faster countdowns increase task satisfaction and lead to more rational decisions in the subsequent task. In Experiment 2, we investigate the effect of countdown speed on delay perception and recall ( N =531). We show that faster countdowns lead to shorter perceived delays, while the delay will be recalled as longer after the task. The opposite is obtained for slower countdowns. We also increased the countdown rate and found a limit for the effect of increased speed. Thus, designers have to trade-off between how delays are perceived at the moment of experience and how they are recalled. We discuss the implications of these findings for user interface design.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.775
Threshold uncertainty score0.995

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0010.002
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0070.005

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.354
GPT teacher head0.449
Teacher spread0.095 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it