<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dan Pearce on Medium]]></title>
        <description><![CDATA[Stories by Dan Pearce on Medium]]></description>
        <link>https://medium.com/@danocpearce?source=rss-7124ef8f0433------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*axwjvv58sn7S9w9OWw8RXg.png</url>
            <title>Stories by Dan Pearce on Medium</title>
            <link>https://medium.com/@danocpearce?source=rss-7124ef8f0433------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:30:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@danocpearce/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A Good Technology Demo is Really a Theory of the Organisation]]></title>
            <link>https://medium.com/@danocpearce/a-good-technology-demo-is-really-a-theory-of-the-organisation-a627bb30d08c?source=rss-7124ef8f0433------2</link>
            <guid isPermaLink="false">https://medium.com/p/a627bb30d08c</guid>
            <category><![CDATA[crm]]></category>
            <category><![CDATA[nonprofit-technology]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[organisational-desig]]></category>
            <dc:creator><![CDATA[Dan Pearce]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 08:28:29 GMT</pubDate>
            <atom:updated>2026-07-31T08:28:29.295Z</atom:updated>
            <content:encoded><![CDATA[<p><em>What an end-to-end nonprofit proof of concept revealed about organisational boundaries, the limits of AI and the assumptions built into CRM design.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q7iha2bt9Mxj_f36zpbT0w.jpeg" /><figcaption>An Experiment on a Bird in an Air Pump by Joseph Wright of Derby, 1768</figcaption></figure><p>I was building an executive demonstration for a national UK charity providing specialist support and community services…it was a Tuesday.</p><p>“Demonstration” is technically accurate, although it undersells what the work had become. This wasn’t a standard product tour, with a fictional employee clicking through a suspiciously empty task list. The brief was to show how a future technology platform might support the charity across service delivery, volunteering, fundraising, communications, data and reporting.</p><p>The demo would form part of a wider Art of the Possible session. Its job was to make a future operating model tangible enough for the charity’s leaders to examine. That meant configuring a realistic proof of concept, creating representative data and following a fictional person through several parts of the organisation.</p><p>Halfway through building it, I had the uncomfortable feeling that I was building the wrong thing.</p><p>Nothing was obviously broken, that would have been easier. It was more a case of it being blah.</p><p>In the service-delivery part of the proof of concept, someone could ask the charity for support, discuss their circumstances with an adviser, complete an assessment and agree a plan. Staff could then organise programmes, allocate places and coordinate the volunteers needed to deliver them.</p><p>Elsewhere in the same proof of concept, fundraisers could see a supporter’s history, communications teams could use interests and preferences to shape contact, and leaders could examine the relationship between delivery, funding and results. AI appeared at suitably futuristic moments and performed a few useful administrative tasks without going full Lawnmower Man.</p><p>The records joined together. The screens behaved themselves. On paper, the whole thing worked.</p><p>And yet.</p><p>Although the demo was intended to show one connected organisation, its underlying design still treated services, volunteering and fundraising as separate worlds. A person’s identity changed according to which department happened to be looking at them. Service participant here. Volunteer over there. Supporter somewhere else, wearing a false moustache and pretending they’d never met.</p><p>The charity’s own research described a much less orderly reality.</p><p>Someone might first approach the organisation for help. Later, they could participate in a programme, join a community, volunteer, advocate, donate or introduce somebody else to the charity. Several of those roles might overlap. Some could disappear and return years later. A person who stopped volunteering might still feel deeply connected to the cause, even if the volunteer management system had quietly filed them under Former and moved on with its life.</p><p>I’d started by modelling several credible business processes, but what I needed to model was the organisation’s understanding of a person.</p><p>A small distinction, perhaps. In practice, it changed nearly everything.</p><h3>Software has opinions, even when we pretend it doesn’t</h3><p>The problem with the proof of concept pointed to something larger than this particular demonstration.</p><p>Every CRM contains a theory of the organisation using it.</p><p>That sounds grander than I mean it to be. I’m not suggesting your contact database spends its evenings reading Foucault. Its structure does, however, encode a view of how the organisation works. I should just add here, this isn’t a new paradigm or concept…this has been there since the dawn of the database.</p><p>The data model defines what counts as a person, which roles they may hold and how those roles relate. Ownership rules decide which team is responsible for a record. Permissions determine who can know what. Automations identify the events deserving attention. Reports decide what counts as activity, progress or success. Maybe there is an argument that, without structure there is nothing…yeah maybe.</p><p>During the design of this proof of concept, those assumptions surfaced as apparently technical questions.</p><p>Should the same individual have one person record or several? Is a referral related directly to that person, to a case opened on their behalf, or to both? Does a volunteer remain part of the organisation between assignments? Can a service team see that somebody also donates? Should a fundraiser know that the same person receives support? Which communication preference wins when three source systems disagree?</p><p>Questions like these usually end up in rooms with architects, administrators and an alarming quantity of virtual sticky notes. Yet none is purely technical. Each contains an assumption about identity, responsibility or the relationship the organisation believes it has with someone.</p><p>Once built, those assumptions become harder to see.</p><p>Staff adapt their work to the system. Reports inherit its categories. Integrations carry them into other platforms. New starters learn that “this is how Salesforce works”, when they may actually be encountering a design decision made four years earlier during a workshop after lunch, you know the one where lunch was pretty much just Krispy Kremes and Tesco finest flapjacks…a lot of sugar was consumed that day and it shows.</p><p>The software begins to look like natural law.</p><p>(As the old systems proverb goes: give a temporary workaround six months and it will demand its own governance committee. Now, I may have just made that up, but the underlying, and yes also made up research is extensive.)</p><p>Some boundaries are necessary. In the charity I was working with, service teams, fundraisers and volunteer managers carried different responsibilities. They had legitimate reasons to restrict access to certain records. Safeguarding information shouldn’t be available to everybody with a login and a passing curiosity. Consent given for one purpose doesn’t wander freely into another because the data happens to sit nearby.</p><p>The weakness in my first design wasn’t the existence of specialist teams or records, more so allowing an operational role to become the system’s complete account of the person.</p><p>A conventional “single customer view” wouldn’t fix that by itself. Combining five disconnected records can simply produce one extremely long disconnected record. The organisation still has to decide which context is relevant, who may use it and what somebody should do differently because they know it.</p><p>Otherwise, you’ve built the CRM equivalent of the kitchen drawer containing batteries, takeaway menus, two Allen keys and a charger for a phone last seen in 2007, I know you have one of those drawers! Point is, everything is technically together, but nobody is better informed.</p><h3>The evidence was messier than the process maps</h3><p>This change in direction didn’t come from staring harder at the Salesforce data model, expecting some kind of Matilda-level tipping over of the beaker. No, as cool as that would have been, it primarily came from returning to the evidence behind the demo narrative.</p><p>Before configuring the proof of concept, I’d read the charity’s annual reporting, user research, service-design findings, language review and work on volunteer recruitment and retention. I’d also lead discovery sessions covering fundraising, services, volunteering and the organisation’s wider ambitions, not just fixated on real and/or imagined challenges.</p><p>These sources described the charity through several lenses, staff explained how work happened today and where it became difficult. Research captured the experiences of people using services, joining communities or giving their time. Strategic material described the organisation the charity hoped to become. What was, and is always interesting here is how those accounts didn’t always line up neatly. It’s the gaps between things that are illuminating…like the gold glue of a wabi-sabi bowl.</p><p>Process diagrams tend to present work as a sequence of defined stages, but they seriously lack vibes. The research on the other had described the lives and captured the essence of lived experience, completely ignoring the diagrams.</p><p>People sought practical help, but they also spoke about confidence, companionship, participation and reduced isolation. Some valued online communities. Others preferred local, face-to-face contact. Digital services could widen access across geography, while badly designed or poorly moderated spaces created their own problems. Accessible communication wasn’t a pleasant addition; for some people, conventional phone contact was an actual barrier…for obvious reasons.</p><p>That evidence affected the service story used in the demo. The fictional person at its centre wasn’t sent directly into a standard programme because she had selected the correct option on a form. The ideal was that first she’d explored what support might be relevant, spoke with an adviser, discussed her circumstances and agreed a plan. The technology organised the work around that relationship, as opposed to pretending to replace it.</p><p>The charity’s own language research also complicated the design. Terms that looked interchangeable to a system designer carried different meanings for the people being described. Some sounded clinical, some implied passivity. Others recognised what people contributed rather than defining them by what they needed. Preferences varied between groups and generations.</p><p>There wasn’t a magic noun everyone could agree on, which is often the point at which software would quite like the humans to settle down and choose something from the picklist.</p><p>The volunteer research disrupted another tidy assumption. The initial proof of concept treated volunteers mainly as delivery capacity. Staff could create roles, identify vacancies, schedule shifts and see whether a programme session had enough cover. All useful, yet, it was also a woefully incomplete account of why people volunteered, and for those especially emotionally draining roles, what keeps people coming back.</p><p>The research described affection for the cause, learning, family participation, social contact and belonging. Which fields do they go in? Recognition and continued contact influenced whether people stayed involved, whilst, formally removing somebody when they stepped back for volunteering, could feel less like good database hygiene and more like expulsion from a community they still considered their own.</p><p>These interconnected strands changed how I thought about the volunteer part of the demo. Filling a vacancy remained operationally important, but it couldn’t be the organisation’s entire understanding of the volunteer relationship, nor fully articulate the technology enabling capability…this is pre-sales after all!</p><p>None of this proved that every person wanted a lifelong relationship with the charity. Some may want help with one specific issue and then leave. Others may prefer their volunteering, giving and use of services to remain separate. A richer dataset doesn’t grant an organisation moral permission to become clingy.</p><p>Still, a pattern had emerged, the departmental labels often described the charity’s administration better than they described the person’s relationship with it. Had I asked each team only which fields, screens and reports it wanted, I could’ve produced a reasonably accurate digital replica of the current organisation. It might even have been efficient, it would also have preserved the very boundaries the executive session was meant to examine, and challenge.</p><p>Pro tip: If the map and the territory disagree, check whether the territory attended the requirements workshop.</p><h3>Roles are useful. They’re also temporarily true</h3><p>The redesigned proof of concept still needed categories, the business of work becomes impossible without them.</p><p>“Applicant’ can indicate that someone is waiting for a decision. “Participant” shows that they’ve joined a programme. “Volunteer” brings responsibilities, checks and support needs. “Donor” gives fundraisers a way to understand and manage giving.</p><p>All useful, and you instantly recognise some if not all of these labels, but none are really complete.</p><p>A volunteer may have personal experience of the issue the charity addresses. A participant may become an advocate. Somebody who once needed support may later give money, time or expertise. A donor may be closely connected to a person receiving services.</p><p>These roles don’t form a tidy ladder, people don’t necessarily begin as prospects and progress through the approved stages until, Pokémon-like, they reach their final form as Major Donor…Major Donorzar, I don’t know, wasn’t into Pokémon.</p><p>Life is less considerate than that, people hold several roles at once. They pause. Return. Change their minds. Ask for help after years of giving it. Feel connected without being active. Remain active without wanting a deeper relationship. I want to say at this point, nonprofit organisations compared to commercial businesses, really start to give you an idea of how multi-faceted they can be.</p><p>Anyway, the design risk is easiest to see through what happens when systems forget this.</p><p>Someone repeats information already supplied to another team. A fundraising communication ignores a recent change in their circumstances. Several departments maintain separate histories and each believes it owns a different relationship. Volunteer contributions vanish from view when an assignment ends.</p><p>Funding data sits apart from the programmes it pays for, while outcome reporting is reconstructed afterwards through a heroic combination of spreadsheets and institutional memory.</p><p>The redesigned proof of concept didn’t attempt to show every member of staff everything about everyone…everywhere all at once. It treated the person as the stable point around which referrals, programme participation, volunteering, preferences, communications and giving could be related. Specialist records remained specialist, access remained controlled, and teams retained their responsibilities.</p><p>The design principle I settled on was simple: store the roles, preserve the person. I know, I know…It sounds suspiciously like something created for a slide because, eventually, it was. But in it describes a specific modelling decision rather than a vague ambition to become “more joined up”.</p><p>(Just on that “store the role, preserve the person”, wasn’t that clever? I originally wanted to put a misquote from The Usual Suspects, “the greatest trick the departmental system ever pulled was convincing us the department was the person.” I honestly chuckled and thought it was too good <em>not</em> to put it in, but if you want this to be a serious article then just skip over this bit. If you’ve already read this bit and are mildly annoyed, I’m sorry, if you chose to re-read this article then you can skip this bit, and also the long winded explanation, explaining the bit…which I also find funny.)</p><h3>Turning the idea into something people could argue with</h3><p>Having changed the theory behind the proof of concept, I needed to test whether it could survive contact with actual processes. You know that saying “everyone has a plan until they get punched in the face”?</p><p>A diagram could have expressed the idea, diagrams are excellent at expressing ideas. They’re less reliable when asked to prove that anything underneath them actually works. Boxes can be connected with arrows before anybody has decided what the connections actually mean. Add a few cloud shapes and tasteful gradients and the architecture begins to look almost inevitable. Nobody asks what happens when there are two active plans or the volunteer cancels on Tuesday.</p><p>Configuration is less forgiving, even with the latest vibe coding tools at your disposal.</p><p>The service-delivery demo followed “Mary”, a fictional person trying to understand a change in her circumstances and what support might be available. She asked for support, met an adviser, completed an assessment and agreed a plan. Staff enrolled her in appropriate programmes and organised the benefits, sessions and volunteer support needed to deliver them. Later, she could use a portal to view her plan, upcoming sessions and tasks, while the charity remained able to communicate with her according to her interests and preferences.</p><p>Behind that story sat the operational machinery that tends not to make it onto the inspirational slide.</p><p>Staff needed to manage referrals, assessments, care plans, programme places, volunteer availability, communications and funding. The proof of concept contained enough of this machinery for dependencies to become visible.</p><p>If a programme session required volunteer cover, the lack of a volunteer couldn’t remain somebody else’s spreadsheet problem. The demonstration showed the uncovered session and the operational action needed to resolve it.</p><p>If funding had been designated for a particular programme, leaders needed to see how that funding related to planned and delivered activity. The proof of concept therefore connected fundraising records and capability to programme funding rather than presenting income and services as parallel universes.</p><p>An assessment had to shape the agreed plan instead of retiring gracefully into an attachment. A communication preference recorded during the referral process needed to influence later contact. Participation and delivery data needed to contribute to the organisation’s understanding of outcomes, and a gauge of how well it’s delivering upon its mission and purpose.</p><p>The same logic applied to the separate fundraising story that I wanted to tell, one where we’d follow a supporter whose record initially contained very little information, literally a bit of a name, and an email address. As they engaged, donated and expressed preferences, the organisation’s understanding developed. The point wasn’t to create an omniscient profile, the thinking was to show how consented information could help staff make a more appropriate decision about the relationship.</p><p>The human stories and the operating detail kept correcting each other…weird.</p><p>The personas made abstract design choices easier to understand, but also exposed places where the processes expected people to behave like records, and abstract data points. Service design revealed hand-offs where context might disappear, data modelling tested whether the proposed relationships held together in the first place, and configuration found the loose floorboards.</p><p>Which record owns the date? What happens when two plans are active? Can one volunteer cover several sessions? How should restricted income relate to delivery? Which information should an AI agent be allowed to summarise? What should staff see when something important is missing…how would they even know?</p><p>These are mildly annoying questions, which is generally how you know the proof of concept is doing useful work.</p><p>An executive demonstration needs enough operational truth to be challenged…otherwise what is the point?!</p><p>The aim wasn’t to present the proof of concept as a finished solution or to suggest that every design decision had already been made. It gave the charity’s leaders something specific to examine. They could question whether context should pass between teams, where responsibility ought to sit, which dependencies justified investment and which decisions must remain with staff. Also, more fundamentally I hoped it would elicit more existential questions about the charity, how it wants to deliver its mission, and the mission itself.</p><p>That’s more revealing than asking whether everybody liked the screens.</p><h3>Where Salesforce fitted</h3><p>Salesforce entered the story as the platform used to build and test this proposed model, for any of my colleagues reading this no doubt you’re thinking “what an odd thing to say”, it’s fine, it should now be obvious to readers that I work for Salesforce, but just in case it’s not, or you didn’t know…so yeah I work for Salesforce.</p><p>The core model was built upon Nonprofit Cloud, with it providing the structures for people, referrals, case management, programmes, outcomes, volunteering and fundraising etc. Data 360 allowed the proof of concept to explore how identity and activity from different sources might be related. Experience Cloud provided the basis for a self-service portal. Marketing Cloud Advanced capabilities supported communications shaped by consent and preferences. Tableau Next connected operational, funding and outcome information for leaders.</p><p>The product names mattered to the architecture…kinda, but during the demonstration, they mattered only when they explained something the audience had just seen.</p><p>The relevant questions were about the combined design. Could information recorded during an assessment influence planning and later evaluation? Could volunteer availability be considered alongside programme demand? Could designated funding be connected to the work it supported? Could the organisation recognise one person across several roles while applying different access rules to each?</p><p>A broad platform creates somewhere to answer those questions, however it won’t answer them on the organisation’s behalf.</p><p>Salesforce can’t settle disputed ownership, repair a confused process or persuade staff to adopt a system they had no part in shaping. A larger technology footprint brings licence cost, implementation risk and greater dependence on disciplined governance, in some instances, some existing platforms may remain better suited to particular work. Replacing them simply to make the architecture diagram prettier would be an expensive form of interior decorating.</p><p>The future-state design was therefore deliberately mixed. Salesforce could provide a common operational and data foundation where that served the proposed model. Other systems could remain where they performed a clear function and exchanged information responsibly, and most importantly help unlock intrinsic value. Sorry, that sounded like a meta meme about Linkedin posts.</p><p>The point is, the aim should not always be to rip and replace the incumbent tech, unless it’s causing the digital equivalent to constant damp and wild mould growth. No dramatic platform deathmatch was required…early 2000s MTV gave us enough of those (remember MTV?).</p><h3>You mentioned AI, what was the AI was actually doing?</h3><p>AI appeared at several points in the proof of concept, but only after the underlying processes and data had been established…only after the underlying processes and data had been established…only after the underlying processes and data had been established.</p><p>I should say, as an aside, that I’ve got this bee in my bonnet about the “Agentic Nonprofit”, particularly “Agentic Fundraising”. There’s something genuinely interesting to explore here, and how those ideas could apply to the sector, so I suspect a longer piece will follow once I’ve developed my thinking a little further.</p><p><em>[Sorry, just a moment…an aside within an aside. The expression ‘bee in my bonnet’ when I was a kid I always thought this referred to a bee under the bonnet of a car, like how did it get there? It wasn’t until years later that I realised a bonnet was a type of hat — which I guess would be more annoying. Anyway, I digress.]</em></p><p>Where was I? Ah yes, AI. During the referral journey, an AI assistant (*ahem* Agentforce) could summarise information already provided by the person and help a member of staff see what remained unclear. After an interaction, it could help turn informal notes into an appropriate organisational record. Elsewhere, it could help staff interpret a more complicated history without opening every related record individually and going full Miss Marple.</p><p>The point is, that’s the context behind the AI examples. They weren’t a separate parade of features added because the session needed more sparkle, each sat inside a defined piece of work that a staff member was already responsible for completing. The boundaries mattered more than the animation.</p><p>Relevant records had to exist and be related correctly. Access needed to reflect permissions. The expected output had to be defined. Missing information had to be exposed rather than invented with great confidence and impeccable grammar. A person remained accountable for reviewing the result and deciding what happened next.</p><p>The AI didn’t assess eligibility, make safeguarding decisions or choose which service somebody should receive. Those decisions relied on professional judgement and information that could be incomplete, sensitive or contested. That isn’t to say those things aren’t possible, but those things need to be attached to clear and robust AI governance, AND data governance policies, also known as “the sexy stuff”.</p><p>The visible agent interaction took a few minutes to demonstrate, deciding what the agent could know, write and influence took rather longer.</p><p>That imbalance gets lost in many AI demos. The glowing interface receives top billing while data structure, permissions, process design and accountability are treated like the people listed during the credits of a Marvel film. They’re still doing the work; most of the audience has gone home.</p><p>Adding an agent to an unclear process doesn’t make an organisation AI-ready. It gives the confusion a faster user interface. Talking of Marvel, and I’ve said this before “good becomes great, bad becomes worse!”</p><p>In this proof of concept, the credible AI uses appeared only after the records, responsibilities and decision points were in place, and made sense.</p><p>There is a time-honoured principle in artificial intelligence: first teach the machine what it may do; then spend considerably longer explaining why it mustn’t do everything else. I’ve paraphrased several thousand governance documents there, saved you some time…you’re welcome.</p><h3>A complete demonstration is not an implementation plan</h3><p>The executive session needed to show enough of the future state for leaders to understand the larger proposition. That created another risk: an end-to-end demonstration can make the whole design look as though it should be implemented at once.</p><p>It shouldn’t.</p><p>The charity’s work covered specialist services, community support, a volunteer-intensive delivery model, fundraising, communications, data and reporting. Alongside these sat a highly specialised operational model with its own long-term lifecycle, dependencies and support requirements. Each area came with established processes, systems, ownership and history.</p><p>Attempting to replace all of it in one programme would produce an enormous amount of activity, followed by several steering committees and a general sense that everyone had aged a hundred years.</p><p>The architecture therefore needed to distinguish the common foundation from the order of implementation. The organisation could first agree how it represented a person, how roles related, which information could be used for which purpose and which definitions needed to remain consistent. It could then choose one business area in which to deliver a complete slice of work on that foundation.</p><p>That first area might cover referral through to programme participation. It could instead focus on volunteer recruitment, assignment and continued involvement. Fundraising might offer a different starting point. The right choice depends on urgency, feasibility, organisational readiness and where a coherent piece of change can produce evidence soonest.</p><p>Later areas could join the same foundation without reopening its basic assumptions every time.</p><p>This approach asks for more thought early on, a kind of ‘measure twice, cut once’ philosophy. Teams have to settle definitions, access and ownership questions that separate projects can politely avoid. Local delivery may appear slower at first, but truss fam…it works!</p><p>The sometimes assumed apparently quicker option is to let each department improve its own system and reconcile everything later. That invoice eventually arrives as duplicated integration, inconsistent reporting and another spirited discussion about whose person record is the real one, and of course plenty of bucks spent on very little. Just to labour the point, technical debt is a lot like glitter…introduced during a moment of optimism, discovered in places nobody remembers approving, and functionally impossible to remove.</p><p>Coming back to the PoC, it also needed to touch upon human contact where it served a purpose. Self-service could give people access to their information and greater control over practical tasks, but it shouldn’t convert sensitive or relationship-based work into a digital transaction because it’s convenient for the back office. A joined-up record didn’t and shouldn’t imply open access.</p><p>These constraints were part of the future state being demonstrated, and they stopped it floating off into the PowerPoint stratosphere…other slideware is available.</p><h3>What was I actually demonstrating?</h3><p>The session’s live demonstrations showed referrals, assessments, plans, programmes, volunteers, communications, fundraising, analytics and AI. Quite a lot for one sitting. Possibly too much, but that’s another article and a small cry for help.</p><p>Those screens were evidence for a set of organisational propositions.</p><p>Could the charity recognise a person across several roles without weakening privacy, consent or specialist practice?</p><p>Could programme delivery be understood alongside the volunteers and funding required to sustain it?</p><p>Could technology reduce administrative work while staff retained responsibility for sensitive decisions?</p><p>Could the organisation start with one business area while preserving a foundation that others could later share?</p><p>Seen in that context, the demonstration wasn’t a prediction of exactly how the charity would operate. Nor was it a disguised implementation plan. It was a configured argument about how the organisation might work, built with enough detail for people to find its weaknesses.</p><p>I used to think the hardest part of an ambitious demonstration was deciding how much technology to show.</p><p>I’m less certain now.</p><p>The harder work is identifying what the proposed system assumes about the organisation, then making those assumptions visible enough for people to poke at them. Some will prove sound. Others won’t survive contact with an ordinary Tuesday afternoon.</p><p>There’s probably a German word for the moment a beautiful architecture first encounters an ordinary Tuesday. If there isn’t, enterprise technology has finally identified a genuine gap in the market. Don’t steal my idea.</p><p>Better to discover those weaknesses while the system is still a proof of concept and the arrows on the diagram remain negotiable.</p><p>Software will encode a theory of the organisation either way.</p><p>It’s worth letting people argue with the theory before asking them to live inside it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a627bb30d08c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Mosquito in the Amber, and How Nonprofits and Vendors Talk Past Each Other About Data]]></title>
            <link>https://medium.com/@danocpearce/the-mosquito-in-the-amber-and-how-nonprofits-and-vendors-talk-past-each-other-about-data-d2b99ca6c21e?source=rss-7124ef8f0433------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2b99ca6c21e</guid>
            <category><![CDATA[nonprofit]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[salesforce]]></category>
            <dc:creator><![CDATA[Dan Pearce]]></dc:creator>
            <pubDate>Fri, 06 Feb 2026 16:06:19 GMT</pubDate>
            <atom:updated>2026-02-06T16:06:19.294Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oCuB618liraLkplAXgpxAA.png" /></figure><p>In conversations with some nonprofit organisations about data, there is often a curious sense of agreement. The same words surface repeatedly. Data quality. Single source of truth. Reporting. Insight. Value. Progress appears to be made quickly, heads nod in unison, and yet months later both sides can feel a quiet frustration that something fundamental was missed.</p><p>What is usually missing is not intent, capability, or effort. It’s a shared mental model of what data actually is…kinda fundamental, no?</p><p>Across many of my nonprofit engagements, a pattern emerges. Some understand data as something to be captured, stored, protected, and used within defined processes. Technology vendors, particularly those operating in modern cloud ecosystems…*ahem* like Salesforce, tend to see data as something that moves, evolves, combines, and creates new meaning over time. Both views are rational, both are shaped by history, incentives, and constraints. The difficulty begins when we assume these views are already aligned, and have agreed upon definitions. (I have a strong belief some of these assumptions are rooted in cultural norms and biases…but that’s definitely another article for another day!)</p><p>It’s also important to say that this does not describe the entire sector. Some nonprofits are already leading the way, experimenting with more dynamic approaches to data, and demonstrating what is possible when insight, technology, and organisational intent align. They remain, however, the exception rather than the norm…in my experience.</p><h3>Saying the Same Words, Meaning Different Things</h3><p>When a nonprofit says, “We need to get the data into the CRM,” the statement usually carries a sense of completion. Data enters a system, becomes governed, and is ready to support reporting, audits, and day-to-day operations. The CRM acts as a reliable container, and the job feels largely done.</p><p>When a vendor hears the same sentence, it often signals the beginning of a longer journey. Data enters a system as a starting point, then becomes enriched, connected to other sources, analysed, and reused in contexts that may not yet exist. The CRM is part of a wider fabric rather than the destination.</p><p>Neither interpretation is flawed per se. The challenge lies in the assumption that both sides are visualising the same end state.</p><p>This gap rarely shows up as conflict. It appears as subtle misalignment: initiatives that technically succeed while strategically underdeliver, or platforms that feel powerful yet underused. Over time, these moments accumulate and shape how organisations perceive the value of “data programmes”, and “platforms” altogether.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n3v_38os9eNwqOw0ARFGXQ.png" /><figcaption>(This one&#39;s for me and my brother, deep cut reference and in-joke…anyway)</figcaption></figure><h3>Why Data Became Static in the First Place</h3><p>Some nonprofits don’t arrive at their relationship with data by accident. Many organisations grew their data practices in response to accountability requirements, and system limitations, rather than analytical ambition. Funders, regulators, trustees, and boards asked for evidence, accuracy, and consistency, whilst donors <em>expected</em> transactional relationships. Systems were designed to answer questions about what happened, who was involved, and how resources were used.</p><p>Within this context, data behaves like a ledger. It records activity, preserves history, and supports transparency. Stability becomes a virtue, change introduces risk, and movement requires justification.</p><p>This paradigm makes sense when teams are small, budgets are constrained, and the consequences of error are high. It also explains why many nonprofits have deep expertise in capturing some types of data accurately while feeling less confident in transforming or reusing it beyond its original purpose.</p><h3>The Assumption Trap</h3><p>A sometimes common assumption follows naturally from this history: once data is captured and stored, it remains useful indefinitely. We all know that isn’t really true, we’ve all seen enough “gone-aways” and “hard bounces” within a campaign selection to really challenge this assumption…and yet.</p><p>In practice, data carries context, it reflects the question that existed at the moment of collection. As organisational priorities shift, new questions emerge, and external conditions change, so much so that that original context can fade. Fields that once felt comprehensive begin to feel insufficient. Reports answer yesterday’s needs while today’s decisions demand something else.</p><p>This is rarely framed as a data problem. It appears as an insight gap, a reliance on intuition, or a sense that “the data just isn’t there”, or “we have bad data…”. In reality, the data often exists, however its shape, freshness, and connectedness limit what it can become.</p><h3>The Quiet Wealth of Untapped Signals</h3><p>Some nonprofits frequently underestimate the range of signals already flowing through their organisations. Beyond donations and memberships, sit patterns of engagement: how supporters move through digital journeys, how volunteers return or disengage, how beneficiaries interact with services over time, how communities respond to specific messages or moments.</p><p>These signals rarely resemble the behavioural exhaust of large consumer platforms, like Facebook, or that other one, and they don’t need to. Their value lies in relevance rather than volume. When engagement, interaction, and outcome data can be viewed together, even at a modest scale, a richer picture begins to form.</p><p>The challenge is that these signals often live in different systems, arrive at different speeds, and resist simple reporting structures. Without a way to model and revisit them over time, their potential remains largely theoretical.</p><h3>Understanding Data Relationships in a Nonprofit World</h3><p>Discussions about first-party, second-party, and third-party data can feel abstract in a nonprofit setting. In practice, these categories map closely to everyday realities.</p><p>Supporter and service interactions form a strong base of first-party data. Partnerships, federated structures, and shared delivery models introduce second-party relationships. Public datasets, research sources, and demographic information provide a broader third-party context.</p><p>What matters less than the definitions, is the relationship between them. When data remains isolated within its original boundary, insight remains narrow. When it can be connected thoughtfully and ethically, it gains explanatory power.</p><h3>A Shifting Technology Landscape</h3><p>Over the past few years, the technology landscape has shifted toward platforms that treat data as a living asset rather than a static record. Tools such as Salesforce Data Cloud represent a broader movement toward systems designed to ingest, harmonise, and activate data across multiple use cases.</p><p>This shift changes the conversation…data becomes something that informs campaigns, analytics, and AI models simultaneously. It adapts as new sources appear and new questions emerge. The technology itself is increasingly accessible, however, the harder work sits in adjusting how organisations think about data ownership, stewardship, and purpose.</p><h3>The Mosquito in the Amber</h3><p>I sometimes think about how Jurassic Park (stay with me here) captures this tension. In the story, a mosquito preserved in amber becomes the unlikely bridge between the distant past and an imagined future. The mosquito itself is not the breakthrough. What matters is what it carries.</p><p>Inside the mosquito is blood [of a long since extinct dinosaur], inside that blood is DNA [again, dinosaur]. The value doesn’t sit in the insect as an object, but in the information embedded within it, contextual, extracted, and combined with other sources to create something entirely new.</p><p>Many nonprofits treat data in a similar way. Records are carefully preserved, protected, and admired in their original form. Yet the real potential lies in the metadata around those records: the timing, the sequence, the relationships, the behaviours implied but never explicitly captured. When that contextual information can be extracted, modelled, and combined with other data, it starts to reveal patterns that static records alone cannot.</p><p>In Jurassic Park, the scientists don’t stop at preservation. They extract what is useful, accept what is missing, and fill the gaps with other inputs. I should say, the results were dramatic, ethically questionable, and slightly unhinged…though the underlying principle remains sound..the dinosaurs, thankfully, should remain optional at your organisation.</p><h3>Looking Ahead</h3><p>A more data-driven nonprofit future brings promise and complexity in equal measure. Organisations gain earlier signals, clearer insight, and a stronger ability to adapt. They also face new responsibilities around ethics, consent, bias, and governance. Skills, culture, and trust become as important as architecture.</p><p>Some limitations will always remain. Nonprofits will never possess infinite data, or near infinite resources, nor should they aspire to. Their strength lies in purpose, proximity, and trust. Data serves best when it quietly enhances these qualities rather than overshadowing them.</p><p>The real question is not whether nonprofits should “do more with data.” It’s whether they are ready to let their data evolve beyond the moment it was captured. If data is allowed to move, combine, and grow, it becomes something more than a record of the past. It becomes a tool for shaping what comes next.</p><p>…and perhaps that is where the conversation truly begins.</p><h3>Author’s Note</h3><p>I’m a Solution Engineer at Salesforce, working within the UK &amp; Ireland Nonprofit industry vertical. Over the course of more than 12 years in the nonprofit sector, I have worked with a wide range of nonprofit organisations across fundraising, service delivery, membership, and advocacy. The reflections shared here are shaped by those experiences, and by conversations with organisations at very different stages of their data journeys. I saw Jurassic Park at the Cinema when I was 8 years old.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2b99ca6c21e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Campaigns to Connections: Embracing Audience-Based Marketing in Nonprofit Fundraising]]></title>
            <link>https://medium.com/@danocpearce/from-campaigns-to-connections-embracing-audience-based-marketing-in-nonprofit-fundraising-a5fb356a0cdd?source=rss-7124ef8f0433------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5fb356a0cdd</guid>
            <category><![CDATA[nonprofit-marketing]]></category>
            <category><![CDATA[nonprofit-technology]]></category>
            <dc:creator><![CDATA[Dan Pearce]]></dc:creator>
            <pubDate>Sat, 18 May 2024 15:58:02 GMT</pubDate>
            <atom:updated>2024-05-18T15:58:02.388Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JoMf78Ui_FSil-5Gv3ieAg.png" /></figure><p>I think many would agree that the typical traditional strategy within nonprofit fundraising often revolves around product-centric approaches; specific initiatives on traditional channels with a clear ask or call to action, such as DRTV or digital ads for ongoing appeals, postal and digital mailers, and events. These product-based campaigns are built around a single theme or ask, designed to attract donations through a direct appeal. However, as digital transformation reshapes how we connect, a new marketing paradigm is gaining ground among UK nonprofits. This new strategy, audience-based marketing, focuses on engaging supporters more deeply by understanding their individual preferences and motivations. This article looks into how this shift is changing the game, the tech that’s making it happen, and what nonprofits stand to gain or the challenges to be faced from this new approach.</p><h3>Understanding the Shift: From Campaigns to Connections</h3><p>Old-school nonprofit marketing was (still is) pretty straightforward. It centred on big, broad campaigns that hit up a lot of people at once through stuff like mail, TV, or events. These campaigns were direct and made it clear what they wanted: your support, right then and there.</p><p>Now, things are shifting towards audience-based marketing. Nonprofits are focusing less on one-off donations, or even recurring donations, and more on building ongoing relationships. This means getting to know supporters through various ways, not just one campaign (I’d go as far as to suggest that the concept of the supporter persona is also being flipped on its head). Using digital tools, platforms and services, nonprofits can figure out what supporters care about and offer them content that really resonates and speaks to them.</p><h3>Contrasting the Approaches</h3><p>The big difference between the old and new strategies is focus. Traditional campaigns shot for a wide audience with a single message. Audience-based marketing, though, is all about the details. It’s personalised. Instead of sending the same old letter to everyone who’s ever donated, this approach uses data to figure out who’s interested in what and tailors the message to match.</p><p>This more personal touch doesn’t just make supporters happy — it retains them. When supporters feel like they’re truly understood, they’re more likely to keep engaging, donate more often, and even spread the word about the cause. This is especially true for millennials and Gen Zers, who aren’t interested in just transactional relationships. They want deeper connections and meaningful experiences with the causes they care about. Audience-based marketing taps into this desire by creating personalised and engaging interactions, making these younger supporters feel valued and more connected to the nonprofit’s mission.</p><h3>Technological Boosts</h3><p>As UK nonprofits shift from traditional product based marketing to audience-based marketing, they’re starting to use a load of advanced tech that used to be way too complex or expensive. Now, these technologies are cheaper, intuitive and key to their work, making tough tasks easier and giving them a deeper understanding of what supporters want.</p><p>At the centre of this tech revolution are Customer Relationship Management (CRM) systems like Salesforce (and yes, other CRMs are available). Think of CRMs as the brains of the operation, storing detailed records of each supporter’s interactions, preferences, and activities. Just like our brain remembers and processes information about the people we know, CRMs help nonprofits tailor their communications to each supporter perfectly.</p><p>However, the brain doesn’t work alone! Enter Data Management Platforms (DMPs) and Customer Data Platforms (CDPs). Imagine the DMP as the digestive system, taking in vast amounts of raw data, processing it, and extracting valuable insights for broad targeting and advertising…almost like food for thought (boom!). Meanwhile, the CDP acts like the heart, pumping integrated data from various sources to create unified, comprehensive profiles of each supporter. Just as the heart ensures all parts of the body are connected and working together, the CDP ensures all data points about a supporter are linked, giving nonprofits a complete and cohesive understanding of each individual.</p><p>Together, this tech trio; brain, digestive system, and heart, enables nonprofits to tailor their approach in ways they could only dream of before, making supporter engagement more personalised and effective…but wait, there’s more!</p><p>Marketing automation platforms naturally play a huge part, changing the game by handling the repetitive stuff and making sure campaigns are on point across different channels. These platforms make sure the right messages get to the right supporters at just the right time, making things run smoother, whilst making each interaction more relevant, strengthening relationships with supporters.</p><p>Alongside automation, data analytic tools are super important in helping nonprofits make smart choices, often referred to as being data-driven (side note, being data-driven is great and all, but without purpose you’ll only be driven around in circles). These tools look at data patterns to identify audience segments, and predict what the audiences and supporters within them might do next and figure out the best ways to keep them engaged. With predictive AI, nonprofits can anticipate supporter needs and behaviours with greater accuracy. We are now seeing how generative AI can be used to create personalised content for different audience segments, making engagement even more effective. With these insights, nonprofits can better meet supporters’ needs and plan campaigns that are more likely to get everyone excited.</p><p>The glue that holds all these tools together is often the Integration Platform, built on API-driven architecture principles. These principles greatly increase interoperability between systems, scalability, and the ability to innovate rapidly. By connecting CRMs, DMPs, CDPs, marketing, and data analytics tools, nonprofits can keep supporter info up-to-date and accessible across all channels. This integration reduces data mistakes and makes marketing efforts more effective. An API-driven architecture ensures seamless data flow, enabling near real-time updates and consistent supporter experiences across all touchpoints. This cohesive set up allows nonprofits to leverage the full power of their tech stack, from predictive analytics to generative content creation, enhancing their overall strategy and execution.</p><h3>Navigating the Change</h3><p>So we’ve talked quite a bit about the technology, and no doubt if you’re reading this you’ve probably already sat through a few “art of possible” demonstrations, and “visions of the future” keynotes… but let’s be real, shifting from product-based to audience-based marketing is a big move for any nonprofit. It means changing up the “old” ways of doing things, and sometimes this includes changing the inner workings of the organisation itself. This might not seem obvious, after all, aren’t we just talking about starting to engage with supporters on a more personal level and all that jazz? Well, yes, but this is also a mindset and behavioural shift, as much as it’s a technology and marketing shift.</p><p>To kick off this change, nonprofits need to truly understand their supporters. Leveraging advanced data tools and customer data platforms (CDPs) like Salesforce Data Cloud, Twilio Segment, and Adobe Real-Time CDP allows organisations to delve deep into supporter behaviours, preferences, and patterns. This rich data helps in creating detailed supporter personas, which are fictional representations of ideal supporters based on real data. Segmenting the supporter pool into groups with similar characteristics is crucial, as it allows for the development of tailored communication strategies that resonate with each group’s specific interests and needs.</p><p>For instance, some supporter personas might be “Digital Natives” who prefer interactive, digital content like emails, social media campaigns, or online webinars. Others might be “Traditionalists” who appreciate the personal touch of printed materials, personalised letters, or in-depth reports. Understanding these preferences is key to crafting messages that truly connect with supporters on an individual level, it’ll also help determine what your tech stack could or should look like.</p><p>Implementing these strategies requires consistency across all touchpoints. Whether a supporter interacts with the nonprofit through email, social media, a website, or face-to-face events, the message should be coherent and reflect the nonprofit’s core values and mission. Integration platforms such as Zapier or Mulesoft AnyPoint Platform are vital here; they ensure that all systems; from CRM to marketing automation tools are synchronised, providing a seamless and unified supporter experience.</p><p>A clear vision is essential for guiding this transformation. Leadership must articulate this vision compellingly and ensure it is well-communicated across the organisation. Everyone should understand not just what changes are happening, but why these changes are crucial for the nonprofit’s future success. This vision should highlight the benefits of audience-centred marketing, such as stronger supporter relationships, increased engagement, and better alignment with supporter needs and values. (I want to just add at this point that any vision should be open to challenge, and that this should be encouraged and embraced, albeit constructively and respectfully. Basically, don’t get upset if not everyone agrees with you, debate and discuss)</p><p>Training is another cornerstone of this transformation. It’s not enough to just introduce new tools; staff need to understand how to use it! Training sessions should cover the technical aspects of new systems but also emphasise the importance of these changes for building stronger, more meaningful supporter relationships. Being able to explain the concepts and principles that underpin the tech, what you are doing and why is also key here.</p><p>It almost goes without saying that change management is another integral part of this transition. Resistance is natural, but it can be managed by actively listening to concerns, addressing them constructively, and fostering an inclusive environment where everyone feels invested in the new direction. Open communication channels and regular feedback loops are essential for smoothing the transition and ensuring that staff feel heard, valued and fully onboard with the vision.</p><p>Monitoring and evaluation are critical as new audience-based fundraising methods are rolled out. Setting SMART goals; Specific, Measurable, Achievable, Relevant, and Time-bound — helps nonprofits clearly define what success looks like in this context. Examples of key performance indicators (KPIs) might include supporter retention rates, engagement metrics (such as open rates, click-through rates, and social media interactions), and donation amounts from segmented campaigns. Regularly assessing progress involves tracking these KPIs to see which strategies are resonating with various supporter segments. Conducting A/B testing on different campaign elements (e.g., email subject lines, content formats) can help refine approaches based on what works best for each segment. Gathering supporter feedback through surveys or direct conversations can also provide qualitative data to complement quantitative metrics.</p><p>Being flexible and ready to adapt based on this continuous feedback and performance data ensures the organisation remains responsive to supporter needs and preferences. This iterative process of monitoring, evaluating, and refining strategies helps maintain alignment with the evolving expectations of the supporter base and enhances the effectiveness of audience-centred fundraising efforts.</p><p>So what does good look like during the shift from product-based to audience-based fundraising marketing? Well, it’s an organisation that uses supporter data to create personalised, engaging experiences for different supporter segments. Where every communication channel; emails, social media, face-to-face interactions; delivers a consistent, compelling message that reflects the nonprofit’s core values and connects with various audiences. It’s a team that is not only skilled in using advanced data tools and integration platforms but is dedicated to understanding and meeting supporter needs through continuous learning and adaptation. It’s an organisation united by a clear vision, effectively communicated by leadership…that everyone understands and works toward. Ultimately, it’s a nonprofit that stays agile, continually evolving its strategies based on ongoing monitoring, evaluation, and supporter feedback to build deeper, more meaningful connections with its supporters…and remember, being agile is not a methodology, but a state of mind baby.</p><h3>Understanding the Challenges and Benefits</h3><p>As nonprofits start to transition towards and the embracing of audience-based marketing, it’s key to understand both the challenges and the benefits of what this will entail.</p><p>One big challenge is dealing with lots of data…lots and lots of data. Data, data everywhere. Nonprofits need to be able to manage and understand huge amounts of information, which means they will no doubt need to invest in data warehousing, eventually data lakes, related tooling, and also the skills, expertise, and policies to maximise these investments.</p><p>Changing the way people think at the nonprofit can also be tough. Moving from the old-school way of doing things to a new, data-driven approach means changing habits and ways of thinking that have been around for a long time. This can cause some pushback since it asks everyone to try new things and work differently. It’s important to stress that we shouldn’t be advocating for throwing practitioners of the “old school” to the trash heap, on the contrary, there is a great deal of value for ‘old’ knowledge and experience, use and embrace it.</p><p>As mentioned above, having a clear and transmittable vision is vital, without one, it’s difficult to know what is important, what good looks like, what data and information is needed, and as a result it makes making decisions difficult (sometimes impossible).</p><p>Even with these challenges, switching to audience-based marketing has some tasty benefits. By focusing on what each supporter likes, nonprofits can create stronger connections. This usually means supporters stick around longer and give more over time, and give more of their time. This approach also lets nonprofits use their resources smarter. Instead of spreading their effort and money thin over big, general campaigns, they can target their resources better and get more done with less. This not only saves money but also makes their messages more spot-on for each supporter, making each person feel special and valued (real talk, they are!), and connecting people with the things they care about, and sometimes even to each other).</p><h3>Conclusion</h3><p>The transition from product-based to audience-based fundraising marketing represents a profound shift for UK nonprofits. It’s a move from broad, one-size-fits-all campaigns to a more nuanced, data-driven approach that seeks to build lasting relationships with supporters. This evolution requires not only adopting advanced technologies but also fostering a cultural shift within the organisation, embracing continuous learning, adaptability, and a clear, compelling vision.</p><p>Those nonprofits that commit fully to this new paradigm stand to reap significant rewards. By understanding and responding to the unique preferences and motivations of their supporters, these organisations can craft personalised experiences that deepen engagement and loyalty. They will be better equipped to harness the full potential of their data, making smarter, more informed decisions that maximise the impact of their resources.</p><p>This journey is not without its challenges. Managing vast amounts of data, overcoming resistance to change, and ensuring that all staff are aligned with the new vision requires thoughtful planning and execution. However, the benefits; stronger supporter relationships, increased engagement, and more efficient use of resources, make it a worthwhile endeavour.</p><p>Those who truly commit to this new way will likely lead the pack, showing innovative, successful ways to connect with supporters. They will set new standards for the nonprofit sector, demonstrating that audience-centred marketing is not just a trend, but a transformative approach that can enhance supporter relationships and drive long-term success. As the landscape of fundraising continues to evolve, the nonprofits that embrace this change will be the ones to watch, pioneering new paths to engagement and impact.</p><p>The question then becomes, are you ready to lead the charge and redefine how your organisation connects with its supporters? The future of fundraising is here, and it’s audience-centred.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5fb356a0cdd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Tech-savvy Nonprofit: Oh No, Not Another Article About Digital Transformation!]]></title>
            <link>https://medium.com/@danocpearce/building-a-tech-savvy-nonprofit-oh-no-not-another-article-about-digital-transformation-a595148efcf7?source=rss-7124ef8f0433------2</link>
            <guid isPermaLink="false">https://medium.com/p/a595148efcf7</guid>
            <category><![CDATA[nonprofit-technology]]></category>
            <category><![CDATA[marginal-gains]]></category>
            <category><![CDATA[nonprofit]]></category>
            <category><![CDATA[mach-architecture]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Dan Pearce]]></dc:creator>
            <pubDate>Mon, 19 Feb 2024 19:30:24 GMT</pubDate>
            <atom:updated>2024-02-19T20:21:25.070Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qj1iS0NBXJWGxgfp8ox0vQ.png" /><figcaption>Image generated with DALL E 2</figcaption></figure><p><strong>Trigger Warning: I’m going to talk about digital transformation…you have been warned!</strong></p><p>In the ever-shifting sands of today’s digital landscape, it seems like every week there is a new “innovation” or fingy-ma-bob, while the nonprofit sector stands at a crossroads. The horizon is ripe with opportunities for enhanced efficiency, broader reach, and deeper engagement, particularly with those pesky digital-native younger generations. Yet, for organisations whose roots are deeply embedded in traditional operational soils, the journey towards digital transformation can appear as formidable as charting a course through shark infested waters, or simply browsing through Twitter these days.</p><p>Enter the guiding principles of MACH architecture — Microservices, API-first, Cloud-native, and Headless. Like a compass pointing toward technological north, these principles offer a strategic map for navigating the complexities of digital transformation. Coupled with the philosophy of marginal gains (we’ll go deep into this in a bit)— the pursuit of small, continuous improvements, illuminate a path where each step, no matter how seemingly insignificant, contributes towards a larger goal of organisational growth and mission fulfilment…<strong>wait wait don’t go!</strong></p><p>Digital transformation within the nonprofit sector is not just a case of buying and adopting new technologies, it’s a fundamental reimagining of how organisations operate, engage, and deliver in a digital-first world. By embracing the flexibility, scalability, and innovation that MACH architecture facilitates, nonprofits can construct a technological ecosystem as adaptable and resilient as the fast-paced digital environment itself. Also, with that philosophy of marginal gains — we’ll come on to this in a bit I promise, we’ll start to see that even the smallest steps toward digitisation can accumulate, leading to significant benefits over time.</p><p>So with that, in this article we’ll explore the key steps to building a tech-savvy nonprofit through digital transformation, emphasising the importance of MACH architecture and marginal gains. Whether you’re just beginning your digital transformation journey, looking to refine your approach, or reading this on the train after one too many after work drinks, I hope this article will provide valuable insights and practical strategies to help your nonprofit thrive in the digital age.</p><h3>Understanding Digital Transformation in Nonprofits</h3><h4>Definition and Importance</h4><p>Yeah I know, the phrase “digital transformation” is often seen as a bit of a bull**** business buzzword in bull**** business bingo, however if we can overlook that for a moment we’ll start to appreciate that digital transformation within the nonprofit sector is an imperative shift, enabling organisations to enhance operations, engage more effectively, and deliver greater value in an increasingly digital world. This transformation integrates digital technology across all areas of a nonprofit, fundamentally changing how it functions and interacts with its supporters, beneficiaries, and stakeholders. The importance of this shift is underscored by findings from Capgemini, which noted that a significant majority of businesses view digital transformation as crucial to maintaining a competitive edge, a perspective that holds true for the nonprofit sector as well (Futr, n.d.).</p><h4>Overcoming Barriers to Digital Transformation</h4><p>Over 10 years of experience within this sector has taught me that adopting digital technologies presents several challenges for your typical nonprofit, from resource constraints to cultural resistance, skill gaps, and data management complexities. A report by NetChange Consulting revealed that many nonprofits struggle with integrating technology effectively into their strategy, highlighting the need for a rethink of strategic approaches (Futr, n.d.). I should note at this point that there is of course a cost consideration here, but I won’t be going into into the details on that in this article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vw9I5sFyN9vI9UJVHDoDsw.png" /><figcaption>Examples of challenges adopting digital technologies within a nonprofit organisation.</figcaption></figure><h4>Benefits of Digital Transformation</h4><p>With grand statements like <em>“… digital transformation within the nonprofit sector is an imperative shift”</em>, or “<em>…the [digital] horizon is ripe with opportunities</em>”, what are the actual benefits of digital transformation, and how do those benefits resonate with nonprofit organisations?</p><h4>Elevating Operational Efficiency</h4><p>Let’s start with elevating operational efficiency. The push towards automating simple or even complex tasks is a game-changer for many nonprofits. Imagine reallocating the countless hours people spend on manual data entry to strategic initiatives or developing new programmes and services that directly contribute to the mission. This shift not only optimises resource allocation but also empowers staff to invest their talents where they truly matter, pushing the boundaries of what’s possible in mission-critical activities, especially knowing how difficult it can be to attract and retain the best and brightest within the sector.</p><h4>Expanding Reach</h4><p>Leveraging digital tools and capabilities now presents the opportunity for nonprofits to cast a much wider net, engaging with potential donors, volunteers, beneficiaries, and ambassadors across the globe. Missions originally focused on “local”, or single issue challenges can touch and inspire other communities at home or across the globe. Universal challenges like climate change, or social justice come to mind. This expanded reach is instrumental in building a diverse supporter base and amplifying an organisation’s community impact, effectively turning local missions into global movements.</p><h4>Deepening Engagement</h4><p>We have seen over the last 15 or so years that personalisation is key to forging meaningful connections. Through technology, nonprofits can tailor their communication, making every donor feel seen and every volunteer feel valued. This level of personalised engagement deepens relationships, fosters loyalty, and cultivates a community of supporters who are as invested in the cause as you are. This shift has been further exemplified by a rapid generational move from older transactional forms of donor relationships, to more experiential ones.</p><h4>Harnessing Data-Driven Insights</h4><p>In a world inundated with information…maybe sometimes too much, data is the compass that guides strategic decision-making. Digital transformation equips nonprofits with the tools to collect, analyse, and act on data like never before. We’ve gone from databases, to data warehouses, to data lakes, to data lake houses. These insights enable organisations to refine their strategies, ensuring that efforts are not just well-intentioned but are also impactful, driving initiatives that resonate with their audience and maximise resource utilisation.</p><h3>Real-World Examples of Digital Transformation with the Nonprofit Sector</h3><h4><strong>Chatbots for Fundraising and Engagement</strong></h4><p>During the COVID-19 pandemic, UK adults expressed a willingness to donate more, despite economic uncertainties. Charities like Mencap have leveraged chatbots to automate fundraising activities and provide information on learning disabilities, demonstrating the potential of digital tools to enhance donor engagement and service delivery (Futr, n.d.).</p><h4><strong>Data Analytics for Targeted Campaigning</strong></h4><p>The effective use of data analytics allows nonprofits to understand donor habits and optimise fundraising efforts. Organisations that leverage advanced analytics are found to be more effective, underscoring the value of data in enhancing decision-making and campaign strategies (Futr, n.d.).</p><h4><strong>Digital Solutions for Service Delivery</strong></h4><p>The Good Exchange created a matchmaking portal with a digital solution to help funders find worthwhile causes, demonstrating how digital tools can transform donor journeys and user experiences. This project, which involved consolidating databases and migrating to Microsoft’s Azure Cloud platform, highlights the transformative impact of digital adoption on operational efficiency and service delivery (One Beyond, n.d.).</p><h4><strong>Local Government Digital Transformation</strong></h4><p>Newham Council’s digital transformation initiative aimed at improving online services for housing, homelessness, and children’s services exemplifies the broader applicability of digital strategies. By partnering with digital specialists and adopting an agile approach to service design, the council enhanced the user experience for local residents, showcasing the potential for digital tools to significantly improve public sector services (GOV.UK, 2017).</p><h3>The Role of MACH Architecture in Nonprofits</h3><p>Finally the bit you were waiting for, MACH architecture…sounds delicious! MACH architecture represents a significant shift in IT infrastructure, aligning perfectly with the dynamic requirements of the nonprofit sector. The components of MACH — Microservices, API-first, Cloud-native, and Headless — collectively contribute to a more agile, flexible, and scalable technology environment for nonprofits. The “Enterprise MACHified” 2022 study by the MACH Alliance highlights the growing adoption and investment in MACH technologies by senior technology decision-makers in the UK, indicating a 19% increase in companies moving away from monolithic to best-of-breed systems. This trend underscores the recognition of MACH’s potential to meet evolving digital demands (MACH Alliance, 2022).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L2DKqzAemg_UgLOpYN2M4w.png" /><figcaption>Image generated with DALL E 2</figcaption></figure><h3>Overview of MACH Architecture Components</h3><p>The beauty of Microservices lies in their ability to break down complex applications into smaller, independent units, allowing for targeted updates and improvements without the risk of widespread disruption. This modular approach ensures that nonprofits can maintain and enhance their digital services more effectively. Services are typically organised around business capabilities, with each service often owned by a single, small team. These microserves can then be consumed across multiple platforms and applications, enhancing the organisation’s agility and responsiveness. By decentralising control and distributing the workload, nonprofits can accelerate development cycles, making it easier to implement new features or adapt to changing needs. This flexibility is crucial for responding promptly to donor demands, regulatory changes, or emerging trends. Ultimately, microservices enable nonprofits to innovate faster, providing services that are more aligned with their mission’s goals and the expectations of their supporters.</p><p>Adopting an API-first strategy is all about prioritising seamless communication between various systems and services. For nonprofits, this means the ability to integrate and enhance their digital ecosystem effortlessly, from managing donor databases to streamlining social media interactions, thereby boosting operational efficiency and data exchange. More often than not this means opening up alternatives to the point to point integrations that hurt me so much back in the day.</p><p>The cloud-native approach leverages the cloud to scale resources as needed, offering nonprofits a way to reduce IT costs, enhance security, and remain adaptable to changing operational demands without the burden of heavy upfront investments, and hotter than hell server rooms on the top floor.</p><p>Finally, headless architecture separates the frontend user experience from the backend data management. This separation is crucial for nonprofits aiming to update their digital presence and adopt new technologies without the need for complete system overhauls, ensuring a consistent user experience across all digital platforms.</p><h4>Advantages of MACH for Nonprofits</h4><p>Implementing MACH architecture can significantly enhance a nonprofit’s technological ecosystem. It introduces agility, allowing organisations to quickly adapt to new technologies and evolving user expectations. The flexibility offered by MACH makes integrating new tools and platforms straightforward, improving functionality and user experience, often reducing cost in the process. Its scalable nature means that nonprofits can efficiently manage varying operational demands without performance hitches. Moreover, MACH encourages innovation, enabling nonprofits to explore new digital engagement strategies and tools, thereby enriching how services are delivered and how supporters and stakeholders are engaged.</p><h3>Embracing the Concept of Marginal Gains</h3><p>One of the challenges of being a Solution Engineer is being able to highlight all the amazing things your platform and ecosystem can do; often referred to as the “Art of Possible”, whilst also articulating how to actually do it in reality. The answer (IMO) is to start small and iterate from there (please pick your own battles with what constitutes as MVP, I’m not touching that one!).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lq9kVn86nmniBs137lY2Uw.png" /><figcaption>Image generated with DALL E 2</figcaption></figure><p>With the technological shift brought about by MACH architecture, the concept of marginal gains plays a vital role in the continuous improvement of nonprofit operations and technology adoption. For those not familiar, marginal gains, introduced by Dave Brailsford in the context of British Cycling, provides a powerful framework for achieving substantial improvement through small, continuous enhancements. Brailsford’s philosophy, centred on the “aggregation of marginal gains,” revolutionised British Cycling by focusing on tiny margins of improvement in every conceivable aspect related to cycling. The principle is simple yet profound: if you break down everything you can think of that goes into an activity (in this case, cycling), and then improve each element by just 1%, the cumulative effect can lead to significant overall progress (Clear, n.d.).</p><p>This approach led to extraordinary successes for Great Britain’s professional cycling team, demonstrating the power of focusing on small details. By making adjustments across various aspects, including equipment, rider health, and even the minutiae of hand washing techniques to prevent illnesses, Brailsford’s team achieved a remarkable transformation, culminating in numerous world championships and Olympic medals, as well as multiple Tour de France victories (Clear, n.d.).</p><p>For nonprofits embarking on digital transformation, adopting the marginal gains philosophy means looking for incremental improvements across all facets of their operations and technology adoption. This could range from refining email campaigns for better engagement, optimising website performance for faster loading times, to streamlining the online donation process for enhanced user experience. Each small step, inspired by the marginal gains approach, contributes to a larger impact, fostering a culture of continuous enhancement and adaptation.</p><p>By focusing on making 1% improvements regularly, nonprofits can adopt a proactive approach to digital transformation, ensuring that they are constantly moving forward and adapting to new challenges and opportunities. This philosophy not only encourages innovation but also ensures that organisations remain agile and responsive in a rapidly evolving digital landscape.</p><h3>Key Steps to Digital Transformation Using MACH Architecture and Marginal Gains</h3><p>So we’ve gone about defining digital transformation, MACH and marginal gains within a nonprofit context, but how should all of this be approached? As one can imagine embarking on a digital transformation journey entails strategic planning and execution, also blood, sweat and tears! To implement this approach effectively, I’ve tried to outline the key steps involved (below) — this is drawn from a mixture of personal successes and epic failures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WjDkg5pNG36UOtSIN5oDSw.png" /></figure><p>These steps emphasise a holistic approach to digital transformation, ensuring that every facet of an organisation’s digital strategy is continuously refined and aligned with overarching objectives. By leveraging specific tools and methodologies at each step, nonprofits can systematically enhance their digital capabilities, improve stakeholder engagement, and ultimately achieve a greater impact in their missions. The goal here is to help demonstrate a structured yet flexible approach that enables organisations to navigate the digital transformation journey with clarity and purpose, ensuring that technology serves as a powerful enabler of their goals and values.</p><h3>What Good Could Look Like</h3><p>In the table below I’ve gathered examples that serve to illuminate the path toward operational excellence, increased stakeholder engagement, and enhanced mission fulfilment, essentially what good could look like for nonprofit digital transformation. Through careful planning, implementation, and continuous refinement, nonprofits can demonstrate their capacity to not only navigate the complexities of digital transformation but to thrive within them, setting a benchmark for what success can look like in the digital age.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XI__0kgkFxYtIVKeSJg2MQ.png" /></figure><h3>Forward-Looking Advice for Sustainable Digital Transformation</h3><p>We’re almost there. As you embark on the journey of digital transformation within your nonprofit, it’s crucial to adopt a mindset that embraces continuous learning and innovation. Remember, digital transformation isn’t a destination but an ongoing path of growth and adaptation, and unfortunately the similarities with Waynestock ends there, “if you book them…” <em>they won’t come</em>. Encourage your team to experiment, learn from every outcome, and stay open to exploring new technologies and methodologies. This approach will keep your organisation agile and well-equipped to navigate the ever-changing digital landscape.</p><p>Prioritising user experience and accessibility is another must. As you enhance your digital footprint, make every effort to ensure that your websites, apps, and digital content are not only engaging and intuitive but also accessible to everyone, including those with disabilities. This focus not only expands your reach but also fosters deeper connections with your audience, allowing more people to access and benefit from your services.</p><p>Mate, data! Leveraging data should be at the heart of your decision-making process. In today’s digital era, data is invaluable for crafting informed strategies and making impactful decisions. Invest in robust data management tools and analytics to effectively capture, analyse, and utilise data. This will enable you to tailor your programmes and communications for maximum impact, ensuring that you’re using your resources in the most efficient way possible.</p><p>Collaboration is also a cornerstone of successful digital transformation. Forge partnerships with technology companies, other nonprofits, and sector experts to enhance your digital efforts. These alliances can offer new technologies, skills, and insights, driving more innovative solutions and broadening your impact. It almost goes without saying, partnerships can foster shared learning and joint initiatives, amplifying the benefits of your digital transformation endeavours.</p><p>Staying abreast of digital trends and opportunities is essential. The digital domain is constantly evolving, with new technologies and practices emerging all the time. Keep an eye on these developments and evaluate how they can be integrated into your digital strategy. Being proactive about leveraging the latest technologies can significantly boost your operations, engagement efforts, and service delivery.</p><p>Finally, and most importantly…<strong>if things start going sideways it’s ok to pause or even stop!</strong></p><h3>Conclusion</h3><p>The journey of digital transformation for nonprofits, driven by the adoption of MACH architecture and the principle of marginal gains, represents a significant shift towards more efficient, expansive, engaged, and dare I say it…more interesting operations. This shift not only addresses the need to modernise operational frameworks and overcome technological barriers but also highlights the importance of data-driven strategies for impactful outcomes. Through practical examples, we’ve had a flash of ankle at how digital tools can bolster service delivery, engagement, and mission fulfilment.</p><p>I hope this article has provided food for thought for your digital transformation journey, it’s a challenging one for sure, but one filled with endless possibilities and opportunities. And with that I wish you good luck, and leave you with a quote from the series finale of the Star Trek TNG:</p><p>“<em>…In any case, I’ll be watching. And if you’re very lucky, I’ll drop by to say hello from time to time. See you… out there!</em>” — <strong>Q</strong></p><h3>References:</h3><ul><li>Futr. (2021). <em>Essential Guide to Nonprofit Digital Transformation</em>. <a href="https://futr.ai/the-essential-guide-to-digital-transformation-for-nonprofits-and-charities">https://futr.ai/the-essential-guide-to-digital-transformation-for-nonprofits-and-charities</a></li><li>Unit4. (2023). <em>Nonprofits on the Road to Digital Transformation</em>. <a href="https://digitalisationworld.com/news/66293/nonprofits-on-the-road-to-digital-transformation">https://digitalisationworld.com/news/66293/nonprofits-on-the-road-to-digital-transformation</a></li><li>Unit4. (2024). <em>Nonprofits are on the road to digital transformation</em>. <a href="https://www.unit4.com/blog/nonprofits-are-road-digital-transformation">https://www.unit4.com/blog/nonprofits-are-road-digital-transformation</a></li><li>GOV.UK 2017. Supporting Newham Council’s digital transformation. <a href="https://www.gov.uk/government/case-studies/supporting-newham-councils-digital-transformation">www.gov.uk/government/case-studies/supporting-newham-councils-digital-transformation</a></li><li>MACH Alliance. (2022). <em>Global 2022 Research Shows MACH Adoption Is High On The Agenda for Tech Leaders</em>.<a href="https://machalliance.org/insights/our-2022-research-shows-mach-adoption-is-high-on-the-agenda-for-tech-leaders"> https://machalliance.org/insights/our-2022-research-shows-mach-adoption-is-high-on-the-agenda-for-tech-leaders</a></li><li>IMPACT. (n.d.). <em>Demystifying MACH — understand the acronym that will flex up your IT architecture</em>.<a href="https://impactcommerce.com/"> https://impactcommerce.com</a></li><li>MACH Alliance. (2023). <em>Meet Your MACH Alliance Ambassador: Mark Elliott, Chief Architect at Boohoo Group PLC</em>.<a href="https://machalliance.org/insights/meet-your-mach-alliance-ambassador-mark-elliott-chief-architect-at-boohoo-group-plc"> https://machalliance.org/insights/meet-your-mach-alliance-ambassador-mark-elliott-chief-architect-at-boohoo-group-plc</a></li><li>Clear, J. (n.d.). <em>Marginal Gains: This Coach Improved Every Tiny Thing by 1 Percent</em>.<a href="https://jamesclear.com/marginal-gains"> James Clear</a></li><li>Champions Speakers. (n.d.). <em>The Ultimate Guide to Marginal Gains</em>.<a href="https://champions-speakers.co.uk/"> Champions Speakers</a></li><li>Wikipedia. (n.d.). <em>Dave Brailsford</em>.<a href="https://en.wikipedia.org/wiki/Dave_Brailsford"> Wikipedia</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a595148efcf7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Constructing a Scalable and Effective MEAL Toolkit: A Lego-Inspired Approach]]></title>
            <link>https://medium.com/@danocpearce/constructing-a-scalable-and-effective-meal-toolkit-a-lego-inspired-approach-7628539c7f76?source=rss-7124ef8f0433------2</link>
            <guid isPermaLink="false">https://medium.com/p/7628539c7f76</guid>
            <category><![CDATA[international-development]]></category>
            <category><![CDATA[strategic-thinking]]></category>
            <category><![CDATA[nonproft]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Dan Pearce]]></dc:creator>
            <pubDate>Tue, 30 Jan 2024 20:31:58 GMT</pubDate>
            <atom:updated>2024-01-30T20:31:58.354Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MZECp7X04OYo2xIpz2l4oA.png" /><figcaption>Image generated with DALL E 2</figcaption></figure><h3>Understanding the MEAL Toolkit</h3><p>Throughout 2023 and into my 2nd year as Lead Solution Engineer at Salesforce, I’ve had the opportunity to collaborate with an important global children’s nonprofit. This experience not only enriched my perspective of the sector, but also introduced me to the significance of a Monitoring, Evaluation, Accountability, and Learning (MEAL) Toolkit. A MEAL Toolkit is an integrated set of tools designed to systematically gather, analyse, and use data to improve the effectiveness and accountability of nonprofit programmes. It’s pivotal for ensuring that programmes are not just well-intentioned but are actually making a tangible difference, and in example of my recent experience, a tangible difference in the lives of children across the world. The importance of such a toolkit cannot be overstated — it’s the compass that guides nonprofits in navigating the complex terrains of international development and humanitarian aid, in an increasingly turbulent world. This article proposes a theoretical, yet practical approach to building a scalable, sustainable business and technology architecture for a MEAL Toolkit, inspired by countless hours of playing with Lego…both as a kid and now with my daughter.</p><h3>Crafting the Business Architecture</h3><h4>Strategic Alignment: Laying the Foundation</h4><p>The foundation of our Lego-inspired MEAL Toolkit architecture is strategic alignment. Like interlocking the base blocks of a Lego structure, this involves ensuring every aspect of the toolkit aligns perfectly with the nonprofit’s mission and strategic goals. This alignment is more than procedural; it’s about embedding the essence of the nonprofit’s objectives into every tool and process. A practical manifestation of this would be a visual dashboard within the toolkit that maps each programme, programme’s purpose, activities, and outcomes to specific organisational goals, thereby ensuring that every action taken is mission-driven and impactful.</p><h4>Stakeholder Engagement: Weaving a Tapestry of Collaboration</h4><p>Above this foundational layer is the intricate interplay of stakeholder engagement. This stage is about connecting diverse blocks — each representing different stakeholders like programme staff, local and global partners, beneficiaries, and donors. It’s about creating a colourful Lego tapestry that reflects the multitude of perspectives and needs. For effective engagement, imagine a digital forum embedded within the toolkit that allows for continuous feedback from field workers, and partners. This platform would serve as a dynamic space for real-time input and collaborative decision-making.</p><h4>Programme Unity: Integrating with Existing Frameworks</h4><p>Integrating our toolkit’s architecture with existing programmes and initiatives is like building upon an already intricate Lego structure. This step ensures that the toolkit not only fits into the existing programme landscape but also enhances and strengthens it. A practical approach could involve a system where the toolkit’s functionalities are embedded within existing programme management workflows or data models. This could be achieved through features that link programme delivery metrics directly with evaluation tools, creating a seamless data flow and comprehensive analysis capabilities.</p><h4>Capacity Empowerment: Fortifying the Structure</h4><p>Capacity building involves reinforcing the structure with blocks of knowledge and learning. These blocks represent training modules and support resources, essential for enhancing the skills and understanding of the toolkit users. An effective capacity-building component could be an integrated online learning portal within the toolkit, offering interactive and engaging modules on MEAL best practices, data analysis techniques, and effective use of the toolkit. These modules could (should) also extend to [non-exploitative] cultural learnings, and language, offering an opportunity to develop a non-eurocentric worldview with different cultural lenses.</p><h4>Adaptive Design: Crafting a Flexible and Dynamic Framework</h4><p>Creating a scalable and adaptable framework within the business architecture is not unlike using Lego blocks that can be reconfigured for different purposes, for those familiar with the <a href="https://9now.nine.com.au/lego-masters">Lego Masters TV programme</a>; they would refer to this as “NPU” or “<a href="https://bricknerd.com/home/tag/NPU#:~:text=NPU.,perfectly%20fits%20the%20overall%20model.">Nice Part Usage</a>”. Anyway…these blocks allow the toolkit to be tailored to varying programme sizes and contexts in a reusable fashion. Customisable data model templates and guidelines could be included, allowing field staff or partners to adapt the toolkit to local cultural nuances, languages, and specific programme requirements, ensuring relevance and effectiveness in diverse settings. This in turn will roll all the way up, through our layers of interconnected blocks, to our strategic alignment, ensuring that regardless of the programme context, we are aligned to our strategic objectives and goals.</p><h3>Elevating the Technology Architecture</h3><h4>Tech Foundation and Data Integrity: Robust Base and Core Blocks</h4><p>In technology architecture, platform selection is similar to choosing a sturdy and flexible base for a Lego structure. It needs to be robust, adaptable, and capable of supporting the weight of the entire structure. In the context of a MEAL Toolkit, this means opting for a platform that is not just versatile in the present but can adapt and scale according to future needs. Opting for a cloud-based, modular platform that can adapt to various operational contexts is definitely the way to go. With regards to Data management — the core of our structure, it must prioritise security and integrity. Implementing a hierarchical data structure with adjustable data access levels can exemplify this robust data management. This system ensures that sensitive information, particularly that of children, is handled with the utmost care, respecting privacy and adhering to international data protection regulations.</p><h4>User-Friendly Design and Seamless Integration: Interactive Surfaces and Connecting Bridges</h4><p>A user-friendly interface is the interactive surface of our Lego model. It should be intuitive and accommodate users with varied digital skills, possibly through a simple, intuitive UI for easy navigation. Interoperability is like adding connecting bridges between different Lego structures, achieved by using common data standards and open APIs for smooth data exchange, functionality sharing, and aiding the development of engaging user experiences.</p><h4>Modularity: Flexible and Evolving Components</h4><p>A modular design approach in the technology architecture is akin to using Lego blocks that can be independently modified, swapped out, or completely replaced without having to completely rebuild our model. This allows for the toolkit to evolve and adapt, accommodating new technologies and changing needs. Also this means that as long as the lego blocks conform to particular standards and form factors, it doesn’t matter how the blocks are arranged (e.g. a rectangle, or a sphere with the <a href="https://bricknerd.com/home/snot-basics-geometry-techniques-and-pitfalls-3-18-2021">SNOT technique</a>), we know it’ll be “compatible” within our structure. In practical terms, it doesn’t matter what our data collection tool is, just as long as the data collected conforms to our data model and data measurement schemas.</p><h4>Insight Generation: Turning Data into Actionable Intelligence</h4><p>Incorporating analytics and reporting into the MEAL Toolkit’s architecture is a bit like adding sophisticated elements to a Lego build that transform raw data into easily understandable visuals. This process is crucial, as merely collecting data without purpose is like scattering Lego pieces all over the floor, without a plan to build something meaningful (and just being a mess). While we’re here, let’s talk about GDPR — it’s not just a stick to be beaten with, but a critical consideration on what data we collect, and how we handle this data, ensuring compliance and ethical usage.</p><p>In the realm of actionable intelligence, the goal is to convert data into insights that drive decision-making and foster knowledge sharing. Imagine a feature within the toolkit that not only collects data but also analyses trends, patterns, and outcomes. This could look like a dynamic dashboard that not only displays programme metrics but also offers predictive analysis and recommendations. It’s about creating a system that not only tells you what has happened but also offers insights into what could happen next, enabling proactive programme management. Further, through smart design these programme metrics should roll all the way up to our strategic objects (I’ve said this twice now, so it must be a thing).</p><p>Moreover, turning data into accessible knowledge means ensuring that these insights are communicated in a user-friendly manner. Whether it’s through interactive graphs, simplified reports, or visual summaries, the idea is to make complex data easily digestible for all stakeholders, regardless of their technical expertise. This approach not only enhances the understanding of programme impacts but also promotes transparency and accountability from the inside out.</p><h4>Security and Compliance: The Protective Shield</h4><p>When we talk about security and compliance within the architecture, we’re referring to the protective measures that are as crucial as the transparent neon shields of my 1990s Lego Space sets — not only do they look cool, but they also protect the core of our structure, ensuring that sensitive information, especially children’s data, is safeguarded at all times, and ensuring that the toolkit is a trusted and reliable resource.</p><p>In the digital age, protecting sensitive information, especially children’s data, is paramount. This involves implementing robust encryption protocols, secure data storage solutions, and regular security audits. It’s about creating a digital fortress that shields the data from external threats while maintaining transparency and integrity.</p><p>Compliance, particularly with regulations like GDPR, is another key aspect here. Following the rules is one thing; but having a deep respect and understanding of the rights of individuals and handling their data with the utmost care and responsibility…is pretty fundamental. This means having clear policies on data collection, storage, and sharing, and ensuring that these policies are not just understood but also practised at every level of the organisation.</p><p>Integrating security and compliance into our MEAL Toolkit’s architecture is like building a safeguarding layer around our Lego structure, ensuring that every block, no matter how small, is protected and treated with respect.</p><h4>Technical Support and Maintenance: The Toolkit’s Lifeline</h4><p>The role of technical support and maintenance within our architecture is as crucial as the maintenance crew of my <a href="https://brickset.com/sets/6981-1/Aerial-Intruder">Blacktron 2 Aerial Intruder Lego set</a> (good memories). It’s not just about fixing problems as they arise; it’s about ensuring the long-term functionality and relevance of the toolkit.</p><p>Imagine an online support portal as part of the toolkit, acting as a help desk where users can seek assistance, report issues, and find resources. This portal would be the go-to place for all support needs, staffed by a team ready to address technical challenges, offer guidance, and provide training.</p><p>Regular system updates are another key aspect of maintenance. Just as Lego sets can be expanded and enhanced with new pieces, the toolkit should evolve over time to incorporate new features, address emerging needs, and adapt to technological advancements. These updates might include enhancements to existing features, introduction of new tools, or improvements in user interface and experience.</p><p>Moreover, maintenance also involves regular monitoring of the toolkit’s performance. Again this speaks to not just reacting to issues but proactively seeking out areas for improvement, ensuring the toolkit remains a cutting-edge resource. By regularly updating and maintaining our architecture, we ensure the MEAL Toolkit’s relevance, efficiency, and effectiveness in a rapidly changing world.</p><h4>Seamless Communication: Integrating Digital Messaging into the Architecture</h4><p>Interwoven throughout our technology architecture lies the digital messaging system, think of the intricate network of tubes in a Lego Technic hydraulic set that allows for smooth and swift transfer of air…or in this case, information. This system serves as the electrical pulse of our toolkit architecture’s connectivity, facilitating real-time communication within the organisation and with external stakeholders etc.</p><p>Implementing a unified messaging framework within the MEAL Toolkit ensures that all components — be it data collection tools, analysis software, or reporting modules — are in constant dialogue. This integration allows for automated alerts, updates, and reminders, ensuring that no critical information falls through the cracks. Furthermore, digital messaging is essential for enhancing stakeholder engagement. By incorporating tools like email, SMS, chatbots, and notification systems, the toolkit can provide a responsive and interactive experience for users. It enables programme staff to quickly disseminate information, gather feedback, and engage with beneficiaries in a way that is both scalable and personal.</p><p>Beyond mere communication, the digital messaging aspect of the toolkit paves the way for knowledge sharing and collaboration. With features like group discussions, forums, and shared workspaces, teams across the globe can collaborate on projects, share insights, and collectively problem-solve, turning individual knowledge into collective wisdom.</p><p>With the inclusion of digital messaging, security and privacy considerations take on even greater importance. Ensuring end-to-end encryption, secure message storage, and compliance with data protection laws is paramount. This will instil confidence among users and uphold the integrity of the organisation’s communication channels.</p><h3>Conclusion</h3><p>As we reach the final brick in our Lego-inspired journey of constructing a business and technology architecture for a MEAL Toolkit, it’s clear that this isn’t just child’s play (Ooof two puns for the price of one!). From the strategic alignment that lays our foundation to the intricate stakeholder engagement creating a vibrant mosaic, each step in crafting the business architecture has been like piecing together a masterful Lego creation — thoughtful, intentional, and with an eye for both form and function.</p><p>In the realm of technology, we’ve seen how choosing the right platform and ensuring data integrity form the robust base and core of our structure. The user-friendly design, seamless integration, and modularity are akin to those versatile Lego pieces that can be transformed and repurposed, breathing life and adaptability into our toolkit.</p><p>Let’s not forget the neon shields of security and compliance, ensuring that our creation is not only awe-inspiring but also safe and respectful of the precious data it holds. The technical support and maintenance? They’re our diligent Lego minifig maintenance crew, constantly fine-tuning and enhancing our structure to withstand the test of time.</p><p>By threading digital messaging through the fabric of our toolkit, we have effectively equipped it to be more than a set of tools; it becomes the central nervous system of a nonprofit’s operations, interwoven connectivity, scalable and adaptable to any context.</p><p>In essence, constructing a scalable and effective architecture for a MEAL Toolkit is much like building an elaborate Lego set. It requires vision, patience, and an unwavering commitment to quality and detail. But most importantly, it’s about building something that’s greater than the sum of its parts — a toolkit that not only serves its immediate purpose but also inspires, empowers, and makes a tangible difference in the world of international development and humanitarian aid.</p><p>So, as we snap the last piece into place, let’s step back and admire this structure we’ve built. It’s not just a testament to our skill and creativity but a beacon of hope and progress in a world that desperately needs it. In the hands of dedicated nonprofits, this architecture will be more than just a set of tools; it will be a catalyst for change, a builder of futures, and a creator of possibilities. And who knew all this could start with the simple joy of playing with Lego?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7628539c7f76" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>