<?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 Hafidz Zulkifli on Medium]]></title>
        <description><![CDATA[Stories by Hafidz Zulkifli on Medium]]></description>
        <link>https://medium.com/@hafidz?source=rss-9d98e8dadfc2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2zQ9d0myivvoyHckRRllcw.png</url>
            <title>Stories by Hafidz Zulkifli on Medium</title>
            <link>https://medium.com/@hafidz?source=rss-9d98e8dadfc2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:01:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hafidz/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[In Defense of the Managers]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/in-defense-of-the-managers-b91ea611790a?source=rss-9d98e8dadfc2------2"><img src="https://cdn-images-1.medium.com/max/1456/0*BcW0AqizWl5XlGuu.png" width="1456"></a></p><p class="medium-feed-snippet">Revisiting what managers bring to the table in the age of AI-driven layoffs</p><p class="medium-feed-link"><a href="https://medium.com/swlh/in-defense-of-the-managers-b91ea611790a?source=rss-9d98e8dadfc2------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/in-defense-of-the-managers-b91ea611790a?source=rss-9d98e8dadfc2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b91ea611790a</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Hafidz Zulkifli]]></dc:creator>
            <pubDate>Thu, 11 Jun 2026 06:40:40 GMT</pubDate>
            <atom:updated>2026-06-13T06:29:42.385Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Decision Architecture: The Missing Link in Management]]></title>
            <link>https://hafidz.medium.com/decision-architecture-the-missing-link-in-management-e10ea90add74?source=rss-9d98e8dadfc2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e10ea90add74</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[Hafidz Zulkifli]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 05:15:23 GMT</pubDate>
            <atom:updated>2025-12-16T05:15:23.793Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why capable managers become bottlenecks — and how teaching decision logic restores speed and trust</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KUTM16TEjGiOx6AN.png" /></figure><p>Your best individual contributor becomes a manager. Six months later, their team is slower, decisions pile up on their desk, and everyone — including them — wonders what went wrong.</p><p>Organizations routinely promote their strongest experts into management roles. The expectation is simple: excellence in craft, paired with good intentions and strong communication skills, should translate into effective leadership. Yet the outcome is often the opposite. Teams slow down. Decisions escalate upward. Managers become bottlenecks — despite being capable, diligent, and deeply invested in quality.</p><p><strong>This pattern is not a failure of leadership character or effort. It is a failure of explicit system design.</strong></p><p>What is missing in most management transitions is not vision, empathy, or goal-setting ability. It is the manager’s ability to understand, articulate, and teach the decision architecture embedded within the organization’s operating model — and the organization’s willingness and ability to make that architecture shareable.</p><h3>The expert-to-manager failure mode</h3><p>High-performing individual contributors succeed by optimizing for decision quality. They are rewarded for judgment, precision, and personal ownership of outcomes. When promoted, these same individuals are expected to optimize for something fundamentally different: <strong>decision throughput</strong>.</p><p>Most organizations do not teach this shift. New managers receive training on communication, feedback, and alignment, but rarely on how authority is distributed, how trade-offs should be made, or when escalation is expected. As a result, managers continue to apply expert instincts — reviewing, correcting, and deciding — inside roles that now require them to <strong>design how others decide</strong>.</p><p>The result is predictable. Decisions accumulate at the manager. Teams hesitate, escalate, or wait. Under pressure, managers intervene more, reinforcing dependency. Over time, both sides conclude that autonomy “doesn’t work,” when in reality it was never made explicit — and often never made safe to question, test, or refine.</p><p>To see what this looks like on the ground, it helps to make the failure concrete.</p><h3>What failure looks like in practice</h3><p>Imagine a customer service team at a bank that handles complaints about failed transactions, account access issues, and billing errors. Each agent is assigned KPIs for resolution time and customer satisfaction. The team lead coaches on empathy and communication. Performance dashboards are green.</p><p>Yet certain issues — like duplicate charges from third-party merchants or delays in refund processing — repeatedly require manager intervention. Agents follow the playbook, but when a customer demands immediate resolution or threatens to escalate publicly on social media, they ping the manager. The manager steps in, makes a judgment call on whether to issue a goodwill credit, override a policy, or escalate further to finance or legal.</p><p>The same scenarios recur weekly. Agents cannot predict when a waiver will be approved. Some customers get immediate credits; others are told to wait. The criteria seem to shift based on urgency, tone, or which manager is available. Agents become risk-averse, escalating borderline cases “just to be safe.” Customers sense the inconsistency and push harder, knowing that escalation increases their odds of a favorable outcome.</p><p>Nothing is obviously broken — tickets are closed, SLAs are met, complaints are handled. Yet agent burnout is high, customer trust is fragile, and the same issues never seem to improve structurally.</p><p>The bottleneck is not the manager’s judgment or the agents’ capability. It is the absence of clear, teachable decision logic: under what conditions can agents issue a credit without approval? What dollar thresholds require escalation? When does “customer threatens to go public” justify overriding policy versus when does it not?</p><p><strong>Without shared decision architecture, every judgment remains personal, inconsistent, and unscalable.</strong></p><h3>What decision architecture is (and is not)</h3><p>Decision architecture is often mistaken for bureaucracy. In reality, it is the practical logic that governs how authority and accountability flow. At a minimum, it answers three questions:</p><ul><li>Who decides what?</li><li>What constraints define acceptable decisions?</li><li>When and how should decisions be escalated?</li></ul><p>These are not abstract governance concerns. They are teachable concepts that must be translated into everyday language and reinforced through action.</p><p>Decision architecture lives in things like:</p><ul><li>The unwritten rule that “all pricing changes must go to the VP.”</li><li>The quiet understanding that “risk wins over revenue when in doubt.”</li><li>The pattern that “if a customer mentions social media, call a manager.”</li></ul><p>Every team has decision architecture. The problem is not that it does not exist. <strong>The problem is that it is invisible, inconsistent, and often only truly understood by a few people.</strong></p><p>When managers fail to make this architecture explicit — or when the environment makes it unsafe or unrewarded to do so — teams escalate by default. Not because they are incapable, but because the cost of guessing wrong, challenging precedent, or experimenting with new decision patterns is too high.</p><p>Making decision architecture visible is the first step. Making it usable and trustworthy is what unlocks autonomy.</p><h3>Autonomy as an outcome of predictability</h3><p>Autonomy is often framed as a cultural attribute — something teams either possess or lack. In practice, <strong>autonomy is an outcome of design, teaching, and environment</strong>.</p><p>Without explicit decision boundaries, escalation logic, and quality constraints, autonomy feels unsafe. Team members cannot predict when they are empowered to decide and when they will be corrected after the fact. In low-safety environments, they may also fear that asking for clarity will be interpreted as dissent or incompetence. Managers, sensing risk to standards or to their own accountability, step in to maintain control. <strong>The result is a familiar paradox: organizations talk about empowerment while centralizing decisions.</strong></p><p>Documentation alone does not solve this. Writing decision rules into a Confluence page is necessary but insufficient. What matters more than having the rules written is whether they are applied consistently. If managers override the documented logic when under pressure, or if exceptions are granted unpredictably, the team learns to ignore the document and escalate anyway.</p><blockquote><strong>Consistency builds predictability. Predictability builds trust. Trust makes autonomy feel safe.</strong></blockquote><p>Autonomy without understanding produces anxiety. Control without explanation produces compliance. A culture without safety produces silence. Effective management produces autonomy by teaching the rules of the game and creating conditions where those rules can be relied on and improved.</p><p>With that foundation, it becomes easier to see why some common patterns — like managers insisting on the final say — are not just personal quirks, but architectural issues.</p><h3>Decision architecture as a teaching problem</h3><p>Decision architecture is not just something to be designed; it must be taught.</p><p>At minimum, managers need to be able to explain, in plain language:</p><ul><li>The types of decisions their team owns outright.</li><li>The constraints that must never be violated (e.g., regulatory, risk, brand).</li><li>The triggers that require consultation or escalation.</li></ul><p>This is where many capable managers get stuck. They can make excellent decisions themselves, but they have never been asked to unpack <em>how</em> they decide: what signals they weigh, what trade-offs they treat as acceptable, and where their own red lines are.</p><p>Teaching decision architecture means:</p><ul><li>Turning personal judgment into shared principles and examples.</li><li>Using real cases (like that escalated customer complaint) to codify rules for next time.</li><li>Inviting questions and challenges so the logic can improve rather than ossify.</li></ul><p><strong>When managers fail to teach this architecture — or when the environment punishes them for doing so — teams remain dependent. The organization keeps rewarding expert problem-solvers instead of system designers.</strong></p><h3>When managers insist on having the final say</h3><p>In many teams, managers acknowledge the value of autonomy but still insist that final decisions come to them “because quality matters.” On the surface, this sounds like craftsmanship. Underneath, it usually signals a mix of issues: a manager identity still anchored in being the best problem-solver, low trust in current team capability, unclear accountability, and an environment where mistakes are costly to careers, not just to outcomes.</p><p>This is not a character flaw. It is a rational response to how the organization allocates risk and recognition. As long as accountability is personalized and decision rights are fuzzy, centralizing the final call will feel responsible.</p><p>The work is not to shame this instinct, but to redesign the conditions around it:</p><ul><li>Clarify where the manager truly must retain decision authority (e.g., regulatory exposure, reputational risk).</li><li>Define guardrails that make delegation safe (limits, thresholds, required checks).</li><li>Reward managers for scaling good decisions rather than personally making every critical one.</li></ul><p>The goal is to move from “I must decide this” to “I must define how this type of decision should be made, and under what constraints.” That is the shift from being the bearer of quality to being the architect of quality.</p><p>Even when this mindset begins to shift, managers still need practical arenas where decision architecture can be taught and reinforced. One of the most powerful of these is the interlock.</p><h3>Interlock sessions as decision-architecture classrooms</h3><p>Interlock sessions — used to resolve overlapping goals and dependencies — are often treated as coordination rituals. In reality, they are one of the most powerful teaching surfaces available to managers.</p><p>Before: Marketing and Product disagree on launch timing. The manager arbitrates, explains the reasoning to a few people, and moves on. The same issue recurs next quarter with new faces in the room.</p><p>After: The manager uses the session to establish a rule: “Product owns launch dates when features are incomplete. Marketing owns dates when positioning isn’t ready. Tie goes to Product.” The rule is documented in the team’s decision playbook and referenced in future planning. The next conflict resolves without escalation.</p><p>When used deliberately, interlocks clarify:</p><ul><li>Primary decision authority when goals conflict.</li><li>Non-negotiable constraints.</li><li>Default rules for future trade-offs.</li></ul><p>Their value lies not in resolving the immediate issue, but in making the rule explicit, tested, and accessible so the next occurrence does not require escalation. When interlocks also invite questions and challenge — rather than performative agreement — they become places where decision architecture is both taught and improved.</p><p>Well-run interlocks reduce the need for future interlocks. That is the signal that decision architecture is working.</p><p>Seen together, these patterns point to a broader truth: decision architecture is not a side concern. It is a core multiplier of team performance.</p><h3>A simple model of team effectiveness</h3><p>Team effectiveness can be understood as the interaction of three variables:</p><blockquote><strong><em>Team Effectiveness = Capability × Trust × Decision Architecture</em></strong></blockquote><p>Most organizations invest heavily in capability and trust. Training budgets, hiring standards, culture programs, and engagement surveys all live here. Decision architecture — the part that determines how authority actually flows — is assumed to emerge organically.</p><p>It does not.</p><p>When decision architecture is weak, increased capability leads to more escalation, not speed. Trust erodes under pressure as decisions feel inconsistent or political. Managers compensate by intervening. Teams become dependent. Knowledge stays local.</p><p>When decision architecture is strong, capability compounds through repetition. Trust becomes resilient because people can predict how decisions will be made and how disagreements will be resolved. Decisions decentralize without chaos. Knowledge about “how we decide” spreads beyond individual leaders and teams.</p><p>Understanding this model is one thing. Acting on it requires starting somewhere concrete.</p><h3>Where managers can start</h3><p>A practical starting point is deceptively simple. Managers should be able to answer — publicly and consistently — three questions with their teams:</p><ul><li>What decisions do you own without me?</li><li>What constraints must you never violate?</li><li>When do I expect escalation?</li></ul><p>If a manager currently acts as the final gate for most important decisions in the name of quality, the first step is not to let go blindly. It is to make that pattern explicit with the team: which decisions genuinely require the manager’s signature, why that is so today, and what would need to be true to push those decisions down. From there, managers can progressively convert “I must decide this” into “I must define the constraints and review the pattern.”</p><p>Then, they can use everyday moments to turn those answers into shared practice:</p><ul><li>In reviews, explain not just what changed but why, in terms of principles and constraints.</li><li>In interlocks, turn one-off trade-offs into reusable rules and document them.</li><li>In 1:1s, ask “How did you decide?” and tune the thinking, not just the outcome.</li></ul><p>Organizations can amplify this work by:</p><ul><li>Rewarding people who document and teach decision patterns.</li><li>Creating simple, living repositories for decision rules and precedents.</li><li>Building cross-functional forums where real decisions are dissected and understood, not just announced.</li><li>Raising the bar on psychological safety so that asking “Why do we decide this way?” is seen as diligence, not dissent.</li></ul><p>Until the answers to those three questions are shared, stable, and routinely challenged, autonomy will remain fragile and local.</p><h3>The real measure of management effectiveness</h3><p>A manager is not effective because they are involved in every decision. They are effective when:</p><ul><li>Decisions happen at the right level.</li><li>Quality holds without constant intervention.</li><li>The team functions in their absence.</li><li>The logic behind decisions is understood well enough to be taught to someone new.</li></ul><p>This is not abdication. It is competence at scale.</p><p><strong>When experts become bottlenecks, the cause is rarely a lack of leadership intent or interpersonal skill. It is the absence of explicit, taught decision architecture — the invisible rules that govern how work actually gets done — and the organizational conditions that keep that architecture trapped in a few heads.</strong></p><p>Organizations do not need managers to invent new, grand operating models. They need managers who can see the existing decision patterns, explain them clearly, and teach their teams how to operate within and improve them — and leaders who make that knowledge safe and worthwhile to share.</p><p>Management is not primarily about personally making every decision or constantly motivating people. It is about designing and maintaining conditions under which decision-making is teachable, scalable, and safe.</p><p>When that work is done well, managers become optional in the best possible way — and the organization gets stronger.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e10ea90add74" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How AI Will Transform the Relationship Between Product Managers and Product Analysts]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://hafidz.medium.com/how-ai-will-transform-the-relationship-between-product-managers-and-product-analysts-0840314dbca7?source=rss-9d98e8dadfc2------2"><img src="https://cdn-images-1.medium.com/max/1640/1*GYSE08qL9afJVpRH0PHZ2A.png" width="1640"></a></p><p class="medium-feed-snippet">If a PM can use AI for everything, do they still need the analysts?</p><p class="medium-feed-link"><a href="https://hafidz.medium.com/how-ai-will-transform-the-relationship-between-product-managers-and-product-analysts-0840314dbca7?source=rss-9d98e8dadfc2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://hafidz.medium.com/how-ai-will-transform-the-relationship-between-product-managers-and-product-analysts-0840314dbca7?source=rss-9d98e8dadfc2------2</link>
            <guid isPermaLink="false">https://medium.com/p/0840314dbca7</guid>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Hafidz Zulkifli]]></dc:creator>
            <pubDate>Sun, 19 Jan 2025 02:37:08 GMT</pubDate>
            <atom:updated>2025-01-19T02:43:24.313Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[From Individual Contributor to Lead: Balancing Leadership and Hands-On Execution]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://hafidz.medium.com/from-individual-contributor-to-lead-balancing-leadership-and-hands-on-execution-4817be6bc7f7?source=rss-9d98e8dadfc2------2"><img src="https://cdn-images-1.medium.com/max/1024/0*ATFtNghF3CfOOhvL" width="1024"></a></p><p class="medium-feed-snippet">How to balance guiding your team with rolling up your sleeves</p><p class="medium-feed-link"><a href="https://hafidz.medium.com/from-individual-contributor-to-lead-balancing-leadership-and-hands-on-execution-4817be6bc7f7?source=rss-9d98e8dadfc2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://hafidz.medium.com/from-individual-contributor-to-lead-balancing-leadership-and-hands-on-execution-4817be6bc7f7?source=rss-9d98e8dadfc2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4817be6bc7f7</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Hafidz Zulkifli]]></dc:creator>
            <pubDate>Mon, 16 Dec 2024 15:41:04 GMT</pubDate>
            <atom:updated>2025-01-02T01:52:07.344Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Pursuing Quality Without a Map: What Zen and the Art of Motorcycle Maintenance Teaches Us About…]]></title>
            <link>https://hafidz.medium.com/pursuing-quality-without-a-map-what-zen-and-the-art-of-motorcycle-maintenance-teaches-us-about-d61eab21e312?source=rss-9d98e8dadfc2------2</link>
            <guid isPermaLink="false">https://medium.com/p/d61eab21e312</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[excellence]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Hafidz Zulkifli]]></dc:creator>
            <pubDate>Wed, 02 Oct 2024 22:41:00 GMT</pubDate>
            <atom:updated>2024-10-02T23:41:03.623Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FeoUq_ANq9VfKvpW" /><figcaption>Image by author</figcaption></figure><h3>Pursuing Quality Without a Map: What Zen and the Art of Motorcycle Maintenance Teaches Us About Leadership and Craft</h3><h4>How do you pursue quality when you don’t have a clear standard to follow?</h4><p>It&#39;s easy to say &quot;let&#39;s aim for world-class,&quot; but what does that even look like when you’re leading a team with no real visibility into industry benchmarks? How do you know if you’re on the right path when &quot;industry standard&quot; is a vague term that seems to float above your head, just out of reach?</p><p>It’s a scenario I imagine many of us in leadership face, especially in fast-evolving fields where the definition of excellence shifts almost daily. If you&#39;re running a digital bank, a startup, or leading a data science team, the challenge is real. You&#39;re building towards &quot;quality,&quot; but often without a clear map.</p><p>Oddly enough, Robert Pirsig’s <a href="https://www.amazon.com.au/Zen-Art-Motorcycle-Maintenance-Anniversary-ebook/dp/B0063HC7EQ">Zen and the Art of Motorcycle Maintenance</a> offers some surprising insights for leaders in this situation. It’s not a book about business, but the philosophical discussions around the concept of Quality are rich with lessons for leadership and craftsmanship, especially when you’re working without a predefined “standard.”</p><p>Here’s what stood out to me and how it might reshape how you think about leading a team toward excellence.</p><h4>Quality is Intuitive – You Don’t Need a Definition to Pursue It</h4><blockquote>“But if you can’t say what Quality is, how do you know what it is, or how do you know that it even exists? If no one knows what it is, then for all practical purposes it doesn’t exist at all. But for all practical purposes it really does exist.”</blockquote><blockquote>— Robert Pirsig, from the book Zen and the Art of Motorcycle Maintenance</blockquote><p>In Zen and the Art of Motorcycle Maintenance, Pirsig argues that Quality is something we instinctively recognize, even if we can&#39;t pin down a precise definition. It exists in that moment when you know something &quot;just works&quot; – the way a product feels right, or when a process flows seamlessly. It’s beyond metrics or KPIs; it’s an intuitive sense of balance.</p><p>As a leader, this means that even if you don’t have a clear benchmark for what “world-class” means, you can still pursue Quality. The trick is to cultivate a culture where your team learns to recognize when something feels right, when their work is resonating at a higher level. You don&#39;t need a checklist for that. Trust in the intrinsic drive that every member of your team has – the desire to produce something that they themselves find valuable.</p><h4>Care as the Core of Craftsmanship</h4><blockquote>“Care and Quality are internal and external aspects of the same thing. A person who sees Quality and feels it as he works is a person who cares. A person who cares about what he sees and does is a person who’s bound to have some characteristic of quality.”</blockquote><blockquote>— Robert Pirsig, from the book Zen and the Art of Motorcycle Maintenance</blockquote><p>One of the central ideas in Pirsig’s philosophy is that Quality is inherently tied to care. When people care about what they do, Quality naturally follows. It’s not just about following processes or meeting deadlines. If your team genuinely cares about the work they are producing, if they take pride in every piece of code, every marketing campaign, every product release, then quality will emerge organically.</p><p>For a manager, this means your role is to cultivate an environment where people feel ownership and pride in what they do. You don’t need to point to an external standard and say, “This is what we need to achieve.” Instead, focus on making sure everyone on your team cares enough to chase excellence, however they define it in their work.</p><p>Care, when embedded into the culture, is far more powerful than mimicking an industry standard that may or may not even be relevant to your specific context.</p><h4>Quality Is Not Out There—It’s Within Your Team</h4><blockquote>“The place to improve the world is first in one’s own heart and head and hands, and then work outward from there.”</blockquote><blockquote>— Robert Pirsig, from the book Zen and the Art of Motorcycle Maintenance</blockquote><p>This is a big one. Pirsig suggests that Quality is not something that can be dictated by external standards. It&#39;s not some abstract ideal floating out there that you need to capture and measure against. Quality is something that emerges from the work itself, from the context of what your team is doing.</p><p>This is crucial for leaders. If you’re constantly looking outside for benchmarks, you may miss the unique strengths and innovations happening within your own team. Quality is something you can create and define from within, based on the values, creativity, and problem-solving abilities of your people.</p><p>Instead of chasing someone else’s version of &quot;world-class,&quot; why not define your own? Build internal benchmarks based on the impact your work is having, on the value you’re creating for your customers, and on the satisfaction your team gets from doing meaningful work. External standards may shift, but your own definition of excellence will always be relevant.</p><h4>Continuous Improvement – The Path to Mastery</h4><p>Finally, and perhaps most importantly, Pirsig’s approach to Quality emphasizes the importance of continuous improvement. Mastery doesn’t happen overnight, and neither does achieving “world-class” status. You don’t need to know what industry leaders are doing to begin improving. Start with where you are, keep learning, keep refining, and the standards will naturally emerge over time.</p><p>As a leader, this is where you can make the most impact. You don’t need to have all the answers. What you do need is a commitment to helping your team continuously reflect, iterate, and get better at their craft. Over time, as they improve, they’ll be able to match or even surpass those elusive external benchmarks without ever having chased them directly.</p><h4>Conclusion: Redefining Quality on Your Terms</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bm9Ex5bZcE2U4GH-" /><figcaption>Image by author</figcaption></figure><p>Pursuing quality without external benchmarks isn’t a disadvantage. In fact, it can be a liberating opportunity for your team to define what excellence looks like on their own terms. By focusing on care, balance, innovation, and continuous improvement, you don’t need to chase world-class standards—you can create your own version of them.</p><blockquote>Quality is not something you find — it’s something you create</blockquote><p>The real challenge for leaders is building a culture where quality emerges naturally, from within the team’s creativity, care, and dedication. As Pirsig reminds us, Quality is not something you find—it’s something you create.</p><p>If you enjoy the above, here are some other articles from me:</p><ol><li><strong>Data Science Leadership Paradox</strong>: <a href="https://medium.com/@hafidz/data-science-leadership-paradox-navigating-expectations-vs-reality-30ef56f1c6dc">https://medium.com/@hafidz/data-science-leadership-paradox-navigating-expectations-vs-reality-30ef56f1c6dc</a></li><li><strong>Lessons from No Rules Rules, Netflix and the Culture of Reinvention — Part 1</strong> : <a href="https://medium.com/@hafidz/lessons-from-no-rules-rules-netflix-and-the-culture-of-reinvention-part-1-a8aa898aaea">https://medium.com/@hafidz/lessons-from-no-rules-rules-netflix-and-the-culture-of-reinvention-part-1-a8aa898aaea</a></li><li><strong>Finding the Best Channel via Growth Hypothesis</strong> : <a href="https://medium.com/@hafidz/finding-the-best-channel-via-growth-hypothesis-9e48503c64a5">https://medium.com/@hafidz/finding-the-best-channel-via-growth-hypothesis-9e48503c64a5</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d61eab21e312" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data Science Leadership Paradox: Navigating Expectations VS Reality]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://hafidz.medium.com/data-science-leadership-paradox-navigating-expectations-vs-reality-30ef56f1c6dc?source=rss-9d98e8dadfc2------2"><img src="https://cdn-images-1.medium.com/max/1876/1*sgj1R0BiB9S2sbNz88HGwg.png" width="1876"></a></p><p class="medium-feed-snippet">Effective Management of Real-World Challenges in Data Science Teams</p><p class="medium-feed-link"><a href="https://hafidz.medium.com/data-science-leadership-paradox-navigating-expectations-vs-reality-30ef56f1c6dc?source=rss-9d98e8dadfc2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://hafidz.medium.com/data-science-leadership-paradox-navigating-expectations-vs-reality-30ef56f1c6dc?source=rss-9d98e8dadfc2------2</link>
            <guid isPermaLink="false">https://medium.com/p/30ef56f1c6dc</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Hafidz Zulkifli]]></dc:creator>
            <pubDate>Sat, 27 Apr 2024 19:50:45 GMT</pubDate>
            <atom:updated>2024-04-27T19:50:45.415Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Discovering Data Misrepresentation]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/data-science/how-to-lie-with-data-c58df403bdce?source=rss-9d98e8dadfc2------2"><img src="https://cdn-images-1.medium.com/max/2600/0*iKk15ETwoWYfRcPM" width="5472"></a></p><p class="medium-feed-snippet">A walkthrough in critically evaluating charts and figures</p><p class="medium-feed-link"><a href="https://medium.com/data-science/how-to-lie-with-data-c58df403bdce?source=rss-9d98e8dadfc2------2">Continue reading on TDS Archive »</a></p></div>]]></description>
            <link>https://medium.com/data-science/how-to-lie-with-data-c58df403bdce?source=rss-9d98e8dadfc2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c58df403bdce</guid>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[statistics]]></category>
            <dc:creator><![CDATA[Hafidz Zulkifli]]></dc:creator>
            <pubDate>Wed, 30 Nov 2022 21:14:12 GMT</pubDate>
            <atom:updated>2022-11-30T22:51:42.912Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Writing Stories with Illustrations with GPT-3 and DALL-E]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://hafidz.medium.com/writing-stories-with-illustrations-with-gpt-3-and-dall-e-9b17fe409442?source=rss-9d98e8dadfc2------2"><img src="https://cdn-images-1.medium.com/max/1024/1*qtBkIox2b7KSw9JDYVcFGg.png" width="1024"></a></p><p class="medium-feed-snippet">A short exploration on how content creators can leverage GPT-3 and DALLE in their creative process</p><p class="medium-feed-link"><a href="https://hafidz.medium.com/writing-stories-with-illustrations-with-gpt-3-and-dall-e-9b17fe409442?source=rss-9d98e8dadfc2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://hafidz.medium.com/writing-stories-with-illustrations-with-gpt-3-and-dall-e-9b17fe409442?source=rss-9d98e8dadfc2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b17fe409442</guid>
            <category><![CDATA[dalle-2]]></category>
            <category><![CDATA[copywriting]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[gpt-3]]></category>
            <category><![CDATA[illustration]]></category>
            <dc:creator><![CDATA[Hafidz Zulkifli]]></dc:creator>
            <pubDate>Tue, 21 Jun 2022 01:44:54 GMT</pubDate>
            <atom:updated>2022-06-21T01:44:54.935Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Lessons from No Rules Rules, Netflix and the Culture of Reinvention — Part 3]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://hafidz.medium.com/lessons-from-no-rules-rules-netflix-and-the-culture-of-reinvention-part-3-1263f1255aba?source=rss-9d98e8dadfc2------2"><img src="https://cdn-images-1.medium.com/max/800/1*t4t5tfNdGqP-S6LdpzCpxQ.png" width="800"></a></p><p class="medium-feed-snippet">The final entry of the lessons from the book.</p><p class="medium-feed-link"><a href="https://hafidz.medium.com/lessons-from-no-rules-rules-netflix-and-the-culture-of-reinvention-part-3-1263f1255aba?source=rss-9d98e8dadfc2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://hafidz.medium.com/lessons-from-no-rules-rules-netflix-and-the-culture-of-reinvention-part-3-1263f1255aba?source=rss-9d98e8dadfc2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1263f1255aba</guid>
            <category><![CDATA[netflix]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Hafidz Zulkifli]]></dc:creator>
            <pubDate>Sun, 20 Feb 2022 18:03:05 GMT</pubDate>
            <atom:updated>2022-02-20T18:03:05.276Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Lessons from No Rules Rules, Netflix and the Culture of Reinvention — Part 2]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://hafidz.medium.com/lessons-from-no-rules-rules-netflix-and-the-culture-of-reinvention-part-2-8cf030229784?source=rss-9d98e8dadfc2------2"><img src="https://cdn-images-1.medium.com/max/1016/1*rGQCzi-f4UCdGG1ZniL-uQ.png" width="1016"></a></p><p class="medium-feed-snippet">With talent density, candor, and freedom being introduced in Part 1; Netflix ramps it&#x2019;s cultural innovation to the next level.</p><p class="medium-feed-link"><a href="https://hafidz.medium.com/lessons-from-no-rules-rules-netflix-and-the-culture-of-reinvention-part-2-8cf030229784?source=rss-9d98e8dadfc2------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://hafidz.medium.com/lessons-from-no-rules-rules-netflix-and-the-culture-of-reinvention-part-2-8cf030229784?source=rss-9d98e8dadfc2------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cf030229784</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[netflix]]></category>
            <category><![CDATA[human-resources]]></category>
            <dc:creator><![CDATA[Hafidz Zulkifli]]></dc:creator>
            <pubDate>Mon, 08 Nov 2021 15:16:26 GMT</pubDate>
            <atom:updated>2021-11-08T15:16:26.262Z</atom:updated>
        </item>
    </channel>
</rss>