|
Getting your Trinity Audio player ready...
|
Research increasingly depends on teams, but scientific careers still depend on individuals. This creates a structural problem: funders may support a laboratory, consortium, or institution while obscuring which people actually generated the ideas, wrote the software, collected the data, solved the technical problems, or maintained the infrastructure.
The solution is not to choose between funding teams and funding individuals. Research funding should support teams operationally while preserving individual credit economically and reputationally.
A team may need a shared budget, equipment, administration, and long-term coordination. Yet the money and recognition generated by its achievements should remain divisible among identifiable contributors. Team membership alone should not determine credit, and individual work should not disappear behind the name of a principal investigator, university, consortium, or DAO.
Why Research Teams Need Collective Funding
Many scientific projects cannot be divided into isolated individual grants.
A biomedical study may require clinicians, statisticians, laboratory technicians, data managers, software developers, regulatory specialists, and principal investigators. An astronomical survey may involve hundreds or thousands of contributors. A mathematical research program may depend on several theorists, formalization specialists, software maintainers, and expository authors.
Funding only isolated individuals can create several problems:
- shared infrastructure may remain unfunded;
- researchers may optimize their work for personal visibility rather than collective value;
- technically essential supporting roles may be neglected;
- teams may spend excessive time dividing every expense among separate grants;
- no participant may have both the authority and resources to coordinate the entire project.
A team-level budget is therefore often justified. It can pay for equipment, computing, laboratory space, data collection, shared software, administration, travel, and other genuinely collective costs.
But operational unity does not imply equal contribution—or justify transferring all credit to the team’s most senior member.
The Danger of Treating the Team as a Single Contributor
When funders evaluate only the team or institution, individual contributions become difficult to observe. This can produce several distortions.
The Principal Investigator Becomes a Proxy for Everyone
Grant systems commonly identify one or several principal investigators as the responsible recipients. This may be administratively convenient, but it can create the impression that the principal investigators produced everything funded by the grant.
The work of junior researchers, technicians, research software engineers, data curators, and independent collaborators may then be treated as an input owned by the laboratory rather than as an attributable scientific contribution.
Prestigious Teams Accumulate Credit Automatically
Once a laboratory or consortium becomes famous, its reputation can influence the evaluation of every subsequent output. A researcher working inside a prestigious team may receive too much credit merely through association, while a substantial contributor outside the central institution may receive too little.
This is one expression of the Matthew effect: prior recognition increases access to future recognition and resources.
Mobility Can Destroy a Researcher’s Visible Record
A person may contribute for several years to a large project and then move to another institution before the final paper, dataset, or instrument is released. When credit is attached primarily to current team membership, earlier contributors can become nearly invisible.
Scientific credit should follow the contribution, not the contributor’s current employer.
Team-Level Funding Can Conceal Internal Inequality
A team may receive a large award while the people performing much of the substantive work remain on temporary contracts or receive little discretion over research priorities. The existence of a well-funded laboratory does not prove that its funding has been allocated fairly within the team.
Funding a team is not the same as funding every contributor to that team.
Authorship Is Too Crude to Solve the Problem
Traditional authorship cannot carry the entire burden of allocating scientific credit.
Author order has different meanings in different disciplines. In some fields, the first author is presumed to have performed most of the work. In others, authors are listed alphabetically. The last author may indicate supervision, laboratory leadership, or nothing in particular. Middle authorship can represent either a major intellectual contribution or a narrowly defined technical task.
Large collaborations make these ambiguities worse. A single paper may have hundreds or thousands of authors, while important contributors to software, data, engineering, reviewing, or project maintenance may not satisfy a journal’s authorship rules.
The CRediT Contributor Roles Taxonomy improves this situation by describing contributions through 14 roles, including conceptualization, methodology, software, data curation, formal analysis, supervision, and funding acquisition. CRediT was designed to complement conventional authorship and make the work behind a research output more explicit.
However, a role taxonomy answers only one question: what kind of work did each person perform?
It does not necessarily answer:
- how much of the work the person performed;
- how difficult or original the contribution was;
- whether the contribution was essential;
- how later researchers used it;
- how much funding or recognition it should generate.
A fair funding system therefore needs contributorship records, but it cannot stop there.
Separate the Team Budget from Individual Reward
A better model distinguishes two financial layers.
Shared Operational Funding
The first layer finances resources that must be controlled collectively:
- equipment and facilities;
- cloud computing and data storage;
- laboratory materials;
- fieldwork;
- administrative and regulatory work;
- shared personnel;
- project-wide software and infrastructure;
- coordination among institutions.
This money belongs to the project budget. It should be governed transparently, with clear spending rules and auditability.
Individual Merit-Based Funding
The second layer rewards identifiable contributors for demonstrated work and impact.
It may recognize:
- discovering or defining the central problem;
- developing a theory or method;
- proving a theorem;
- designing an experiment;
- writing or maintaining scientific software;
- producing or curating a dataset;
- detecting an error;
- replicating a result;
- writing documentation;
- performing analysis;
- coordinating a difficult collaboration;
- creating infrastructure used by other researchers.
These payments should not be determined solely by formal position, salary grade, authorship order, or proximity to the project leader.
This distinction permits a funder to say:
“The team needs $2 million to operate, but the scientific credit generated by its work remains divisible among the people who contributed.”
Credit Should Be Divisible, Multidimensional, and Revisable
Individual credit should not be treated as a binary choice between “author” and “non-author.”
As discussed in Why Scientific Recognition Should Be Divisible Rather Than Winner-Take-All, different people can deserve different shares of recognition for different types of contribution. A single percentage attached permanently to an entire project is also insufficient.
Credit should be multidimensional. One person may deserve strong credit for conceptualization, another for execution, another for software, and another for making the result usable by the wider scientific community.
Credit should also be revisable. The importance of a contribution may become clear only later.
For example:
- a dataset may become highly reused several years after publication;
- a software library may become essential infrastructure;
- a seemingly minor lemma may enable an entire research program;
- an early negative result may prevent many groups from repeating a failed approach;
- a maintainer may preserve a project long after the original investigators leave.
Immediate contribution statements should therefore be combined with later evidence of adoption, dependency, verification, and impact.
Use Contribution Graphs, Not Only Author Lists
A research output is rarely produced by a flat list of interchangeable authors. It is better represented as a graph.
The graph can connect:
- people;
- papers;
- datasets;
- software repositories;
- experiments;
- proofs;
- reviews;
- replications;
- instruments;
- definitions;
- earlier discoveries;
- downstream applications.
Edges in the graph describe relationships such as “created,” “verified,” “maintained,” “extended,” “used,” “corrected,” or “depended on.”
Such a graph can reveal contributors who disappear from conventional bibliometrics. A widely used scientific library may support hundreds of papers without its maintainers becoming co-authors. A mathematical definition may enable many later theorems. A dataset curator may make several research programs possible without receiving proportional citation credit.
The purpose of a contribution graph is not to calculate an infallible numerical score. It is to provide structured evidence that evaluators, funding mechanisms, and contributors can inspect and contest.
Do Not Let Team Leaders Allocate All Credit Unilaterally
Team leaders possess useful information about internal work, but they also have conflicts of interest.
A principal investigator may overvalue supervision, funding acquisition, or project ownership. Senior researchers may unintentionally underestimate technical work they did not personally perform. Junior researchers may hesitate to challenge inaccurate contribution records because their recommendations, contracts, or immigration status depend on senior colleagues.
Consequently, self-reported contribution claims should be treated as evidence—not as final judgment.
A credible allocation process can combine:
- contributor self-reports;
- assessments by collaborators;
- version-control and authorship histories;
- laboratory or project records;
- public artifacts;
- independent expert review;
- downstream reuse and dependency evidence;
- an appeal procedure.
No single signal should determine the result. Commit counts, for example, measure activity but not necessarily intellectual value. Citations measure some forms of attention but can miss software, maintenance, negative results, and foundational work. Peer assessments can provide context but may reproduce hierarchy and favoritism.
Team Membership Should Not Guarantee Equal Credit
Equal division is attractive because it appears simple and peaceful. But it can be unfair in both directions.
When contributions are highly unequal, equal division underpays central contributors. It may also encourage honorary membership, in which names are added because of status, institutional politics, or reciprocal arrangements.
At the same time, a purely proportional model can exaggerate minor differences and encourage constant internal competition.
The appropriate compromise is not necessarily to calculate each contribution to several decimal places. A system could use broad evidence-based ranges or categories while preserving a meaningful distinction between:
- central intellectual contributions;
- major technical or empirical contributions;
- substantial supporting work;
- limited but legitimate contributions;
- institutional or administrative association without a scientific contribution.
The objective is not perfect measurement. Perfect measurement is probably impossible. The objective is to avoid the much larger error of treating all team members as identical—or crediting only the most powerful ones.
Preserve Credit Across Institutions and Over Time
Contribution records should be portable.
Researchers should retain attribution when they:
- leave a university;
- move between countries;
- change fields;
- work independently;
- lose access to an institutional account;
- contribute before a formal consortium exists;
- contribute after the original grant ends.
Persistent researcher identifiers, public repositories, signed contribution records, and transparent project histories can help preserve this continuity.
Blockchain may be useful for timestamping claims, recording decisions, and making funding transactions auditable. It cannot determine scientific merit by itself. As explained in Blockchain Grants for Independent Researchers, transparent infrastructure can support attribution and accountability, but scientific evaluation still requires evidence, expertise, and contestable judgment.
How AI Internet-Meritocracy Could Evaluate Team Contributions
AI Internet-Meritocracy is designed to allocate funding according to publicly visible scientific and open-source contributions rather than institutional affiliation alone.
In a team-science context, AIIM should not simply evaluate the team as one indivisible entity. It can instead analyze the relation between team outputs and individual contributors.
The system could consider:
- contribution statements;
- publication and repository histories;
- software authorship and maintenance;
- dataset creation;
- formal proofs and verification;
- citations and downstream use;
- dependency relations;
- replication evidence;
- peer assessments;
- public explanations and documentation.
Human voting and appeals remain important because automated evaluation can misinterpret ambiguous records, overvalue easily measured activity, or fail to understand an unfamiliar contribution.
A defensible AIIM architecture would therefore fund on several levels:
| Funding level | Recipient | Purpose |
|---|---|---|
| Infrastructure allocation | Team or project | Shared operational resources |
| Contribution payment | Individual | Demonstrated scientific or technical work |
| Maintenance payment | Individual or subgroup | Continued support for valuable infrastructure |
| Impact adjustment | Individual or team | Later evidence of reuse or importance |
| Coordination reward | Identifiable coordinator | Genuine organizational contribution |
| Corrective allocation | Overlooked contributor | Credit restored through appeal |
This approach recognizes that coordination itself may be valuable without allowing “leadership” to absorb all the credit generated by everyone else.
Practical Rules for Fair Team Funding
A funding organization that wants to support teams without erasing individuals should adopt several basic rules.
First, every major output should include structured contribution records. Second, team overhead and individual rewards should be reported separately. Third, credit claims should be reviewable by all contributors before publication or payment. Fourth, people should be able to challenge an attribution decision without requiring permission from their supervisor. Fifth, funding systems should recognize outputs beyond papers, including software, datasets, replication, reviewing, maintenance, and infrastructure. Sixth, records should remain attached to contributors after they leave the team.
Most importantly, the system should never infer that controlling the grant means creating all the value.
Conclusion
Scientific teams need collective resources, but collective funding must not produce collective anonymity.
The team should be treated as an operational unit where shared resources and coordination are necessary. The individual should remain the unit of attributable contribution, professional reputation, and merit-based reward.
A fair funding model therefore combines:
- shared budgets for shared needs;
- structured records of individual work;
- divisible and multidimensional credit;
- evidence from outputs and dependency relations;
- portable attribution;
- independent review and appeal;
- later adjustment when long-term impact becomes visible.
The central principle is simple:
Fund the team so that collaboration is possible. Credit the individuals so that collaboration does not become appropriation.
Research funding does not have to choose between collective capacity and individual justice. A well-designed system can provide both.
Support Independent Science
Our flagship product is AI Internet-Meritocracy - an app, that unlike universities distributes money directly to researchers and open source developers, without traditional bureaucracy.
AIIM’s dependency-aware allocation model is currently being tested. Support the next testing milestone.
Supporting independent science is not only a matter of fairness to researchers whose expertise and work are often underfunded. It is also essential for addressing systemic failures in scientific publishing that delay discoveries and leave important results unnoticed. In science and software, even one missing component can prevent an entire system from working.
Help valuable research and open-source infrastructure move forward. Please make a donation to support independent scientists and free software developers.
Dislclaimer
Experimental-system notice: AI Internet-Meritocracy is an experimental funding system. Its AI-generated evaluations are heuristic judgments based on available public or connected-account evidence; they are not validated measurements of a person’s causal economic or scientific impact. The current beta uses custodial and administrative components. Decentralized governance, non-custodial wallets, and complete on-chain auditability remain under development. Evaluations may contain factual errors or biases and should be interpreted together with audit logs, appeals, human oversight, and published test results.
Ads:
| Description | Action |
|---|---|
|
A Brief History of Time
A landmark volume in science writing exploring cosmology, black holes, and the nature of the universe in accessible language. |
Check Price |
|
Astrophysics for People in a Hurry
Tyson brings the universe down to Earth clearly, with wit and charm, in chapters you can read anytime, anywhere. |
Check Price |
|
Raspberry Pi Starter Kits
Inexpensive computers designed to promote basic computer science education. Buying kits supports this ecosystem. |
View Options |
|
Free as in Freedom: Richard Stallman's Crusade
A detailed history of the free software movement, essential reading for understanding the philosophy behind open source. |
Check Price |
As an Amazon Associate I earn from qualifying purchases resulting from links on this page.

