This isn't the first time doing user feedback of course but we are now doing an official system with numbered system and specific test schema that work for different user sets. (First time, New, intermediate, advanced etc)

We're paying some users and using the feedback to identify a lot of areas of polish and perhaps some new features. Also it can help identify some features we already know we should do and help place them in a good priority location.

THE MAIN IDEA OF THESE FEEDBACK SESSIONS
Give them a task ... Then shut up and watch.
This is not a conversation this is observation.
This isn't about their opinions on things it's about seeing them in action and the reality of a situation.

Recommend watching at 2x speed

WHY SHARE IT?

Because it was a good session. It maybe helps long time users recognize and see first hand what a normal person experiences when they try a Hive app like peakd.com for the first time.

Also sharing this work we've done will hopefully inform other APPS and Projects and they can adapt the messages to their own applications.

Some direct feedback on 3rd party features.

KEYCHAIN
@stoodkev may be interested in the task around 1hr40 mark where the user was tasked with installing and using keychain. Keeping in mind they had already had experience with peaklock and hivesigner. But there were a couple key moments that are of interest specially for most of the population that doesn't really fully understand what an extension really is or how they work. We may have some changes to do to specially with wording. but maybe this part of the video can help Keychain developers to understand how a normal web user interacts with their product.

HIVESIGNER
This was very early in the test.

I am VERY CONCERNED about the test subject's interaction with HiveSigner and I would assume most people who value both key security and user experience should be as well. So this may be of interest to @good-karma
You will note I didn't stop the test subject from using the master key inappropriately because it was a test account I will likely never use again.But then i realized she likely will do the same thing with her personal account. Wording and UI are important and i used to think no one uses it because of how confusing it is...

There apparently needs to be better clarification about how a HiveSigner password is something completely different. Some things to help would be:

1. a maximum size for the password so a hive key can't be used.
2. A check to reject a password suspected to be a key.
3. Better wording... I noticed Keychain used the word NEW and it made so much difference for our user. "Create a NEW password for Hivesigner"
4. Better wording or UI throughout would help. A plus sign next to an account name can imply that a user can add another account.
5. Saying the word SETUP helps them know this stage is merely a setup and they shouldn't expect this each time.

There are soooo many ways to go making some simply easy changes.

This is important to us because our analytics show there area a lot of users (predominately non-english speaking countries) that use it, perhaps because of mobile ONLY users where they need active key. I'm worried that many of them have not understood the directions on their app and set it up incorrectly and don't understand a few things.

HiveSigner had big plans to work on the UI/UX not sure what happened with that. But i volunteer my services to help if desired no knowing how many of our users use it and potentially use it incorrectly.

SOME OF MY NOTES AND TAKE AWAYS

Our team will be discussing this together and coming up with conclusions but I thought I'd share my own personal notes I wrote to help me remember some things to talk about in a team meeting.

• If you are expecting new information refresh page
• Before you can login setup the Hive Keychain extension to add your account information
• Create a NEW password for HiveSigner
• Create a new blog post > "Create a post"
• "Create more posts" "create another post" if only a couple posts
• "Expecting new information? Refresh the page."
• Would have been benefitted by password field rather than separate sectioned pin field
• Consider what it would be like to have a left only menu
• Make pencil more obvious. Or put "write" in other places.
• Bookmark button on Collections
• "Install Extension on Chrome"
• "Handle confusion with vote percentage slider
  ""Change to advanced slider""
  Why a percentage?
  Why is there a slider?"
  "Any percentage counts as a vote
  The higher the percentage the more potential financial impact you have on this content.
  However it is dependent on how much HivePower (HP) you own"
• Make collections easier to find
• Suggest communities/collections to new users - another indication this feature would be helpful
• "Tell her why she can't publish when hovering.
  ""Error: You must include a title before publishing"""
• Put a pencil or "edit" nex to their account name
• Change schedule to minimum 1 or 2 minutes (not important but no reason not to)
• Find another place to put drafts written by a user... like on posts or in profile
• "Do a check to see if they have already voted if so
  Put ""you are changing your vote amount. 0% will remove the vote"""
• rename tips found in top right menu > Feature Introductions

YOUR TAKE AWAYS?

I wrote many other pages of notes and may rewatch it. But please please please share any thoughts you have about this. If you have someone you think would be a good test subject send them our way as I'll likely do a couple more of these next week as well.

But in general if you watch this and you OBSERVED something interesting please do share. I know it's not your job... but a lot of you care about helping HIVE make it to the masses. If we can make a new user have a very nice and easy experience that will do wonders.

Another Test Schema?
I'm developing other sets of tasks which i call a Test Schema... if you have a suggestion let me know. I'm gonna try to make some with newer users and not just First Time users.

We paid the user @jjsienna (who as a friend would have done it for free anyway) and they're also a beneficiary of this post.