<?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 UX Life on Medium]]></title>
        <description><![CDATA[Stories by UX Life on Medium]]></description>
        <link>https://medium.com/@jonnyux?source=rss-c6943e833a8a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kRdoWgweVMrW0_eEjppL3Q.png</url>
            <title>Stories by UX Life on Medium</title>
            <link>https://medium.com/@jonnyux?source=rss-c6943e833a8a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 19:01:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jonnyux/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 Homegrown: the conference down under]]></title>
            <link>https://medium.com/@jonnyux/ux-homegrown-the-conference-down-under-291355164369?source=rss-c6943e833a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/291355164369</guid>
            <category><![CDATA[uxhg]]></category>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-homegrown]]></category>
            <dc:creator><![CDATA[UX Life]]></dc:creator>
            <pubDate>Wed, 11 Apr 2018 01:25:09 GMT</pubDate>
            <atom:updated>2018-04-11T01:31:32.198Z</atom:updated>
            <content:encoded><![CDATA[<p>UX Homegrown (UXHG) is a boutique UX conference for local NZ stories, knowledge sharing and growing the UX community down under. In this post I’m going to discuss how I got involved and why you should go this year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*TlK7DXFlyw5pSIBbiF0CKg.png" /></figure><p>From their website:</p><blockquote>“UX Homegrown is built on the stories of real UX practitioners, from our foremost experts to our front line workers sharing how they make UX work in the New Zealand context. Hear about their triumphs and failures and how they do the work to create world class user experiences in New Zealand.”</blockquote><p><strong>Content is key</strong></p><p>Back in 2017 I spoke with my team (<a href="https://medium.com/u/e685a2c81b1a">Ross Tulloch UX</a>, Anna Bek) and we agreed that it would be a great idea to share our story and learnings from being in a “corporate innovation lab”. I put together a submission description, pressed the big red button and the rest was history.</p><p>I had a feeling we had good content, and potentially a great story to tell. This is where UXHG fits in — the talks are curated/voted for based on content, without revealing the presenter or their background. For the audience, it means you get great stories, told by “fresh” presenters. It’s emotional. It’s a great way to curate the lineup and you’ll be inspired to share your story. Naturally, the lineup of speakers will include some UX heavyweights with global chops (such as <a href="https://www.mrtappy.com/">Mr Tappy’s</a> creator, <a href="https://medium.com/u/bdc711666f1d">Nick Bowmast</a>) so you’ll get exceptional value too.</p><p><strong>From a speaker’s point of view</strong></p><p>Rather than review the conference itself (you should check out <a href="https://www.linkedin.com/pulse/ux-homegrown-highlights-insights-lee-young">Lee Young’s post</a>), I’ll share my thoughts about my time as a speaker. A review from the inside, if you will.</p><p>After submission, a month or so passed by and I assumed my talk wasn’t picked. Great — no need to prepare, more time in the garden and less stress. Emma from UXHG got in contact via LinkedIn, her previous emails had been “marked as spam” and I was late to the party. I was very excited to have been picked. But now I had less time to prepare (I love being prepared) and increased stress with the looming deadline. I spent two weeks preparing the content and drafting the first set of slides. I was concerned that my story wasn’t fluid and I still hadn’t practiced verbalising the talk yet.</p><p><em>I was still a virgin conference speaker.</em></p><p>My past mentors had always said conference speaking was a good thing — for the career, skill building and giving back to the UX and tech community. They were right.</p><p>There were some really great features of UXHG. Firstly, we had organised speaker training with a professional coach (over two weekends). Emma provided moral support, tips and constructive feedback during our rehearsal sessions. It was great to network with the small but growing UX community in Auckland — I finally met some of the familiar faces that I’ve seen floating about on social channels.</p><p><strong>After the talk</strong></p><p><em>One of the best parts of the conference happened afterwards — customer feedback.</em></p><p>After my talk I had attendees approach me and share their thoughts. “Customer feedback” — who would have thought? I met other seasoned designers, aspiring designers and non-UX folk that could relate to my talk in one way or another and I still keep in contact with them today.</p><p><strong>So, where’s the video?</strong></p><p>My video will be on YouTube shortly. It’s a 10 minute talk plus some curly questions that I answered without really answering. Ops.</p><p>If you know me personally, I don’t care much for chitter chatter and I’m definitely an out-of-the-closet introvert. Yes, I don’t like people. Kidding. I just enjoy solitude now and again. So this was definitely a new challenge for me. I’d like to thank Nano girl for her insights and I found this video really helpful — “<a href="https://www.youtube.com/watch?v=uKtMwmWv6Q0">How to rock the stage — public speaking and presentation skills you can master</a>”.</p><p>So check out <a href="http://www.uxhomegrown.co.nz/">www.uxhomegrown.co.nz</a> to see the lineup for 2018 and to submit your talk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=291355164369" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The power of prototyping]]></title>
            <link>https://medium.com/@jonnyux/the-power-of-prototyping-9832ecaf48d9?source=rss-c6943e833a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9832ecaf48d9</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[industrial-design]]></category>
            <dc:creator><![CDATA[UX Life]]></dc:creator>
            <pubDate>Mon, 29 Jan 2018 22:52:07 GMT</pubDate>
            <atom:updated>2018-01-29T22:55:03.454Z</atom:updated>
            <content:encoded><![CDATA[<p>Prototyping is one of the UX outputs I often recommend as part of my UX artillery. I’ll share a few thoughts from my prototyping work in 2017.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*avQb9sjdPaePaunvIDMmTQ.gif" /><figcaption>Prototyping example: customising the orientation angle for a mechanical component</figcaption></figure><p>For me, 2017 was a great year to follow my UX gut. I started my own independent consultancy, following my my own rules and values to give customers a premium level of service. Realistic prototyping is one of the services I provide to give customers extra value. In a couple of projects I had the liberty of doing hi-fidelity (all “singing and dancing”) prototypes and ditching the typical UX artefacts - wireframes and “flat” page designs, etc.</p><p>Prototyping, is truly a powerful technique (commonly used in other design disciplines such as automotive, engineering and industrial design) that is often overlooked in UX/digital projects due to time, cost or a lack of skill.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7cdhNaZuFzotDhq4RgRYDQ.png" /><figcaption>Car prototype made from clay: <a href="https://www.pinterest.nz/pin/561050066052984054/">https://www.pinterest.nz/pin/561050066052984054/</a></figcaption></figure><p>I often prototyping in code (Javascript, HTML, CSS), as it’s very flexible and realistic. If you have experience with these languages, then I recommend you use them to your advantage — don’t let anyone tell you otherwise.</p><p><strong>Note: you must treat the code as “throw away” — else you’ll focus your energy on the wrong thing (designing code over product design).</strong></p><p>Quite often, coding isn’t for everyone. Luckily, there are a plethora of great tools that can bring your designs to life. Check out <a href="https://medium.com/u/698d3446046">Atomic</a> (made in NZ!) and some of the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bMmj-keUVAZpaDlkdKwjJg.png" /><figcaption>Source: <a href="https://blog.prototypr.io/14-prototyping-tools-how-each-can-be-used-1c804fab33a6">https://blog.prototypr.io/14-prototyping-tools-how-each-can-be-used-1c804fab33a6</a></figcaption></figure><p><strong>Here are some of the benefits of prototyping:</strong></p><ol><li>The prototype becomes the complete design — including structural, visual/content and interaction elements</li><li>Clients/stakeholders will understand the design quicker and ask better and more useful questions</li><li>You will have a tangible “thing” that is easily testable with its own URL</li><li>Feedback from prototype testing will be more reliable (as it’s more believable in the eyes of users)</li><li>Clients will quickly become comfortable talking through the design (to their peers) and will be able to run their own testing sessions (due to points 2 &amp; 3)</li><li>Iteration and design changes of the prototype usually become quicker once a base prototype has been established</li><li>The prototype can be used as (or to derive) documentation by project teams to start development</li><li>As a designer you will uncover exceptions, edge cases and navigational issues by doing and experiencing the interaction design</li><li>As a designer you will become knowledgeable in technical limitations and better at determining feasibility of design concepts</li></ol><p><strong>Of course, there are some factors that work against prototyping:</strong></p><ol><li>The client may have trouble updating the prototype (they would need to know the specific tool or coding languages)</li><li>The time to build a prototype is usually longer than creating visual designs</li><li>You still need to do adequate groundwork (and maybe more) before going into prototype design/build</li><li>A prototype may not be necessary in simpler cases</li></ol><p>If you would like me to elaborate on any of the above ideas, please let me know and I can write it up in another post. Thanks — good night :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9832ecaf48d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Startup weekend — 54 hours of crazy]]></title>
            <link>https://medium.com/@jonnyux/startup-weekend-54-hours-of-crazy-f1309acac4a6?source=rss-c6943e833a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1309acac4a6</guid>
            <category><![CDATA[startup-weekend]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[tgasw]]></category>
            <dc:creator><![CDATA[UX Life]]></dc:creator>
            <pubDate>Wed, 30 Aug 2017 09:25:17 GMT</pubDate>
            <atom:updated>2017-08-30T09:25:43.670Z</atom:updated>
            <content:encoded><![CDATA[<p>This month I had the pleasure of taking part as a mentor, at Tauranga Startup Weekend 2017 (TGASW). One of the highlights for me was meeting a range of great people, such as <a href="https://medium.com/u/1ed3b15276f0">Lisa Wong</a> (one of the mentors who did a fantastic <a href="https://medium.com/@lisawongravlich/10-lessons-from-a-startup-weekend-from-idea-to-business-pitch-in-54-hours-704be99d3bd2">summary</a> of the event), Jo and Pascale (the organisers at <a href="http://venturecentre.co.nz/">Venture Centre</a>) and all the participants who turned out to this great bay event (which was part of Tauranga’s Innovation festival — <a href="http://www.gswell.co.nz/">Groundswell</a>).</p><p>In business, your network is extremely valuable especially when starting out in a new place or venture. In little NZ, where people are often at the beach eating ice-cream or “fish and chups”, a friendly, word-of-mouth referral from someone in your network is worth it’s weight in gold. I encourage you to build your network, if not for now, for the near and uncertain future.</p><h3>Startup culture</h3><p>Naturally when I think about startups, it’s about cool tech, building stuff and good times… and hopefully some paying customers at the end of it all.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F69V__a49xtw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D69V__a49xtw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F69V__a49xtw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c4a4303dabdf6ce877171583d46a3d7f/href">https://medium.com/media/c4a4303dabdf6ce877171583d46a3d7f/href</a></iframe><p>But Startup Weekend focusses on the business end of things — the important stuff before you get designing and building.</p><p>I saw a few technologists bemused by this reality, as they were keen to tool up and build some crazy shit. This is where the learning comes in, at Startup Weekend. Designers and technology enthusiasts need to understand business concepts to have the best chance of success in their future ventures. Designing something “pretty”, or building something with 100% uptime is no good to anyone, if there are no paying customers.</p><blockquote>Startup weekend prepares people to become better entrepreneurs.</blockquote><h3>Got an idea? Isn’t that cute</h3><p>No doubt, you’ve had an idea for a product or service. But before you go out and pursue it, Startup Weekend guides you along a proven path of questioning…</p><ul><li>Have you validated the problem with real people (your target market)?</li><li>Do you have a business model (how will you make money or make a social difference?)</li><li>What is the product or service you will offer (is it an app, a physical product or an experience?)</li><li>Can you talk through your idea (does it make sense to people?)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*ld8R2VmWXOMen7D8kXxJBA.jpeg" /><figcaption>This advert delivers a good point — ideas are nothing on their own</figcaption></figure><h3>Don’t forget to fuel up</h3><p>Participants (and mentors) get fed for 2 days. For a minimal entry fee, there is nothing nothing to loose, but everything to gain (BTW the food was great — Thai curry, pulled pork and amazing bagels). One of the big draw cards for participants is the volunteer mentor group, who provide guidance and advice from their fields of expertise (business, design/UX, tech, people wrangling etc). As a mentor, it was great chance to give back to the community and be part of the intense madness. If you’re keen to sign up next years event, I can connect you with the right people.</p><h3>Jonny UX on Twitter</h3><p>Basestation breakfast to fuel the teams! Final day #spicy @tgasw #tgasw</p><p>Thanks for all who took part in the 54 hours of crazy. I hope everyone has since recovered :) Here’s a summary video of the event!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQa0ne9juHI8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQa0ne9juHI8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQa0ne9juHI8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b51f15f0a2939fcef4239d5561d185d7/href">https://medium.com/media/b51f15f0a2939fcef4239d5561d185d7/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1309acac4a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX as a philosophy, not a discipline]]></title>
            <link>https://medium.com/@jonnyux/ux-as-a-philosophy-not-a-discipline-68ec48d9f88a?source=rss-c6943e833a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/68ec48d9f88a</guid>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-designer]]></category>
            <dc:creator><![CDATA[UX Life]]></dc:creator>
            <pubDate>Mon, 05 Jun 2017 10:45:48 GMT</pubDate>
            <atom:updated>2017-06-05T10:45:48.496Z</atom:updated>
            <content:encoded><![CDATA[<p>I once explained to a young CEO that UX is a mindset and a way of thinking, rather than a job title or discilpline. I look back and wonder if this is valid, given the rise of job openings and growing demand for UX professionals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*11bWQGlm7pdN_CGOtwelXQ.jpeg" /></figure><p><strong>So how can you achieve the best UX in your organisation?</strong></p><p>Can you simply hire the best UX designers? In my experience, you can have great UX teams or dedicated people doing “UX” work, but if they are siloed and not given top-level support, they will ultimately fail. The closest parellel is development teams — you can hire the best engineers, but if they are poorly managed and only seen as code producers, you’ll get poor results.</p><p>Good project teams are run by Product Owners who understand both business and technology. Excellent project teams are run by Product Owners who also understand UX. By understanding the constraints of technology and the benefits of customer satisfaction, Product Owners can prioritise based on facts and deliver the most value to the business.</p><p><strong>So, do I need to hire UX designers then?</strong></p><p>Yes, yes and yes. But only if you trust them to do good work. Don’t expect them to colour in buttons and do powerpoint decks for you (if they are happy doing this, then you have hired an imposter or a junior). They need to be given bandwidth to solve business problems, to work on strategy and to shape the culture of your organisation.</p><p><strong>So, what’s your point?</strong></p><p>As people get more acustomed to the UX way of thinking, the role of the UX designer will change in the next 5+ years. But for the time being, if you can pair a good UX designer with a Product Owner who understands UX, then you have a great chance of acheiving success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68ec48d9f88a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple email forwarding with AWS]]></title>
            <link>https://medium.com/@jonnyux/simple-email-forwarding-with-aws-f88b9ffdb60a?source=rss-c6943e833a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f88b9ffdb60a</guid>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[e]]></category>
            <category><![CDATA[domain-names]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[email-forwarding]]></category>
            <dc:creator><![CDATA[UX Life]]></dc:creator>
            <pubDate>Sun, 28 May 2017 08:46:15 GMT</pubDate>
            <atom:updated>2017-05-28T08:46:15.572Z</atom:updated>
            <content:encoded><![CDATA[<p>Did I say simple? Ok, it’s taken a lot longer than anticipated, but after some serious troubleshooting at odd hours of the night, my domain email address now works with Amazon Web Services (AWS).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*8UeN_CkFgH6yLHpCK0-M4Q.jpeg" /><figcaption>Source: <a href="https://www.r-bloggers.com/april-fools-day-the-7-funniest-data-cartoons/">https://www.r-bloggers.com/april-fools-day-the-7-funniest-data-cartoons/</a></figcaption></figure><p><strong>Why use AWS?</strong></p><p>With all the buzz around AWS, the cloud and scalable computing, I was eager to give it a try. Amazon offer <a href="https://aws.amazon.com/free/">free web hosting</a> for 12 months —so nothing to loose (and of course after a year I’ll be too lazy to switch, they’ve got me already). The two components that handle hosting and domain registration are Amazon’s <a href="https://aws.amazon.com/s3/">Simple Storage Service (S3)</a> and <a href="https://aws.amazon.com/route53/">Route 53</a>. It’s really nice to have all that web stuff in one place.</p><blockquote>AWS is a convenient one stop shop. It’s the Tesco of the web.</blockquote><p><strong>Introducing Amazon’s Simple Email Service — SES</strong></p><p>But what about receiving emails sent to my domain? Amazon now offer their simple email service (SES). But either someone forgot, no one spoke to any users or the developers just hacked it together — but out of the box you can’t get emails from your domain forwarded to your inbox of choice (i.e. Gmail). Perhaps it’s a bit too simple?</p><p>Luckily, Joe Turgeon has written a function to do this; you’ll need to configure it in <a href="https://aws.amazon.com/lambda/details/">AWS Lambda</a>, their serverless compute service. It’s quite involved for the non-geek — you’ll need to:</p><ol><li>Create an S3 bucket to store your emails</li><li>Copy some code to Lambda to handle the forwarding</li><li>Set up a role in <a href="https://aws.amazon.com/documentation/iam/">AWS Identity and Access Management</a> (IAM) to allow the code to access the bucket</li><li>Configure a forwarding rule in SES so it all magically works</li></ol><p>Joe’s readme is on GitHub, it’s well documented with precise steps:</p><p><a href="https://github.com/arithmetric/aws-lambda-ses-forwarder">GitHub - arithmetric/aws-lambda-ses-forwarder: Serverless email forwarding using AWS Lambda and SES</a></p><p><strong>Troubleshooting</strong></p><p>Unfortunately, the process didn’t go super smooth for me. I got a couple of errors:</p><p><strong>“AccessDenied: Access Denied”</strong> — a permission issue. I fixed this by making the Resource field in the Role policy less strict:</p><pre>&quot;Resource&quot;: &quot;arn:aws:s3:::BUCKET_NAME/*&quot; </pre><pre>// becomes...</pre><pre>&quot;Resource&quot;: &quot;arn:aws:s3:::*&quot;</pre><p><strong>“NoSuchKey: The specified key does not exist”</strong> — again an access issue. I fixed this by removing the object key prefix (emails/) in the SES forwarding rule, so any received emails would sit in the top level of the bucket.</p><p>Hopefully you can get it all working fine without too much stress. I’ve gathered the few articles that also explain how to set it up, with slightly different instructions (they helped me get to grips with the whole setup). Enjoy.</p><ul><li><a href="https://jeremyfelt.com/2016/05/22/send-receive-email-domain-postmark-amazons-ses-s3-lambda-services/">Send and receive email for your domain with Postmark and Amazon&#39;s SES, S3, and Lambda services</a></li><li><a href="https://bravokeyl.com/how-to-set-up-email-forwarding-with-amazon-ses/">How to set up email forwarding with Amazon SES | Bravokeyl</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f88b9ffdb60a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hiring UX v.s. UI]]></title>
            <link>https://medium.com/@jonnyux/hiring-ux-v-s-ui-b178c43fe3d5?source=rss-c6943e833a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b178c43fe3d5</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[hiring-for-startup]]></category>
            <dc:creator><![CDATA[UX Life]]></dc:creator>
            <pubDate>Thu, 18 May 2017 08:37:17 GMT</pubDate>
            <atom:updated>2017-05-18T08:37:17.094Z</atom:updated>
            <content:encoded><![CDATA[<p>My first task at Yellow NZ was to build UX capability within the company — to reduce the reliance on agencies and freelancers. Everyone has different approaches for hiring, but I was certain I could build a great team based on my experiences of “what good looks like” (I’ve worked within large teams as well as being the“UX team of 1”). I was keen to get the mix right — to have a range of skills by getting different <a href="http://www.uxforthemasses.com/what-makes-good-ux-designer/">T-shaped</a> people. Let me share a couple of techniques I used to sift out UX and UI people.</p><p>The recent barrage of UX/UI designers has caused murkiness in the market, it’s very confused (you can tell when a recruiter thinks its cute to have lots sticky notes in your portfolio or they ask you how good is your “IA”). Is the UX/UI designer a true UX person, a visual designer or a generalist blend of both? The first task I would give to candidates was a pre-interview test, to choose between the following:</p><ol><li>Redesign the Yellow App — choose 2–3 key screens of your choice</li><li>Review the Yellow App — let me know what works, what doesn’t</li></ol><p>Even before agreeing to an interview, I could see what type of designer they were, solely based on their choice. Awesome.</p><p>Once the candidates were invited to meet in person, it was a pretty standard interview —company background, portfolio, questions. I did employ one special technique, which was getting the participant to complete a card sort of UX methods. The task itself was a UX talking point, plus I could get a strong grasp for their experience, based on how they grouped the cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ciG58qK3jJk6G4bS0ZMzgw.jpeg" /><figcaption>UX methods from <a href="https://uxdesign.cc/ux-design-methods-deliverables-657f54ce3c7d">uxdesign.cc</a></figcaption></figure><p>After a handful of CVs and a few formal interviews, I was able to make good hires. Surprisingly, this was the easy part. We had to get to work fast, so onto forming, storming, norming and performing. The rest is history.</p><p>I would like to acknowledge two great articles that helped shape my interview process. Please read them if you haven’t already.</p><ul><li><a href="https://blog.intercom.com/how-to-hire-designers/">How to hire designers - Inside Intercom</a></li><li><a href="http://firstround.com/review/An-Inside-Look-at-Facebooks-Method-for-Hiring-Designers/">An Inside Look at Facebook&#39;s Method for Hiring Designers</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b178c43fe3d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[People over Pavlova (process)]]></title>
            <link>https://medium.com/@jonnyux/people-over-pavlova-process-9bff341a484c?source=rss-c6943e833a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bff341a484c</guid>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[UX Life]]></dc:creator>
            <pubDate>Sat, 13 May 2017 07:47:05 GMT</pubDate>
            <atom:updated>2017-05-13T07:48:45.809Z</atom:updated>
            <content:encoded><![CDATA[<p>I once worked with a UX Designer who was mad about Agile. Alas, her previous employer was <a href="https://www.thoughtworks.com/about-us">ThoughtWorks</a>, where Agile was loosely conceived. Often she would recite the manifesto — it was always on tap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XWeHZ-n6jZx3pMazOzfTew.png" /><figcaption><a href="http://www.mydayinfood.com/pavlova/">Penny’s Pavlova recipe</a></figcaption></figure><p>The <a href="http://agilemanifesto.org/">Agile manifesto</a> states the following guiding principles of Agile teams, in that we value:</p><blockquote><strong>Individuals and interactions</strong> over processes and tools<br><strong>Working software</strong> over comprehensive documentation<br><strong>Customer collaboration</strong> over contract negotiation<br> <strong>Responding to change</strong> over following a plan</blockquote><p>She would often drop the saying “<strong>people over process</strong>”. This concept rings true to me time and time again. Good people, are your biggest asset. Let me highlight the truths with some real examples:</p><p>Wanda, a senior product person approaches me:</p><blockquote>Hey Jonny — can you come up with a process and share it with my team? They’ve got different personalities and they fight a bit over your resource. I think this will help manage them better?</blockquote><p>John, a senior graphic designer person approaches me:</p><blockquote>Hey Jonny — what’s your process for managing the traffic? How do you manage those different pieces of work coming in? What ticketing system do you use?</blockquote><p>In the first scenario with Wanda, it’s pretty much the case of “process over people”. If her people were disciplined, stopped changing their priorities and understood how UX Designers can do more than Photoshop (you mean Sketch, anyway) then such a process isn’t required. If you need to educate people on how to behave at work — are they doing their job right in the first instance?</p><p>In the second scenario with John, it’s clear to me that there are different processes for different types of work. Designing logos, banners and email templates is a different paradigm compared to designing digital products. My own process would involve a bit of project management, tracked and shared on a Trello board. I would assign UX Designers to the most important projects and they would self-manage their duties for each project. Give people responsibility and remit and there becomes very little process required. Of course, you need senior people who can manage their time and understand how everything fits together, else you need to hit them with process. So hire good people.</p><p><strong>Forget the </strong><a href="http://www.urbandictionary.com/define.php?term=Palava"><strong>palava</strong></a><strong>, it’s about people.</strong></p><p>(If you’re interested in the history of Pavlova, see <a href="https://en.wikipedia.org/wiki/Pavlova_(food)">wikipedia</a>.)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bff341a484c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t dismiss the CEO, you may work for her one day]]></title>
            <link>https://medium.com/@jonnyux/dont-dismiss-the-ceo-you-may-work-for-him-one-day-4091f29cbe37?source=rss-c6943e833a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4091f29cbe37</guid>
            <category><![CDATA[ceo-skills]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ceo]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <dc:creator><![CDATA[UX Life]]></dc:creator>
            <pubDate>Wed, 10 May 2017 12:51:21 GMT</pubDate>
            <atom:updated>2017-06-05T10:53:11.089Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first started my career as a developer, I was very fortunate to have many morning chats with the CEO. She had been informed about my design prowess and highjacked me onto a design project before I got to write a single line of code. Little did I understand at the time, being fresh faced out of uni, this person was extremely powerful, with strong credentials, who built the company of 300 people from scratch.</p><blockquote>All I kept thinking, was, how annoying it is that she keeps drawing on my (CRT) monitor with a yellow highlighter! Can I now just go back to what my job title says and write some (boring) Java code?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PaASf58vfmF_mxpDw9hwDA.png" /></figure><p>Ten years later, as Head of UX for a different company, through an interesting series of events I get to report directly to the CEO. Now I’m thinking woohoo! I’ll have so much more head cover and clout; I can put “reporting to CEO on my linked-in”, forget C-level execs!</p><p>If I had known what I knew back then, I may have approached things differently. In the early days, <strong>being nobody to the CEO</strong> meant: low responsibility, high chance of uptake. <strong>Reporting to CEO</strong>: high responsibility, low chance of uptake. This is purely empirical, but on other occasions when I’ve managed to get a prototype in the hands of a CEO (even as a external consultant) they were far more receptive than when I was a direct report. In a conversation with a bright startup CEO, she also shuddered at the notion of innovation being directly controlled by the top — it went against everything she had come across.</p><p>This is probably a big fat disclaimer in this — it depends on the type of CEO. The two that I speak about here are quite different and if they were swapped in my longitudinal study, would the results differ? Happy for more input. Night.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4091f29cbe37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Just let me write dammit!]]></title>
            <link>https://medium.com/@jonnyux/just-let-me-write-dammit-7dc61bdc32e8?source=rss-c6943e833a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7dc61bdc32e8</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[blogging]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[UX Life]]></dc:creator>
            <pubDate>Wed, 10 May 2017 11:33:53 GMT</pubDate>
            <atom:updated>2017-05-10T11:33:53.976Z</atom:updated>
            <content:encoded><![CDATA[<p>Since 6th form English class (year 11 in NZ), when I smashed all competition in creative writing and toped the final exam, I’ve had an innate passion for writing. That was in 1997. But I’ve never had the time or topics to blog about… well I did had that beloved travel blog (my persona was a wannabe DJ groupie travelling Europe, go figure!), which was more of a safety blanket for me whilst away from home and I can write a mean Agile user story when the CTO asks me to. Anyway, I digress — excuses, excuses!</p><p>Finally, after 10+ years working in tech I finally have something unique to talk about — my <strong>work experiences</strong> <strong>in (typically) large corporations</strong> and my <strong>evolution from “programmer” to “designer”</strong>. Yes, I want to write lovely tales about funny bosses, inappropriate HR-related behaviours in the workplace, general bad practice and unearth the truths of the 9–5 corporate. But does this really help you, the reader?</p><blockquote>And that is what User Experience is all about.</blockquote><p>What would the user find insightful to read, rather than what I want to tell them? Of course, I could still write for myself, but the target audience would be limited to people that I know personally and of course myself. I’ve done this before, i.e. the travel blog. I do want to reach a wider audience — so please tell me if I go off piste.</p><p>So, better than just sharing experiences, I want to lead with tips and solutions to problems, backed my with real-world experiences and examples. Turning my blog’s content strategy upside-down, I can hopefully help you the reader, while still enjoying off-the cuff writing when I get a moment away from the garden and of course the baby.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7dc61bdc32e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kia ora]]></title>
            <link>https://medium.com/@jonnyux/kia-ora-309a4ca5df23?source=rss-c6943e833a8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/309a4ca5df23</guid>
            <dc:creator><![CDATA[UX Life]]></dc:creator>
            <pubDate>Sat, 25 Mar 2017 23:07:35 GMT</pubDate>
            <atom:updated>2017-03-25T23:07:35.529Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m about to embark on a new chapter in my life, where I set the rules. “Working to live” will take a back seat. Work will fit around family, our needs, goals and our time. This is <strong>UX Life</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=309a4ca5df23" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>