backtothehuman/anatomy-generative-prototyping
The Anatomy of a Generative Prototyping Session, Study 1 Anonymous authors, CHI 2027 submission. The dataset accompanies a preregistered study in which 100 non-experts completed three ten-minute prototyping tasks with Mark, a generative prototyping environment: two from a blank page, in an unfamiliar and in a familiar domain, and one on an existing prototype. Every generation is dissected into the formulation of the prompt (abstraction and specificity), the extent of the… See the full description on the dataset page: https://huggingface.co/datasets/backtothehuman/anatomy-generative-prototyping.
The Anatomy of a Generative Prototyping Session, Study 1
Anonymous authors, CHI 2027 submission. The dataset accompanies a preregistered study in which 100 non-experts completed three ten-minute prototyping tasks with Mark, a generative prototyping environment: two from a blank page, in an unfamiliar and in a familiar domain, and one on an existing prototype. Every generation is dissected into the formulation of the prompt (abstraction and specificity), the extent of the generated change (changed nodes), the verification time, and the move that followed (progression or repair).
Preregistration (anonymized view-only): https://osf.io/8wh4x/?view_only=84f9f96334d44652b9f5ddee4bbf3230
Files
The research log
One JSON object per line. type names the event (prompt_sent, generation_started, generation_terminal, preview_click, composition_started, history_rolled_back, window_blur, task_started, task_timeout, and so on), ts_server and ts_client are milliseconds from the session start, task_key is T1, T2 or T3, and payload carries the event's data. A generation is committed when its change reached the preview, aborted when the participant interrupted it, and failed when the generated source did not pass validation; after an aborted or failed attempt the preceding snapshot was restored.
Measures
- abstraction: the level of the prototype at which the prompt operates,
product,design_system,featureorcomponent, assigned by the coding pipeline. - specificity: the extent to which a request constrains its realization, from 1 (the request states an aim and leaves the change open) to 5 (the request determines the change).
- changed_nodes: the number of nodes added, removed or modified in the structural diff of the source snapshots before and after the generation.
- verification_s: seconds from the completion of the generation to the participant's first composition-related interaction, with the time the window was out of focus removed.
- repair and repair_type: whether the next move returned to the request that produced the generation, and how (
restate,refine,revert).
Anonymization
Session identifiers are the study's own pseudonyms; Prolific identifiers never entered the logs. Participant and run identifiers and absolute timestamps were removed. Age is given in five-year bands; occupation and the free-text area of expertise were dropped, and the generated T3 brief carries the domain in the words the generator chose. Prompts are the participants' own words; a scan found no e-mail addresses or URLs in them.
License and citation
CC BY 4.0. Cite the CHI 2027 submission "The Anatomy of a Generative Prototyping Session"; the reference will be completed after the review.
