<?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 Renn Jarrett on Medium]]></title>
        <description><![CDATA[Stories by Renn Jarrett on Medium]]></description>
        <link>https://medium.com/@rennebago?source=rss-cd227bf0db60------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*b2CB229ofXuGwrYZCc4Sgw@2x.jpeg</url>
            <title>Stories by Renn Jarrett on Medium</title>
            <link>https://medium.com/@rennebago?source=rss-cd227bf0db60------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:28:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rennebago/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[And Back to Designer]]></title>
            <link>https://rennebago.medium.com/and-back-to-designer-a8d8931b6f7c?source=rss-cd227bf0db60------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8d8931b6f7c</guid>
            <dc:creator><![CDATA[Renn Jarrett]]></dc:creator>
            <pubDate>Mon, 10 Feb 2025 17:27:39 GMT</pubDate>
            <atom:updated>2025-02-10T17:27:39.301Z</atom:updated>
            <content:encoded><![CDATA[<h4>My decision to step back away from Design Leadership.</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F26gs6ASI0ExbUXq0g%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fschittscreek-schittscreek-pop-eugenelevy-comedy-26gs6ASI0ExbUXq0g&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExejVmc3BvOXF6amhveXdqb3lpZGd6aDNzam43dDBwNzFsZjB4dmF3cSZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2F26gs6ASI0ExbUXq0g%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/1d077b1c41217e454adf1b0130e0f30d/href">https://medium.com/media/1d077b1c41217e454adf1b0130e0f30d/href</a></iframe><p>In May 2020 I made the decision to take a promotion from Product Designer to Design Manager. I was absolutely ecstatic to lead an incredible growing team of 7 designers. It was a journey I felt excited and ready to embark upon. However, that journey was a short-lived.</p><p>I originally shared my <a href="https://medium.com/@stephanierennj/from-designer-to-manager-f9001b338100">Designer to Manager</a> transition story in the hope to help those who may be at a similar crossroad. In this post, I want to share the story that followed; my move back into a Designer role.</p><p>I won’t have any how-to’s or list of questions to bring to your interviews in this post. This is from a deep desire to be honest about the reality that some of us may face:</p><blockquote>I no longer wanted to be (and perhaps shouldn’t be) a manager — and that’s okay.</blockquote><p>That first year after my promotion, I walked the awkward transition to establish a different relationship with my team. I made an effort to create a routine of bi-weekly 1:1’s with 4 former peers, to learn about their challenges, projects, and goals.</p><p>Alongside this peer-to-manager metamorphosis, I’d taken on new hiring responsibilities. I rapidly started to review applications, resumes, provide insight for a job description for a future researcher role, and help conduct the interviews with potential candidates. Over that year in the whirlwind hiring process, I’d helped expand the team from 7 product designers to 14. With that exciting increase, I had gone from a being a brand-new-baby-manager with 4 reports to a daunting 10.</p><p>Along with growth, the team gained a few additional exciting wins. In a partnership with my design leader, we delivered a message to our partners and stakeholders that spoke to the importance of our design team, the research they conduct, which built recognition for the work the team provides, along with the importance of coverage through the product spaces.</p><p>With this important message, my manager and I partnered together with product, development, and architect leads to collaborate on an artifact that would be referenced and built upon, helping teams understand and capture requirements and deliverables through each phase of the Product Lifecycle.</p><blockquote>I felt this huge push delivered the importance of our teams’ value, skillsets, and research efforts. It was something I’m still proud of today.</blockquote><p>That said, with the interviews and value prop conversations and preparations, this led to many important presentations. I was presenting ideas not just to my peers in leadership but upper management, as well. That new expectation was absolutely terrifying. On the plus side, this practice helped me hone my presentation skills. Today, I’m able to tell a customer-centric story with much more ease, and identify any areas of fluff that could be saved, thus making your point faster, yet leaving details for questions.</p><p>I found myself in an anxiety-inducing position to be the one to convince upper leadership how and why we needed more designers and a research department. After a few weeks of prep with my immediate leader and sweating during the call with upper leadership, we had some relative success. We asked for 3+ more designers and a start on research role and landed on a few and maybe a research-focused leader.</p><p>Yet through and at the end of these conversations, I found myself drained. I had such high-hopes to make a difference, I truly felt I would be the one to be diplomatic and assertive enough to make a change and improve the environment for future designers. I found that with all the hours of research, editing, and practicing, the result was less than we asked — which, hey, we have to start somewhere right? But I still felt like I had disappointed the team and took it harder than I likely should have.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FfQoIDlLW6A6BAhyev8%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fcbc-schittscreek-schitts-creek-fQoIDlLW6A6BAhyev8&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExbW1yZDdiY3hpOTFmaHRwMzZpOGYwbWtyNm90Mjd3b3czYzAza2ttcyZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FfQoIDlLW6A6BAhyev8%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/956550c1849558c42913602430ea39c1/href">https://medium.com/media/956550c1849558c42913602430ea39c1/href</a></iframe><p>One of the biggest realizations I had during this time as a manager is perhaps the hardest to admit. I had to face the irony of learning I’m a highly-sensitive person, and that I <em>hate</em> confrontation. My initial reaction to conflict is to either avoid it or offer a solution as a suggestion. I quickly learned this wouldn’t always cut it as a leader — Not only did I need to learn to resolve conflict within the team but welcome it.</p><blockquote>Being a manager can sometimes mean constant confrontation, so for me to realize I hated dealing with it, was to realize I hated an integral part of being a leader.</blockquote><p>To be fair to myself, I can handle certain types of confrontation. For example, a disagreement on the direction the project should take. I’ve found these situations can be cleared with direct communication on concerns, questions, and reframe the discussion back to original requirements and any research outcomes. Then by the end of a simple call or meeting, each participant leaves understanding the decided direction, desired outcome, and next steps.</p><p>The type of confrontations I’m talking about are can be more difficult to deal with, and quickly can get personal and lead to contentious energy on the team, if left unchecked. These were the conversations that left me feeling dejected, exhausted, and often times completely lost on what to do next.</p><p>There are times as a manager you need to have direct feedback with reports, of course. It’s something I was aware of and understood the job requirement. I’d envisioned myself able to observe my team handling projects, lead efforts on their own, and handle their own conflict, and if something falls off, I felt confident enough to ask about a deadline or method of communication that could be delivered. Often, feedback like this is received, especially if I worked with them in conversations, more of a coaching technique and watched them use the advice and see for themselves how it may help or not.</p><p>Additional coaching was how to prepare people for a big part of careers; promotions. This was something completely new and difficult to handle, for myself. I had to understand and help define the promotion process and carefully and clearly deliver role expectations by level, so the team had a method to understand each position and whether it was a move for them or not. Along with this, once a report expressed interest in moving up, I then had to take time to evaluate performance, attitude, and their current state of their skillsets to help coach them on where to go and how to improve.</p><blockquote>This was a part of management I quickly realized I felt uncomfortable with. Passing judgement on how good or not someone is for a role they want? Yikes.</blockquote><p>This piece of the job also became extremely difficult when feedback was given to someone on ways to improve a skillset and was met with disagreement. That’s when I landed myself in the tough spot to assertively explain the role expectations were not being met yet, then to continue being pushed back on and challenged as to why that wasn’t true.</p><p>Again, when you hate confrontation, this part sucks.</p><p>I’d gone from collaborating with my team and partners in order to deliver designs to a role that dealt more with people and their personalities, including a few egos on the team our with other leadership.</p><p>In that manager role I had to learn I can’t simply avoid or ignore a personality-type I don’t get along with, whether a direct report or another partner I work with daily.</p><p>One particular example still makes my head spin when I think about it. I had a co-worker that was fun, inviting, yet could be difficult to collaborate with on projects. I’d noticed at times that insight or critique quickly led to defensive conversations with other designers.</p><p>In the manager role I experienced the perspective shift with their strong defensive responses. I’d gotten into a habit of creating detailed 1:1 notes to help guide conversations, ensuring topics are addressed and time given to them to discuss what they need. For more difficult conversations, I started getting even more detailed and providing myself scripts to prepare.</p><p>I get on topic then quickly it felt my brain freeze in the moment confrontation began. I’d even captured their responses to make sure I could process the full conversation, reflect, and follow-up. Yet with every point and example, I met a wall, refusing to acknowledge or respect the feedback. Perhaps if I’d simply said <em>“Hey, you can’t just be a dick to your teammates, or me. There’s ways to have conversations with each other and that ain’t it,”</em> then maybe it would have been heard, but I digress.</p><p>Looking back, I understand there were so many factors that fed into the swirl of disagreement that was created. The mixture of going from peer to boss, questioning that authority, to knowing in my gut that this person could be a sly jerk to work with. As I was a new manager, I was coached on coaching the behaviors that needed attention almost out the gate. Even with all the preparation, notes, and advice from other managers, I was completely drained at the end of each day.</p><p>Being a manager meant possibly dealing with more of these strong egos daily, and knowing how much they drained me, I realized I didn’t want to do it anymore.</p><p>. . .</p><p>I felt myself in a constant struggle between two sides: The designer that wanted to make an impact, to make a change, to do right by my design team; and the design leader who had expectations from upper management to fulfill certain quotas or metrics I’d yet to wrap my head around and understand the drive behind, while delivering a message or expectation to the team when it was still being figured out, all while swirling within a tumultuous time of change in the company.</p><p>Towards the end of that first year, I was tired, cranky, and felt a deep pang of regret watching the new designers work on exciting new projects. I could envision the conversations and research planning they could do with each other and felt excited for them. That excitement quickly sizzled out as I had to turn around and log on to a 1:1 I had been nervous about for an entire week.</p><p>So what the hell am I trying to say with all of this? That I hate confrontation and can only handle it when I’m in or leading a design project; but not juggling a multitude of personalities and their challenges? Honestly, probably a bit.</p><p>Maybe I realized that with my sensitivity I was trying to take on more than I anticipated. I was taking on multiple humans’ emotions and griefs as my own, which in turn, quickly burned me out. I strive to provide a safe space for friends and even coworkers, I greatly value a place where one can be vulnerable, with no judgement, and get what they need off their chest. I thought I would excel as a leader with that ability, yet in practice, it meant taking on all of their woes as my own. As a designer and peer, it’s more fruitful for me to listen and provide a space when I know I don’t have the be the one to solve it for them, as their manager.</p><p>I grew weary balancing between the issues of those who just wanted to do good work and attempting to not be bullied into driving towards the (sometimes unreasonable) expectations from upper leadership — while still trying to deliver those expectations to them.</p><p>I appreciate good leaders and managers, the ones that provide that safe space while still being able to help you problem-solve and step up when you need backup. I appreciate them now, when I get them, more than ever, after my own attempt to be one of them.</p><p>I may feel like I failed on some level, but I celebrate being self-aware enough to know I needed to step back.</p><p>I’m happy to made the decision to be a designer again. I can say I feel lighter and happier contributing to a team and leading in other ways that feed into my strengths.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8d8931b6f7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Empathy in Teams]]></title>
            <link>https://medium.com/ncino-design/empathy-in-teams-b78e8ac42b95?source=rss-cd227bf0db60------2</link>
            <guid isPermaLink="false">https://medium.com/p/b78e8ac42b95</guid>
            <category><![CDATA[working-together]]></category>
            <category><![CDATA[teams-and-teamwork]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Renn Jarrett]]></dc:creator>
            <pubDate>Mon, 04 Jan 2021 18:23:33 GMT</pubDate>
            <atom:updated>2021-03-08T16:15:23.973Z</atom:updated>
            <content:encoded><![CDATA[<h4>Beyond our inner design circle</h4><figure><img alt="brain plus heart graphic, symbolizing empathy" src="https://cdn-images-1.medium.com/max/1024/1*4Dbp7jtZu3bLXw7lbECJzw.jpeg" /></figure><p>Empathy as designers has always been a driving factor in the way we build our understanding of users’ problems. We take pride in our empathetic sides to avoid making assumptions and instead ask,</p><ul><li><em>Who will be using this?</em></li><li><em>What have customers said about this?</em></li><li><em>What pain points do they have within their process?</em></li><li><em>What is the real issue we’re trying to solve?</em></li></ul><p>As designers, we have the ability to maintain a view of the root of the problem we’re solving as well as the needs of users. We get the gold medal in exercising empathy for them to understand the reasoning behind their behaviors in a way not many others can. This is not only our job but our passion.</p><p>Let’s look at how this works outside of our inner design circle and within our broader teams.</p><h3>Our Teams</h3><p>Take a second and think about who you work with throughout a typical week. It might be other designers, engineers, product owners, project managers, writers, QA—the list goes on and will be different for every organization.</p><blockquote>No matter how our teams are built, empathy should extend to the roles we interact with, daily.</blockquote><p>Extending our understanding to our coworkers is incredibly important when it comes to building work relationships and trust between roles. Our teams have diverse backgrounds and experiences so it’s natural to have some conflict or debate. Nurturing these working relationships with empathy can foster a healthy collaborative environment with multiple valuable perspectives.</p><h3>Lend an Ear</h3><p>Step away from your tasks for a moment and identify the needs and interests of the other roles you’re working with.</p><p>Think about the mindset of the first person you interact with when you walk away from your standup. Maybe it’s the PM you‘re kicking off a new project with, or maybe it’s a copywriter. What are their needs and wants throughout a project for this role? What do they require to accomplish their tasks? What would it be like to work in their role for a day? The things you expect other roles to understand about your work are the same things they desire from you.</p><h3>In Practice</h3><p>It’s easy to discuss needs and goals in theory but what does this look like in practice for designers? Whether you sit down one on one with someone or listen to a group of people on a panel, creating this habit to listen will develop the ability to see things from another person’s perspective — much like the way we design for users. Here are a few methods to build empathy with other roles.</p><h4>One on Ones</h4><figure><img alt="Two smiling faces graphic" src="https://cdn-images-1.medium.com/max/1024/1*odTOGdBXkBmnCv2sfO_O_g.jpeg" /></figure><p>A great way to open the floor with someone is scheduling some time with them one on one. These sessions can be kept casual and open, but keep a list of questions you want to ask them:</p><ul><li><em>What does your day-to-day look like?</em></li><li><em>What does your typical sprint look like?</em></li><li><em>What’s the most stressful part of your job?</em></li><li><em>What are things I can do as a designer to help you or make your day?</em></li></ul><p>Have your list of questions handy to keep the conversation moving while maintaining an organic flow of conversation. If you already have a good working relationship this act will deepen your understanding further and enhance your relationship.</p><p>For an extra challenge, try scheduling a one-on-one empathy session with someone you don’t know very well, or better yet, someone with whom you don’t have the best chemistry (yet). Maybe you and a product owner or engineer don’t always agree on projects, or you forget to include each other in important conversations, resulting in a bit of awkwardness.</p><p>Reaching out is the first step to begin improving this relationship. Start the conversation by stating your goal: to partner with them and multiple roles and improve your working relationships and understand each other&#39;s needs.</p><p>From there, let the conversation flow, keep your questions handy, and listen. If this is a tense working relationship, the act of reaching out will not be a gesture wasted, but one that will strengthen your understanding of each other.</p><h4>Empathy Panels</h4><figure><img alt="4 face graphics in a circle, symbolizing a group" src="https://cdn-images-1.medium.com/max/1024/1*m9y5-h8FrAgFvzRpZA_eqA.jpeg" /></figure><p>At nCino, we hold Empathy Panels to give insight into other roles’ day to day, needs, and goals. Various roles across the company answer questions such as:</p><ul><li><em>What gets you out of bed in the morning?</em></li><li><em>What keeps you up at night?</em></li><li><em>What is one thing you wish others understood about your role?</em></li><li><em>When is the busiest or most stressful time of the release for your role?</em></li><li><em>For someone in your role, what could someone else do to make your day?</em></li></ul><p>The questions could be the same or similar to a one-on-one session. An empathy panel is beneficial to get a group of varying roles, including design, to answer these questions and discuss and discern other peoples’ needs together.</p><p>If you don’t have an empathy panel at your company yet, consider starting one. Reach out to a product manager, engineer, or a writer you work well with to start the conversation and consider:</p><ul><li><em>Who needs to be included in this panel?</em></li><li><em>What questions will we ask?</em></li><li><em>What format will we start with, IE a survey or group discussion?</em></li><li><em>How can we message this beyond the group?</em></li></ul><p>You’ll be amazed at how willing people will be to speak up, especially when it relates to their job. With a group started, provide these questions ahead of time then allow the discussion to unfold. These sessions can cultivate valuable feedback across roles which can then be communicated to your respective teams.</p><p>The discussions alone are incredible but when left to a small group, they can easily become an echo chamber. After these discussions are kicked off and feedback is flowing, the next crucial step further should be to relay the conversation to your teams and department.</p><p>While it can be close to impossible to get a huge department together to discuss their jobs and day-to-day, an empathy panel can provide a forum where representatives for various roles can speak for each. For example, our Product Development and Engineering department at nCino include well over 500 people (and growing), with multiple scrum teams within portfolios. These empathy panels are beneficial to open the conversation for all roles that contribute to the bigger picture of the department and company as a whole.</p><h4>Retrospectives</h4><figure><img alt="3 faces representing three topics in a retro: what went well, what didn’t go well, and what needs improvement." src="https://cdn-images-1.medium.com/max/1024/1*NgSfQOhZMq8aYL5i7ayGOA.jpeg" /></figure><p>Retrospectives are a common ceremony agile teams practice. These ceremonies improve communication between teammates, enhance motivation, and allow others to be heard. This same format can be utilized by designers and developers, designers and PMs, and any other roles that work together on a regular basis.</p><blockquote>Retrospectives open the door for better communication and can help frustrated teams become more collaborative.</blockquote><p>From a design perspective, you may have pinpointed places in your process that need improvement: designer to engineering handoff, communication with PMs, etc. Once you figure out what needs to change, you can share that need with the goal to improve and strengthen collaboration together.</p><p>For example, consider designer to engineering handoff, a common area for improvement on teams. Ask each other:</p><ul><li><em>What did we do well last release?</em></li><li><em>What needs improvement from the designer’s perspective?</em></li><li><em>What needs improvement from the engineer’s perspective?</em></li><li><em>What pain points do we deal with when sharing design system specs now?</em></li><li><em>What are ideas to improve communicating design system requirements?</em></li></ul><p>Work together to come up with a list of questions to bring to the table. Treat this retrospective just like any other with a board to capture thoughts, feedback, and ideas. Specifically, with the designer handoff process, there will be plenty of ideas to improve and create an efficient workflow for all involved, so be ready to capture them.</p><h3>Open Up</h3><p>Conflicts and debates will always occur at some point. When they do, take a step back and consider the root of the problem. It could be the pressure of a deadline, demanding tasks, communication styles, different usage of tools, handoff process, or even trust.</p><p>Designers excel at solving problems for users. Flexing that same empathy muscle for our teams strengthens our communication with and understanding of our teammates. Your empathy-building methods may look different for each situation. When we disarm ourselves and open up conversations with our teammates, we truly partner together to understand each other, enabling us to build stronger working relationships and better products together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b78e8ac42b95" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ncino-design/empathy-in-teams-b78e8ac42b95">Empathy in Teams</a> was originally published in <a href="https://medium.com/ncino-design">nCino Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Designer to Manager]]></title>
            <link>https://medium.com/ncino-design/from-designer-to-manager-f9001b338100?source=rss-cd227bf0db60------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9001b338100</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[career-journey]]></category>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Renn Jarrett]]></dc:creator>
            <pubDate>Wed, 29 Apr 2020 17:55:59 GMT</pubDate>
            <atom:updated>2021-03-18T20:28:04.315Z</atom:updated>
            <content:encoded><![CDATA[<h4>My Move from Player to Coach</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3TJxYt1noF5bvvYpwE_fwQ.jpeg" /><figcaption>Image by <a href="https://unsplash.com/@dsmacinnes">Danielle MacInnes</a> from <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>A younger Stephanie dreamed she would either be an art director or creative director. Little did she know, she would end up here — an associate product design manager.</p><p>I have always lead teams, in a sense. Sometimes I led in small ways, like making a final design decision a team would go back and forth on, and other times I took a larger role, such as fine-tuning, testing, and implementing better processes for the team so we could collaborate better with engineers, work faster, and nurture a confident design voice.</p><p>Still, when presented with the opportunity to step into an official management role, I paused. If I was going to make this change, I had to ask myself a lot of hard questions:</p><ul><li><em>Why</em> do I want to become a manager?</li><li>What is my motivation to become a design leader?</li><li>What would my leadership style be?</li><li>Where do I want to take the team?</li><li>Am I <em>really</em> going to enjoy all these meetings? Let’s face it, there’s gonna be more.</li><li>Will I miss being in the weeds, finding solutions for complicated scenarios?</li><li>Will I be able to handle conflict well?</li><li>Will I miss design?</li></ul><p>There are tons of articles and books on what it’s like to transition from design to management, other career paths, and what being a manager is really like. I did my research and dove into these resources. <a href="https://medium.com/u/b8a4e5ae7490">Julie Zhuo</a>’s book, <em>The Making of a Manager</em>, became my bible as I made notes, highlighted passages, and reread chapters. All to get my final answer:</p><p><strong>Yes. I want this.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VLovskDv2d5K_vsU3ETJzw.jpeg" /><figcaption>Notes from my bible, also me completely overpreparing for the interview</figcaption></figure><h4><strong>Why I said yes to the position</strong></h4><p>I love seeing teams thrive. I genuinely enjoy being a part of making that happen by building an understanding of what process works best for our team. Being in a product-focused company like nCino, we are all motivated by the same goal, and learning how to best cultivate the growth and direct the culture of the team was something I wanted to do.</p><blockquote>My biggest motivation is the confidence of the design team.</blockquote><p>In the design world, it’s common for designers to feel left out of the big conversations, or deal with clients or agency owners that treat us like mockup churning machines. These are taxing situations that make it difficult to break the designer stereotype and become the design evangelist in those situations. I’ve been there and I understand the heaviness that comes with dealing with those situations. It’s heartbreaking to witness, and something I greatly empathize with. I’ve felt deeply discouraged in these same situations and watched other designers feel their inspiration diminish or their passions completely disappear.</p><p>As a result, I realized one of my motivations is to encourage my team and help them avoid those pitfalls. To encourage them to speak up and fight for good design, knowing and believing their voice matters.</p><p>Ultimately, I want to take the empathy I have for our users and extend that to my team and colleagues. I understand how important it is to build trust with your team, to be able to talk openly and freely about what drives and motivates me, and even what’s pissing me off that week. I want to provide that same environment to build trust and confidence in a rockstar team of designers.</p><h4>Can I deal with the hard stuff?</h4><p>That was something I really needed to consider. How would I handle conflict? What if a designer doesn’t get along with another colleague? How would I handle someone coming to me asking for a promotion or raise that we don’t have in the budget yet, or they’re not ready for? Coming from the designer position and having an environment where I raise all my concerns to my manager, would I be comfortable when people start to raise those very same issues to me?</p><blockquote>Admittedly, the hard stuff sounded scary and awkward.</blockquote><p>Sure, I’ve listened to teammates share discouragement and issues they want to fix. I’ve even helped solve a few problems by testing a new process or simply offering my own experience as advice. It becomes a whole new realm when your peers, now your direct reports, turn their eyes and ears to you for solid input and solutions.</p><p>Eventually, I realized that that’s what will help me; the fact that I’ve been in the trenches with them. I’ve experienced the same designer frustrations and worked out new suggestions and solutions. I think back on the advice my manager gave me in those times and the results that followed. That’s what made me more comfortable with the hard, awkward stuff.</p><h4>Will I miss design?</h4><p>I was pretty happy designing alongside an awesome team of designers, working out complicated workflows, and building an understanding of use cases for various roles in the banking industry. I enjoyed the complex combination of facilitating meetings and communicating with the customers and team members. I loved seeing our hard work and designs come to life and getting kudos from customers.</p><p>So will I miss design? Sure, at first, but moving into a position where I can help ensure the team has all the tools they need, evangelizing design to the company, and hiring the right people to keep our team of rockstars vibing, seems just as fulfilling, if not more.</p><p>I’ll miss the design process initially, but I’ll still be around to join the critiques, watch discussions in our slack channels, and weigh-in as needed. When I need a creative outlet, I have other options, such as drawing, painting, or freelance.</p><h3>After my questions to myself are answered</h3><p>I took a long introspective look at myself and my goals before reaching my answer. Doing so made me realize my true motivation behind taking this next step in my career.</p><p>Next was prepping for the internal interview.</p><p>The process seemed simple; I expressed my interest in the position and my manager and I continued working together on expectations. We discussed what I should read and what I should prepare for, including what kind of questions to expect during my interview.</p><p>I should note that quite a bit of this preparation and the actual interview happened during the COVID-19 pandemic, which brought up a whole new round of questions:</p><ul><li>Am I only this confident right now because I’m remote and not in front of actual people?</li><li>Will I come across confident in the video conference then fall flat in person when we get back to the office?</li><li>How can I truly judge the reaction if I get the job through video? Will the team really be happy about it?</li></ul><p>I was genuinely worried about this until the actual interviews started. It was two panels of people, then two one-on-one sessions with VP’s. After a brief moment of awkwardness, I sank into the conversations and felt comfortable talking about my goals, motivation, and answering the questions thrown at me—even the hard ones.</p><p>As someone brand new to the world of management, I had plenty of questions for each group I spoke with. Of all my questions, I realized these were the most valuable things I asked:</p><blockquote>“What are your beginning stories when you first started management?”<br>“What were your challenges and what helped you in your journey?”</blockquote><p>The answers I got were nuggets of advice that will forever remain in my bullet journal and stay with me through my first steps into this position:</p><blockquote>“Lean on your peers and instincts. As long as you do it for the right reasons, you’re good.”</blockquote><blockquote>“Get to know your team and build trust with them.”</blockquote><blockquote>“The relationships you build are important, and more often are built in the tough times.”</blockquote><p>Before the interview, I almost expected to have a residual feeling of whether or not this was really for me. In truth, my discussions with everyone gave me a realistic outlook and more motivation to take it on.</p><h3>I accepted the job</h3><p>I got the call from my manager on my day off. He told me all the feedback was very positive and they wanted to offer me the position. Yes, and thank you! After learning the position was mine, I went through the following steps:</p><p>I did the usual process after learning such a big position was mine:</p><ul><li>Stare off into space in a daze from the magnitude of what had just happened.</li><li>Open a bottle of sparkling rosé.</li><li>At random times throughout the night, comment “Oh my god, this is happening.”</li><li>Continue my evening with the aforementioned rosé.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Ky5XMpkfmHTHtr8R-HAkWA.gif" /></figure><p>After returning to work the following Monday, my manager and I synced up virtually on the next steps, as well as responsibilities to tackle now and in the future. We’ve been discussing things like hiring, budget, process, new direct reports, and more.</p><p>As this is written, I’m in a daze about the entire thing off and on and sometimes none of it feels real, though that could be from the pandemic. I’m constantly taking notes, organizing my thoughts on future candidates, planning what to say when things are announced to the team, and what to say when the designers have their first one-on-one with me.</p><p>I’m pleased I took the time to take a deep look at myself, and confront both my own strengths and weaknesses. Getting to this point was a long journey with a few stumbles, and I’m sure I’ll face plenty more challenges in my future. I look forward to learning from them and continuing to take obsessive notes, providing empathy for my team of designers, and building a team I’m proud to lead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9001b338100" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ncino-design/from-designer-to-manager-f9001b338100">From Designer to Manager</a> was originally published in <a href="https://medium.com/ncino-design">nCino Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>