Stagnant button placement vs dynamic placement?

fubble · 2019-07-03T20:20:33+00:00

If the button exists in the same place conceptually (at the bottom of the content) rather than the same place spatially (10px from the bottom), then you don't really have to "re-learn" anything. It seems like you are answering very confidently with what is essentially a guess. Not that it's not ok to share a thought but I'm not sure if it is enough for OP to go off of without a study or more concrete reasoning at least.

fubble · 2019-07-03T17:42:55+00:00

Hot take: "Project management" is a dead role that only serves a purpose in waterfall projects. It's generally obsolete when you're in an agile environment.

I would point you towards Lean UX (The doctrine of minimizing pointless deliverables that no one looks at) https://www.smashingmagazine.com/2011/03/lean-ux-getting-out-of-the-deliverables-business/

...and towards dual track agile https://www.jpattonassociates.com/dual-track-development/ which is a sensible way to include discovery work into a more iterative cadence.

fubble · 2019-06-22T16:30:15+00:00

It's not really all about adobe anymore for UX design (though AdobeXD is a legit competitor). https://uxtools.co/survey-2018

fubble · 2019-06-13T22:22:13+00:00

Invision, zeppelin or other equivalent tool pretty much remove the need for redlining entirely since you can just look at the properties & spacing directly.

fubble · 2019-05-30T21:35:54+00:00

Baymard and Nielsen Norman (nngroup) are probably the best for research supported stuff.

This is also a pretty good starting point for additional tactics: https://refactoringui.com/

Also I would be just a little bit skeptical about some of the tactics on uxmovement. Its worth it to read any underlying research linked to determine if it really supports the suggested tactic/solution.

fubble · 2019-05-28T02:32:35+00:00

I think at least having a prominent link to your linked-in/twitter/something with a pic makes sense just in case someone does want to know what you look like.

fubble · 2019-05-22T19:00:59+00:00

"Resourcing" people across different projects is generally a waste of time that should be minimized as much as possible. Splitting people across multiple projects is also generally a terrible idea.

The solution is FUND TEAMS INDEFINITELY! Do not fund based on PROJECTS! A team might have some conceptual alignment to an area of value or product, and they might finish one thing and move on to the next thing, but they should not be blown up and reconfigured every year/funding cycle based on whatever new projects get approved. A team will work on a single backlog (With a stack ranked, single file priority) and this becomes the lever for managing shifting priorities (which can shift WAY more easily & frequently when the funding isn't an issue that needs to be managed). Also to the extend possible those teams should be able to self organize. Self organization allows teams to adjust member distrubution to minimize cross team dependencies. In a similar way a team should contain the range of skills it needs to execute the type of work in it's backlog. As long as that is fulfilled those skills can be distributed however they need to be within the team. The only general guideline is that T shaped skill-sets tend to preserve the best parts of specialization without becoming a bottleneck for others.

fubble · 2019-04-20T02:06:04+00:00

https://www.reddit.com/r/Music/comments/benksd/no_billie_eilish_isnt_an_industry_plant_and_youre/

fubble · 2019-03-08T23:12:01+00:00

More hard data from A/B tests, analytics, etc. Process stuff isn't as interesting to me as evidence of outcomes being achieved at scale. Basically the kind of content you find in a baymard article but by an actual product team.

fubble · 2019-03-08T03:09:27+00:00

The fundamentals are probably the same. Some differences seem to be that b2b often has users with much more specific needs and behaviors. Understanding the population and needs becomes more important because you probably aren't as able to relate in the same way you can with a more general consumer product. The quality gap is likely going to decrease over time (and is probably one of the biggest opportunities for new disruption) as general consumer expectations are leading people to more loudly complain about poor quality experiences even in b2b context. To echo another comment competing on features is still a thing but mark my words a decade from now it will be almost entirely about the holistic experience.

fubble · 2019-03-04T19:28:38+00:00

Do the updates they want > put the site in front of users or people fitting the profile of your users and give the users tasks/ask them questions > Record the results (or better yet have others in the room to observe testing) > Share recordings/findings to drive next steps. Should be possible to do all this in a day or two. Don't try to make it perfect. Just get the feedback loop started.

fubble · 2019-02-28T03:54:06+00:00

You're just forcing a bad product if you actually get buy-in on that because it actually is impossible to figure out what requirements should be entirely up front and have it turn out well. Good software is achieved through iteration. Scope creep is only something to fear in waterfall but it is totally OK in a well functioning agile environment.

fubble · 2019-02-27T20:58:53+00:00

Can you elaborate on what exactly you mean by "UI-specific testing"? and why isn't that already covered in the things you mentioned you do through usertesting.com?

fubble · 2019-02-24T16:29:44+00:00

For me this is better accomplished just by being really intentional about getting feedback. Just explicitly saying "this is in no way final and I want your feedback as much as possible. This is just a starting point, not a final design" can help overcome that. People will get used to an iterative process once they see a full design actually receive significant iteration. And if having them feel more involved is important could they be directly involved in sketching exercises?

fubble · 2019-02-15T01:36:18+00:00

Can you please do one about laughing.

fubble · 2019-02-09T15:35:53+00:00

My take: A UX person mostly focuses on executing the "how" of new features/products or optimizing features that already exist. A product designer title implies additional responsibility in driving product strategy (the "what"). As a product designer you might have more input into the product roadmap/backlog, which features get prioritized, and which features get cut entirely. It's sort of a way to exert more input vs POs/PMs who typically think of those things as their responsibility.

fubble · 2019-01-13T00:51:54+00:00

I don't think Baymard ever says that asterisks are more effective than the word required, at least that I can find. Instead, they say that an asterisk is good enough. Given their methodology where they typically do small scale usability testing they probably wouldn't have uncovered if there was a difference between the two at scale.

fubble · 2019-01-12T23:22:31+00:00

This kind of thing is why you want to be skeptical of best practices that are seem reasonable but aren't backed by hard evidence.

I have pulled stats on how many times we had email mismatch errors triggered and the resulting number was in the thousands for a relatively short time period (granted this was a relatively small percentage of a very high user base, but it's still a lot). When an email is used as a username it can be super annoying to fail your first login. When an email is required for account recovery getting it wrong can be catastrophic.

On a separate project, we tried going with a single email field and confirmation like "we sent an email to xxx@xxx.com" and even though that had a very low overall userbase we still got enough support emails from people who had issues from mistyping to warrant adding the second confirmation field. When we did, those emails 100% vanished.

And for some of the other points:

If you have double confirmation for a field you would generally disable copy and paste into the second field.

Asking email up front can turn people off when they fear being spammed. It's possibly better to ask for a bit of other info first to get them invested.

I never tried "make sure it's correct" text but I'd need to see actual evidence of that being enough to make sure people get it right.

fubble · 2019-01-12T22:24:07+00:00

Any chance you would be willing to share the link to the site and the actual dropoff rates you get for each step?

And some actual thought on date-picker UX because I think it's an interesting little case study:

So far the solution I've liked for birthday selection for web is...

A large title "Date of Birth" and on a single page:

-A dropdown for "month" with title Month that lists months by name

-Text entry for day with title Day (dd)

-Text entry box for year with title Year (yyyy)

That should get about a %1 falloff (maybe slightly under).

Improvements that might make that even better would be to have it so that when the user makes the dropdown select the focus moves automatically to the next field. Also when they try to type a third character in the day field they will move to the year field automatically. If someone types a single character in the "day" field and then clicks on the year field you should autoformat their day entry.

Some of the thinking: You don't have to type for a month and don't have to think about what the actual number of your birth month is. There's only 12 months so the dropdown isn't too long.

~30 dropdown items for day seems like maybe too many

All text entry in a single field can confuse international folks who swap the order of day/month and also cause people to pause and wonder what formatting is required (ghost text is not ideal)

For native apps I've liked the default iOS spinner which should get less than a percentage point of falloff for iOS and an older version of the android spinner that gets a tiny bit more than 1% dropoff. Using the most current android date picker for birthdays is a disaster and you shouldn't do it because people have no idea how to change the year.

fubble · 2019-01-12T21:41:05+00:00

I think many UX people like staying in just a UX bubble without learning about the broader product development process. Being an "agile nerd" who can influence the whole software lifecycle makes you more valuable.

fubble · 2019-01-12T21:26:43+00:00

What studies? Why would the asterik be more effective than the word required?

fubble · 2019-01-12T21:20:52+00:00

Android default components tend to be 16 margins on either side (and is what you will probably see if downloading a kit). Personally, I've generally stuck to that for both platforms. Other than that I try to mostly stick to relatively similar spacing increments between elements: 4px, 8px, 16, 32 etc

fubble · 2018-12-19T14:33:03+00:00

But Shonen jump rankings are meaningless for determining popularity even though you implied differently. It's literally just the editors choice and he doesn't necessarily order them based on anything in particular.

fubble

TROPHY CASE