search

TeamMentor / Master

TEAM Mentor 3.x Released Code
16 stars 17 forks source link

As a new user I should be able to sign up as quickly as possible to begin using TM (FLARE) #913

Open romichg opened 10 years ago

romichg commented 10 years ago
luchia commented 9 years ago

What we currently have on 3.5 is -

screen shot 2014-09-20 at 2 25 20 pm

And what we have currently on 4.0 is -

screen shot 2014-09-20 at 2 27 10 pm

I don't think we need any more fields at the sign up, but I think we need to design how and when they will fill out the remaining fields, which are not unimportant but slow down the sign up process.

My initial thoughts on this was that it should be done at the end of the 30 day trial but now I think maybe that's too long. Reasons:

So when is a good time. Maybe on the third or fourth login? And maybe we could have the application direct them the Personal Details edit page so they fill in the remaining forms and save them, thus redirecting them back to the main app.

Should we allow them to be able to navigate away from that page without saving (eg. having the menu still in the top right corner)? I don't think so, so long as we make the page as short and succinct as possible so they can get through it quickly.

Thoughts?

romichg commented 9 years ago

I agree that end of the trial is too long. We need to have the info for the sales guys to follow up. I would say we should have something in the corner, or up on top of the UI, breaking news style. Sort of please fill in your user details. And then maybe give them a nudge on 3d/4th login to say that you won't be able to continue your trial if you don't fill it out in next few days. And then in 2 weeks basically force them to do it.

luchia commented 9 years ago

Like an alert on login? I've been working on an alert system that I should done in the next week that would probably be a good way to display this.

romichg commented 9 years ago

By breaking news style I mean something more like image image

michaelhidalgo commented 9 years ago

Also as a complementary information here (not sure if this needs to be a separate issue), as a potential sales opportunity, when the user has logged in the system the third or fourth time, we should display a message indicating him how many remaining days she/he has access to the system with a link to the pricing and license model so she/he can go to that and get all the information to get the license.

luchia commented 9 years ago

Cool, thanks Roman. Will work on this workflow.

luchia commented 9 years ago

There's quite a large gap between the search bar and the nav bar which I originally left free for an alert system so that we're interacting with the user as things happen within the app.

main-view

I've been thinking about the scenarios that might happen during the use of the application and have been brainstorming which of these are important enough to warrant a need for an alert and which can go without. This also applies to what we've been discussing above.

I think the following scenarios should have an alert:

If anyone has any other suggestions for things that should require an alert, please let me know. Once we have a list of scenarios, I'll ask the marketing team to help with the copy so it aligns with the TM brand.

Thanks.

romichg commented 9 years ago

Yep, agreed. I think this looks good. I think this is under the wrong issue though :)

On Tue, Sep 30, 2014 at 10:54 AM, Luchia Bloomfield < notifications@github.com> wrote:

There's quite a large gap between the search bar and the nav bar which I originally left free for an alert system so that we're interacting with the user as things happen within the app.

[image: main-view] https://cloud.githubusercontent.com/assets/4547737/4460226/0c1dd436-48b1-11e4-9bd8-b6572c385f09.jpg

I've been thinking about the scenarios that might happen during the use of the application and have been brainstorming which of these are important enough to warrant a need for an alert and which can go without. This also applies to what we've been discussing above.

I think the following scenarios should have an alert:

  • Search Results or Article saved
  • Learning Path completed
  • User details updated/saved
  • Request to complete user details (trial user)

If anyone has any other suggestions for things that should require an alert, please let me know. Once we have a list of scenarios, I'll ask the marketing team to help with the copy so it aligns with the TM brand.

Thanks.

— Reply to this email directly or view it on GitHub https://github.com/TeamMentor/Master/issues/913#issuecomment-57326392.

romichg commented 9 years ago

Actually never mind, yes it is the right issue. Looks good.

On Wed, Oct 1, 2014 at 8:48 PM, roman garber rgarber@gmail.com wrote:

Yep, agreed. I think this looks good. I think this is under the wrong issue though :)

On Tue, Sep 30, 2014 at 10:54 AM, Luchia Bloomfield < notifications@github.com> wrote:

There's quite a large gap between the search bar and the nav bar which I originally left free for an alert system so that we're interacting with the user as things happen within the app.

[image: main-view] https://cloud.githubusercontent.com/assets/4547737/4460226/0c1dd436-48b1-11e4-9bd8-b6572c385f09.jpg

I've been thinking about the scenarios that might happen during the use of the application and have been brainstorming which of these are important enough to warrant a need for an alert and which can go without. This also applies to what we've been discussing above.

I think the following scenarios should have an alert:

  • Search Results or Article saved
  • Learning Path completed
  • User details updated/saved
  • Request to complete user details (trial user)

If anyone has any other suggestions for things that should require an alert, please let me know. Once we have a list of scenarios, I'll ask the marketing team to help with the copy so it aligns with the TM brand.

Thanks.

— Reply to this email directly or view it on GitHub https://github.com/TeamMentor/Master/issues/913#issuecomment-57326392.

luchia commented 9 years ago

Cool, then I think this one is ready to be dev'ed on Flare.

michaelhidalgo commented 9 years ago

I'm not sure if we already agreed on which fields would be available at the beginning of the trial, I was looking at few Web sites where you can start up a trial account and they request Name and Last Name at the beginning. See for example https://saucelabs.com/signup/trial

The reason why I've been thinking about it is because I was thinking about the scenario of sending an email upon sign up, probably with a marketing message or something similar. At least welcoming the new user to the platform. But if we do not have Name and Last Name it is kind of weird to send an email, well that is my impression.(Although we could send something like Hi there!) .

romichg commented 9 years ago

Yea, we actually had a discussion on this. So I think that it’s the least obstacles to sign up that important. We can ask for all the other information latter, nagging the user with alerts and finally suspending access if need be. But the less we ask from the user from the beginning the more chance we have the user actually signing up and giving TM a try.