<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Andy Birchwood on Medium]]></title>
        <description><![CDATA[Stories by Andy Birchwood on Medium]]></description>
        <link>https://medium.com/@andybirchwood?source=rss-bdaa251b8290------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*v06xKrwjGyuaPd-_o8XeXQ.jpeg</url>
            <title>Stories by Andy Birchwood on Medium</title>
            <link>https://medium.com/@andybirchwood?source=rss-bdaa251b8290------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:08:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andybirchwood/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Fixing design in squads]]></title>
            <link>https://medium.com/swlh/fixing-design-in-squads-f9291309c0a8?source=rss-bdaa251b8290------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9291309c0a8</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-operations]]></category>
            <category><![CDATA[agile-design]]></category>
            <dc:creator><![CDATA[Andy Birchwood]]></dc:creator>
            <pubDate>Thu, 09 Apr 2020 15:06:12 GMT</pubDate>
            <atom:updated>2020-04-13T09:38:54.038Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*facJUURxvws8EvCFSpKt-g@2x.png" /></figure><p><em>I’ve worked in several waterfall projects in big corporations, where development and deployment happens at a glacial pace. I often found myself lusting after jobs embedded in product teams in squad based companies. I dreamed of a promised land full of autonomy, responsibility and recognition, constant shipping and feedback and improvement. Sigh… The grass is always greener.</em></p><p>My role: UI Team Leadership</p><p>In one of the startups I joined, the squad based model was causing people to pedal fast but achieve little. A string of underperforming features and initiatives had led the start-up to burn through much of its series B funding without showing the growth expected by investors.</p><p>After my first design project was cancelled after 6 weeks of work, I realised the company had some serious design strategy challenges. Together with design director <a href="https://www.linkedin.com/in/alexhorstmann/">Alex Horstmann</a>, and fellow lead designer <a href="https://www.linkedin.com/in/kieronscott/">Kieron-Scott Woodhouse</a>, we devised a way of reasserting the importance of human-centred design and reintroducing some discipline to the design process. I learned a huge amount during this process, and our team is now humming along, delivering great outcomes for the company.</p><h3>A well trod squad</h3><p>The benefits of <a href="https://medium.com/productmanagement101/spotify-squad-framework-part-i-8f74bcfcd761">squad based agile</a> are well known, and don’t need repeating here. What the company was doing well was deploying code quickly and regularly. It was responding in lightning-quick time to stakeholder requests and changes in the market.</p><p>What it wasn’t doing well was delivering good outcomes. Engineers were focused on shipping fast, not the problems being solved. Feature decisions were being made on what would ship in the smallest possible time. Companywide strategies were rapidly splintered into projects that were focused towards fulfilling the requirement with the least possible development. QA and performance was subservient to rapid deployment. Any doubts about the design solution were deferred — promises of iterations which never came.</p><p>Lots of things weren’t being measured, and what was, was being measured in flawed and biased ways. Even what was measured was being communicated in a haphazard way.</p><p>The designers, especially, were unhappy with the quality of their output. With no time for gathering evidence, or generating and testing ideas, design decisions would be made on the hoof. Solutions were provided by stakeholders all over the business, but rarely interrogated.</p><p>Bizarrely, despite the fact that designers would turn around screens in hours or a couple of days, and there was more design work being done than being developed, the most common word to describe the design team was “bottleneck”. There was an terminal lack of recognition of the value of design to the production process.</p><h3>The symptoms of squaditis</h3><h4>Overworked designers hurrying with no time to think or plan</h4><p>Designers were generally being asked to visualise the ideas of product managers and other stakeholders in one or two day turnarounds, whilst developers twiddled thumbs and waited for the artwork. No time for <strong>research</strong>, <strong>problem framing</strong>,<strong> ideation</strong> or <strong>prototyping</strong>. Design was a single column in an engineering kanban board.</p><h4>Designing straight into high fidelity</h4><p>There was a perception that it would be quicker to design more quickly in high fidelity. And if you have UX designers who can also do UI — why not? The designer role was frequently reduced to graphics package operator with stakeholders directing from the shoulder. With no framework to demonstrate the <strong>value of design thinking</strong> or practice, the stakeholders weren’t going to improve their behaviour any time soon. It was the opposite of the ideals of trust and autonomy promised by squad-based culture.</p><h4>Little shared expertise or peer reviews</h4><p>Designers felt isolated in squads, and were so overworked they they felt there was little time to organise guilds, share knowledge and support, and most importantly, peer review each other’s work for consistency and standards.</p><h4>No prioritisation or coordination across squads</h4><p>Some squads had no designer at all. With a lack of awareness about design velocity or resource, design time was being allocated day-to-day. Designers didn’t feel able to say no to product managers, and it was the quality of the design that suffered.</p><h4>Poor quality delivery — no QA step</h4><p>With all the time spent tweaking high fidelity artwork and fielding new requests, there was no time for designers to review code in staging. At any point during development, the scope could be changed without the designer’s knowledge and broken up into “iterations” which never came. The resulting delivery rarely bore much resemblance to the original design, in appearance or feature set. The product was essentially untestable.</p><h4>Poor communication</h4><p>A continuous delivery pipeline, with designers excluded from the few ceremonies that there were, gave little time for evaluation of the design process. Failing fast only works if you learn something. Design mistakes weren’t being recognised, and actions weren’t being documented.</p><h4>Poor results</h4><p>For some teams, an obsession with A/B testing and narrow OKRs motivated squads to work on what was perceived as low effort/ high reward jobs, with little overall feature strategy. Larger build tasks were broken into smaller chunks and delivered and A/B tested independently. This obscured major fundamental usability problems that we revealed through qualitative usability testing. The user experience was inconsistent, half baked, unlikeable. Any benefit gained from feature development was small, and for some teams, virtually nonexistant.</p><h3>Sprint therapy</h3><p>You may be thinking now that this was just half-baked agile — and you would be right, but it wasn’t the only problem. One solution might have been to double down on resource and recruit more designers, so that there were at least 2 per squad. That option wasn’t available to us. With fewer than 8 designers facing off with around 60 engineers in 7 squads, we would have to think laterally and cross-tribe. The plan was delivered in 5 stages.</p><h3>Stage 1: Detach the design process from the development process</h3><p>The short term priority was to give the design process visibility. We created a new Jira project per tribe, which gave us access to a backlog, sprint planning, velocity and retros. Some of these agile ceremonies were happening in the squad boards, but they were engineering focused, and gave little constructive data or feedback for improvement for designers.</p><p>Organising design at a tribe level allowed us to pool talent and resources. Designers might have experience working from research to prototyping and UI production, but they are rarely deeply skilled at everything. Some designers are more comfortable working at the research and strategic end of the process, some love to solve problems with screen design and some work with developers to polish up interfaces. With a single designer embedded in each team, it would usually mean some tasks would be rushed or skipped entirely.</p><p>We split our backlog into research, discovery, flow analysis, wireframing and UI tasks. This not only gave us a good idea of who would be best working on it, it also allowed us to estimate on each design step in isolation. This gave stakeholders and PMs much better visibility of the end to end design process, and how long it would take, allowing them to prioritise more effectively. We made it clear to stakeholders that we wouldn’t be following a design process dogmatically, only introducing design tasks where they were relevant and necessary.</p><p>At a tribe level, we were able to introduce regular informal feedback sessions — peer review is much less intimidating than a guild-level session.</p><h4>Difficulties with stage 1</h4><p>There was some concern that <strong>having separate design boards might cause confusion</strong> by splitting the documentation. We linked the design issues in Jira with their corresponding issues in squad boards. Many developers came to prefer this, as long design conversations and design proposals were confined to a separate channel, rather than cluttering the technical channels.</p><h3>Stage 2: Initiate design sprints, one sprint ahead</h3><p>The first few design sprints were galling for the PMs, as they needed to start thinking ahead, supplying us with fully researched, prioritised and briefed work to complete two weeks ahead of the developers.</p><p>We were flexible on the content of project initiations, but not on briefs. Briefs took the form of user stories with hypotheses and supporting data. If a brief wasn’t fully formed, we could turn it into a discovery task, to help the PM identify goals and outcomes, to ask questions and banish assumptions using qualitative and quantitative evidence.</p><p>For some PMs, this was an education exercise, because they were unaccustomed to interrogating ideas to this level of detail or communicating that detail to designers. Despite some reluctance, rarely could they argue against the case we made for fully fleshed out briefs.</p><p>Being thorough with our briefs and discovery phases helped focus everyone’s attention on the problem rather than the solution. On more than one occasion, it helped us find evidence that users didn’t want the feature to begin with, so we could be comfortable terminating the project long before developing it.</p><p>We started with no idea of velocity, and the first couple of two week sprints were completed without strict estimation.</p><p>The squads needed to work on non-feature work for a sprint or two before the design work came in. We suggested they work on technical debt until the features were ready.</p><h4>Difficulties with stage 2</h4><p>Squads accustomed to continuous deployment found it difficult not to work on new features, and <strong>some attempted to shortcut the process</strong> by starting dev early and by bypassing discovery and design altogether. Both attempts were highly unsuccessful mainly due to unclear goals and outcomes. We were later able to highlight and improve these in retros.</p><p>To compensate for the <strong>perception of inflexibility in the process</strong>, we agreed to hand over work as soon as it was ready, rather than at the end of sprints, and engineers agreed to wait until work was handed over before grooming solutions. In the end though, the new rhythm became clearer, and the engineering squads followed our lead and began to work in sprints as well.</p><h3>Stage 3: Plan, plan, and plan again</h3><p>We began to run sprint planning ceremonies where all the product managers and directors in the tribe could review, discuss and prioritise our fully fleshed out design backlog. We encouraged attendance by gently reminding PMs that their work may not be prioritised if they tried to feed their work in by other channels.</p><p>As designers, we were simply there as facilitators of the discussion. I had initially imagined these sessions might be confrontational. But the product manager peer group was engaged, reasonable and focused on getting the best outcomes for the whole tribe. In the sessions, poorly thought out ideas were called out by peers and pushed down the priority list or back to discovery, which compelled PMs to properly frame problems and brief their work.</p><p>With full and consistent briefs emerging from squads, it was much easier for the product director to keep a view on outcomes, and they became a more effective, predictable and, less reactive arbiter and representative for business strategy.</p><p>After two sprints, we introduced story point estimation and after one more sprint we had a very good idea of the velocity of the team. This gave us a very clear idea of the effort that could be spent, and sprint planning ceremonies began to go very smoothly indeed — we’d often finish well before the 1hr time limit.</p><h4>Problems with stage 3</h4><p>There was a feeling from some PMs that <strong>detaching the design process from the engineering process would result in a loss of control</strong> over the programme of work by PMs. We asked for their faith here, and agreed with them that if the new operating model was to prove less effective, we would roll back. Once they had become accustomed to the planning sessions, they realised they still had full control over priority and schedule.</p><p>There was the <strong>perception that designers were being removed from squads to join a new team</strong>. Managers are always fiercely protective of resources. Again this perception was dismissed after the first sprint planning meeting. PMs became much more aware of resources across the tribe, and encouraged each other to justify that resource to their peers, rather than ringfence it.</p><p>Priorities in startups change quickly and constantly. Some PMs weren’t happy to wait two weeks to discuss new stories or <strong>assess if the sprint needed reprioritising</strong>. At their request we added a half-sprint replanning ceremony. But this wasn’t well attended and we decided to stop them. I interpreted this as a change in behaviour amongst the PMs, who had become used to thinking ahead, and deploying resources more proactively.</p><h3>Stage 4: The ceremonies: Technical reviews, show &amp; tells, wireframe and UI Handovers</h3><p>In the original embedded design process, engineers felt connected to the design solution because they were co-located. The designer would show designs to developers on the local machine, informally and one to one, allowing constant feedback and iteration in the design. Technical considerations were fed constantly into the design.</p><p>But some of the changes were suspect — for the sake of convenience and speed of development. Decision making was opaque and undocumented. Originally the team we colocated in Spain, this way of working became increasingly unsustainable as the team decentralised.</p><p>Moving to sprints allowed us to schedule more formal reviews and checkpoints for technical and product oversight.</p><ul><li>Within the team, we requested ad-hoc <strong>peer review</strong> sessions. Focussed on idea generation rather than critique, these were useful in getting over periods of creative block and stagnation, and were sanity checks on more unusual ideas.</li><li>For the product managers, we booked in weekly <strong>show &amp; tell </strong>sessions, to show work in progress, review work against goals, and accommodate feedback early on.</li><li>For all of the engineers, we organised <strong>technical reviews</strong> of low fidelity wireframes. Discussions centred around feasibility, effort and the quality of the solution, and new ideas were welcome.</li><li>Once the solution had been agreed, we worked on hi fidelity UI specifications, ending with a <strong>UI handover to the FE team</strong>. Discussions at this point could be centred around usability, content, style and branding.</li><li>We asked for a <strong>UI QA step</strong> before deployment. The product of this would be screenshots of the release candidate, a list of small snags in the UI. These were prioritised and remedied before release.</li></ul><p>With UX designers able to operate graphics software, low fidelity wireframing was previously seen as an unnecessary step. But we demonstrated that design ideas and proposed solutions were better assessed as early as possible in the sprints and at the lowest fidelity possible. It allowed back end teams to analyse any new data requirements for the design and to get started earlier. In many cases this meant the data structures and APIs were ready before the front end team started work.</p><p>The front end teams could analyse interactions and carry out spikes to discover the effort required to solve them. Any changes that came through technical limitations could be incorporated in low fidelity. The hi fidelity UI step could then be produced much more quickly, with iterations focused only on solving creative problems rather than business ones.</p><p>To facilitate communication of designs, we used a combination of Jira, Figma and Zeplin.</p><h4>Difficulties with stage 4</h4><p>A <strong>technical review isn’t always the best forum for feedback</strong>. In general, we found our engineers tend to be an introverted bunch, preferring to prepare responses than in reviews. There’s also not much time to review things in depth. We found it useful to send out links the day before reviews and handover sessions, allowing the engineers to prepare their questions and comment directly on the artwork.</p><p>Showing work in progress and low fidelity work through Figma gave access to engineers of unfinished designs. With unlimited access to this work in progress, they <strong>became confused about what was ready to develop and what wasn’t</strong>. A couple of times, they started development before the designs were ready and had to roll back when the designs were handed over with major iterations.</p><p>Although Figma’s cloud file hosting and sharing makes Zeplin redundant in a lot of ways, we found it useful to separate the “in progress” and “handover” environments. Designs that were ready to develop were “committed” to Zeplin.</p><h3>Stage 5: Retros</h3><p>No process is ever perfect. Retros have outsized importance when introducing operational changes. Before implementation, we used retros to help persuade reluctant PMs that the process was malleable and adaptable. In the retros themselves, people were encouraged to share their views without blame, and the whole team accepted responsibility for the problem. We made some major tweaks to the process at first, focusing on <strong>making estimation more accurate</strong>, <strong>introducing flexibility into the delivery</strong>, and <strong>improving communication</strong> by adding lots of new sync meetings.</p><h4>THREE BIG TAKEAWAYS</h4><h3>Squads need more than one designer, or they need to pool talent</h3><p>It’s impossible to carry out a full design cycle with one designer in a squad — turnaround times are two weeks at most. With all the hats that a product designer is supposed to wear (research, creative, wireframing, prototyping, usability testing, UI design &amp; asset production, QA), something is going to get missed out.</p><h3>The design process needs to be visible</h3><p>Predictability must be established in a design process, even if you don’t dogmatically follow one. It was difficult to demonstrate the value of discovery and research tasks until they were recorded and budgeted for in our project management software.</p><h3>Delivery needs direction</h3><p>Features, when broken down into agile stories, tasks and sub-tasks, can result in a scattegun approach to the final experience. When we moved our design sprints outside of engineering sprints, feature deliveries became larger, more strategic, and more impactful. By delivering multiple improvements at once <strong>we quadrupled conversion in the sign up experience</strong>.</p><p><em>Credit goes to </em><a href="https://www.linkedin.com/in/alexhorstmann/"><em>Alex Horstmann</em></a><em>, a master in organisational change and digital transformation — for protecting, nurturing and encouraging us. And especially </em><a href="https://www.linkedin.com/in/kieronscott/"><em>Kieron-Scott Woodhouse</em></a><em>, whose confidence, communication skills and experience got us through many difficult conversations. He’s a Jira-whisperer, able to bend this unloved software to his will. He showed me that it’s possible to use Jira for good, whilst protecting creativity and thorough design problem solving.</em></p><p><em>I’m </em><a href="http://www.andybirchwood.com/"><em>Andy Birchwood</em></a><em>, An experienced freelance product designer who specialises in UI, design systems and operations.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9291309c0a8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/fixing-design-in-squads-f9291309c0a8">Fixing design in squads</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Airline app]]></title>
            <link>https://medium.com/@andybirchwood/case-study-airline-app-91e94d106def?source=rss-bdaa251b8290------2</link>
            <guid isPermaLink="false">https://medium.com/p/91e94d106def</guid>
            <category><![CDATA[app-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[air-travel]]></category>
            <dc:creator><![CDATA[Andy Birchwood]]></dc:creator>
            <pubDate>Fri, 07 Jun 2019 07:25:40 GMT</pubDate>
            <atom:updated>2019-06-07T07:25:40.870Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CQol2XX5iO3whgNkpOWslw.gif" /></figure><h3>Recovering from a tailspin</h3><p>Our research showed us that airline passengers are obsessed with checking and rechecking their booking information. In the lead up to the day of travel, schedule changes and luggage rules are the main sources of anxiety.</p><p>Fliers also experience information overload. With almost every part of the flight experience unbundled from the ticket price and varying between destinations and airlines, booking details are variable and complicated. There’s a wide selection of edge cases that we need to support, like connecting flights, refuelling stops, large groups of passengers.</p><p>In the lead up to the day of travel, in the air, and on arrival, passenger information requirements change radically. From checking in to boarding, different slices of the booking data become vital, and then irrelevant.</p><p>We discovered a surprising number of passengers still tend to print all their documents and screenshot boarding passes in apps. This could be a response to an unnervingly fluid situation — delays and changes are so common that they are expected. The printed artefact may serve as a physical anchor to their journey.</p><p>We needed a design that clearly communicated the <strong>time-sensitive actions</strong> related to a flight, and also <strong>stayed consistent</strong> for quick and easy reference.</p><h3>First concept</h3><p>To win the budget for the project, I mocked up a high fidelity animated prototype based on some assumptions. This concept divided the content into <em>pre-flight</em>, <em>airport</em> and <em>in-flight</em>. In one sense the design was successful — with all the flashy animations, stakeholders were pleased and we got the cash for the project- but it fell short for a real life application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fo3qXFq0L-TeRoqvwlcl5A.gif" /><figcaption>The first design concept</figcaption></figure><p>The bottom navigation clearly communicated the idea of grouping the content around the user journey, but it was binned when we realised it made no sense to have the customer manually switch between these modes — a companion app should be intelligent enough to do this automatically.</p><p>The design also had a checklist — a commonly requested feature in our research. Later, we came to think that this represented an underlying desire for passengers <em>to know what they’ve done and need to do next</em>, rather than a specific feature request, so this was also binned.</p><p>However, there <em>were</em> elements from this concept that ended up in the final version —context sensitive Google Now-type cards, for example.</p><h3>The flight-centric design</h3><p>The second major iteration divided the flight itinerary into <strong>flight cards</strong>. Each card represented a flight in a horizontal carousel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oSt4Lim_0Y9GNrKFTp9BKw.png" /><figcaption>The various states of flight cards</figcaption></figure><p>In the lead up to the flight, buttons for Advance Passenger Information and check in appeared and disappeared when they were no longer required. Updates to the itinerary or flight would be displayed inside the cards. Displaying flight delays and changes next to flight data was a logical choice.</p><p>After researching best practice in mobile design, the team chose a bottom navigation bar. The <strong>Home</strong> tab was mainly concerned with the more context sensitive events and the day of travel, and the full booking information was accessed through a dedicated <strong>Bookings</strong> tab.</p><p>Initially the <strong>Home</strong> tab was fairly clean and simple, but as time went on and edge cases were designed for, we added a lot of extra data to the <strong>flight cards</strong>. The distinction between the <strong>Home</strong> and <strong>Bookings</strong> sections blurred as more flight detail was added.</p><p>On the UI side, the <strong>flight card</strong> layout created problems between devices. Elements like the check in buttons and travel related warnings were designed to appear and disappear in consistent positions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rWlnsGto3varAfwU3-kCZg.png" /><figcaption>Flight Cards weren’t fully responsive to screen size</figcaption></figure><p>The horizontal carousel meant that the height of the flight cards had to be optimised for the smallest supported device (iPhone 5S). With fixed size limits, we were underutilising the space on larger devices and leaving large areas of empty space in and around the cards.</p><p>This approach wasn’t future proof either — elements added later would have caused a lot of redesign effort to squeeze them in to smaller devices. The carousel was initially a popular interaction choice for the home screen, but it became a burden as the project went on.</p><p>The <strong>Bookings</strong> tab was a more traditional vertical itinerary view of all the flights in the booking. A secondary purpose was navigation to the <strong>flight detail</strong> view. Again this was a perfectly logical approach — you consume one flight at a time, so slicing the booking data into flights seems intuitive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pNS_wsMMsWQUCuVpXqqOMw.png" /></figure><p>However, some ancillaries are edited across flights — you would most likely want the same luggage or sports equipment coming back as flying out, for example. To check or change this for all flights would mean navigating in and out of flight detail views through the generic “show details” buttons.</p><p>In testing, we found the generic “show details” buttons to be a flaw — we usability tested several versions of the copy, and participants often had trouble predicting exactly what information or actions would be on the flight detail view.</p><p>The design was developed for a year. But when we looked at adding transactions (the ability to book ancillary products like seats, extra bags and meals), it became clear that the design was unsustainable.</p><p>Most of the itinerary flight data was repeated in the <strong>home</strong> and <strong>bookings</strong> sections. When it came to booking ancillaries, the data and actions were split down several levels of navigation. The <strong>flight detail</strong> views were long and complicated, and in testing we saw people ping-pong scrolling from top to bottom looking for the detail.</p><p>Fewer than 0.5% of travellers have more than one active booking. We felt that the dedicated <strong>Bookings</strong> section was unnecessary and was the culprit in the duplication in data.</p><p>Despite a looming internal release, we thought the risk of a big redesign was worth the benefit, and took a step back.</p><h3>The Action Card design — “What next?”</h3><p>We needed to reinvestigate the user requirements and approach the problem in a different way. From booking, to preparing, travelling to the airport and in the air, the passenger’s journey is a linear process. In order to reduce the information overload of the previous design, we needed a layout concept that was a lot more <em>time and context focused</em> than the flight cards.</p><h3>Action Cards</h3><p>We revived the “Google Now” style cards from the first design concept. But we wanted a design that achieved even more focus than that, so we reduced the number of cards down to one. By presenting the <em>single most important</em> piece of information and action, we want to reassure our passengers by always being able to answer the question “What do I need to do next?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/819/1*lzeBpW8wbWMMi1lqNvPq6Q.png" /><figcaption>Action Cards changing over time</figcaption></figure><p>The main portion of the home screen of the app is given to <strong>Action Cards </strong>that inform passengers of their latest status;<strong> </strong>like checking in, retrieving boarding passes, going to the gate and so on, together with a call to action to immediately respond to the status.</p><p><strong>Action cards</strong> are delivered synchronous to travel preparations and journey. Only one is displayed at a time, and a system of prioritisation has been devised to make sure the most important or mandatory cards are displayed first. On the day of travel, the cards also contain the flight times for the next flight. Any associated delays will also be displayed here.</p><h3>Booking Card</h3><p>Switching between bookings is a secondary activity — so we relegated that function to the burger menu. The <strong>Booking Card</strong> can now be focused around a single booking. It is always available at the bottom of the screen, following the popular ergonomic <a href="https://www.material.io/design/components/sheets-bottom.html#">bottom sheet pattern</a> introduced in apps like Uber, Google maps, and Waze. From here the passenger can swipe it up at any time to see all of the booking details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/243/1*yPwdJwufUDfiAL3bQsIEYA.png" /><figcaption>The booking card</figcaption></figure><p>To reduce the amount of clutter, we use a hub &amp; spoke navigation model. The Booking Card is the permanent hub for this paradigm.</p><p>Many attempts were made to summarise the booking information itself concisely for this view (seat numbers, baggage allowances and meals), but they all tested badly as none conveyed the complexity behind outbound/return legs, fare inclusive/extra allowances or connecting flights. Reducing the Booking Card to simple navigation only, test participants could instantly see how the information was arranged.</p><h3>Overlays</h3><p>The check in and flight ancillary details are allocated separate views that we call <strong>overlays</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bIBhmXb0zWJ5bSwuL9ijFQ.png" /><figcaption>Ancillary overlays</figcaption></figure><p>Most respondents in the initial research wanted all their details “in one place” (like a huge one-page printout). However, we learned from the second iteration of the design that the sheer amount of data involved in a flight booking is overwhelming, especially presented all at once on a mobile screen.</p><p>One of the criticisms I would level at digital airline experiences are the large number of different interactions used to convey the complex business rules around products. Each different UI control increases cognitive load slightly. The overall impression conveyed is complexity. We were proud to find a design pattern that worked for all our ancillary products with minimum variation.</p><p>In the database, ancillary products are usually assigned to a passenger because it’s the passenger’s profile that determines the options available to them. For example, luggage rules for children are different to those for adults. The overlay complements this <em>booking › flight › passenger › ancillary</em> hierarchy.</p><p>In testing we found this pattern is initially unfamiliar to customers, especially families who tend to configure luggage for the group for the whole trip rather than individually. But because we reuse the pattern for all the ancillaries, we found this unfamiliarity is soon overcome and the flow becomes natural.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/1*GDY9PqKp6dC4jhu3xL6b1Q.png" /><figcaption>Our hub &amp; spoke model</figcaption></figure><p>The hub-and-spoke model facilitates a non-linear browsing experience that has become customary for ecommerce sites. In our Action Card design, passengers can go into several overlays and make changes to their booking before checking out in a single transaction, something they were previously unable to do in the web post-booking implementation.</p><p>With a business as fast changing as air travel, having different interaction patterns increases the design effort involved in implementing business changes across platforms. We saved lots of design effort by reusing the overlay patterns from the flight booking web application, and made steps towards a cross-platform design system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XSe2_URk0DVSCbqgpVtlug.png" /><figcaption>Overlays in on the flight booking web app</figcaption></figure><p>The <strong>Overlays</strong> serve one more important function. They underpin the <strong>Action Card</strong> design, by making it possible to act on information from anywhere in the app, including the <strong>Action Cards</strong> on the home screen. Passengers make changes to their booking without losing context, as they would in a linear flow. In this way, the navigation structure is much flatter, specific, and intuitive, solving the problem we previously encountered with generic “show details” buttons.</p><h3>Testing results</h3><p>The <strong>Action Card</strong> design tested extremely well for simple outbound-return bookings. All test participants understood that action cards are time sensitive and were reassured that they would receive the right information at the right time. All participants found and navigated the <strong>booking card</strong> successfully.</p><p>The <strong>overlays</strong> also tested well for simpler flight itineraries. Around 80% of customers have this type of booking. They didn’t test quite as well for bookings with connecting flights, which are usually served by a different airline and are subject to different business rules. Participants often missed the distinction between the main flight and their connecting flights, or failed to understand why the business rules might be different for those flights. These comprehension problems are common to every interface we’ve designed to solve this issue, so more work is needed on this theme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SvfN7sAob6WwI8JkjXUMTQ.jpeg" /><figcaption>Usability testing Action Cards in Berlin</figcaption></figure><p>One insight we observed was a learned lack of trust in airline apps in general. Most participant specifically called out gate announcements, for which they would always double check departure boards. This is a failure of the airline industry as a whole — data sources tend to be clunky and unreliable, undermining the convenience and service enhancements that apps offer.</p><p>Participants also recalled taking screenshots of boarding cards, despite the fact that in apps you can usually access them offline. This behaviour has probably carried over from the web. We need to do more to educate customers on the offline capabilities of apps.</p><p>These problems, though significant, weren’t fundamental to the Action Card design approach, and we feel confident that we’ve given a strong design foundation for solutions to these outstanding issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cpiiTMiPCnZyvQVUy-ujvg.gif" /></figure><p><em>Thanks to the all the team who worked on this project — </em><a href="https://twitter.com/leemcivor"><em>Lee McIvor</em></a><em>, </em><a href="https://www.linkedin.com/in/kasia-grabowicz-36a25769/"><em>Kasia Grabowicz</em></a><em>, </em><a href="https://www.linkedin.com/in/mike-middleditch-9aa7845/"><em>Mike Middleditch</em></a><em>, </em><a href="http://www.pollya.uk/"><em>Polly Averill</em></a><em>, </em><a href="https://www.linkedin.com/in/kerichilds/"><em>Keri Childs</em></a><em>, </em><a href="https://www.linkedin.com/in/chiwah-liu-85155543/"><em>Chiwah Liu</em></a><em> and </em><a href="http://www.playserious.co.uk/"><em>Mo Baghdadi</em></a><em>.</em></p><p><em>I’m </em><a href="https://www.linkedin.com/in/andybirchwood/"><em>Andy Birchwood</em></a><em>, a digital designer specialising in product design strategy and design systems. I’m available for new contracts! </em><a href="/service/mailto:andy@overhead.tv"><em>Get in touch</em></a><em> if you want me on your team.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91e94d106def" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Framer X and the DNA of design systems]]></title>
            <link>https://blog.prototypr.io/framer-x-and-the-dna-of-design-systems-9cd7ff6e1aa?source=rss-bdaa251b8290------2</link>
            <guid isPermaLink="false">https://medium.com/p/9cd7ff6e1aa</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[framer-x]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Andy Birchwood]]></dc:creator>
            <pubDate>Wed, 29 May 2019 11:00:56 GMT</pubDate>
            <atom:updated>2019-05-29T15:06:06.947Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/1*VMMI5qytVJfRp7YrXk_juA.jpeg" /></figure><h4>The days of lobbing flat designs into Invision and Zeplin for developers to interpret in our absence may soon be over.</h4><p>Framer X is an altogether different proposition to what has gone before, and one UI specialists need to skill up in — because it fundamentally changes our workflow and responsibilities. The innovation in Framer is certain to spread to other design applications. It’s not going to be an easy road, especially for designers who don’t like coding, but it’s going to be interesting.</p><h3>Bumpy curve balls</h3><p>For a UI designer, Framer X currently has a very bumpy difficulty curve. The interface starts out absurdly minimal. You soon encounter unintuitive concepts like “design components” and “code components”, and the subtle but fundamental differences between Framer frames and Sketch symbols.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*0IDVbvRyLk0BU8KYgDfTVg.png" /><figcaption>Where to start?</figcaption></figure><p>Those initial impressions are an uncanny valley that’s not too hard to cross now that <a href="https://www.framer.com/docs">Framer X’s API documentation</a> has finally been published. After a bit of poking around in the interface and the docs, the Framer X approach starts to make sense. Frames are just as intuitive as symbols — but they also replace vector shapes. Smart presets on constraint-based alignment makes resizable components even easier than Sketch.</p><p>The component store and team store have enormous implications for working as a team. They formalise and extend the old process of symbol libraries into fully functional components, allowing you to leverage React components in a way that’s as expressive as downloading a sketch UI kit. With features like those, knocking together a simple prototype with built-in or publicly available components is a cinch.</p><p>On the flip side, going beyond the default parameters in components becomes very complicated, and you need a very good foundation in React (or the ability to call on someone who has) very quickly. I once tried to fix a knotty double scroll bug on an instance of the framer draggable component when it was embedded in a a different component from the store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*xrYF7BRwJdYKebSxcFVapA.gif" /><figcaption>Grrrrr</figcaption></figure><p>I hit a wall, several walls, all of which compelled me to learn a lot more about how Framer X (and by extension React) actually works.</p><p>Whilst clinging onto dear life from a particularly steep part of the learning curve, I had an epiphany. It had nothing to do with the double scroll bug, which remains unsquashed. The function that opened my mind to Framer X’s unique take on the future of design tools was <a href="https://www.framer.com/api/property-controls/"><strong>property controls</strong></a>.</p><h3>Property Controls: Great Scott!</h3><p><a href="https://www.framer.com/api/property-controls/">Property Controls</a> are a bit like overrides in Sketch. They allow you to customise the Framer interface to make any feature of a UI component editable in the Framer sidebar. This is especially useful when prototyping with UI components from the store. A designer can quickly control unique or non-standard features of a component without any coding at all. Switching vertical scrolling to horizontal in a scrolling component or a stack, for example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/211/1*nhnGEdAfXrQI4sZ9XDqUyg.png" /><figcaption>The direction Property control of a Framer X stack component</figcaption></figure><p>Property controls adjust specific properties and variables defined by the developers when the React component is coded, so you know instinctively what parameters are available in the production code.</p><p>With property controls, the relationship between production code and prototype code shrinks to almost zero. If you can usefully prototype with production components from the design system (Or <em>team store</em> as Framer calls it), or fine tune their appearance <em>even after they have been coded up</em>— suddenly you have the design-prototyping-development workflow of your dreams; handoffs can happen in any direction, at any time. Prototypes can use live data sources. With the latest release of Framer X, a feature called <a href="https://www.framer.com/blog/posts/announcing-framer-bridge">Framer Bridge</a> attempts to formalise this flexible process.</p><h3>Good feels</h3><p>Part of the role of a Digital product designer is to translate a brand into UI styles that express the core values of the company and product. It’s a form of <a href="https://en.m.wikipedia.org/wiki/Synesthesia">synesthesia</a> that seems to make non-designers uncomfortable, so it’s often reductively called “beautifying” or “the fluffy stuff”. A designer is defining how a UI <em>feels</em> - transforming absolute values with no inherent feeling into something that their customers instinctively know is right. Turning notes into music. To most people, it’s a <a href="https://www.thevintagenews.com/2017/12/06/glenn-seaborg-alchemimist-in-1980/">kind of Alchemy</a>. UI designers play on the mystery and encourage the myth, but really they shouldn’t.</p><p>The “feeling” of a UI can be complicated to define, but not impossible. Hence the best design systems try to outline <em>design intent </em>— like <a href="https://material.io/design/environment/elevation.html">Material Design’s concepts of “elevation”</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*i_Zy469xqfSMtJvNJb0AiA.gif" /></figure><p>It’s these parts of a design system which make it interesting and unique. It’s this DNA that the UI designer spins into myriad component forms, trying to create new things without diverging too far from the original definitions of the brand.</p><p>Interestingly, the official Framer store Material Design components in the Framer X store don’t yet fully exploit Material’s “Elevation” guidelines. The card component could easily have a property control for <em>elevation</em>, which has the effect of automatically applying the correct drop shadow and z-index to the component.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/1*1B1eqW0Em3LQ0GLRVgVKkQ.png" /></figure><h3>Global Property Controls</h3><p>Custom properties are ostensively designed to change variables and functionality of individual components. They could also be used to change the properties of an entire design system — and this has some very interesting consequences for UI designers.</p><p>UI Frameworks like Bootstrap and Foundation already have <a href="https://getbootstrap.com/docs/4.3/getting-started/theming/">theming functionality</a> — global settings expressed as sass variables that allow you to quickly set global colours, fonts, grid spacing etc:</p><pre><em>// Default padding for button.</em> <br>$button-padding: 0.85em 1em !default;  </pre><pre><em>// Default margin for button.</em> <br>$button-margin: 0 $global-padding $global-padding 0 !default;  </pre><pre><em>// Default fill for button. Is either solid or hollow.</em> <br>$button-fill: solid !default;  </pre><pre><em>// Default background color for button.</em> $button-background: $primary-color !default;  </pre><pre><em>// Default hover background color for button.</em> $button-background-hover: scale-color($button-background, $lightness: -15%) !default;</pre><p>Similarly, a design system usually has a set of global visual properties that apply to the whole interface. Over the development of a design system, with multiple designers working in multiple teams, they are the hardest to keep consistent to the original intent. Tastes wander, interpretations differ.</p><h3>Design DNA</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/213/1*yUVYXq2mOIjFCvUdyYXcdA.png" /></figure><p>With global property controls in a design system, we could abstract the feel of an interface away from the absolute values of individual components. We could start talking about previously nebulous terms like <em>roundness</em>, <em>bounciness and density </em>as editable features of our entire UI kit or component library. We could come up with design system specific concepts like <em>elevation</em>. These values could be expressed as relative units, from which the absolute values of the individual components could be derived. Of course, these broad strokes would work best at the beginning of a project with the basic UI kit. Individual or more complex components would still require fine tuning— but Framer‘s system of overrides has you covered there, too.</p><p>We could take it further. The potential is there with tools like Framer X to create a UI kit that instantly responds to the fundamental personality of a brand - it’s DNA. In the past, I’ve tested the “feel” of an interface with bipolar scales. What if we created global property controls for these more esoteric concepts and defined their effects in the UI?</p><h3>The future</h3><p>With tools like Framer X, the alchemy of “look and feel” could be within reach of non-UI designers. Getting started with new products with a well-defined Framer X design system would take next to no time at all. Even a machine could learn the kind of visual styles that represent brand ideals. Machine learning could analyse branded materials and style guides and algorithmically generate a UI kit with a “feel” sourced from thousands of Framer X design systems.</p><p>Machines are replacing skilled jobs across industries. Although the threat of AI driven screen design <a href="https://thegrid.io/">has been confounded</a> multiple times, Framer X has shown me how it could work. If we can teach machines how to express brands using design systems, they could soon carry out much of the hands-on UI work.</p><p>If UI designers are going to stay relevant, we’re going to have to get a lot better at understanding the DNA-like abstractions that connect the code of our design systems with how they feel to the end user. The good news is, we’re an adaptable bunch, and technology like Framer X lets us focus less on menial and repetitive UI tasks, and focus more on the underlying design DNA of our products.</p><p><em>I’m Andy Birchwood, a digital designer specialising. in product design strategy and design systems. I’m available for new contracts! </em><a href="/service/mailto:andy@overhead.tv"><em>Get in touch</em></a><em> if you want me on your team.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff51076%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Ff51076%2F&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Ff51076%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href">https://medium.com/media/b85dfbb5286d8a25cf2e754b9462cf45/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9cd7ff6e1aa" width="1" height="1" alt=""><hr><p><a href="https://blog.prototypr.io/framer-x-and-the-dna-of-design-systems-9cd7ff6e1aa">Framer X and the DNA of design systems</a> was originally published in <a href="https://blog.prototypr.io/">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Jetset design system]]></title>
            <link>https://medium.com/@andybirchwood/case-study-jetset-design-system-6474a54729e?source=rss-bdaa251b8290------2</link>
            <guid isPermaLink="false">https://medium.com/p/6474a54729e</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design-operations]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Andy Birchwood]]></dc:creator>
            <pubDate>Thu, 09 May 2019 13:17:17 GMT</pubDate>
            <atom:updated>2019-05-10T14:37:09.111Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*grPJ0-QFR-uo9fEu3D9pYw.png" /></figure><h3>A design system on a shoestring, 3 years in the making.</h3><p>I joined Thomas Cook Airlines to work on the UI designs for a new flight booking system.</p><p>The design of the booking app had already begun and was rapidly evolving and older designs were falling out of step. There was no central source of truth or conceptual documentation for buttons, form elements or larger components.</p><p>As the project was was new, there was a lot of iteration and re-evaluation of UI elements. The artwork was exclusively maintained in page-level PSDs. Even a slight tweak to a button style would require the agonising update of many Smart Objects and Layers in hundreds of PSDs across three hard breakpoints. After dutifully adding lots of unique button classes to deal with the variations, the developers were the first to spot inconsistencies between elements — which for a “pixel perfect” designer is irritating.</p><h3>The debt restructure</h3><p>We had to get serious with our UI elements. Based on their feedback, we conducted an audit of all the UI work so far. We collected every UI variation and type style across the whole project and ran sessions to agree between the whole UX and UI team which styles would be the best global style.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*Chj2KYkKnTwynmKr-jTZ1A.png" /></figure><p>I wasn’t too enamoured with the look and feel of the first UI kit. But the review sessions were the first steps towards a design system. They teased out the thinking behind each UI element — for example the hierarchy of button styles or why and when we use icons. They helped us to begin to define usage rules around the elements and debate a team-wide approach to solving common interaction problems. They solidified the first iteration of our <strong>design principles</strong>.</p><h3>The Sketch migration</h3><p>After the audit, it wasn’t long before I pushed a switch to Sketch and got to work with symbols. Front end development had already begun in Angular. Without the time to go back and recreate all the page-level artwork from scratch in Sketch, this migration happened organically as we moved across sprints in various projects. Even now, some of the oldest designs are still in Photoshop, but the vast majority of page level designs are now properly documented and connected to Sketch symbols, which have the same or similar names as their css counterparts.</p><p>My UI kit sketch library file started simply, with the most common elements classified and codified. Almost straight away, I was able to start feeding the unified UI kit elements into dev sprints. Even though it caused more rework in the short term, the developers received the UI kit enthusiastically, as they could see immediately that much more time could be saved later if we organised and named our UI elements in the same structure as their code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xeedDhRyxDrTNG7ZC1UrdA.png" /></figure><p>But we found this type of design debt is expensive to pay back: One entire dev sprint was spent deleting redundant button variations and unifying these button classes in the developed code. It would have been far cheaper to set up a component-centric workflow at the start, and allow the UI kit to evolve whilst retaining the ability to update symbols in projects without changing css class names. It’s a chicken-and-egg situation though, since most elements can’t be fully validated or tested until they appear in page level designs across a whole project. This was the first hint to me that a design system can’t be designed. It emerges from a lot of other designs.</p><p>We’ve now reached a point where all of our UI elements are connected to a UI kit and component library shared with Google Drive. This was an enormous improvement over the PSD workflow. We discovered Sketch has it’s own limitations, especially around version control, and we have to be extremely careful when updating the library, not to overwrite each other’s work or break things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GxZRANUcPad0uN2ZRTrivQ.png" /><figcaption>The Sketch symbol page from the UI kit</figcaption></figure><p>We tried a few version control services like <a href="https://blog.prototypr.io/8-reasons-why-designers-use-plant-for-version-control-795c72a61c27">Plant</a> and <a href="https://www.abstract.com/">Abstract</a>, but these seemed a little overpowered for our needs — not to mention the requirement to train up designers on the developer concepts of <em>branches</em> and <em>merging</em>. So the UI kit still sits in Google Drive. As long as we communicate well enough when we’re updating it, we haven’t lost any work so far.</p><p>After establishing the UI element library, we felt confident enough to begin documenting more complex patterns.</p><h3>Being principled</h3><p>Design principles are an important aspect of a design system. Web designers once had a limited palette of interaction options, restricted by user ability and browser compatibility. But interaction patterns have come a long way, driven by mobile devices and touch interfaces, which are much more organic and intuitive.</p><p>With so many different ways to solve an interaction problem, group reviews of interaction designs can get long and intractable. The <strong>design principles</strong> help resolve discussions of principle, by expressing an <strong>intent </strong>behind the choice of interaction. Here’s the ten principles we established for the flight booking engine:</p><ol><li><strong>Sell the flight first</strong> — We don’t have a customer until they make their first purchase</li><li><strong>Separate content from config</strong> — Separate the decision to add a product from the more complex interactions to configure it</li><li><strong>Make choices transparent</strong> -The customer must understand the results of the decisions they make</li><li><strong>Don’t confirm</strong> — Be tap-friendly. Avoid unnecessary submit buttons</li><li><strong>Make undo easy</strong> — Customers make a lot of mistakes, don’t tie them in</li><li><strong>More meaning, fewer words</strong> — Keep it short, remove extraneous words</li><li><strong>Focus attention</strong> — Present one decision at a time</li><li><strong>Help customers learn</strong> — Make a consistent language of interaction patterns</li><li><strong>Think big, think small</strong> — Design interactions optimised for all devices — try not to create two experiences</li><li><strong>Goals &amp; tasks first</strong> — Prioritise customer tasks over a neat IA</li></ol><p>One of the criticisms I would level at digital airline experiences are the large number of different interactions used to convey the complex business rules around ancillary products. Each different UI control increases cognitive load slightly. The overall impression conveyed is one of complexity. We were proud to find a design pattern that worked for all our ancillary products with minimum variation.</p><p>The <strong>ancillary overlay pattern</strong> we devised expresses these design principles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*HT2dCTEYphpWz6xkQLkDtg.gif" /></figure><p><strong>Sell the flight first</strong> — To reduce friction we allowed the customer to check out for their flight without seeing any of the complexity around products. There’s a single call to action / decision point around each ancillary product before the configuration begins. Other sites put the configuration up front, pushing several simultaneous decisions onto the customer.</p><p><strong>Separate content from config </strong>—Persuasive content is presented in the page, configuration actions are completed in the overlays. This allowed us to keep our sales messaging persuasive and focused on the single decision to add the ancillary product.</p><p><strong>Focus attention</strong> — Value judgements around ancillary options are usually multi-dimensional decision, but we presented one decision at a time, simplifying the decision making process to steps.</p><p><strong>Don’t confirm </strong>— Selections are made instantly, without an additional click</p><p><strong>Help customers learn</strong> —Unlike other airline websites, all the ancillaries follow this interaction pattern or a close variant.</p><p><strong>Think big, think small</strong> — With a fast growing mobile booking segment, we prioritised the mobile/touch experience. The desktop experience was enhanced later — but we tried to bear all platforms in mind.</p><h3>The component workflow</h3><p>After establishing the principles and their relationship to the design patterns, we tried to improve our component design workflow by delivering component-level specifications rather than full screen designs. Previously the developers were making educated assumptions about alignments and constraints, these deliverables made all of that explicit with markups overlaying the designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4KYjsZcho8OGXIQh3IHHmw.png" /></figure><p>There was some resistance from some designers who were used to publishing full page designs to Zeplin without markups. For them, manual markups were a step back. But we persisted in trying to persuade every designer to get on board with this process, because it made them think more explicitly about the underlying intent behind each small design decision. <a href="https://medium.com/tap-to-dismiss/constraint-layout-for-designers-3c665cb4d074">Creating Sketch symbols for the markups</a> sped this process up a great deal.</p><p>This was a big step up in the volume of artwork and documentation. The strain of having a small design team without dedicated resource began to show. The extra markups step caused about a 50% increase in workload. Developers were much happier with our documentation and it cut their time down, but it was difficult to demonstrate the value of this extra time to product managers, who were rightfully focused on delivery of their features.</p><p>Not only that, but 40 components had already been deployed, meaning we’d have to go back and bring all the artwork for them up to scratch.</p><p>As a result, the component-centric design process was implemented more haphazardly than I hoped. But at last every designer was thinking <strong>component-first</strong>, rather than page-first.</p><h3>Joining the Jetset</h3><p>After we had refined our UI processes, we enlisted the help of the UX team to begin to organise our elements and components, so that we could plan our design system site. A lot of great UX and UI work went into the IA, the navigation and content of this site. It turned into a really good looking, well thought out design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lPUaqSe7RCJmhlYliBwyVA.png" /><figcaption>The Jetset homepage</figcaption></figure><h3>Developers, developers, developers</h3><p>Our excellent development team at <a href="https://incendiaryblue.com/">Incendiary Blue</a> had already begun to manage their codebase in a similar structure to the site we had designed. Their ultimate goal was to have a set of versioned Angular &amp; Vue front end snippets that could be invoked in the IDEs by a simple abbreviation. The foundation work in vue.js allowed the near-automated generation of a basic design system site. Unfortunately, we didn’t discover this until after we had the Jetset template designs finalised.</p><p>In retrospect, using this code as a basis for and MVP, and incrementally improving it would have saved a lot of development effort. Instead, Jetset was envisioned as a brand new product with it’s own templates and components. With no developer time to commit to building these new templates, development was repeatedly put on a back burner.</p><p>The hard lesson we learned from this is that a design system is an emergent property of continuous cycles of design &amp; deployment. You can’t immediately jump from zero to <a href="https://material.io/">material.io</a>.</p><h3>Where we left it</h3><p>Thomas Cook moved digital operations up to Manchester, and the London team handed over the design system work before disbanding.</p><p>Many posts about design systems recommend making the design system into a product. This make sense — A design system has it’s own users, use cases and <a href="https://medium.com/@didoo/measuring-the-impact-of-a-design-system-7f925af090f7">success metrics</a>. But what if you don’t have the luxury of dedicating multiple designers to the product?</p><p>At Thomas Cook Airlines, we were already overwhelmed with projects, replacing the CMS, launching a cross platform React Native and Angular app built on a new set of web services, as well as implementing product changes for the rapidly evolving airline business.</p><p>The operational budget didn’t account for changes in design operations, which usually add overhead to urgent changes to the website. This overhead is easily ignored in the rush to get things built. Design and technical debt quickly snowballs to an unmanageable size. Design begins to cost more, take longer, and reduce in quality.</p><p>The other challenge was keeping the developers engaged in the process. Despite their enthusiasm, from development tokens to understanding the shortcuts available in modern front end frameworks, we didn’t take advantage of the technical tools in order to pair back development effort enough to produce the MVP.</p><p>The most successful part of the initiative was devising and bedding in component-centric thinking, which made for a quicker design process across all projects, and a more robust and consistent codebase.</p><p><em>Thanks to the all the team who worked on this project —Rich Smith, Marceli Cieplik, Mo Baghdadi, Paul Mason, Lee McIvor, Phil Benoit, Bianca Theunissen, Alex Joe Katz at Incendiary Blue.</em></p><p><em>I’m </em><a href="https://www.linkedin.com/in/andybirchwood/"><em>Andy Birchwood</em></a><em>, a digital designer specialising in product design strategy and design systems. I’m available for new contracts! </em><a href="/service/mailto:andy@overhead.tv"><em>Get in touch</em></a><em> if you want me on your team.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6474a54729e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Throwing out the kitchen sink]]></title>
            <link>https://medium.com/@andybirchwood/case-study-throwing-out-the-kitchen-sink-fad868f38020?source=rss-bdaa251b8290------2</link>
            <guid isPermaLink="false">https://medium.com/p/fad868f38020</guid>
            <category><![CDATA[design-strategy]]></category>
            <category><![CDATA[email-marketing]]></category>
            <category><![CDATA[email-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Andy Birchwood]]></dc:creator>
            <pubDate>Mon, 18 Mar 2019 16:11:16 GMT</pubDate>
            <atom:updated>2019-03-19T10:00:56.198Z</atom:updated>
            <content:encoded><![CDATA[<h3>Quadrupling email revenue for an airline with barebones email designs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/1*4n1Xx0k-BrfbaFzuJ8-uUg.png" /></figure><h3>Why are emails so important to airlines?</h3><p>For the past 20 years, <a href="https://www.skyscanner.net/">Skyscanner</a> and similar sites have driven service design in the airline industry. What was once an experiential product has turned, through successive generations of unbundling, into a price-first race to the top of search results on price aggregators. The things that used to be a value-add to fares, like reserved seats, extra luggage, and food, are now optional extras. In the airline industry, these are called <strong>ancillaries</strong>.</p><p>The airline industry responded by pivoting to selling ancillaries as the main profit driver. With long haul fare classes now available <a href="https://www.travel-news.co.uk/11212/2018/10/thomas-cook-airlines-launch-long-haul-economy-light-fares/">without checked-in luggage included</a>, and short haul fares without hand luggage, there’s now very little left to unbundle, unless airlines can <a href="http://business.time.com/2012/11/12/new-low-for-flying-standing-room-only/">figure out how to make you stand</a>. Adding to the urgency, the margins are much higher on ancillaries than on the ticket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uDQqDZ7B_FGqSlHk9KsXkg.png" /><figcaption>Typical airline ancillary products</figcaption></figure><p>Email is one of the most important channels that airlines use to sell ancillaries. Once you’ve booked your flight, the airlines have weeks of second chances to sell you ancillaries before you fly.</p><h3>The kitchen sink approach</h3><p>For years, the strategy was to send 4–6 post booking promotional emails to every lead passenger, depending on how late you booked.</p><p>The number 6 seemed arbitrary. There didn’t seem to be a clear picture of how that number of emails was chosen as optimal. That number had become fixed. The email templates were referred to as their number “PB 6”, with no reference to what the emails were originally for.</p><p>These emails had very low open rates averaging <em>less than 10%</em>. Some people — <em>most people — </em>were not opening emails. There was a fear from the marketing side that a customer might “miss” a promotion if it was only included in one or two emails. The apparent solution to this was to send identical emails with <strong>every ancillary product promotion included</strong>. I’ll call this the <strong><em>kitchen sink approach</em></strong><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JhXgmZkNEJS8QCZq4UtnDw.png" /><figcaption>The kitchen sink approach</figcaption></figure><p>Although the “hero” content of the email differed, the overall impression that the <strong>kitchen sink approach</strong> gave was of a piece of junk mail sent repeatedly. I suspected that once people learned that the emails were virtually identical, and full of sales messages instead of useful information, their trust dropped to zero — and they were ignoring or junking future emails.</p><p>The <strong>kitchen sink approach</strong> also led to customers missing some important information buried in the emails — like visa requirements, and details about their connecting flights — and this was increasing the number of support calls.</p><p>We’ve done a ton of research about holidays. We know, for most people, the lead up to travelling is a stressful time. Airlines have an opportunity to reduce that stress, by providing the right information at the right time. The post-booking focus on selling ancillaries conflicted with this aim, and at that time, was completely burying it.</p><p>With more ancillary products becoming available, and new marketing initiatives each year, the emails grew longer and longer. They were full of content of limited value to customers, like out-of-date awards badges and links to blogs and marketing campaigns. These were expensive to maintain and code. Most of the design effort was going into maintaining these emails. The fundamental design questions weren’t being asked.</p><h3>A lightbulb moment</h3><p>I looked outside the travel industry for inspiration. I’ve been floored by the emails I get from <a href="http://bulb.co.uk/refer/andrew4326">Bulb</a>. From the disarming, creative copywriting to the quirky animations, I rarely get irritated with an email from <a href="http://bulb.co.uk/refer/andrew4326">Bulb</a> — even when they are nagging me for a meter reading. Emails focus on one primary message, with a minority containing referral messages or marketing. I tend to open every one, and even if i’m not interested in the content, I’ll enjoy the animated eyecatcher image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*24H_wXJqLA-Y7RJOJbS75g.png" /><figcaption>Gorgeous, quirky emails from Bulb</figcaption></figure><p>I wanted to replicate this feeling. I wanted our customers to feel like we were trying to help, rather than barking BUY NOW. By leading with useful information about their booking, and piggy-backing secondary upsell messages, we could build, then maintain trust in our communications.</p><p>Following the Bulb example, I pitched a hypothesis that sending <strong>fewer, more specific</strong> emails, <strong>leading on useful messages</strong> rather than sales messages, and <strong>reducing graphics, </strong>would increase engagement and conversion.</p><p>It felt counter-intuitive to the marketing team, who were understandably reluctant to risk revenue. In my favour, the fair winds of GDPR were blowing, so I piggybacked the design change on top of requirements to meet the new, stricter legal definitions of unsolicited spam. We decided to test the approach with the email that promoted seats.</p><p>Without an expensive A/B testing platform, we had to get creative with the technicals. We split the traffic for the email based on whether the booking number was even or odd. it was crude, but it was all I needed to test the hypothesis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZBDnJP8xidQ-qQzJQst-3w.png" /></figure><p>To test the two extremes, I removed <em>all</em> graphical promotions from the email that promoted seats, and made the new approach text-only. The text-only approach gave us the opportunity to introduce a more strict hierarchy in the content — allowing us to front-load the messaging in the <a href="https://www.nngroup.com/articles/inverted-pyramids-in-cyberspace/">classical inverted-pyramid approach</a>.</p><p>I hypothesised that the high-design-effort graphics weren’t adding much value for customers, and may even be reducing their comprehension of the main message. My long term plan was to reintroduce creative eye-catcher graphics once I had proven the hypothesis, and to give a new baseline and strategy on which to build creatively.</p><p>From extensive user interviews, we knew that our customers often get confused about seating policies. So for the copy, we focused on explaining the seating policy, then presented the options and benefits of reserving seats - and at no point did we mention prices.</p><p>We also adjusted the overall tone of the copy to help customers understand we were trying to be helpful. Previous service oriented emails contained language like “all passengers must present one form of identification on demand!”. We changed that to a more personal approach: “Remember to bring your passports or ID cards.”</p><h3>Sometimes, less design is better</h3><p>Results were way beyond expectations. Conversion rates immediately jumped by 40% and carried on climbing.</p><p>The text-only seats email performed so well, the marketing team immediately switched strategy to converting all the emails to the minimal, service-oriented design. 10 months later, we’re seeing overall ancillary revenue from emails quadruple.</p><p>An interesting, if unexpected effect was that we saw an increase in cross-sales. Because we were restricting each email to one subject, I expected sales of ancillaries to become more focused around the time the email that promoted them was sent. Counter-intuitively however, customers were reacting to all emails to book any ancillary.</p><p>To me, this was evidence that the emails can never be seen in isolation and that <strong>trust in communication works broadly across a customer experience</strong>. Emails are part of a continuous conversation with customers in a variety of channels – building trust with content is key to keeping them engaged. One message might seed the intention to buy, but it might be the next message that reminds them to act.</p><h3>Why did less content work?</h3><p>The advantage for airlines is that some information is too important to be ignored. Customers desire constant reassurance that their trip is going to plan. The ultimate goal for air travellers: to have a stress free journey, whether for business or pleasure, it compels customers to check and double check the details of their booking to make sure nothing unexpected happens. By always leading with information about the booking, we vastly increased the chances that a customer might also see the options to upgrade various parts of their booking.</p><h3>The subject line</h3><p>When you’re flicking through emails, you get a chance to make a value judgement in the inbox without opening the email. For some users, getting to inbox 0 is an addiction, and deleting or junking emails is a reflex action. If a brand becomes associated with junk, emails will be instinctively ignored or deleted.</p><p>For this reason, more customers will check an email with subject lines like “About your seats”. Fewer customers will check an email with the subject “Reserve your seats for £XX” because the intention is clearly to sell.</p><h3>Attention pizza</h3><p>User attention is a finite resource, like a pizza. Doubling the amount of messages in an email doesn’t mean people will spend twice as long considering them. More likely they will spend half as much time (or less) trying to comprehend each. We’ve just sliced the attention pizza in half.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h-P7Fv_v-GNLBayNuMUbOg.jpeg" /><figcaption>Attention pizza</figcaption></figure><p>What if customers focus on the sales message first? They will assume that all the messages are sales. Sales messages combined with personalisation make customers feel uneasy. But useful messages combined with personalisation will make customers feel reassured.</p><p>At some point, the attention pie is so fragmented, no message is clear, users give up on trying to comprehend anything at all.</p><p>If the copy is clear, simple, direct and useful. People feel like they are having an intimate conversation with ground crew, rather than standing at the back of a crowd listening to a loudhailer.</p><blockquote>To build and maintain trust when you’re communicating with customers, sales messages must be diluted by messages that customers find genuinely useful.</blockquote><p><em>Thanks to the all the team who worked on this project — </em><a href="https://www.linkedin.com/in/cathy-cibert-goton-63316536/"><em>Cathy Cibert-Goton</em></a><em>, </em><a href="https://www.linkedin.com/in/varun-khanna-bb5b1829/"><em>Varun Khanna</em></a><em>, and Andy Harrison.</em></p><p><em>I’m </em><a href="https://www.linkedin.com/in/andybirchwood/"><em>Andy Birchwood</em></a><em>, a digital designer specialising in product design strategy and design systems. I’m available for new contracts! </em><a href="/service/mailto:andy@overhead.tv"><em>Get in touch</em></a><em> if you want me on your team.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fad868f38020" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>