<?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 Jing Jin on Medium]]></title>
        <description><![CDATA[Stories by Jing Jin on Medium]]></description>
        <link>https://medium.com/@jingidy?source=rss-32bc279208c7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZDA4UiGmnV2qQVJ_TiygWw.jpeg</url>
            <title>Stories by Jing Jin on Medium</title>
            <link>https://medium.com/@jingidy?source=rss-32bc279208c7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:41:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jingidy/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[Wireframes are dead.]]></title>
            <link>https://jingidy.medium.com/wireframes-are-dead-f732441aae8b?source=rss-32bc279208c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f732441aae8b</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Jing Jin]]></dc:creator>
            <pubDate>Fri, 29 Aug 2025 20:01:36 GMT</pubDate>
            <atom:updated>2025-08-29T22:24:50.407Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Wireframes are washed-up B-list celebrities.</strong><br>They still turn up on the red carpet, everyone politely applauds, but nobody came for them. Once they were stars: bridging UX, visuals, and engineering. But now they linger in the background, making awkward cameos in design reviews while everyone’s really just waiting for the “real” designs.</p><p>Nobody even agrees what a wireframe is anymore. Ask 5 people and you’ll get 6 different expectations. We just keep using it out of habit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dQ8NdY5Zb7C73pODymECEA.png" /></figure><h3>When ‘Close Enough’ Stopped Being Enough</h3><p>Wireframes thrived in the waterfall era with point-and-click UI. They mapped behavior and functionality so backend engineers could start building while visual designers created UI for front-end engineers. Everyone knew exactly what “wireframe” meant: gray boxes that showed structure without polish.</p><p>That world died three deaths:</p><ul><li><strong>Teams went parallel and generalist.</strong> No more waterfall handoffs and specialties got merged with product designers and full-stack engineers.</li><li><strong>Software became more alive.</strong> Modern apps aren’t static screens. They’re fluid, responsive, full of gestures and live data. Gray boxes can’t capture what users actually experience.</li><li><strong>Design systems flipped the script.</strong> When you can drag in components that already look polished, making a sketchy grayscale version takes <em>more</em> effort than just building the real thing. The path of least resistance is high-fidelity.</li></ul><p>So we build layouts half-filled with polished components but still call them “wireframes”. And don’t even start on Lorum Ipsum vs. placeholder copy vs. real data. No wonder everyone is confused.</p><h3>The Nail on the Coffin: AI</h3><p>With <a href="http://v0.app/">V0</a>, <a href="http://uxpilot.ai/">UX Pilot</a>, and <a href="https://www.figma.com/make/">Figma Make</a>, anyone can generate something that looks high fidelity at the snap of a finger. Non-designers create in minutes what used to take designers days. And it looks <em>good enough to ship</em>.</p><p>If anyone can make something pretty, what’s the point of a designer? The answer is obvious to us: usability, edge cases, systematic thinking… but stakeholders just see pretty screen that looks better than your “wireframes”.</p><p>This is the brutal reality for today’s designer:</p><ul><li><strong>Expectations inflated.</strong> Designers are now expected to outpace AI, delivering work that’s faster, sharper, and more polished than what anyone can generate.</li><li><strong>Pretty hides the pain.</strong> In reviews, designers get judged first on how polished something looks. We’re still accountable for long-term system-wide usability, it just takes more effort to get stakeholders to focus on that.</li><li><strong>The artifacts shifted.</strong> Designers are also using AI to deliver polished designs and prototypes faster, so stakeholders get even less used to the idea of having to “imagine it”.</li></ul><p>Wireframes existed because waiting for high-fidelity work was costly, but with today’s fast-paced expectations, an abstract middle step is much harder to justify.</p><h3>The Singularity of Future Design</h3><p><strong>As AI and automations advance, the cost of producing polished interactive designs will shrink to zero. </strong>Generating 10 ideas will be as fast as generating 2 ideas. A concept design will no longer mean one screen, it will be an entire flow of polished interactions.</p><p>The future of design work will look very different:</p><ul><li><strong>Every idea looks complete.</strong> Stakeholders will evaluate all options as if they are finished, raising the bar for clarity and intent earlier than ever.</li><li><strong>Design work becomes creative direction.</strong> Designers will move from drawing artifacts to directing AI outputs, iterating through 10 times as many explorations to discover the best solution for both first impressions and hidden edge cases.</li><li><strong>Manual craft becomes a rare luxury.</strong> Like a handmade chair in a world of mass-produced furniture, hand-crafted design will be for exclusive experiences only.</li></ul><p>This will actually be good: we’ll dogfood the exact user experience from the start. We can user test complete experiences instead of wondering if our lower fidelity skewed the user feedback.</p><h3>Living in the Awkward Now</h3><p>We are certainly not at zero cost yet, but expectations are starting to shift toward “better and faster.” So it’s more important than ever to be explicit when you’re creating low-fidelity <em>on purpose</em>. Otherwise people just assume you made an ugly design. When everything can look polished, choosing not to polish needs to be explained as a deliberate decision.</p><p>Stop saying “wireframe” and assume that means polish isn’t expected. Be explicit about what kinds methods you’re choosing and the tradeoffs:</p><ul><li><strong>Sketches and flows</strong> to show structure and sequence while removing the need to match every UI with every gray box on screen.</li><li><strong>A concept screen</strong> or two to give stakeholders something that they can feel and react to, before investing in all use cases.</li><li><strong>Interactive prototypes</strong> that you vibe coded to show a specific behavior in detail, rather than trying explain every interaction using the same fidelity.</li></ul><p>These artifacts aren’t stages in a process anymore — they’re tools to use whenever needed. The future demands precision in our language so we can have flexibility in our workflow, not nostalgia for a more cut-and-dry process.</p><p>Wireframes had their moment. But the word has outlived its usefulness. Stop saying wireframe. Say what you actually mean.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f732441aae8b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons in Leadership: My Journey Growing The UX Team at a Hyper-Growth Startup]]></title>
            <link>https://blog.startupstash.com/lessons-in-leadership-my-journey-growing-the-ux-team-at-a-hyper-growth-startup-c9f7129807e8?source=rss-32bc279208c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9f7129807e8</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[career-growth]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[communication-skills]]></category>
            <category><![CDATA[company-culture]]></category>
            <dc:creator><![CDATA[Jing Jin]]></dc:creator>
            <pubDate>Thu, 29 Dec 2022 21:41:57 GMT</pubDate>
            <atom:updated>2023-01-05T11:58:19.182Z</atom:updated>
            <content:encoded><![CDATA[<p>When I joined <a href="https://outschool.com/">Outschool</a> as the first designer and employee 13, I had no idea that it would grow to over 180 people in three years. My role also grew with it, and I expanded the UX team to 15 people and became Head of User Experience. I want to share some of the lessons I learned about communication, culture, and career advancement that helped me navigate the challenges and opportunities that come with hyper-growth.</p><h3>Trust and Communication</h3><h4>Lesson: Trust is everything</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6faq_aTyPCcmzn_k0yaMZw.png" /><figcaption>Trust, transparency, risk-taking, and productivity have a self-reinforcing effect on each other.</figcaption></figure><p>Trust is critical in a startup because processes often change rapidly and there may not be time to document or build norms across the company. Trust allows for increased communication and transparency, which helps to address problems early on. It also enables greater productivity, as team members are more likely to take risks and try new things when they know they have the support of their colleagues.</p><p>When there is less trust, people are adverse to sharing information for fear of their decisions being challenged, don’t want to take risks for the fear of being blamed for failure, and stay in their lane even if some burning problems aren’t being solved. Effective communication is crucial for building trust, and it’s easier to maintain trust than to fix lack of trust.</p><h4>Lesson: Documentation isn’t the same as communication</h4><p>When there is too much documentation, it becomes too overwhelming and time-consuming for people to find what they need, especially in a fast-paced startup environment.<strong> A complete document is completely useless if no one reads it.</strong></p><p>Documentation also only has one context in which people can discuss it — in full view of everyone else. When people are not comfortable sharing their doubts with the entire company, they may not comment, and this feedback may not reach you until it blocks you at a formal decision point.</p><p>Is documentation ever useful? Yes, but only after you have gotten buy-in through individual conversations and group discussions, to help you capture agreements for future reference. It can also be useful if you find yourself repeating the same information over and over again — having a document to point to makes it quicker to convey context and show historical buy-in, as long as it’s easy to peruse.</p><h4>Going Forward: Proactively communicate expectations and concerns</h4><p>The key to building trust is to proactively communicate expectations and concerns. As the book <a href="https://www.blackswanltd.com/never-split-the-difference">Never Split the Difference</a> advises, “fishing for concerns” by asking open-ended questions and actively listening can uncover hidden issues and defuse potential roadblocks.</p><p>If disagreements persist, switch to a real-time, private communication method to build empathy. Once I was in a Slack discussion that spanned several days without resolution, and was able to reach agreement within 1 day with just two short live meetings. To resolve conflicts, identify common ground and use frameworks for conflict resolution and high stakes situations from <a href="https://cruciallearning.com/books/">Crucial Conversations</a> and <a href="https://www.nonviolentcommunication.com/product/nvc/">Non-Violent Communication</a>.</p><h4>Going Forward: Step outside of your lane without stepping on toes</h4><p>One of the best things about startups is that there are endless interesting things you could explore, even if it’s not your core competency. However, it’s also important to be mindful of not stepping on others’ toes in the process.</p><p>If you find yourself stepping into what might be someone else’s lane, it’s important to respect their ownership of deciding how to handle it, even if you disagree. Instead of going around them or trying to do things on your own, <strong>start a conversation and ask for their input or feedback on any opportunities you see, and being flexible in finding common ground</strong>.</p><p>By showing respect and being willing to collaborate, you can build trust and strengthen relationships with your team members. These relationships are the foundations for working togther successfully going forward.</p><h3>Maintaining Culture and Good Practices</h3><h4>Lesson: Culture changes every time the team doubles</h4><p>I’ve heard that “a team’s culture changes every time it doubles in size” and thought that this only applied sometimes. I was surprised to see it was true whether my team was doubling from 2 to 4 or from 7 to 15, or the company as a whole, doubling from 100 to almost 200.</p><p>For example, a group check-in that worked well with a tight-knit team of 7, feels stifled and long-winded with a team of 15. When the UX team surfaced a desire to feel closer to each other, I implemented a rotating buddy system to allow team members to build rapport in pairs while still eventually meeting everyone on the team. This didn’t make us feel like the old 7-person team, but it helped us maintain a sense of closeness despite the larger team size.</p><h4>Lesson: If an idea is good, it will come back up again</h4><p>Many designers have experienced the frustration of having a good idea dropped due to lack of resources. However, I have found that <strong>good ideas often resurface later through different advocates. </strong>Eventually, you reach a critical mass of advocates who can help you push the idea through to production.</p><p>At Outschool, I have seen this happen countless times — the creation of the learner space, the improvement of our messaging platform, the development of internal tools like user journeys, and more. These projects often started as design sprints or side projects that didn’t amount to next steps, but after a few months, other teams would be working on similar areas and were grateful to have the foundation laid by these earlier projects.</p><h4>Going Forward: Actively reinforce existing good practices as the team grows</h4><p>Change is the norm, not the exception, in startups. So it’s important to continually reinforce existing practices and not assume they would practice on their own.</p><p>In the early days of the UX team, I created a project template and tracker to ensure all our deliverables were aligned and accountable. As we grew and the existing template became too restrictive, I allowed the team to document in their own way. However, after a while, we had lost the norm of tracking project timelines. New team members weren’t aware of the templates, and there was a lot of confusion around project scope and progress with stakeholders and leadership. To fix this, I had to personally require and check every project’s documentation, even if I wasn’t the direct manager of the project, which took a lot of time.</p><p>I realized that <strong>while flexibility was important, we also needed to actively reinforce good practices as the team grew. </strong>Going forward, I would check in on our practices often to make sure we keep the ones that work, adapt the ones that almost work, and don’t throw out everything that was old just because it was “old”.</p><h4>Going Forward: Repeat important points like a broken record</h4><p>There’s a common saying in marketing that you have to repeat something 7 times for people to remember it. Applying this philosophy to advocating for good ideas is how features like learner space and messaging improvements eventually made it to production at Outschool.</p><p>There’s also a way to get a group of people to <strong>use repetition in order to to create cohesion and train skills. </strong>For example, I asked the UX team to explain how their projects related to company OKRs at every team meeting. Initially this felt awkward and we kept forgetting, but eventually this helped the team understand how their work fit into the bigger picture and allowed me to coach them on strategic focus and clear communication.</p><p>This technique only works if the team feels purposeful and empowered. As the book <a href="https://davidmarquet.com/turn-the-ship-around-book/">Turn the Ship Around!</a> emphasizes, it’s important to involve others in the decision-making process and gain their commitment to change. By repeating important points and involving others in the process, we can successfully establish and reinforce good practices as the team grows.</p><h3>Maximizing Career Advancement</h3><h4>Lesson: You can impact many things, but will only be rewarded for some</h4><p>At Outschool, I’ve had the opportunity to take on projects outside of my core skillset and see the impact of my work, such as creating culture values and bringing in <a href="https://www.findem.ai/knowledge-center/what-is-diversity-equity-inclusion-and-belonging">DEIB</a> consultants. However, not all additional work can help you achieve career advancement. One of my past managers told me:</p><blockquote>“Everything you do is appreciated, but the things that only you can do are what’s needed.”</blockquote><p>As a startup matures, it will often hire people with expertise in specific areas rather than generalists who can cover many areas. Being the first to own an area does not always lead to a promotion to continue expanding that area, as I’ve seen many early employees disappointingly found out.</p><p>It’s hard to predict which side projects are a distraction and which ones further your career. My culture values and DEIB work helped the company but weren’t directly related to building my UX practice. However, when I was up for promotion to Head, these projects demonstrated my commitment to company culture and ability to put the company’s needs ahead of department needs, which were key requirements for the role.</p><h4>Going Forward: To be more strategic, focus on fewer things</h4><p>There is always more than enough to do at a startup, so it’s important to prioritize the important ones. As my mentor said:</p><blockquote>“It’s like juggling balls knowing you’ll drop some, and deciding which ones will shatter, which you can pick up later, and which ones you don’t need at all.”</blockquote><p>I’ve used the <a href="https://gettingthingsdone.com/">Getting Things Done</a> methodology for many years, which involves separating to-do lists into “today”, “this week”, and “this month” and reviewing and moving tasks between them at the beginning of each day, week, and month.</p><p>At Outschool, I needed more than just getting things done, I needed to ensure the right things were getting done, whether I’m doing or I’m supervising. Using inspiration from the <a href="https://review.firstround.com/read-this-before-joining-as-employee-1-to-20-at-a-startup">Eyes On, Hands On, Horizon</a> framework, I maintained a list of focus areas (e.g. rebranding, hiring, department offsites) and marked 2–3 as top priority each week. When adding new tasks, I label them by focus area and prioritize those that align with top priorities. This helps me react to urgent changes without losing sight of long-term investments, which is a common challenge for leaders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ucw9FneM1V1qI-L96DaY3A.png" /><figcaption>You can set up this structure with tools like Coda or Notion</figcaption></figure><h4>Going Forward: Satisfy the job you have, but excel at the job you want</h4><p>Excelling at your current job doesn’t necessarily guarantee a promotion, especially in startups where opportunities may arise in unexpected ways.</p><p>But how do you do both the job you have and the job you want when the work is already never-ending? <strong>Simply say “my plate is full” with a suggestion of how to move forward. </strong>For example, when I was a solo designer and wanted to grow a team, I advocated for new opportunities and pointed out when my plate was full with higher priority work. Several times, this got me buy-in to hire contractors, demonstrating my management skills, and eventually form a team that produced Outschool’s learner space.</p><p>More recently, my biggest desire was to align the company to a common vision, even though that was a better fit for a higher level executive. I advocated it to the Head of Outschool and he wanted the UX team to drive that vision, but I pointed out how everyone had a full plate working on more immediate outcomes. After brainstorming together, we eventually held a 1-hour workshop with the Head of Outschool and the UX team, which resulted in a vision story that he presented at our company-wide offsite. By setting boundaries and collaborating with my main stakeholder, I was able to fulfill my desire with less time and give my team the bonus of more exposure to executives.</p><h3>Learn, Hypothesize, Test, and Repeat</h3><p>In my 3 years at Outschool from solo designer to Head of UX, I’ve learned countless lessons that would be too long to write. But if I had to take away just one, it would be that there’s a 4-step process that’s very effective at affecting change: Learn, Hypothesize, Test, and Repeat until satisfied.</p><p>This might sound similar to many product development frameworks, but “<strong>Learn, Hypothesize, Test, and Repeat” focuses on learning and testing rather than immediate outcomes, which helps embrace uncertainty and adapt to change. </strong>In <a href="https://adamgrant.net/book/think-again/">Think Again</a>, Adam Grant goes into more detail on how staying curious and open to new ideas is the key to success across all walks of life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XRqKxyaSuXYc4tmP94SkMg.png" /><figcaption>The goal is to learn and build upon learning, not getting to the checkmark on the first try.</figcaption></figure><p>I’ve used this framework to find new mentors and coaches, start innovation projects, troubleshoot team friction, and even write more and network more.</p><p>I’m now applying it to my next career step, where my hypothesis is “I care about creative partnerships that bring ease to everyday lives more than the exact type of role or engagement.” To test this hypothesis, I am seeking out opportunities that align with this value, and applying the lessons I’ve learned wherever I go next. I hope to share more learnings in the future!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9f7129807e8" width="1" height="1" alt=""><hr><p><a href="https://blog.startupstash.com/lessons-in-leadership-my-journey-growing-the-ux-team-at-a-hyper-growth-startup-c9f7129807e8">Lessons in Leadership: My Journey Growing The UX Team at a Hyper-Growth Startup</a> was originally published in <a href="https://blog.startupstash.com/">Startup Stash</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get involved in strategy as a designer]]></title>
            <link>https://jingidy.medium.com/how-to-get-involved-in-strategy-as-a-designer-9d5520f515d5?source=rss-32bc279208c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d5520f515d5</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jing Jin]]></dc:creator>
            <pubDate>Thu, 08 Dec 2022 21:19:43 GMT</pubDate>
            <atom:updated>2022-12-08T21:19:43.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BjyPFovb4QAmhYoQc_kO0w.jpeg" /></figure><p>As a designer, you may want to get more involved in the strategy process. But where do you start? How can you get involved in strategy and have more influence on your company’s decisions? In this post, I’ll share some tips for getting started. So whether you’re just starting out or you’re looking for new ways to deepen your skills, read on for some helpful advice.</p><p>There are four steps to getting involved in strategy:</p><ol><li>understand what it means to be strategic and why it is important to your organization</li><li>connect your tactical work to the overall strategy</li><li>measure and evaluate your impact on the company</li><li>build credibility with stakeholders</li></ol><h3>What is strategy and why it’s important</h3><p>When people say “I want to be involved in strategy”, they often mean “I want to have influence over the important decisions.” However there are 3 different types of important decisions in every company: vision, strategy, and tactics.</p><p>Vision is where you want to end up — e.g. eating a delicious birthday cake. Strategy is choosing a path— e.g. making a cake instead of buying one. And tactics are the steps within the approach — e.g. buy groceries, bake, decorate, etc.</p><p>Vision, strategy, and tactics have to exist together: tactics without strategy is just a to-do list of things that may not be important, and strategy without tactics tend to become marching orders that are unachievable. Vision is the raison d’être that gets you out of bed each morning, but without strategy or tactics, it’s just a pipe dream.</p><blockquote>Vision is where you want to end up. Strategy is choosing what path to take. Tactics are individual steps within the path. Vision, strategy, and tactics have to exist together.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VvtF5VtZIDosCYG7wkv6gg.png" /></figure><p>To be involved in strategy, you have to understand why they are important to your organization — for-profit companies tend to focus on profits and market share, while non-profits tend to focus on impact that will enable them to acquire in more funding. Strategy at any organization is about survival: financial success that achieves the vision. To be involved in strategy, you have to make every tactical decision serve these goals.</p><blockquote>Strategic decisions at any organization is about survival: financial success that achieves the vision. To be involved in strategy, you have to make every tactical decision serve these goals.</blockquote><p>Good news: designers are already trained at tactics. These are decisions like what design methods to use, how long you spend on a design, and what to include or exclude in a design. So your path into strategy is through connecting it to your tactical work.</p><h3>Connecting tactical work to strategy</h3><p>As designers, we generally receive projects with “we want to solve problem X” or “we want to build feature Y”. You want to ask questions to understand the strategic reasoning behind that request — why it’s important to organizational survival. This helps you learn strategic thinking from others and gives you a chance to offer your design perspective at a strategic level.</p><h4>Here’s an example:</h4><blockquote>Stakeholder: We want to add chat support to our account setup flow.</blockquote><blockquote>You: What problem does the chat support solve for our users?</blockquote><blockquote>Stakeholder: It gets their questions answered quicker than an email.</blockquote><blockquote>You: Why is this an important problem to solve for our business?</blockquote><blockquote>Stakeholders: We see the biggest drop-off in account setup when someone asks a question and never comes back even after we answer them.</blockquote><blockquote>You: Why is focusing on users in the account setup stage important, vs. users who’ve already set up their accounts?</blockquote><blockquote>Stakeholder: Because if they complete account setup, we can send them re-engagement emails even if they curn. And we also think fixing new user activation is easier than fixing retention for existing users in terms of immediate growth.</blockquote><blockquote>You: Why is it important to focus on immediate growth right now?</blockquote><blockquote>Stakeholder: Because we are fundraising in 6 months and need to show good recent growth.</blockquote><p>In this example, you found out that the strategy is to grow new user activation first, so that the company can raise more funds to increase retention later. And a tactic within this strategy is to use chat support to reduce the biggest drop-off scenario in account setup.</p><p>Asking why contributes strategically by uncovering any misalignments in the team’s goals, or any assumptions that aren’t supported by data. (It didn’t happen in this example but often happens in real life)</p><p>And when there is clear alignment, knowing why you’re doing something will help you course-correct when things don’t go as expected. If users feel meh about your chat support designs, you can move up a level and ask “is the lack of real-time support why they’re dropping off?” If users love chat support but you’re not seeing new user growth, you can move up a level to ask “is the biggest drop-off in new user growth during account setup?” These are your tools to give your projects the best chance of being successful in a strategically relevant way.</p><blockquote>Asking why uncovers any misalignments in the team’s goals, or any assumptions that aren’t supported by data. It also helps you course-correct when things don’t go as expected.</blockquote><h3>Evaluate your impact</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5btaMJpyiJlVbJWCfgasJw.jpeg" /></figure><p>Another key component of being strategic is being able to look back and evaluate whether the path you chose worked well. The most common way is for businesses to set quantitative metrics such as conversion rate, activation rate, retention rate, CAC, LTV, etc.</p><p>You don’t have to learn SQL. What’s more important is being able to use these concepts in discussions at a high level, rather than being the person to pull data direct from the database (although it’s a plus).</p><p>As a designer, you add the unique strategic value of understanding qualitative metrics — quantitative metrics only tell you the “what”, but qualitative tells you the “why”.</p><blockquote>As a designer, you add the unique strategic value of understanding qualitative metrics , which tells you the “why”.</blockquote><p>An example of a conversation where you can apply these concepts:</p><blockquote>You: How’s the chat feature doing?</blockquote><blockquote>Stakeholder: It’s definitely bumping activation up, but we’re seeing a lower LTV and higher churn. We’re trying to re-engage them through email.</blockquote><blockquote>You: What’s the current click-through rate on the re-engagement email?</blockquote><blockquote>Stakeholder: CTR is around 1%</blockquote><blockquote>You: Hm… that sounds lower than industry average. Do we know why?</blockquote><blockquote>Stakeholder: Not sure, but we’re planning to do some A/B testing to try to get that metric up.</blockquote><blockquote>You: That sounds like it could take many weeks, especially since we’re fundraising so soon. How about I take a week to conduct some user research and find out if there’s a pattern in why they’re churning, that way we can implement less experiments but be more confident in each one.</blockquote><p>You just provided strategic value: saving the company a few weeks in finding out what’s wrong means that you’re more likely to achieve better metrics before fundraising.</p><p>You may find that users are churning because the value prop doesn’t resonate with them, and that it’s also the original reason for them not finishing the signup — they didn’t need support in completing their accounts, they needed more motivation for why it’s worth it. And if that’s the reason, then the right strategy isn’t better re-engagement emails, it’s going to be onboarding messaging and education. Boom, you provided strategic value again!</p><h3>Build credibility</h3><p>The art and science of gaining credibility in a business setting is subtle. It’s about being proactive, but not forcing your way into conversations that don’t serve you or the organization at large. These conversations often start as informal “hey I wanna run an idea by you…” chats, so you have to show enough respect for others’ opinions that they’ll seek out yours without feeling like an interruption (or worse yet — a threat).</p><p>That doesn’t mean you should sit still in your lane until your name is called. Here are some steps to smoothly get more into strategic circles:</p><ol><li><strong>Show you can do the expected</strong> — be good at your first responsibility: Create designs that makes stakeholders say “Wow, we wouldn’t be able to do it without you.” This is a pre-requisite for influence in future projects.</li><li><strong>Show you understand where the business goals and constraints are</strong> — Ask questions to show empathy for your stakeholders’ goals. Make stakeholders say “Wow, you really understand what I’m going through.” Make them feel like you’re eager to learn and easy to get along with. This will get you exposed to much more informal, private, conversations that are usually the beginnings of a strategy.</li><li><strong>Show the extra value you bring</strong> — After you’ve done the groundwork, you’ll be in the right place at the right time to contribute to strategic discussions, and you’ll have stakeholders who already trust you. Here you’ll finally have a chance to bring up additional insights, suggest outside-the-box solutions, ask questions to anchor the discussion to concrete next steps, and in general bringing out the best in other people. 🙂</li></ol><p>As you can see, becoming a strategic designer is no easy task. It requires an understanding of not only design, but also business and how to measure success. However, if you are up for the challenge and want to make a real impact on your organization, it is definitely worth the effort. Are you ready to take your design career to the next level?</p><p><em>P.S. Hey, did you notice that I used AI to write this post? In fact it helped me tweak my outline and even rewrite entire paragraphs! So tell me if what we wrote together makes any sense at all and guess which parts the AI did — I’ll let you know if you’re right or wrong ;)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d5520f515d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The pros and Cons of Integrating Designers into Product Teams]]></title>
            <link>https://medium.com/design-bootcamp/the-pros-and-cons-of-integrating-designers-into-product-teams-a21c5d8c32a6?source=rss-32bc279208c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a21c5d8c32a6</guid>
            <category><![CDATA[organization-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jing Jin]]></dc:creator>
            <pubDate>Tue, 22 Nov 2022 22:20:34 GMT</pubDate>
            <atom:updated>2022-12-09T04:00:41.600Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EEspS0Ryk1RNlqbGO1iKJQ.jpeg" /></figure><p>Many organizations believe that integrating designers into product teams is the key to success, but is this really the best way? On one hand, this can help to create a streamlined and efficient experience. On the other hand, this approach can limit creativity and stifle innovation. So, what’s the verdict? Let’s take a look at the pros and cons of tying design to product so that you can make an informed decision for your organization.</p><h3>The pros of integrating designers into product teams:</h3><h4>1. Increased efficiency</h4><p>Tying design to product can provide a massive increase in efficiency. This is because there is less need for coordination and meetings between different departments (such as marketing, engineering, and design) when everyone is working towards the same goal with the same set of people. Additionally, having a clear design direction from the start can help save time during the development process because engineers can map out software architecture in parallel with designers as long as the high level design direction is set.</p><h4>2. Greater accountability</h4><p>When design is tied to product, designers are more likely to be held accountable for their work. This is because their impact is directly measured by the success or failure of the product. As such, designers will be motivated to create high-quality designs that deliver value to the company, and not be distracted by creative ideas that do not serve the organization’s needs.</p><h4>3. Better user experience</h4><p>Integrating design into product teams can lead to a better overall user experience. Product managers, engineers, and designers all bring different perspectives on the constraints they’re creating the product within. Product managers understand business needs, engineers understand technical abilities and limitations, and designers understand what resonates with users. By having them work together as a team, it will be easier for them to identify what is feasible and make the optimal compromises, avoiding situations where the implementation is nothing like the design simply because constraints weren’t considered holistically.</p><h3>The cons of integrating designers into product teams:</h3><h4>1. Less innovation</h4><p>One of the biggest disadvantages of tying design to product is that it can limit creativity. This is because designers may feel pressure to conform to the existing product metrics and minimize technical changes rather than experiment with new ideas with metrics more fitting to design innovation. As a result, innovative solutions may be overlooked in favor of more predictable ones.</p><h4>2. More siloing</h4><p>Integrating design into product teams can also lead to more siloing of solutions. This is because designers may be too focused on specific tasks rather than the big picture, which could lead to solutions that are not well-rounded across the system. Additionally, having less collaboration between departments means ideas may be created in a vacuum, without considering potential solutions from other teams.</p><h4>3. Greater External Pressure</h4><p>Finally, tying design to product can also lead to greater pressure from stakeholders to conform designs to specific requirements rather than exploring different options fully. This can be difficult for designers who may feel that their creative vision or research rigor is being sacrificed in order to work around technical constraints and deadlines. As such, it’s important to establish a clear balance between design and product decisions. A successful integration gives designers enough control over the resources needed to adequately explore vision and conduct research to ensure the best user experience.</p><p>Overall, integrating designers into product teams can have a number of benefits including increased efficiency, greater accountability, and better user experience. However, it is important to note that there are also some potential downsides to this approach such as less innovation and flexibility. It is also not an all-or-nothing choice. Organizations can also choose to have some designers work within product teams and others in a separate but connected role. Ultimately, the best approach for any organization will depend on its individual needs and goals, and it is up to each team to design a balanced solution what works best for them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a21c5d8c32a6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-pros-and-cons-of-integrating-designers-into-product-teams-a21c5d8c32a6">The pros and Cons of Integrating Designers into Product Teams</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[Career ladder from junior to director — guidance for UX professionals]]></title>
            <link>https://medium.com/design-bootcamp/career-ladder-from-junior-to-director-guidance-for-ux-professionals-1b5f9b2bd6b8?source=rss-32bc279208c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b5f9b2bd6b8</guid>
            <category><![CDATA[career-ladder]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jing Jin]]></dc:creator>
            <pubDate>Tue, 28 Jun 2022 21:42:49 GMT</pubDate>
            <atom:updated>2022-07-08T04:21:27.491Z</atom:updated>
            <content:encoded><![CDATA[<h3>Career ladder from junior to director — guidance for UX professionals</h3><p><em>This is a cleaned-up version of career guidance I’ve written for the UX team at Outschool. The company was 200 people total, and the UX team consisted of 15 product designers, visual designers, user researchers, and UX writers. I hope this is a helpful data point for people looking to advance in their careers as well as people creating career ladders for their teams.</em></p><p><em>Outschool has 6 levels for non-executive employees, roughly corresponding to junior, mid-level, senior, lead, and director (Outschool doesn’t use these titles). There are parallel tracks for individual contributors and people managers starting at level 4. This guide is a companion to a more detailed“Leveling Rubric” Outschool has, which defines competencies x levels. The Leveling Rubric is referenced but not shared here.</em></p><h3>Overview</h3><p>A <em>career ladder</em> is a tool that helps the company attract and retain employees. It is also a progression framework that documents the path(s) an employee can take as they develop their career within the company. A career ladder can have one or more tracks on one dimension, and multiple levels on another dimension, and the tracks can split or merge on certain levels.</p><figure><img alt="Levels 1–3 visualized as a train track, where the sigle track splits after L3 so that L4, L5, L6 have parallel IC and management tracks" src="https://cdn-images-1.medium.com/max/1024/0*_uA8nkW4y5BysH8q" /></figure><p>A leveling rubric describes expectations for different levels in the career ladder and provides detailed information to map out a path from one level to another. A leveling rubric is not meant to be a checklist that one can tick to unlock a promotion to the next level. Rather, it is meant to serve as a guide to employees and their managers regarding career progression within the company. It is a way to indicate areas that employees may need to improve in to move up to the next level. <strong>The leveling rubric should act as a compass rather than a GPS. </strong>A compass is a tool that gives one a general direction allowing someone to find their own way as opposed to a tool like a GPS that gives someone a specific route to follow.</p><p>An employee’s level is largely defined by the business impact that they produce (not just the skills they exhibit). Their impact is highly correlated to their levels. The larger the impact is, the higher their level is. However, in order to determine impact, we must first define what impact is.</p><h3>What is Impact</h3><p>Impact at any company can be described in terms of its mission and how much an employee contributes to achieving that mission. (What is a “mission” is a topic for another day, but a mission should differentiate one company from others — so it should be more unique and purposeful than “reach $10M in revenue”)</p><p>While impact is not always easily measured, we can consider it from 3 core pillars.</p><ul><li><strong>Consistency</strong>: How is the employee delivering impact over time? Is the employee able to deliver their work (i.e features, projects, process improvements, etc) not just once or twice, but consistently?</li><li><strong>Velocity</strong>: What is the rate at which the employee is delivering impact? Is the employee able to deliver their work on time consistently?</li><li><strong>Value</strong>: What is the value of the impact that the employee is producing? What is the value in relation to the levels in our career progression framework? More senior levels are expected to deliver more value in their work.</li></ul><h3>How to Determine Impact</h3><p>To determine the impact of an employee, a manager needs to view it in terms of the outcomes of the initiatives the employee contributed to, how the employee contributes their expertise and influence, and how those contributions map to the competencies in the Leveling Rubric. The answers to these questions will help the manager get a better understanding of the type of impact the employee is having in the organization.</p><figure><img alt="Outcomes come from various contributions, and each contribution is possible due to specific competencies in the rubric." src="https://cdn-images-1.medium.com/max/1024/0*1aCSKSKtPW1i0BbX" /><figcaption>Outcomes come from various contributions, and each contribution is possible due to specific competencies in the rubric.</figcaption></figure><h3>Leveling Rubric</h3><p>Overall, lower levels have a smaller area of focus and are more about demonstrating domain expertise, and higher levels have a larger area of focus and are more about demonstrating impact.</p><p>As the IC (Individual Contributor) and manager tracks split at L4, the start of leadership levels, different competencies are expected for different tracks, even at the same level. ICs are expected to demonstrate impact through the breadth and depth of their domain expertise, while managers are expected to demonstrate impact through <a href="https://www.dougdickerson.net/2019/08/04/how-to-leverage-your-influence-as-a-leader/">leveraging their influence</a> on different domain experts.</p><p>An L1–3 usually has a specific specialty within UX that they are focusing on, while L4–6 may either be experts in their specialty or generalists. Experts achieve impact through most effectively using their specialty, while generalists utilize a variety of specialties (either via their own skills or by leveraging other experts) to achieve impact.</p><figure><img alt="Areas of focus grow in scope at each level, from yourself in L1 to company in L6. At L3 your area of focus starts being more about your team, at L4–5 your area of focus starts being more about the function." src="https://cdn-images-1.medium.com/max/992/0*ImodK5XlAiX7YMzY" /><figcaption>Areas of focus grow in scope at each level, from yourself in L1 to the company in L6</figcaption></figure><h3>Level 1:<em> (e.g. Junior Designer, Junior Researcher, Associate Writer)</em></h3><p>This level is considered entry-level. At this level, the employee is expected to know the basics of their UX specialty. They are able to solve tightly scoped tasks with some supervision from more experienced mentors within the same specialty. An area of focus is improving their craft and learning how to be a productive, self-reliant UX professional with little supervision from others. For example, they are learning how to create a page layout, how to conduct usability testing, or how their research questions contribute to delivering a better experience. The career progression of an employee at this level is expected to be faster. Typically, an L1 employee is expected to progress out of the L1 within a year or two.</p><h3>Level 2: (e.g. <em>Mid-Level Designer, Researcher, Writer, etc)</em></h3><p>An employee at this level has a good understanding of the fundamentals of user experience. They are able to autonomously execute defined projects within their team’s areas of responsibility. They can independently define the right solutions to solve problems and execute from discovery to delivery. Although the focus is still on how to improve skills and knowledge in their specialty, they are beginning to expand their impact to others in the team through co-creation and feedback. They collaborate with others in their functional areas such as PMs, engineers, designers, data scientists, researchers, managers, and others to get the work done. Typically, an L2 is expected to progress to the next level within a couple of years.</p><h3>Level 3: (e.g. <em>Senior Designer, Senior Researcher, Senior Writer)</em></h3><p>This level is the first inflection point where leadership is a defining requirement. An employee at this level is expected to lead projects within their team’s area of responsibility. They are able to define milestones for and deliver well-scoped projects. At this level, the employee is expected to demonstrate functional skills in common user experience concepts as well as mastery in their specialty, and knows when to seek advice from other specialties to create the best outcome.</p><p>For example, common user experience concepts include wireframing, user interviews, affinity diagramming, usability testing, user flows, competitive analysis, personas, etc. Specialty concepts for a Designer include color theory, rapid prototyping, responsive design, etc. Specialty skills for a Researcher include survey design, diary studies, meta-analysis, etc. Specialty skills for a writer include taxonomy, content guidelines, etc.</p><p>The employee may also be expected to lead and or mentor others in their specialty, and possibly manage a contractor to contribute to their projects. This is also the level where we expect employees to do more than merely completing the work that’s been assigned to them. They have a good understanding of the company and team goals and are able to connect those goals to the work that they are doing. They also keep the business needs in mind and leverage input from product stakeholders to determine the right solutions in order to deliver value.</p><p>Additionally, they are starting to create their own work by understanding the problems the team faces, implementing, and delivering the solutions to those problems. Typically, the progression of an employee in this level starts to slow down due to the amount of learning required for this level.</p><p>At this level, there is no longer a default expectation that they will eventually be promoted to the next level, so you can choose to stay at this level indefinitely.</p><p>This is also the level at which the employee starts to consider which of the two tracks to pursue. Either the employee will continue the IC track or switch over to the people management track.</p><h3>Level 4</h3><p>An employee at this level is setting a medium-to-long-term strategy for business-impacting projects. This level is an inflection point, where the employee is defining and leading complex work across teams, amplifying impact through other people, and proactively seeking and creating opportunities to be effective beyond their own team. Effectively, <strong>an employee at L4+ is “helping the manager do their job” more than “the manager helping the employee do their job”</strong>, and becomes a collaborator and thought partner to the manager. There is no expectation to move beyond this level.</p><p>Starting at this level, the IC and manager tracks differ in how they achieve these outcomes.</p><h4>IC Track: (e.g. <em>Design Lead, Research Lead, or Lead Writer)</em></h4><p>The IC starts leading cross-functional projects that impact multiple teams. They initiate and successfully drive challenging initiatives that cut across multiple teams’ work, projects and processes. They are considered an expert in their part of the business or domain, a strong communicator, a mentor, and role model even to experienced UX professionals, a driver of best practices, and have delivered multiple projects that move the needs of their team. They actively keep customer needs in mind and leverage stakeholders in order to determine the appropriate solutions in order to deliver value.</p><p>The IC may also manage an intern seasonally, or manage 1 other employee during a transitional period as a path to the manager track.</p><h4>Manager Track: (e.g. ___ Manager)</h4><p>At this level, a manager is expected to be responsible for the impact of 2+ ICs working on similar, related areas. They empower their direct reports (DRs) to successfully deliver impact through coaching, being a conduit of information, and building trust and resolving conflict with the DRs’ stakeholders. A manager at this level is learning to shift their method of impact from “I can do this” to “I can teach my team to do this”. Their main focus is to conduct coaching, training, and hiring, only taking on direct hands-on work as a short-term solution to resource constraints or as a way to train their DRs.</p><p>The manager may manage various specialties in order to deliver impact for their area. While the manager isn’t expected to be an expert in all specialties they manage, they’re expected to have basic knowledge of each specialty and be aware of their blind spots and seek advice from leaders in other specialties when providing training, assigning work, or evaluating their DRs.</p><h3>Level 5</h3><p>At this level, the employee is expected to solve problems and deliver solutions that consistently impact the entire UX organization, and often multiple organizations in Outschool. They are essentially force-multipliers who amplify their impact through other teams by creating opportunities to be effective throughout the entire organization. There is no expectation to move beyond this level.</p><h4>IC: (e.g. <em>Principal ___, ___ Architect, ___ Strategist)</em></h4><p>An IC at this level is increasingly influential on product decisions and scope, as well as determining the right tradeoffs to deliver customer value. They are able to align UX strategy for several projects that cut across groups of pods or functions. They demonstrate a high level of depth in a particular product category. They will often “hunt work” by identifying and formalizing the problem, devising a solution, getting leadership buy-in, leading its implementation, and disseminating information to others. They are often leading other ICs and contractors on their initiative, though that is not a requirement. They are expected to actively mentor others in the Design function. They are seen as a critical strategic partner by other functions.</p><h4>Manager: (e.g. <em>Senior Manager of ___ or Director of UX)</em></h4><p>At this level, a manager is expected to handle increasingly complex organizational needs. They are responsible for multiple DRs working on areas that may not be related, potentially also managing other managers. They will develop strategies for systematic and scalable solutions that improve organizational efficacy, and iteratively execute on it. They will utilize a wide variety of management toolkits beyond individual coaching and troubleshooting. There is no expectation to move beyond this level.</p><h3>Level 6</h3><p>An employee at this level is amplifying their impact not only through the entire company but also beyond the company. They partner with cross-functional stakeholders to identify major new business opportunities unlocked by UX capabilities. They contribute to strategy on broader organizational design, and proactively consider team design and skills integration ahead of any hiring. They consider the economic impact of every product, process, and team decision as well as the cost/benefit analysis of those decisions. They are considered an expert by the industry beyond Outschool, and they utilize their reputation and network to increase the recruitment and retention of talent. There is no expectation to move beyond this level. The next promotion level of them is the executive level, if and only if the company has a need for an executive with this type of expertise.</p><h4>IC: (e.g. <em>UX Architect, UX Strategist)</em></h4><p>An IC at this level aligns the UX strategy for high-risk high-reward projects across several groups to the broader initiatives of the company.</p><h4>Manager: (e.g. <em>Director of UX)</em></h4><p>A manager at this level designs their organization to unlock different ways of working that allow ICs to pursue complex high-risk high-reward projects. They create effective and replicable systems that often also level up other organizations via influence and knowledge-sharing.</p><h3>Moving Between Levels</h3><p>While levels are presented as integers, the progression between levels is more of a continuum. For example, two employees could both be Level 2, while one of them is working toward consistently showing L2 competencies, the other one could be working toward showing more L3 competencies.</p><p>While L1 and L2 employees are expected to eventually reach L3 if they follow the guidance their managers have given, an L3 employee is not expected to move levels simply because they have followed their manager’s guidance. An L3 can stay a valuable member of the team without ever moving to L4. Employees who wish to work toward levels beyond L3 are expected to go above and beyond what is expected at their current level, proactively engaging in conversations with their manager about how they can grow beyond their current level.</p><h4>Moving Up a Level</h4><p>Promotions are expected to happen faster at lower levels and slower at higher levels because competencies at higher levels are more complex and take longer to demonstrate. An L1 can demonstrate enough competencies to be promoted to L2 in under 2 years, while an L5 could take many years to demonstrate enough competencies to be promoted to L6.</p><p>An employee can be recommended for promotion (moving to a higher level, let’s call it L+1) by their manager during a formal review cycle when their manager is confident the employee can consistently demonstrate the L+1’s competencies. This usually means the employee has already exhibited some L+1’s competencies consistently, and their rate of growth extrapolates to predict that they will master a solid set of L+1’s competencies within a year. While the official process to promote an employee is through manager recommendation during a review cycle, <strong>an</strong> <strong>employee who hopes to be promoted is expected to start a conversation with their manager before the review cycle begins</strong>. Ideally, the employee should start talking to their manager about how to demonstrate more L+1’s competencies <a href="https://askgib.substack.com/p/whats-the-right-way-to-ask-for-a?s=r">a year before they hope to be promoted</a>.</p><p>If a promotion adds significantly different responsibilities, the manager is expected to check with the employee if they desire those responsibilities. An employee can also decline a promotion that will add responsibilities.</p><p><em>Is this helpful information on how to grow to your next level? Does your company use a similar system for its promotion levels? How can this system be improved? I’d love to hear your suggestions and ideas!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b5f9b2bd6b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/career-ladder-from-junior-to-director-guidance-for-ux-professionals-1b5f9b2bd6b8">Career ladder from junior to director — guidance for UX professionals</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[Why Making Your Bed Increases Productivity]]></title>
            <link>https://jingidy.medium.com/why-making-your-bed-increases-productivity-393e4f273275?source=rss-32bc279208c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/393e4f273275</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[cleaning]]></category>
            <category><![CDATA[quarantine-hacks]]></category>
            <dc:creator><![CDATA[Jing Jin]]></dc:creator>
            <pubDate>Sat, 23 Jan 2021 19:55:06 GMT</pubDate>
            <atom:updated>2021-01-23T20:08:28.895Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m a big believer in efficiency. My clothes are grouped into shirts/pants/jackets so I can pick my outfit faster. I save a stack of dishes to wash together to reduce context switch time. I eat <a href="https://en.wikipedia.org/wiki/Go-Gurt">Go-Gurt</a> for breakfast because I can walk/bike at the same time. And I never make my bed when nobody but me is going to see it. Until now.</p><p>I haven’t departed from my belief in efficiency. I’ve discovered that making my bed is a deceptively simple way to increase my productivity throughout the day. Talk is cheap, let’s prove it with math:</p><p><strong><em>ROI = productivity / timeToMakeBed</em></strong></p><p>It takes me about 10 seconds to make my bed, but I have a very simple setup: 2 pillows, a down comforter, and a fitted sheet. I don’t know what kind of bed the average person has, but judging from furniture catalogs it seems like two flat sheets and a few decorative pillows are involved. So let’s say it takes an average person 60 seconds to make the bed.</p><p><strong><em>ROI = productivity / 60s</em></strong></p><p>And here are all the things you accomplish in 60 seconds by making your bed:</p><ol><li>You’ve already accomplished 1 quick win, and <a href="https://www.inc.com/benjamin-p-hardy/this-one-idea-from-atomic-habits-will-change-your-life.html">atomic habits</a> like this are a proven way to increase your overall productivity.</li><li>Every time you walk past your bed, you’re reminded of your accomplishment. And it looks nice. These tiny boots to your brain’s reward system reinforce the habit and just plain makes your day happier.</li><li>You’re creating a clear visual difference between your “seize the day” mode and “rest and relax” mode. Our memory is very context-dependent, and being in the same environment makes it easier for the same neurons to fire, be it for <a href="http://www.rethinkstudying.com/study-environment/">getting a better test score</a> or for being more focused on work.</li></ol><p>So how much time would you invest for starting your day feeling accomplished, staying focused throughout the day, and the ascetic appeal of an organized environment? How much time do you spend getting coffee? Eating breakfast? Or any other “start the day right” habit? I bet most of them take more than 60 seconds.</p><p>So. 1) Make your bed. 2) ??? 3) Profit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*Pkl_9KjE015p9O3BglaH1w.png" /></figure><p><em>P.S.</em></p><p><em>I actually wrote 90% of this article 5 years ago. I don’t eat Go-Gurt anymore, but I still make my bed everyday. Except… I have a Murphy bed now, and I’ve maximized the utility of my 9&#39;x10&#39; room with the Murphy bed folded up: it’s my office, my pole dance studio, plant nursery, and still has space for a couch where I do my “relaxing” activities. I’m a pretty big believer in </em><a href="https://youtu.be/snAhsXyO3Ck"><em>separate spaces for separate activities</em></a><em>.</em></p><p><em>So in one sense the habit of making my bed has allowed me to turn one room into 4. Or you can say I’m more motivated to make my bed because of the extra value of all these extra “rooms” I get from it. Either way, it’s a great ROI habit and I still highly recommend it.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=393e4f273275" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Mistakes in Rookie Design Portfolios, and How to Fix Them]]></title>
            <link>https://medium.com/interactive-mind/3-mistakes-in-rookie-design-portfolios-and-how-to-fix-them-ed6b2c2a27e1?source=rss-32bc279208c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed6b2c2a27e1</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[junior-designer]]></category>
            <dc:creator><![CDATA[Jing Jin]]></dc:creator>
            <pubDate>Sat, 02 May 2020 23:30:30 GMT</pubDate>
            <atom:updated>2022-09-23T00:15:40.501Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Are you fresh out of school or looking for your first design gig after a career transition? Based on years of experience interviewing and mentoring UI/UX designers, web design designers, product design designers, and visual designers, these are the most common mistakes I see, and how to fix them.</p><h3>Mistake #1: Your portfolio is hard to skim</h3><p>Hiring managers are busy. For a recent job I listed, I had about 10 incoming applicants a week, but only have time to phone interview 3. And this is in addition to my day-to-day responsibilities, which is already taking all of my time (that’s why I’m hiring).</p><p><strong>As the hiring manager, I spend about 5 minutes per portfolio</strong> — and I’m trying to see 2–3 projects in that time.</p><p>Hiring managers need to be able to skim:</p><ul><li>Final deliverable — bonus if you can state the impact of these deliverables</li><li>Your team and role — which part of the deliverable was yours vs. your team’s</li><li>Scope — expectations are different for a 2-week project vs. a 6-month project</li><li>Realness — real stakeholders&gt; solo case study, solo case study &gt; nothing, but if you try to disguise case studies as real, it’ll leave a bad taste when the manager finds out</li></ul><h4>The Mistake</h4><p>Reading. Like. A. Novel. Especially for the more lengthy projects — where they best demonstrate your range of skills, and it’s a huge loss of opportunity.</p><h4>The Fix</h4><p>Make sure your reader can get a general idea for these as they scroll through your project. You can summarize the project brief up top, highlight key points within a paragraph, or use good ol’ visual hierarchy of font treatments to achieve a more skimmable story.</p><p>Here’s an example of a good summary…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/455/1*v1OxLGAyveouH7QnoaaxRw.png" /><figcaption>Credit: <a href="https://www.angela-hui.com/literatorproject">Angela Hui</a></figcaption></figure><p>And here’s an example of good use of highlighting…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/785/1*boUxvwPjoib5rWF2cmuigA.png" /><figcaption>Credit: <a href="https://www.judy-chun.com/privacy-manager">Judy Chun</a></figcaption></figure><p>Then as all good designers do: get feedback. Try a variation of the <a href="https://articles.uie.com/five_second_test/">5-second test</a> — give your friends 1 minute to skim through a project and ask them what they remember.</p><h3>Mistake #2: You say what you did but not why</h3><p>Hiring managers are looking for these things from junior designers:</p><ol><li>Basic skills — do you have a basic practical understanding of the tools and methods you’d encounter on the job</li><li>Trainability — are you thoughtful and reflective, trying to improve after each experience</li><li>Raw Talent — do you shine in a particular area that sets you apart from others with a similar level of experience</li></ol><h4><strong>The Mistake</strong></h4><p>Many people focus on demonstrating basic skills and raw talent but forget the most important trait: trainability. <strong>Trainability is demonstrated through thoughtfulness beyond what is minimally required.</strong></p><p>A lot of projects read like <em>“Here’s our wireframes. Here’s the research we did. Here are the final designs.”</em></p><p>The problem with this is that there is no indication that you made thoughtful decisions, just that you were following prescribed steps. It communicates that when you start a job, you’ll follow what is given but not proactively seek out opportunities for improvement — both in your projects and in your career.</p><h4>The Fix</h4><p>The ideal design process involves multiple iterations between design and feedback/research, so you should clearly <strong>show the connection between each iteration and how one stage influenced the next stage</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mNZ-HLn4sAb4qHARgteY9Q.jpeg" /><figcaption>Ideal process where each iteration is influenced by feedback and/or user testing results.</figcaption></figure><p>Your project should read like “<em>Here’s our wireframes. We tested these parts because we wanted to understand X. The results showed Y, which is why we did Z in our final design.</em>”</p><p>But the world isn’t perfect. You had limited time and weren’t able to do 100% of the things you wanted. <strong>Turn limitations into opportunities to demonstrate your thoughtfulness:</strong></p><ul><li>Didn’t have time to do user research → Due to the tight project timeline, I decided skip user testing in favor of speed. If I had time to conduct research… (outline what you would test)</li><li>Inconclusive results → My hypothesis is that the mixed results due to X. If I was to conduct another round of research I would do Y.</li><li>Didn’t have time to revise based on feedback → Due to limited time, I prioritized fixing A instead of B because XYZ.</li></ul><p>Another way to show that you thought about the “why” — not just the “what” — is through a Lessons Learned<strong> </strong>section. <strong>Lessons Learned shows that you’re able to learn something that you can take beyond the project at hand</strong> — be it a personal skill or an understanding of this user audience.</p><p>Here are some examples…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/1*oi47rNF_BuZOGTlUwhRhDA.png" /><figcaption>Credit: <a href="https://www.laurenchandlerdesign.com/work/bookr">Lauren Chandler</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*f0T8qIRjUMJt6VxFAkLsOw.png" /><figcaption>Credit: <a href="https://aakriti-chugh.in/gokart-labs.html">Aakriti Chugh</a></figcaption></figure><p>Writing about the why of your decisions, and showing how you can bring your learnings to the next project shows hiring managers that you are <strong>communicative, reflective, and eager to learn</strong> — all traits of a highly trainable designer.</p><h3>Mistake #3: Not polishing your portfolio like a design</h3><p>Everything you show a prospective employer is a design artifact you delivered — be it the cover letter, your resume, or your portfolio.</p><p>Depending on your specialty, you’ll get more passes for certain areas and be more strictly judged on others. For example:</p><ul><li>UX designer — your portfolio should have clear information hierarchy and be easy to use on any device</li><li>Visual designer — your portfolio should look beautiful and demonstrate your unique style</li><li>UX researcher — your portfolio should be logical, clearly demonstrate your influence, and be written for your target audience</li></ul><h4>The Mistake</h4><p>I’ve seen so many ways portfolios are incongruent with how the designer presented themselves, such as:</p><ul><li>a UX designer with flickering scrolls in their portfolio</li><li>a web designer with a portfolio that’s not mobile friendly</li><li>a visual design portfolio that has pixelated images</li><li>a product designer with mostly graphic design projects in their portfolio</li></ul><h4>The Fix</h4><p>Just because your portfolio is a design doesn’t mean you have to design it from scratch. As a designer, one of your skills is delivering the best design with limited time, so focus on what is <strong>the best experience for the person reading the portfolio: getting to the information they’re seeking as smoothly as possible.</strong></p><p>It’s totally fine to use existing layouts on sites like Squarespace and Behance. A portfolio design that leaves little impression allows the reader to focus on the content. A portfolio design that leaves a big impression will make you more memorable, but if it leaves a big negative impression, then that’s worse than leaving no impression.</p><p>A few rules of thumb to follow:</p><ul><li>Simple but smooth is better than special but buggy</li><li>Tell a coherent story about you, remove works that don’t serve that story</li><li>Empathize with your portfolio’s end user</li><li>Test on several devices and browsers</li></ul><p>If you avoid mistakes #1 and #2, and serve reader’s needs before bells and whistles, you’ll naturally end up with a well-made portfolio.</p><p><em>Looking for more guidance on your portfolio? </em><a href="https://medium.com/design-bootcamp/if-your-ux-portfolio-has-this-20-well-done-it-will-give-you-an-80-result-a129f048d8a7"><em>This great article</em></a><em> goes into a lot more detail on how to do some of the things I’ve recommended.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed6b2c2a27e1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/interactive-mind/3-mistakes-in-rookie-design-portfolios-and-how-to-fix-them-ed6b2c2a27e1">3 Mistakes in Rookie Design Portfolios, and How to Fix Them</a> was originally published in <a href="https://medium.com/interactive-mind">Interactive Mind</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons Learned on Creating Focus at Literator]]></title>
            <link>https://jingidy.medium.com/lessons-learned-on-creating-focus-at-literator-ac8b0bc0db49?source=rss-32bc279208c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac8b0bc0db49</guid>
            <category><![CDATA[company-values]]></category>
            <category><![CDATA[product-focus]]></category>
            <category><![CDATA[value-proposition]]></category>
            <category><![CDATA[example]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Jing Jin]]></dc:creator>
            <pubDate>Sat, 02 Feb 2019 22:49:21 GMT</pubDate>
            <atom:updated>2019-02-12T19:20:09.735Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>How to Create Focus for a Startup: Real-World Examples from Literator</h3><p>In the last 12 months, Literator has grown a lot — we started our first cohort of paid pilots and have grown to 4,000+ schools world-wide. Over dozens of releases on multiple platforms and hundreds of customer conversations later, we’ve learned a lot about how to grow while staying focused.</p><p><strong>The internet is full of advice and frameworks, but not many real-world examples, so I’d like to share 3 artifacts that we use at Literator: company values, value props, and product focus guidelines.</strong></p><p>These examples are most useful for people on a small team that’s already shipped an MVP and fixed the low-hanging fruits (if you are pre-product, <a href="https://medium.com/interactive-mind/how-to-create-a-kick-ass-product-7d525d032e20">this other article</a> I wrote will be more helpful).</p><p>If you feel like your product just isn’t “leveling up” despite everyone working hard, then frameworks like the ones shown below can help you discover where the problem is.</p><h3>Company Values</h3><p>Defining your company’s core values is important for a variety of reasons. <a href="https://7geese.com/benefits-of-having-core-values-and-how-to-set-them-in-your-organization/">This article</a> does a great job of going into the what, why, and how… so I’ll fast foward to showing you Literator’s core values:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ofMzlUCMYn1sr2ebbCTaVw.jpeg" /><figcaption>Literator’s values</figcaption></figure><p><strong>We share this document with every employee and contractor. </strong>We have it pinned up in the office. It’s helped us come to a consensus faster on many decisions , such as:</p><ul><li>Have you ever had a terrible day but you had to put on a brave face for some really important meeting? At Literator, when someone asks “I’m not in a good place today, can we do this tomorrow?” We always say “Yes.” — no judgement — because we’d rather you take care of yourself, and come back when you can perform your best. — Our value of sustainable culture.</li><li>We sent a December newsletter about self care because we knew it was a really hard month for teachers, even if the content had anything to do with Literator. — Our value of teachers first.</li><li>We discussed shuttering the free product so we can focus on our paid product, but decided against it because we are committed to making a difference, even if it’s a very small difference, for teachers and schools that can’t afford it. — Our value of committed to equity.</li></ul><p>Every company is different and there are no right or wrong values. Some of the decisions that were right for our company can be completely wrong for a company that holds different values. This is simply an example of what values can look like and how they can be used to make decisions.</p><h3>Value Props</h3><p>After our first few releases, we fell into what I can only describe as “running in quicksand”: our team had to re-align on <a href="https://www.quora.com/What-is-the-difference-between-product-description-and-product-value-proposition">value props</a> for every major release (which took hours), feature requests all seemed equally critical, and we were using business/product/value/lean canvases but we iterated so fast that we need to completely revamp them every release.</p><p>I desperately needed a one-glance visual that can be my team’s starting guide for every discussion. Like setting an intention for a meditation session. The answer to our problem is this pyramid:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QAGMP_O7-ULwEzdUnDM7Ig.jpeg" /><figcaption>An educator’s Maslow’s hierarchy of needs</figcaption></figure><p>This was the result of digging back through 3 years of user feedback, cross-checking it with our 5-year and 10-year visions, and validating with the rest of the company. We used the shape of Maslow’s hierarchy because it represented the relationship between Literator’s value props.</p><p><strong>We use this visual for every strategy and tactics meeting — it helped aligned our sales, support, design and engineering efforts over multiple releases. </strong>It gave us a clearer way to think of our priorities, and allowed us to refer back to a common vocabulary. The result was intangible but clear — our meetings were shorter and had clearer conclusions because there was less arguing and we came to a consensus faster.</p><h3>Product Focus Guidelines</h3><p><strong>The product team uses the guidelines to decide on granular tradeoffs during planning, design, and the inevitable cutting-tasks-to-ship-on-time phase.</strong></p><p>For brevity, I’ll focus on 2 examples in our guideline:</p><h4>1. The only opinion that matters is one that follows up with money</h4><p>A startup’s core market is people who are already willing to pay you — really kill their problems and find more people like them. We follow this formula:</p><p><em>current customer &gt; churned customer &gt; current free user &gt; churned free user</em></p><p>When we had to decide between the ability to “import custom skill packs” (request of current customers) or fixing the “onboarding experience” (feedback from churned customers), we decided to do the former since it is feedback from current customers. As a result, we had better retention and more schools interested in purchasing us because of this new feature.</p><h4>3. Focus on the value props</h4><p>In our Product Value Props visual, the bottom of the pyramid must be “stable” — don’t design features for the higher levels if they weaken the foundation. (Just like Maslow’s hierarchy of needs)</p><p>Also, MVP is not neccessarily just 1 feature. MVP solves 1 problem, even if it involves multiple features, to provide reward &gt; effort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*_UnGMHBoeZbpQmVE3JJw_Q.png" /><figcaption><a href="http://futureofwork.nobl.io/future-of-work/start-with-a-skateboard-how-spotify-builds-products">Source</a></figcaption></figure><p>When we were planning for the release of Student Groups on mobile, we didn’t have the resources to ship the full feature set, which included: displaying a list of skills (#1), rating each skill (#2), taking free-hand notes (#3), on both Android and iOS (#4).</p><p>Using the above guideline, we knew that delivering the value prop “everything in 1 place” was more important than platform parity, and we knew that free-hand notes satisfy more data-entry situations than rating skills, so we decided to ship displaying a list of skills (#1) and taking free-hand notes (#3) on only iOS.</p><p>With this tighter scope, we were able to ship a quality release of Student Groups instead of scrambling to finish on time, and these features immediately provided teachers with a complete solution to their problem.</p><h3>Your mileage may vary</h3><p>These 3 artifacts — Company values, Value props, and Product focus guidelines— are not one-size-fits-all. We’re a small team, newcomers to the market, and everyone works on every product. I have no idea if it’ll work for large teams, products that have saturated the market, or teams that are more silo’d.</p><p>I only briefly touched on each topic, but I hope this was helpful. Would you like to read a full article on Company values, Value props, or Product focus guidelines? Or have you done similar things with bigger teams or more mature products? Let me know in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac8b0bc0db49" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EdTech Sales & Efficacy — Lessons from SXSWedu 2017]]></title>
            <link>https://medium.com/literator/edtech-sales-efficacy-lessons-from-sxswedu-2017-a2aa118cba68?source=rss-32bc279208c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2aa118cba68</guid>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[sxswedu]]></category>
            <category><![CDATA[sxsw]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[edtech]]></category>
            <dc:creator><![CDATA[Jing Jin]]></dc:creator>
            <pubDate>Mon, 27 Mar 2017 18:42:01 GMT</pubDate>
            <atom:updated>2017-03-27T18:42:01.065Z</atom:updated>
            <content:encoded><![CDATA[<h3>EdTech Sales &amp; Efficacy — Lessons from SXSWedu 2017</h3><h3>Lesson 1: Being trustworthy is essential in selling to schools</h3><p>This is a “duh!” to most people in EdTech, but I learned some pretty surprising things about what “trust” actually means at SXSW.</p><p>Most districts &amp; vendors avoid RFPs as much as possible. But there is no established alternative for purchasing, so educators rely on many channels to discover new tools:</p><ul><li>District leaders are going to <strong>marketplaces</strong> &amp; <strong>consortiums</strong> to discover good products</li><li>90% of EdTech purchasing happens by word of mouth</li></ul><h4>Success in 1 school doesn’t mean success in any school.</h4><p>What makes for success in a large school may not work in a small school, and vice versa. So references need to be from comparably-sized places:</p><ul><li>Referrals need to come from colleagues from comparable districts/schools/classrooms <em>(e.g. a superintendent recommending to a superintendent 0f a similar district is much stronger than a superintendent of a large district recommending to a superintendent of a small district)</em></li><li>Use case studies &amp; data to support your case, especially from similar schools/districts</li></ul><h4>Understand budget cycles, but don’t use it as unfair leverage.</h4><ul><li>Budget cycles are different for software than, say, budget cycles for construction. Know which category you fall into.</li><li>“It’s predatory to call a district in May to see what money is left.”</li></ul><h3>Lesson 2: Empathy is *negatively* correlated with sales success</h3><p>I was shocked, but this is what they found in a study of over 500 salespeople in 44 companies. Top salespeople…</p><ul><li>Care about money the most. <strong>Not education. Not the mission.</strong></li><li>Are all <strong>ambitious</strong> (make the quota), <strong>detailed-oriented</strong> (due diligence), and <strong>persistent</strong> (always gets the real reason behind a lost sale)</li><li><strong>Good at using experts</strong> — top-peforming sales people do not have an education background, but are good at learning from educators.</li><li><strong>Quit quickly if they’re not getting supported</strong> — 30% of top salespeople leave the company within 1 year. Their stance is <em>“if I’m bringing in all the money, and you’re not giving me top-notch support, then you’re dragging down my performance.” </em>Support can be anything from providing training to having the best-in-class product.</li></ul><h4>Sales is a very different beast than the rest of your organization.</h4><p>A sales rep’s job is to make sure you get paid for the value you (supposedly) provide. <strong>If they sell your product, and your product doesn’t help the customer, that’s not the salesperson’s fault, that’s the product team’s fault.</strong></p><p>Similarly, in most of the company you want to support the underdogs to help them perform better. But in your sales organization, <strong>the bottom 10% will never out-perform your top 10%</strong>, and giving support to 10x-ers means you get 10x the value for your investment. So you should give all your support to the top 10% of sales reps and fire the bottom 10% of sales reps.</p><h4>That doesn’t mean you should hire a$$holes.</h4><p>Good sales reps see future sales opportunities and offer “free” help to customers who are well-qualified for a purchase in the future. They still help people, but they do it as an investment for their future, not for altruism.</p><h3>Lesson 3: Teachers need a little help using EdTech, but not the kind of help they’e been offered.</h3><p>A lot of traditional purchases from school districts become shelfware — tools that sound good in theory but are abandoned by teacher due to practical problems. One teacher said:</p><blockquote>“We’re making assupmtions that every person is data-literate in schools &amp; districts. But that’s not the teacher’s job. Our job is to teach.”</blockquote><p><strong>But just because teachers aren’t neccessarily data-literate doesn’t mean they’re not computer-literate:</strong></p><blockquote>“I don’t need training on how to use a tool, I can just google it. But I do need help telling the story of how this tool is going to change my practice and build success for <em>my</em> students.”</blockquote><p>What teachers need are tools that are low-risk to try. Teachers will pick up a product and try it quickly. But if the product requires the teacher to teach her students how to use it, she is much less likely to pick it up.</p><p>And pilots don’t need to take forever:</p><blockquote>“If your product is good, I only need 6 weeks of piloting to decide.”</blockquote><p>SXSWedu was a very informative blend of educators and techies. But what we got most out of SXSWedu is actually from our individual meetings with teachers &amp; administrators in Austin. Now that we have a good handle on the day-to-day realities educators experience in both California and Texas, we’re ready to transform <a href="https://literatorapp.com/?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=blogpost_20170325">Literator</a> so it supports an even larger set teaching styles.</p><p>We also discovered that teachers love to share what they’ve created with others. When we (timidly) ask teachers if we can post their posters/classroom setup/advise online, everyone gave us an enthusiastic yes!</p><p>If you’re interested in seeing what strategies teachers use in their classes, follow us on <a href="https://www.pinterest.com/literatorapp/">Pinterest</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2aa118cba68" width="1" height="1" alt=""><hr><p><a href="https://medium.com/literator/edtech-sales-efficacy-lessons-from-sxswedu-2017-a2aa118cba68">EdTech Sales &amp; Efficacy — Lessons from SXSWedu 2017</a> was originally published in <a href="https://medium.com/literator">literator</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Tips For Giving Good Criticism]]></title>
            <link>https://jingidy.medium.com/7-tips-to-giving-good-criticism-840c0a51d39b?source=rss-32bc279208c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/840c0a51d39b</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[employee-feedback]]></category>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Jing Jin]]></dc:creator>
            <pubDate>Sat, 29 Oct 2016 20:34:02 GMT</pubDate>
            <atom:updated>2016-10-29T20:38:47.982Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>Giving feedback, especially when it’s criticism, is hard. One often has to walk the line between not-clear-enough and too harsh. Why is it bad to be harsh? A lot of research has shown that feeling safe (both psychologically and physically) in the workplace is essential for high productivity. In <a href="https://rework.withgoogle.com/guides/understanding-team-effectiveness/steps/introduction/?utm_source=teams_promo&amp;utm_medium=social_blast&amp;utm_content=teams_guide&amp;utm_campaign=teams_launch">Google’s research</a> on their teams’ productivity, psychological safety was one of the basic pillars needed for high performance.</p><p><strong>Good criticism should:</strong></p><ol><li>Alert the critiqued to what can be improved</li><li>Teach the critiqued something that can be used in the future</li><li>Encourage the critiqued to seek more feedback in the future by making them feel capable of improving</li></ol><p>Here are 10 basic rules to abide by when you’re giving feedback on designs, code, proposals, or speeches:</p><h3><strong>1. Criticize the work, don’t criticize the person</strong></h3><p><strong>Good:</strong> “These sentences are run-ons. Can you fix them?”<br><strong>Bad: </strong>“You write a lot of run-on sentences. Can you fix that?”</p><h3>2. Explain the principle behind every critique</h3><p><strong>Good: </strong>“We always put braces here because it’s less prone to copy-paste errors, can you add that too?”<br><strong>Bad:</strong> “We always put braces here, can you add that too?”</p><h3>3. Use “we” instead of “you” whenever possible</h3><p><em>Because we’re all in this together =)</em></p><p><strong>Good: </strong>“Our signup design is confusing to a lot of users. Can you work on improving it?”<br><strong>Bad:</strong> “Your signup design is confusing to a lot of users. Can you work on improving it?”</p><h3>4. Recognize the both the good and the bad</h3><p><em>I call these shit-sandwiches: compliment-criticize-compliment. But that name is probably not SFW…</em></p><p><strong>Good:</strong> “I really like how you pull at the listener’s emotional strings, but I think we need to touch more on our business case too. Can you add it? You know best where it would fit naturally.”<br><strong>Bad: </strong>“We don’t touch on our business case enough, can you add that?”</p><h3>5. Use socratic questions to identify problems without suggesting solutions</h3><p><strong>Good: </strong>“What would happen if the user just walks away from this?”<br><strong>Bad: </strong>“This should auto-close if the user walks too far away.”</p><h3>6. Be aware of the relationship between critic and critiqued</h3><p><em>You are in a position of power as the critic, and if you also have seniority in your org, your negative words can sound like ultimatums. It’s ok to sarcastically say “ew, that color is gross” to a good friend, but it’s not ok to say that same thing to a junior designer.</em></p><p><em>In short, critiquing a stranger or someone junior will require more care and empathy. Politeness is key!</em></p><p><strong>Good: </strong>“The view seems like the wrong place to execute this code, is there a reason why it’s not part of the controller?”<br><strong>Bad: </strong>“Wrong. This belongs in the controller.”</p><h3>7. Be mindful of the scope of the critique and why it was requested</h3><p><strong>Good:</strong> “This wireframe makes sense but I’m curious to see if the buttons look too busy or not in the visual design.”<br><strong>Bad:</strong> “There are too many blocky buttons and I don’t like Comic Sans.”</p><p><em>All examples are real situations I’ve encountered at Apple, Literator, BazaarVoice, Fyusion, Marble, and Konsult. Thanks to </em><a href="http://trydesignlab.com/"><em>Designlab</em></a><em> for the original list for designers. Thanks to Matt for encouraging me to also make a list for engineers. </em>❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=840c0a51d39b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>