MétaCan
Menu
Back to cohort
Record W2088401202 · doi:10.1080/15710880412331289926

Patterns of interaction in construction team meetings

2004· article· en· W2088401202 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.

fundA Canadian funder is recorded on the work.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueCoDesign · 2004
Typearticle
Languageen
FieldPsychology
TopicTeam Dynamics and Performance
Canadian institutionsnot available
FundersMcGill University
KeywordsKnowledge managementComputer scienceHuman–computer interactionProcess managementSociologyPublic relationsEngineeringPolitical science

Abstract

fetched live from OpenAlex

noted its confrontational and adversarial nature. Both the original report and its subsequent endorsement in Accelerating Change (Strategic Forum 2002) called for improved working relationships—so-called ‘integration’—within and between both design and construction aspects. In this paper, we report on our observations of on-site team meetings for a major UK project during its construction phase. We attended a series of team meetings and recorded the patterns of verbal interaction that took place within them. In reporting our findings, we have deliberately used a graphical method for presenting the results, in the expectation that this will make them more readily accessible to designers. Our diagrams of these interaction patterns have already proved to be intuitively and quickly understood, and have generated interest and discussion among both those we observed and others who have seen them. We noted that different patterns of communication occurred in different types of meetings. Specifically, in the problem-solving meeting, there was a richness of interaction that was largely missing from progress meetings and technical meetings. Teammembers expressed greater satisfaction with this problem-solving meeting where these enriched exchanges took place. By making comparisons between the different patterns, we are also able to explore functional roles and their interactions. From this and other published evidence, we conclude that good teamworking practices depend on a complex interplay of relations and dependencies embedded within the team.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.125
Threshold uncertainty score0.215

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.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.021
GPT teacher head0.301
Teacher spread0.280 · 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