Closed
Bug 1004013
Opened 10 years ago
Closed 10 years ago
Improve UX and messaging on Contributor Dashboard
Categories
(Mozilla Foundation :: Metrics, task, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: adam, Assigned: adam)
References
Details
(Whiteboard: [metrics] [June27])
Opening a bug to get this conversation moving. Feel free to loop people in. Our contributor dashboard is taking shape, and starting to be referenced as a meaningful working document rather than a demo prototype. This is a good time to work on the messaging on this page to ensure the dashboard explains itself well. Initially, let's gather possible problems and solutions in a discussion here. Here's the current dashboard: http://adamlofting.github.io/mofo-contributors-dashboard/
Assignee | ||
Comment 1•10 years ago
|
||
Here are the initial points on my mind, but there are likely others... Potential problems: * Viewer doesn't understand the 'rolling active' model of contribution. * Current event buckets don't articulate the meaningful level of contribution that sits behind these * Bucket labelling is misleading (e.g. "1250 Events" actually means "1250 unique people who have made meaningful contributions to MoFo in relation to events). How do we communicate this well, and still keep the dashboard clean and readable like a good dashboard should be. Possible solutions: * Click for a video walkthrough that briefly explains what the dashboard shows * Pop-up / hover find out more info on each bucket that 'sells' it better
Assignee | ||
Comment 2•10 years ago
|
||
Another discussion point: Can this scroll to a longer format page? I think the graph should always be 'above the fold' in a single screen view, but the individual actions could be explained better in a longer format perhaps. I'm keen to keep this a dashboard rather than a report, but I think there is scope for a longer page format.
Assignee | ||
Updated•10 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•10 years ago
|
Priority: -- → P2
Comment 3•10 years ago
|
||
* Adam: let's do a work sprint on this together in our next 1-on-1 * And aim to ship the result on the [June13] train
Whiteboard: [June13]
Comment 4•10 years ago
|
||
* Adam: I think a longer page scroll format is a great idea. * Let me know if I can help.
Flags: needinfo?(matt)
Comment 5•10 years ago
|
||
* Adam: can you remind me when we believe the dashboard will have roughly *caught up with reality?* ie, when we think all or most of the primary data sources are wired in? * We could probably tie this to that. Because that change of state will give us reason to shout about the dashboard, and therefore ensure it's spiffed up in its best clothes accordingly.
Flags: needinfo?(matt) → needinfo?(adam)
Assignee | ||
Comment 7•10 years ago
|
||
* Counting the mentors via badges is the 'caught up with reality state change' (Bug 1024999) * I'm still planning to address some of the UX issues here, but now that we're progressing on the combined http://areweamillionyet.org dashboard - more time consuming ideas like video walk-throughs can be save for that.
Flags: needinfo?(adam)
Updated•10 years ago
|
Whiteboard: [June27] → [metrics] [June27]
Assignee | ||
Comment 9•10 years ago
|
||
TBC. The scope might change as the Baloo and areweamillionyet dashboard project is taking shape as we speak. I'll move this into the general foundatio::metrics component so it's not cluttering up the webmaker heartbeat view.
Flags: needinfo?(adam)
Product: Webmaker → Mozilla Foundation
Assignee | ||
Comment 10•10 years ago
|
||
I've made enough updates to this that it should last us while we transition to the shared MoCo/MoFo dashboard at areweamillionyet.org Updates include: * More specific text around rolling-active definition * Specific examples of contribution types, and a link out to all types * Highlighting that this is the interim dashboard, and flag-up the transition to areweamillionyet.org * Added basic navigation links between the team views
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•