I am reworking memberships and invitations
As part of my invitations overhaul I need to change the way people are invited to groups. This has lead me to design the following mockups as my intended way to put my new invite people to join group process in place
Please let me know what you think of the following mockups:
https://loomio.mybalsamiq.com/projects/invitesomeonetojoingroup/grid
Thanks Rob for doing the mockup and starting this discussion.
Upon first glance I'm not a huge fan (but happy to be convinced). The dropdown seems confusing to me. What is the logic for separating out the functionality into separate pages? I really like it when you can accomplish a task in as few of clicks as possible, and the suggested solution adds a click to the edit memberships functionality. But I'm guessing there's a reason you chose to do things this way so I'm just interested in hearing why.
Also, do we really wanna expose the invite link?
And one more thing, are we going to verify a user's email after they click the invite link and set up their account?
Also, what's the thoughts behind having an editable invite message? It seems to add some bulk to the process and personally I'd be inclined to axe it if possible and keep the invite process as simple as possible.
(All of this said, I think this system is going to be a vast improvement over the previous one and I'm really excited about it!)
Hey @jonlemmon I think the idea was to reuse the same invitation form for both admin an users. Which gives us the functionality of adding multiple users at the same time.
We have also run into formatting problems with the current system when we added Espanol. This would be hard to keep under control unless we changed to icons instead of words. It seems there is a lot of functionality packed into that small space. For the general user, they wouldn't notice to much change. For the admin I think it would feel more intuitional and consistant with the rest of the site (dropdown -> edit_page). A better place for 'email members' too. This is what I see as the benefits so am OK for an extra click or two.
Hi Jon, Thanks for looking over this. You've got good questions I've tried to repsond as best I can:
as rich mentioned - this is tablet and mobile ready
a page to show pending invitations is necessary to offer the necessary new functionality (resend invite and view/copypaste invitiation link)
The most common and important and 'I expect this to be easy! damnnit ' action is 'invite people'. So I want it to be easy to discover. It also hints that this is the area to sniff around in to find related functionality around membership management.
I think this change reduces complexity on the group page -
I want to pull the membership management into it's own page because it is a task in itself - rather separate from selecting discussions to read.
We were at the limit of amount of actions we could put into the members sidebar list, and over the limit for size of list we can have hanging off of the group discussion index. - I wanted to go futher and truncate the member list - so on groups of (say..) 10 or less you get the whole list and more than that we just show the newest members - I don't think there is a lot of value in a very very long list of members on the group discussion index page.
It's the same number of clicks if you're on the group memberships index :) But seriously.. clicks vs visual clutter and our ability to have the richer functionality that comes with more space and focus - I was hoping that this would be a natural place to discover the functionality without being in the way.
I could be convinced that not using the editable message body for invitation to join group is the better thing to do.
@robertguthrie @aaronthornton sweet, that all makes sense to me.
The phrase "Pending Invitations" seems a bit confusing to me on the drop down. Perhaps we could change it to "See invited members" or something like that? Just so it's in the same language as the rest of the drop-down (an action).
But I guess the thing is, I'm just a dude on the internet making comments on some mockups at this point (which probably isn't very helpful). Is there a way we can expose these mockups to a more rigorous UX process so that we know we're solving these problems in the right way?
@jessedoud
Great to see inside your thought process thanks @robertguthrie that was very edifying
Sorry for such a late response, I couldn't even bloody sign in via mobile to view the mockups. Now I'm pissed and really want to kill that issue :0
I also want to point out @robertguthrie here for such a cogent and comprehensive response. It's really good to hear well thought out reasoning behind design decisions. I think what you're after here @jonlemmon, is to get this part of the process out of the sticks a bit, to a place where Rob doesn't necessarily have to explain the very core of his decision making process (the 'clicks vs visual clutter' part). Ideally everyone would already know what his basic reasoning is because it would be a shared basic reasoning.
I think there are 3 things that could help. One would be drafting a User Experience Strategy: a broad set of long-term goals that everyone would know to give us direction as we build and evaluate feature mockups. This probably already exists, this team is really great at focusing on why we are all here, it would just have to be assembled into one place. This could help us know that we're all working from the same baseline and give us something to reference to when justifying decision making.
Like Rob's decision to separate content into individual pages for example. It sounds good to me to build for quick load times and mobile ready templateing. These are already two things in the 3 month trello card. But while right now these are features about to be built, they will be design tenets for the foreseeable future. And as the team expands, it would be great to have a permanent place for these goals to live.
It would change a design brief from "x is good because it supports mobile users", to "x supports mobile users through y and z".
It's possible y'all have already done something like this, my apologies if that's the case. I jus don't know no better.
The second thing that could be done is to include design criteria with the mockups. It would be great for the evaluation process if the basic elements of the feature that were discussed prior to design were available for everyone to see. In this case it would be:
Design Criteria:
new functionality to add:
resend invite action
ability to view/copy/paste invitation link
invite multiple email recipients
improve experience for:
emailing all members
... etc
This would be something concrete to reference during group validation.
The third thing would be after design and implementation, getting some data on how we did with the new feature. Get on tracking the analytics to see if Rob was right to expose 'invite people' out on its own (i believe he is). I see that metrics is in the 3 month plan so I'm probably preaching to the choir here, I just couldn't leave out the importance of measuring the effectiveness of our decisions.
There could be processes used by you guys that I'm unaware of at this point so some of this may be redundant.
p.s. I could also be convinced that going with a strait forward static template invite is the way to go. Editable is a good idea. I'm not certain it's essential to the activity this feature supports however. Seems like an easy win.
p.p.s I was going to give the mockups a little tweak and ask some questions but wasn't sure if I should just edit it (haven't used balsamic before). Then I was going to just do it in photoshop but you can't post images to loomio outside of the discussion description to my knowledge. Decided to wait, as Rob you may already be past the point in development where design input is helpful.
#longestposteva
Sorry, that alphabet soup bit was meant to look like this:
Design Criteria:
new functionality to add:
- resend invite action
- ability to view/copy/paste invitation link
- invite multiple email recipients
improve experience for:
- emailing all members
... etc
Wow. Really great ideas @jessedoud. Thanks.
Looking forward to creating shared understanding on user experience with you.
Also I believe there is a 'suggest an alternative' button in balsamiq.. but if there isnt feel free to edit my mockups.
I miss the feature to invite someone directly to participate in a voting rather than invite them to a group and then he/she has to find out where is/are the things to vote for.
Thanks @miguelpradosrodrig, thats awesome feedback
We miss the percentage number in the graphic distribution of votes, sometimes an agreement needs more that a qualified majority, a 2/3 or 75% so it would be simpler if we have the numbers…. Although the impressive translation of Noelia in Spanish still we do not have the “Sí” rather than Yes possible answer. (That comes from real testing of the tool, thank you for letting us use it !!)
@miguelpradosrodrig. Ages ago, I made an experimental vote visualisation for Loomio to show the proportion of votes cast in each category: http://simontegg.info/loomio.
Initialise the proposal with the "Total Members" in the group, and push "Draw Waffle". You have to manually enter a random individual number for each member and then push the corresponding button for their vote.
There's actually a reasonably sophisticated tiling algorithm sitting behind this :)
Wow @simontegg that's AMAZING!
Lets have a talk about what api would support your visualisation as a plugin.
FYI the missed translation @miguelpradosrodrig is referring to relates to this issue - any text currently in javascript is not being translated.
@miguelpradosrodrig in regard to 'Si' for 'Yes'. The key of the graph should actually be 'Agree' as we are moving more to Agree/Disagree from Yes/No.
This is good, I'd also like to see the whole process streamlined, as per this discussion I just started:
https://www.loomio.org/discussions/5130
Just to add, being able to edit the subject line of the invite email is quite an urgent need for me. I want to invite a load of people who helped fund the first Building Man Festival to participate in an important decision about it's future, but if I send an invite out now it will say "Josef Davies-Coates has invited you to join United Diversity on Loomio" which wont mean anything to them.
Thanks Josef.. How about if we insted created the feature that you can invite people to join a discussion. so the subject line would/might say:
Josef Davies-Coates invites you to discuss The future of the Burning Man Festival on Loomio.
It's something we can do pretty quickly and I think it's a big workflow upgrade
@robertguthrie yeah, that'd be great! :)
Nice! Particularly like the checkbox for add/remove admin. So much better use of real estate.
Also good to have one concept per page, nice quick load time and mobile friendly.