Summary

  • Laura Kaplan’s public record at LACNIC connects several forms of development work that are often treated separately. Her documented remit covers technical-community development, events, training platforms, policy participation, FRIDA, FORT Validator, mentoring, cooperation and research projects. In the most detailed example, Ayitic Goes Global, Kaplan’s own recorded explanations joined a funding process and digital-skills goals to a recognition that local Internet infrastructure also had to be addressed. Later records show the same operating instinct in different settings: identify a participation barrier, propose a mechanism that can be assigned to institutions and communities, and place the result inside a formal decision or evaluation process. LACNIC’s current staff biography supports the scope of the role, while the dated program and governance records establish the specific interventions.

  • The evidence also sets firm limits. Kaplan did not act alone in Ayitic, did not personally produce its measured results, and did not single-handedly write LACNIC’s Community Code of Conduct. The first Ayitic cohort’s reported 86 percent graduation rate applies only to that cohort, and the independent assessment’s figure of 316 female youth trained is not an employment-placement count. The Board’s approval of Kaplan’s Technical Forum redesign proves a governance decision, not a later improvement in submissions or event quality. The strongest account is therefore neither a hero narrative nor a list of programs. It is an analysis of institutional cooperation in which Kaplan’s attributable work is visible while partnership delivery, community authorship, board authority and unresolved outcomes remain explicit. The UN IGF session record, the independent Ayitic assessment and LACNIC’s approved Board minutes preserve those distinctions.

The mandate is a portfolio, not a personal ownership claim

LACNIC’s current professional materials say that Kaplan has been part of its staff since 2012 and leads the Development and Cooperation function. The organization’s directory labels the position CDCO, or Chief Development and Cooperation Officer, while its biography uses Manager of Development and Cooperation. That variation makes function-based wording more precise than turning either title into a broader corporate claim. The same biography assigns her a wide institutional remit: development of the regional technical community; two annual events; the CAMPUS and Technical Training Center; the Policy Development Process; FRIDA; FORT Validator; mentoring; and cooperation and research projects. These are responsibilities within an organization, not evidence that she founded, owns or personally delivers every item in the portfolio. LACNIC’s staff biography is the appropriate basis for both the scope and the limit.

The breadth matters because it reveals the kind of work placed under “development and cooperation.” Training is present, but so are funding, mentoring, event design, policy participation and research. A narrow reading would treat those as unrelated programs that happen to report through one function. Kaplan’s dated record supports a more useful interpretation: the function works on the conditions under which people and institutions can participate. Sometimes the immediate condition is access to technical skills. Sometimes it is infrastructure.

Sometimes it is the design of a committee, the path for a complaint, or the ability of strategic decision-makers to engage a technical transition.

That interpretation remains an analysis of the documented portfolio, not a claim that one master plan governed every activity. The public materials do not establish that Kaplan originated each program, controlled every implementation choice or determined every outcome. They do establish a continuing role broad enough to connect program design with the mechanisms through which regional cooperation is carried out. The distinction is central: a portfolio can make a leader accountable for coordination and design without transferring collective ownership to that individual.

Cooperation as connected operating work

The clearest pattern in Kaplan’s record begins with a constraint rather than a slogan. In the Ayitic material, the constraint included skills and infrastructure. In the Technical Forum record, it was a committee structure described as rigid, insufficiently broad and marked by low election participation. In the Community Code process, it was the need for a workable complaint path and coverage of virtual spaces without creating an unnecessarily complex separate rule for a mailing list. These are different fields, but each record moves from a stated participation problem toward an operating mechanism.

The second part of the pattern is assignment. A cooperation mechanism has to locate work among actors that can perform it. In Ayitic, LACNIC worked with IDRC and local or regional partners; Kaplan described an infrastructure component and the development of networking and cybersecurity courses. In the code process, a community working group developed recommendations, Kaplan presented them, and the Board retained approval authority. In the forum redesign, Kaplan proposed a structural change and the Board decided on it. None of those arrangements erases individual contribution.

They make the contribution legible by showing where it entered a collective process.

The third part is a bounded result. A funding request can be documented without calling it a grant approval. A Board vote can be reported without claiming that it later improved an event. A graduation rate can be reported without turning it into employment. This discipline is not merely defensive. It is how a repeatable cooperation system can learn: decisions, responsibilities, outputs and longer-term outcomes must remain separate enough to be examined. The public record around Kaplan is strongest precisely where it preserves those separations.

Ayitic began with a funding and design sequence

The Ayitic chain did not appear in the record as an instant success story. Approved LACNIC Board minutes from 29 November 2016 record Kaplan reporting that the formal request for IDRC funding for Ayitic 2.0 had been sent and that the project was expected to begin in early 2017. At that point, the documented fact was an application action and an expectation. The minutes do not establish that funding had already been approved, and they do not establish a program result. The 29 November 2016 Board minutes are valuable because they preserve the beginning of the decision sequence without compressing it into hindsight.

By 30 November 2017, LACNIC publicly attributed a developed account of Ayitic Goes Global to Kaplan. She described a goal of training 300 young Haitian women and said the approach could not be implemented or replicated without work on local Internet infrastructure. She also described LACNIC as responsible for the infrastructure component, said it was working with Fundación Transversal, and referred to networking and cybersecurity courses being developed for local technicians. The 300 figure was a goal at that date, not a measured result. LACNIC’s 2017 program report supports the design statements and their attribution.

Those two dated records show more than chronology. The funding request created a channel through which a proposed intervention could be supported; the later explanation defined why the intervention could not be limited to a classroom. Kaplan’s attributable role lies in reporting the request and publicly articulating this linked design. It would be inaccurate to jump from those acts to sole authorship of Ayitic or to claim that she personally delivered its courses. The relevant contribution is the connection she made between a social objective, a training design and the technical conditions required to pursue it.

The independent funder record supplies a wider institutional frame. IDRC identifies LACNIC and the University of the West Indies as lead institutions, describes a 30-month project and records completion on 11 March 2020. It also catalogs evaluations produced by 3x3 Design. That record confirms that the initiative belonged to an institutional partnership and that assessment was built into the project’s public documentation. IDRC’s completed-project page therefore corroborates the program chain without assigning every implementation choice to Kaplan.

Why skills and infrastructure belonged in one intervention

Kaplan’s 2017 explanation placed infrastructure inside the program logic rather than treating it as background. Her point was specific: implementation and replication depended on work on local Internet infrastructure. The same account linked LACNIC’s infrastructure responsibility with cooperation involving Fundación Transversal and with courses in networking and cybersecurity for local technicians. The LACNIC report supports that combination. It does not support a claim that Kaplan personally built infrastructure or taught entities.

IDRC’s project material independently explains why the combination mattered. It identifies scarce skills and infrastructure, problematic labor conditions, and inconsistent electricity and connectivity among the constraints surrounding the effort. The completed-project page also says the first cohort included 50 ICT professionals and 50 young women, giving the initial work both a technical-capacity and a entity-facing dimension. IDRC’s project record is the basis for those program-level facts.

Taken together, the two records support a bounded design inference. Training could address a capability gap, but training alone could not make unreliable electricity or connectivity disappear. Infrastructure work could address part of the operating environment, but infrastructure alone would not provide entities or local technicians with the intended skills. The intervention therefore paired mechanisms that addressed different constraints. That is a stronger and more precise claim than saying that one component caused the other or that the combination guaranteed employment.

The replication point is especially important. Replication is sometimes described as repeating a curriculum in another place. Kaplan’s recorded warning made the surrounding conditions part of the question: a program could not simply be copied while ignoring whether the local Internet environment could support it. The public record does not prove that Ayitic produced a universally replicable template. It shows that Kaplan explicitly rejected a training-only conception of replication and located infrastructure work inside the implementation problem.

This is the first clear example of the wider cooperation system. A program goal was converted into multiple workstreams; responsibilities were distributed among institutions and partners; and the environment that could limit delivery was named before outcomes were claimed. The value of the example lies as much in its constraints as in its reported numbers.

The partnership is the unit of delivery

The Ayitic record contains several person-attributable statements, but its delivery belongs to a larger group. Kaplan reported the funding request and later explained the goal, infrastructure requirement, LACNIC component and course-development work. IDRC’s record identifies lead institutions, while the LACNIC account names cooperation with Fundación Transversal. Evaluations were produced by 3x3 Design for IDRC and LACNIC. The UN Internet Governance Forum record names Kaplan as an organizer of a 2018 session about the project, not as its sole implementer. The IGF session page and IDRC’s project catalog make the institutional distribution visible.

Using the partnership as the unit of delivery solves an attribution problem without making individual agency disappear. Kaplan can be credited for the actions and explanations attached to her name. LACNIC can be credited for the responsibilities attributed to the organization. Funders, lead institutions, local partners, trainers and evaluators retain the work that the records assign to them. Entities remain people in a program, not evidence for someone else’s personal success story.

That allocation also explains why cooperation is an operating method rather than ceremonial language. Funding, infrastructure, course development and evaluation require different forms of authority and expertise. The public documents do not describe one actor absorbing all of them. They show a design in which several actors can contribute through defined roles. A regional development function can help connect those roles, but connection is not possession.

The same principle applies when interpreting results. An observed graduation rate or training count belongs to the program and the conditions in which it operated. It is not a personal performance metric for Kaplan. Keeping that boundary explicit allows the article to identify her contribution—linking mechanisms and advancing a design—while leaving delivery and measured outcomes with the partnership.

Reading the first-cohort result with discipline

The UN IGF’s record for a 13 November 2018 lightning session names Kaplan of LACNIC as an organizer and reports an 86 percent graduation rate for Ayitic’s first cohort. It also distinguishes that result from the broader goal of reaching 300 women. The IGF session record supports the date, role and figure.

The figure answers a narrow question: what share of the first cohort graduated, as reported for that session? It does not establish the graduation rate for later rounds. It does not show that 86 percent of all intended entities completed the program. It does not show how many graduates obtained online work, what kind of work they obtained, or whether any employment continued. Those questions may be important, but the cited record does not answer them.

This distinction illustrates how a cooperation system should handle interim evidence. A first-cohort measure can inform discussion while a program continues, provided it is labeled by cohort and type. It can be compared later with broader evaluations without being retroactively turned into a final impact result. Kaplan’s organizer role helps connect the program to a public Internet-governance discussion; it does not transfer the cohort’s result to her personally.

The careful reading also protects the entities from being reduced to a promotional number. Graduation is a program output associated with a defined stage. Employment is a different outcome shaped by labor conditions as well as skills and access. IDRC’s record explicitly places problematic labor conditions among the constraints. The IDRC project page supports that wider boundary.

Evaluation closes the learning loop without proving employment

IDRC records Ayitic as completed on 11 March 2020 after 30 months and catalogs 3x3 Design evaluations for two individual rounds and an overall assessment spanning all three. The overall assessment says the program taught digital skills to 316 female youth and examined infrastructural, socioeconomic, cultural and pedagogical barriers. IDRC’s project and research-output catalog and the overall assessment support those program-level findings.

The 316 figure is a training-participation result. It should not be rewritten as 316 jobs, 316 successful placements or 316 people whose economic position was transformed. The external assessment ran from February 2018 to September 2019 and analyzed a program operating amid multiple barriers. Its value is not that it closes every causal question. It provides a structured account across the rounds and records how inconsistent electricity and Internet access were mitigated through multiple sources while remaining part of the operating context.

Evaluation completes an important part of the cooperation loop. A design begins with identified constraints and proposed mechanisms. Delivery produces activities and immediate outputs. Evaluation then asks what happened across the work and what barriers persisted. The evaluator’s independence from a person-centered narrative matters here: the findings belong to the assessment, not to Kaplan’s self-description, and they can qualify an institutional account rather than merely repeat it.

The record nevertheless stops short of a complete long-term outcome chain. It does not permit the conclusion that every entity found digital work. It does not permit a claim that Kaplan caused the reported training reach or the first cohort’s graduation rate. It does not isolate which component—courses, infrastructure work, mentoring, partner coordination or another factor—produced any later outcome. A credible interpretation therefore treats the evaluation as evidence of reach, implementation conditions and persistent constraints.

That limit strengthens the article’s thesis. Repeatability does not mean promising identical social outcomes whenever the same program labels are used. It means making the design, roles, constraints and measures clear enough that another cooperation effort can examine them. Kaplan’s recorded insistence on infrastructure and the evaluators’ attention to electricity and connectivity meet at that point: both keep the surrounding operating environment inside the analysis.

The Technical Forum redesign started with a diagnosed bottleneck

Ayitic addressed participation through skills and infrastructure. A February 2021 Board record shows Kaplan addressing participation through governance design. According to approved minutes, she described the former Technical Forum committee as too rigid to expand themes and processes, insufficiently broad in technical terms to attract new talent, and affected by low participation in elections. LACNIC’s 23 February 2021 Board minutes are the direct record of that diagnosis.

The diagnosis is notable because it does not blame a lack of participation on an abstract absence of interest. It identifies features of the mechanism itself: the committee’s combined responsibilities, its technical breadth and the selection process for a community representative. That framing makes institutional redesign possible. If a structure is part of the constraint, changing the structure becomes a legitimate response.

Kaplan proposed separating the program-committee function from evaluation of technical papers. She also proposed replacing the low-participation election with a community representative designated by the Board. The Board unanimously approved the modification at the same meeting. The approved minutes support both the proposal and the decision.

The two elements addressed different parts of the diagnosis. Separating program design from paper evaluation reduced the concentration of functions in one committee arrangement. Changing how the community representative was selected responded to the recorded problem of low election participation. The public minutes support that relationship at the level of proposal and rationale. They do not show how the new arrangement operated over time.

Here again, the cooperation method begins by turning a broad concern—attracting wider participation—into a design question. The proposed remedy does not guarantee new talent. It creates a different mechanism through which themes, processes, evaluation and representation can be organized. Formal Board approval then supplies institutional authority for the change.

Approval was real; downstream impact remains unmeasured

The February 2021 record supports a concrete outcome: the LACNIC Board unanimously approved Kaplan’s proposed Technical Forum modification. That is more than an idea or an informal recommendation. It is a dated institutional decision with an attributable proposal and a recorded decision-maker. The Board minutes establish that outcome.

The same minutes do not establish a later increase in submissions, technical diversity, new entities or event quality. They do not report a before-and-after measure for election participation. They do not show that the redesigned committee attracted the talent Kaplan hoped a broader structure would reach. Treating approval as proof of those later effects would collapse a decision into an impact claim.

That boundary is useful for understanding institutional leadership. A person can identify a constraint, formulate a remedy, win formal approval and remain unable to guarantee the ultimate result. The later result depends on implementation, community response and conditions not measured in the decision record. Credit for the proposal does not require pretending that those dependencies vanished.

The forum example therefore adds a governance module to the repeatable system. Define the participation problem in operational terms. Separate functions when their combination creates rigidity. Choose a decision route with authority to change the structure. Record the approval. Then leave downstream claims open until evidence can support them. This is disciplined cooperation design, not a claim of completed transformation.

Turning community principles into usable mechanisms

Approved Board minutes from 19 May 2020 record Kaplan presenting a community working group’s second set of recommendations for LACNIC’s Community Code of Conduct. The recommendations included a complaint guide and form, extending adoption to virtual spaces, and inviting partner organizations to adhere. The working group also considered a separate mailing-list section unnecessarily complex because the code’s general provisions were broad enough. The May 2020 Board minutes support the content and attribute the presentation to Kaplan.

The authorship boundary is explicit. Kaplan presented the recommendations, but the work belonged to a community working group. The Board held decision authority. Describing the update as Kaplan’s personal code would erase the group that developed the proposals and the institution that approved them. Describing her as merely present would erase her documented role in carrying the recommendations into the Board process. Accurate attribution keeps all three layers visible.

The recommendations translated broad conduct principles into ways people could use them. A complaint guide and form offered a defined route for raising a concern. Coverage of virtual spaces addressed where community interaction was occurring. Inviting partner adherence recognized that cooperation can cross organizational boundaries. Choosing not to create a separate mailing-list section reflected another kind of design judgment: add an operating mechanism where one was needed, but avoid a new layer when the general code was considered sufficient.

LACNIC’s public update of 15 December 2020 records Board approval of the revised code, Trusted Representatives, a complaint guide and a complaint form. The December update matches the operational recommendations documented earlier. The record supports a chain from working-group proposals, through Kaplan’s presentation, to collective approval and published mechanisms.

It does not establish how many complaints were later submitted, how they were resolved or whether entities experienced the community as safer. Those would be separate outcome questions. The documented result is narrower and still important: principles were paired with roles and procedures through which concerns could be raised. In a participation system, access is incomplete if people are invited into a community but lack a workable process when conduct problems arise.