MétaCan
Menu
Back to cohort
Record W2029170202 · doi:10.1177/0170840614525321

Organizational Ingenuity: Concept, Processes and Strategies

2014· article· en· W2029170202 on OpenAlex
Joseph Lampel, Benson Honig, Israel Drori

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

VenueOrganization Studies · 2014
Typearticle
Languageen
FieldPsychology
TopicCreativity in Education and Neuroscience
Canadian institutionsMcMaster University
Fundersnot available
KeywordsIngenuityProcess (computing)Context (archaeology)Computer scienceConstraint (computer-aided design)Face (sociological concept)Creative problem-solvingResource (disambiguation)Management scienceCreativityKnowledge managementSociologyEpistemologyEconomicsPolitical scienceMathematicsSocial scienceLaw

Abstract

fetched live from OpenAlex

In this introduction to the special issue we explore the main features of ‘organizational ingenuity’, defined as ‘the ability to create innovative solutions within structural constraints using limited resources and imaginative problem solving’. We begin by looking at the changing views of the importance of ingenuity for economic and social development. We next analyse the nature of ingenious solutions. This is followed by a discussion of structural, resource and temporal constraints that face problem solvers. We next turn our attention to creative problem solving under constraints. We contrast ‘induced’ and ‘autonomous’ problem solving. The first arises when external stakeholders or top managers impose tasks that define problems for the individuals and groups that must solve them; the second arises when these individuals and groups recognize and define the problems for themselves. We argue that in both induced and autonomous problem solving, individuals and groups that wish to act creatively confront two types of constraint. The first are ‘product constraints’ that define the features and functionalities that are necessary for a successful solution. The second are ‘process constraints’ that stand in the way of creative problem solving in a given organizational context. We argue that both types of constraints can lead to organizational ingenuity, but that dealing with process constraints is crucial for organizational ingenuity, and hence for sustaining organizational ingenuity more generally. We provide an overview summary of the articles in the special issue, and conclude with suggestions for future research.

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.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.538
Threshold uncertainty score0.510

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
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.041
GPT teacher head0.362
Teacher spread0.321 · 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