<?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 Stephen McCarthy on Medium]]></title>
        <description><![CDATA[Stories by Stephen McCarthy on Medium]]></description>
        <link>https://medium.com/@loft27design?source=rss-8f93ee455de1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2wpD5PdGvCFj7qfj.jpeg</url>
            <title>Stories by Stephen McCarthy on Medium</title>
            <link>https://medium.com/@loft27design?source=rss-8f93ee455de1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:11:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@loft27design/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[Improving how we approach user research and experimentation across our product squads]]></title>
            <link>https://medium.com/which-product-delivery/improving-how-we-approach-user-research-and-experimentation-across-our-product-squads-786391655383?source=rss-8f93ee455de1------2</link>
            <guid isPermaLink="false">https://medium.com/p/786391655383</guid>
            <category><![CDATA[design-management]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-leadership]]></category>
            <dc:creator><![CDATA[Stephen McCarthy]]></dc:creator>
            <pubDate>Wed, 01 Nov 2023 23:04:03 GMT</pubDate>
            <atom:updated>2023-11-01T23:04:03.475Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Venn diagram — user needs on the left, business needs on the right — they overlap to create good things in the middle" src="https://cdn-images-1.medium.com/max/1024/1*zHmLoNwz_eEWbau3ss0BBw.jpeg" /><figcaption><strong>Good user research addresses both business and user needs</strong></figcaption></figure><p>In the Which? Product &amp; Technology department we have approximately 15 product and platform squads who design, build and run various parts of our digital estate. In this post I share some tactics and insights on how we’ve improved user research and experimentation processes across these squads.</p><h3>Understand where you are at</h3><p>In order to know where and how you need to improve, it’s important to know where you are at. At Which? we had the catalyst of a department-wide training day delivered by <a href="https://www.svpg.com/">Silicon Valley Product Group</a> where we could ask everybody the question — ‘How many of you have engaged with users over the last 3 months’. We were able to see straight away that we had a problem regarding the lack of wider team/discipline involvement in research activities.</p><h3>Set some initial output targets to enable pace</h3><p>Many of our teams have recently completed big migration projects and needed an operational reset when it came to approaching research and experimentation. We decided it was useful to set some arbitrary but stretchy targets around the amount of experimentation/testing we wanted to see over a period of time. In this case we suggested 10 experiments a month, per squad. An experiment could be anything from unmoderated usability testing of a prototype as part of some discovery research, to A/B testing a big new feature on the live site. We realised the risk of potential vanity metrics, but targets like this helped set some pace.</p><h3>Create a structure that enables alignment and clear prioritisation</h3><p>We have a relatively small but talented team of 6 user research and experimentation/CRO specialists who all work really hard. Rather than prioritising research and experimentation initiatives across all squads in the round, we enabled our specialists to have more coherent research and experimentation ownership over multiple (related) squad areas. This allowed our specialists to work more closely with squad leads to align and prioritise work across related squad initiatives early, informing our OKR setting process. This is leading to a ramping up of research activity across squads, and avoidance of duplicated effort. This ultimately seems like an obvious thing to do — but we had only recently added headcount to the team and that gave us the ability to have this more balanced squad ownership model.</p><h3>Make the work you are doing visible</h3><p>Visibility is important, it not only shows the hard work being done, it also gives people a better chance to get involved with research initiatives that are in flight. So we created and circulated a User Research Dashboard that highlighted in-progress and recently completed research initiatives. It gives a high level overview of the research intentions of each strand of work and how to get involved. We also made research and experimentation updates a much more permanent fixture of our weekly squad check-ins and we ran a department wide all hands focused purely on research methodologies.</p><p>We’re also looking to better contextualise our user research/insights archive. We’ve got a lot of historical research that sometimes gets forgotten, so we’ve been thinking how we can give this work more prominence in our day to day decision making so we avoid duplication of effort. The holy grail is to create an easily accessible archive of insights that helps us to:</p><ol><li>Identify gaps in our knowledge</li><li>Identify themes across research</li><li>Identify what we can focus on for discovery in the short, medium and long term</li><li>Avoid unnecessary duplication of research</li></ol><h3>Encourage involvement</h3><p>Encouraging involvement with the research process across all levels and disciplines is important. At the <a href="https://www.gov.uk/government/organisations/government-digital-service">Government Digital Service</a> (GDS) they have a mantra that everyone should be involved with user research at least <a href="https://govdesign.tumblr.com/image/142784324568">2 hours every 6 weeks</a>, so we took that as an initial ballpark metric to work with across everyone in the department — from Junior engineers to the CPTO. Getting involved can mean viewing user interviews first hand, to being part of analysis sessions.</p><h3>Coach others</h3><p>This goes one step further than above. When operating in a lean team environment it’s important where appropriate to give others the skills that will enable teams to test and learn fast. Coaching designers to run some of the evaluative research themselves, or coaching others to conduct quality analysis and synthesis of research outputs are examples of this in practice. This enables us to focus our user research and experimentation specialists on more complex or strategic tasks.</p><p>When hiring our user researchers we knew the ability to coach would be a crucial element of the job. This is a facet of the job that takes time, thought &amp; skill, and it has played a huge part in our ability to ramp up research across squads. We knew our designers would need a lot of focused support in this space and this has proven to be an important part of the user researchers role.</p><h3>Join-up across the organisation</h3><p>At Which? we are fortunate to have various research, data and audience insight specialists situated across different parts of the organisation. Wherever possible we’ve been relying on those teams for existing insight and data so we’re not needlessly repeating work or generating insights we already have. We meet regularly to discuss research priorities and align where we can for optimal operational efficiency.</p><blockquote><em>“We’ve never felt closer to the User Research team from my point of view, and that’s because you’ve been so supportive in pushing more collaboration”</em> — Audience Insight team member</blockquote><h3>Take time to assess the impact of new processes (and iterate)</h3><p>After a quarter working in this new way we held a retrospective within the Product Design and User Research (PDUR) team. The user researchers also held various sessions within the squads to gather feedback over the course of the quarter. The aim was to get a temperature check on new approaches and expectations. Broadly speaking people were energised by the better collaboration between disciplines and the pace we were working at, but some folks also felt overwhelmed or too stretched at various times over the period in question.</p><p>All the feedback gathered from these sessions is enabling us to have better conversations around topics like headcount prioritisation and what will enable us to move faster &amp; smarter. The ultimate aim is to deliver outcomes that work for our users and the business, and these recent changes are enabling squads to be more user-centred and focused in their approach. Squads are getting better at telling the story from initial insight through to build — creating shorter feedback loops. By maturing in how we think about user needs — we are better able to solve for them.</p><p>Thanks for taking the time to read this post. Every organisation is different, but I hope some of what I shared here can help you evolve your processes to enable better user research and experimentation outcomes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=786391655383" width="1" height="1" alt=""><hr><p><a href="https://medium.com/which-product-delivery/improving-how-we-approach-user-research-and-experimentation-across-our-product-squads-786391655383">Improving how we approach user research and experimentation across our product squads</a> was originally published in <a href="https://medium.com/which-product-delivery">Which? Product Delivery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing the Product Design and UX Research team at Which?]]></title>
            <link>https://medium.com/which-product-delivery/introducing-the-product-design-and-ux-research-team-at-which-8d789cef2a04?source=rss-8f93ee455de1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d789cef2a04</guid>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Stephen McCarthy]]></dc:creator>
            <pubDate>Thu, 21 Jul 2022 12:54:06 GMT</pubDate>
            <atom:updated>2022-07-22T15:34:52.072Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="2 team members talking at a table. One has a phone in their hand. There are post-its on the wall behind them." src="https://cdn-images-1.medium.com/max/1024/1*bu1ajMczlX6UkWp4SebJxw.jpeg" /></figure><p>The design, UX and research practitioners that work across the digital products we create at Which? are well established and respected within the organisation. But we’ve recently gone through a bit of a transition within the team that I’d like to talk about, in the hope that it might help other organisations who are making a similar transition.</p><h4>What has changed and why</h4><p>Prior to me joining the organisation back in January 2022 the team was made up of UX designers, visual designers and UX researchers. Generally teams had an embedded UX designer and visual designer — with the UX researchers prioritising work across a number of teams. As we transitioned to a modern agile multidisciplinary squad model over the last few years, we decided to trial a move to more hybrid Product Designer roles. When I joined this trial was just starting and 3 people in my team had moved from UX and visual design roles to being the single product designer within a multidisciplinary squad.</p><p>The core aims in moving to the product designer model were to:</p><ul><li>Minimise unnecessary hand-over within teams and enable simpler communication channels between squad practitioners</li><li>Open up the design process so the whole squad are more involved</li><li>Become leaner in our make-up and improve product/design/engineer ratios within teams to enable more efficient delivery cycles</li><li>Enable more opportunities for capability growth within the design and UX research community</li></ul><h4>What happened</h4><p>The truth is our industry is riddled with interchangeable job titles that don’t mean much to many. But the skill sets (and indeed mindsets) of a UX designer and a visual designer can be very different. We wanted to make sure that our team members were willing and even excited to evolve their capabilities and move into this new role.</p><p>The people undertaking the trial very much embraced the extra responsibility. Generally designers like to learn and be challenged, and moving to a product design role brings different obstacles depending on your design/UX background.</p><p>We know that capability growth is key and needs to be nurtured properly. We wanted to set up in a way that enabled proper capability growth with these new roles. So when I joined we immediately kicked off work building a fit for purpose capability framework that our team could benchmark against. This is enabling us to focus training, coaching and work opportunities more effectively — tailoring them to the individual as they evolve as practitioners.</p><h4>The new set up</h4><p>We now have a product designer embedded in each squad. Some squads — that have a broader remit — have two.</p><p>UX researchers are responsible for strategic research initiatives that sit across multiple squad priorities. The longer term aim is for the UX researchers to also act in a coaching capacity to enable the product designers to do some of the more day to day usability testing and research that enables iterative user-centred development within the squads.</p><p>We are also maintaining specialist visual design, UX design and UX research roles across our leads layer so that they can give appropriate support across the squads and projects where coaching or hands on design/research intervention may be needed.</p><p>We’ll continue to monitor how this new shape is working. As we grow as a team — in both headcount and capability — we’ll iterate as needed to make sure people are happy, doing good work and being challenged. We know our designers and researchers will still have different strengths and we don’t expect people to become unicorn practitioners. We’ll continue to seek both generalists and specialists to shape the overall capabilities of the team.</p><h4>We’re hiring — come work with us</h4><p>We are currently hiring <a href="https://www.linkedin.com/jobs/view/3181486381/?refId=0RWWaelBVxxYIYp2Wp1kzQ%3D%3D&amp;trackingId=48pD5O3e34dxxrlNWJjMwg%3D%3D">Senior UX researchers</a>. It’s a great time to come work for Which? and help people in the UK navigate the ever more complex consumer landscape. The cost of living crisis and broader issues around scamming, sustainability and travel industry chaos are just some of the areas where people really need help at the moment. At Which? you can give that help — in a supportive, inclusive and flexible work environment.</p><p>Feel free to contact me on twitter <a href="https://twitter.com/loft27design">@loft27design</a> if you’d like more info.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d789cef2a04" width="1" height="1" alt=""><hr><p><a href="https://medium.com/which-product-delivery/introducing-the-product-design-and-ux-research-team-at-which-8d789cef2a04">Introducing the Product Design and UX Research team at Which?</a> was originally published in <a href="https://medium.com/which-product-delivery">Which? Product Delivery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first month at Which?]]></title>
            <link>https://medium.com/which-product-delivery/my-first-month-at-which-b4958742aabe?source=rss-8f93ee455de1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4958742aabe</guid>
            <category><![CDATA[new-job]]></category>
            <category><![CDATA[design-management]]></category>
            <category><![CDATA[design-leadership]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Stephen McCarthy]]></dc:creator>
            <pubDate>Fri, 11 Feb 2022 12:47:21 GMT</pubDate>
            <atom:updated>2022-02-14T09:11:58.594Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*laZ1fFQq7C5riV-xcIYk9w.jpeg" /></figure><p>I’ve just finished my first month as Head of Product Design and UX Research at <a href="https://www.which.co.uk/">Which?</a>. I’m really enjoying it so far. It’s a fascinating organisation with a <a href="https://campaigns.which.co.uk/">long history of consumer advocacy</a> dating back to 1957. Which? does some amazing things for the people of this country — pushing to protect consumers across a range of different areas, from online scamming, to fighting for better food standards.</p><p>In this post I’ve tried to articulate some observations from my first month. People often call this the listening phase of a new role. I’ll use my different ‘spheres of influence’ as a lens to frame my experience so far, these include:</p><p>1. My direct team of designers and researchers</p><p>2. Peers in different disciplines across the organisation</p><p>3. The leadership team</p><p>4. Wider industry peers</p><h3>1. My direct team of designers and researchers</h3><p>The design and UX research team I manage at Which? is a lot smaller than in my previous role at GDS. In a way this has been good because it’s made it easier to get to know people. I received a really good onboarding document from the team when I joined. This included introductions to every team member, outlining their strengths and self-identified areas for development. This was valuable as it immediately gave me a sense of the people within my team and where they sit as practitioners.</p><p>Recently the designers on the team have been on a bit of a journey, moving from a UX and Visual Designer model, to a hybrid Product Designer model. I’ve taken over at an interesting point on this journey where we are actively scrutinising the challenges and opportunities moving to this model might bring. A core part of implementing changes like this is bringing clarity over skill and capability expectations. I recognised that this is something I needed to focus on straight away and jump into with the team. We’ve kicked off work to develop a capability framework that will hopefully enable better conversations around career development and pay in the future.</p><p>I’ve been really impressed by the maturity of the team so far and I’ve seen some strong ways of working within the multidisciplinary squads. They’ve been on a long journey of content migration and simplification regarding the publishing platforms used across the myriad of Which? websites and apps. From experience I know that this type of work can be a slog — so I’ve been impressed by the resilience of the team in this regard. They’ve been using it as an opportunity to embed the design system, improve accessibility and improve the web performance of the Which? digital estate. This foundational work will enable us to invest more time into greenfield and experimental work in the near future.</p><h3>2. Peers in different disciplines across the org</h3><p>My role sits on the organisations ‘extended leadership team’, and lives in a part of the organisation called Product and Technology. This is where all our multidisciplinary delivery teams (or squads) sit. A core part of any design leadership role is building relationships with peers across different disciplines. Thankfully I’ve been able to lean heavily on <a href="https://medium.com/@1kevincurtis">Kevin</a> (our Head of Product Management) in these early weeks. He’s brought me up to speed on the journey we’ve been on moving towards a squad model and defining (and refining) useful OKRs.</p><p>As each week has gone on I’ve attempted to theme the introductions I arrange. For example:</p><p>Week 1 — leadership and extended leadership team members</p><p>Week 2 — my direct design and research team</p><p>Week 3 — Product managers and data analysts, etc.</p><p>Obviously it hasn’t worked out exactly like this, but the point is I want to meet a broad range of people and it takes time to do this properly.</p><p>Squad check-ins happen on Thursdays and on the whole they’ve been really engaging. What I’ve found particularly positive is that people from different disciplines present at them. From my experience these types of ceremonies are often left to a delivery or product manager to present a formulaic overview — removing the detailed insights that designers, engineers, researchers and data analysts can bring.</p><p>A great part of working at a truly unique organisation like Which? is that you get to work with people from a wide range of areas, such as: commercial operations, consumer rights policy, member services, journalism and magazine production. Reaching out and building relationships with folks in these areas has been a really exciting part of my first few weeks.</p><h3>3. The leadership team</h3><p>I report into the Chief Product and Technology Officer, <a href="https://medium.com/@rico.surridge">Rico</a>, who sits on the executive leadership team for Which?. Having a direct line into the top of the organisation is really important and removes some of the bureaucratic layers I often felt in government.</p><p>On my 2nd day at Which? I had an hour long chat with our CEO, <a href="https://www.which.co.uk/about-which/company-info/which-limited-board">Anabel</a>. This was great and it immediately gave me an insight into her passion for the organisation. I was also able to give her an insight into my values as a designer. Some key takeaways from our conversation were that she spoke of the need to improve the accessibility of our content, and of Which? being on a journey of ‘modernisation’ rather than ‘transformation’. Transformation is a phrase I’m glad I won’t have to use for a while.</p><p>As my role evolves I’ll undoubtedly become more familiar with the whole leadership team as we endeavour to build a useful, coherent and beautifully designed experience for a more diverse consumer audience.</p><h3>4. Wider industry peers</h3><p>One of my key takeaways from working in government is the importance of building relationships with peers working in organisations tackling similar problems to you. They can be great sources of information and inspiration.</p><p>Over the last few weeks I’ve been reaching out to a number of designers and design leaders for advice and everyone has been really receptive to my questions. I want to say a big thank you to those folks who I’ve spoken to in detail. I look forward to building an even wider peer support network over the coming months. I also hope that I have useful things to say that can support them in their respective roles.</p><p>Another way to influence and engage with wider industry is through being open about the work you are doing and the problem spaces you are grappling with. I’ve been encouraging our design and research team to start blogging more — so expect to see some movement in this space in the coming months. We already have a backlog of great posts in progress.</p><h3>Conclusion</h3><p>I was nervous about joining a new org after nearly a decade working at GDS. I wouldn’t say I had imposter syndrome, but the fear of the unknown is definitely real. In Which? I think I’ve found another organisation that I can be passionate about. Luckily the people I’ve met have been really sound as well. As I always say, ‘Come because of the work, stay because of the people’.</p><p>We’re going to be opening some UX research and design roles soon, so watch this space. Follow me on twitter <a href="https://twitter.com/loft27design">@loft27design</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4958742aabe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/which-product-delivery/my-first-month-at-which-b4958742aabe">My first month at Which?</a> was originally published in <a href="https://medium.com/which-product-delivery">Which? Product Delivery</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good design doesn’t just happen]]></title>
            <link>https://medium.com/@loft27design/good-design-doesnt-just-happen-7602358096e5?source=rss-8f93ee455de1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7602358096e5</guid>
            <category><![CDATA[design-teams]]></category>
            <category><![CDATA[design-culture]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[organisational-culture]]></category>
            <dc:creator><![CDATA[Stephen McCarthy]]></dc:creator>
            <pubDate>Sun, 09 Dec 2018 22:58:42 GMT</pubDate>
            <atom:updated>2018-12-09T22:58:42.105Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Observations on maintaining a strong organisational design culture</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-2qIw0Q2Lzq9_i9KUHb_FQ.jpeg" /></figure><p>A lot of factors are at play within an organisation that hinders or helps good design to happen. Investing effort into maintaining a strong design culture is important.</p><p>For a good design culture to thrive certain things need to be in place. I’ve outlined some factors that should be prioritised by organisations who are serious about promoting a strong design culture.</p><p>Some of these observations can relate to any discipline — but I’m looking at it through the perspective of being a designer (and design manager). Nothing I’ve noted is new or groundbreaking, but the point is these things need to be consistently maintained for design to flourish.</p><h3>Clear direction and vision</h3><p>In the organisation where I work we’re really lucky to have clear and strong design principles that we can stand behind. No matter how confused organisations can get, if you have strong guiding principles they can really bring you through the difficult times and keep you on the right path.</p><p>It’s really important to keep these principles prominent in the mindset of the organisation and make sure new people — especially senior management — have bought into them.</p><h3>An open working environment</h3><p>Designers should be shielded as much as reasonably possible from the internal politics and bickering of an organisation. Every organisation has silos, problems and infighting. People in leadership roles often have agendas. When this starts inhibiting designers it becomes a massive problem.</p><p>For good design to happen it needs to be collaborative, open, and free from the personal agendas and the whims of those in power. Maintaining a culture of sharing work and ideas is really important and should always be a high priority.</p><h3>The right mix of people</h3><p>Work output suffers when people feel alone. Design always thrives on collaboration: designer and writer, designer and developer, designer and user researcher — to name a few.</p><p>Getting the right team dynamics in place isn’t just about having the right roles. It also relies on having an inclusive environment. Great work happens when diverse people with different viewpoints and backgrounds come together to tackle a problem and feel safe to challenge each other.</p><h3>Respect for each others roles and skills</h3><p>Having respect for your colleagues is paramount.<strong> </strong>Blurred role boundaries happen all the time and it’s often healthy to have some overlap. It’s inevitable when people care about the things they’re working on that disagreements will happen. However, you need to be aware of the red lines and be open with each other when you feel these boundaries have been crossed.</p><p>Team relationships are hard and don’t magically just work. Respect and trust is fostered with good team dialogue and proper engagement with what everyone is working on. If you don’t know what certain roles do, invest time in trying to find out.</p><p>When relationships aren’t maintained and nurtured the design output is often weakened. Strained relationships lead to misunderstandings and ultimately to a poorer standard design.</p><h3>People to lean on</h3><p>Everyone needs people they can go to for impartial advice. Someone who isn’t directly involved in your day to day work. As an organisation, try and put community structures in place that allow this to happen more easily.</p><p>A strong design community isn’t just built on talent. It’s built on empathy too. Senior people in the community should be present and approachable.</p><p>I’ve been fortunate enough to have great colleagues who I’ve learned a lot from by just having chats. Sometimes it’s good to just get stuff off your chest and talk about it out loud. Chances are other people have been in the same sticky situation as you have.</p><h3>Time and space to understand the problem</h3><p>Deadlines and constraints are generally good for a designer, but they need to be realistic. Give designers time and space to get a thorough understanding of their users and the context of their work. This means allowing time for proper discovery and experimentation. Don’t just throw stuff over the wall and expect a designer to pick it up and make it work.</p><p>Only when fully informed of the problem space can designers properly contribute. A half baked understanding of the parameters you’re working in can lead to many wasted months designing the wrong thing. This then leads to frustrated designers and researchers who feel their skills aren’t valued.</p><h3>Credit and reward where it’s due</h3><p>Reward isn’t just about money — although that’s still important. When someone does good work tell them and credit them. If someone seems bored and ready for a new or bigger challenge, give it to them. When someone seems like they need help, offer it.</p><p>Depending on the organisation you are in, salary increases and promotions can be a long bureaucratic process. Invest time in making transparent what you expect from designers working at different levels of seniority and be proactive in trying to help them develop their skills and careers.</p><p>—</p><p>The above list isn’t exhaustive. They are just some of the observations formed while helping to build and maintain what I see as one of the strongest design teams around. If you want your organisation to produce good design work — then invest the time and effort into maintaining a strong design culture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7602358096e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Balconies as design components]]></title>
            <link>https://medium.com/@loft27design/balconies-and-design-components-9fb5e509b65e?source=rss-8f93ee455de1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fb5e509b65e</guid>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[balcony]]></category>
            <category><![CDATA[tel-aviv]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Stephen McCarthy]]></dc:creator>
            <pubDate>Mon, 09 Jul 2018 06:46:44 GMT</pubDate>
            <atom:updated>2018-07-09T09:02:38.475Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bYtAoLHX6D2puCYz7kLnwA.jpeg" /><figcaption>Balcony with slit to create better air flow, White City, Tel Aviv.</figcaption></figure><p>I was in Tel Aviv earlier this year and took the Bauhaus tour around the ‘White City’. A UNESCO heritage site of over 4,000 buildings built in the 1930’s in a locally adapted form of International Style architecture. The tour was good and the guide went into some nice details about the nuances of the Israeli output of the modernist movement.</p><p>When these architects moved to Tel Aviv many of them were still learning their craft. Some had studied in the Bauhaus and moved to Israel with relatively little experience. They had a blank slate to build on (it was pretty much desert where Tel Aviv stands now apparently) and they had to put stuff up quick. This was due the the big influx of Jewish people during that period.</p><p>When they were creating these new buildings they were pretty much learning by doing. The temperature in Tel Aviv is hot and dry with very strong sun. Very different to the likes of Dessau where these students learned their trade. Try as they did to design for the heat and scorching sun the architects couldn’t fully understand how liveable these homes would be until they built them.</p><p>Tel Aviv is often called the city of balconies. Pretty much every residential building has (or *had) them. Thinking of balconies as design components it’s interesting how they evolved as the designers gained more experience and pushed to better meet user needs. In the early iterations of International Style homes in Tel Aviv the balconies were often impenetrable for the residents. They were hot and humid and weren’t fit for purpose. In some circumstances the term ‘cigarette balcony’ was coined, meaning they were useless for anything else other than having a quick cigarette on.</p><p>As the architects gained more experience and experimented with different designs they realised what they needed to do to make balconies more habitable spaces. The key was in creating better air flow. They did this by having slits in the balcony below knee level, thus enabling better air circulation around the space.</p><p>Balconies and buildings in the White City can look aesthetically different but the core ingredients for making a habitable balcony space remain the same. You can draw many parallels here with designing accessible components for the web. Sites can look different but the core elements that make them accessible and work shouldn’t be touched.</p><p>Someone I know was recently lamenting how most government websites now look like GOV.UK. The thing is many GOV.UK design patterns have been rigorously tested and are fit for purpose. It’s easy for teams doing similar projects to just copy this wholesale as they know it will do what they need it to do.</p><p>When this work is in the hands of more skilled designers they know they can tweak these patterns in different ways while still keeping the core aspects of the design that make these patterns work for everyone. Whether that’s big click areas, good contrast, clear typography or accessible code. The aesthetics are secondary and will evolve and change as people get more confident in understanding why good design is good design. It’s not just how it looks.</p><p>Just like those architects in 1930’s Tel Aviv, we’re learning as we go. Hopefully making things better for users with every iteration.</p><p>*<em>Because their balconies weren’t useable many residents have simply walled them in in order to get more floor space in their apartment. This is the cause of great upset to the Tel Aviv city planners and architecture historians.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fb5e509b65e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designers as power brokers]]></title>
            <link>https://medium.com/@loft27design/designers-as-power-brokers-403338d79361?source=rss-8f93ee455de1------2</link>
            <guid isPermaLink="false">https://medium.com/p/403338d79361</guid>
            <category><![CDATA[information]]></category>
            <category><![CDATA[understanding]]></category>
            <category><![CDATA[power]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Stephen McCarthy]]></dc:creator>
            <pubDate>Wed, 20 Jun 2018 09:18:06 GMT</pubDate>
            <atom:updated>2018-06-20T09:18:06.992Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*46k0SH0fS2pbCRoUNOE9nw.jpeg" /><figcaption>Flag stating ‘Information is Power — if you understand it’</figcaption></figure><p>I put this flag up in work a couple of weeks ago. It caused a bit of a conversation and people had different interpretations of what it meant. I thought it best to explain the way I intended it.</p><p>The piece initially came about after a workshop I did with the students at Cardiff School of Art and Design on their module called ‘Information is Power’.</p><h3>Stephen McCarthy on Twitter</h3><p>Workshop today with the students @bagcw210</p><p>The concept of power is a complicated thing. It means different things to different people. Often power is treated as a zero-sum game. So for someone to have power or feel powerful the notion is that there must be someone on the opposite side who is being disempowered because of this.</p><p>As a designer in government my role is to give power to those people who often feel disempowered. This might sound grandiose but it’s why I go to work and do what I do.</p><p>If people feel like they understand the information being presented to them — in our case by government — then they feel able to better make a decision about what to do. I’ve seen this time and time again with user research participants, who can go into a session expecting something to be really difficult. When the thing they’re doing turns out to be easy and understandable their demeanor immediately changes and they feel more confident and empowered about the process they’re going through.</p><p>Just giving the information to the user isn’t enough. This empowerment only comes about when this information is given to people in a way that they can understand it. This is hard to achieve and some organisations simply wipe their hands of this second part.</p><p>As designers in government it’s up to us to make this information understandable. We need to redress the balance between the powerful and the disempowered in our society. Fixing impenetrable information is a good place to start.</p><p>Organisations like <a href="https://projectsbyif.com/blog">Projects by if</a> have written extensively on the subject of how we can put power back in the hands of the user. I’d recommend a sift through their blog.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=403338d79361" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning how to lead (or whatever that means)]]></title>
            <link>https://medium.com/@loft27design/learning-how-to-lead-or-whatever-that-means-24af8993e007?source=rss-8f93ee455de1------2</link>
            <guid isPermaLink="false">https://medium.com/p/24af8993e007</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Stephen McCarthy]]></dc:creator>
            <pubDate>Wed, 18 Oct 2017 22:02:05 GMT</pubDate>
            <atom:updated>2017-10-18T22:04:57.005Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4lYGvKkN9wPM3s4jdWVa4w.jpeg" /></figure><p>As I’ve taken on more management and leadership responsibilities my role as a designer has become more complex. These responsibilities are tough, energy sapping, but very important. They help facilitate an atmosphere where you can have a good, happy and productive team. Giving them the space to do great work.</p><p>There are many factors at play that can have a negative impact on these things. Dealing with those factors can be difficult. You don’t truly realise this until you have to face them. These are some of the things I’ve learned.</p><h3><strong>Know when to step in</strong></h3><p>Managing and mentoring other designers is rewarding and difficult in equal measure. It takes a lot of time and emotional investment that isn’t often acknowledged. Perhaps as designers it’s even tougher because we’re naturally empathetic and want to fix and improve things. The ability to adapt your ways of mentoring to different personalities is key to bringing the best out of people.</p><p>It’s important to give designers earlier in their career the space and backing to think for themselves and make mistakes. Making sure they are being rewarded both intellectually and monetarily as they progress is key. The monetary progress can be difficult to implement depending on the type of organisation you are in and the bureaucracy you have to deal with.</p><p>Doing all this while still being a ‘designer’ is a hard balancing act and one that’s difficult to master. I’ve had some creative directors that would undo all my good work and ruin it — just so they could put their mark on it. I’ve had others who trusted me to get on with it and gave me the confidence to improve as a designer. Stepping in at the times when I most needed their help or guidance. These are the things you remember as you take those steps up the ladder and decide the type of leader you want to be.</p><h3><strong>Build your resilience</strong></h3><p>Earlier in my career I lived in an idealist bubble. I felt that everything in my organisation or team should just run smoothly according to how I saw it. I struggled to deal with awkward people or processes. I consistently see younger designers struggling with the same things I struggled with.</p><p>The more experience you gain, the more you realise just how difficult it is to make things run smoothly and keep everybody happy. People won’t always get along and factors out of your control can hinder the work you are doing.</p><p>When things go wrong you need to have the resilience and nous to bounce back. In a leadership role you also have to have the resilience to help your team bounce back as well. This can be emotionally tiring as you’ll lose some good people along the way. It’s part and parcel of the job. During these periods it’s important to stay calm and not make any rash decisions.</p><h3><strong>Ignore the nonsense</strong></h3><p>I realised early on the importance of that person above me guarding my peers and I from the noise. Enabling us to get on with doing good work. As I get closer to being that person I’m starting to realise how hard it is. I’ve worked with some excellent people who have very different mechanisms to deal with this. Some are good at picking their battles and others just have an ability to ignore the nonsense. Over the last while I’ve had to figure out how I can handle this stuff.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24af8993e007" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 CV tips for ‘Junior’ Graphic Designers]]></title>
            <link>https://medium.com/@loft27design/10-cv-tips-for-junior-graphic-designers-b5872c82cc1f?source=rss-8f93ee455de1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5872c82cc1f</guid>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[cv]]></category>
            <category><![CDATA[graphic-design]]></category>
            <dc:creator><![CDATA[Stephen McCarthy]]></dc:creator>
            <pubDate>Mon, 23 Nov 2015 16:50:24 GMT</pubDate>
            <atom:updated>2015-11-23T17:29:59.864Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*K47RqvGE865jPt6rwupbQQ.png" /></figure><p><strong>I’ve sifted through many CVs and see common mistakes occur time and again. I thought I’d share some tips based on this experience.</strong></p><p>A CV should give a concise overview of your competencies and experience. It validates the work you stated you have done and education level you have reached. It’s a doorway to your portfolio, not a portfolio piece in itself.</p><p><strong>1. </strong>Your CV will probably be the first point of contact with a potential employer. Clearly link to your work, including your portfolio, Tumblr’s, blogs or any other sites that may help potential employers understand your design output and thinking.</p><p><strong>2. </strong>Don’t use meaningless buzz words to describe yourself, eg ‘highly creative’ or ‘imaginative’.</p><p><strong>3. </strong>Explain your past job roles concisely and truthfully. It’s a small industry so don’t lie.</p><p><strong>4. </strong>A well designed CV is nicely typeset, has good hierarchy and is easy to read. Don’t overdo it. Keep icons and infographics to a minimum and don’t use garish typefaces.</p><p><strong>5. </strong>On that note don’t use top trump style graphics to say you are 65% proficient at HTML or 9/10 at Adobe illustrator.</p><p><strong>6. </strong>No typos or spelling errors. You can’t expect anyone to bother reading your CV if you can’t be bothered to use the spell check tools available.</p><p><strong>7. </strong>No typographic errors either (show you have some attention to detail).</p><p><strong>8. </strong>You don’t need to state your GCSE or A-level results or that you won a regional poster competition when you were 12.</p><p><strong>9. </strong>The ‘I’m good at making tea’ joke should be put to bed.</p><p><strong>10.</strong> Don’t make it too long. 1 or 2 pages is enough.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5872c82cc1f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The big win for Irish design]]></title>
            <link>https://medium.com/@loft27design/the-big-win-for-irish-design-c9ea90f50c8c?source=rss-8f93ee455de1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9ea90f50c8c</guid>
            <dc:creator><![CDATA[Stephen McCarthy]]></dc:creator>
            <pubDate>Tue, 10 Feb 2015 13:03:56 GMT</pubDate>
            <atom:updated>2015-02-10T14:06:22.479Z</atom:updated>
            <content:encoded><![CDATA[<p>This year Ireland is promoting its design credentials. It’s a good thing. On the back of the (<a href="http://www.pivotdublin.com/bid/">almost successful</a>) push for Dublin to be World Design Capital of 2014, momentum is building for design to be recognised as a core part of the new post-recession Ireland.</p><p>We are an island full of talented designers, crafts people and general creative minds not limited to either of those fields. In a broader context though, we (as a nation) have a narrow-minded view of what ‘design’ is and what areas it can or should permeate. To many design is seen as:</p><ul><li>Furniture and Interiors</li><li>Fashion, Textiles and Jewellery</li><li>Products</li><li>Buildings and Spaces</li><li>Graphics, Packaging and Branding</li></ul><p>Design is not seen as:</p><ul><li>Something for everybody</li><li>A core part of our public/private services</li><li>User-centric</li></ul><p>Design in Ireland (or the discussion of such) feels a bit like it’s something reserved for the middle classes. The Monocle Magazine effect — something we can buy into to show our good taste at dinner parties with friends. It’s the trimmings that makes things a little nicer. We are all guilty of this and that’s fine, up to a point. What isn’t fine is when we think this is where design ends. In general, many people (both designers and users) don’t see that it’s a core part of our everyday lives.</p><p>In the field of Graphic Design many designers are more interested in branding or packaging the ‘thing’, than the actual ‘thing’ itself. This is partly down to the fact that they are often only asked to package the ‘thing’ (whether that’s a brand, product or service), but it’s not the only reason. We as designers have to take some blame for putting our focus in the wrong place.</p><p>Let’s think of this hypothetical situation — Dublin City Council has put out a tender for 2 jobs. The first is to rebrand the organisation — a full, traditional identity roll-out — logos on vans, uniforms, bus stops … the whole nine yards. The second tender is to plan and design the Social Housing Application service on the DCC website.</p><p>The first job sounds a lot sexier, right? I guarantee students and experienced professionals alike would — in most cases — go for the rebranding job. What we really need though is more designers who understand and want to go for the second job, because that’s where the big win is. That’s the design that touches people in the most tangible way. Not the big bi-lingual logo on a Ford Transit.</p><p>The experience should be the branding. Designer’s and service owners need to understand this and push for design professionals to be engaged at an earlier stage of the process. They shouldn’t just be asked to intervene at the end of a costly/lengthy process to package something up and pretend it’s lovely and all works great. It’s not about putting lipstick on a pig and trying to make something fundamentally flawed look pretty.</p><p><a href="http://www.irishdesign2015.ie/">ID2015</a> has some high level government backing. That’s great. My fear though is that what politicians and the public are seeing is a sort of ‘Irish Craft 2015&#39;. A narrow view of design which seems to be skewed towards beautifully crafted, artisanal consumer goods, packaged and sold to the select few who can afford them.</p><p>There is a tendency to think the big, boring stuff is for the politicians, policy makers and big company consultants, not for designers. There are many designers in Ireland who would like to change this. I know some of them.</p><p>We need politicians and those in government positions to see design and designers as something that can have a positive effect and change public services for the good of the people. To achieve this they need to place users at the centre of public service redesign and build design capability across government and local authorities. This way good design can finally get to the people who don’t often engage with it, but really need it. That, potentially, is the big win for the year of Irish design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9ea90f50c8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>