Pink is for ladies, red is for men.

20160225 IMG 20160225 002927

These “pink taxis” are for Muslim women who do not want to get into taxis with men. They are driven by women, for women passengers only.

“Our society is conservative and our women do not want to ride with men alone at night or when they arrive at the airport at two or three in the morning,” Ammar Bin Tamim, director of Dubai Taxi, told Reuters.

Men can use the “red taxis”.

Launching a service in Kuwait – adjusting your user research

[My blog post was originally published on the Home Office Digital blog on the 27th of November. This is an archive, with some added information such as links and specific dates.]

Walking back to our hotel after a busy day during the EVW private beta launch in Kuwait city.
Walking back to our hotel after a busy day during the EVW private beta launch in Kuwait city.

On the 23rd of November, Monday morning, we successfully launched the Electronic Visa Waiver (EVW) service private beta in Kuwait to very little fanfare. The way a private beta should be launched.

The launch was combined with a user research field trip so we could test the system with these beta users.

I’ve been on many research trips in the past, but this user research trip was different: we were watching our users interact with our service in anger. This wasn’t a simulated scenario in a lab. It wasn’t a simulated scenario at someone’s home. This was for real.

It went smoothly. At the time of writing, 10 participants had made applications and 28 EVWs had been approved – for the individuals making the applications, and members of their families. The way we worked helped.


Like any research activity, planning is very important. It helps you identify what you want to get out of the research. It also helps you to anticipate things that might go wrong.

For our private beta in Kuwait we based our research plan on our previous user research trips to UAE and Kuwait.

We learned from previous difficulties. This time around we created guidelines for local translators to help, and being more aware of the culture, we scheduled the sessions for later in the day – between 12pm and 7pm) to make it more convenient for the users. We had iterated our user testing, and this made our launch easier.

We planned for things to go wrong – participants coming without the necessary documents, participants being delayed, technical issues.

When things went wrong, we were ready, we adapted and our users appreciated it.

Houston, can you hear me?

Communication with the participant

During the recruitment phase we put a lot of emphasis on explaining to the potential participants that they needed to have travel and accommodation booked in order to take part in our research.

Normally, you would not tell the user too much information in advance, but we decided to do this because this was a private beta launch – the user would be using the service for real.

On Thursday we were visited by Tobias Elwood, Minister at the Foreign and Commonwealth Office, and Matthew Lodge, the British Ambassador to Kuwait. Not a usual occurrence during a research session, you’ll agree.

The presence of high-ranking officials wasn’t ideal, as it put many of the participants on edge. It was a necessary part of the service launch, however, and when we explained the situation to the participants they felt more at ease.

Communication with the team

Communication between team members is important during any usability testing session. It’s even more important when your users are using your service for real, and your team members are 6,000km away.

A screenshot of the Slack messaging channel used for the launch of the EVW private beta
A screenshot of the Slack messaging channel used for the launch of the EVW private beta

During the live applications we kept in touch with our team in London via Slack. We alerted the team when the participant was about to submit the form so that the caseworkers would be ready.

This real-time communication is vital when a participant is sitting beside you in one country and the outcome of their actions is only seen in another.

It allowed us to identify issues, notify the necessary people and manage the participants’ expectations.

You’ve gotta roll with it

This user research trip was quite different from our normal work. It was a combination of user testing and service launch, meaning we needed to perform a complicated several role: part user researcher, part troubleshooter, part tester, and part childminder.

A participant using the EVW service on their smartphone. The recording was done with our DIY mobile usability testing kit.
A participant using the EVW service on their smartphone. The recording was done with our DIY mobile usability testing kit.

Some participants were mobile device users and preferred to use their smartphones, so we tested them using their phones.

As anticipated, some participants came without travel details, so we had sample travel arrangements prepared for them. In these cases we used those sessions as more formative research.

A picture of a young boy playing with post-it notes and sharpies
An unexpected, but welcome visitor.

Some participants came with their children, so we kept them occupied while their parents took part in our research.

A screenshot of an SMS from a user research participant
We kept in touch with our participants to make sure they received the EVW email notifications.

When something went wrong, we waited for a suitable moment, so we didn’t compromise the research, and then explained to the user what had happened. We then worked with them to find an answer, and ensured they left feeling satisfied.

What’s valuable is how we use what we have learned to inform the next service iteration.

We will use these learnings for next week when we continue with our research and continue to improve the service.

Let’s share

Do you have a different approach or thoughts on what we’re doing? We’re open to further improvements in how we approach digital transformation and would love to get your thoughts, inputs and experience in the Comments section below or via twitter.

W3C public-privacy thread

uT8ì4XY0R È42R0X0Z8UT U5 ÓíS0T é867ZYÕXU2R08S43 1ó Z74 uT8Z43 À0Z8UTY Ì4T4X0R ÂYY4S1Ró 8T Õ0X8Y UT õô È424S14X õûáÂXZ82R4 õúDÀU UT4 Y70RR 14 Yí1942Z43 ZU 0X18ZX0Xó 8TZ4X54X4T24 i8Z7 78Y VX8ì02óC 50S8RóC 7US4 UX 2UXX4YVUT34T24C TUX ZU 0ZZ02QY íVUT 78Y 7UTUíX 0T3 X4VíZ0Z8UTD Íì4XóUT4 70Y Z74 X867Z ZU Z74 VXUZ42Z8UT U5 Z74 R0i 0608TYZ Yí27 8TZ4X54X4T24 UX 0ZZ02QYD

Concerns about Dept. of Education’s “Primary Online Database”

Digital Rights Ireland Simon McGarr speaks about the Dept. of Education Primary Online Database by Bernard Tyers on Mixcloud

The recording can be downloaded for reference.

Simon McGarr from Digital Rights Ireland speaks on Drive Time, Irish national radio, about the privacy, and misuse of data concerns with the Department of Educations’ proposed Primary Online Database programme to collect sensitive, and nonsensitive data about primary school children until at least their 30th birthday.

Simon has written about it already, and has created an online form where parents can express their concerns.

The proposed database has been covered in Irish media.

Installing Trisquel GNU/Linux on a MacBook Pro

If you try to install Trisquel 7.0 1)Trisquel Operating System website: on a MacBook Pro using Virtual Box 3)Virtual Box website:, you’ll run into a problem.

When you configure the VM, and go to start it, you’ll get the following error:

This kernel requires the following features not present on the CPU: pae.
Unable to boot – please use a kernel appropriate for your CPU.

Error with Trisquel on a VirtualBox VM

This is due to Trisquel kernel requiring PAE 2)Physical Address Extension wikipedia article:, to be enabled.

The solution is to enable it in settings –


Trisquel running on Virtual Box VM - System VirtualBox Manager

This option “Extended features: Enable PAE/NX” must be enabled. Restart the VM and you can continue installing Trisquel GNU/Linux.

References   [ + ]

1. Trisquel Operating System website:
2. Physical Address Extension wikipedia article:
3. Virtual Box website: