You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 12, 2021. It is now read-only.
Work load became too much by 5pm, needed 2 people, he did data entry and
she did prioritisation and informing committee rooms
Combination of mental load, getting in more data, and prioritisation had
then became more important (more data to base things off) - though
at points they had so many volunteers all boards were out so
prioritisation less important
at times were just deprioritising certain areas rather than
prioritising
Data entry time spent:
managing polling agents
updating spreadsheet for his committee room with new figures he was
given
given sticky notes with figures, sometimes stacked up, sometimes he
could keep on top of
syncing latest figures from (road group-granularity) spreadsheets to
(polling district-granularity) dashboard
prioritising all committee rooms
prioritisation improvements
highlighting single row that we did was not super useful
just one piece of info and only based on (guesstimated/confirmed)
Labour votes left
often told people things were a priority and were already out
better might be incorporating road group level data and then we can give
full road group prioritisation based on:
confirmed Labour votes
guesstimated Labour votes
insight priorities
should allow manually adjusting these to account for local knowledge -
estate with no access etc.
can then share view-only view of this with other committee rooms
The text was updated successfully, but these errors were encountered:
From Eran discussion:
The text was updated successfully, but these errors were encountered: