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
If we had a UX designer's help, these are a sample of things we'd like help with. An ideal candidate would have experience with maps, data visualization, and accessibility. We do not need help running user studies or gathering feedback; we have plenty of that. We need help addressing known problems. We have internal users ready to help evaluate any fixes.
Scheme sketcher
Improve the style of objects we draw on top of the basemap (noting there are multiple basemaps people use)
Validate/improve our strategy for modal interactions on the map -- one tool active at a time, with context-sensitive instructions on the sidebar
Design a way to move some controls to the map for better visibility, handling problems with those controls taking up lots of space when activated
Review the mechanics of map drawing interactions and suggest improvements
Improve the "layer" mechanics, which group multiple features
Help design an interaction for joining routes together
Scheme browser
Improve the style of objects we draw on top of the basemap (noting there are multiple basemaps people use). There are 30+ layers to review, but only a few types of data we show -- so reusing some common patterns would be fine
Think through how multiple active layers on the map should act
Revisit the left sidebar's use and figure out more useful info to put there
Redesign the scheme filters/search interaction
Think through an alternate user flow through the tool, where people first select layers, then see a map with controls only for those layers
Inspectorate tools
Improve our "file management" design
Review the problem mapping and junction assessment flows, some of the most complicated pages
Review the scorecard design, especially for questions with lots of text
Validate that we're using gov.uk design components in reasonable ways, or suggest changes
Prototype a next-gen cross section tool, taking inspiration from Streetmix
The text was updated successfully, but these errors were encountered:
From Sept 2024 user research sessions with internal users (inspectors and regional managers)
Feedback about the map
Legend that is more visible on the map and explains what each coloured line means
Modal with caveat about the data rather than the button we currently have. This loads at the start with a check box saying I have read this message to stop it appearing again. The message is ‘a reminder this data is based off’
Feedback about layers
Find a way to show selected layers, group them to the top or pull them out of the nested layer lists
Turn off all layers button at the top
Feedback about filters
Put a search field above schemes. Not immediately apparent the search field updates the schemes below - not obvious. Group them together in a way that makes it obvious the schemes are updated with the search terms you use.
Feedback about schemes (listed in left hand panel)
It would be useful to have a unique ID for a scheme, because scheme names can change
Deselect show schemes check box when the tool is loaded if we decide to load all schemes.
Feedback about scheme information on the map (pop-ups)
"Not sure what some of these headings refer to"
Feedback about the scheme data
"It's out of date information in terms of the designs that they the information that they have placed in more recent pulse surveys"
"it's out of date in terms of information on the level of interaction they've had on this scheme with Active Travel England's inspectorate"
If we had a UX designer's help, these are a sample of things we'd like help with. An ideal candidate would have experience with maps, data visualization, and accessibility. We do not need help running user studies or gathering feedback; we have plenty of that. We need help addressing known problems. We have internal users ready to help evaluate any fixes.
Scheme sketcher
Scheme browser
Inspectorate tools
The text was updated successfully, but these errors were encountered: