PowerPoint Presentation

3 Resource Allocation and Decision-Making Tools.

[Audio] Let's start from the big picture — and with an observation that might seem obvious but carries a lot of practical weight. Digital Agriculture doesn't operate in an ideal environment. Even when projects are well-funded, resources are always constrained. And I'm not just talking about money. I mean time, skills, infrastructure, and even stakeholder attention. Every one of those is a resource, and every one of them is limited. Here's the critical point: success is not determined by how much funding is available. It is determined by how effectively those resources are allocated. What we see in practice — and this is consistent across many Digital Agriculture initiatives — is that poor allocation decisions dilute impact. Projects delay adoption, or they produce solutions that are technically sound but fail to achieve real-world uptake. The technology works. Nobody uses it. And that is a failure, regardless of what the technical performance reports say. On the other hand, when allocation is done in a structured way, accountability improves, decisions become more transparent, and — most importantly — the initiative becomes more sustainable over time. The key message from this slide is this: resource allocation is a strategic decision layer, not an operational detail. It belongs at the same level of seriousness as the technical design of a project, the choice of partners, or the targeting of a funding call. If we treat it as administrative housekeeping, we will pay for that choice during implementation..

[Audio] The answer is that allocation in Digital Agriculture is shaped by three forces — complexity, uncertainty, and strong interdependencies — that make even experienced teams struggle. Think about the structural reality of most projects. Key parameters — budgets, timelines, staff capacities — are fixed very early. Once implementation begins, the room to adjust is very limited. And any attempt to reallocate resources after the fact often comes with real costs: contractual obligations, partner agreements, organisational politics. The room to manoeuvre shrinks quickly. At the same time, teams rarely have all the capabilities they need internally. This creates difficult trade-offs: do you hire the expertise you need, do you outsource, or do you simplify the project ambition? None of these is a trivial decision. Each has long-term consequences for the coherence of the initiative — and for its sustainability after the funding period ends. Add to that the inherent uncertainty of operating in agricultural systems. Climate conditions, regulatory environments, and market dynamics are constantly shifting. This means many allocation decisions are made with incomplete information, at a moment when it matters most. And once resources are committed, reversing those decisions is either costly or impossible. But I want to highlight the fourth point on this slide as perhaps the most important. Impact does not depend only on technical performance. It depends on uptake — on whether farmers, advisors, and other actors in the value chain actually use what we develop. And this is precisely where many well-resourced initiatives fall short: they invest heavily in technology, at the expense of engagement and validation, and the result is low adoption..

[Audio] Before we look at any specific tool, I want to give you the architecture within which all these tools operate. Because a tool without a process is just a technique — and techniques in isolation rarely solve strategic problems. The framework on this slide has six steps, and I'd like you to think of them not as a checklist to complete once, but as a continuous cycle that you return to throughout the life of an initiative. The sequence begins with the one step that teams most consistently skip: defining your objectives and impact KPIs before you allocate anything. No tool in this module produces meaningful results unless the team has first agreed on what they are trying to achieve — and how they will measure it. This seems obvious, but in practice the pressure to act quickly leads many teams to jump straight to activities before the goals are actually clear. From there you identify candidate activities — what could actually help you achieve those objectives — and then you evaluate them using the quantitative and qualitative tools we'll cover in detail. That leads to prioritisation, using decision aids like the Impact-Effort Matrix or MCDA to produce a ranked, defensible shortlist. Then you allocate and document — you commit resources and you record the rationale for your choices. And finally, you review and adapt as the project evolves. Step five — documenting the rationale — deserves particular emphasis. In any initiative involving shared funds or multiple stakeholders, the reasoning behind allocation decisions must be on record. Not as a bureaucratic exercise, but because it is the mechanism by which teams learn from their decisions, resolve disputes, and demonstrate responsible stewardship. Now, before we get into the tools themselves, there's one conceptual distinction I want to make explicit, because it often causes confusion in practice..

[Audio] The distinction I want to draw is between funding decisions and allocation decisions — because while they are related, they are fundamentally different in nature, and treating them as the same thing is one of the most common weaknesses in Digital Agriculture initiatives. Funding decisions are typically driven by external actors — EU programmes, investors, banks, grant-making bodies. They focus on eligibility, compliance, and financial rules. They answer the question: how much money is available, and under what conditions? Funding is an input. Allocation decisions, by contrast, are internal strategic choices. They are driven by project leaders, SMEs, and consortia. They focus on priorities, trade-offs, and sequencing. They answer a completely different question: where should we invest first, and why? Allocation is a strategic transformation mechanism — it is what converts available funding into actual impact. Confusing the two leads teams to think that securing funding is itself the achievement, and that the allocation will sort itself out. It doesn't. Funding enables action. Allocation determines impact. And only one of those two is within your control once the grant is signed. So with that distinction in place, let's look at the environment in which these allocation decisions have to be made — because context shapes which tools are appropriate..

[Audio] Resource allocation in Digital Agriculture takes place under conditions that make unstructured, intuition-based decisions unreliable. There are limited resources, high uncertainty, and competing priorities — often represented by stakeholders with genuinely different objectives and perspectives. This is where structured decision-making tools earn their value. They do three things that informal judgment alone cannot reliably deliver. First, they transform qualitative judgements into comparable formats. When you're comparing investing in a drone fleet against investing in a farmer training programme, those are not naturally comparable — they operate in different dimensions of value. Tools like weighted scoring and CBA create a common basis for comparison. Second, they facilitate collective decision-making. When a consortium of eight partners needs to agree on allocation, a structured tool provides a shared language and methodology. It reduces ambiguity and, importantly, it reduces the risk of conflict — because the disagreement can be about criteria and scores rather than about who gets the money. Third, and I want to be clear about this: a structured approach does not eliminate uncertainty. What it does is provide a framework within which uncertainty can be managed — where assumptions are made explicit, and where trade-offs can be systematically evaluated rather than implicitly absorbed. This is a crucial distinction. The goal of these tools is not to produce a definitive "right answer." The goal is to make the decision process transparent, contestable, and improvable over time. With that framing in place, let's move to the tools themselves. We'll start with the quantitative methods..

[Audio] We now move into the first category of decision tools — the quantitative approaches. These are methods that convert resource allocation questions into structured, numerical comparisons. There are three core tools here: Cost-Benefit Analysis, Weighted Scoring, and Return on Investment. Each one answers a slightly different question, and together they cover most of the situations you will encounter..

[Audio] Cost-Benefit Analysis — or CBA — is the most foundational of the three. Its logic is intuitive: you compare what an activity costs against what it is expected to generate, and you express that comparison as a ratio. When the Benefit-to-Cost Ratio exceeds one — that is, when benefits outweigh costs — the activity generates positive net value. The higher the ratio, the stronger the case for investment. When it falls below one, you are spending more than you gain, and that should raise serious questions. In Digital Agriculture, the cost side is usually relatively straightforward to identify: equipment, installation, personnel time, training, maintenance, and the opportunity cost of what you chose not to fund instead. The benefit side requires more careful thinking, because benefits in agricultural innovation are often indirect or shared. Yield improvement that accrues to farmers, input cost savings on fertiliser or water, labour efficiency gains, the adoption multiplier when a solution scales — these are real benefits, but they require explicit estimation. And this brings us to the sensitivity check shown at the bottom of the slide — arguably the most important discipline in any CBA exercise. Ask yourself: what happens if my benefit estimates come in 25% lower than expected? If the BCR still comfortably exceeds 1.0, your investment case is robust. If it falls below 1.0 under that scenario, the case is fragile and deserves much more scrutiny before you commit. CBA gives you a starting point. But many investment decisions involve criteria that a single ratio cannot capture — which is where the next tool becomes essential..

[Audio] Weighted scoring is particularly valuable when the activities you are comparing are genuinely diverse — when you need to evaluate a technology investment, a training programme, and an outreach campaign on the same basis, and financial return alone does not tell the whole story. The process works in four steps. You define four to six evaluation criteria that reflect your initiative's real priorities. You assign weights to each criterion — summing to one hundred percent — and crucially, you debate those weights openly before scoring anything. Then each team member scores each option on each criterion independently, on a scale of one to five. Finally, you multiply the score by the weight and sum across criteria to get a total for each option. The highest score wins, under the agreed priorities. I want to dwell on the weight-setting step for a moment, because it is the most revealing part of the exercise. Before any option is scored, the team must agree on what matters most. And this conversation is often where the real strategic disagreements surface — because a technical lead will instinctively weight technical readiness highly, while a field coordinator will weight farmer impact, and a financial officer will weight cost efficiency. Making those instincts explicit and negotiating to a shared set of weights is genuinely valuable alignment work — often more valuable than the scores that follow. A practical tip: run the scoring independently before comparing results. When team members score the same option very differently on the same criterion, that disagreement is a signal — it reveals a knowledge gap, or an assumption that hasn't been surfaced. Resolve those before committing resources. Remember: weighted scoring doesn't produce a "correct" answer. It produces a transparent, structured ranking that reflects your team's agreed priorities. The discipline is in the process, not in the final number. Now let's look at the third quantitative tool, which is less about internal decision-making and more about communicating value externally..

[Audio] ROI is the metric that travels furthest beyond the project team. Where CBA and weighted scoring are primarily internal tools — used to structure decisions within the team — ROI is also a communication tool. It translates the impact of an investment into a single number that any stakeholder, any investor, any cooperative board, can immediately understand and compare. The formula is straightforward: you take the net benefit, subtract the investment cost, divide by the investment cost, and multiply by one hundred to get a percentage. The slide draws an important distinction between financial ROI and impact ROI. Financial ROI applies where activities generate direct monetary returns — a subscription-based platform, a licensing agreement, measurable input cost savings for farmers. Impact ROI is more relevant for publicly funded or mission-driven activities, where you replace the monetary benefit with a unit of impact: farmers reached per euro, hectares covered, tonnes of CO₂ avoided. Both apply the same rigour. The difference is what you put in the numerator. The precision irrigation example on the slide is worth walking through carefully. A pilot deployed on fifteen farms costs eighteen thousand euros. Over one growing season, the monitored savings in water, energy, and labour adjustments total twenty-six thousand euros. That is a net benefit of eight thousand euros, and an ROI of 44.4% — a strong single-season return by any standard. But the more powerful step is projecting to scale. If that ROI holds across one hundred and fifty farms, the investment case for full deployment is not just positive — it becomes compelling. That is exactly the analysis that cooperative boards and regional funders want to see before they commit to scaling a pilot. We've now covered the three core quantitative tools. But numbers alone are never sufficient for good allocation decisions. There are criteria that matter enormously but cannot be expressed in a ratio or a score — and we need to address those directly..

[Audio] We now move from quantitative tools to the broader category of decision aids — structured frameworks that help teams make allocation choices when the picture is more complex, the options are harder to compare, or the team needs a shared visual language to have a productive conversation. Two qualitative criteria come first, then two decision aid.

[Audio] Let me open with a question that I'd invite you to hold in your mind as I talk through this slide. Can you think of an activity in your own work — something you chose to invest in — that would not have scored particularly well in a financial analysis, but that was clearly the right decision? What made it right? In most rooms, the answers cluster around two themes. The first is that the activity was essential to maintaining the trust and engagement of farming communities, cooperatives, or partners — even if the direct financial return was negligible. The second is that it generated knowledge, protocols, or tools that benefited the wider field far beyond the specific project. Those two themes are exactly what this slide captures: mission alignment and ecosystem value. Mission alignment asks whether an activity directly advances the core purpose of the initiative — not just its measurable outputs. Here is the risk it guards against: an activity might score very well on financial ROI while quietly drifting away from the mission. A precision agriculture platform that optimises yields for large commercial farms while becoming increasingly inaccessible to the smallholder farmers the initiative was designed to serve is a classic example. The numbers look fine. The mission is being undermined. Mission alignment is the check that prevents that kind of strategy drift — the gradual, often unnoticed movement of resources toward what is easy or profitable rather than what the initiative actually exists to do. Ecosystem value captures something different. It's about the contribution an activity makes to the Digital Agriculture community beyond the immediate project. Activities that generate open-source tools, validated field protocols, publicly accessible datasets, or replicable methodologies create value that extends to other teams, other projects, and other farmers — often for years after the activity itself is finished. A farmer co-design workshop that costs five thousand euros and directly trains thirty farmers might also produce an engagement methodology that fifty other projects subsequently use. The total ecosystem value of that investment vastly exceeds what any direct ROI calculation would show. The practical implication: include these criteria explicitly in your weighted scoring model. Assign them real weights. Don't treat them as tie-breakers after the quantitative analysis has already reached a conclusion. With these qualitative dimensions in mind, let's look at the first decision aid — a tool designed for rapid, participatory prioritisation..

[Audio] The Impact-Effort Matrix is the most immediately accessible tool in this module. It requires no data, no calculation, and no specialist expertise. It requires only one thing: honest collective judgement. Which, as it turns out, is both the simplest and the most powerful input into any prioritisation decision. The mechanism is straightforward. You plot candidate activities on a two-by-two grid. The vertical axis represents expected impact — how strongly does this activity advance the project's objectives? The horizontal axis represents required effort — what does it take in financial cost, time, technical complexity, and organisational capacity to implement it? The resulting quadrants give you a clear prioritisation logic. Activities in the top-left — high impact, low effort — are your quick wins. Do these first. They deliver disproportionate value relative to the resources they consume. Activities in the top-right — high impact, high effort — are your strategic bets. Worth pursuing, but stage the resources and set clear milestones before committing fully. Activities in the bottom-left — low impact, low effort — are fill-ins. Do them when capacity allows, but never at the expense of higher-impact work. And activities in the bottom-right — low impact, high effort — are the ones to avoid. They consume resources without generating proportionate value. The way I recommend running this is as a workshop exercise. Write each candidate activity on a card. Put the matrix on a whiteboard. Ask team members to place activities independently — without discussion — and then compare placements. The disagreements are the most valuable part of the exercise, not the final positions. When one person puts an activity in the top-left and another puts it in the bottom-right, that gap reveals either a difference in information, or a difference in assumptions that needs to be surfaced and resolved before resources are committed. One honest caveat about this tool: it relies on subjective assessments, and those can vary significantly depending on the experience and perspective of participants. This is why its primary value lies in the discussion it generates, not in the precise final positioning. It is a conversation tool that produces a decision — not an algorithm that produces an answer. For decisions that are more complex, that involve higher stakes, or that need to produce a fully documented rationale for external stakeholders, we need a more rigorous method. That's MCDA.

[Audio] MCDA extends the logic of weighted scoring into a full evaluation framework designed for high-stakes allocation decisions — situations where options are complex, criteria are diverse, multiple stakeholders are involved, and the decision needs to produce a documented, auditable rationale. The process has six steps, and I'll walk you through them using the worked example on the right. The scenario: a consortium needs to allocate forty thousand euros across three competing investments. Option A is expanding the drone fleet. Option B is developing a farmer-facing mobile advisory application. Option C is commissioning soil laboratory analysis across the pilot farms. The team agrees on four criteria and their weights. Strategic KPI contribution carries thirty-five percent — it's the primary measure by which the project will be evaluated. Cost efficiency carries twenty-five percent. Farmer adoption potential and technical readiness each carry twenty percent. Each option is then scored on each criterion from one to five. The mobile advisory app scores five on KPI contribution — it directly drives the initiative's primary outcome metric. It scores five on adoption potential. It scores four on cost efficiency because the development costs are well understood. But it scores only three on technical readiness, because development is not yet complete. Multiply each score by its criterion weight, sum across all criteria, and the mobile app emerges with a total weighted score of 4.35 — clearly ahead of soil analysis at 3.70 and the drone fleet at 3.55. The decision: fund the mobile app as the primary priority. Allocate remaining budget to soil analysis. Defer the drone fleet to the next allocation cycle, where it can be reconsidered with better mid-term evidence. But notice what this process produces beyond the ranking itself. It produces a documented rationale where every number is traceable to a criterion weight and an explicit score. That is exactly what programme officers, auditors, and consortium partners need when they ask how allocation decisions were made. MCDA doesn't just tell you what to fund — it tells you why, in a way that can be defended. Now, before we bring all of this together, there's one more dimension of allocation we need to address — arguably the most recurring trade-off in Digital Agriculture practice..

[Audio] One of the most consistently difficult allocation decisions in Digital Agriculture is how to balance investment across three fundamental resource categories: people, technology, and outreach. Each creates value. Each is necessary. And all three compete for the same budget. Let's take them in turn. Human capital — the agronomists, data scientists, field coordinators, and project managers — is the most flexible resource in any initiative. Skilled people adapt to unexpected challenges, build trust with farming communities, and apply contextual judgement in situations that no algorithm can anticipate. But human capital is also the most expensive fixed cost. Over-staffing an initiative while under-investing in tools creates a team of skilled professionals who are either waiting for technology that doesn't exist yet, or duplicating by hand analyses that software could perform in minutes. The principle is to right-size the team to the technology available — and the technology to the team's capacity to deploy it. Technology investment — sensors, platforms, data infrastructure — creates the scalability that human effort alone cannot achieve. A well-designed monitoring network can track fifty farms as efficiently as five, at a marginal cost per additional farm that is far lower than adding field staff. But here is the graveyard of Digital Agriculture: expensive hardware, sitting underused, because the expertise to deploy and maintain it was not budgeted alongside the procurement. Technology without the human capability to operate it fails at the first technical obstacle. Outreach and adoption — farmer training, demonstration events, advisory networks — is what converts technical achievement into actual impact. In agriculture, where change happens slowly and trust is built over seasons rather than weeks, an excellent tool that is not adopted is an investment that has failed its ultimate purpose. And yet outreach is chronically underbudgeted in technology-led initiatives. The instinct is to invest in building and proving the technology, and treat adoption as something that will follow naturally. It rarely does. The practical implication: all three categories must be present, and their relative balance should shift as the initiative matures. In early phases, human capital and co-design dominate. In implementation phases, technology investment peaks. In later phases, outreach becomes the critical investment to drive adoption and long-term sustainability. This brings us to the portfolio perspective — which is where these trade-offs come together..

[Audio] The three resource categories we just discussed are not independent choices. They are interdependent components of a portfolio, and this is the reframing I want you to take from this slide. In Digital Agriculture, resource allocation should not be approached as a single-choice optimisation problem — as if the goal is to identify the single best investment and direct everything toward it. Instead, it should be understood as a portfolio construction exercise — where the objective is to combine different types of investments in a way that maximises overall impact under real-world constraints. The diagram on this slide shows why. Impact is not generated by isolated actions. Technology development without outreach stays in the lab. An isolated pilot without a deployment plan has no path to scale. Outreach activities without a technological backbone generate engagement but not lasting change. Technology alone, without adoption, creates no value for farmers. What generates impact is the combination: pilot and validation activities reduce uncertainty and build credibility; technology development creates the infrastructure for efficiency and scale; outreach and advisory activities translate technical capabilities into behavioural change; and scaling activities ensure that successful solutions move beyond isolated experiments and generate systemic impact. The allocation question, then, is not "which of these should we fund?" It's "how do we resource all four phases in the right proportions, given where we are in the initiative's lifecycle?" That is a portfolio question, and it requires portfolio thinking. And to support that thinking, here is the reference tool that should guide you in choosing which decision instrument to apply in which situation..

[Audio] This table is designed to be a practical reference — something you can return to whenever you face an allocation decision and need to identify the right starting point. The logic is straightforward. Match the tool to the situation, not to the team's comfort zone. When you have a long list of candidate activities and need a rapid first-pass prioritisation — use the Impact-Effort Matrix. It's fast, collaborative, and requires no data. When you're comparing two to four activities with quantifiable financial returns — use CBA plus ROI. These give you a clear, evidence-based financial ranking. When multiple criteria are involved, some of them non-financial, and the team needs to align around a shared decision — use Weighted Scoring. It surfaces disagreements about priorities before they become disputes about outcomes. When the stakes are high, multiple stakeholders are involved, and you need a fully auditable rationale — use MCDA. It's the most rigorous of the tools, and produces the most defensible documentation. When you need to test whether your budget is robust to uncertainty in your assumptions — apply Sensitivity Analysis to your CBA or ROI estimates. And before any of these: always start with the KPI Mapping exercise to make sure the activities you're evaluating actually connect to the objectives you are supposed to be achieving. This is the non-negotiable first step. Applying analytical rigour to the wrong activities is worse than applying no analysis at all. In practice, these tools are used in sequence and in combination. You start with KPI mapping, filter quickly with the Impact-Effort Matrix, compare frontrunners with CBA, and use MCDA when the final decision requires full documentation. The discipline is knowing which layer you're in..

[Audio] We've covered a lot of ground, so let me distil this into the four ideas that I want you to carry forward. First: objectives before everything. No tool in this module produces meaningful results unless you have first defined what you are trying to achieve and how you will measure it. The KPI mapping exercise is not optional — it is the entry point to every other method we've discussed. Start there, every time. Second: quantify what you can. CBA, weighted scoring, and ROI don't claim to eliminate uncertainty. What they do is make uncertainty visible and manageable. They transform subjective preferences into comparable, evidence-based estimates. That is enormously valuable, and it is available to any team willing to invest the time in using these tools honestly. Third: include what you cannot quantify. Mission alignment, ecosystem value, and risk tolerance shape the long-term sustainability of a Digital Agriculture initiative in ways that no financial model fully captures. If you build your allocation decisions purely on quantitative scores, you will underinvest in the things that actually sustain a project over time. Build qualitative criteria explicitly into your evaluation frameworks and give them real weight. Fourth: balance your resource portfolio. People, technology, and outreach are all necessary. A portfolio dominated by any one of them is at risk. As the initiative matures, the balance should shift — and revisiting that balance at every major allocation decision point is one of the most important habits a project team can develop. Analytical tools do not replace leadership judgement. What they do is improve it — by making assumptions explicit, making comparisons fair, and making decisions traceable. That is the discipline this module is designed to build.

thank you!. TALLHEDA has received funding from the European Union's Horizon Europe research and innovation programme under Grant Agreement No. 101136578. Funded by the European Union. Views and opinions expressed are however those of the author(s) only and do not necessarily reflect those of the European Union or the European Research Executive Agency (REA). Neither the European Union nor the granting authority can be held responsible for them..