Closed Bug 1010295 Opened 10 years ago Closed 10 years ago

Gauntlet Dashboard - V2

Categories

(Mozilla Foundation :: Metrics, task, P1)

x86
macOS

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: adam, Assigned: adam)

Details

(Whiteboard: [June27])

Update to a single chart:
* 2014 Grants
* 2015 Grants
* 2014 User accounts

Build integration with new sheet to manage user account predictions.
* Accounts target is 150,000
* User accounts is a combination of original Gauntlet Doc, and new Maker Party comms plan Gauntlet
* Make targets manageable through a gdoc
This is ready for another round of testing/feedback:
* http://gauntletdash.herokuapp.com/

* I've simplified the graph a lot to try and make it readable. 
* It's loading data from both Google docs now, and using a third to manage the target lines

* Visually, there's a bit of ambiguity around the 2 x Y-Axis scales (dollars and accounts), but the most important thing should be clear at a glance (i.e. whether or not a particular measure is on track to hit it's target).
* Also, I've upped the 2015 target in the admin doc mainly so the target line is visible on the graph for this demo.
Flags: needinfo?(geoffrey)
Flags: needinfo?(ben)
Per discussion in Skype—

Love new look. Some thoughts:

1. Do we need a vertical line for year start? Good for visual weighting. How about a vertical line for "now"?

2. For readability, I wonder if we could apply some transparency css to each trend line, use jquery to selectively apply the class. Mouse over "contributors" we remove the transparency / highlight the trend line.

3. I think we could also add some explanatory text on what each target represents, with links to Engagement dashboard. Maybe Hannah would be interested in taking that on?

4. Maybe we could also have a display mode that cycles through each trendline, highlighting it with the explanatory text? Good for office monitors if we ever want to show.
Flags: needinfo?(ben)
+ a bug:

* When two or more values are at the maximum, the values are sitting on top of each other at the top of the graph (and become impossible to read)
@Ben - happy to help if I can. Not sure what you're suggesting we link to, though. This *is* the Engagement dashboard, isn't it?
@Hannah Engagement workbench maybe?
@Adam, if it would be useful, I could help craft some copy describing where the data is coming from, though I'm sure you know better than I do. 

The Engagement workbench (https://wiki.mozilla.org/Foundation/Engagement) is more of an overview of the entire scope of the team's work, not limited to MP outreach (which is where the "People" line is pulling from now).
(In reply to hannah from comment #8)
> @Adam, if it would be useful, I could help craft some copy describing where
> the data is coming from, though I'm sure you know better than I do. 
> 
> The Engagement workbench (https://wiki.mozilla.org/Foundation/Engagement) is
> more of an overview of the entire scope of the team's work, not limited to
> MP outreach (which is where the "People" line is pulling from now).

That would be useful. I think we just need some explanatory text on there to say what this is, who is using it, and a link to the engagement workbench for people who want to find out more about our work. It can be simple though.
I'd like next steps on this to be a 60 min sprint with Adam, Sabrina, and me.

Geoffrey's Productivity Theory #117: The last 5% of any design project is best done in real time. Doing it over bugs and e-mail turns 1 hour's work into days of exchanges re: tweaking font size and shades of red.

Can we set that up for first part of June?
Flags: needinfo?(geoffrey)
I've added the two Y-axis in ahead of the staff call toady so the graph is easier to read, along with some basic notes on where the data comes from and what the graph shows:
http://gauntletdash.herokuapp.com/

I'll schedule the call for the final design tweaks now.
Whiteboard: [June13]
http://gauntletdash.herokuapp.com
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [June13] → [June27]
You need to log in before you can comment on or make changes to this bug.