<?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 Karine Tavrizyan on Medium]]></title>
        <description><![CDATA[Stories by Karine Tavrizyan on Medium]]></description>
        <link>https://medium.com/@karine.tavrizyan?source=rss-17980efe73f3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qUU3N64m-ko5VtnXqQDkMQ.jpeg</url>
            <title>Stories by Karine Tavrizyan on Medium</title>
            <link>https://medium.com/@karine.tavrizyan?source=rss-17980efe73f3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:13:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@karine.tavrizyan/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[Normalizing the Broken]]></title>
            <link>https://medium.com/@karine.tavrizyan/normalizing-the-broken-a00dcbb76443?source=rss-17980efe73f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/a00dcbb76443</guid>
            <category><![CDATA[dysfunction]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[normalization]]></category>
            <dc:creator><![CDATA[Karine Tavrizyan]]></dc:creator>
            <pubDate>Thu, 29 May 2025 13:41:49 GMT</pubDate>
            <atom:updated>2025-05-29T13:48:55.574Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aN7f53cPkx6n3sRj4crO3w.jpeg" /></figure><p>I’d been meaning to write about this for a month or so. But the topic is complex, sensitive to some extent, and interrelated with millions of other topics about leadership, management, and human behavior. So I kept postponing. Then I came across the illustration above on LinkedIn and started drafting.</p><p>This isn’t about one company in particular (though each of you may have names in your heads). Instead, It’s about a pattern I’ve seen and many of you probably have too. A culture where dysfunction gradually becomes invisible. Where someone calling out a real problem is treated as <em>the problem itself</em>. And over time, deviation from what’s “normal” becomes the new normal.</p><p>In psychology this is called <strong>Normalization of Deviance (</strong>a term coined by Diane Vaughan): in other words, if something hasn’t been fixed or addressed for a prolonged period of time, people become used to it and assume that it’s okay to continue operating in this manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D3aWfiNTtElIKCN6JuHgvw.jpeg" /></figure><p>Now, what follows are my thoughts only and they don’t map to the articles you can find in the web about Normalization of Deviance. And no, I am not going to mention HR or People Ops as in most broken systems, HR isn’t leading or driving the culture. When leadership is absent, HR can’t fix what no one’s willing to face.</p><p>Here’s the breakdown of how Normalization of Deviance happens based on my experience and why it’s so dangerous.</p><h3>1. What You Tolerate Is Who You Become</h3><p>You’ve probably heard: <em>Your company culture is who you hire, fire, and promote.</em></p><p>Systems are shaped by what’s tolerated. When underperformance and toxic behavior goes unaddressed, it sends a louder message than any values deck your HR/People Ops department could provide.</p><p>It usually starts with small symptoms:</p><ul><li>A deadline missed without consequence</li><li>A toxic teammate who’s “just joking” all the time</li><li>A manager who plays favorites but delivers results, so no one touches them</li><li>A culture survey where the results were never shared or discussed</li><li>Etc.</li></ul><p>Slowly, these exceptions become patterns, then the team mindset gradually adjusts, people stop expecting accountability and anyone who tries to raise the problems is seen as “difficult,” “negative,” or just “not a fit”.</p><p>Meanwhile, high performers, the ones who are capable of seeing the problems and have courage to raise the flags, still continue pushing. They end up doing the work others avoid, carrying more than their share while most just do the bare minimum. As a result, high performers get frustrated and leave.</p><p>As the dysfunction drags on, people stop questioning it. Rather they start justifying the dysfunction, e.g. <em>“That’s just how things are here,”</em> or <em>“At least it’s better than in Company X.”</em></p><p>Psychologists call this <strong>System Justification Theory</strong>: the tendency to defend and rationalize broken systems. People defend and make excuses for a broken system, not because it works, but because accepting the truth would mean facing discomfort or conflict. It feels safer to go along than to challenge the structure.</p><p>In short: if you don’t hold the line, it moves and almost always downhill. As a project manager, I’ve learned the following throughout my career: when you normalize dysfunction, undoing it becomes 10x harder.</p><h3>2. Loyalty Over Competence</h3><p>Most probably you have witnessed companies where loyalty is valued more than skills, competence or professionalism. In environments where loyalty is prioritized over competency, people are promoted not because they solve problems or drive impact but because they “get along” with the right people. Because they have been there for so many years that can be considered “loyal”. Because they stay silent when things go wrong. Because they make their manager feel safe instead of challenging them.</p><p>And here’s the dangerous part: the truly competent, driven people, the ones who care about outcomes are often the least interested in playing political games or in soft-soaping the management. So they leave. What you’re left with is an employee layer that’s loyal but disconnected from reality, afraid of conflict, incapable of meaningful change and just doing their bare minimum to stay where they are.</p><p>Here is how you end up having mediocrity as a norm. And eventually, the whole organization forgets what good actually looks like.</p><h3>3. Everyone’s Working, Nothing Works OR Leadership Left the Room</h3><p>At some point, when no one from leadership takes real ownership, chaos becomes the system.</p><p>There are companies full of motion: meetings, updates, metrics, dashboards <strong>but no direction</strong>. People are “doing their best,” but no one is leading. There’s no clear vision where they go.</p><p>In that vacuum, the wrong things get normalized. Accountability disappears. Dysfunction spreads because of <strong>favoritism, nepotism and leaders who promote this.</strong></p><p>That’s how normalization of deviance happens: not overnight, but through silence, inaction, and absent leadership.</p><p><strong>The truth is, cultures don’t break from the bottom. They break from the top.</strong><br>If no one’s leading, nothing changes.<br>If no one speaks up, dysfunction becomes the norm.<br>And if no one cares, the boat keeps sinking.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a00dcbb76443" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One PM’s Real Playbook]]></title>
            <link>https://medium.com/@karine.tavrizyan/one-pms-real-playbook-0b7d9b5eeae7?source=rss-17980efe73f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b7d9b5eeae7</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[project-manager]]></category>
            <dc:creator><![CDATA[Karine Tavrizyan]]></dc:creator>
            <pubDate>Mon, 05 May 2025 12:27:58 GMT</pubDate>
            <atom:updated>2025-05-05T13:17:23.503Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Op3HX5nZUjfc0Gi2YI1dJw.png" /></figure><p>The job market will never be the same again. And since many project managers (and not only) in software development are now struggling to find jobs, I want to share a few thoughts. These points are purely my personal opinion — I’m not claiming they’re absolute truths, just sharing my perspective in case it’s useful.</p><p><strong>1. Networking is Overrated Until You’re Good Enough</strong></p><p>People who know me or have ever worked with me know that I’ve never been the networking type. I usually don’t attend industry events, I rarely post on LinkedIn, and I don’t go out of my way to collect contacts. It’s not that I don’t believe in networking — I do. I just believe more in my own skills.</p><p>Recently, I’ve seen many LinkedIn posts claiming that networking is everything when you are searching for a job. Reality is — your network won’t save you if your skillset can’t stand on its own. I’ve conducted many interviews, and yes, as a hiring manager, if I was hesitating between two candidates — one of whom was referred by a colleague I trust — I would likely choose the referred one, assuming my colleague had worked with them. However, that only applies when both candidates demonstrate similar skill levels or impress me equally. If you stand out from the crowd, no one is going to pick someone else just because they’re a referral.</p><p>Aim to be so good that sending out a strong CV is enough to land interviews on your own terms. That shift — from relying on others to relying on yourself — will change the way you value your own work and reduce unnecessary expectations from others.</p><p><strong>2. When Theory Fails You</strong></p><p>The best PMs I’ve worked with aren’t obsessed with theoretical frameworks. Theory gives you a foundation, and best practices should serve as guidelines — not strict rules.</p><p>Recently I came across my ex colleagues’ post saying:</p><p><strong><em>“Experience isn’t about following best practices, it’s about knowing when and how to redefine them.”</em></strong></p><p><em>The same applies to theory — and it’s not always just about experience, sometimes it’s about plain </em><strong><em>common sense</em></strong><em> (aka. քթածակ).</em></p><p>I’ve seen highly theoretical PMs fail in practice, while those who ignore it entirely often miss patterns that matter over time. The best ones balance both — aim to be one of them.</p><p><strong>3. No, You Can’t Be a Great PM Without Technical Knowledge</strong></p><p>I don’t believe in the idea of non-technical project managers — cause you can’t lead what you don’t understand. Years ago, this wasn’t a dealbreaker. Now, it often is. PMs who understand the tech can make better decisions, communicate better with engineers, and spot problems early.</p><p>The definition of “technical” can vary, but at a minimum, you should understand the software development lifecycle (SDLC) and general programming concepts. If you want to level up, go further: experiment with APIs, get familiar with how databases work, I don’t know, you can even learn the basics of any programming language — not to become a developer, but to familiarize yourself to patterns, syntax, and logic, learn to use an IDE, and get comfortable with version control systems like Github, Gitlab, Bitbucket, etc.</p><p>Remember the job market is still a market where you should have a competitive advantage.</p><p><strong>4. Product Context Isn’t Optional</strong></p><p>You can’t manage what you don’t understand — and that includes the product too. PMs who treat product knowledge as optional end up blocking more than they unblock. You don’t need to be a product manager, but you need to know what your product does, who it’s for, and why it matters.</p><p>Understand the end user and features that your product manager brings. Know the roadmap. If you don’t, you’ll always be a middleman — not a multiplier.</p><p><strong>5. Professionals Don’t Repeat Tasks Cause Manual Work Is a Career Killer</strong></p><p>Speaking as someone with an economics background, <em>opportunity cost in economics</em> is simple: doing one thing means not doing another — and that tradeoff matters. When you spend your time on repetitive tasks, you’re not just missing a chance to grow — you’re holding back your potential impact on the organization. It can also send the wrong signals: that you’re resistant to growth or intentionally avoiding automation to stay needed.</p><p>At the end of the day, no one promotes someone for doing the same thing well forever. They promote people who solve new problems, build systems, or multiply output.</p><p>Growth comes from taking on things that stretch you, not just things you already know how to do on autopilot. So if you want to stay relevant: automate, document, delegate, and level up.</p><p><strong>6. Use AI Tools — Like, Actually Use Them</strong></p><p>Start using AI tools in your daily workflows. Not in theory — in practice. Don’t just read about how ChatGPT or GitHub Copilot works. Integrate them into your actual work: use AI for draft writing, meeting notes, QA coverage analysis, even sprint retros. Most people talk about AI but very few incorporate it as an extension of their day-to-day execution.</p><p>The ones who do will outpace everyone else.</p><p><strong>7. Remote Work Exposes Weak PMs, Elevates Strong Ones</strong></p><p>Remote work didn’t kill project management — it just exposed who was faking it. In distributed teams, you can’t rely on in-person chats or endless meetings to mask disorganization. Communication, clarity, and ownership become ten times more important.</p><p>Strong PMs thrive remotely because they build structure where there is none, keep async momentum, and know how to surface blockers without micromanaging.</p><p>If you struggle with remote, the problem isn’t the format — it’s your system. Fix that.</p><p><strong>8. Master People, Not Just Plans</strong></p><p>Project managers often underestimate how much human behavior shapes outcomes — just like people managers who ignore how one toxic employee can poison an entire team. Deadlines slip not just because of poor planning, but because of miscommunication, lack of engagement, etc. Psychology helps PMs see beneath the surface — why teams procrastinate, why someone resists, why meetings go off track.</p><p>I’ve always told my team this:<strong> analyze everything and everyone.</strong> You can’t manage people you don’t understand. Know your team — what drives them, what irritates them, how they think, and what they care about. You should be able to sketch a rough psychological portrait of each person you work with. That’s how you lead humans.</p><p>A psychologically informed PM anticipates resistance, manages stakeholder expectations more effectively, and builds trust faster. Psychology isn’t optional — it’s a strategic advantage.</p><p>If you want to get better, study basic behavioral psychology, learn to read the room, and practice active listening — it’s more useful than half the certifications out there.</p><p><strong>9. Control Yourself First OR Your Team Feels What You Leak</strong></p><p>One thing I’ve always advised as a people manager of PMs — nothing should make you lose control. ​​Why? Because the best PMs I’ve met over the years, stay calm when things go sideways. And things <em>always</em> go sideways. Priorities shift, stakeholders panic, team pushes back, deadlines slip. If you don’t have self-control, you’ll end up reacting emotionally, micromanaging, or making rushed decisions that only make things worse.</p><p>Self-control isn’t about being passive. It’s about staying clear-headed when everyone else is emotional. It builds trust. It gives your team stability. And it helps you make better calls under pressure. If you want people to follow your lead, especially in tough moments, you need to show you’re in control — of the situation, and yourself.</p><p>So, start by observing your reactions under pressure, learn to pause before responding, and train yourself to stay steady.</p><p><strong>10. Manage Up, Manage Down — Two Fronts, One Job</strong></p><p>One of the most underrated skills in project management is knowing when to manage up and when to manage down.</p><p>Managing <strong>down</strong> means unblocking your team, protecting their focus, giving clarity, and helping them grow. It’s about day-to-day execution, team morale, and tactical decisions. This is what most PMs default to — but it’s not enough.</p><p>Managing <strong>up</strong> means influencing stakeholders, aligning expectations, and foreseeing escalations. It’s about pushing back when timelines are unrealistic, surfacing trade-offs early, and making sure leadership hears about progress and problems before they blow up.</p><p>If you’re only managing down, you’re just a team babysitter. If you’re only managing up, your team burns out while you chase approval.</p><p>The best PMs do both — they act as a shield and a signal. Learn to read the room and recognize where the gap is. That’s where our job starts.</p><p><strong>11. Projects End — Programs Drive Impact</strong></p><p>Recent trends show a shift toward program management roles, especially in large tech firms, e.g. Google, Meta, Amazon, Adobe, etc. These companies want people who can drive cross-functional initiatives, align with product strategy, and deliver outcomes — not just timelines.</p><p>If you’re still thinking like a traditional technical project manager, you’re already behind. Start learning program management. Study how to manage complexity, lead across teams, and think long-term. The market isn’t just asking for execution anymore.</p><p>That’s it. Just my two cents. I’m not saying I’ve got it all figured out, but I’ve seen enough to say — the role’s changing, the bar’s rising, and sticking to old habits won’t save you. If this made you rethink even one thing, great.</p><p>The truth is, if you’re not the most proactive person in the room, you’re not the project manager de facto — someone else is driving, whether you realize it or not. So stay sharp and stay ahead.</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b7d9b5eeae7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>