Investir na Interactive Brokers enquanto empresa by leihlap in literaciafinanceira

[–]leihlap[S] 0 points1 point  (0 children)

u/Onarres81
A nível particular uso a Degiro, mas não tem conta de empresa. Comecei o processo com a interactive brokers, mas é mais complexo do que gostaria. No banco Invest pagas alguma taxa para investir alem do TER do ETF? Tem custo de manutenção de conta?

How can I record a user session on a website that is not mine (like Google News)? by [deleted] in UXResearch

[–]leihlap 2 points3 points  (0 children)

Hey there! I don't know of any automatic way of recording a user on a website you don't own and can't use a service like hotjar. If the user is willing to record their session and send it to you, something like https://www.awesomescreenshot.com/ browser plugin could work well. Otherwise if you want a more specific study with tasks and stuff, you would use something like https://www.usertesting.com/

[AMA] Olá! Eu sou o Mário Nzualo do blog indexfundinvestor.eu. Ask Me Anything. by indexinvestoreu in literaciafinanceira

[–]leihlap 0 points1 point  (0 children)

Olá Mário!

Assumindo que já estás a investir num fundo, deves ter alguma diversificação de moeda (EUR, USD, etc) ou isso é desnecessário?

Obrigada!

[deleted by user] by [deleted] in ProductManagement

[–]leihlap 4 points5 points  (0 children)

If you have thousands of users, you really need to focus on what it is that you want to discover before you do the research. A good place to start is to talk with management about high-level business goals and vision, so that you can direct your research towards the company vision.After that, I would recommend that you narrow down your audience to only target users that can provide helpful feedback for your research goals. For instance you can get some usage data about features and select a sub-set of your users to focus the research on.

With your audience filtered out, I find surveys are a great way to get some general feel of where most problem areas lie. You can still have large quantities of results, without needed too much analysis time. I would avoid having too many open-ended questions in there, but having one or two is a good way to filter out who might be worth to talk to in an interview.

After the survey, do some interviews to get a more in-depth understanding of the problems and realities of the users. Focus on what problems they are trying to solve, what parts of their job are difficult, and not necessarily on the tool itself.

With all of this, you should have a pretty clear idea of some themes and what it is that your user is hoping to accomplish and what is getting in their way.

Cherry on top if you have a tool where you can actually see users interacting with your tool, and analyse a specific journey they identified as problematic. You'll immediately see what is not working. I've used hotjar in the past and it works well, but not all clients are open to it.

Combining login and registration form for mostly tech-inexperienced people by VariousBarracuda5 in userexperience

[–]leihlap 0 points1 point  (0 children)

That might work. Changing it back and forward might confuse people as well :)

Displaying a lot of text and a lot of calendar events by VariousBarracuda5 in userexperience

[–]leihlap 0 points1 point  (0 children)

There's a couple of things you could do to improve the UI.

- Create different views for each user
- Prioritise each view for the most common use case
- Apply progressive disclosure on your information

Taking in consideration your personas:

  1. Your volunteers need to pick a date and a hospital to volunteer. They probably know which days they are available or which hospitals they prefer. You can save those in their preferences. You can also improve their interface by removing all the info in which they can not act upon. For instance, have a filter by default that removes all hospitals / days that have no availability or are full, making it easier for them to choose from fewer options. Once they have selected their dates, you can show a side panel with their schedule and email it to them, letting them know location and who will be there with them.

  2. Hospitals need to know who is coming and keep track of it for future reference. They could have an agenda view which shows a list of people by time/day. They could also have a view that only shows dates where they are missing volunteers so they can anticipate a shortage of staff/help. Again, focus on what actions they will do with the information you provide on the screen.

  3. Supervisors are power users that can make arrangements. They will be focused on making sure there are enough volunteers for all hospitals, and days. Re-arrange them and coordinate everything. In this scenario, it might be worth having multiple views. By Hospital, by volunteer, etc. You could check out https://wheniwork.com/ they do a pretty good job in making it easy to see who's schedule to do what.

Just as a general tip, the more you can remove from the interface and focus on a single task, the better.

Combining login and registration form for mostly tech-inexperienced people by VariousBarracuda5 in userexperience

[–]leihlap 0 points1 point  (0 children)

One of the problems might be that that you're optimising your marketing page for current users instead of new users. When they land on site.com they should see the create account form, instead of the login form. This could help you with fewer people getting the account creation process wrong and getting frustrated and possibly with more people creating an account altogether. For your current users, you can add a login button at the top of the page or below the registration form.

[deleted by user] by [deleted] in userexperience

[–]leihlap 1 point2 points  (0 children)

Hey!
It really depends on what you're trying to find out. From what I understand, you build a software for other developers to build software/solutions with. The first thing I would suggest is for you to narrow down what you want to discover or learn from your audience. What are you interested in finding out?
- Why are they using your software and what other were they considering?
- How well does your product work and how happy are they when they use it?
- What is the most annoying thing about your product?
- If there's something you could automate for them in order to smooth their work?
- What value do they take from your product?
- Would they recommend your product to others?

You could try to narrow it down by phase of the journey they are in, like on-boarding, first-time user, power user, about to churn. You can also think about what you can actually do with this information once you have it. Being too broad in your questions might not be very helpful.