<?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 David Cristian on Medium]]></title>
        <description><![CDATA[Stories by David Cristian on Medium]]></description>
        <link>https://medium.com/@departive?source=rss-e1a07ecb4b46------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*yfX-6BMyvprSJ-PVNDLhsg@2x.jpeg</url>
            <title>Stories by David Cristian on Medium</title>
            <link>https://medium.com/@departive?source=rss-e1a07ecb4b46------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:27:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@departive/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[UX Designers Today]]></title>
            <link>https://medium.com/nyc-design/ux-designers-today-87f504b76edb?source=rss-e1a07ecb4b46------2</link>
            <guid isPermaLink="false">https://medium.com/p/87f504b76edb</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[new-york]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[recruitment]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[David Cristian]]></dc:creator>
            <pubDate>Sat, 08 Sep 2018 09:05:30 GMT</pubDate>
            <atom:updated>2018-11-26T19:54:02.944Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6_FWkA3iO9gbnGy3uvY9Mw.jpeg" /><figcaption>source: unsplash.com</figcaption></figure><p>Some reflections I had after interviewing a good amount of UX Designers lately:</p><ol><li>Many* UX Designers are devoted mostly to designing beautiful animations, and less to creating useful products.</li><li>Often, the number of years of experience is an unreliable indicator of proficiency.</li><li>Divergence is missing from the design process of many of the UX Designers.</li><li>Thus, refinement comes too early in the design process.</li><li>Thus, many UX Designers are not skilled at, or aware of, any prioritisation methods (of needs, ideas, concepts) as this step is often non-existent.</li><li>Prototyping comes too late in the design process.</li><li>Often, UX Designers are devoted to designing “screens”, apps and websites instead of experiences. Other touch-points in the customer journey (especially analogue) are unknown or ignored.</li><li>As nebulous as the concept of UX can be for many people, if you call yourself a (senior!) UX Designer, you shouldn’t hesitate when asked what User Experience is — at least come up with your own interpretation.</li><li>Many UX Designers execute on requirements given to them and don’t participate in defining them.</li><li>Design systems and animations are great, but a useful product is better.</li><li>Producing wireframes in isolation with your headphones on is way more comfortable than getting out on the street with a bunch of prototypes and asking people to evaluate them. That’s hard.</li></ol><p>I find fear of stepping out of your comfort zone, poor design culture or company immaturity, the main blockers for UX growth. On the other hand, skepticism, curiosity, collaboration or being comfortable with ambiguity, failure and experimentation, are some of the skills that I look for in a UX Designer.</p><p>Anything I missed?</p><p><em>*While I do use words like “often”, “many” or “any” to give a sense of my perceived scale, there is still no statistical significance behind these and you are free to challenge them in the comments section if you have a different point of view.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87f504b76edb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nyc-design/ux-designers-today-87f504b76edb">UX Designers Today</a> was originally published in <a href="https://medium.com/nyc-design">NYC Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Broken Customer Experience of the Hotel Type Accommodation]]></title>
            <link>https://medium.com/nyc-design/the-broken-customer-experience-of-the-hotel-type-accommodation-ab79f45f05ec?source=rss-e1a07ecb4b46------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab79f45f05ec</guid>
            <category><![CDATA[new-york]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[hotel]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[travel]]></category>
            <dc:creator><![CDATA[David Cristian]]></dc:creator>
            <pubDate>Mon, 05 Feb 2018 09:56:12 GMT</pubDate>
            <atom:updated>2018-11-04T20:13:49.371Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>— You need to fill this form Sir, he said<br>— Certainly, I replied with zero enthusiasm but compliant, as I was writing “Sagrada Familia” as my home address in a two-paged form with more than fifteen fields. I guess I wasn’t really in the mood to start an argument at 1 AM in the morning after a late arrival caused by a delayed flight.</blockquote><p>I had my fair share of hotel stays in 2017 (mostly across Europe and US). This made me realize how non-user centric they operate their business and design their systems (even some of the biggest hotel chains in the world).</p><blockquote>Most of the times hotel management seems to think good Customer Experience is just about having a bigger TV in your room or more pillows on the top of your bed, rather than focusing on the entire guest journey.</blockquote><p>I’m highlighting below some of the pain-points (analog or digital) experienced across the customer journey*. I’m not a pretentious guy, a clean room and a place to sleep will do, that’s why my rant here is not related to a number of stars, the TV size, the products in the mini-bar or the density of the pillows.</p><h3>1. Check-in: Personal Data Gathering</h3><p>Asking your customers to fill a huge form manually when they check-in, is a shitty experience. Firstly, check-in should be as fast and smooth as possible. When you arrive at your hotel late at night the last thing you want to do is spend unnecessary time at check-in. Heck, even if you <strong>don’t</strong> arrive late at night, the last thing you want to do is spend unnecessary time. Secondly, if you want to gather personal data at least follow the GDPR recommended practices (like <em>purpose limitation</em>) and explain to me what the hell are you planning to do with my home address? During 2017, I filled as a home address on these forms places like Sagrada Familia or La Pedrera (what can I say, I’m a man with architectural taste).</p><p>Apart from the form, another thing I observed is that many times the check-in process is lengthy not because there’s a big guest queue but because the reception staff themselves need to go through a lot of complicated steps in their systems until they can provide you the key.</p><h3>2. Check-in: Payment</h3><p>When trips are booked by the company or a travel agency there can be all sorts of little annoyances. The form sent by the travel agency to the hotel can have some missing data (e.g. the company card details) which could mean you need to pay yourself for the accommodation and expense it later. Not the end of the world and not entirely the hotel’s fault, but another area where things can be improved.</p><p><em>— Please swipe your card for incidentals.</em></p><p>Heard this countless times. You have my company’s card details on record why you want to block $200–$300 on my personal card <em>just in case</em> I smoke in the room or I destroy something. This amount can take up to 2 weeks to be released back on my debit card after I check out. You are blocking huge amounts of money daily on cards from all customers “just in case” something happens, while in reality, the number of incidents must be really small. I get it, you want to cover your back, but there must be a better way.</p><h3>3. Finding your room</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F247306334&amp;dntp=1&amp;url=https%3A%2F%2Fvimeo.com%2F247306334&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F672520250_640.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="720" height="1280" frameborder="0" scrolling="no"><a href="https://medium.com/media/e4e7d2402ced92f51e3c8c26f157a104/href">https://medium.com/media/e4e7d2402ced92f51e3c8c26f157a104/href</a></iframe><p>Most of the times at check-in, the staff places your key card in a little paper where they manually write your room number. If you stay in the same hotel for 2 weeks, that might work as you only need to remember one number, and eventually, you will memorize it. When you do 10+ hotels in 2 weeks, that’s more than ten, 3–4 digit numbers you need to remember, a new one almost every day. After a while, all these numbers will mix in your head. Multiple times my reply to “what is your room number Sir?” was “Sorry, I don’t remember”. That’s when you need to provide your surname so they can check you up in the system. The solutions for this can be multiple and as simple as attaching somehow your room number to your key card.</p><blockquote>A great CX is much more than having a website or an app that works well. It can be about things like how easy to understand is your signage and way-finding in your elevators or corridors.</blockquote><p><em>Pro Tip: Take a photo with your phone of your room number as soon as you check-in.</em></p><h3>4. Your room — one size fits all</h3><p>Most of the hotels don’t have any type of room personalization.</p><p>All blankets are tucked in, which for a 190cm tall individual (like myself), is annoying. The first things I do when I enter a hotel room, I untuck my blankets and get rid of all the pillows. Every single time. <a href="https://www.youtube.com/watch?v=bl3HcIXvIo0">George &amp; Lupe would understand.</a></p><p>And 8 pillows on my bed is excessive. Usually, I don’t sleep with an entire football team in my room.</p><p>If you want to use data somehow, do it for personalization and to enhance the experience — but be transparent about it, give me the choice, don’t opt me in by default — not for sending me shitty spam.</p><h3>5. Connecting to Wi-Fi</h3><p>Sometimes I use hotels close to airports as I need to go in an out as quickly as possible. As these are usually in the middle of nowhere, it happened multiple times not to have network coverage on my phone. That’s no calls, no texts, no emails, nothing. That’s when free wi-fi is <strong>not</strong> included and they charge like 15 pounds for 24 hours of slow wi-fi, because they know you’re out of options. Now, connecting to wi-fi is an entirely different story with all the landing pages and infinite forms. Let’s gather even more data which we have no clue how to use.</p><h3>Some do get it.</h3><p>I did have good experiences in a few hotels though. I remember <a href="https://www.theverbhotel.com/">one particular hotel in Boston</a> where at reception they have a big collection of vinyls you can choose from and bring up to your room which is equipped with a record player and Marshall speakers. Apart from the cool vibe, it seems like they pay attention to details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nAyMrvOurQBrs1TnyAg9oA.jpeg" /><figcaption>Reception @ The Verb Hotel in Boston, sep 2017.</figcaption></figure><p>Your keycard is placed in backstage-pass-like necklace that you can put around your neck and have it with you (room number is placed there as well, so you don’t have to memorise it!).</p><h3>Conclusion</h3><blockquote>The disjointed Customer Journey in the hotel industry — similar to other complex industries like health, transportation, etc. where the user is taken through multiple touch-points both digital and analog — is symptomatic of different departments being in charge of different things with little or no communication between them.</blockquote><h3>What to do</h3><ol><li>Involve a cross-department team in your design process.</li><li>Analyse the customer journey —Think from a system design perspective, identify the steps in the journey and understand where the customer is being underserved, where the pain-points and frustrations arise.</li><li>Understand your customers (develop personas) — try to map their goals behaviours and motivations.</li><li>Ideate — it’s very unlikely that a unique solution will fix all your problems, so be generative. Try to resist thinking exclusively digital, sometimes simple analog solutions solve problems well.</li><li>Prioritise — map ideas on an opportunity map and look at dimensions like business value, user value or technical feasibility to understand which are the quick wins, which are strategic initiatives and what should be de-prioritised.</li><li>Prototype &amp; Test — find the appropriate form of prototyping depending on what the solution is. If the solution takes the user through multiple touch points, a storyboard or a prototyping environment work better, while for an app or a digital solution an InVision prototype is more appropriate.</li></ol><p><em>*This isn’t meant to be in any way an exhaustive customer journey mapping exercise. I’m just highlighting some of the main pain points experienced from a single point of view. Also, my experience with hotels starts usually at check-in so this piece doesn’t cover any steps in the customer journey (like awareness or consideration) prior to check-in.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab79f45f05ec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nyc-design/the-broken-customer-experience-of-the-hotel-type-accommodation-ab79f45f05ec">The Broken Customer Experience of the Hotel Type Accommodation</a> was originally published in <a href="https://medium.com/nyc-design">NYC Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Maximise Learning Through Rapid Prototyping]]></title>
            <link>https://medium.com/@departive/how-to-maximise-learning-through-rapid-prototyping-848b89d11975?source=rss-e1a07ecb4b46------2</link>
            <guid isPermaLink="false">https://medium.com/p/848b89d11975</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[discovery]]></category>
            <dc:creator><![CDATA[David Cristian]]></dc:creator>
            <pubDate>Mon, 01 Feb 2016 11:54:43 GMT</pubDate>
            <atom:updated>2016-02-19T10:17:36.024Z</atom:updated>
            <content:encoded><![CDATA[<p>One of my latest projects I’ve led at DMI started off with some fuzzy requirements, no clear problem statement and ambiguous concept (which in reality was no concept at all). In addition to that, we were swimming in an overcrowded space with huge competitors. Prototyping played an essential role in our process of discovery and conceptualisation. Through rapid prototyping and rigorous user research, we were able to clearly articulate the problem we wanted to solve and also experiment the solution space by switching from a “let’s build it” to a “let’s test it” approach. Instead of requirements we started with assumptions. After 9 weeks we ended up with a clear problem statement, solid concept and an interactive prototype which helped the client raise a big investment. Here are some things I learnt along the way.</p><h3>Why should you prototype?</h3><h4><strong>1. Prototyping is a cheap and efficient way to deal with things that are hard to predict.</strong></h4><p>One of the most famous stories about prototyping is the one with Jeff Hawkins, who was a Palm co-founder and one of the inventors of the Palm Pilot. Before committing to develop the Pilot, he cut a block of wood that would fit into his pocket and “use” it for several weeks pretending it was a real computer. The story says that every time someone was asking him about his availability he would “check” his schedule on his block of wood. It might sound stupid, but this allowed him to understand better how the experience might be like and all the potential challenges that might arise.</p><h4>2. Prototypes help externalise ideas</h4><p>Prototypes can do a very good job to externalise ideas to stakeholders and facilitate user evaluation or usability tests.</p><blockquote>“A lot of times, people don’t know what they want until you show it to them” — Steve Jobs</blockquote><p>I was around London Eye a couple of months ago, asking people to test my prototypes. Loading InVision prototypes using 4G proved to take more time than expected, due to the terrible connection. In many cases I had to fill this loading time with some conversation explaining what this app is about. “Explaining” the app using just words had almost no effect on people (I could tell that by the body language) but after the prototype was loaded, the whole perspective of the user was changed. I often got reactions like “wow… this is pretty cool, actually!”. That’s when I realised the Steve Jobs quote is more valid than ever.</p><h4>3. Prototypes replace documentation and deliverables</h4><p>Most of us learned the hard way how complicated it is to work following the old deliverables/documentation based model. Iterating is a pain as you have to update wireframes and flowcharts, explain interactions by showing static presentations containing non-interactive wireframes, information architecture, content maps and mock-ups. A prototype eventually encapsulates all of that. The documentation is the prototype itself. IA is there, wireframe flow-charts are not needed since the flows are in the prototype.</p><h4>4. <strong>Prototypes maximise the amount of learning and minimise the amount of time spent going into the wrong direction</strong></h4><p>By rapidly prototyping and testing you’ll discover early what is working and what isn’t, in order to minimise risk. You’ll be able to reduce as much as possible the risk of working on things that are not going to be successful. Try to get the prototypes quickly in front of the users. Kill them if you have to (the prototypes, not the users!). Iterate, then repeat.</p><h3><strong>How should you prototype?</strong></h3><h4>1. Prototypes are questions. Ask many.</h4><p>Many raw ideas are necessary for innovation and in order to externalise these ideas and show something tangible to stakeholders you’ll need to prototype a lot. Start with low fidelity prototypes that express the core concepts of the ideas you’re trying to communicate. Make one prototype for each and generate as many as you can.</p><blockquote>“The best way to have a good idea is to have lots of ideas” — <a href="https://en.wikipedia.org/wiki/Linus_Pauling">Linus Pauling</a> (Nobel Prize Winner)</blockquote><p>Designers often get fixated on one idea and this can lead to missing other good opportunities. Starting off with many ideas not only reduces the chance of missing good opportunities but also helps the designer avoid fixation. When you have only one idea you’re more likely to be attached to it than when you have many.</p><h4>2. Build quickly</h4><p>Your goal at this point should be to maximise the amount of learning and minimise the time spent going into the wrong direction. Prototypes shouldn’t be complete, they develop over time, so don’t spend time on visuals, beautiful mockups or trying to finish all the sections in the app. Push non-relevant sections (like settings) as late as possible in the project and spend the time on getting the concept right. You don’t even have to think too much about usability, you can worry about that later. <strong>Usability testing can tell you if an interface is usable but cannot tell you if it’s useful.</strong></p><p>Right now your goal is to start a conversation and answer some questions, such as “Is this useful? Why/Why not?”, “Is this something desirable? Why/Why not?”, “How does it compare with the other alternatives?”. Answering these questions will make it easier to filter out the bad ideas or things that won’t work.</p><p>Prototypes are ways to start a conversation and not options for the user to choose from.<strong> </strong>I avoid showing multiple options to the same user for several reasons. I don’t want to limit the conversation to the options shown so the user feels like he needs to choose something. Second, a user can be under the impression that he likes one option just due to the fact that he saw that one first. When doing interviews, by laddering and asking a lot of “whys” you can uncover core problems. After you have answers to the questions above you’ll be able to throw to the trash the bad ideas and start another round of prototyping. You can combine prototypes, duplicate and create multi-variants which you can test again. Sketch, prototype, research, critique, test. Do this cyclically and you’ll increase your chances of building something solid, something that solves a real problem.</p><p>The essence of innovation is based on hypothesis and experimentation. Designing software is a continuous task and differs a lot from assembling a chair, for example. When we design software we often don’t know how the product it’s going to look like and we need to learn as we move forward. That’s where prototyping plays a crucial role. It’s a mechanism that helps you to move from ambiguity to certainty and to learn quickly what works and what doesn’t in order to reduce risk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=848b89d11975" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>