<?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 Oana Grigore on Medium]]></title>
        <description><![CDATA[Stories by Oana Grigore on Medium]]></description>
        <link>https://medium.com/@oelenagrigore?source=rss-3db4b209f042------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*RgSnLGbXrHda7Cmd.</url>
            <title>Stories by Oana Grigore on Medium</title>
            <link>https://medium.com/@oelenagrigore?source=rss-3db4b209f042------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:43:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oelenagrigore/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[The design hiring theater: stop looking for unicorns and start seeing people]]></title>
            <link>https://medium.com/@oelenagrigore/the-design-hiring-theater-stop-looking-for-unicorns-and-start-seeing-people-c00acef1f6ab?source=rss-3db4b209f042------2</link>
            <guid isPermaLink="false">https://medium.com/p/c00acef1f6ab</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Oana Grigore]]></dc:creator>
            <pubDate>Thu, 29 Jan 2026 17:33:46 GMT</pubDate>
            <atom:updated>2026-02-09T17:45:58.480Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eDoH8dpRsbh5ypHKT0QSLg.png" /></figure><p>We’ve made hiring designers into a high-stakes drama. Everyone is following a script, but no one seems entirely sure what the outcome is supposed to be.</p><p>If you’re a designer searching for work right now, you’re not just applying for a job; you’re also auditioning for a role in a corporate play. There are endless quick chats, portfolio deep dives, and technical tests that feel more like Figma competency checks than real conversations about how to solve problems.</p><p>It’s tiring. It’s unnecessary. And honestly, it points to a much bigger issue: the industry seems to have forgotten that design is a human field.</p><h3>1. The Unicorn</h3><p>Job descriptions are starting to look more and more alike. They’re filled with “nice-to-have” skills — some ambitious, some oddly specific, and some simply unrealistic.</p><p>High-fidelity motion, SEO optimization, professional copywriting, production-ready React code.</p><p>I don’t mean this as an attack on generalists. I enjoy the generalist approach myself. I’m naturally curious, I like learning new tools, and I like understanding how things work. But at some point, it’s fair to ask who this role is really meant for.</p><p>We ask designers to customize their case studies and cover letters for specific jobs. But how are we supposed to do that when the job description itself is ambiguous and tries to include everything?</p><p>You’re not looking for a designer; you’re looking for a small agency compressed into one person. And often, you’re offering a junior salary for senior-level expectations. That doesn’t signal flexibility — it signals that depth doesn’t really matter as long as the checklist is long enough.</p><h3>2. The influencer mandate: signals vs. noise</h3><p>There are genuinely insightful voices online that we can all learn from. They exist, and they’re valuable.</p><p>But let’s be honest: <em>a lot of what circulates is just noise</em>. The same ideas get recycled, reframed as <em>hacks</em>, and redistributed with new packaging. How many “Day in the Life of a Designer” videos can we realistically consume before they stop saying anything new?</p><p>If you’re hiring based on someone’s audience size or posting frequency, you’re probably not looking for a problem-solver. You’re looking for a cheerleader.</p><p>Some of the best designers I know are quiet, thoughtful people. They don’t optimize for engagement metrics. They spend their time figuring out how to make complex systems usable.</p><h3>3. The performance of <em>professionalism</em></h3><p>Lately, professionalism seems to be measured by optics rather than thinking.</p><p>Talent now appears to be linked to your payment card. I’ve started hearing that applying with a simple fullname@gmail.com address is considered unprofessional. You need a custom domain. You need a paid workspace just to send an email, as if paying for an email setup were a prerequisite for good judgment.</p><p>When did a €20-a-year domain become a substitute for design thinking?</p><p>The same logic applies everywhere else. For everything you do, you’re expected to have a “pro” plan — ChatGPT, Claude, Midjourney, Figma, Framer, Webflow. Subscriptions signal seriousness. Meanwhile, investing in courses, books, or mentorship feels almost secondary.</p><p>Somehow, professionalism has become less about how you think and more about what you pay for.</p><h3>4. The AI hypocrisy: “AI-first” but “human-only”?</h3><p>There’s a strange contradiction in the current business landscape.</p><p>Companies proudly advertise themselves as “AI-first.” Entire workflows are automated. Efficiency is celebrated. Speed is praised.</p><p>But the moment a candidate uses AI to help draft a cover letter? Suddenly it’s a problem.<br> “I want to hear your authentic voice.”</p><p>So which is it? You want AI-driven output when we’re working for you, but handcrafted authenticity when we’re applying?</p><p>You can’t have it both ways.</p><h3>5. The wars over portfolio formats</h3><p>We’ve reached a point where the format of the work is sometimes judged more than the work itself.</p><p><strong>No Figma links</strong>: “They take too long to load.”<br><strong>No Notion</strong>: “Another Notion page? That feels lazy.”<br><strong>No website</strong>: “Why didn’t you use Framer?”</p><p>No Dribbble, no Behance. We want detailed case studies — but not too detailed. We want depth — but only if it grabs our attention in two seconds, because we don’t have time to go through your entire work.</p><p>Designers are expected to guess the right format in advance, even though the expectations shift constantly.</p><p>If someone is dismissed because their portfolio doesn’t include enough motion or micro-interactions, you’re not hiring for product thinking. You’re hiring for aesthetic preference.</p><h3>6. The Portfolio paradox: if you didn’t read it, don’t ask for it</h3><p>We’ve all experienced this.</p><p>You spend weeks refining your case studies. You explain the why. You show the messy middle. You document trade-offs and failed ideas. You send it over.</p><p>Then the interview starts—and it becomes clear very quickly that no one actually read it.</p><p>Suddenly, you’re expected to narrate a case study that was already written for an audience that requested it but didn’t review it.</p><p>There’s also an uncomfortable truth we rarely talk about: case studies are already filtered. We don’t write that the CEO pushed a feature despite the data. We don’t mention that the PM changed the flow behind our backs. We translate reality into something interview-safe, because being fully honest is often considered unprofessional.</p><p>If you’re a recruiter or hiring manager, reading the work is part of your responsibility. The interview shouldn’t be a repeat of the document — it should be a conversation.</p><h3>7. The assessment</h3><p>Then comes the assessment. Usually a small exercise (5–6 hours of genuine work) focused on screens, tokens, or Figma organization.</p><p>Tools change. When I started, it was Photoshop. Then Illustrator. Today it’s Figma, Cursor, Claude, UXPilot, etc. Tomorrow, it’ll be something else.</p><p>If your main signal of talent is how fast someone can navigate a tool, you’re measuring software familiarity, not design thinking.</p><p>Tools are easy to learn. Understanding people isn’t.</p><h3>8. The “trial week” mirage</h3><p>Paid trials are often presented as a fair way to evaluate fit. In reality, a week rarely tells you anything meaningful.</p><p>You can’t judge a designer’s long-term value by how they perform in a week where they don’t even know where the documentation lives. It takes more than five business days to understand a product, to learn the team dynamics, and to feel safe enough to ask the “dumb” questions that actually solve problems.</p><blockquote>Trust and collaboration take time.</blockquote><p>If multiple interview rounds weren’t enough to decide, a short trial won’t magically provide clarity. It usually just reveals a lack of trust in the process.</p><h3>9. The investment void: we want the cherry, but we won’t water the tree</h3><p>One thing I rarely hear during interviews is a conversation about growth.</p><p>There’s little discussion about mentorship, learning opportunities, or how a designer might evolve inside the company. The expectation is often that people arrive fully formed.</p><p>Companies don’t want to invest anymore. They want the final, polished product. They want the top 1% of designers on the globe, but they want them for a minimum wage.</p><p>They want the cherry on top, but they refuse to provide the soil for the tree to grow. If you aren’t offering a place where a designer can actually become <em>better</em>, you aren’t building a team; you’re just renting tools.</p><h3>10. The “expert” noise: Can we just stop?</h3><p>Every day, there’s new advice telling designers what they <em>should</em> be doing.</p><p>“You should code.”</p><p>“No, focus on business.”</p><p>“Use this tool.”</p><p>“Comment ‘system’ and I’ll send you my 24-step guide on how to get hired — if you had started when you were a teenager.”</p><p>“Subscribe here and you’ll receive a custom plan to get a job yesterday.”</p><p>“I’ve analyzed over 1,000 portfolios, and I’m here to tell you — you’re doing a terrible job.”</p><blockquote>The message is always the same: you’re not enough yet.</blockquote><p>Advice keeps piling up, not because it helps, but because it performs well. And it lands especially hard in an industry where design is still treated as “nice to have.” Where making things look good is tolerated, but real thinking is constantly second-guessed.</p><p>There’s always another opinion. Another review. Another “let’s run this by a few more people.” Not because collaboration is valued — but because trust isn’t. Let the product manager decide. Let the room decide. Just don’t let the designer be the final voice.</p><p>Meanwhile, the real work — the thinking, the trade-offs, the responsibility — gets buried under noise, opinions, and performative expertise.</p><p>And don’t get me started on the number of fake job announcements.</p><p>You can’t say you <em>didn’t find the right designer</em> when the market is full of talented, experienced designers actively looking for work. What’s usually missing isn’t talent — it’s willingness to compromise.</p><p>Instead, we’re fed the same narrative: more steps, more filters, more interviews, all justified by the idea that there’s a <em>perfect</em> candidate out there if we just keep looking long enough. Recruiters reinforce it. Processes expand. Expectations inflate.</p><p>But what exactly is perfect in this context? And who, realistically, thinks they are?</p><blockquote>Design has never been about perfection. It’s about trade-offs, constraints, collaboration, and progress. Treating hiring like a purity test doesn’t lead to better teams — it just leads to empty roles and burned-out candidates.</blockquote><h3>The bottom line: can we make this easier?</h3><p>Designers are trained to look at broken systems and ask how to simplify them.</p><p>Yet when it comes to hiring, we seem to do the opposite. We add steps. We add tools. We add friction.</p><blockquote><strong>We demand custom effort while giving back automated responses.</strong></blockquote><p>If you’re involved in hiring, take a step back. Strip away the theater.</p><p>Instead of asking for perfect formats, flawless optics, and endless proof, ask yourself how you can better understand the person behind the work.</p><p>There’s also something else we need to acknowledge: I’ve never seen this much pressure placed on designers. Pressure on how to think, how to work, how to behave. Be opinionated, but not too opinionated. Stay in your lane, but cross it when needed. Be professional, but let others define what that means. Have a voice, but don’t use it too loudly.</p><p>At some point, this stops being about standards and starts feeling like performance. We need to take some of that pressure off and let people live this fucking life.</p><p><strong>Design has always been about people. Our hiring processes and our expectations should reflect that.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c00acef1f6ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding your way back after collaboration breaks you]]></title>
            <link>https://medium.com/@oelenagrigore/finding-your-way-back-after-collaboration-breaks-you-cd12b5db2b50?source=rss-3db4b209f042------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd12b5db2b50</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Oana Grigore]]></dc:creator>
            <pubDate>Mon, 27 Oct 2025 15:57:49 GMT</pubDate>
            <atom:updated>2025-11-22T19:48:35.308Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ctWYHc14XOzEJwW_DmLh5w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@teamnocoloco?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Team Nocoloco</a> on <a href="https://unsplash.com/photos/a-computer-screen-with-the-words-nothing-great-is-made-alone-YRUj8BENrVQ?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>There’s life after bad collaboration.<br>After the gaslighting, the endless calls where your voice didn’t matter, and the slow erosion of your confidence.<br>After working with the kind of people who made you question your value, your ideas, your sanity.</p><p>You can find your spark again.<br> You can love what you do again.<br> It just takes time and a few reminders that <em>you were never the problem. </em>But maybe it was me? Or was it all in my head? Gosh, the never-ending roller coaster.</p><p>I know this because I’ve been there.</p><p>Fourteen years into this craft, I’ve worked with teams that made me better and with others that nearly broke me.<br>This story isn’t about bitterness; it’s about understanding what happens when collaboration stops being collaboration… and how you find your way back from it.</p><h3>When collaboration isn’t collaboration</h3><p>Let’s talk about working with <em>certain colleagues.</em><br> Not all of them, just a very specific kind.</p><p>Let’s call him <strong>Jack</strong>.<br>Jack the Master. The Buddha. The one and only. The man whose name is on the app, on the feature, and on the release notes.</p><p>Jack speaks first and never listens. Jack is always right.</p><p>You know the type.</p><p>Jack knows the strategy, the roadmap, the “why.”<br>Your role? Do what he says, as he says it.<br>Bring your own ideas? Hell no. Who do you think you are? You’re not here to think; you’re here to execute.</p><p>But Jack is clever. Diplomatic. Hardworking.<br>On the surface, he looks like <em>the good guy</em>. Which makes it even easier to paint <em>you</em> as the problem.<br>You’re <strong>difficult</strong>. You’re <strong>not aligned</strong>. You’re <strong>too emotional. </strong>You do<strong> not care. </strong>You are<strong> aggressive. </strong>You are<strong> the disturber. </strong>You are<strong> sarcastic. </strong>You are<strong> mean. </strong>And I can go on and on.</p><p>And suddenly, everything goes south. The trust, the collaboration, and the spark all fade away.</p><h3>What this does to a designer</h3><p>When your ideas are dismissed before they’re even heard, when curiosity is treated as defiance, it doesn’t just silence you — it <em>shrinks</em> you.</p><p>You start doubting yourself.<br>You stop suggesting new approaches, because what’s the point?<br>You stop asking questions, because they only earn you labels.<br>And little by little, you stop believing your work matters at all.</p><p>It’s not just your confidence that goes.<br>It’s your <em>energy</em>.<br>Your <em>creativity</em>.<br>The joy that made you fall in love with design in the first place.</p><p>And if it goes on long enough, it follows you home.<br>Music stops sounding the same. Books stay closed. Even rest feels restless.</p><h3>Business without users</h3><p>When people like Jack are in charge and you, as a designer, are seen as the problem, the whole vibe of the team changes.<br>It’s no longer about solving problems or caring about users.<br>It becomes about who’s right, whose idea gets implemented, and who gets the credit.</p><p>It’s not about UI, UX, or best practices anymore.<br>It’s not about craft or building intuitive workflows.<br><strong>It’s about generating revenue with half-copied features from the competition and rushing through deadlines so tight that quality doesn’t stand a chance.</strong></p><p>It’s all about what takes the least time to build because somewhere along the way, <strong><em>speed</em> </strong>became more valuable than <strong><em>sense or quality</em></strong><em>.</em></p><h3>The quiet erosion</h3><p>This dynamic doesn’t break you overnight. It wears you down in small, invisible ways.</p><p>One meeting, one ignored idea, one dismissed comment, one bypassed decision at a time. Until one day, you realize you’re not yourself anymore.<br>You’ve become a robot, just executing—not creating.<br>You’re no longer solving problems; you’ve hit rock bottom.</p><h3>So what do we do?</h3><p>We stop pretending this is normal.<br>Because it’s not.</p><p>It’s not collaboration when one person talks and everyone else just nods along. It’s not leadership when <em>ownership</em> really means <em>do what I say</em>, <em>because I said so</em>. And it’s not respect when your ideas only count if they match someone else’s vision.</p><p>Real collaboration means asking questions without fear.<br>Real leadership means sharing credit, not guarding it.<br>And real respect looks like sitting down together, listening, and figuring things out — even when it gets messy.</p><p>Design has never been about egos. It’s about empathy.<br>And empathy doesn’t survive in power games.</p><h3>A message to Jack</h3><p>Jack, if you ever read this:<br>I don’t need your fake diplomacy.<br>I don’t need your empty talk about <em>ownership</em>.</p><p>What I need, what every designer, developer, and person on a team needs <strong>is trust, respect, and the space to be heard.</strong><br>That’s how ideas grow.<br>That’s how people feel valued.</p><p>That’s leadership. That’s collaboration.<br>Until then, stop calling it teamwork.<br>Because we both know it’s not.</p><h3>Finding joy again</h3><p>Here’s the part I couldn’t see back then:<br>You <em>do</em> recover. Slowly, quietly, and often when you least expect it.</p><p>You heal through small wins.<br>Through that one teammate who asks for your opinion and actually listens.<br>Through projects where curiosity is encouraged, not punished.<br>There are moments when you find yourself smiling at your screen again, simply because you care. <br>When you wake up on a Monday morning, your thought should not be, &quot;I hate this day.&quot;</p><p>You stop designing to defend yourself and start designing because it makes you feel alive again.<br>That’s when you know you’ve truly healed.</p><p>So if you’re still in that kind of storm, hear this:<br>You are not broken.<br>You are not <strong><em>too much</em></strong>.<br>You are not the problem for wanting better.</p><p>You <em>will</em> find teams that listen.<br>You <em>will</em> find people who value your mind.<br>And you <em>will</em> fall back in love with your craft.</p><p><strong>Because even after the worst collaboration, there’s still joy waiting for you on the other side.</strong></p><p><strong>And this time, it’s all yours.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd12b5db2b50" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leadership isn’t a job title]]></title>
            <link>https://medium.com/@oelenagrigore/leadership-isnt-a-job-title-e0ca6e3a4415?source=rss-3db4b209f042------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0ca6e3a4415</guid>
            <category><![CDATA[management-and-leadership]]></category>
            <dc:creator><![CDATA[Oana Grigore]]></dc:creator>
            <pubDate>Fri, 17 Oct 2025 10:47:52 GMT</pubDate>
            <atom:updated>2025-10-17T10:47:52.348Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>Note:</strong> Imagine working in a place where your voice is heard. Where your ideas matter, where respect is the baseline, not a luxury. Feels nice, right?</blockquote><blockquote>Now imagine the opposite. Imagine the story I’m about to tell you.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a2zvQqUSUOnDaqkL5wOAAA.jpeg" /><figcaption>Freepik</figcaption></figure><p>I worked on teams where trust and leadership felt like alien concepts. Everything was about ego—whose idea, whose voice, whose victory. You get the point. If you had an idea — and I was stupid enough to share mine — it went one of three ways:</p><ol><li>It was dismissed.</li></ol><p>2. People laughed about it.</p><p>3. You were made to feel stupid, if not outright told you were (not in those exact words, but close enough).</p><h3>When feedback isn’t feedback</h3><p>I heard things like</p><blockquote><em>“Who do I need to talk to in order to make the change I want?”</em></blockquote><blockquote><em>“Why did you present something different when I already told you what to do?”</em></blockquote><blockquote><em>“I don’t like it.”</em></blockquote><p>And many more in the same tone. At some point, I just wished for the cliché feedback of <em>make it pop</em> or <em>make it bigger.</em> At least then it would’ve been obvious that the problem wasn’t the design—it was the lack of real communication.</p><h3>When trust disappears</h3><p>I tried to fix the miscommunications. Different approaches, different people—nothing changed. The people I trusted to listen didn’t. The people I respected disrespected me—<em>because they could</em>. I was called names I’d rather forget.</p><p>Every time, somehow, I became the problem. <em>The one who didn’t understand how the business works</em>. The one who should <em>just find another job</em>. Right—because it’s that easy.</p><p>The truth is, I loved the project. I wanted to make it work. I held onto the hope that things could change.</p><p>I was the only one on the team who raised the issues, and I ran out of ideas. I was stuck—in a job I liked, on a project I believed in, but with a team that diminished me. A team that wanted control instead of ideas.</p><p>And in the end, I became <em>the aggressive one</em>. The one disturbing the vibe. Aggressive, because I wouldn’t let people disrespect me, control me, or undervalue me.</p><h3>How it takes everything</h3><p>Being dismissed like that didn’t just hurt my work. It ate at my trust in myself. It stole my joy. It dimmed the love I had for design.</p><p>It spread into the rest of my life. Music stopped filling me up. I lost the peace I got from reading and buying books. Things that used to be safe and nourishing felt heavy or pointless. It destroyed me from the ground up: my mental health, then my physical health.</p><p>That’s the real cost of a toxic workplace—it doesn’t stay inside the office. It bleeds into the parts of you <strong>you thought were untouchable</strong>.</p><h3>The myth of leadership</h3><p>We’re told leadership lives in titles, in offices, and in the person whose name is on the release notes. But authority without care is just control. Control creates fear, and fear shrinks people. <strong>Fear doesn’t inspire, guide, or build. It erodes.</strong></p><p>Leadership confused for dominance will always leave teams hollow. When credit is hoarded and voices are silenced, the work suffers—and so do the people making it.</p><h3>Is this the norm? (and should it be?)</h3><p>It looks like there are a lot of places that are at the same level of toxicity, and a lot of the people working in tech think that this is the norm, this is how things work, and if you are not tough enough, you should find something else.</p><p>But are you sure this should be normalized?</p><p>I know that change comes from us, and I cannot change someone else, and I don’t really want that. But I also shouldn’t be silenced because I don’t agree with you. I would treat you with respect and kindness for as long as you would do the same. At the moment you start to do otherwise, don’t expect me to be proactive, kind, and unsarcastic.</p><h3>What leadership actually is</h3><p>Real leadership is simple, and it’s human:</p><ol><li>Trusting your team.</li></ol><p>2. Listening to what they have to say.</p><p>3. Taking feedback seriously instead of brushing it off.</p><p>4. Giving feedback that helps — not “I don’t like it,” but “This part is strong; this part could be clearer. Walk me through your thinking.”</p><p><strong>Leadership is creating clarity and safety</strong>. It’s not redoing someone’s work because you can. It’s not laughter that dismisses. It’s not excusing one person and punishing another. That’s not leadership — that’s ego.</p><h3>The cost to creatives</h3><p>Designers (and other creative people) don’t burn out because the craft itself is impossible. They burn out because they are asked to work with people who don’t trust them enough to share context, data, or even clear KPIs. They burn out because they are asked to design in the dark.</p><p>And when the work is finally done, they discover someone else has changed it. The guidelines weren’t followed. The flow was cut apart in the name of urgency. Navigation is tossed, and details vanish.</p><p>Design is treated as <em>nice to have</em>.</p><p>This is what leads people to burnout.</p><h3>The small, quiet acts that save us</h3><p>If a toxic culture can break you from the ground up, then the opposite can rebuild you from the ground up — but it doesn’t happen at once. It starts in small, quiet acts:</p><p>Saying, “Tell me how you thought about this.”</p><p>Acknowledging someone’s contribution out loud.</p><p>Letting mistakes be lessons rather than ammunition.</p><p>It&#39;s important to say, &quot;I see you,&quot; and to mean it.</p><p>These are leadership too. They don’t need a title. They need people brave enough to choose them.</p><h3>Therapy helped</h3><p>You may ask: did therapy help? Yes. Therapy helped a lot.</p><p>It helped me see that my value wasn’t tied to my work. It helped me find the parts of myself the workplace had dimmed. I started enjoying music again. I started reading books for pleasure, not as something to squeeze into the cracks of my life. I learned to notice the light at the end of the tunnel.</p><p>Therapy didn’t fix everything overnight. But it gave me tools to rebuild trust in myself and to understand that the brokenness was the environment’s doing, not a measure of my worth.</p><h3>Refusing silence</h3><p>People always say: “Move on.” “Go find another job.” “It’s pointless to even say something.”</p><p>Well, for me it is not pointless.</p><p>I’ve always been the person encouraging others to stand up for themselves. To not accept toxic behavior in their lives. To cut out people who drain them. To ask for help and to speak about it.</p><p>And now—am I the one that stays silent? Am I the one that doesn’t take action? That would be a betrayal of my own principles of living. I can’t do that.</p><p>With small steps, I’m starting to be loud about it.</p><h3>A message to anyone who’s still there</h3><p>If you’re reading this and still in that place: <strong>notice the signals</strong>. If feedback is always a put-down, if only one voice ever counts, if people you trusted leave you alone when you ask for help—those are signs. You don’t have to stay where you’re being diminished.</p><p>And if you can, choose small acts of leadership where you are. Listen. Give helpful feedback. Say the credit out loud. Make space. You don’t need permission. You only need courage.</p><h3>We can rebuild</h3><p>Leadership isn’t a job title. It’s a choice. It’s a mindset. It’s understanding people.</p><p>Leadership shouldn’t be something you pick up in a masterclass. It should be built into you as you grow, into how you listen, how you respond, and how you respect others.</p><p>When we choose to treat people with respect, when we listen and trust instead of punish, we rebuild not only teams but also the people inside them. And when that happens, the projects we work on grow stronger too.</p><p>Design is not about <em>cute images</em>. And if you work in tech and you still think that, I feel sorry for you.</p><p>Being a good human is a choice. And I know I’m a good human who fell in love with design 14 years ago. A bunch of people might want to destroy that—but you’ve got to do better than that.</p><p>I’ve met a**holes my whole life. And I’m still here.</p><p>— — —</p><p>If this article helps one person spot the red flags earlier or helps one person believe they can rebuild, then it’s worth it.</p><p>I’m writing this because I don’t want anyone else to lose the things I loved—my confidence, my creativity, the music, the books—without knowing they can be found again.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0ca6e3a4415" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a system that wasn’t supposed to exist]]></title>
            <link>https://medium.com/@oelenagrigore/designing-a-system-that-wasnt-supposed-to-exist-983d69c59899?source=rss-3db4b209f042------2</link>
            <guid isPermaLink="false">https://medium.com/p/983d69c59899</guid>
            <dc:creator><![CDATA[Oana Grigore]]></dc:creator>
            <pubDate>Tue, 09 Sep 2025 13:17:36 GMT</pubDate>
            <atom:updated>2025-09-09T16:59:48.397Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How two designers, a “patient” dev team, and two years of “side questing” built a design foundation that powers 40+ apps (and counting) while blending seamlessly into thousands of Shopify stores.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DhK6VXpQt13iYVGQNVWiUg.png" /></figure><h3>The system that no one had time for</h3><p>When I first floated the idea of building a design system for Vitals, the reaction was… polite smiles and a lot of “maybe later.”</p><p>We were in growth mode: new features shipping constantly, merchants asking for more, bugs popping up daily. A design system felt like something <em>big tech companies</em> had the luxury of doing. We were a scrappy team — we didn’t have time to “make things pretty.”</p><p>But that wasn’t the point.</p><p>I wasn’t losing sleep over “pretty”. I was losing sleep over <strong>consistency</strong>.</p><p>Vitals has over 40 apps, built by multiple teams, all running inside one Shopify integration. Without a shared system, every feature felt like its own product.</p><p>We had five different button styles, more variant selectors that I can count on, color contrast issues all over the place, and onboarding a new engineer … well, let’s just say it wasn’t fun. :)</p><blockquote>We weren’t building a product anymore. We were building 40 products.</blockquote><p>So I started a secret side quest.</p><p>Whenever I had downtime (read: rarely), I audited <strong>Shopify’s Polaris system, the top Shopify themes, most known design systems, and our own UI mess</strong>. I filed away every inconsistency. I collected screenshots, compared patterns, and made mental notes.</p><p>That “side project” lasted two years.</p><h3>Getting buy-in (kind of)</h3><p>Convincing developers to slow down and invest in a design system? <em>Not easy</em>. There were sighs, pushback, and a lot of “Can this wait?”</p><p>Then another designer joined the team. Suddenly I wasn’t alone in this fight. Together, we started small:</p><ul><li>Hosting meetings</li><li>Collecting feedback from engineers</li><li>Sketching out what this system <em>could</em> look like</li></ul><p>And wow, did people have opinions.</p><p>Some wanted to go all-in. Others worried about performance. We argued about naming conventions, and even went down rabbit holes about whether to use rem, px, or % for spacing or line height.</p><p>And because Vitals apps have to integrate into <em>so many different store themes</em>, it wasn’t just a theoretical argument. Some themes used pixels for spacing, others relied on rem values defined anywhere from 0px to 16px, and when it came to line-height… let’s just say there were <em>too many scenarios to even want to remember</em>.</p><p>At some point, we realized something important:</p><blockquote><em>The words “Design System” were scaring people.</em></blockquote><p>So… we dropped the name.</p><p>It wasn’t “The Design System” anymore. It was just <strong>a set of rules to make our lives easier</strong>. And that small shift in language made a huge difference. (Thank you, A. for your advice)</p><h3>Designing for chaos</h3><p>This wasn’t your typical design system project. Most systems start with a brand identity. Fonts, colors, spacing tokens… the works.</p><p>We had none of that.</p><p>Vitals widgets need to <strong>blend in</strong> with thousands of Shopify store themes, from ultra-minimal boutiques to colorful mega-catalogs.</p><p>That meant:</p><ul><li><strong>No fixed font families.</strong> Our widgets inherit whatever the merchant’s store is using. We had to design for hierarchy and spacing, not typefaces.</li><li><strong>Dynamic color tokens.</strong> No “brand blue” to lean on. Colors had to adapt to store themes while staying <strong>WCAG 2.1 AA compliant</strong>.</li><li><strong>Defaults over customization.</strong> Merchants don’t want to fiddle with a dozen color pickers. We built thoughtful defaults so they don’t have to think about it at all.</li></ul><p>The goal wasn’t to make merchants feel like designers. It was to <strong>get out of their way</strong>.</p><h3>Isn’t this a developer’s job?</h3><p>At some point, someone might say: <em>“Come on, it’s just a few components — isn’t that a frontend developer’s job?”</em></p><p>And yes, building tokens, components, and applying accessibility rules are things engineers excel at.</p><p>But a design system isn’t just about code. It’s about <strong>consistency, usability, color theory, typography, layout</strong> — the things designers live and breathe. Pair that with developers’ ability to create scalable, accessible components, and you get something stronger than either side could do alone.</p><p>A design system is a <strong>common language</strong> — something everyone involved in the project can “speak” and understand. Designers, developers, and PMs can all approach it from their own perspective, but they’re working from the same playbook.</p><p>Because here’s the truth: <strong>nothing meaningful is ever built in solo mode</strong>. You need a team with different areas of expertise, and you need to trust them. That trust — between designers, developers, and PMs — is what makes a system not just usable, but scalable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lOkmErTWoNgqEIi5AFzI2g.png" /></figure><h3>Two years of side quests</h3><p>None of this happened overnight. It was slow, messy, and honestly kind of exhausting.</p><p>Most mornings I’d start the day telling myself, <em>“We are going to do it!”.</em><br>By the evening? It was usually closer to, <em>“F**k it. This is not possible.”</em></p><ul><li>We renamed components.</li><li>We tested color systems.</li><li>We created patterns, scrapped them, and created new ones.</li><li>We begged PMs to make accessibility a priority.</li></ul><p>And because this wasn’t anyone’s “full-time” job, we built it piece by piece, <strong>in between product launches, bug fixes, and marketing deadlines</strong>.</p><p>But slowly, we replaced chaos with clarity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OhTjQzrQx6BcF3lFOw7eKg.png" /></figure><h3>Wins we’re proud of</h3><ul><li><strong>A solid foundation is in place</strong>: Core components (buttons, variant selectors, quantity selectors) are standardized across major apps.</li><li><strong>Work in progress</strong>: Full adoption across all 40+ apps is ongoing, rolled out carefully to avoid disruption.</li><li><strong>Developer trust is growing (we hope!)</strong>: Engineers are starting to see the benefits of a shared source of truth, though it’s a cultural shift we’re still building.</li><li><strong>Accessibility is non-negotiable</strong>: WCAG contrast compliance is baked into every design decision.</li><li><strong>Improved design–dev velocity</strong>: Fewer style debates, more focus on features.</li><li><strong>Invisible design wins</strong>: Merchants never notice the system — and that’s exactly the point.</li></ul><h3>Lessons learned</h3><ol><li><strong>Start small, stay patient</strong><br>Design systems are marathons, not sprints — especially at startups. Small wins create momentum.</li><li><strong>Words matter</strong><br>“Design System” felt big and scary. Calling it “tools” or “foundations” made it approachable.</li><li><strong>Collaboration over ownership</strong><br> Devs helped us shape this system. Thank you.</li><li><strong>Invisible design is the best design</strong><br> Nobody thanked us for typography tokens or contrast ratios, but they trusted the product more because everything just … worked.</li></ol><h3>Looking ahead</h3><p>When I first started documenting our design system, <strong>AI integration was firmly “out of scope.”</strong> We were just trying to get consistent variant selectors and colors — nothing fancy.</p><p>But now? Writing this article made me realize that’s our next step.</p><p>I want our design system to go beyond documentation. I want designers to ship <strong>prototypes faster</strong>, using AI tools that plug right into our system. Imagine generating screens in minutes with consistent components, tokens, and accessibility baked in.</p><p>We built this system to make life easier. The next step is to make it <strong>effortless</strong>.</p><h3>The best part</h3><p>We’re not “done.” A design system is never finished. But now, every new feature doesn’t feel like starting from scratch. We have a <strong>language, a toolkit, and a shared vision</strong>.</p><p>And honestly? That’s worth every late-night audit, every debate about line-height units, and every time we changed a component name… again.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=983d69c59899" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>