<?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 Julianna Wang on Medium]]></title>
        <description><![CDATA[Stories by Julianna Wang on Medium]]></description>
        <link>https://medium.com/@juliannawang?source=rss-33aa368e6fba------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*I5aZD7EmkHaHDNllPYqU4A.jpeg</url>
            <title>Stories by Julianna Wang on Medium</title>
            <link>https://medium.com/@juliannawang?source=rss-33aa368e6fba------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 06:08:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@juliannawang/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[Kill the Friction: How I Automate Vague Goals into Hard Execution]]></title>
            <link>https://medium.com/@juliannawang/kill-the-friction-how-i-automate-vague-goals-into-hard-execution-6348825b77d3?source=rss-33aa368e6fba------2</link>
            <guid isPermaLink="false">https://medium.com/p/6348825b77d3</guid>
            <dc:creator><![CDATA[Julianna Wang]]></dc:creator>
            <pubDate>Sat, 18 Apr 2026 21:19:54 GMT</pubDate>
            <atom:updated>2026-04-18T21:19:54.487Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>TL;DR</strong></p><p><strong>The Problem:</strong> Ambiguous goals (like “leveling up a specific skill”) fail because they lack the hard, quantifiable metrics of a goal like “lose 20 lbs.”</p><p><strong>The Architecture:</strong> A three-stage pipeline to strip away cognitive load and eliminate manual setup friction.</p><p><strong>The Workflow:</strong></p><ul><li>AI Dialogues (to fracture the ambiguity into actionable workstreams).</li><li>Agentic Automation via Notion MCP (to construct the tracking system without manual data entry).</li><li>Calendar Time Blocks (to force physical execution).</li></ul><h3>Engineering Execution: Taming Ambiguous Goals with Notion MCP</h3><p>The fundamental flaw in most personal development frameworks is the assumption that all goals are created equal. They are not.</p><p>If your goal is to “lose 20 pounds,” the mechanics are painfully simple: calculate a caloric deficit, track your intake, and execute. It is highly quantifiable. However, professional and cognitive goals are rarely this neat. When you set an objective like “improve my strategic visibility” or “master AI-driven interaction design,” you are dealing with profound ambiguity. There is no obvious starting line, and attempting to directly execute on an abstract concept usually results in either misdirected effort or complete paralysis.</p><p>To solve this, I stopped trying to force ambiguous goals into standard to-do lists. Instead, I built a deterministic pipeline that forces ambiguity through a series of filters until it becomes a mechanical action on a calendar.</p><p>Here is exactly how the system works.</p><h3>Phase 1: Dissolving the Fog (The AI Dialogue)</h3><p>You cannot execute on a fog. The first step is not planning; it is interrogation.</p><p>When confronting a nebulous objective, I initiate a multi-shot conversation with an LLM — whether that is Claude, Jamila, Hatch, or Ida. The goal here is not to ask the AI for a generic plan, but to use it as a cognitive wedge to split a massive problem into manageable pieces.</p><ul><li>I feed the AI the raw context of my current bottlenecks and the vague direction I want to move in.</li><li>Through back-and-forth iteration, we isolate the core problem.</li><li>We force the abstract goal into 3 to 4 distinct “Workstreams.”</li></ul><p>By the end of this phase, the monolithic goal has been fractured. I now have specific workstreams, and beneath each one, a set of defined, granular Action Items. The cognitive heavy lifting is done.</p><h3>Phase 2: Eliminating Setup Friction (Cursor + Notion MCP)</h3><p>This is where most systems break down. You have a great brainstorming session, but the effort required to manually translate a text file into a structured tracking database kills your momentum. Data entry is a waste of human capital.</p><p>This is where the Model Context Protocol (MCP) changes the paradigm.</p><ul><li>Instead of opening Notion and building tables, I take the structured output from the AI chat and feed it directly into Cursor (or a similar agentic environment).</li><li>Using Notion MCP, the agent connects directly to my Notion workspace. I simply instruct the agent to build the system for me.</li><li><strong>The automated result:</strong> The agent autonomously creates the database, configures the necessary properties (Status, Priority, Workstream tags, Deadlines), and populates the board with the exact Action Items we defined in Phase 1.</li></ul><p>What used to take 30 minutes of tedious formatting now happens in seconds via API calls. The unstructured text is instantly mapped into a structured, trackable roadmap. I never touch a database toggle.</p><h3>Phase 3: The Mechanical Constraint (Time Blocking)</h3><p>A highly organized Notion database is structurally beautiful, but practically useless if it does not interface with reality. A roadmap without a timestamp is just an organized wishlist.</p><p>The final step is ruthless translation. I take the granular Action Items sitting in Notion and map them directly into Time Blocks on my calendar.</p><ul><li>The calendar block acts as a physical constraint.</li><li>When the notification fires, the time for strategy is over. I do not need to think about <em>what</em> to do or <em>how</em> it fits into the bigger picture.</li><li>I simply open the designated Notion ticket and execute the specific task.</li></ul><h3>The System Architecture</h3><p>This workflow works because it respects the division of labor. It uses Large Language Models for what they excel at: navigating cognitive ambiguity and structuring unstructured thought. It uses Agentic tooling (Notion MCP) to handle the plumbing and eliminate the friction of system maintenance. Finally, it relies on the calendar to act as the ultimate mechanism for accountability.</p><p>You isolate the thinking, automate the structuring, and force the doing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6348825b77d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Lessons for Designers Who Want to Go Beyond Execution]]></title>
            <link>https://medium.com/design-bootcamp/7-lessons-for-designers-who-want-to-go-beyond-execution-ec36182b1179?source=rss-33aa368e6fba------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec36182b1179</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-strategy]]></category>
            <dc:creator><![CDATA[Julianna Wang]]></dc:creator>
            <pubDate>Wed, 05 Feb 2025 06:25:11 GMT</pubDate>
            <atom:updated>2025-02-05T06:43:40.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="What Happens When You’re Both ‘Head of Design’ and ‘Senior Product Designer’? — Tired" src="https://cdn-images-1.medium.com/max/1024/1*o9BrlHltMdRzADwaG3NBxw.png" /><figcaption>Me after 8 months</figcaption></figure><p>I’ve been a senior product designer at a startup for the past 8 months, operating as a team of one. In reality, that means wearing two hats — one as the Head of Design, where I need to think strategically, shape the design vision, and gain stakeholder buy-in, and the other as an individual contributor, executing hands-on design work.</p><p>To be honest? It’s been incredibly challenging<strong>.</strong> Navigating this level of ambiguity has pushed me to think beyond execution and take on a more strategic role. To help myself grow, I’ve turned to online resources (special thanks to the <a href="https://www.dive.club/"><strong>Dive Club podcast</strong></a>), learning from the experiences of other designers who have faced similar challenges.</p><p>Through a mix of what I’ve learned and my own experience, I’ve identified seven key lessons that can help any designer looking to <strong>move beyond execution</strong>, advocate for <strong>design’s business value</strong>, and <strong>communicate ideas effectively across teams</strong>.</p><h3>1. From Execution to Strategy: Owning the Bigger Picture</h3><p>Many designers get stuck in the <strong>“execution trap”</strong> — waiting for work to be assigned instead of actively shaping the problems they solve. The shift to a more <strong>strategic role</strong> comes from:</p><p>✅ <strong>Engaging early in business conversations</strong> to align design work with company goals.<br>✅ <strong>Building partnerships with PMs and engineers</strong> to stay plugged into decision-making.<br>✅ <strong>Proactively identifying problems</strong> instead of waiting for assignments.</p><p><em>“You go from being told what to do, to being told to achieve an outcome — and you have to figure it out.”</em> — Catt Small</p><p>The ability to <strong>navigate ambiguity</strong> is what sets apart senior and staff-level designers. Those who thrive in uncertainty <strong>create opportunities</strong> instead of waiting for clarity.</p><h3>2. Owning Your Work &amp; Demonstrating Impact</h3><p>Designers often undersell their work, framing it passively instead of <strong>owning its impact.</strong> A few mindset shifts can change that:</p><p>✅ <strong>Take credit with confidence:</strong> Instead of saying <em>“This was designed to do…”</em> say <em>“I designed this to…”</em><br>✅ <strong>Reframe credit as teaching:</strong> If self-promotion feels uncomfortable, think of it as sharing knowledge.<br>✅ <strong>Speak in business metrics:</strong> Explain how your work drives real change in user behavior, confidence, and emotions:</p><ul><li><strong>Behavior:</strong> Improving usability, conversion, and engagement.</li><li><strong>Attitudes:</strong> Boosting user confidence, activation, and retention.</li><li><strong>Emotions:</strong> Enhancing experience to improve NPS and referrals.</li></ul><p>Quantifying impact makes design’s value undeniable.</p><h3>3. Building Executive Presence &amp; Reducing Risk</h3><p>At leadership levels, <strong>design is viewed as a risk that executives must underwrite.</strong> Designers who gain influence don’t just present compelling ideas — they make them feel <strong>attainable.</strong></p><p>✅ <strong>Break ideas into roadmaps</strong> to show a clear path forward.<br>✅ <strong>Frame design proposals through a business lens</strong> to make a stronger case.<br>✅ <strong>Make adoption feel inevitable</strong> — leaders approve what feels low-risk and near production-ready.</p><p><em>“Anytime [Micah] presented something, people would say: ‘Do it. Go figure it out’ — and that’s what great influence looks like.”</em> — Catt Small</p><h3>4. Making Big Ideas Happen</h3><p>Great ideas don’t happen in isolation. Designers who drive change <strong>form alliances, reduce risk, and persist through initial setbacks.</strong></p><p>✅ <strong>Bring people along early:</strong> Make PMs, engineers, and other stakeholders feel like partners.<br>✅ <strong>Start small:</strong> Get buy-in with low-risk asks (e.g., <em>“Can we explore this further?”</em>).<br>✅ <strong>Set realistic expectations:</strong> Acknowledge risks and failure points upfront.<br>✅ <strong>Be persistent:</strong> Many great ideas see negative numbers before they succeed.</p><p><em>“Those numbers are going to be negative until they’re not. You have to have conviction that it’s worth moving forward.”</em> — Ryan Scott</p><p>A designer’s ability to <strong>navigate pushback and rally support</strong> is what transforms an idea from a concept into reality.</p><h3>5. The Path to a Staff Designer Role</h3><p>Staff designers aren’t just executors — they <strong>steward unstable ideas</strong> from concept to business impact. This means:</p><p>✅ <strong>Taking ownership:</strong> Push forward ideas that matter, don’t wait for an assignment.<br>✅ <strong>Finding advocates:</strong> Secure 1–2 people who will champion your idea.<br>✅ <strong>Tailoring your pitch:</strong> Learn what resonates with different audiences (execs, PMs, design leads).<br>✅ <strong>Creating an aura of inevitability:</strong> Use high-fidelity prototypes to make an idea feel like it’s already happening.</p><p><em>“When leadership saw a prototype that ‘wasn’t far from production-ready,’ it became much harder to ignore.”</em> — Kathy Zheng</p><p>Moving into <strong>staff-level roles</strong> isn’t just about doing great work — it’s about influencing direction, securing buy-in, and making sure good ideas don’t get lost.</p><h3>6. Presenting Design Directions Effectively</h3><p>How you present ideas <strong>shapes how they’re received.</strong> Instead of showcasing isolated explorations, structure them as <strong>clear, actionable directions.</strong></p><p>✅ <strong>Frame work as “design directions” not scattered concepts.</strong><br>✅ <strong>Use spectrums:</strong> Anchor ideas on variables (e.g., simplicity vs. power) to create a mental map.<br>✅ <strong>Compare trade-offs:</strong> Make it clear what’s gained and lost with each approach.<br>✅ <strong>Name your prototypes:</strong> Giving them labels makes discussion easier.<br>✅ <strong>Say “It could look something like this”</strong> — this keeps feedback constructive instead of nitpicking details.</p><p><em>“Understand that if we go this way, we’re not going that way — and there are trade-offs we need to acknowledge.”</em> — Alex Cornell</p><p>Great designers <strong>don’t just explore options — they guide teams toward the best path forward.</strong></p><h3>7. The Power of Storytelling</h3><p>Design influence isn’t just about <em>what</em> you say — it’s <em>how</em> you say it. Strong storytelling makes ideas memorable and shareable.</p><p>✅ <strong>Turn ideas into “memes”</strong> — concise, repeatable concepts that spread easily.<br>✅ <strong>Give concepts names</strong> so they stick (e.g., “CLPeek”).<br>✅ <strong>Highlight conflicts</strong> — show what users struggle with and how your solution addresses it.<br>✅ <strong>Use visuals</strong> — illustrations and comics make abstract ideas tangible.</p><p><em>“Storytelling isn’t just a skill — it’s the most important skill anyone can learn.”</em></p><p>Designers who <strong>tell compelling stories</strong> don’t just create great products — they drive real change.</p><h3>Final Thoughts</h3><p>The key to increasing your impact as a designer is <strong>moving beyond execution into strategy, communication, and leadership.</strong></p><ul><li>Own your work.</li><li>Speak in business terms.</li><li>Build strong partnerships.</li><li>Advocate for your ideas.</li><li>Influence decisions, not just designs.</li></ul><p>Design isn’t just about aesthetics — it’s about solving the right problems and proving its value. The more you shape the conversation, the more you shape the future of design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec36182b1179" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/7-lessons-for-designers-who-want-to-go-beyond-execution-ec36182b1179">7 Lessons for Designers Who Want to Go Beyond Execution</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How did I improve my visual design and interaction skills?]]></title>
            <link>https://medium.com/design-bootcamp/how-did-i-improve-my-visual-design-and-interaction-skills-f6869da12276?source=rss-33aa368e6fba------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6869da12276</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-patterns]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Julianna Wang]]></dc:creator>
            <pubDate>Mon, 10 Jul 2023 06:46:27 GMT</pubDate>
            <atom:updated>2023-07-13T02:40:21.615Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 1 Visual Design</h3><p>When I first became a designer, I was always dissatisfied with my visual design skills. Whenever I saw the work of talented designers, I would be fascinated by their creations, while feeling regretful that I couldn’t reach the same level. Especially without a formal background in design or art education, I was curious about how to improve my visual design abilities. Out of curiosity, I interviewed many peers and mentors and conducted extensive research.</p><p>I’m sure if you’re interested in this topic, you must have heard of the 100 Days of Design Challenge. I tried it, but unfortunately, it didn’t work well for me because:</p><ol><li>Completing a challenge usually took several hours, which was difficult for me to sustain while working full-time.</li><li>Merely designing without critique and reflection makes it challenging to make progress. It’s like doing a lot of exercises without knowing the answers; you can’t determine whether you’re right or wrong, which doesn’t really help in improving your skills.</li></ol><p>After conducting in-depth research, I found another method to train my design abilities, and after testing it for nearly a year, I found it to be highly effective. So, I’d like to share it with you.</p><p>The method is to analyze one piece of work that you consider good every day. Next, I will explain specifically how you should do it and why it is effective.</p><h4><strong>How to do it?</strong></h4><p>There are basically just two steps:</p><p>Step1: Every day, find any UI work that you consider good.</p><p>Step 2: Observe it and ask yourself the following 14 questions. This framework can help you analyze it effectively and comprehensively.</p><p>Questions:</p><ul><li><strong>Adequacy of impression.</strong> Does the visual fit the subject matter? What style is the work in? Why?</li><li><strong>Visual architecture.</strong> Is the design well-structured? What was the reasoning behind the composition formula? Do you understand the logic behind the content placement at a glance?</li><li><strong>User objectives.</strong> Put yourself in the user’s place. Is it immediately obvious what is being offered? Would you like to buy it / accept the offer? Is it easy to do?</li><li><strong>Color palette.</strong> Why were these colors chosen and not others? Do they induce the right emotions?</li><li><strong>Navigation.</strong> Does the navigation look convenient and logical? Is it immediately clear where everything is?</li><li><strong>Functionality.</strong> Which functions are used in the design? How do they solve the users’ problems?</li><li><strong>Content.</strong> Is the content understandable? Is there an obvious hierarchy of elements? How are the logical blocks grouped and separated? Does the design feel airy and spacious or does it appear cluttered?</li><li><strong>Highlights.</strong> What is highlighted? How is it done? (e.g. color, shape, size, animation, etc.)</li><li><strong>Graphics.</strong> What graphic elements are used? (e.g. lines, shapes, textures, color spots, etc.) What do you think was the reasoning behind their inclusion?</li><li><strong>Icons.</strong> How are the icons rendered? Are they immediately understandable? Do they fit in with the overall style?</li><li><strong>Images.</strong> How does the design use photos, illustrations, animations? Do these work toward the main goal? What was the principle for choosing them? How have they been edited? What is interesting about them?</li><li><strong>Fonts.</strong> What fonts are used and what is their hierarchy? Is the text legible, especially the small type?</li><li><strong>CTA.</strong> How is the CTA block designed? Why? Does it make you want to push the button?</li><li><strong>Uniqueness.</strong> Is there anything special about the design that makes it stand out? (There probably is, since you have noticed it and chosen it for analysis!) Try to identify this unique feature.</li></ul><h4>Why it works?</h4><p>Design is sometimes mistaken as purely a matter of creativity, as if design ability is solely related to talent. But what is creativity? One explanation that resonates with me is that creativity = structure + transformation + combination.</p><p>When you look at design from this perspective, there is no such thing as a “truly” original design in the world. Everyone gains inspiration from others’ works and then develops their own ideas through their understanding. Instead of simply training your eye by looking at a large number of good designs, I believe a more effective approach is to understand why those designs are considered good. And this framework helps you deconstruct designs from various aspects, while you just need to follow its structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VAIKaEdDpCrJvN3vVhllxw.png" /></figure><p>This is the so-called Golden Circle rule. “What” only lets you understand what you see, improves your aesthetics, and accumulates surface-level information related to design. When you think about “How”, you gain the ability to understand how to achieve a certain effect. Going further, when you start thinking about “Why”, you finally delve into the essence of design. You explore the foundation upon which the design was proposed, what design challenges or problems it encountered, what problems it solves, how it solves them, and whether there could be better solutions. Can the current solution be incorporated into your knowledge base?</p><p>After training for a while, you may find that it takes you more and more time to find good designs. Congratulations! This indicates that your standards for “good” are improving, and your taste is getting better.</p><h3>Part 2 Interaction Design</h3><p>Similarly, when I started working, I was always amazed at how quickly my leaders could come up with multiple possible interaction solutions for a given problem. It seemed to be an instinct for them. I also wanted to develop this ability quickly, but when I asked them how they cultivated this skill, they simply told me it takes time. I wasn’t satisfied with such an answer, so I deliberately sought out methods to improve my interaction abilities and put them into practice over the past year. I have two proven effective methods to share:</p><h4>Study Design Systems</h4><p>Studying design systems is essential in my view. Every interface design process involves expressing the product solution through a design language. As a designer, we often get stuck during the ideation process because we lack a clear understanding of which components are best suited to solve specific problems. However, every design component exists for a reason. The more we understand them, the better and quicker we can generate ideas.</p><p>By studying design systems, we gain insights into established and effective design patterns and components. Systems such as Material Design, Carbon Design, or Apple’s Human Interface Guidelines have been extensively tested and optimized for usability and user experience. They provide comprehensive sets of components, guidelines, and principles that serve as valuable resources for the design process.</p><p>Through studying design systems, we can:</p><ul><li>Understand design patterns: Design systems offer predefined patterns and guidelines for common design challenges. By studying these patterns, we gain a deeper understanding of how different components can be used in specific contexts and learn from established best practices.</li><li>Discover and leverage existing components: Design systems provide a wide range of ready-to-use components that have been carefully designed and tested. By utilizing these components, we can save time and effort in creating new designs from scratch, while ensuring consistency and usability.</li><li>Stay up-to-date with industry standards: Design systems are regularly updated to reflect the latest trends and advancements. By studying popular design systems, we can stay informed about current industry standards and design practices, ensuring that our designs remain relevant and aligned with user expectations.</li></ul><h4>Do UX audit for popular products (just like how you prepare your app critique interviews)</h4><p>Sometimes, design goes beyond assembling existing components or patterns, especially in enterprise design where user tasks can be more complex and there are additional technical constraints. In such cases, the components or patterns available in a design system may not fully meet the requirements. Exploring existing products can provide you with richer inspiration and insights to address those specific needs.</p><h4>How it works?</h4><ol><li><strong>Start with foundation</strong></li></ol><p>We all know the 5 elements of UX design. To better understand why interactions of a product work in a certain way, it’s better to understand the foundation of it. You can start with understand their business model and then dive deep. If you don’t mind, you can even use Business Modal Canvas to help you get started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*un3isthjEl9ZTMXVKc-rmA.png" /><figcaption>5 elements of user experience design</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RaNw4t_k8gCpMoUrtiwZIQ.png" /><figcaption>Business Model Canvas</figcaption></figure><p><strong>2. Put yourself in the user’s shoes and go through the flow step by step</strong></p><p>Take on the role of a user and navigate through the product’s flow. Engage with each step and interact with all the available features and functions. This hands-on approach allows you to experience the product firsthand and gain insights into its interaction design. Observe how different components and patterns are utilized and analyze their effectiveness in facilitating a seamless user experience.</p><p><strong>3. Take note of effective and innovative interactions</strong></p><p>During your exploration, identify interactions that stand out as particularly effective or innovative. Note down the specific components, patterns, or techniques used to achieve these interactions. Analyze how these elements contribute to a positive user experience and consider how you can apply similar principles to your own design work. In this way, you can look beyond your immediate industry or domain to gain fresh perspectives and insights. Analyze how different products solve similar interaction challenges and consider how you can adapt those approaches to your own projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6869da12276" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/how-did-i-improve-my-visual-design-and-interaction-skills-f6869da12276">How did I improve my visual design and interaction skills?</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I accelerate my growth as a product designer]]></title>
            <link>https://medium.com/@juliannawang/how-i-accelerate-my-growth-as-a-product-designer-92b27a5b3cb0?source=rss-33aa368e6fba------2</link>
            <guid isPermaLink="false">https://medium.com/p/92b27a5b3cb0</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <dc:creator><![CDATA[Julianna Wang]]></dc:creator>
            <pubDate>Tue, 04 Jul 2023 05:49:36 GMT</pubDate>
            <atom:updated>2023-07-05T01:59:53.426Z</atom:updated>
            <content:encoded><![CDATA[<p>Starting my career without a design degree and working in a startup, I have always considered myself an underdog in the competitive job market. However, fueled by a deep passion for design and a strong desire for rapid growth, I embarked on detailed research to develop a comprehensive career development plan for myself.</p><p>In this article, I will outline my plan in several sections, hoping that it can also provide assistance to others.</p><h3>Know the Career Path</h3><p>Just as determining the destination is the first step in planning a trip, understanding the common career paths in a specific profession is crucial for developing a career plan. For a product designer, like many other roles in the tech industry, there are two common career paths: individual contributor (IC) or management. By referring to websites like level.fyi, you can gain insights into the career ladder for each path. At this early stage of my career, I am not in a rush to decide between IC or management. Instead, I aim to gain experience in different types of work, focusing on the breadth of my job responsibilities rather than depth. I want to start as a generalist, laying a solid foundation for my career development, and later, based on my preferences and abilities, choose a specialization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ez3SvZszukkH_I-kkIN7UA.png" /><figcaption>Created by <a href="https://uxdesign.cc/fixing-product-design-career-paths-with-the-mirror-model-76152b7e547">Ryan Ford</a></figcaption></figure><p>However, merely having a general understanding of future career development is not enough. A job title does not guarantee anything, and promotions are not entirely within our control. Rather than pursuing titles, it is more important to strive for the skills required to achieve those titles.</p><p>So, how do I know what skills each level requires? The answer lies in leveling rubrics.</p><p>Every company may have specific requirements for designers at different levels due to the nature of their business. To gain a comprehensive understanding, I collected specific job level standards from several companies within my current field or the field I aspire to work in. By compiling this information, I obtained a widely accepted set of requirements for designer career levels. Here, I provide some resources that I found helpful:</p><ul><li><a href="https://www.figma.com/community/file/1220482745322443565">Figma Product Design &amp; Writing Career Levels | Figma Community</a></li><li><a href="https://uxdesign.cc/a-guide-to-becoming-a-senior-product-designer-7b7296f08910">A guide to becoming a senior product designer</a></li><li><a href="https://docs.google.com/spreadsheets/d/1ZfINiB3u94ZaYH-rcuW9tI09jO9GvFbUs4G49gyyGgY/edit#gid=0">Mixmax Product Design Leveling Matrix - 2020</a></li></ul><h3>Assess My Current Level</h3><p>Understanding your current position is another important aspect after knowing the career path. You can assess your level in the following ways:</p><ol><li>Conduct a self-assessment as accurately as possible.</li><li>Request an evaluation from your leader during a one-on-one meeting.</li><li>Participate in interviews to gauge your current level.</li></ol><p>Among these options, the first one is the least costly and challenging, but it may lack objectivity and accuracy. However, it serves as a reference point. I have also attempted the second method, but it was met with rejection from my leads for unknown reasons.</p><h3>Identify Areas for Improvement</h3><p>After assessing myself, I discovered that my proficiency in different skills may vary. In such cases, I create a document where I record my self-assessment results. For each skill, I ask myself the following four questions:</p><ol><li>What’s my current level in ______?</li></ol><p>I write down what I believe is my level in a particular skill and provide as much evidence and reasoning as possible.</p><ol><li>What’s my current weakness in ________?</li></ol><p>Even if I have reached a certain level in a skill, there may still be aspects where I need improvement. I focus on identifying areas where I can enhance my performance.</p><ol><li>What’s the next level expectation in _______?</li></ol><p>I document the criteria for the next level according to the rubric, highlighting the key points.</p><ol><li>What actions should I take to achieve the next level?</li></ol><p>I outline the actions I believe I should take. I may not always have the answers to this question on the first try (if I did, I probably wouldn’t be lower that level). To solve this, I usually conduct research specific to the identified problems and address them in the next steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*BBY_sQEmHB7Bv2XtKyIfIw.png" /><figcaption>My assessment</figcaption></figure><h3>Set a Plan and Stick to It</h3><p>Now comes the most crucial part.</p><p>I particularly resonate with the quote from “Atomic Habits” by James Clear: “You do not rise to the level of your goals. You fall to the level of your systems.”</p><p>To ensure consistent growth, I choose to create detailed plans. Here, I adapt August Bradley’s Goal-Project-Task model, replacing “Goals” with “Skills”. For each skill I need to improve, I divide them into projects, which can be both work-related and side projects. Next, I break down these projects into smaller tasks, which serve as the basic units of execution. For example, if I aim to enhance my interaction design skills, at the project level, I set several projects: studying design systems, analyzing the interactions of popular products, as well as reading classic books on interaction design. At the task level, I further break down each project, such as studying Apple Human Interface Guidelines, Material Design System, Ant Design System, and more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KwR8g79RIKIgnn4mkcW03A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n2BcZqD1QhjL9roSASxUlQ.png" /><figcaption>Part of my plan</figcaption></figure><p>Now, big goals are transformed into actionable to-do lists. To ensure adherence to these lists, I incorporate them into my weekly schedule. Every Monday before starting work, I write down my to-do list for the week and review it. I determine their priority and urgency, ensuring they align with my goals.</p><p>By regularly reviewing and aligning my tasks with my overarching goals, I maintain focus and ensure that my actions contribute meaningfully to my professional development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TbWoXyRj6IQdWg-w2WrnVg.png" /><figcaption>One of my weekly plans</figcaption></figure><h3>Review the Progress and Set New Plans</h3><p>I usually set a review cadence of three months for my plans. Every three months, I assess my progress, identify areas of improvement, and evaluate whether I have followed the initial plan as expected. After the review, I develop a new three-month plan, repeating the cycle. Of course, the three-month timeframe may not be suitable for everyone, and you can adjust it based on your preferences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92b27a5b3cb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>