<?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 Sara Young on Medium]]></title>
        <description><![CDATA[Stories by Sara Young on Medium]]></description>
        <link>https://medium.com/@sara.young?source=rss-e3348b8ad89d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*7ShGaFSjLop0VYKo</url>
            <title>Stories by Sara Young on Medium</title>
            <link>https://medium.com/@sara.young?source=rss-e3348b8ad89d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:16:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sara.young/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[Why is process adherence so damn hard?]]></title>
            <link>https://medium.com/data-systems-internal-ai-personio/why-is-process-adherence-so-damn-hard-47f87062304b?source=rss-e3348b8ad89d------2</link>
            <guid isPermaLink="false">https://medium.com/p/47f87062304b</guid>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[operations]]></category>
            <category><![CDATA[human-behavior]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Sara Young]]></dc:creator>
            <pubDate>Fri, 02 Oct 2026 11:24:10 GMT</pubDate>
            <atom:updated>2026-10-02T11:33:30.156Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZHUId3g9JOHf7TiqYl2w7Q.png" /></figure><p>If this is a question you and your team are asking, or if you are interested in human behaviour, this article is for you.</p><p>This week, we had our Strategy &amp; Operations onsite. I lead the Strategy &amp; Ops team in DSAI (Data, Systems &amp; Internal AI) at Personio, and as an operations team, we design and manage a lot of processes. I knew one thing that was definitely going to come up at the onsite was the need to rethink some of these processes. Well overdue.</p><p>Before the onsite, I started thinking about the processes that exist today and why some of them seem so damn hard for people to follow. Quarterly planning, Jira hygiene, project updates to name a few.</p><p>Then I started thinking about processes in general. What even is a process? And what does it actually take to ensure a process gets followed?</p><h3>What even is a process?</h3><p>A process is a set of steps someone asks you to follow, because following them creates value for.. someone… but for whom?</p><figure><img alt="Image decribes the flow of a process, the steps that lead to an outcome and that outcome should provide value for … someone" src="https://cdn-images-1.medium.com/max/1024/1*NvPxBbcAM6htLGxQ6GGY5g.png" /></figure><p>Then I started thinking about the processes in my own day-to-day life <em>(you should do this too).</em> At the time, I was rinsing out my used couscous carton, getting ready to recycle it, and had to remind myself: do I need to take the label off or not? I read the box and see, oh yeah, I do need to take the label off this one before I recycle it.</p><p>Don’t worry, this is not an article about recycling. I know we all try our best. But there I was, following this process of taking off the label, rinsing the carton and separating it into two different bins, and it made me think: God, recycling is hard. This process is hard.</p><p>We all <em>want</em> to recycle (and we should), but if you look at the process today, the effort on the consumer is extremely high. It’s disproportionately high, especially compared to the effort for the other personas in the chain and the immediate (perceived) value for each.</p><p>Another way to put it: for everyone else in the chain the process is convenient, but for the consumer, high effort means low convenience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MOGd89jzobdk4OJ61u2X2Q.png" /><figcaption>Today the consumer is the only one in the chain with low convenience</figcaption></figure><p>Personally, I think this is why so many people don’t recycle, and why so many recycling plants end up with contaminated cartons. I don’t actually blame the consumer here. The <strong>process is broken.</strong></p><h3>The Process Matrix</h3><p>This is what led me to drawing up a Process Matrix. On the x-axis, we have convenience: how convenient is it to follow the steps, or in other words, how much effort it takes. On the y-axis, we have value or consequence, from low at the bottom to high at the top. Both are perceived, so it’s about how it feels to the person following the process.</p><p>Before you create any new process, you should map out where the people you’re expecting to follow it will likely sit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xEhC2VCWQtgmInIVGc2Rgg.png" /><figcaption>The Process Matrix: perceived effort (as convenience) against perceived value or consequence.</figcaption></figure><ul><li>High value + high convenience = <strong>Yes.</strong> People are likely to follow this process.</li><li>High value or consequence + low convenience = <strong>Maybe.</strong> They might.</li><li>Low value or consequence + low convenience = <strong>No.</strong> There’s really nothing in it for them, and it’s hard.</li><li>Low value or consequence + high convenience = <strong>Maybe.</strong> It’s easy to do, but why bother?</li></ul><p>Only one box in the Process Matrix is a reliable yes, and it’s our job in Operations to get our processes into that box, or as close to it as possible. And if we really can’t, we either move the effort to a different persona or we exnovate (remove the process altogether)!</p><h3>Giving the work to the least-cost avoider</h3><p>You’ll be glad to know the EU has already passed a law, the Packaging and Packaging Waste Regulation, which means that from 2030 all packaging must be designed for recycling. This hopefully means less label confusion. It’s going to be up to the manufacturer to make sure their packaging can be recycled, which means higher effort (lower convenience) for the manufacturer. There’s also a higher consequence: producers will pay higher fees when their packaging is harder to recycle.</p><p>Again, this is not an article about recycling. It’s about the Process Matrix in action, and how we need to consider not only which box a process sits in, but which persona can handle which box. This is what’s called the least-cost avoider: whoever can prevent a problem most cheaply should carry the job of preventing it.</p><p>In this example, the EU has made things easier for the consumer. Their value and consequence might stay roughly the same, but it’s easier, so they’re more likely to recycle. And it has shifted both the effort and the consequence to the manufacturer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LZh6d-caMSY-OTTKembHHw.png" /><figcaption>From 2030, the effort and the consequence move to the manufacturer, and the consumer’s job gets easier</figcaption></figure><h3>The bottle deposit</h3><p>There are a couple of other examples you can think of. The bottle deposit is a great one. Getting your deposit back for returning the bottle increases the value you get as the consumer for following that process, so people are more likely to do it. In Ireland, plastic bottle recycling went from 49% before the scheme to 91% by July 2025. But of course, there are still a lot of people who don’t claim their deposit back, and I think that’s because for some people, the convenience of returning is still too low.</p><h3>Takeaways</h3><p>My team have recently improved our quarterly planning process by adding a Claude skill to handle our DSAI intake forms. The skill asks a couple of questions, then outputs a structured project intake document, and only then is the project taken to the next step of planning, to be stack-ranked into the quarterly plan.</p><p>We had started to see that this was increasing process adherence, but only now, when we mapped it to the Process Matrix, did we realise why. What we were effectively doing was:</p><ol><li>Increasing the convenience for users to write up an intake plan</li><li>Increasing the “consequence”, given that items are only taken to the next planning step when we have the structured intake form</li></ol><p>At our onsite, we also started looking at our other key processes, like sprint planning and project documentation, and it’s already given us some great ideas on how to improve them to increase process adherence using this Process Matrix.</p><p>So next time you’re setting up a new process or reviewing existing ones, map them out on the Process Matrix, so you can make sure the effort is lying with the right person and the value is clear. And if a process isn’t being followed, ask yourself: is there a way to increase convenience, increase the perceived value or consequence?</p><p>Hope this helps!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47f87062304b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/data-systems-internal-ai-personio/why-is-process-adherence-so-damn-hard-47f87062304b">Why is process adherence so damn hard?</a> was originally published in <a href="https://medium.com/data-systems-internal-ai-personio">Data • Systems • Internal AI @ Personio</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Title:
Introducing the Personio Data & Systems Publication]]></title>
            <link>https://medium.com/@sara.young/title-introducing-the-personio-data-systems-publication-29c4e48d6a13?source=rss-e3348b8ad89d------2</link>
            <guid isPermaLink="false">https://medium.com/p/29c4e48d6a13</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[system]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Sara Young]]></dc:creator>
            <pubDate>Mon, 16 Feb 2026 11:17:35 GMT</pubDate>
            <atom:updated>2026-02-16T11:18:08.197Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Title:</strong><br>Introducing the Personio Data &amp; Systems Publication</p><p><strong>Subtitle:</strong><br>A space to share our work, experiments, and lessons in data and systems innovation at Personio.</p><p>The Personio Data and Systems team is launching this publication to share insights from our ongoing projects, engineering practices, and data initiatives.<br>Through short articles, technical deep dives, and process notes, we’ll document the ideas and methods shaping how we build and scale Personio’s data and systems foundations.</p><p>Follow this space to see how we approach data strategy, automation, system design, and everything that powers Personio from within.</p><p>— — — — — — — — — — — — — — — — — — — — — -<br>The Personio Data &amp; Systems Department</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29c4e48d6a13" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>