<?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[Promoting UX Practices — a journey - Medium]]></title>
        <description><![CDATA[Jamieson is an aspiring UX Designer, working in an organisation rife with traditional development approaches. Follow his journey as he challenges existing process and champions a focus on User Experience Design. - Medium]]></description>
        <link>https://medium.com/promoting-ux-practices-a-journey?source=rss----34cc42c6843c---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Promoting UX Practices — a journey - Medium</title>
            <link>https://medium.com/promoting-ux-practices-a-journey?source=rss----34cc42c6843c---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:41:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/promoting-ux-practices-a-journey" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Being the expert, when you know nothing]]></title>
            <link>https://medium.com/promoting-ux-practices-a-journey/being-the-expert-when-you-know-nothing-54d6a349fcf3?source=rss----34cc42c6843c---4</link>
            <guid isPermaLink="false">https://medium.com/p/54d6a349fcf3</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jamieson]]></dc:creator>
            <pubDate>Mon, 09 Nov 2015 11:16:47 GMT</pubDate>
            <atom:updated>2015-10-23T04:24:20.472Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve been following along my UX journey, you’ll know that I recently managed to <a href="https://medium.com/promoting-ux-practices-a-journey/the-challenge-and-the-opportunity-5db13ff8719">carve out a unique opportunity</a> and liked what I saw when I figured out <a href="https://medium.com/promoting-ux-practices-a-journey/the-lay-of-the-land-aac21752f34d">the lay of the land</a>.</p><p>I’m now halfway through my placement focusing on UX Design, and the effect of constant on-the-job experience is apparent. I’ve spent countless hours refactoring and tweaking the design of one of the our externally-facing web apps using HTML/CSS/Javascript, and have learned first-hand the pitfalls of designing directly in code. Attempting to move this practice out of the realm of code has proved equally challenging, with no budget available yet every worthwhile tool bringing its own monthly subscription fee along for the ride.</p><p>But these are mere distractions — the real challenges have been how to approach collaboration and communication, along with what documentation and processes to make use of.</p><p>My approach to many of these challenges was at first rigid; I looked for processes, documentation, and frameworks that would help me achieve a desired outcome, or to ‘slot into’ an existing process. I quickly found these to be red herrings; additional documentation was often a chore (with no added benefit), and strict processes too rigid to be of practical assistance.</p><p>Slowly a terrible realisation dawned on me — I couldn’t trust these things to do the job for me. There was no ultimate process or document template that I could hide behind as an authority on the matter, to hold up as the esteemed ideal. No, instead it was on me to do the work. To trust the instincts and knowledge I had built through constant research and analysis, be collaborative yet decisive, and put myself forward as the force to be relied upon. To do so when my skills were yet unproven was terrifying. Never mind that almost no one else within sight appeared to have an understanding of how to implement good UX and so far my input had been valued and respected — I was standing up and telling people how this was to be done, and I had no proof to back me up other than my own confidence in my delivery.</p><p>But you know what? It’s working. When I presented my ‘User Experience Awareness’ presentation to the team, feedback was resoundingly positive, and I have other teams now eager. Requests for more follow-up content followed, and I began to believe that my limited knowledge paired with insatiable passion may really be enough.</p><p>The nature and breadth of my work has now increased. I’ve continued to redesign existing systems, but I’ve also begun to partner with others developing new systems to uplift their effectiveness before they are even made live. The developers haven’t just appreciated my input, but relished in it, and what we have succeeded in developing together now far outweighs the capabilities of either party alone.</p><p>Designing interfaces is fine, I enjoy that. Partnering and consulting with others is valuable, I’ve gained a lot from it. But that’s only one half of the picture. Throughout all this, all of my design decisions and recommendations were based on conventions, heuristics, and subjective (although reasoned) opinions. <strong>I had yet to talk to a real life user.</strong></p><p>I knew I needed more development in the second half of my placement here, and I had begun to free up capacity in my day. So I approached the boss — I wanted to do user research. I wanted to really get to the bottom of someone’s problems, unearth opportunities, and build the understanding that leads to truly unique and tailored experiences.</p><p>I couldn’t believe my luck — that very morning, the directive had been handed down from on high to replace a web-based tool in daily use throughout the organisation’s 500+ outlets, along with varying levels of regional/national management. There were no formal requirements, and the team didn’t possess the right skill set to elicit and document these appropriately — but I did.</p><p>We discussed options as a team (1 lead developer, 1 junior developer, myself on requirements and design), and held our kickoff meeting with the business. I ruminated on it and, after a couple of Friday night beers (always an appropriate setting for such conversations), I put it to the lead developer: I wanted to do more. There was opportunity here. A broad user base whose daily frustrations we knew little about, business stakeholders that were passionate and engaged, and a mandate from a senior enough level that we could take the time to do this right. He gave me exactly what I asked for.</p><blockquote>Do it. Take it and run with it. You can have ownership over the user research and UX design activities. I trust you, and I want to see what you come up with.</blockquote><p>After initial feelings of being pretty pleased and excited with that outcome, the ever-predictable fear set in — what had I set myself up for? I haven’t done this before, how am I going to ensure I do a good job?</p><p>But I’m starting to recognise that feeling — it’s merely a sign that I’m about to stretch and develop, and prove to myself again that I’m capable, I can do this, I can add value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54d6a349fcf3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promoting-ux-practices-a-journey/being-the-expert-when-you-know-nothing-54d6a349fcf3">Being the expert, when you know nothing</a> was originally published in <a href="https://medium.com/promoting-ux-practices-a-journey">Promoting UX Practices — a journey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The lay of the land]]></title>
            <link>https://medium.com/promoting-ux-practices-a-journey/the-lay-of-the-land-aac21752f34d?source=rss----34cc42c6843c---4</link>
            <guid isPermaLink="false">https://medium.com/p/aac21752f34d</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jamieson]]></dc:creator>
            <pubDate>Thu, 09 Jul 2015 23:22:21 GMT</pubDate>
            <atom:updated>2015-07-09T23:22:21.198Z</atom:updated>
            <content:encoded><![CDATA[<p>Back in May I opened this publication with an introduction to my new challenge at work — championing the cause of User Experience Design throughout the organisation (see the article below).</p><p><a href="https://medium.com/p/5db13ff8719"></a></p><p>I’m now just shy of two months into the role, and so far it’s been both an interesting and thoroughly enjoyable journey.</p><h4>The role</h4><p>Beginning these placements always fills me with a touch of trepidation — the stated intent of my roles in the past haven’t always matched up with reality once I join a team. In this case, however, the role has played out even more fortuitously than was expected.</p><p>Whilst the intent to focus on UX Design was agreed with my manager, my broader goals I had kept closer to my chest. So I was thrilled when I was asked to not just research and present to the team on the topic, but also provide recommendation as to how these principles should be integrated into our current development practices, including who should do what activities and at what phases in the development cycle.</p><p>It’s also been a relief that my manager is protective of the nature of my role — in a team that exists to code, I have yet to touch a line of code (other than HTML/CSS/Javascript, of course).</p><h4>The people</h4><p>Discussions with my new colleagues showed varying levels of understanding of the importance and complexity of UX. The developer I was to work closest with was passionate about placing more of a focus on design — but continually referred to it as ‘UI Design’. The seasoned-yet-jaded veteran to my right fully appreciated the need to have clear and explicit reasoning underpinning all design decisions — yet didn’t see much value in developers gaining a greater understanding of the design process. My manager is fond of the phrase “making it look pretty”.</p><p>I see my role here being as much about changing those attitudes as it is about producing deliverables.</p><h4>The work</h4><p>The initial projects I have been handed are both proof-of-concept redesigns of existing web-based systems. At first I lamented the lack of contact with actual users, but being handed full responsibility to take a design wherever I desire has allowed me to experiment with my approach and refine my skills before tackling ‘real world’ problems.</p><p>I’ve been pleased to find that, having researched and ruminated on the practice for so long, it actually comes quite naturally to me. I see clear needs and solutions in every aspect of the screens I am redesigning; I can identify major use-cases and better groupings of on-screen elements; and I’ve begun to document the reasons for every design decision made and link them back to pre-defined guiding principles or established heuristics.</p><h4>The uplift</h4><p>In parallel I’ve been researching specific practices and frameworks with increased verve and distilling these into my own training materials. Discovering frameworks and terminology to define ideas which I could previously only intuit has been empowering, and will be crucial in the process of uplifting both myself and others.</p><p>These dual benefits have led me to devote much time to this activity, however I don’t feel this time could in any way be described as wasteful or luxurious. The change I leave in my wake will be the most important outcome from the time I spend in this role — much more important than any particular work I happen to produce along the way.</p><p>The next challenge for me is to better understand the organisation’s development processes as they are followed today, and construct a lean framework and supportive resources to empower my colleagues to achieve greater success. It will also soon be time to start exposing some of my content to the team — that is a process which both scares and excites me at the same time, but is nevertheless required to move things forward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aac21752f34d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promoting-ux-practices-a-journey/the-lay-of-the-land-aac21752f34d">The lay of the land</a> was originally published in <a href="https://medium.com/promoting-ux-practices-a-journey">Promoting UX Practices — a journey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Challenge, and the Opportunity]]></title>
            <link>https://medium.com/promoting-ux-practices-a-journey/the-challenge-and-the-opportunity-5db13ff8719?source=rss----34cc42c6843c---4</link>
            <guid isPermaLink="false">https://medium.com/p/5db13ff8719</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[change]]></category>
            <dc:creator><![CDATA[Jamieson]]></dc:creator>
            <pubDate>Fri, 22 May 2015 07:12:20 GMT</pubDate>
            <atom:updated>2015-05-22T07:12:20.299Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IAEs1TXgOtUGxgbqQbSOLg.jpeg" /></figure><blockquote>“I would love to have more UX capability in my team, but it’s difficult to get an organisational focus on it.”</blockquote><blockquote>“I’ve been talking with senior leadership about UX focused resources, but haven’t had any traction yet.”</blockquote><blockquote>“I wish we could complete more UX activities up front rather than in tandem with development, but we’re provided no time for this.”</blockquote><p>These were just three of many comments made, from developer through to middle management level, as I discussed my upcoming placement within the organisation focusing on User Experience Design — a practice rarely followed throughout the organisation but, clearly, oft desired.</p><p>Let me back up a little bit and explain the opportunity afforded to me.</p><p>I currently work for a medium sized yet conservative organisation of approximately 8000 staff. Its primary business is not in IT, but its IT spend in enabling its core business is significant. I’m both studying and working in Information Technology; rather than a fixed role or team that I work with, my job entails the undertaking of ‘placements’ performing various roles of interest to me. Apart from the obvious advantages of actually working in a number of areas of my own choosing throughout a relatively short period of my career, this has the additional benefit of rendering me, as a resource, <strong>entirely free</strong> to any department I work in (at least in monetary terms). So when I approached the manager of an area producing small internal apps and proposed that I join them and focus on User Experience Design, she was more than happy to oblige.</p><p>I’m passionate about UX; I believe design permeates everything we do. I see poor experiences all around me, and nowhere more so than at my place of employment. As an organisation we’re in a period of serious and ongoing maturation across the board. There are pockets of progressive thinkers trying to move development practices forward to a more agile, customer-focused means of operation, and the future looks bright — but progress in this area is slow.</p><p>Once I had gained agreement that I could undertake this role, I began talking with management of the various teams and departments that I believed would have a vested interest in the practice. I was pleased to find that they were generally more than receptive to it — in fact, they actually had been attempting to instill it more in their own areas, albeit without much success.</p><p>To my mind, this begged questions — did their own line of management not trust their ability to make recommendations on how their teams should be operating? Did they lack the ability or resources to construct a decent business case? Or was it just too easy to get bogged down in the day-to-day; were their stated desires simply not strong enough to really dedicate to beginning that long and difficult process of adjusting the course of the ship?</p><p>These middle managers — the ones with a modicum of power, and access to those with more — were sitting there crying out for change, when they were the very ones that were able to effect it. A post on our internal social network mentioning my upcoming role led to a 45 minute impromptu conversation with the head of our internal knowledge-management functions on the need for a set of user interface standards across the organisation. The only reason it finished at that point was that we’d gone well past close of business and the poor man had to get home to his family.</p><p>The more I read, and pondered, and talked — the more I believed that there was significant potential to upgrade our processes and thinking to a level where User Experience Design was simply a part of what we did. The desire was there, the recognition was there, but no one was ready to stand up and make it happen. All it required was someone to dedicate to doing it.</p><blockquote>So I decided to be that person.</blockquote><p>I’m excited for this placement — although I have to say I’m a bit scared too. Through all of this, I have no formal (or even informal) qualifications in the field. But I do have passion, and a tendency of loitering in the pockets of the internet where thought leaders in the field reside. I think that’s enough; it’s certainly enough for me to give it a try.</p><p>Heck, in this battle, my naivety could actually be my strongest ally.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5db13ff8719" width="1" height="1" alt=""><hr><p><a href="https://medium.com/promoting-ux-practices-a-journey/the-challenge-and-the-opportunity-5db13ff8719">The Challenge, and the Opportunity</a> was originally published in <a href="https://medium.com/promoting-ux-practices-a-journey">Promoting UX Practices — a journey</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>