<?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 Cameron Rickersey on Medium]]></title>
        <description><![CDATA[Stories by Cameron Rickersey on Medium]]></description>
        <link>https://medium.com/@brosrickersey?source=rss-c90a1323254a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*y5HoFeTsAmw_l_IuEIUVZg.jpeg</url>
            <title>Stories by Cameron Rickersey on Medium</title>
            <link>https://medium.com/@brosrickersey?source=rss-c90a1323254a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:16:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brosrickersey/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[The term ‘user experience’ is a terrible ‘user experience’]]></title>
            <link>https://medium.com/@brosrickersey/the-term-user-experience-is-a-terrible-user-experience-ce3e2f3b59ee?source=rss-c90a1323254a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce3e2f3b59ee</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Cameron Rickersey]]></dc:creator>
            <pubDate>Thu, 03 May 2018 01:13:01 GMT</pubDate>
            <atom:updated>2018-05-03T01:13:01.154Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently I had a conversation with someone I had just met, lets call them Sam, the usual exchange went down</p><p><em>Sam: What do you do?<br>Me: I’m a ‘user experience designer’<br>Sam: ok, so what is it you do?<br>Me: well, I work on digital applications and websites to work out how to identify and solve problems and work out who for, and then make them in the best way for people to use them (ok so this isn’t verbatim but basically what I said)<br>Sam: sounds cool, though sounds like you need a better title so you don’t need to explain it, especially if your job is to make things easy to understand and use, maybe that should be in your title.</em></p><p>And it got me thinking, everytime someone asks me what ‘User Experience’ is, it needs to be explained, …..do people ask dentists, builders, architects, what it is they do? Granted UX design is a very new field/term in a fast paced changing industry but we as the owners and creators of that industry have done ourselves a dis-service by creating these titles, albeit for ourselves, but when we talk about being ‘User Centred’ and all about the ‘user’ <em>(which in itself is a bad term that only drugs and design+tech have adopted)</em> , then why do we come up with some bad titles for ourselves.</p><p>The design and build of the internet and all the applications built from it has grown at such an exponential rate that its hard to beleive that we can credit so much to one single man, yet now there are giant companies with large teams, all dedicated to building tools that rely 100% on this new technology. As this scaled from 1 man working it out, to these enormous teams, companies and careers were created. Being the hierarchial humans we are we needed to then create systems that stacked and ranked people into levels and roles. Ranking levels an roles were all then born to fill these teams and these intricate titles were then adopted from the existing company structures that had all come before them.</p><p>As time moved on and teams grew certain tasks were then delegated and new roles born. Where the ‘web designer’ used to both design and develop a site it become two peoples job, the designer and developer were born. Where the designer used to work out how the site worked and looked, it then became two peoples job, visual designer and user experience designers where born. Where the user experience designer used to do all user research and documentation, behavioura studies, persona creation and prototyping, it then became two peoples job, the ux researcher and ux designer were born. And on and on it goes with some even more interstitial states where we changed terms in some instances with semantic detail. Can you tell me with no jargon or industry buzzwords the difference between a CX designer and a UX designer?</p><p>It’s awesome then when you do come across people/organisations in the industry who do ‘keep it real’ so to speak. Yesterday I came across the Big Spaceship (<a href="https://www.bigspaceship.com/">https://www.bigspaceship.com)</a> user manual which was an epicly refreshing viewpoint of how they approach both the way they communicate to each internally and taking this into there external communications with clients and vendors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gg8dlEK-AC9j_PUn48plcQ.jpeg" /><figcaption>Talk like a human <a href="https://www.bigspaceship.com/public/manual.pdf">www.bigspaceship.com/public/manual.pdf</a></figcaption></figure><p>I love the ‘Talk like a human’ approach, though this should flow all the way to the job title level, and ‘user experience designer’ to me sounds like something a little less on the human side. If you’ve ever thought the title ‘Human Resources’ was as un-human as possible will know what I mean.</p><p>As always the case its easy to be negative than provide solutions, so in order to not dwell on the negative what my answer I hear you say? To be honest I’m not sure, though I do know that I’d love it to be more people focused. The exact responsibilites of designers and developers differs in any given company and in any team within that company, as it should with teams moulding to individual complimenting skills. Instead of then taking the ‘drill down to the final solution’ approach it could be nice to keep it goal focused. Who are we designing and developing for, people, humans <em>(AI can have there own terminologies, their problem to solve</em>). Using terminology that keeps team members titles and roles that at the forefront of what teams are trying to achieve and for whom would move closer to the ‘user centred design’ approach so that is oh so popular at present.</p><p>As stated in a great interview I observed recently , we are a mostly unregualted industry with only internal critique to help and progress and , which can lead to negative effects of insular thinking and processes, even though what we mostly build is for mass society adoption and use. The same way that Directors don’t make movies just for other Directors, and Chef’s don’t only cook for other chef’s, people in tech need to keep our heads above our monitors (pun intended) and internal meeting rooms to keep ourselves relevant and connected to the people (nice way of saying ‘users’) that we are solving problems and building solutions for.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce3e2f3b59ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your User Experience problem is a luxury]]></title>
            <link>https://medium.com/@brosrickersey/your-user-experience-problem-is-a-luxury-f77a9bda95d2?source=rss-c90a1323254a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f77a9bda95d2</guid>
            <category><![CDATA[third-world]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Cameron Rickersey]]></dc:creator>
            <pubDate>Tue, 16 Jan 2018 14:26:55 GMT</pubDate>
            <atom:updated>2018-01-16T14:26:55.481Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a-__MurztCR5m2iH4NP0hA.jpeg" /><figcaption>A rural Laos school</figcaption></figure><p>Like most UX/UI (whatever is trendy to call yourself these days) designers these days I bury my head in technical readings, writings, blogs and try to pay as much attention as possible to how others are solving problems and reading human behaviour changes and applications in the tech world. It is indeed exciting times and can be an all consuming rabbit hole that leaves one thinking can you ever actually have the feeling of being on top of all the changes in processes and technology? Admittedly after a hard days ignoring the task at hand to be consumed by article after article one can feel a little overwhelmed by the pace of it all.</p><p>To overcome this feeling one can then open the door, go out of the office/house and walk on the footpath, down the street, get to the coffee shop and decompress. Things are a little different where I live, there is no footpath, the road is still predominantly a dirt track, and navigating across the road is an illogical game of luck plus skill at the best of times. Smack bang in the middle of South East Asia, seemingly frozen in time, is the land-locked country of Laos, where unlike your local coffee shop, the society and the way things work is not reflectant or representational of what you can see or read online.</p><p>In a country where the pursuit of people is not solely financial gain, and the rate of change is slow, it can be a refreshing change to disconnect and get a first hand view of ‘the way things used to be’. Laos is a small country with a fast growing economy (<em>apparent growth rate of over 7% per year since early 2000’s</em>) but the struggles of being a remote land-locked, developing country that most people have never heard of are real. Issues such as the minimum wage just now reaching a record high US$111 a month, quality and access of education, healthcare, cultural barriers, trade and buying powers, skills development, reliance on foreign input and all manner of issues make up this great place.</p><p>Being a long term visitor / or short term resident from a first worldit becomes tempting to view the way things work through the lense of a practitioner and applying such logic, favourite phrases raise weekly “Why can’t the traffic work like this?”, “why don’t stalls setup and process things like that?” but in the end these are all trivial selfish personal pursuits. The other side of being a long term visitor is the opportunity to realise that lessons learnt come easy in the first world where schools teach you not only content of what you should know, but moreseo how to think to search for knowldge on your own.</p><p>When I first arrived in this small great peaceful land I set to work to try and balance my life of remote work back to Australia and the US for my main commercial practice but also be able to use some of the skills I’ve been lucky enough to learn over my career to apply to some local projects and people to try and “help” (&lt;- total common white man philosophy). Another story for another time but realising some cold truths about both the inner working of the development world, and the levels of digital engagement (outside of facebook) and competency it became pretty clear that my skillset would be better spent somewhat ‘not on the ground’ so to speak, but looking a bit more practically at real life in a uniquely positioned developing country. A country where ‘user experience design’ as a trade is about as primarily needed and useful as a Fine wine Sommelier for people with an average income of $111 a month. Namely a complete luxury that has a few things needed to fix first before getting to.</p><p>Upon this realisaton that my ‘help’ was crap I needed to find a better way to possibly contribute to this country that would be my new home for half a decade. Having seen on the ground the way the ‘development’ world works (another story altogether) I thought it best to try and cut out the middle man and use the advantage I did have, actually being present.</p><p>People talk alot about networking and the importance of face to face meeting opportunities. This rarely comes my way down here in my field but seeing and meeting the people on the ground from the international aid organisations that I saw growing up on television (you know the ads) I get the unique opportunity to see just how things get implemented on the ground. Without naming any names or getting into the mindgame of aid and development, there are some parts of the process that could be improved to get better end results.</p><p>The designer and problem soliver in me asked how can I go the other way that can skip the beauracracy and go straight to the source. As I mentioned the benefit of being on the ground is that you are there and present and can see the problem first hand, and can then extend that hand directly in return, cutting out the middle man. Alot of my work as UX designer looks at improving processes to either do exactly that, optimise for best usage and efficiency for both the business, and the people that the products hand then goes in, the end “user” (only business except drugs that has users).</p><p>All of this is well and good to understand but then how could I use my skillset to actually help people, if as mentioned my skillset wasn’t useful in this part of the world? Well sometimes you just have to look up, there are so many sectors of this country with opportunities to help, education, health, forestry, the list goes on. With a problem so big, what can I do? Hence your UX problem is a luxury, “increasing engagement of a CTA to buy stuff” is a bit different to getting kids to be able to go to school. But this is what I wanted to do, help kids go to school. Being lucky enough to know some people in the field who were involved in remote communities that were trying to get kids to go to school, it was a place where I could help.</p><p>So putting on the work hat, and connecting it to the simplist way possible. Problem = kids find it hard to get to school when its wet and is hard to stay clean and healthy when do attend. Translated into a user story; As a user I want to be able to go to school when its wet and stay healthy and clean when I get there.</p><p>As you can see from the image above, remote schools are basic structures with a roof over a dirt floor with some log chairs and tables. Theres alot that could be done but what could I do that was the simplest thing that could be done to start to hit the problem on the head.</p><p>The simplest solution for me. Concrete the floor. Literally just put concrete down on the dirt floor that turns to mud that then prevents children from staying dry and clean when in class.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AGYc8Hn5vpDwlhx7ONaTSA.jpeg" /><figcaption>Concrete pad installed</figcaption></figure><p>It sounds simple. And often the best solutions are. Without the need for total over regulation and deep consultant over-analysis we were able to do the things I love to do in my work, test and learn, move fast and get things done. Real artists ship as they say, and as I don’t profess concreting a floor to be painting the Sistene Chapel, nor the methodology of just doing something and walking off, the effects were monitored and beyond any of our imagined expectations. School attendance for the whole term post concrete floor went up from 25 kids on average a day to 42. More kids came, stayed healthier and learned. The link from the concreted floor to toilets and handbasins made then cleaner, more accessible and more utilised with an average of 17 more kids per day going to school to get and education. To me this was one of the most satisfying results to a user experience problem I’ve helped to solve to date.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f77a9bda95d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>