A few months ago, I was tasked with designing a Data Sharing Framework for a complex project that brought together government officials, private sector players, and humanitarian stakeholders.
At first, it felt overwhelming—so many actors, so much data, and so many expectations. But as I went through the process, I began to see patterns and lessons that made the work not just possible, but impactful..
Here are the biggest lessons I learned that I believe anyone can apply when building a framework for data collaboration:
🔹 1. Begin with clarity of purpose
I learned that you can’t design a framework in a vacuum. Start by asking: What is the project trying to achieve? What data is truly needed? Once the objectives are clear, everything else starts to align.
🔹 2. Stakeholder mapping is non-negotiable
Before the first meeting, I created a detailed map of all stakeholders—who they are, what they bring to the table, and where their influence lies.
🔹 3. Data quality and security come first
In an era where data privacy is a hot topic, I quickly realized that trust hinges on how well you handle data quality and security. Without strong safeguards, no framework will survive stakeholder scrutiny.
🔹 4. Understand what data really means
It wasn’t enough to say “we’ll share data.” I had to break it down: Are we talking about personal identifiable information? Aggregated stats? Operational data? Knowing who holds what and how it has been shared before was key.
🔹 5. Capture stakeholder needs early
I made it a priority to listen—really listen—to what stakeholders needed from the framework. Some wanted visibility, others wanted safeguards, and a few wanted both.
🔹 6. Always bring a draft to the table
One mistake I avoided: calling a meeting with no draft. By sharing an initial framework early, I gave stakeholders something concrete to react to.
🔹 7. Co-create, don’t dictate
During workshops, I shifted from “presenting” to “co-creating.” I asked guiding questions, facilitated group discussions, and made sure every voice was heard. That’s when the framework started to feel like ours, not mine.
🔹 8. Transparency builds trust
The more I explained every element of the framework, the more open stakeholders became. Transparency created room for tough questions.
🔹 9. Decide on the legal angle early
One key decision was whether the framework should be legally binding or serve as a reference guide. Getting clarity on this upfront prevented confusion later.
🔹 10. Train and empower champions
After the framework was approved, I worked with stakeholders to identify champions who would train their teams. That step was essential to moving from “document on paper” to “culture in practice.”
💡 My takeaway:
A Data Sharing Framework isn’t just about systems and protocols—it’s about people.
👉 If you’ve ever been part of building or using a data sharing framework, what lessons stood out for you?
