{"id":43469,"date":"2018-01-08T04:50:36","date_gmt":"2018-01-08T11:50:36","guid":{"rendered":"http:\/\/www.taterboy.com\/blog\/2018\/01\/how-we-designed-our-new-appointment-booking-experience\/"},"modified":"2018-01-08T04:50:36","modified_gmt":"2018-01-08T11:50:36","slug":"how-we-designed-our-new-appointment-booking-experience","status":"publish","type":"post","link":"https:\/\/www.taterboy.com\/blog\/2018\/01\/how-we-designed-our-new-appointment-booking-experience\/","title":{"rendered":"How we designed our new appointment booking experience"},"content":{"rendered":"

Simpler, more intuitive and scalable.<\/strong><\/p>\n

\"\"<\/figure>\n

Planning a big redesign of an app liked ours, without affecting general development or our legacy, requires a strong considering of priorities. We knew that working in phases would not be easy, but it was the only way to get\u00a0there.<\/p>\n

The quick growth of babylon meant we had to cover a greater number of users and integrate new features, thus demanding a versatile application that is prepared for what is coming. We were aware that the future had arrived, and we needed to evolve to create the foundations of a product in constant development.<\/p>\n

\u201cThe new appointment experience fitting with the new babylon generation, improving bugs of the past and it\u2019s prepared for the future features\u201d<\/p><\/blockquote>\n

babylon was born with a clear idea?\u2014?to democratise health?\u2014?and that meant creating a simple product with a clear purpose, where all users are able to solve their medical problems or worries in a simple, fast and secure\u00a0way.<\/p>\n

Solving issues from the\u00a0past<\/h3>\n

The good part about designing something that already exists and on which you have data is that you can see easily what works and what doesn\u2019t, but the worst part is the restrictions that this entails to freedom, since trying new things is a major\u00a0risk.<\/p>\n

The first thing was to see what we had, analyse the data, understand it, find out the things that are working properly, what problems we had, how we can solve them and the right way to evolve the\u00a0product.<\/p>\n

The key was to reduce the steps and friction to a minimum without affecting the UX, to make each section even clearer to eliminate mistakes, and to look for the way we never get blocked every time we wanted to introduce something new.<\/p>\n

Bringing the family\u00a0closer<\/strong><\/h3>\n

Another important part on which we focused, was to make it obvious who the appointment is for and create an easy way to select and add <\/strong>family members at any\u00a0time.<\/p>\n

Supporting the family is an ever-increasing priority for babylon.. More and more users expand their experience to their family, trusting the health of all them in us. Therefore, we made it obvious and simple how the different members of the family access to the consultations.<\/p>\n

Scalable and customisable<\/h3>\n
\"\"
Modular UI helps to make an scalable\u00a0product<\/figcaption><\/figure>\n

Because of babylon\u2019s rapid growth, the only way to develop a product well is through the idea of product\u00a0design.<\/p>\n

We had to think of a system of blocks or interchangeable pieces that would give us the freedom to create adaptable templates to each situation and to each user. It should be noted that babylon must meet the health needs of very different groups of\u00a0users.<\/p>\n

\u201c\u2026it\u2019s about designing with the big picture in mind?\u2014?it\u2019s about designing the core of the system\u201d- Joe\u00a0Toscano.<\/p><\/blockquote>\n

The main idea was to reduce the task to the minimum expression, to the most basic, the common, and from there start to build everything else.<\/p>\n

Reducing steps<\/h3>\n

When you need medical help you need it as soon as possible, you don\u2019t want to get lost in precious UI\u2019s or endless\u00a0forms.<\/p>\n

What makes babylon unique is that it breaks traditional schemes making health accessible in minutes wherever you are. Therefore, with that in mind, we set our goals higher and aim to reduce the process without affecting efficiency. The user should be able to reserve her appointment in the simplest way without making mistakes.<\/p>\n

\"\"
New slot selection reduces\u00a0friction<\/figcaption><\/figure>\n

We worked to integrate the experience into a single screen, where the user was able to review everything together, including time slots as an essential part of the appointment and thus eliminating unnecessary screens.<\/p>\n

\"\"
The appointment\u2019s new look is\u00a0ready!<\/figcaption><\/figure>\n

Don\u2019t miss a\u00a0call<\/h3>\n

Now that the booking is done, the next most important interaction is the call with the doctor. And here is where we also made major improvements. This part must be clear, frictionless and natural, received by the user as if they were getting a call from a friend or partner. This eliminates its cold character so that the user will feel calmed down and prepared for the consultation. All this in a much more obvious and integrated environment with the rest of your calls so that it does not lead to confusion or losing a\u00a0call.<\/p>\n

\"\"
Dr Hannah is\u00a0calling!<\/figcaption><\/figure>\n

How do we know we designed the right experience?<\/h3>\n

To understand how users interact with our experience we built a series of prototypes that we tested with real users. These usabilities studies help us spot pain points early on in the journey before development.<\/p>\n

Whatusersdo<\/a> is a remote user testing platform that allows us test our prototypes on a variety of users. Here are some of the quotes from the\u00a0testing:<\/p>\n

\u201cLooks really professional which is what you expect for an app for\u00a0doctors\u201d<\/p><\/blockquote>\n

\u201cVery Easy. Not difficult at all. Straight\u00a0forward\u201d<\/p><\/blockquote>\n

\u201c Quite good you can see the selection of specialist\u201d<\/p><\/blockquote>\n

Analysis focused on key metrics around satisfaction, ease of use, and time on\u00a0task.<\/p>\n

\"\"
Whatusersdo platform<\/figcaption><\/figure>\n

This is just the\u00a0start<\/h3>\n

This is just the beginning of a new complete health experience. With this work, we set up the basics to build on top all the amazing features we have prepared as well as the upcoming\u00a0ones.<\/p>\n

Visit babylon Design Team<\/a>\u00a0website.<\/p>\n

<\/p>\n

\n

How we designed our new appointment booking experience<\/a> was originally published in The babylon blog<\/a> on Medium, where people are continuing the conversation by highlighting and responding to this story.<\/p>\n

Powered by WPeMatico<\/a><\/small><\/p>\n","protected":false},"excerpt":{"rendered":"

Simpler, more intuitive and scalable. Planning a big redesign of an app liked ours, without affecting general development or our legacy, requires a strong considering of priorities. We knew that working in phases would not be easy, but it was the only way to get\u00a0there. The quick growth of babylon meant we had to cover… Read the full article…<\/a><\/p>\n","protected":false},"author":4,"featured_media":43470,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[15],"tags":[],"class_list":["post-43469","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general-info"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t