Skip to content

Post-Integration Contribution Review

Review ritual — instantiates Net-Additive Contribution Intake

A scheduled look-back that compares a contribution's promised value against what it actually delivered — hidden coordination cost, work displaced, upkeep incurred — and feeds the verdict back into intake criteria.

Every intake decision is a forecast, and forecasts are only as good as the systems that check them. Post-Integration Contribution Review is the scheduled look-back that closes the loop: some months after a contribution has been accepted and integrated, it asks the question the intake gate could only guess at — did this actually add net value, once all the costs came in? It compares what was promised against what was realized: the hidden coordination cost that only appeared in operation, the primary work quietly displaced to keep the contribution alive, the maintenance burden it created, and how the contributor experience actually went. Its defining orientation is backward and systemic: unlike the forward-looking review that scores an offer at the door, this one measures a contribution already in the system, and its real output is not a verdict on one contribution but a correction to the intake criteria that let it in.

Example

A small nonprofit accepted a pro-bono website from a volunteer developer — a five-figure gift on paper, a modern site to replace a creaky one. A year on, the post-integration review compares the promise to the reality. The site is genuinely nicer. But the volunteer moved on the week after launch; the content system is bespoke and undocumented; and two staff now lose several hours a month wrestling updates a normal platform would have made trivial. Netted out, the "gift" is running at a slow loss — real primary-work hours displaced into fighting a system no one on staff can fully maintain.

The review's value isn't just this reckoning; it's what it changes. The finding feeds straight back to the entry channel: the intake criteria for donated software gain two new hard requirements — a maintainable, standard stack, and a named internal maintainer committed before acceptance. The next pro-bono offer is screened against a rule the organization only learned by living through this one. That is the review working: a single accepted contribution turned into a permanent upgrade of the gate.

How it works

  • Look back after integration, not at the door. The review runs once the contribution has been live long enough for its real costs to surface — the maintenance, the drift, the displacement that no up-front estimate could see.
  • Compare promised vs. realized. It sets the original value case against what actually happened, so the gap between forecast and outcome becomes visible and learnable rather than quietly absorbed.
  • Name the displacement. It specifically surfaces the primary work that was given up to keep the contribution running — the cost most likely to hide, because it shows up in other people's slipped priorities rather than on any invoice.
  • Feed the gate, not just the file. Its findings are routed back to the intake criteria as concrete changes — new requirements, new exclusions, new sponsor conditions — so the system's next decisions improve.

Tuning parameters

  • Review lag — how long after integration the look-back runs. Too soon and the real maintenance and displacement costs haven't surfaced; too late and the lesson arrives after several more offers were waved through on the old criteria.
  • Scope of accounting — how fully hidden and displacement costs are chased. Thorough accounting catches the true net figure but is itself coordination work; a light-touch review is cheaper but may miss the very costs it exists to find.
  • Feedback bindingness — whether findings are advisory or automatically amend the intake criteria. Binding feedback makes learning stick but risks over-correcting from a single bad case.
  • Contributor-experience weight — how much the review credits how the contributor was treated, not just the ledger. Weighting it protects the contributor base; ignoring it optimizes one contribution at the expense of future ones.

When it helps, and when it misleads

Its strength is that it is the archetype's learning organ: without it, an intake system never discovers that its forecasts were wrong and keeps admitting the same net-negative contributions on the same optimistic criteria. By naming displaced primary work and hidden upkeep — the costs invoices never show — and routing them back to the gate, it turns each integrated contribution into a correction that makes the next decision sharper.

It misleads in two opposite directions. Run as a blame exercise, it makes people defend past acceptances rather than learn from them, and it can tip into escalation of commitment[1] — pouring more resources into a contribution because so much has already been sunk, exactly when the honest reading says stop. Over-corrected, a single bad outcome hardens into an over-strict rule that bars good future contributions. The discipline that keeps it honest is to review the decision and its criteria, not the people, and to let the finding either improve the gate or trigger a clean wind-down — never to justify throwing good work after bad.

How it implements the components

Post-Integration Contribution Review realizes the feedback-and-detection components of the archetype — the ones that let intake learn from its own outcomes:

  • core_work_displacement_signal — it specifically measures the primary work that was displaced to sustain the contribution, surfacing the cost that hides in slipped priorities rather than on any bill.
  • feedback_loop_to_entry_channel — its findings are routed back to the intake criteria as concrete amendments, so a realized outcome improves the system's next decisions.

It does not score offers at the door before acceptance (Contribution Net-Value Review), test an uncertain contribution in advance (Bounded Contribution Pilot), or maintain the published request list its lessons update (Requested Contribution Menu).

References

[1] Escalation of commitment is the well-documented tendency to invest further in a failing course of action to justify resources already sunk into it. A post-integration review is where it most often strikes intake — the pull to keep pouring effort into a net-negative contribution because so much has already gone in — which is why the review must judge the criteria and the outcome, not defend the original decision. ↩