Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / How a Fulfillment Log Changed My Work Boundaries
Transcript
- Lucas: So a few months ago I started keeping what I called a 'fulfillment log.' Not a time log — not tracking where every minute went — but a log of what tasks actually left me feeling good versus drained. Luna: Okay, I want to hear the full method, but first — what prompted you to do it? Were you just feeling burned out? Lucas: Honestly? I was fine. But I noticed I had this recurring Sunday evening dread that wasn't about the volume of work — it was about specific things. I'd look at my week ahead and there'd be two or three items I'd physically recoil from. And I realised I couldn't articulate why those particular tasks bothered me. Luna: Right, because if you can't name the pattern, you can't fix it. Lucas: Exactly. So I started a simple spreadsheet. Three columns: the task, the energy after completing it — green, yellow, or red — and a one-line note on why. Did it for two weeks. Luna: Were the results surprising? Lucas: Very. I expected to discover that I hated administrative stuff — expense reports, scheduling, that kind of thing. And sure, those were red. But there were also a few tasks I'd always assumed were 'real work' — meaningful work — that were actually yellow bordering on red. One was reviewing draft press releases from our PR agency. I thought I was adding value by line-editing them. The log showed I felt irritated and slightly resentful every time, and the agency's version was usually fine without me. Luna: So you cut that task? Lucas: I outsourced it. I told the agency: 'You have full authority to publish unless you hear from me within 24 hours.' I set up a simple filter so I only get involved if there's a major announcement. That one change saved me about two hours a week. Luna: Two hours a week from one task. That's significant. Lucas: It added up. Over the two weeks I identified about five tasks that were consistently red or yellow. Together they represented maybe 20 percent of my weekly work hours — but probably 80 percent of my negative energy. Luna: So you're applying the Pareto principle to job satisfaction. Lucas: Exactly. And the boundary wasn't 'work less' — it was 'stop doing the work that drains me and doesn't need me.' The boundary was against my own habits, not against other people's requests. Luna: That's a subtle but important distinction, because most boundary-setting advice is about saying no to others. This is about saying no to yourself. Lucas: Right. And I think that's harder, because we've internalised that busyness equals value. But there's actually research on this. The University of Chicago did a study a few years ago on what they called the 'satisfaction paradox' — the finding that people who report the highest levels of career satisfaction aren't necessarily the ones doing the most work or the most important work. They're the ones doing work that aligns with their personal energy patterns. Luna: I remember that study. They followed knowledge workers for six months and found that satisfaction was more correlated with the ratio of energising to draining tasks than with total hours worked or even promotion rate. Lucas: Exactly. And that ratio is something you can actively manage — but only if you know what your energising and draining tasks actually are. That's what the fulfillment log does. Luna: Okay, but I have a skeptical question. Isn't this just another form of productivity optimisation? Like, 'track everything, optimise everything' — doesn't that risk turning your work life into a machine you're constantly tuning? Lucas: That's a fair critique. And I think it depends on how you use it. If you're logging every single task and trying to get your green to red ratio up to 100 percent, yes, that's obsessive. But I used it as a diagnostic — not a permanent tracking system. Two weeks, then act on the insights. Luna: So it's a bounded experiment, not a lifestyle. Lucas: Exactly. And the insight I got wasn't 'eliminate all red tasks.' Some red tasks are unavoidable. But I found that a few red tasks were actually tasks I could delegate, automate, or simply stop doing — and nobody would notice. The boundary was allowing myself to stop. Lucas: You know, it's funny — when I first started this I thought the log would lead me to negotiate with my boss for fewer responsibilities. Instead, it led me to renegotiate with myself about what I considered 'my job.' Luna: That's a really honest reframe. Because a lot of us expand our job descriptions silently, taking on things that no one asked us to do. Lucas: Exactly. And if we've been doing them for a while, they feel like requirements. The log made me realise that a few of my 'requirements' were entirely self-imposed. Luna: I want to ask about one specific category: meetings. Did any meetings show up red? Lucas: One big one. A weekly cross-team status update where I was basically a spectator. I was there 'for visibility,' but I realised I never spoke and never needed the information. I dropped it, and the organiser didn't even notice I was gone for three weeks. Luna: Three weeks! That's both funny and a little depressing. Lucas: It's a useful data point. If your absence from a meeting isn't noticed for a month, you probably didn't need to be there. Luna: So what about the flip side — did you find any green tasks that surprised you? Lucas: Yes. One was writing internal documentation. I'd always viewed it as low-value busywork, but the log showed I consistently finished those tasks feeling clear-headed and useful. So I actually started doing more of it — I volunteered to write the team's onboarding guide. Luna: So the log didn't just help you cut — it helped you redirect. Lucas: Exactly. And that's the part I think is under-discussed. Boundaries aren't just about saying no. They're also about saying yes to the right things. If you don't know what energises you, you can't protect time for it. Luna: Speaking of protecting time — this ties into something I've been reading about. Microsoft is piloting something similar at scale. They're calling it an 'energy audit' — basically a company-wide version of your fulfillment log. Employees track their tasks for two weeks, and then the company uses the aggregate data to redesign workflows. Lucas: I saw that. They published some early results from their 2025 work trend index. Teams that did the audit reduced low-energy tasks by an average of 18 percent over three months. And engagement scores went up. Luna: So it's not just an individual tool — there's an organisational version too. But I wonder if the company-level approach loses something. When you do it yourself, you're making the call about what to cut. When a company does it, they might cut the wrong things. Lucas: That's a real risk. But Microsoft's pilot was opt-in and employee-led. They gave teams the framework and let them decide. So it's more like providing a shared language for boundary-setting, rather than imposing it. Luna: I like that. A shared language. Because one problem with boundaries is that they feel individual, but they're often relational. If I drop a meeting, it affects others. If we all agree on the language of 'energising vs draining,' it becomes easier to negotiate. Lucas: Exactly. And that's where I think the fulfillment log is more powerful than just a personal productivity hack. It gives you data to have a real conversation. 'I'm going to stop attending this meeting because it consistently drains my energy and I'm not contributing' — that's a much stronger argument than 'I'm too busy.' Luna: The data makes it impersonal. It's not about your feelings; it's about the evidence. Lucas: Right. And that's actually freeing. You're not being difficult; you're being evidence-based. Lucas: I think the biggest takeaway from my experiment is that boundaries don't have to be dramatic. They can be small, data-informed adjustments that compound over time. Two hours a week is eight hours a month — that's an entire workday back. Luna: And an entire workday you can spend on things that actually energise you. Or, you know, leave the office earlier and use that hammock in the background. Lucas: The hammock is not just decorative, Luna. Luna: I believe you. So what's the one step someone should take this week if they want to try this? Lucas: Start a simple log. Paper, spreadsheet, notes app — doesn't matter. For every task you complete, assign it a color: green for energising, yellow for neutral, red for draining. After two weeks, look for patterns. Pick one red task and ask: 'What would happen if I stopped doing this?' You might be surprised. Luna: And if the answer is 'nothing,' you've found your boundary. Lucas: Exactly. And if the answer is 'something bad,' then you know what you need to negotiate. Either way, you have clarity. Luna: Alright, I'm actually going to try this. I have a feeling my red list is longer than I think. Lucas: Mine was too. But the good news is, you don't have to fix everything. Just the 20 percent that's costing you 80 percent of your energy. Luna: That's a good note to end on. If this episode gave you one small insight worth acting on, and if it saved you even a fraction of the time we talked about, you can support the show at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. No pressure, just a way to keep this ad-free and focused on what actually works. Lucas: Yeah, and honestly, even just knowing someone tried the fulfillment log because of this conversation — that's the real return. So thanks for listening, and we'll be back next week with another angle on making work actually work for you.