The “Management-Per-Result” Approach to International Development Project Design
Bibliographic record
Abstract
Results-based management (RBM) has proved to be a valuable tool for international development project management; however, there are some inconsistencies that limit the use of RBM at the design phase to manage for results. This article presents a “management-per-result” approach to reinforcing the project design function of RBM and illustrates its application to a real-life project. Shying away from a technocratic approach, it emphasizes a “quick-and-dirty” approach and proposes an updated version of the logical framework to include success criteria and factors and very rough estimates for both project costs and benefits for targeted project results for different types of projects (infrastructure development, “process” type of project, and so forth).
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.061 | 0.036 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.006 | 0.003 |
| Science and technology studies | 0.003 | 0.013 |
| Scholarly communication | 0.013 | 0.008 |
| Open science | 0.005 | 0.006 |
| Research integrity | 0.003 | 0.004 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".