Beruflich Dokumente
Kultur Dokumente
First thoughts
Scope - in Concerns
R&M wide Not trying to create new sources of data
Multiple data sources & types (surveys, data, Not separating each document into individual
quotes, observations) data points for storing as separate clues
Ongoing data sources & on-offs are stored Not making sense of content or adding meaning
Kirsty inputs documents & tags manually Not jumping to insights
Store data as whole existing documents
Tag parts of documents
Intuitive & useful search routes
Acts as memory prompt of where to find clues on a
topic
Owned by Kirsty
Secure
Used quarterly to search for inputs for the insights
forum.
Used more frequently to dip in and out to spot
emerging patterns or search for inputs for a one-
off brief.
Quarterly ‘milestone’ summary of key insights
added after insights forum
2
What is it?
Positives Concerns
Focuses on R&M business priorities It will require set up time and effort
Simple, not over engineered Payback will take time. This will need managing with
It is a proven solution – a database/file storing and communicating to with business
system How do we make our tags smart enough – are they
Distinct and has its own function and identity currently too broad?
Involves manual input, which is good because it We need to spend time getting the first level tags
sticks in your head as you input right and working out what some of the sub tags
It will be a solid foundation to any future capability are.
It is safe and reliable Is it too reliant on one person inputting and tagging?
We are clear on who it is for and who owns it (solution: handover notes or inputting guide created
It can exist beyond Kirsty by Kirsty from outset.)
3
What are the components?
Getting docs, Read through Keyword search Dashboard & Tool to let you
presentations, files… across categories, charts to let you take reports from
spreadsheets etc. …select the tags, comments quantify incidence the Vault and build
into the Vault important bits… and file content of tags & interactive
Converting them Search results categories presentations
…categorise, tag &
into a format we comment on those allow you to look Drilldown from
can apply tags to bits so they can be at ‘bits’ of files chart into
found later plus jump straight constituent file
into full file excerpts
Reporting tool
allows you to
create excerpts
from all docs
relevant to tag /
category
4
What are the components?
1. Ingest
5
What are the components?
t: c an we
s
ir sty reque surveys
K f qual ly
kick -o f
? ? P robab
here? R1
from
not in
t a g ging /
batch
Need -tagging c
un
a t the do
g
aggin the
Plus t as well as l
level d t e xt leve
e
select 6
What are the components?
What happens… Search will allow you to filter results on tags &
comments vs. full file contents
• Keyword search across categories,
tags, comments and file content
th i nk this
t
s ty d o e s n’ d
Kir de
is nee
7
What are the components?
i) Chart data
ps good P / data
Heat ma what OLA
en d s o n nds on…
ality dep et our ha
Function tools w e ca n g
zation-too
.html
s ati on ith - v isu ali
visuali w
…check in 09/12/28-rich-da
ta
om /2 0
eria.c
ww.insid
http://w
8
What are the components?
5. Interactive presentations
1…
is N O T part of R
his
NOTE – t
Rollover people to see quote
9
Project plan
Plan for demo end-June & 1st working system release end of the
Summer
Stage Time
User Experience Design Develop Demo Technical Build Pilot >> Live
What happens
• Map all use cases & main • Agree what to demo (24th • Technical briefing to • Pilot launch
user journeys May) developer • Bug fixes, functionality
• ½ day shadowing Kirsty • Technical build • Copy initial codebase tweaks
on Vault tasks (ideally w/c • Demo complete w/c 14th from Sherlock • Finalise and launch
10th May) June to present w/c 21st • Iterative design & build >> release 1
• Select ‘chart & drilldown’ test outputs and feedback
technology
• Define information
architecture (navigation)
• Develop look & feel
• Cut user interfaces
time delivered
What’s
• Updated requirements • ‘Canned’ demo ready to • Working application ready • Release 1 of the
doc be presented for user testing application, tested and
• User interface (screens) bug-fixed
• ½ day w/c 10th May • Use UE meeting time end-May • 2-3 30 min demo tests wks • Test & use system
Kirsty
We’re
building
Sherlock –
a tool with
a lot of
elements
the Vault
will need
• Insight platforms
• Search