Understanding Data Sharing— Data Triage: move fast and tidy up

(Open Google slide version http://bit.ly/data-triage)

Our data-enabled world will be continuously monitoring and learning. We must step up to the challenge of managing our individual agency as innovation outpaces regulation

even without an ‘emergency’, there is often a rush to technology-led solutions without considering the overall decision-making environment that will impact users.

Questions to consider

  • What problems are we really trying to solve — based on actual user needs?
  • How will data help these problems?
    (what data? when? what frequency is timely? what analysis? for whom?)
  • Who should act to convene and lead: a sector, public body, both?
  • When are solutions needed and what might be our MVP (minimum viable proposition) intervention? (nb: this may not need any data at the outset)
  • What single issue could act as an exemplar to focus everyone’s mind?
  • What institutional memory, standards, principles and practices can be created as a legacy output and how will we make it discoverable?

Roles & responsibilities

A process outline (illustrative):

  1. A ‘Triage team’, comprising practitioners from the various domains, can act as the first point of call and consider the different user needs in the assessment and development of programmes.
  2. A ‘Governance/ Steering Group’ is assigned to approve recommendations and prioritises responses put forward by the Triage team.
  3. The Governance group can initiate rapid-response from a Delivery team who focus on solutions in the knowledge that there is a process overseeing and following them to ‘tidy up’ (rapid development is messy and leaves a data footprint).
  4. The Risk analysis team ‘follow’ the Delivery team, both documenting lessons learned, making sure that the output work is compliant with standards, regulation, principles and practices and highlighting areas for review and clean up. The Delivery team relies on this independent team managing risks arising or issues that materialise, enabling them to focus on delivery.
  5. The Clean up team follows the outputs of the Risk team to ensure data, code, and related digital assets are secure, deleted or otherwise made compliant.
  6. The Governance team have responsibility for both oversight and capturing outputs in an incremental manner to both (a) build usable institutional memory and (b) develop and input into living standards.




https://dgen.net || https://icebreakerone.org || Twitter: @agentGav // @icebreakerOne for climate+finance+data

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

SVMs for Non-Linearly Separable Data with Python

AI2FUTURE: How Data Could Save the World

Apache Spark Performance Boosting

Multiple Linear Regression in Python

How to tackle any Data Science problem? CSISP-DM

The Data Series

Cutting Edge Real Estate Analytics

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Gavin Starks

Gavin Starks

https://dgen.net || https://icebreakerone.org || Twitter: @agentGav // @icebreakerOne for climate+finance+data

More from Medium

Want to be an Analytics Engineer?

cartoon professor in front of a chalk board shown to represent Professor Data

A brief introduction to data deduplication | TiloRes

The Key Elements of A Data Driven Culture

Why is Data important for any business?