Start with work, not features
A long feature list can still produce a poor operating system. Discovery should begin with the decisions people make, the information they need and the hand-offs where work slows down or becomes unreliable.
This is especially important in fundraising, where sales, verification, payments, rostering, quality, client reporting and finance often cross several disconnected platforms.
One source does not mean one screen
A connected environment can still provide different views for different roles. Field leaders need immediate operational signals; finance needs reconciliation and commercial controls; executives need trend and risk visibility.
- Define ownership for every critical record.
- Integrate at stable boundaries rather than duplicating data everywhere.
- Design permissions around real responsibilities.
- Preserve an audit trail for material changes.
Build for exception handling
Most systems demonstrate the happy path. Operational reliability is revealed by what happens when a payment fails, a supporter disputes an interaction, data is incomplete or a campaign rule changes.
Designing these exceptions deliberately reduces spreadsheet workarounds and gives teams a clear path through unusual situations.
Keep humans accountable
Automation should remove repetitive effort and surface decisions—not obscure who is responsible. A useful system makes action easier, provides context and preserves accountability.