<?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 Gary J. Anderson on Medium]]></title>
        <description><![CDATA[Stories by Gary J. Anderson on Medium]]></description>
        <link>https://medium.com/@garyjanderson?source=rss-3909e595bd0a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*9xCEaE1ONdofIKcPQRCepA.png</url>
            <title>Stories by Gary J. Anderson on Medium</title>
            <link>https://medium.com/@garyjanderson?source=rss-3909e595bd0a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:58:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@garyjanderson/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[Managing Design Capacity with Transparency]]></title>
            <link>https://medium.com/university-of-washington-hcde-alumni/managing-design-capacity-with-transparency-371dafef70d?source=rss-3909e595bd0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/371dafef70d</guid>
            <category><![CDATA[design-management]]></category>
            <category><![CDATA[resource-management]]></category>
            <category><![CDATA[ux-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-manager]]></category>
            <dc:creator><![CDATA[Gary J. Anderson]]></dc:creator>
            <pubDate>Thu, 30 Jan 2020 07:32:46 GMT</pubDate>
            <atom:updated>2020-02-01T21:44:05.757Z</atom:updated>
            <content:encoded><![CDATA[<p>Every designer — whether they are fresh to the profession or seasoned for decades — will experience a situation where they have too much to do with too little time to do it. Some of this is normal. Sometimes this can even be a <em>good</em> thing; it can force judiciousness or generate constraints that lead to ingenuity. Too much of this though, only serves to burn people out, reduce design quality, and makes your job a nightmare.</p><figure><img alt="Tired designer looking at computer screen. It is late night, as can be seen via the moon outside the window." src="https://cdn-images-1.medium.com/max/1024/1*JK_GqWmquBXc0uD5l5CuTg.png" /></figure><p>Here is the good news: I believe wholeheartedly that repeated patterns of overwork need not happen, and I’d love to share how you can create a structure to minimize these problems.</p><p>But first, some context: The story I share below is regarding a design manager role for a team of nine designers, supporting a portfolio of 15 products/product areas and three major partners (i.e.product management/development orgs). During the time in question, our team was championing a major design language update, several new products were entering the portfolio, complaints were erupting regarding the volume of work, and we were temporarily missing two designers due to a departure and a leave of absence.</p><p>Something needed to change, and that is when we created something like this:</p><figure><img alt="A spreadsheet showing products, suggested resourcing, current resourcing, resource deficit/overage, and assigned designer." src="https://cdn-images-1.medium.com/max/1024/1*h_0xxLCQSMvWIqx7w-EFGg.png" /><figcaption>Design Resourcing Spreadsheet — Version 1 Sample</figcaption></figure><p>This simple spreadsheet listed each product (or product area) we were supporting, the name of the designer who was working on each product, the volume of time the designer was spending to support the product (current resourcing), and our initial guess on the amount of design support that was <em>realistically</em> needed to support the product (suggested resourcing).</p><p>This isn’t anything new. In fact, some might consider this quite generic — especially if they are a well-trained Product Manager or Product Owner. However, the benefits from this approach were quite noteworthy:</p><figure><img alt="Image of a beaker filled to a line which reads “30 hrs.”" src="https://cdn-images-1.medium.com/max/300/1*AnVxwVX_e8h0-O5ZZM65HA.png" /></figure><p><strong>It set a baseline of expectations for how much design work was created by each designer. </strong>Once you write down “30 hours per week, per resource” you’ve set a stake in the ground… “if we assign this designer half time to your product, you get 15 hours of design a week.” Why 30 hours? Because 10 hours are reserved for admin (email, team meetings, or broader organizational goals), and we want to accurately estimate all work — including non-design work — that is being handled by each person. Doing this puts us in a position to support improved work-life balance.</p><figure><img alt="A figure with the label “0.5.” This is followed by the word “or” and then another figure with the label “1.0.”" src="https://cdn-images-1.medium.com/max/300/1*mZDOa6mhRZsbB5UUcMa20Q.png" /></figure><p><strong>It allowed us to get honest about the volume of support needed for a product, identify designers working over capacity, and show gaps of support. </strong>When talking with partners, we worked together to reconcile, and then document, their view of what was needed to support their products. Since my team supported multiple partners, this provided transparency for how resourcing and support was allocated over the full portfolio.</p><figure><img alt="Picture of a scale weighing a beaker mostly filled with water. The scale reads “30 hrs.”" src="https://cdn-images-1.medium.com/max/300/1*Ag_Dnkd4baTMPhpc3rIlLQ.png" /></figure><p><strong>It created trust. </strong>Since partners/leaders could now see EXACTLY what each resource was doing, there could be no suspicion of withholding resources or allocating resources inappropriately. Of course, the accountability here on our side was that they had the right to validate our allocations with their teams: “<em>X designer is allocated at 50% — are we getting at least 15 hrs of design support each week?</em>” Their ability to openly confirm our allocations, and our consistency in meeting those expectations, is what validates their trust.</p><p><strong>It allowed us to create boundaries and regain control of our capacity. </strong>This last one is the most critical benefit… and also the hardest and most sensitive to execute: it put us in a position to say “no.” Because we had established an honest accounting of their needs AND our available resources, and we had previously agreed that we wanted to support effective work/life balance, we could now say something like this: “<em>Based on your identified needs, we are approximately 3.5 resources short of what is needed to meet such demands. Team members are stretching to try and meet those needs. However, this is ineffective and we are beginning to burn people out. This cannot continue. Let’s prioritize the portfolio of needs, and let’s talk about what we will no longer support, or for which we will put support on hold, to get us back to an appropriate workload</em>.”</p><p>And then we reduced demand by 3.5 resources and lived happily ever after, right?</p><p>Wrong. It wasn’t that easy. Comments and suggestions rang forth:</p><p><em>“What if we split this designer 25% here, and 25% there…”</em></p><p><em>“What about you, design manager, stepping in to do some direct product support?”</em></p><p><em>“Maybe we were wrong… maybe product area Y doesn’t need that much support…”</em></p><p>Thanks to our preparations, each of these attempts to reconcile gaps in a way that would have hurt quality or capacity could be addressed unemotionally:</p><p><em>“Sure, we can split the designer four ways, but that means you will be getting seven and a half hours of design support for each product area per week. Are you ready to incur the impact to your timelines? Are we ready to incur the lost efficiency and focus?</em></p><p><em>“I (design manager) cannot step in to provide design support — my time is needed to manage and guide the team. Besides, if this is where we are, then it only reiterates that we are under-resourced and we are making short-term trade-offs for the well-being of our long-term future. None of us want that, right?”</em></p><p><em>“Okay… so you believe this other product area actually needs less support than identified? Let’s make a note of this and I (or we) can reconcile this with our other partner and gain alignment about the volume of support needed. Once we have confirmed needs, we can then determine if we want to fully support, partially support, or end support for these areas.”</em></p><p>This cycle of negotiation continued for <em>two months</em>, driving escalations and conversations about resourcing at higher levels of leadership.</p><blockquote><strong>Because the parameters of the conversation were well defined, because we were willing to defend our resource limitations, and because we entered each conversation with positive intent</strong> <strong>(our goal is to provide effective design services wherever the organization needs them), our resourcing could be approached in a pragmatic, mathematical way.</strong></blockquote><p><em>“We have nine beakers that hold 100 ml each, and we are happy to fill them up with whatever you want…let’s work together to determine how we will fill them in a way that is best for our business.”</em></p><figure><img alt="Picture of a pitcher with liquid. A “Wait” sign is preventing the pitcher from pouring liquid into any of the 9 full beakers." src="https://cdn-images-1.medium.com/max/1024/1*b_H31rwM47ovwkDjfxo63w.png" /></figure><p>The outcome? We received support (and budget!) by leadership to add two new designers to the team — and it wasn’t done with begging or pleading. Again, it was an unemotional management exercise.</p><p><strong>EPILOGUE</strong></p><p>Fast forward another six months, and this initial spreadsheet evolved:</p><figure><img alt="A spreadsheet with all information found in version 1, along with planning information for future quarters." src="https://cdn-images-1.medium.com/max/1024/1*OGsnDTKOqAtwPgPV5PWHvw.png" /><figcaption>Design Resourcing Spreadsheet — Version 1 Sample</figcaption></figure><p>This next iteration added some new bells and whistles: design need forecasting for the remainder of the fiscal year, resource impacts (e.g. parental leave) that will require planning (or additional resourcing) to address, and average design need across the fiscal year. I use a version of this spreadsheet with my team today.</p><blockquote><strong>The value of creating a transparent design resource tracker is that it provides you with the facts needed to effectively and confidently manage your capacity and the expectations of your partners/stakeholders.</strong></blockquote><p>And what about for those of you who do not manage a team, but who may struggle with managing your personal capacity? This is something that can work for you, too — you are only juggling one resource, less product areas, and (presumably) less partners/stakeholders within which you need to coordinate your activities. One recommendation — especially for those who are operating with less well-defined methods of time management: before you shift to a more concrete method of management, make sure to review your approach with your manager and/or leadership chain to ensure their support before the inevitable hard conversations develop.</p><p>No system is perfect, and I would never profess to be an expert in this space… however, I’ve been thrilled with the positive impact this approach has had on my team and the quality of the design work we produce. So, if you find you (or your team) burning the midnight oil more than desired, give something like this a shot… and by all means, please drop me a line and let me know how it goes!</p><p><em>Illustrations © 2020 by Gary Anderson</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=371dafef70d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/university-of-washington-hcde-alumni/managing-design-capacity-with-transparency-371dafef70d">Managing Design Capacity with Transparency</a> was originally published in <a href="https://medium.com/university-of-washington-hcde-alumni">University of Washington Human Centered Design &amp; Engineering Alumni</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>