Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An example of how a seemingly simple UI change can have bigger implications #7

Open
Cleop opened this issue Dec 13, 2017 · 2 comments

Comments

@Cleop
Copy link
Member

Cleop commented Dec 13, 2017

As a product owner it can sometimes be challenging trying to understand how long various issues will take. Sometimes things that one might imagine are small can take a long time and vice versa.

It's great when your scrum master or developer can communicate effectively with you to help you understand how things work and why they may take a given length of time. But sometimes doing this is hard to put into non-technical terms.

Here's a nice example that will hopefully help illustrate this dilemma:

This navbar changes colour so that whichever page the user is on is shown highlighted in blue:


Changing the items in the navbar seems like a simple change, just some new words and text.

However, what if one of these new items were to involve a dropdown menu? What implications does this have for the highlighting styling? When a user clicks on the dropdown menu nav item the menu opens, at this point should that menu item be highlighted to show the menu is open? Should the previous highlighted menu item remain highlighted to show you are still on the same page but you also have a menu open? Or should that item be deselected? In that instance, would the item then be reselected if you were to close the menu again?

As you can see, one simple change from a navbar item leading to a page and highlighting what page you are on to a navbar item acting as a dropdown menu presents lots of questions. Depending on how you choose to answer these questions then may create additional work for the team according to the consequences of the change.

@iteles
Copy link
Member

iteles commented Dec 23, 2017

Thanks @Cleop, this is great.

The other example I often use a client asking for a checkbox to be added to sign up on 'sign up to our newsletter', thinking it will be a 15 minute quick addition at the end of a sprint.

But the questions then begin to appear - how will you know the person has ticked the subscribe box? Do app admins get an email, check a spreadsheet or have an admin dashboard? If none of these things are already in place, they need to be created.
How will the admins safely have access to the person's email address? Is additional consent needed? Is GDPR a consideration? Is there a need to integrate with your mail sending service so you don't have to manually copy each email address?

@iteles
Copy link
Member

iteles commented Jan 12, 2018

Another one: look at all the thought that has to go into a simple delete function!
https://github.com/emfoundation/ce100-app/issues/894

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants