<?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 Rob Scherer on Medium]]></title>
        <description><![CDATA[Stories by Rob Scherer on Medium]]></description>
        <link>https://medium.com/@uxRob?source=rss-cb6fa6047534------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*ILQcEdIXbL_rM7SDEkpHIg.png</url>
            <title>Stories by Rob Scherer on Medium</title>
            <link>https://medium.com/@uxRob?source=rss-cb6fa6047534------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:25:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@uxRob/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[Redesigning Our Design Feedback Sessions. Based On Feedback]]></title>
            <link>https://medium.com/seek-blog/redesigning-our-design-feedback-sessions-based-on-feedback-80d119aea871?source=rss-cb6fa6047534------2</link>
            <guid isPermaLink="false">https://medium.com/p/80d119aea871</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[ways-of-working]]></category>
            <category><![CDATA[design-teams]]></category>
            <category><![CDATA[design-feedback]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Rob Scherer]]></dc:creator>
            <pubDate>Fri, 03 Apr 2020 03:06:54 GMT</pubDate>
            <atom:updated>2020-06-29T05:09:21.103Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A design feedback session (pinup) at SEEK." src="https://cdn-images-1.medium.com/max/1024/0*NE1KTkz9urC0qXyj" /><figcaption>A design feedback (pinup) session at SEEK. Photo captured by Daniel, who was remote.</figcaption></figure><h4>Why (and how) we provide design feedback at SEEK</h4><p><em>This piece was co-written with my colleague </em><a href="https://medium.com/@danjim"><em>Daniel Jimenez Nassar</em></a></p><p>As a growing design organisation, we frequently review the ways we work together to ensure that our rituals are aligned to the needs of our evolving team and practice.</p><p>During a recent review, feedback from the team highlighted that we could make some changes to the framework for our design pinup sessions in order to make the sessions more meaningful and worthwhile.</p><figure><img alt="Output from a team-wide ‘ways of working’ review." src="https://cdn-images-1.medium.com/max/1024/0*4xsOeAX6ynAzvH70" /><figcaption>Output from a team-wide ‘ways of working’ review</figcaption></figure><h4><strong>What are pinups?</strong></h4><p>Pinups are nothing new and pretty common among design teams. You might see them otherwise referred to as “critique” or “design sparring” sessions. We prefer “pinups” as it feels a bit safer and less combative. We’d been running weekly pinups for a number of years without much change so it was good to spend some time looking at what was and wasn’t working well and make some adjustments.</p><p>Pinups at SEEK involve a group of designers coming together to share their work in order to receive helpful and constructive feedback. The goal is to make the designs better, ensure consistency across different products, and share knowledge and viewpoints in order to move the work forward.</p><p>We deliberately keep the size of our pinup groups small as we find that provides everyone a chance to present their work frequently, and so that we can keep the conversation focused.</p><p>We want to ensure that this forum is seen as a safe space where designers can feel supported and gain confidence in the best ways to progress their work.</p><h4><strong>What was lacking?</strong></h4><p>When the team got together to review our ways of working, a number of needs and areas for improvement surfaced. These included: getting timely design feedback, learning from each other, understanding what other parts of the company are doing, and having better cross department collaboration. It was interesting that those themes arose, as they cover many of the reasons why we have design pinups. So we investigated further and started to implement some changes to our pinup framework.</p><h4>What were the issues? What did we change?</h4><p><strong>Issue: </strong>As a 2-sided marketplace, splitting our pinup groups down those sides (employers and job seekers) limited visibility of the impact designs might have on the opposite side of the marketplace.</p><p><strong>Change: </strong>We created groups that mixed designers from both sides of the marketplace. Designers who worked on the job search experience for job seekers were mixed with those who focused on the job posting experience for employers.</p><p><strong>Issue: </strong>Design feedback often lacked focus, or focused on the wrong elements of the design.</p><p><strong>Change:</strong> We created a more structured framework for presenting work and giving feedback. We allocated roles (presenter, facilitator, audience) with specific responsibilities during the session.</p><p><strong>Issue:</strong> Conversation tended to drift to less relevant topics.</p><p><strong>Change:</strong> We made design feedback the primary reason for getting together. Any other type of content would only be discussed if time permitted.</p><h4><strong>Creating new groups</strong></h4><p>We used to have one pinup for designers who were focused on solving problems for job seekers, and another for those working on employer products. We decide to create groups that mixed designers from both sides of the marketplace. Designers who worked on the job search experience for job seekers were mixed with those who focused on the job posting experience for employers.</p><figure><img alt="Image showing how we include designers from both sides of our marketplace in each pinup." src="https://cdn-images-1.medium.com/max/1024/1*usyg69bnbc-jTMYLwFZrug.png" /><figcaption>Mixing pinup groups to include participants working on both sides of the marketplace.</figcaption></figure><p>The result of this simple change has been profound. We are now seeing much better awareness and collaboration across both sides of the marketplace which is resulting in better experiences for our customers.</p><h4><strong>Structuring the sessions</strong></h4><p>As already mentioned, one of the areas of feedback about pinups was that design feedback often lacked focus, or focused on the wrong elements of the design. In order to address this, we implemented a more structured format for presenting work and giving feedback. The person presenting their work frames the conversation by addressing 5 key questions:</p><ol><li>What are you working on?</li><li>What’s the business &amp; user/customer need?</li><li>What’s the goal of your design?</li><li>What specifically are you seeking feedback on?</li><li>What stage is the design at (we use <a href="https://medium.com/swlh/using-the-30-60-90-framework-for-design-critique-960b68026b6f">the 30/60/90 format</a>).</li></ol><p>These questions help the designer who is presenting their work to set the scene for others in order to receive more meaningful feedback and progress the areas of the design that most need to evolve.</p><figure><img alt="Our template for structuring pinups." src="https://cdn-images-1.medium.com/max/1024/0*JbiLkukE0OiI1yfj" /><figcaption>More structured presentations result in better feedback.</figcaption></figure><p>We created a template that helps the designer tell the story by answering the 5 key questions above in order to receive more meaningful feedback.</p><p>This has probably been the most important change.</p><p>It took a little while for people to adjust to the new structure but now that everyone is used to it we’re finding that conversation is more focused and the people presenting their work are receiving much better feedback.</p><h4><strong>The 3 roles in SEEK pinups</strong></h4><p>We were inspired to define the 3 roles of pinups by this <a href="https://www.pinterest.cl/pin/230528074659323632/?autologin=true">poster</a> created by <a href="https://www.linkedin.com/in/pursuitofnow">Jim Jones</a> while working at <a href="https://www.oracle.com/au/industries/utilities/products/what-is-opower.html">Opower</a>.</p><h4><strong>Facilitator</strong></h4><p>One of the challenges when entering a design conversation is to keep focus and keep time under control. It seems we love to chat, and we love to go deep on curly issues. Given the nature of the challenges we commonly discuss it’s easy for conversation to drift into interesting (but less relevant) areas. To address this, we focused on providing clarity about the different roles in pinup and created a dedicated facilitator role. The facilitator:</p><ul><li>keeps the conversation focused</li><li>ensures we stick to the allotted time</li><li>captures notes about the feedback that is being given</li><li>promotes equal participation and ensures that everyone gets a chance to be heard.</li></ul><p>Having the facilitator capture notes has proven to be really valuable. It allows the presenter to really focus on the conversation and the feedback that is being given without having to capture it themselves. We share the feedback in a Slack channel so that it can be referred to in future pinups as the designs evolve.</p><h4><strong>Presenter</strong></h4><p>The presenter’s role is to provide clear context about the work they are presenting and the feedback that they are seeking. The presenter:</p><ul><li>Adds themselves to the pinup agenda (an active post on Slack) during the week leading up to the pinup. We’ve found that 20–30 minutes per presenter is about the right amount of time</li><li>Prepares their response to the 5 key questions (context, need, goal, feedback required, stage of design)</li><li>commits to loop back to the group as the design evolves.</li></ul><h4><strong>Audience</strong></h4><p>The role of the audience is to listen to and understand the context given by the presenter, ask clarifying questions, and provide constructive feedback to the presenter in line with what they have requested (i.e. no discussion of button colours if the presenter is interested in feedback about the page flow or form labels).</p><figure><img alt="The three roles in pinups." src="https://cdn-images-1.medium.com/max/1024/0*8bcox7gRVPow2W0-" /><figcaption>The three roles in pinups.</figcaption></figure><h4><strong>How are these sessions going &amp; where to next?</strong></h4><p>We’ve been running these revised pinup sessions for about 6 months now and we’re really happy with how they’ve been going. Team members seem more engaged, people are presenting their work more frequently and, most importantly, people are getting insightful feedback about their designs that they are able to use to make their work better.</p><p>However we never sit still so we are planning ongoing reviews to continue our commitment to continuous improvement of our design practice at SEEK.</p><p>What does your team do for design feedback? We’d love to hear from you if there are any interesting and effective things that work for you.</p><h4><strong>COVID-19 update</strong></h4><p>We’ve made some adjustments to help these sessions run smoothly in a world where all participants are working from home.</p><p>Presenters now share their designs in the pinup Slack channel ahead of time so everyone has an opportunity to prepare and understand what we’re going to be giving feedback on.</p><p>Presenters are also encouraged to do a little more preparation in structuring their presentation so there’s less jumping around inside Sketch files or similar. This makes it easier for people follow at home.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80d119aea871" width="1" height="1" alt=""><hr><p><a href="https://medium.com/seek-blog/redesigning-our-design-feedback-sessions-based-on-feedback-80d119aea871">Redesigning Our Design Feedback Sessions. Based On Feedback</a> was originally published in <a href="https://medium.com/seek-blog">SEEK blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is My Team Afraid of Me?]]></title>
            <link>https://medium.com/seek-blog/is-my-team-afraid-of-me-b83d97f82cfb?source=rss-cb6fa6047534------2</link>
            <guid isPermaLink="false">https://medium.com/p/b83d97f82cfb</guid>
            <category><![CDATA[ux-leadership]]></category>
            <category><![CDATA[design-teams]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Rob Scherer]]></dc:creator>
            <pubDate>Mon, 07 Aug 2017 23:59:11 GMT</pubDate>
            <atom:updated>2018-12-17T03:02:48.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/815/1*xIRj0Ehbi6kyOoB5UIBsgA.jpeg" /><figcaption>Photo taken by <a href="https://pixabay.com/en/users/Sarah_Loetscher-4248505/">Sarah Loetscher</a></figcaption></figure><p>A series of recent conversations with people in my team left me questioning my success in building trusting relationships.</p><p>I thought I had created strong relationships with my team, where they felt comfortable to come to me with problems, issues, frustrations, and challenges. I thought my team trusted me to be on their side — to have their back — but three separate conversations within a short space of time left me concerned that wasn’t the case.</p><p>These three conversations involved the person communicating something they were struggling with and asking for my advice. They were really productive conversations and I felt like we were able to discuss the problem, unpack goals, explore solutions and formulate a plan. Each team member thanked me for my help and each followed up by saying the thing that shocked me:</p><blockquote>“I wasn’t sure whether or not I should tell you about that.”</blockquote><p>Why would they feel that way? We’d had similar conversations in the past, with positive results. Maybe they didn’t feel those conversations were as useful, on reflection, as I did? Why wouldn’t they think that they could talk to me? Are there other things they’re struggling with that they don’t feel that they can talk to me about?</p><h4>Am I a coach or a manager?</h4><p>I treat these conversations as coaching opportunities, a chance to help my team to learn, grow, and develop their skills. That’s my job and an approach that <a href="https://www.seek.com.au/work-for-seek">SEEK</a> has been really active in promoting among the leaders in the business through our <a href="http://www.hcamag.com/rankings/innovative-hr-teams-2017/seek-234162.aspx">Coaching for SEEKcess</a> program. I’ve been trained to help my team to be their best.</p><p>The way someone will communicate with a coach is different to the way they might communicate with a manager. A typical dictionary definition of “<a href="https://en.oxforddictionaries.com/definition/coach">coach</a>” is: “A tutor who gives private or specialised teaching”. A “<a href="https://en.oxforddictionaries.com/definition/manager">manager</a>” is defined as: “A person responsible for controlling or administering all or part of a company or similar organisation”.</p><p>While I might think I’m playing a coaching role, my efforts are hamstrung if I’m perceived to be a manager. Something as simple as the words used within the organisation can have an impact. People don’t ask “who’s your coach?”, rather, “who’s your manager?”. This sets the default context for the relationship.</p><p>In our next 1:1 catch ups, I made a point of bringing up these conversations and asked them why they felt unsure about talking to me. I was explicit about my desire to help each person in my team with anything they’re finding challenging — that we all struggle with things from time to time — and that it’s healthy to talk about these things. I reinforced that I want to be able to <em>be there</em> for them.</p><p>It turns out that they were afraid that I, as their manager, might see them as weak, incapable, or unprofessional. That I might judge them to be ill-equipped to do their job. Being part of an organisation that is focused on performance and celebrates success, it makes sense that people might be fearful of being seen as weak if they aren’t always ‘winning’. There’s a fear that struggles can be seen as failures if all you ever hear are success stories. We need to get better at sharing, and learning from, our struggles.</p><p>Reinforcing that we all have challenges and sharing some of my own was well received and appreciated. Personal challenges — whether they be about process, relationships, or roles &amp; responsibilities — can benefit from a fresh set of eyes or ears. If those challenges can be overcome, then people are more likely to be happy and productive within their teams.</p><p>This has been a pretty big leadership lesson for me. Being explicit about the role I want to play with my team is really important. It’s not enough to “just do it”. It’s important for me to set the context of our relationship, our goals, and my role as a leader/coach/manager. For the first time, I have been explicit with everyone in my team about seeing myself as a coach, rather than a manager. While I might have felt like it was implied, it’s been important to be explicit.</p><p>People are often afraid of the unknown and affected by past experiences. It’s best to make my intentions understood so that I can be the coach that my team looks to for guidance on how to be awesome at their job.</p><h4>I need your help</h4><p>I’d love to hear about your successes or failures in establishing yourself as a coach, the challenges you’ve faced in building relationships where your team is as comfortable to come to you with problems as they are to tell you about their wins, and the ways you’ve succeeded (or failed) to do this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b83d97f82cfb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/seek-blog/is-my-team-afraid-of-me-b83d97f82cfb">Is My Team Afraid of Me?</a> was originally published in <a href="https://medium.com/seek-blog">SEEK blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The bits are a hit, the experience is shit]]></title>
            <link>https://medium.com/@uxRob/the-bits-are-a-hit-the-experience-is-shit-7074e899844a?source=rss-cb6fa6047534------2</link>
            <guid isPermaLink="false">https://medium.com/p/7074e899844a</guid>
            <category><![CDATA[service-design]]></category>
            <category><![CDATA[xbox-one]]></category>
            <category><![CDATA[gaming]]></category>
            <dc:creator><![CDATA[Rob Scherer]]></dc:creator>
            <pubDate>Wed, 23 Mar 2016 11:27:32 GMT</pubDate>
            <atom:updated>2017-08-07T04:00:43.914Z</atom:updated>
            <content:encoded><![CDATA[<p>January 12, 1987. A Monday. I remember the day clearly. It was the day that I took the money I’d saved up from my paper round and bought my first game console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*txs3J_s3FOLW7DU9DFIvPA.png" /><figcaption>Commodore 64 “Micro Computer”</figcaption></figure><p>While the Commodore 64 was marketed as a “micro computer”, they weren’t kidding anybody. This was, to me, a game console and over the next 5 or 6 years, I spent hours enjoying the high resolution gaming experience delivered by that 8-bit powerhouse.</p><h4>Load “*”,8,1</h4><p>I have a very clear memory of getting home, plugging in the cables, entering the magical string that made the tape drive whirl into action and playing my first game.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ubLvvKnD_qJmxYS-qY91Tg.png" /><figcaption>High Resolution in 1987</figcaption></figure><p>In 1996, I bought a Sony PlayStation. No more entering geek codes in order to play games. Just pop the CD in, shut the lid, and play. A great leap forward in graphics, speed, power, and (arguably) game-play. Game consoles were great and clearly getting better.</p><p>Adulthood largely saw the end of my gaming days and with the exception of a short stint with a Wii, I went consoleless for a number of years.</p><p>So, when I came home with an <a href="http://www.xbox.com/en-AU/xbox-one/consoles/halo-5-guardians">Xbox One Halo 5 bundle</a> for my sons (10 and 12) just after Christmas, I was excited. Excited for them. Well, if I’m being honest, not just excited for them.</p><p>Plugging in the cords while they sat on the couch, controllers-in-hand, I had flashbacks to the excitement and anticipation I had felt 29 years ago. I felt again what they were surely feeling for the first time and was happy for them. Happy that in a few short minutes they would be enjoying their new console.</p><p>But that’s not what happened.</p><h4>System update</h4><p>The Xbox One needed to download and install a 1.2GB system update before it could be used. Over the course of the hour or so that the download took, I was able to explain the difference between a Megabyte and a Gigabyte and how long 1.2GB would take to download on our 8Mbps connection. Every cloud has a silver lining. And the silver lining here was that they got a little schooling.</p><p>Not long now. Sit tight boys.</p><h4>Sign in to Xbox Live</h4><p>I’d pre-empted this. Before purchasing the console, I’d gone online to create a Microsoft Live account for each boy. And one for me, while I was at it. Signing in to the accounts with the controller and on screen keyboard was cumbersome and frustrating, particularly as I had used a password generator to create strong passwords. <strong>Fu(#1ngH377</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*fBhIq8UsUmfpEKKJiFNSHA.png" /><figcaption>Try entering D$k7(bFa@y^</figcaption></figure><h4>Where’s the game?</h4><p>As I’ve mentioned, I purchased a console + game bundle. So once we were signed in, I went to grab the game so that we could, finally, start playing. Only, there was no game. Just a card with a code that I needed to enter in order to download the game. A wave of despair washed over me as it dawned on me that this couldn’t be a good thing. On entering the code and subsequently watching the download status sit on 0% for 5 minutes, I Googled “halo 5 download size”.</p><p><strong>55GB!!!</strong></p><p>The look on my boy’s faces affirmed that had absorbed my lesson about Gigabytes, Megabytes, Mbps, and download speed. They knew before I told them. There’d be no gaming tonight. <a href="https://www.youtube.com/watch?v=2akt3P8ltLM">Not. Happy. Jan.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xT31Hfb3POGVZoYLiEwYyQ.png" /></figure><h4>Auto Shutdown</h4><p>We went to bed that night with the game download sitting at 17% and the expectation that we’d be enjoying our first game at around lunch time the next day.</p><p>We were wrong.</p><p>Little did we know, but the Xbox One’s default setting is to shut down after an hour of inactivity. So that’s what it did. 8 hours of downloading. Lost.</p><p>The game continued to download through the day and by bedtime, it still hadn’t completed.</p><h4>Victory of sorts</h4><p>Finally, the next morning, 36 hours after we first plugged it in, my boys played their first game on the Xbox One.</p><p>While they were clearly delighted and enjoying their new toy, I couldn’t help but feel a little sad for them. Sad that they wouldn’t look back on their first game console experience with the same sense of nostalgia that I look back on my Commodore 64 with. While the hardware, the games, and multi-player capability is clearly orders of magnitude better than it was in the old days, that feeling I had on that day in 1987 would be quite different to the feeling that my boys remember. Their experience was spoiled and it could so easily have been different.</p><h4>Easy fixes</h4><p>Two simple things would have made this a much better experience:</p><ol><li><strong>Pre installing the bundled game</strong>, or including the Blu-ray disk is a no-brainer.</li><li><strong>Simple sign in</strong>: Using the controller and on screen keyboard was painful. Allowing sign in on a computer and then displaying a code (as Plex do) or even better, a sequence of strokes that can be performed on the controller would create a moment of delight.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FkxSPZqKBOM2HEdhFgItCg.png" /><figcaption>Plex’s solution for signing in — where it’s likely the device isn’t connected to a keyboard</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BCRNArA5kZRMBvpJIsU_5A.png" /><figcaption>What might have been</figcaption></figure><p>Despite these issues, Microsoft have sold—and will continue to sell — a load of Xboxes and I have no reason to believe that Sony have done any better with the PlayStation 4. But, I believe that they’re missing an opportunity. By making a couple of small changes to the delivery of the service, they would create positive memories in impressionable young minds. Minds that will go on to make a lot of purchasing decisions over the years to come. The kind of minds that you want to be thinking of your brand in a positive light.</p><p>If only Commodore was still in business.</p><p><em>This is an adaptation of a </em><a href="http://www.slideshare.net/uxRob/the-bits-are-a-hit-the-experience-is-shit"><em>presentation I gave</em></a><em> at UX Australia’s </em><a href="http://www.uxaustralia.com.au/conferences/servicedesign-2016/"><em>Service Design 2016 Conference</em></a><em> in Melbourne, Australia on 22 March 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7074e899844a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Take Yourself Too Seriously]]></title>
            <link>https://medium.com/seek-blog/don-t-take-yourself-too-seriously-16f838ff3db2?source=rss-cb6fa6047534------2</link>
            <guid isPermaLink="false">https://medium.com/p/16f838ff3db2</guid>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[workplace-culture]]></category>
            <category><![CDATA[hackathons]]></category>
            <dc:creator><![CDATA[Rob Scherer]]></dc:creator>
            <pubDate>Mon, 30 Nov 2015 05:37:18 GMT</pubDate>
            <atom:updated>2019-10-23T00:24:22.643Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zkaKmBCaDSkhcvIN9oHBgw.jpeg" /></figure><blockquote>Now here’s a little story I got to tell<br>about a great joint you know so well<br>It started way back in history<br>with Matt-Rock(man), MC Andrew and Paul B</blockquote><blockquote>They had a little company that others would fear<br>Just them, their culture, and a lot of beer<br>Laying out their hand, rivers of gold be damned<br>Fairfax must be thinking that they’ve been scammed</blockquote><blockquote>One little pink book it be<br>A bunch of pictures and some copy<br>The culture’s coming through and it’s really phat<br>We’ll give it to new dames and new chaps</blockquote><blockquote>We’ll tell it how it is and how it was<br>So all will know it’s not just because</blockquote><p>Last week was the fifth (and my second) hackathon at <a href="https://www.seek.com.au/work-for-seek">SEEK</a>.</p><p>Hackathon 5 had a hip hop, rap, street, graffiti theme and, fittingly, the week opened with a rap battle, where the teams busted out the rhymes in order to promote their ideas and recruit members.</p><p>Our Managing Director, Mike Ilczynski, opened the hack by saying: “This is a big investment from the business but we’re really looking forward to seeing what you all create.” I think what he was trying to say was: “Mo money for your skills. Don’t waste my bills.” But, whatever.</p><p>A total of 33 teams self-organised to try to create something great in 3 days. As well as the serious work being done, there was a real emphasis on fun. In addition to the rap battle on day 1, we also had a dance off (complete with massive cardboard dance floor) and a bling making competition — if you can’t find any silver foil at the supermarket this week, you know why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/1*F-ZV6Rc1xl0C16uex2XmKg.jpeg" /><figcaption>The photographer made it look more graceful than it actually was</figcaption></figure><p>One thing that struck me a number of times during the week was that the people who had the most fun and contributed the most to the vibe were the ones who were happy to take the piss out of themselves in order to get a laugh — like the first person to take to the cardboard and show us his terrible moves (with such attitude) or the guy who foiled up a cane, shades, and platter of foil “notes” which he made rain into the crowd. Pimp dawg!</p><p>My awesome team worked on the “Little Pink Book”. Inspired by <a href="http://benbarry.com/project/facebooks-little-red-book">Ben Barry’s Little Red Book</a>, we wanted to create a beautiful book that could be given to new starters so that they could get an impression of the unique culture at SEEK and some of the things that are a bit different to your ordinary company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C-p928m0d4Qh7BuqvT0AoA.jpeg" /></figure><p>I’m in my 12th year (and second stint) at SEEK and there is a large contingent of employees who have been here for more than 10 years so one of the things I hoped to achieve was to give a sense of what it was about this company that led to its employees wanting to stay for such a long time and to come back after they may have left.</p><p>Through the course of the hackathon, we trawled through email archives &amp; photo albums and met with dozens of employees — old and new — to extract the essence of SEEK’s culture and distill it down to a set of statements, anecdotes and images that made the finished book.</p><blockquote>Take your work seriously, just don’t take yourself too seriously</blockquote><p>Work is serious but that doesn’t mean that you have to be or that you can’t have fun. Testament to this; we researched, wrote, designed, published, and printed our book in 3 days while having a great time working with people we wouldn’t ordinarily work with. One of the funniest and most rewarding experiences of my career.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JkS1D4L86VGixHRy3_kj-g.png" /></figure><p>And we clearly weren’t the only ones having fun and doing great things. The work that was displayed in the Hackathon Marketplace on Friday afternoon was creative and innovative. World class. All of the projects focussed on solving real business problems and many of them are ready to ship. Seeing all of the teams dressed up in rap/gangsta threads and presenting their wares — exhausted, but smiling, was a great sight.</p><p>How my team didn’t win “The Marketer” award, I’ll never know. Our marketing campaign included video and email endorsements — one genuine, one hacked (So. Much. Laugh.) — from 2 of the 3 founders of SEEK as well as a fresh rhyme to dope beats. But no sour grapes here, just the sweet taste of working with great people, for an inspirational company where we are able to do serious work and have a heap of fun while doing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vgpsJTCM2Ap9Qn1dJLg71w.png" /></figure><p>Hackathon 5 was, in my eyes, a roaring success. Maybe that’s because of the emphasis on fun. It could be because the reins were loosened and employees were free to work on things they wanted to work on. Perhaps it’s because each team member was invested in their idea. Regardless, I have to take my bucket hat off to the SEEK leadership team for believing that their people will do the right (and great) things if given the chance.</p><p>I hope the investment was repaid in spades. I believe it was.</p><p>Props to my crew.</p><p>Word.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16f838ff3db2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/seek-blog/don-t-take-yourself-too-seriously-16f838ff3db2">Don’t Take Yourself Too Seriously</a> was originally published in <a href="https://medium.com/seek-blog">SEEK blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everyone’s a Designer]]></title>
            <link>https://medium.com/seek-blog/everyone-s-a-designer-a8f599c9b338?source=rss-cb6fa6047534------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8f599c9b338</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[collaboration]]></category>
            <dc:creator><![CDATA[Rob Scherer]]></dc:creator>
            <pubDate>Sun, 20 Sep 2015 23:05:05 GMT</pubDate>
            <atom:updated>2018-12-18T04:39:16.480Z</atom:updated>
            <content:encoded><![CDATA[<p>Whereas this statement used to annoy me, now it excites me!</p><p>I like to think back to when I was a green designer, just starting out — actually I don’t like to think about it too much but it’s good to reflect on.</p><p>Back then, I had to come up with the answers. This was my problem to solve. In order to do my job well, I needed to win at designing awesome experiences.</p><p>I had a pretty tough time! I felt like I wasn’t winning all that often.</p><p>I’d take the brief from the product manager, put my thinking cap on and bury myself away to ‘do design’. Once I was finished, I’d materialise with my designs, hand them over, and <em>run</em>!</p><p>I didn’t run at the start, but I soon learned to.</p><h3>Jeff Croft on Twitter</h3><p>Developer: We should do x. His non-dev boss: You know best! Designer: We should do x. His non-designer boss:</p><p>It seemed that everything I presented was pulled apart and debated. No matter how much thought I’d put into it and no matter how many alternatives I’d considered, it seemed that there was always something that people didn’t agree with. I was proud of my work so I’d often get defensive. Then there’d be arguments and debates. And — because we were working in waterfall — by the time we all agreed, the business priorities had shifted and off we’d all go onto another project, often without building any of the things that we’d argued so furiously about.</p><p>Not the most productive or pleasurable process.</p><p>Contrast that to the way I work now. Now, I don’t have to come up with all of the answers. In fact, sometimes I don’t even try to come up with answers, I just try to come up with as many questions as I can. I let other people answer the questions and in my experience, people love answering questions and solving problems.</p><h3>Many hands make light work</h3><p>Designing collaboratively allows other designers, team members, stakeholders, and even users to create design ideas and explore alternatives. Much better to get another person’s view early on in the process than towards the end.</p><p>By throwing more brains at the problem, you’re likely to uncover alternatives and ideas that you wouldn’t have thought of yourself.</p><p>A problem shared is a problem halved.</p><h3>Shared understanding</h3><p>Collaborative design also facilitates early communication, discussion, debate, and idea sharing which help to create a shared understanding among the team.</p><blockquote>In this world, there are many heads, but in each head there is a different world. — Ida Jo Moreno</blockquote><p>When all members of the team have had an opportunity to contribute their ideas, the designer can then synthesise all of the input into designs that can be tested with users. Going back to the team with user feedback on their ideas (or even better — having the team members observe the user research) is a great way to generate a shared vision of the desired outcome.</p><h3>Shared ownership</h3><p>When you include people in the design process, they become invested in the product and feel a sense of ownership. As a result, they are more likely to provide useful input, rather than just feedback for feedback’s sake.</p><blockquote>The first quality a UXer should have is modesty and humility. To be open to suggestions from the ‘least likely’ person (even the cleaner) and to keep in mind that as a designer they are the facilitator and custodian of good design, not the creator of it. — Bernard Schokman</blockquote><p>As a design facilitator, you’re more likely to be valued, trusted, and respected than you would be as a precious designer. That feels good and a nice by-product is that you’re more likely to get to a better design faster. You spend more time creating and less time debating.</p><h3>More</h3><p>My colleague, <a href="https://medium.com/@ThatBaldUXGuy">Vedran Arnautovic</a>, has previously written about <a href="https://medium.com/seek-user-experience/two-types-of-collaborative-design-sessions-46c6d7090b70">running collaborative design sessions</a> and <a href="https://medium.com/seek-user-experience/4-simple-steps-to-improve-your-ui-sketches-4ad2f1433373">4 steps to improve your UI sketches</a> which I recommend if you’re interested in working more collaboratively with your team.</p><p>Jason Fried recently wrote a great little piece about <a href="https://medium.com/@jasonfried/give-it-five-minutes-b8115d6f2361">asking more questions and giving less answers</a>.</p><p><em>Follow us at </em><a href="https://medium.com/seek-user-experience"><em>SEEK User Experience</em></a><em> and </em><a href="https://medium.com/seek-culture"><em>SEEK Culture</em></a><em> as we tackle the social and ethical challenges of producing software at scale that respects humans on an individual level.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8f599c9b338" width="1" height="1" alt=""><hr><p><a href="https://medium.com/seek-blog/everyone-s-a-designer-a8f599c9b338">Everyone’s a Designer</a> was originally published in <a href="https://medium.com/seek-blog">SEEK blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Principled UX Design Process]]></title>
            <link>https://medium.com/seek-blog/a-principled-ux-design-process-5063a10cc6bf?source=rss-cb6fa6047534------2</link>
            <guid isPermaLink="false">https://medium.com/p/5063a10cc6bf</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Rob Scherer]]></dc:creator>
            <pubDate>Thu, 16 Jul 2015 01:12:48 GMT</pubDate>
            <atom:updated>2018-12-18T04:44:29.036Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently took up the task of re-defining the UX design process for the team at <a href="https://www.seek.com.au/work-for-seek">SEEK</a>, one of Australia’s leading online businesses with a number of concurrent agile projects.</p><p>Each project has different design challenges and individual designers want/need different amounts of guidance so we were keen to update our existing process to one that was guiding, without being too prescriptive.</p><p>While the end result is a documented process that follows the path through a project from discovery to delivery and beyond, we’ve included a set of overarching principles and goals that help the UX designer to determine what should be done, rather than a prescriptive flow of activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*78qjfvmXDgPXYWHbPjI91A.png" /><figcaption>The updated SEEK UX Design Process.</figcaption></figure><h3>Design principles</h3><p>These aren’t the “<a href="http://principles.adactio.com/">good design is as little design as possible</a>” type design principles but more principles that designers should adhere to when deciding what they need to do to get the job done.</p><h4>1. Know the user</h4><p>In order to be the voice of the user, the UX designer must have an intimate understanding of who the users are, coupled with their goals and motivations. Uncover their current ways of working and work with users to create, test and validate designs.</p><h4>2. Understand the problem (or opportunity)</h4><p>Most projects at SEEK originate from analysis done by our Strategy team. They are able to provide a wealth of information about the market, strategic, and operational drivers — particularly at the start of a project. Once a design has been deployed, the designer should ensure that goals have been achieved.</p><h4>3. Know the market</h4><p>What are our competitors doing? What are other sites/services doing well? Are there pre-existing patterns or trends that could be applied?</p><h4>4. Test early and often</h4><p>If you aren’t testing, you’re guessing. Validate thinking at the earliest possible opportunity. And re-test as things progress.</p><h4>5. Ensure shared understanding</h4><p>SEEK has a very collaborative culture. The best results are achieved through creating a shared vision and understanding. The UX designer should ensure that all members of the team have the opportunity to express their views at the right time and agree on the most appropriate course of action.</p><h4>6. Be prepared</h4><p>The majority of the UX groundwork should be completed before inception. The rest should be done in conjunction with the team. The UX designer should have design assets ready for development, and agreed by the team, prior to the start of an iteration.</p><h4>7. Collaborate &amp; critique</h4><p>Engage and consult with the team regularly to obtain input and feedback for your designs. Sketchshops, critique and design wall walks can uncover issues or better solutions. Don’t design by committee but welcome as many ideas as possible.</p><p>There’s an indication of the phases of a project where each principle is important and by checking against these principles, the designer can be more confident that they are doing the right things, at the right times as the project progresses.</p><h3>UX Goals</h3><p>The process defines UX goals for each of the project phases. These goals are the outcomes that the designer should be aiming to reach. Together, the principles and goals are more important than the tools or activities that are used. The designer is essentially free to choose the work that they need to do to achieve the goals.</p><h3>Activities &amp; Engagement</h3><p>Potential activities and consultations further assist the designer in deciding what they need to do and who they should to engage with.</p><h3>Adoption</h3><p>It’s early days for this process at SEEK but we’re confident it will help (particularly new) members of the team to work confidently and productively.</p><p>What do you think? Would a process like this work in your organisation? I’d love to hear about it via a response post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5063a10cc6bf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/seek-blog/a-principled-ux-design-process-5063a10cc6bf">A Principled UX Design Process</a> was originally published in <a href="https://medium.com/seek-blog">SEEK blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>