WIAD DFW 2018 was a success

Jennifer Blatz UX Design World Information Architecture Day WIAD DFW
I was lucky to be a part of this fabulous crew to help plan and organize WIAD 2018 in Dallas.

WIAD, or World Information Architecture Day is an annual event held around the world. This year’s event, which took place on February 24, took place in 56 locations in 25 countries.

This was not my first WIAD rodeo. A few years ago, I acted as the project manager for the WIAD event that took place in Los Angeles.  Planning an even like this is a lot of work, but it’s very rewarding once the event wraps.

For the Dallas area WIAD event, I acted as the Chief Social Officer. What does that mean> I was a lean, mean Tweeting machine. ha!

Jennifer Blatz UX Design social media for WIAD_DFW
WIAD DFW Twitter account was on fire the day of the event.

I had the honor of tweeting leading up to the event as well as documenting all of the highlights on the day of the event. We got a lot of retweets from our sponsors and attendees. Though our attendance was less than anticipated due to a huge rain storm that certainly deterred attendees, those who did brave the storm seemed to enjoy the event and said that they learned a lot.

Overall I would say that they day was a grand success. For me, I enjoyed meeting my fellow volunteers and making new friends and connections. I also enjoyed hearing the speakers and seeing the attendees enjoy the topics as well. Events like this are a great reminder of how wonderful the UX community can be! I certiainly hope I can participate again next year. If I have anything to do with it, I will.

Speaking about UX and Agile for Scrum class

Jennifer Blatz UX User Experience designer talks about UX Process and agile
Jen Blatz spoke about the basics of UX at a scrum master certification course.

One professional goal I am working on for 2018 is to speak publicly more about my craft. I do feel comfortable talking in front of a group. It just takes a bit of discipline on my part to have a presentation ready to go. ha ha

My good friend and professional networking guru, Greg Gomel, reached out to me to ask me to speak to the current Agile for Patriots Scrum master certification class. I was honored that he thought I was capable and a good candidate to speak to his class. I was nervous because I didn’t have a lot of time to throw a presentation together. Yikes! But I knew with a kick in the butt like this, I could get a good presentation together in no time.

I was up for the challenge. I had a presentation I created a while ago for a previous employer explain the basics of UX. So I could use that former presentation as a base. But I wanted to cater this talk to show the scrum masters-to-be how UX ties in to agile.

I know there is a lot of confusion about how and where UX falls in the the agile lifecycle, and in to the developers’ sprints. I wanted to demystify that a bit and prepare them for the future of when they will be leading teams that will (hopefully) include a UX designer. I wanted them to not only learn about UX, but know how User Experience Research and Design works in to the development team.

After I gave my presentation, the asked me to stay and review and critique the website they were building for the class. So I gave them practical advice on some of the design decisions they had made as well as how to improve some things. The students were very receptive to my professional feedback and suggestions. It was a healthy dialog. I helped them to learn about better User Experience and Design. And they helped me to learn about the constraints they were dealing with and the business goals they needed to accomplish for their client.

Jennifer Blatz UX Designer explains scrum
Include your UX Designer in all scrum ceremonies.

One point I wanted to emphasize to the scrum masters in training is to always to include the UX Designer in all scrum ceremonies. As a UX Designer, I have been excluded in scrum ceremonies because it was considered too “developer” focused. The value of UX designers being included is so vast:

  • UX Designers should be in the scrum meetings so that we are “in the know.”
  • We need hear what is coming down the pike so we can plan our projects and research accordingly.
  • We can hear when design decisions are being made without consideration from users or the UX designer. (This should NEVER be happening, but it does. Uhg.)
  • We can provide insight in to how we can do testing on the projects as they are in flight.
  • Finally, we are part of the team. Make sure we are not excluded, and therefore left out of important discussions and decisions.

Read my entire presentation: What is UX Agile Patriots 2-2018

Consider Cultural Differences in your Design

One problem with much of tech coming out of Silicon Valley is the lack of diversity. When the members of a team are primarily one gender (yep, it’s mostly dudes) and of a limited number of ethnic backgrounds, there is the tendency to design in a vacuum. I know it is not intentional for the most part. But I see it time and time again. I have witnessed discussions of what should be included in a design. These debates do not tahe`1 in to consideration racial, cultural or language differences. And I am not even in Silicon Valley!

I was recently taking an online class on Coursera and the segment was over the importance of considering diversity in your product design. So many designers take this for granted. They assume that customers use the same technical terms that are being thrown around by the developers and product managers in house. Designers assume that the designs they make use clear language, when they might just be alienating the user. This type of alienation can unintentionally span into other realms as well.

Examine the chart below. The chart shows the many ways that people input their name and address. Note that countries use different formats. For example, the USA has a 5 digit zip code (sometimes with an additional 4 digits) and other countries have more than 5 digits. We need to keep these differences i mind when we design an address for on our website or app.

Jennifer Blatz Design cultural differences in UX design

Image courtesy of: Coursera Training Course Software Product Management discussion forum

  1. In India, people use the term “Surname” to refer to last name.
  2. Some countries have pin codes or postal codes in their addresses, instead of zip codes.

Here are a few other cultural differences that were shared on the Coursera’s class discussion board.

Date format
  • The USA has the date formate as Month, Day, Year.
  • Other countries have the format Day, Month, Year.

Make sure that the date inputs are clear when you are asking for a date format.


It is well known that the number 4 is not a good number in China as its pronunciation is close to the word meaning “death”, therefore, I am always careful not to use it without carefully identifying its relation with a software user interface. Having 3 clearly identifiable horizontal bars in a layout (clearly identifiable columns or other elements for example) is also to be avoided as it resemble the incense sticks used during worship at buddhist temples. The number 8 however is a go. It is symbol of fortune and prosperity (try to have a vanity plate with a lot of number 8 in it in hong kong and see how much it cost you :). I heard 9 is good in thailand as well.

Jennifer Blatz UX Design colorful diversityMaterial / Colors

Avoid brown. This is a very special one. If you ever design a character for a game application… avoid dressing him / her in brown. Brown is close to the color of suits worn by grieving people in traditional china. This is very little known and I had the experience trying to dress up in a particular way when I was told about it. Probably not the most common mainstream issue but good to know.

Avoid white as it is associated with funerals.

Red is good. Happy events are always covered wit red in China / Hong Kong.

Yellow: thinking of a all yellow themed app for china or hong kong? Depending on which political inclination you have, you may want to look at the recent history of the yellow umbrella revolution in Hong Kong.

Written language

Developing for the chinese market means having an app in chinese language (duh!).

I have seen app design build with english in mind and not fitting chinese at all. Typical issue would be the size of a label. Fits in english… layout is broken when chinese characters are used. Result is ugly and unusable for the user.

For truly global apps, bear in mind that some languages such as arabic are also written from right to left (this is a tough one for UI designers).


No need to say you should not have anything red and yellow in your app which would be considered as an insult to the chinese government or chinese flag.

As an anecdote…. dont build a Winnie the Pooh app for china. The character is banned ever since the chairman was depicted as the character.

No sexually explicit material of any kind. It would be censored as indecent (I hear from relevant sources Hong Kong is more relaxed about this).

Data export and location (not directly linked to user interaction but still good to know): this one is a nightmare for database managers. In some cases, either the government or the client will require data to remain in China (this is also true of some european companies linked to governments activities). Having a datacenter in China less difficult than a few years ago but represent a considerable investment and data confidentiality is following local rules. a few years ago, China also banned any export of data in some cases (survey data for example would not be allowed out of the country). The latter is a difficult one for anyone to track but the rules did apply when I was working for a company performing surveys in China. Any application covering this type of activity is vulnerable to this.

Infrastructure: Hong Kong as the fastest internet speed you can find for consumer grade connections and it is hard to find a spot where no one can call you or send you an email. Pass the border with mainland and it is another story (it is getting much better but China is big… it takes time to setup high bandwidth everywhere). Infrasctructure will impact your end user if your app require heavy bandwidth or needs to be connected all the time (no offline mode).

No google / Facebook: Anything depending on google / Facebook will not work in mainland china. Apple products are still also limited so plan android if you develop for mobile users. Have Baidu and Tencent products in mind as an alternative if your app needs online search / social media interaction.

End users

Chinese people (i.e. mainland Chinese) are not as exposed as the western world to applications and websites. Google is still banned and apple just made it through with being allowed to open stores in mainland china. Facebook is not accessible.

For more pointers at what people are used to, see apps as WeChat, QQ, go on the taobao.com website (chinese only but google will translate it pretty well when using Chrome). The user experience on these apps and website becomes more and more in line with global trends but there are still differences.

Hope this helps. Hong Kong and China are fantastic places to live and work despite its challenges for western people. I encourage anyone to experience it as it really opens minds to developing truly global ready softwares.