Your IT team recommends replacing an ageing system. Operational managers want better tools for coordinating services. Staff are asking about AI, while a recent review has identified gaps in recovery arrangements.
Each proposal may have merit. The challenge for not-for-profit leaders is deciding which should proceed first, what the organisation can realistically deliver and what can wait.
Technology investment involves more than the purchase price. It commits staff time, introduces change and creates ongoing responsibilities. Its value depends on whether those commitments support the organisation’s services, people and long-term sustainability.
A useful starting point is to ask the same practical questions of each proposal. That gives leadership a clearer basis for comparing different needs and understanding the consequences of each decision.
Begin with the problem the investment is intended to address. A proposal should explain which activity will improve, who will benefit and why the change matters.
“Replace the client-management system” describes a project. It does not yet explain the outcome. The underlying need might be to reduce duplicate recordkeeping, improve service coordination, address support limitations or make information more accessible to authorised staff.
Those reasons affect how the proposal should be assessed. A replacement intended to address an imminent support deadline requires a different discussion from one primarily designed to make reporting more convenient.
Ask the people proposing the investment to describe:
This helps establish whether the proposed solution addresses the actual need. It can also reveal cases where configuration, training or a process change could resolve part of the problem.
Deferring an investment can be reasonable, provided the organisation understands what it is accepting in the meantime.
Some delays mean employees continue using a cumbersome process for a few more months. Others may leave a critical application unsupported, postpone a necessary security improvement or trigger another contract term that limits future options.
Ask for a clear explanation of the consequence of waiting. What changes if the investment is deferred by three, six or twelve months? Is there a firm deadline? Can interim measures reduce the exposure? Who will monitor the situation?
Where the concern is risk, describe the affected service and the potential consequences in plain language. A technical finding becomes easier to assess when leaders understand how it could affect access to information, service continuity or the ability to support staff.
Avoid treating every proposal as equally urgent. Equally, an issue should not lose priority simply because capable employees have found ways to manage around it.
A deliberate decision to defer should include an owner, any necessary interim action and a date for reconsideration.
Some technology improvements provide foundations for several later initiatives. Their value can be easy to underestimate when each proposal is considered separately.
Improving identity and access management, for example, may support the introduction of new applications. Addressing inconsistent records may be necessary before a reporting project can deliver reliable information. Strengthening connectivity at a regional location may be needed before staff can make effective use of a new service platform.
Ask IT and operational teams to explain these relationships. Which projects depend on the proposed work? Would proceeding in a different order create avoidable rework or leave an important requirement unresolved?
This does not mean every foundational project should automatically come first. Its scope and timing still need scrutiny. But understanding dependencies allows leaders to assess the sequence as a whole.
It also helps prevent a visible new capability from receiving funding while the less visible work needed to make it succeed remains unaddressed.
A purchase price or monthly subscription provides only part of the investment picture. Ask what it will take to implement, operate and eventually replace or exit the solution.
Depending on the proposal, the commitment may include:
Use a consistent comparison period where practical, and make assumptions visible. A low initial price may be accompanied by higher operating demands, while a larger initial investment may reduce some recurring costs.
Capacity also belongs in this assessment. If internal employees will undertake the work, identify what they would otherwise be doing and whether additional support is needed.
For an NFP, responsible stewardship includes understanding the continuing commitment after the initial project funding has been spent. A grant or one-off allocation may help establish a capability, but the organisation still needs a sustainable way to operate it.
An investment can be worthwhile and still be poorly timed.
Operational staff may be preparing for a major reporting period, opening a new service or adapting to another system change. IT may already be committed to urgent maintenance or a substantial project. A supplier may need decisions and testing input that the organisation cannot provide within the proposed schedule.
Before approving a delivery date, establish who needs to participate and how their time will be made available. Include the people who will use the system, not just those responsible for implementing it.
Ask whether the change can be staged. A smaller initial scope may allow the organisation to validate the approach, support staff properly and resolve issues before expanding it.
Be careful, however, that staging does not remove essential controls or leave teams working across conflicting processes indefinitely. Each phase should have a clear purpose, workable operating arrangements and an agreed point for review.
Define success before approving the proposal. Choose measures that reflect the reason for investing and identify who will assess them.
If the objective is better service coordination, useful evidence might include fewer incomplete handovers or more timely updates. If the aim is stronger recovery capability, success may involve demonstrating that an important service can be restored within an agreed timeframe.
For a project intended to reduce administration, examine the complete task. Include checking, correction and any new work created elsewhere.
Time saved does not automatically become a financial saving. It may provide capacity for more timely recordkeeping, better communication or greater attention to complex work. Those outcomes can be valuable, but they should be described realistically.
Likewise, essential maintenance and risk reduction may be justified without a direct revenue return. The proposal should explain the capability being maintained or the exposure being addressed, together with evidence that the investment achieves its purpose.
Consider three hypothetical proposals: replacing an application approaching the end of support, improving a reporting process and trialling an AI drafting tool.
Each should be assessed using the same questions, but the answers may lead to different decisions.
| Proposal | Key consideration | Possible response |
|---|---|---|
| Replace an application approaching end of support | What services depend on it, when does support end and what preparation is required? | Begin discovery and transition planning early enough to meet the deadline. |
| Improve routine reporting | How much effort and correction does the process require, and what causes the difficulty? | Investigate the workflow and data before committing to a new platform. |
| Trial an AI drafting tool | Is the task suitable, are information boundaries clear and can the result be reviewed effectively? | Run a limited trial with defined measures before making a broader commitment. |
The purpose of comparison is to reach a reasoned decision about each proposal. Some work needs approval, some needs further evidence and some can be deferred with clear conditions.
A simple scoring exercise may help organise the discussion, but it should sit alongside judgement about deadlines, dependencies and service consequences.
Once leadership has made a decision, record why it was made, who owns the next step and when it will be reviewed.
For approved work, identify the outcome, scope, resource commitment and decision points. For deferred proposals, record the consequences being accepted and the circumstances that would bring the work forward.
Revisit those decisions when material assumptions change. A supplier announcement, a change in service demand or evidence from an initial trial may alter the priority.
This creates continuity between leadership decisions and the IT roadmap. It also reduces the need to reconstruct the reasoning every time budgets or priorities are discussed.
Choose three technology investments already under consideration and ask their owners to answer the six questions in this article. Review the responses with IT, finance and the relevant operational leaders.
Where the evidence is incomplete, identify what needs to be established before making a commitment. Where a proposal is ready, agree on its priority and the resources required to deliver it.
For a not-for-profit, sound technology investment supports reliable services, effective staff and responsible use of organisational resources. Clear outcomes, visible trade-offs and realistic delivery commitments give leaders a stronger basis for deciding what deserves attention next.