MétaCan
Menu
Back to cohort
Record W2003823964 · doi:10.1002/pmj.20063

Decision Making within Distributed Project Teams: An Exploration of Formalization and Autonomy as Determinants of Success

2008· article· en· W2003823964 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

VenueProject Management Journal · 2008
Typearticle
Languageen
FieldPsychology
TopicTeam Dynamics and Performance
Canadian institutionsUniversité du Québec à MontréalPolytechnique Montréal
Fundersnot available
KeywordsAutonomyKnowledge managementProcess (computing)BusinessWork (physics)Project teamProcess managementProject managementComputer scienceEngineeringPolitical science

Abstract

fetched live from OpenAlex

Competitive advantages and access to competencies are among the most frequent motivations for developing various forms of collaborative relationships. While some firms claim to collaborate at a strategic level, as in joint ventures, others pursue collaboration at a micro level, as in projects. Collaborations at the project level involve a network of dispersed team members actively involved in common activities. This creates new challenges for effective decision making in distributed project teams, as processes are often ill adapted for facilitating collaborative work. Many researchers have studied aspects of these organizational problems. However, questions regarding team autonomy and decision-making processes remain largely underinvestigated. After reviewing the literature on key concepts related to organizational decision making, we conducted an empirical study using a quantitative approach that involved an online survey sent to project management professionals. The analysis of the data clearly indicates that success in managing distributed project teams is linked to team autonomy in conducting project activities and to formal decision-making processes. These findings also highlight the fact that a formal decision-making process is even more important for distributed teams that are highly dispersed.

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.001
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.254
Threshold uncertainty score0.456

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.001
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.053
GPT teacher head0.375
Teacher spread0.322 · 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