The document outlines insights and strategies related to museum dashboards, emphasizing the importance of pragmatism over idealism and the significance of effective data presentation. It discusses the role of digital tools, the need for training staff, and the integration of data systems to enhance online visibility and community engagement. The document concludes with considerations for future improvements and specific actions for organizations to take.

1. The Museum Dashboard
@katiprice and @chrisunitt

2. How it started

5. What we did

6. Click to increase
Website is currently 84% SPLENDID

11. 7 things we learnt

12. Pragmatism
beats
idealism

13. Narrative
is the
spoonful
of sugar

14. The first
bite is with
the eye

15. Behaviour
beats
demographics

16. Context
is key

17. Strategy
for some,
tactics for
others

18. Dashboards
can’t do
everything

19. The difference it has
made

20. Happy
trustees

21. Happy
developers

22. Better
targeting of
online PR

23. Visibility of
emerging
trends

24. Highlighting
community
activity

25. More
conversations
about all of
this

26. What’s next for us

27. Extend
Improve

28. What you might do

29. 1. What’s the purpose of the
organisation?
2. What role does digital play?
3. What’s usefully measurable?
4. What’s the best way to
present the information?

30. £ ££ £££
People
General member
of staff
Digital
all-rounder
Digital Analyst
Consultant
External partners
Tools Free Free + paid
Free + paid
+ bespoke
Data Silos
More data.
Still mostly siloed
Yet more data.
In silos, but more
interoperability
Reporting Top-line
Top-line
Individual projects
Key departments
Top-line
All projects
Cross-department
Your situation

31. £ ££ £££
People Train staff
Train staff.
Use a consultant for audit/setup
Hire a digital analyst.
Train more staff.
Add analytics to job desc
Tools Use free tools
Use more paid tools
(TrueSocialMetrics,
Raven Tools, Moz)
Invest in bespoke tools.
Data warehouse
Data Use what you’ve got
Bake analytics into
commissioning of projects and
systems
Consolidate systems (eg
CRM, ecommerce, collections,
events, other databases)
Reporting
Report on specifics.
Automate what you can
Automate regular reports.
Set targets per project.
Monitor performance
Do you need
a dashboard?
No Maybe Yes
What you should do

32. Kati Price
@katiprice
Chris Unitt
@chrisunitt
bit.ly/museumdashboard