Loomio

Empowerment of admins via in-group metrics and other

Simon Tegg PublicSeen by 42

A few user groups have requested the development of a metric feature-set that would allow them to track the viewing and comment rate of particular group members.

If this feature or features like this, were only available to group admins it could empower admins at the expense of democratic decision-making. For example, admins would have detailed information about how the group functions online, potentially allowing them put forward proposals at particular times tailored to the likely viewers or commentators.

The obvious solution is to make the in-group metrics available to everyone in the group.

This issue raises the question of how empowered admins are compared to "commoners"in general, and how this may change in the future.

(I'm not yet a member of the features group, so I started this here)

Robert Guthrie

Giving access to everyone does not raise the questions for me that you have suggested it does. I personally don't entertain the idea of admin only metrics for any amount of time, and I think it's because I believe leaders rise out of groups. We give the information to people and those that want to, can use it, admins have responsibilities not privileges - Anyone can start a proposal, right?

What I would like to see is a detailed breakdown of exactly what metrics we should start to deliver.

Simon Tegg

Changed "The obvious solution is to make the in-group metrics available to everyone in the group.ut But this does raise.."

to

"The obvious solution is to make the in-group metrics available to everyone in the group.

This issue raises the question of"

Simon Tegg

Simon Tegg
@robertguthrie . Yeah, that's cool. I was pretty confident there was a general understanding that we wouldn't superempower admins. I just hadn't seen it spelt out anywhere.

Robert Guthrie

No @simontegg, thank you! After I posted this I wondered:

Are there stats that you can think of that would be useful but pose a privacy or secuirty risk? My own guess would be that the stats are only as risky as the content of the group so as long as they have the same protection as the content all should be well.

Benjamin Knight

@simontegg , you should be able to request access to the features group whenever you want!

Richard D. Bartlett

Yeah I feel like you might be asking the question a bit back-to-front. Let's start by exploring what features would be most useful, then figure out who should have access to them.

Simon Tegg

One thing we've talked about is the advantage of "fuzzy" stats for keeping it human. The pie chart gives you an overall impression and the exact proportions "yes" "abstain" etc are not emphasised.

If we start giving groups highly detailed information, I can't name anything specific but it would seem to be a shift away from this ethos, and may shift the tone of decision-making and group process.

Somewhat extreme case but metrics like which users have viewed which content, may undermine the privacy of an individual to operate anonymously within their own groups.

Simon Tegg

Basically, is user-specific data that isn't obvious (like page-views) the property of the user, or the property of the group?

Richard D. Bartlett

I'd say as a rule of thumb, if it doesn't reveal specific users' information, it is fair game for the group to see. E.g. average engagement rate per decision ("on average 40% of members engage on decisions").

When you start getting into specific user information, you get into more complicated territory. E.g. my engagement rate per decision ("on average Rich engages with 40% of decisions"). You could make the argument that this particular piece of information is already available, so providing it in a more accessible format is not a breach of privacy. If that feels wrong, then perhaps we should consider enabling anonymous votes rather than trying to obfuscate the information at the data collection stage.

Likewise, total pageviews per discussion seems like fair game, but 'Rich viewed this discussion' is a different story.

Nicolas Wormser

Haha sounds like we may need per-group "privacy policies". Some group may decide that everything posted inside the group is the group's property and can be used at the discretion of the group's will (including stats and user-specific metrics).

Some other group may decide that everyone should possess their own data and control what usage is made of it. Then users could opt-in to allow access to specific usage of their personal data (comments, votes, user-specific metrics etc…)

Jon Lemmon

In the spirit of agile & iterative I think we should start with some of the less risky metrics that we know we want. We can make them viewable to everyone in the group and see how far we get with these simple metrics.

Then when we start getting into tricky territory I think we should talk about each metric separately and weigh the pros and cons of including it in the app.

Benjamin Knight

The group-ownership vs individual user-ownership of data (specifically page-views) question is something that we've already struck. It's an interesting dilemma!

We've been offered assistance in developing strategy around this issue in particular by a legal team in Hungary - is now a good time to follow it up? What do you think @simontegg ?

Simon Tegg

I think a version of @nicolaswormser's suggestion would work. I'm unsure of the legal aspects of this, or if this needs legal advice at this stage (but I wouldn't know).

I'm not so concerned with user-specific comments, likes etc. As @richarddbartlett mentioned such information is available to group members already. If someone wanted to take the time they could trawl back through discussions and collate this themselves. A metrics system just makes this more available.

With user-specific views however, Linked-In does this, but not even FB allows you to see who has viewed which content (though they probably track this). It would weird to have looser privacy policy than FB!

This is only coming up because a user-group has specifically asked us to implement user-specific views tracking, and we have to give them an answer. (My take (a nicer sounding) : "This feature is not a priority, we have privacy concerns about this, and if implemented it would be opt-in not the default.")