<?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 Harper Reid on Medium]]></title>
        <description><![CDATA[Stories by Harper Reid on Medium]]></description>
        <link>https://medium.com/@harperr89?source=rss-da406b55a6bb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jTDcNFZu90UIWvGJg51ieA.png</url>
            <title>Stories by Harper Reid on Medium</title>
            <link>https://medium.com/@harperr89?source=rss-da406b55a6bb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 01:18:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@harperr89/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 People Save Their Most Honest Feedback Until They’re Leaving]]></title>
            <link>https://medium.com/activated-thinker/why-people-save-their-most-honest-feedback-until-theyre-leaving-477c60859232?source=rss-da406b55a6bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/477c60859232</guid>
            <category><![CDATA[employee-feedback]]></category>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[office-culture]]></category>
            <category><![CDATA[exit-interview]]></category>
            <dc:creator><![CDATA[Harper Reid]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 17:47:25 GMT</pubDate>
            <atom:updated>2026-11-16T17:47:25.726Z</atom:updated>
            <content:encoded><![CDATA[<p>A few evenings ago, a friend and I were catching up over coffee when he mentioned he’d handed in his notice a couple of weeks earlier.</p><figure><img alt="two friends having a conversation over coffee" src="https://cdn-images-1.medium.com/max/1024/1*gjsAIm9AQ3wX3CZhzcKj9Q.avif" /><figcaption>Photo by Priscilla Du Preez 🇨🇦 from Unsplash</figcaption></figure><p>I expected a story about a better offer. What I got was a list.</p><p>During his handover, he told me he had calmly walked his manager through everything that had been wrong for as long as he could remember: a reporting process that had been broken for two years, a senior colleague who regularly took credit for his team’s work, and the extra job he’d absorbed after someone left and was never replaced.</p><p>His manager’s response was to ask why he had never said any of this.</p><p>He shrugged when he told me, “I did. Sort of. Nobody really asked.”</p><h3>The resignation honesty window</h3><p>Anyone who’s worked in HR knows this window. It opens the moment someone hands in their notice and closes on their last day.</p><p>Suddenly people talk. About the process everyone works around. About the meeting that should have been canceled in 2023. About the workload that was “temporary” eighteen months ago. Things they’ve quietly put up with for years come out in one honest handover.</p><p>And companies treat it like a revelation, as if this information appeared out of nowhere. It didn’t. It was there the whole time. It just wasn’t safe, useful, or worth it to say until now.</p><h3>Why now, and not two years ago?</h3><p>The short answer is that leaving changes the math.</p><p>While you’re staying, honesty has a price. Raise a problem about your manager and you still have to work with your manager on Monday. Point out a broken process, and you’re “being negative,” or worse, you’re now in charge of fixing it. Complain about workload, and there’s a small, nagging fear it ends up in your next review.</p><p>Once you’re leaving, most of that price disappears. There’s no promotion to protect and no awkward one-to-one next quarter. For maybe the first time, telling the truth costs you less than keeping quiet.</p><p>There’s also a quieter reason, and I think it’s the bigger one. Most people <em>did</em> try to say something. Early on. Softly. A comment in a one-to-one. A suggestion in a retro. A tired joke in the team chat. Nothing changed, so they stopped. Not because they stopped caring, but because they learned that talking didn’t do anything.</p><p>The resignation period isn’t when people start being honest. It’s when they stop filtering.</p><h3>The data is less surprising than it should be</h3><p>In 2024, Gallup found that 42% of employees who voluntarily left a job in the past year said their manager or organization could have done something to prevent it. That’s more than four in ten people walking out the door who thought it was avoidable.</p><p>The part that stuck with me is that 45% of all voluntary leavers said no manager or leader had proactively talked to them about their job satisfaction, performance, or future in the three months before they left.</p><p>So the conversation that would have helped didn’t happen. Then, once the decision was made, it finally did. Just too late to change anything.</p><h3>Exit interviews are a symptom, not the fix</h3><p>Companies love a good exit interview. I get it. It’s structured, it’s documented, and it feels responsible.</p><p>But think about what an exit interview actually is. It’s a company asking, “What should we have known?” at the exact moment they’re least able to do anything about it. The person is already gone. The best you can hope for is to save the <em>next</em> person.</p><p>And even then, a lot of exit feedback ends up in a spreadsheet nobody opens. I’ve seen companies where the same complaint about the same manager shows up in exit interview after exit interview. That isn’t a feedback gap. That’s a listening gap.</p><h3>What actually changes this</h3><p>I don’t think the answer is more surveys. Most people already have survey fatigue, and an anonymous form doesn’t fix a culture where honesty feels risky.</p><p>What I’d try instead:</p><ol><li><strong>Have “stay interviews” before you need exit interviews.</strong> Ask the questions you’d ask someone who’s leaving, but ask them now. What’s frustrating you? What would make you leave? What have you stopped bothering to mention?</li><li><strong>Fix one small thing fast.</strong> Nothing builds trust like someone raising an issue and seeing it actually change. Nothing kills it faster than silence.</li><li><strong>Make it safe to say it about the manager.</strong> If the only route for feedback runs through the person causing the problem, you won’t hear about the problem. Skip-levels, HR check-ins, anything that gives people a second door.</li><li><strong>Read the exit notes as a pattern, not a one-off.</strong> If three people mention the same thing, that’s not three opinions. That’s a finding.</li><li><strong>Watch the workarounds.</strong> When people quietly build their own spreadsheet to get around the official tool, that <em>is</em> feedback. It’s just not written in words.</li></ol><h3>The uncomfortable bit</h3><p>The most useful information in most companies isn’t hidden. It’s sitting with the people who already gave up on saying it.</p><p>Someone in your team right now probably has a two-year-old frustration they’ve stopped mentioning. They’re not going to bring it up at the next all-hands. They might bring it up in their handover.</p><p>The question is whether you want to hear it while they’re still there to help fix it, or after they’ve already shrugged and moved on.</p><figure><img alt="Author’s cat" src="https://cdn-images-1.medium.com/max/966/1*56DvtkZ3GHLmMWpDrscv-w.jpeg" /><figcaption>Currently saving her thoughts on this household for the exit interview</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=477c60859232" width="1" height="1" alt=""><hr><p><a href="https://medium.com/activated-thinker/why-people-save-their-most-honest-feedback-until-theyre-leaving-477c60859232">Why People Save Their Most Honest Feedback Until They’re Leaving</a> was originally published in <a href="https://medium.com/activated-thinker">Activated Thinker</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Time Tracking Apps I Tested as a Freelancer]]></title>
            <link>https://medium.com/tech-and-me/3-time-tracking-apps-i-tested-as-a-freelancer-76841462433b?source=rss-da406b55a6bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/76841462433b</guid>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[productivity-tools]]></category>
            <category><![CDATA[time-tracking-software]]></category>
            <category><![CDATA[time-tracking]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Harper Reid]]></dc:creator>
            <pubDate>Thu, 22 Oct 2026 10:48:19 GMT</pubDate>
            <atom:updated>2026-10-22T10:48:19.983Z</atom:updated>
            <content:encoded><![CDATA[<h4>Time tracking has a genuinely bad reputation for something so boring. People hear it and think surveillance, micromanagement, somebody standing behind your chair with a clipboard. I used to think that too.</h4><figure><img alt="photo of checking notifications on phone while coffee waits" src="https://cdn-images-1.medium.com/max/1024/1*h0FsCNwFwRais6X-Bd66pQ.jpeg" /><figcaption>Photo by Milad Fakurian on Unsplash</figcaption></figure><p>Here’s the thing nobody tells you: tracking your own time, voluntarily, for nobody but yourself, is almost embarrassingly satisfying.</p><p>There’s a small, specific pleasure in finally knowing something you’ve always just guessed at:</p><ul><li>How long does writing an email actually take?</li><li>How much of a “quick call” is setup versus substance?</li><li>Did that project really take eight hours, or have you just been telling yourself it did?</li></ul><p>There’s a name for why I kept getting this wrong: the planning fallacy, the well-documented tendency to assume a task will take as long as it did the one time everything went right.</p><p>Back then, I didn’t know the term existed. I just knew my invoices never quite matched reality, and I couldn’t figure out why.</p><p>A timer doesn’t lie to you the way your memory does. It tells you whether that “quick call” was actually quick, or whether the project you swore took eight hours quietly stretched into twenty.</p><p>As a freelancer, the appeal was obvious, but so was the budget problem. I wasn’t about to add a monthly subscription to find out something I wasn’t even sure I needed to know yet. So my search started with one filter: free and actually free, not free-for-two-weeks.</p><p>Here are the few time tracking apps I tried:</p><h3>TrackingTime</h3><p>As the name suggests, TrackingTime is built around tracking time, and its free plan looks quite good: unlimited projects, unlimited clients, no seat cap, and the app can work on my desktop, phone, and browser.</p><p>Compared to spreadsheets, it feels like a real upgrade. The timer runs smoothly, projects stay separate, and I get a record of my week that isn’t stitched together from memory. It also keeps things simple on the privacy side, with self-reported time entries and no screenshots or keystroke logging, which fits the idea of tracking your own hours for yourself.</p><p>One thing I only properly understood once I looked closer: TrackingTime isn’t just a timer; it’s built as the operational back office for agencies and professional services. Its paid plans let companies bill retainers, route timesheets through approvals, and even give clients their own login to check hours in real time.</p><p>That’s also where the free plan runs out. Tracking itself is free, but billable rates and invoicing aren’t included, and timesheets and reports export only as PDFs, with CSV and Excel behind an upgrade.</p><p>If you’re a small agency or a team billing retainers, TrackingTime is built for you. As a solo freelancer who just wants to bill for hours, you might outgrow the free plan quickly.</p><h3>Clockify</h3><p>Clockify is the one almost everyone has heard of, and I get why. The browser extension makes starting the timer painless, and the numbers it gives back can be a little uncomfortable, in a useful way. Tasks I’d have sworn took twenty minutes are quietly stretching into forty.</p><p>Clockify also offers a free plan, but it’s now been limited to five users since April.</p><p>With the user cap, it seems reports on the free plan have also moved to covering a 31-day window only. CSV and Excel exports sit behind a paid plan now, so Free means PDF only. Setting an hourly rate or marking time as billable needs an upgrade too.</p><p>The user cap doesn’t touch a solo freelancer like me, but the reporting and billing limits do. A 31-day report window means you won’t be able to see a quarter’s worth of work without stitching exports together.</p><h3>Jibble</h3><p>Jibble is the one I actually use for my own tracking, and it covers more than I expect for free.</p><p>The Chrome extension is the reason it works for me. The timer sits right there in the browser I already have open all day, so starting it isn’t something I have to remember. It’s something my hands do.</p><figure><img alt="using Jibble’s browser extension for time tracking" src="https://cdn-images-1.medium.com/max/1024/1*Nbj90fXLl0b9-FA8FptpKw.png" /><figcaption>Photo of using Jibble’s Chrome extension by the author</figcaption></figure><p>Clients and projects stay separate. If I forget to stop a timer or track something wrong, I can fix the entry. Reports run over whatever stretch I want instead of a fixed window, with an export to Excel whenever I want to look at something properly.</p><p>The part that matters most: I can turn tracked hours straight into an invoice and set project-specific rates, in whatever currency a client pays me in, without it becoming a second piece of software to manage.</p><p>And I don’t pay for any of it: the timer, the corrections, the reports, the billing and invoicing. None of it sits behind a subscription.</p><p>There’s a whole techy side of Jibble that I barely touch: GPS tracking, geofencing, facial recognition, a shared kiosk, QR code, RFID, and NFC, clearly built for a company with people clocking in on a site somewhere. It also connects to Claude now, which is something I’d like to try sometime. None of it is why the app is still open on my laptop.</p><p>If you’re a solo freelancer who wants time tracking and invoicing without another subscription, this is the one I’d point you to.</p><h3>What actually changed when I started tracking time</h3><p>I thought tracking my time would just fix my invoices. It did that, eventually, but that’s not the part that stuck.</p><p>What actually changed is smaller and stranger. I stopped having that vague, low-grade anxiety about where my day went, the kind that shows up at six in the evening when you’re tired but can’t point to anything you finished.</p><p>I know now. Some days that’s a relief. Some days it’s just mildly annoying, like finding out a meeting really was as pointless as it felt.</p><p>I also started saying “quick call” less, mostly out of guilt, since I’m one of the people who knows exactly how long those actually run.</p><p>I don’t think the number itself is the point. The point is that I stopped operating on a story I was telling myself about my own week, and started operating on something closer to what actually happened.</p><p>That’s a small shift. It’s also the only productivity habit I’ve kept that didn’t ask me to become a different kind of person to use it; it just asked me to stop guessing.</p><figure><img alt="Photo of author’s cat, her work partner" src="https://cdn-images-1.medium.com/max/966/1*bWWZrtHs9qr6v3jreGqlTw.jpeg" /><figcaption>The real co-founder of this whole testing operation</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76841462433b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tech-and-me/3-time-tracking-apps-i-tested-as-a-freelancer-76841462433b">3 Time Tracking Apps I Tested as a Freelancer</a> was originally published in <a href="https://medium.com/tech-and-me">Tech and Me, Loving It or Hating It</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Working With Different Clients Taught Me About People]]></title>
            <link>https://medium.com/activated-thinker/what-working-with-different-clients-taught-me-about-people-c2a948a45241?source=rss-da406b55a6bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2a948a45241</guid>
            <category><![CDATA[clients]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[work-tips]]></category>
            <dc:creator><![CDATA[Harper Reid]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 15:14:00 GMT</pubDate>
            <atom:updated>2026-10-09T15:14:00.164Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cBHANXq7xe_oDBjZzTAI-Q.jpeg" /><figcaption>Photo by Luca Bravo on Unsplash</figcaption></figure><p>A few months ago, a client ended a perfectly normal call by saying, “Sorry I’ve been such a pain. It’s been a rough quarter.”</p><p>I hadn’t thought of her as a pain at all. Demanding, sure. Fond of 11 p.m. emails, absolutely. But a pain? No. She was just someone under pressure, doing her best to keep a lot of plates in the air.</p><p>That little apology stuck with me. I realized I’d spent years thinking client work was about deliverables, deadlines, and invoices. It turns out it’s mostly about people. Every client I’ve worked with has taught me something about how people actually work. That includes the easy ones, the chaotic ones, and the ones who ghosted me for three weeks and then needed everything by Friday.</p><p>Here’s what stuck.</p><h3>People rarely ask for what they actually need</h3><p>Early on, I took every brief literally. If a client asked for “an updated employee handbook,” I gave them an updated one. Then I’d watch their face fall on the review call and wonder what I’d missed.</p><p>What I’d missed was the real request hiding underneath. “An updated handbook” usually meant “something happened with an employee and we had nothing in writing to point to.” “Can you make our policies clearer?” meant “I don’t know what’s wrong, but something is.”</p><p>These days, I ask one extra question before I start anything: What made you reach out now? The answer almost never matches the brief. And it’s almost always more useful.</p><p>This isn’t just a client thing, either. Most of us are bad at saying what we need. We describe the symptom because the cause feels too vague, too personal, or too awkward to say out loud. Good listening isn’t hearing the words. It’s getting curious about why someone chose them.</p><h3>“Difficult” usually means scared</h3><p>I once worked with a client who questioned everything. Every clause in the policy. Every word in the job description. Every line item on the invoice. For the first month, I dreaded seeing his name in my inbox.</p><p>Then, on a late call that ran long, he mentioned this project was his first big decision since a promotion. If it flopped, everyone would know.</p><p>Suddenly, the nitpicking made sense. He wasn’t trying to make my life harder. He was trying to make sure nothing could go wrong on his watch.</p><p>I stopped defending my choices and started explaining them. I sent short updates before he could ask. I flagged risks early, so he never had to find them himself. Within a few weeks, the twenty-email threads became two-line replies. Same person. Less fear.</p><p>I think about him whenever someone seems unreasonably prickly, whether at work, at home, or anywhere else. Control is often just anxiety wearing a blazer.</p><h3>Trust is built in boring moments</h3><p>I used to think big wins earned trust. Nail the policy rollout, blow them away with the presentation, and they’d be yours forever.</p><p>Nope.</p><p>The clients who’ve stayed with me the longest didn’t stay because of one brilliant project. They stayed because I replied when I said I would. Because I told them about a delay on Tuesday instead of Friday. Because when I made a mistake, I said “that’s on me” before they had to point it out.</p><p>None of that is impressive. Nobody’s putting “answered emails within a day” in a consulting proposal. But trust is less like a trophy and more like a savings account. Small, regular deposits. Nothing flashy. And it adds up faster than you’d expect.</p><p>The flip side is also true. One missed deadline with no heads-up can drain months of goodwill. People forgive mistakes. They struggle to forgive surprises.</p><h3>Boundaries make relationships better, not colder</h3><p>For a long time, I thought being a “good” freelancer meant being endlessly available. Weekend messages? Sure. A “quick policy check” that was actually a full HR audit? Happy to help. Rates? Oh, whatever works for you.</p><p>I was exhausted. And the work wasn’t getting better. It was getting resentful.</p><p>The first time I told a client, “I’m offline on weekends, but I’ll pick this up first thing Monday,” I braced for a breakup. Instead, they said, “Totally fair.” That was it. No drama.</p><p>What surprised me most was that clear boundaries made people <em>more</em> comfortable, not less. When they knew how I worked, they stopped guessing. They planned around it. Some even started protecting their own weekends.</p><p>Most people don’t want a yes-machine. They want someone reliable. And it’s hard to be reliable when you’re running on fumes.</p><h3>What clients taught me about me</h3><p>Here’s the part I didn’t see coming. Every lesson I learned about clients turned out to be a lesson about myself.</p><p>I’m also someone who describes the symptom instead of the problem. I also get prickly when I’m scared of failing. I also trust people more because of small, consistent things than big gestures. And I also needed boundaries long before I was brave enough to set them.</p><p>Working with different clients didn’t just make me better at my job. It made me more patient with people in general, and a little more honest about what I need from them.</p><p>So, to the client who apologized for being a pain: you weren’t. But thank you. You reminded me that behind every brief, every deadline, and every slightly frantic email, there’s just a person having a long week.</p><p>Most of us are.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/966/1*56DvtkZ3GHLmMWpDrscv-w.jpeg" /><figcaption>My partner who sat beside every deadline</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2a948a45241" width="1" height="1" alt=""><hr><p><a href="https://medium.com/activated-thinker/what-working-with-different-clients-taught-me-about-people-c2a948a45241">What Working With Different Clients Taught Me About People</a> was originally published in <a href="https://medium.com/activated-thinker">Activated Thinker</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We All Have a Favorite Kind of Busy]]></title>
            <link>https://medium.com/activated-thinker/we-all-have-a-favorite-kind-of-busy-b33c97deffa4?source=rss-da406b55a6bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/b33c97deffa4</guid>
            <category><![CDATA[workday]]></category>
            <category><![CDATA[busyness]]></category>
            <dc:creator><![CDATA[Harper Reid]]></dc:creator>
            <pubDate>Sun, 04 Oct 2026 00:36:08 GMT</pubDate>
            <atom:updated>2026-10-04T00:36:08.153Z</atom:updated>
            <content:encoded><![CDATA[<p>Last Tuesday I answered forty-one emails.</p><p>I want to be clear that nobody needed forty-one emails answered. Some of those threads had been peacefully dead for a week, and I resurrected them personally, like someone going door to door reminding the neighbors of unfinished business. I replied to a “thanks!” with a “no problem!” I archived things. I made two folders. At one point, I recategorized a label from Pending to Waiting, which I maintain was the correct call.</p><p>And the whole time, sitting in another tab, was the one document I’d actually promised to write.</p><p>I didn’t open it. I didn’t decide not to open it either. I just kept being extremely busy in the immediate vicinity of it, the way you hover near a cold swimming pool doing stretches you don’t need.</p><p>That was the day I worked out something slightly embarrassing: I am never avoiding work. I’m just picking my favorite kind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wpXhRs2wb4PahT9ZJt8xWg.jpeg" /><figcaption><em>Photo of a work desk by Sash Gabriel on Dupe</em></figcaption></figure><h3>Busy is not one thing</h3><p>We talk about being busy like it’s a single condition. You’re busy, or you’re not, and if you’re busy, you’re presumably doing the things.</p><p>But nobody is generically busy. Everyone has a flavor. There’s a specific type of work each of us slides into when we don’t want to think, and the tell is that it still feels like effort. That’s what makes it so good. You’re not scrolling. You’re not asleep. You’re producing. You just happen to be producing in the one category that costs you nothing emotionally.</p><p>Mine is admin. Give me a stressful week, and I will come out of it with an immaculate folder structure and nothing actually delivered. You could eat off it.</p><p>I should be honest that this is not tidiness. I am not a tidy person, and I have the abandoned systems to prove it. My inbox lives permanently at a number I have stopped arguing with. But give me something I’m dreading, and I will suddenly, temporarily, become the most organized person you have ever met, for exactly as long as the dreading lasts.</p><h3>Everyone’s got a type</h3><p>Once you start looking, you can spot everyone’s.</p><p><strong>Inbox busy.</strong> Treats replying as a deliverable. Measures the day in unread count. Will respond to your message in ninety seconds and to your actual request in three weeks.</p><p><strong>Meeting busy.</strong> Calendar is a Tetris board that never clears a line. Genuinely exhausted, genuinely well-informed, could not tell you what they personally made this quarter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9F1X291Z20TyAFfWdhoexA.jpeg" /><figcaption>The only one in this house with an empty calendar</figcaption></figure><p><strong>Tidying busy.</strong> Renames files. Reorganizes the project board. Once spent an afternoon standardizing the naming convention for documents nobody opens. (Hello.)</p><p><strong>Helper busy.</strong> Cannot start their own thing until everyone else is unblocked, and everyone else is never unblocked. This one is the most dangerous because it’s genuinely virtuous and gets praised constantly, so it never gets examined.</p><p><strong>Research busy.</strong> Three months into “figuring out the right approach.” Has read everything. Has built nothing. Will send you a link instead of a decision.</p><p><strong>Firefighting busy.</strong> Only fully alive during an incident. Slightly disappointed when things are calm. Has, on some level, started needing the fires.</p><p><strong>Planning busy.</strong> The roadmap is beautiful. It is a genuinely lovely artifact. Nothing on it has moved in two quarters, but the color coding is immaculate.</p><p>Most people are one of these with a secondary. And almost nobody thinks of theirs as avoidance, because it doesn’t feel like avoidance. It feels like Tuesday.</p><h3>Why we pick what we pick</h3><p>Here’s my theory, for what it’s worth.</p><p>Your favorite kind of busy is whichever one gives you feedback fastest.</p><p>Answering an email takes ninety seconds and ends in a small, clean, definite done. Clearing a notification badge is instant. Helping a colleague gets you an immediate thank-you, which is a nicer thing to receive than the silence of a document you’re halfway through.</p><p>The hard thing has none of that. The hard thing is four hours of no feedback at all, followed by a draft you dislike. There’s no progress bar. You can work on it for a whole morning and be measurably further from finishing than when you started, because you’ve discovered a problem you didn’t know about. Nobody claps.</p><p>So we don’t avoid it out of laziness. We avoid it because the alternative pays out in certain amounts, immediately, and the brain is not a long-term investor.</p><p>The result is a strange kind of day where you’re completely spent by 6 pm and could not honestly name a single thing you moved forward. You didn’t waste the day. You just spent it entirely in your favorite currency.</p><h3>Teams have one too</h3><p>This is the part that took me longer to notice, and I only noticed it because I keep arriving at companies as an outsider with a temporary account and nothing to do for the first few days but watch.</p><p>Organizations develop a house flavor of busy, and it’s usually inherited from whoever’s in charge. A leader who’s “Meeting busy” produces a company where the week is structurally full of alignment and structurally empty of building. A founder who’s Firefighting busy produces a team that unconsciously generates emergencies, because emergencies are when you get attention and resources and permission to move fast.</p><p>I worked with a small, fast-growing company last year where nothing could be scheduled and everything could be dropped. Every week had a crisis in it. It took me an embarrassingly long time to notice that the crises were not arriving from outside. The company had simply learned that urgency was the only reliable way to get a decision out of anyone, so it manufactured some.</p><p>You can spot it in how a company answers “what did we do this quarter?”</p><p>If the honest answer involves a lot of process, a lot of alignment, a lot of groundwork, and very little of this thing now exists that did not exist before, that’s not a lazy company. That’s a company with a collective favorite, and everybody in it is exhausted.</p><p>Nobody is going to fix that in a retro. The retro is, frequently, the favorite.</p><h3>What actually helps, a bit</h3><p>I don’t have a system for this, and I say that as someone who has tried a genuinely humiliating number of them. The handful that survived are too small to deserve the word. Do the two-minute thing now rather than writing it down. Protect one chunk of the day and accept that you’ll break it. Pick tomorrow’s three things the night before. None of them touch this particular problem.</p><p>What’s helped is smaller than a system. It’s mostly just naming it.</p><p>Once you know your flavor, you start catching yourself mid-slide. I now notice the exact moment I reach for the inbox, and it’s always the same moment: about ninety seconds after opening the hard thing, right when it gets uncomfortable and before it gets interesting. That gap is a ninety-second problem, not a discipline one.</p><p>The other thing that helps is admitting that the hard thing needs fake feedback, because it won’t produce real feedback for days. So I give it a shape that pays out sooner. Not “write the document” but “write the bad version of the first section.” Not “fix the thing” but “find out what’s actually broken.” Small enough that something lands before my attention goes shopping.</p><p>And then the slightly annoying one: doing it first. Not because mornings are magic. I tested that theory once and spent a week tired and faintly emotional about it. I do it first because my favorite kind of busy is infinitely available. The inbox will still be there at four. It is always there at four. It’s the most patient thing in my life.</p><h3>Not the villain</h3><p>I want to be careful, because this could easily curdle into the usual thing where anything that isn’t Deep Focused Output gets classified as a moral failure. That’s not it.</p><p>Admin is real work. Helping people is real work, often the most valuable work in the building and almost entirely unmeasurable, which is why it’s the work I most often find missing when a manager lists who’s carrying their team. None of these categories are fake. They’re all legitimate jobs that legitimately need doing.</p><p>The only question worth asking is whether you chose the one you’re in, or whether you drifted there because it was the one that hurt least.</p><p>Most weeks, for me, it’s the drift. And I’d be more embarrassed about that if my folder structure weren’t so good.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b33c97deffa4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/activated-thinker/we-all-have-a-favorite-kind-of-busy-b33c97deffa4">We All Have a Favorite Kind of Busy</a> was originally published in <a href="https://medium.com/activated-thinker">Activated Thinker</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why “Can We Hop on a Quick Call?” Never Means a Quick Call]]></title>
            <link>https://medium.com/activated-thinker/why-can-we-hop-on-a-quick-call-never-means-a-quick-call-e57640ccf53a?source=rss-da406b55a6bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/e57640ccf53a</guid>
            <category><![CDATA[remote-work-tips]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[team-calls]]></category>
            <dc:creator><![CDATA[Harper Reid]]></dc:creator>
            <pubDate>Sat, 19 Sep 2026 06:06:23 GMT</pubDate>
            <atom:updated>2026-09-19T06:06:23.333Z</atom:updated>
            <content:encoded><![CDATA[<p>It was 4:47 on a Thursday when the message came in.</p><p>“hey! free for a quick call?”</p><p>No subject. No context. Just a lowercase greeting and an exclamation mark doing an enormous amount of emotional labour. I looked at it for a while. Then I looked at my calendar, which had thirteen minutes of daylight left in it. Then I looked back at the message, which had by then been marked as read, which meant the clock was running.</p><p>I said yes, obviously. Everyone says yes.</p><p>Forty-one minutes later I hung up, opened a blank document, and stared at it for a bit trying to remember what I’d been doing before. I never did remember. Whatever it was, it died on that call, and nobody said a word at the funeral.</p><h3>“Quick” is not a measurement</h3><p>Here’s the thing I’ve come to believe: the word quick in “quick call” is not describing the call. It’s describing how the other person feels about asking.</p><p>It’s a softener. A little apology stapled to the front of the request so it lands gently. Nobody writes “can we hop on a 45-minute call where I think out loud at you and arrive at a decision I could have reached alone.” They write “quick.” And they mean it sincerely, in the way you sincerely mean it when you say you’ll be there in five minutes from a car that has not yet started.</p><p>The estimate isn’t a lie. It’s a hope.</p><figure><img alt="Image of author’s cat laying" src="https://cdn-images-1.medium.com/max/953/1*8AlVagj4ErVX6zKZxbTx1g.png" /><figcaption><em>The face I make the second someone says, “It’ll be quick.”</em></figcaption></figure><h3>The maths nobody does</h3><p>A call booked for fifteen minutes is never fifteen minutes. Let’s be honest about what actually gets spent.</p><p>There’s the four minutes of hellos and “can you hear me” and someone’s dog. There’s the actual content, which expands to fill whatever space you’ve given it, plus a bit. There’s the twelve minutes at the end where the real topic finally surfaces, because the real topic is always the last thing anyone says. And then there’s the part nobody counts: the twenty minutes beforehand where you can’t start anything meaningful because you have a call soon, and the twenty minutes afterwards where you can’t start anything meaningful because you just had a call.</p><p>So the quick call cost about an hour. Possibly your whole afternoon, if it was the kind that leaves you needing a walk.</p><p>I’m not even being dramatic about the dread portion. A vague “quick call?” with no agenda from someone senior to you is an hour of low-grade cortisol at absolutely no cost to the sender. They typed four words. You reorganized your nervous system.</p><h3>Why it keeps happening</h3><p>I want to be fair here, because I send these too and I’m not a monster.</p><p>The reason “quick call?” is so popular is that it’s the cheapest possible message for the person sending it. Writing things down is work. You have to figure out what you actually think, arrange it in an order, and then live with it existing in writing where someone could quote it back to you in four months. A call skips all of that. You can arrive half-formed and think out loud and nobody keeps the transcript.</p><p>That’s not laziness so much as it’s a transfer. The effort doesn’t disappear; it just moves from the person asking to the person answering. One side saves ten minutes of writing. The other side loses an hour and the thread of what they were doing.</p><p>And because calendars are free and typing “quick call?” takes three seconds, there’s nothing in the system that makes anybody feel that trade.</p><h3>A short field guide</h3><p>After a few years of paying attention, I can now roughly classify these on arrival.</p><p>“Quick call?” with no context, sent at 4:45pm. Something has gone wrong and they’d rather not put it in writing.</p><p>“Quick call?” with a smiley face. Genuinely fine, but will take thirty minutes because they’re lonely and working from their kitchen.</p><p>“Quick sync to align on next steps.” There are no next steps. This is a meeting to decide whether to have a meeting.</p><p>“Easier to just explain on a call.” It is not easier. It is easier for them, which is a different sentence.</p><p>“Just 5 mins I promise.” The promise is load-bearing and it will not hold.</p><p>“Do you have two minutes?” This one is occasionally real. Roughly one in six. Keep hope alive.</p><h3>What I started doing instead</h3><p>I’m not anti-call. Some things genuinely need voices — anything with feelings in it, anything where three people disagree and it’s getting weird in a thread, anything where you need to hear the pause before someone answers. Trying to resolve a real conflict over Slack is how you turn a disagreement into an incident.</p><p>What I’m against is the mystery.</p><p>So now I reply with one sentence, every time, without apologizing for it: “Sure — what’s it about?”</p><p>That’s it. Not “can you send that in an email instead,” which reads as hostile even when you don’t mean it to. Just a question, the way you’d ask anyone anything.</p><p>What happens next is the interesting part. Maybe a third of the time, the answer to “what’s it about” turns out to be the whole call. They type two sentences explaining the topic, I type two sentences answering it, and the thing is done in ninety seconds. The call was never needed. It was just the first tool they reached for.</p><p>Another third of the time, they tell me the topic and the call goes ahead — but now it’s a different call. I’ve had ten minutes to think. They’ve had to articulate the point. We start at the middle instead of the beginning and finish in the time they originally claimed.</p><p>The last third, the answer is “I’d rather just talk,” which is genuinely useful information. That’s a call about something real, and I should probably clear my afternoon rather than my fifteen minutes.</p><h3>The small thing</h3><p>Nobody’s going to fix this at an organizational level. There will not be a policy. There is no tool you can install that makes people specify what they want before they want it.</p><p>But the fix is embarrassingly small. Four extra words on the way out: “quick call about the invoice thing?” That’s all. Now I know what I’m walking into, I know whether it’s actually quick, and I know I don’t have to spend the intervening twenty minutes mentally drafting my resignation.</p><p>The people who add the four words, I clear space for immediately. The people who don’t, I answer with a question.</p><p>It’s not a boundary. I don’t think it even counts as a boundary. It’s just refusing to attend a meeting whose topic is a surprise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e57640ccf53a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/activated-thinker/why-can-we-hop-on-a-quick-call-never-means-a-quick-call-e57640ccf53a">Why “Can We Hop on a Quick Call?” Never Means a Quick Call</a> was originally published in <a href="https://medium.com/activated-thinker">Activated Thinker</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Weird Anxiety of Sending an Invoice You Already Earned]]></title>
            <link>https://medium.com/activated-thinker/the-weird-anxiety-of-sending-an-invoice-you-already-earned-2171b3485a8e?source=rss-da406b55a6bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/2171b3485a8e</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[anxiety]]></category>
            <category><![CDATA[jobs]]></category>
            <dc:creator><![CDATA[Harper Reid]]></dc:creator>
            <pubDate>Wed, 26 Aug 2026 21:56:19 GMT</pubDate>
            <atom:updated>2026-08-26T21:56:19.845Z</atom:updated>
            <content:encoded><![CDATA[<p>The invoice takes about four minutes to produce and roughly twenty to send.</p><p>Not because anything is complicated. The rate was agreed weeks ago, the work is finished and delivered, and the client has already told me it was useful. The document says the same number we both said out loud in a call. There is genuinely nothing in it that either of us has not already agreed to.</p><p>And yet there I am, rereading a three-line email for the third time, deciding whether “please find attached” sounds unpleasantly formal, adding “whenever you get a chance,” taking it back out because it now sounds like I do not expect to be paid, and then sitting for a second with my hand on the mouse as though I am about to ask this person to lend me money for something personal.</p><p>The same afternoon, I will have sent that client a document telling them their onboarding process is a mess, with no hesitation whatsoever.</p><h3>The work was easier to send than the invoice</h3><p>This is the part I find genuinely funny. Freelancers spend all week sending things that are far more confrontational than an invoice.</p><p>You send the analysis that says the thing they have been doing for two years is not working, and the revision that quietly rejects most of their feedback. The email explaining that their proposed timeline is not possible takes about ninety seconds to write, with no agonizing over the wording at all.</p><p>Then you attach a PDF with a number on it and suddenly need three drafts to write “Invoice attached, let me know if you need anything else.”</p><p>The least controversial document of the entire week is the one that ends up sitting in Drafts.</p><h3>When an agreed price suddenly feels negotiable again</h3><p>Something odd happens the moment the number moves from a conversation into a document.</p><p>During the work, the price is settled. It is background information, decided so long ago that it barely registers while you are actually doing the thing. Then it appears on an invoice, in a box, next to your name, and your brain treats it as a fresh proposal that has arrived for review.</p><p>Was that too much for what it turned out to be? Did it look easier from their side? It took less time than I expected, so should the number somehow reflect that? None of these questions were anywhere near me while I was doing the work. They arrive strictly at the paperwork stage.</p><p>Which is strange, because the invoice does not create the price. It just makes it visible again, at a moment when someone else has to actually do something about it.</p><h3>Employees do not have to do this bit</h3><p>I do not remember ever feeling awkward about being paid a salary.</p><p>Payday happened. It was structural. Nobody expected me to write to my manager at the end of the month explaining that I had done the agreed work and wondering whether it might now be possible to receive the agreed money. Payroll existed precisely so that nobody had to have that conversation with a human being they see every day.</p><p>Freelancing collapses two roles into one person. You are the one who did the work, and you are also the one who turns up afterward holding a bill. Doing the work and asking to be paid for it somehow feel like two completely different jobs, and doing both to the same person, over email, with your own name on the document, makes something administrative feel oddly personal.</p><p>It is the same money. It has just lost the department that used to stand between you and the person paying it.</p><h3>“Just gently following up”</h3><p>Then there is the follow-up, which is somehow worse, despite the fact that by this point your position has only got stronger.</p><p>The invoice is now overdue. You are more entitled to bring it up than you were when you sent it. And this is precisely the moment when freelancers start writing sentences of extraordinary delicacy.</p><p>Just wanted to gently follow up on this. Not sure if this got buried. No rush at all, whenever you get a chance. Hope this finds you well, sorry for the second email.</p><p>What all of these mean is that a payment is late. What they sound like is someone apologizing for an intrusion. Overdue invoices seem to produce their own specific register of aggressive politeness, one that belongs to no other kind of correspondence.</p><p>The clients are usually not the problem here, which makes it stranger. Invoices genuinely do get buried. Accounts departments are slow, approvals sit with someone who is on vacation, and most late payments are nothing more sinister than an email that arrived on a bad day. Everyone freelancing knows this. It does not stop the small worry that a perfectly normal follow-up will somehow cost you the relationship.</p><p>It gets stranger with the clients you actually like. After a while they stop being a company and start being a person, one whose kids you have heard about, who you have had calls with that ran twenty minutes over because neither of you was talking about work anymore. Then you send that person a document that says, essentially, here is what you owe me.</p><p>Nothing about being friendly cancels out the part where they pay you. It can still feel like the invoice walked into the middle of something.</p><h3>It is still just part of the job</h3><p>Somewhere around here I am supposed to tell you to know your worth. I do know it. I said the number out loud several weeks ago, the client agreed to it, and nobody has questioned it since. The feeling is not carrying any new information, which is what makes it interesting rather than useful.</p><p>What does seem to help is having as little of it improvised as possible. Rates agreed before starting, payment terms that exist in writing, invoices sent on a predictable day rather than whenever it starts to feel acceptable. Plain language in the email. Follow-ups treated as administration rather than as a difficult conversation you have to work up to.</p><p>The less of the process you are inventing each time, the less room your brain has to turn a payment into a referendum on whether the client still likes you.</p><p>I doubt it ever becomes completely neutral. But it helps to remember that the invoice is not where the negotiation happens. The negotiation happened weeks ago, in a call, when both people said a number and agreed on it. Everything after that is paperwork.</p><p>Apparently finishing the work is the easy part. Attaching the invoice is where it gets emotional.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hZExPluXUIpsRwwbeJ9U6Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@daizyisumi?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Daizy Isumi</a> on <a href="https://unsplash.com/photos/white-printer-paper-beside-white-ceramic-mug-on-brown-wooden-table-fM35dYst3Rs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2171b3485a8e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/activated-thinker/the-weird-anxiety-of-sending-an-invoice-you-already-earned-2171b3485a8e">The Weird Anxiety of Sending an Invoice You Already Earned</a> was originally published in <a href="https://medium.com/activated-thinker">Activated Thinker</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Would You Train the AI That Might Eventually Do Your Job?]]></title>
            <link>https://medium.com/tech-and-me/would-you-train-the-ai-that-might-eventually-do-your-job-27869b95d424?source=rss-da406b55a6bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/27869b95d424</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Harper Reid]]></dc:creator>
            <pubDate>Wed, 19 Aug 2026 12:48:50 GMT</pubDate>
            <atom:updated>2026-08-19T12:48:50.939Z</atom:updated>
            <content:encoded><![CDATA[<h4>We have always taught other people how to do our jobs. We just called it onboarding.</h4><p>You showed the new hire how the process really worked. Explained the exceptions nobody bothered putting in the handbook. Told them which client needed a different approach and why step four could never actually be skipped.</p><p>Teaching software feels different.</p><p>Not because every AI correction trains a model. It doesn’t. But companies are increasingly trying to capture the knowledge behind how work gets done so AI agents can handle more of it.</p><p>And that creates a much stranger question: would you teach a system differently if you knew the eventual goal might be to need fewer people doing the work?</p><h3>When does helping the AI become training it?</h3><p>Fixing one bad answer is just using a tool. The shift happens quietly and usually in stages. Somebody starts keeping those corrections instead of letting them evaporate. Someone asks you for examples of good and bad outputs, so the standard now lives outside your head.</p><p>You get asked to write down how the work actually happens: the exceptions, the handovers, and the reason step four exists. That has always been good practice. It can also become useful raw material for automation later, which isn’t at all the same as saying anyone wrote it with that in mind.</p><p>Then somebody configures an agent to move work from one stage to the next and has to decide what it should escalate and what counts as finished. That’s where the comparison stops being a metaphor. I doubt there’s one obvious moment when using AI becomes teaching AI more of the job. Nobody announces it, and that grey area is the part I find interesting.</p><p>A recent piece of research made this feel a lot less theoretical. Researchers are building entire simulated workplaces now, fake companies with their own customers, orders, and policies, so AI agents can practice multi-step work rather than just answering questions.</p><p>One example I came across was Surge AI’s CoreCraft benchmark. It recreated a business with a couple of thousand records and a couple of dozen tools, and in its original evaluation, even leading models completed fewer than a third of the tasks properly. Describing a job and doing a job are clearly still very different things.</p><p>But somebody still had to describe that work in enough detail for the simulation to exist, and the people best placed to do that are the people who already understand the work.</p><h3>Why teaching software feels different</h3><p>We have always transferred knowledge at work. We write procedures, train new starters, and explain why one client needs handling gently. Nobody experiences that as loss. When I explain part of my work to a colleague, two people can now do it, and I have a reasonable idea of why they needed to know.</p><p>When the same knowledge goes into a system, you don’t necessarily have the same visibility into what happens next. I might be helping to remove the dullest hour of my week. I might be helping to build the case that the work needs fewer people. The two look identical while they’re happening.</p><p>The discomfort is probably less about being certain software will take over and more about not knowing what the end goal is. I’ve also read that Anthropic surveyed its own users earlier this year, and more than a third expected AI to handle most or nearly all of their work within twelve months. Not a representative sample, obviously. But it does say something about how people are feeling about where all of this might be heading.</p><h3>Would anyone behave differently if they knew?</h3><p>Imagine someone is asked to test an internal tool, label a few examples, and explain the exceptions, and imagine they also knew the aim was to find out whether that workflow could eventually run with fewer people in it. Would they refuse? Probably not. Some would decide, quite sensibly, that being the person who understands the system beats being the person surprised by it.</p><p>Which is what makes avoiding that conversation strange. If plenty of people would help anyway, leaving the aim unsaid starts to look less like a practical necessity and more like the path of least awkwardness.</p><p>At what point does adopting a tool become redesigning a workforce, and whose job is it to say so out loud?</p><p>I don’t have clean answers. I suspect people are more likely to resent finding out later than they are to object to being told upfront. But that’s easy to say from outside the room where the budget gets decided.</p><p>None of which makes the underlying project a bad one. The same survey asked people what they hoped for, and just over half wanted AI to take the tedious parts off their hands so they’d have more free time. Removing repetitive admin is a genuine improvement, and handling exceptions well tends to make experienced people more valuable rather than less, because the exceptions are the part the system keeps failing at.</p><p>But “this frees you up for higher-value work” is a claim about job design, and job design is something an organization either does deliberately or doesn’t do at all. If nobody has decided what those hours are for, they’ll be filled by whatever turns up.</p><p>Most people, I suspect, would gladly teach a system to absorb the dullest parts of their job. Plenty are already helping systems take on pieces of that work without thinking much about what to call it. The harder question is whether they’d feel the same way if nobody could tell them where it stops.</p><p>When I teach a colleague something, I usually know why they need to learn it. But if you knew the system you were helping improve might eventually need less of you, would you still teach it the same way?</p><figure><img alt="View of a computer screen and keyboard" src="https://cdn-images-1.medium.com/max/1024/1*VkPxi3vJHUeG7WOS-K8xNQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@almoya?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Aerps.com</a> on <a href="https://unsplash.com/photos/a-laptop-displays-what-can-i-help-with-5e4Zlblkvks?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27869b95d424" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tech-and-me/would-you-train-the-ai-that-might-eventually-do-your-job-27869b95d424">Would You Train the AI That Might Eventually Do Your Job?</a> was originally published in <a href="https://medium.com/tech-and-me">Tech and Me, Loving It or Hating It</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Whose Definition of Success Are We Chasing?]]></title>
            <link>https://medium.com/illumination/whose-definition-of-success-are-we-chasing-b5610732ee32?source=rss-da406b55a6bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5610732ee32</guid>
            <category><![CDATA[success]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <dc:creator><![CDATA[Harper Reid]]></dc:creator>
            <pubDate>Tue, 11 Aug 2026 09:13:29 GMT</pubDate>
            <atom:updated>2026-08-11T09:13:29.055Z</atom:updated>
            <content:encoded><![CDATA[<p>People tell me what they want next long before they tell me whether they like what they have now.</p><p>It comes up in almost every conversation I have about someone’s career. The next step, the next level, the move into management, the title that would finally reflect the work. All of it arrives fluently and without much prompting, and it is usually described in the future tense. Whether the present tense is any good is a question that has to be asked separately, and often more than once.</p><p>That gap interests me more than the ambitions themselves, because a surprising number of the things people describe wanting turn out to be things they had learned to want rather than things they had consciously chosen.</p><h3>The Promotion Everyone Was Supposed to Want</h3><p>There was someone I worked with who had wanted a management role for the better part of two years. He talked about it in reviews, in casual conversation, in the way people do when a thing has become part of how they describe themselves.</p><p>When it finally came through, everyone was pleased. There was a lunch. His LinkedIn post did unusually well.</p><p>I spoke to him again about eight months later, mostly about something unrelated, and somewhere in the middle of it he mentioned that he missed the actual work. His days had become meetings, approvals, planning, and absorbing other people’s problems, which is an accurate description of management and not a complaint about it. He was reasonably good at it. He simply preferred the job he had before, where he had been very good at something specific and could see what he had made at the end of a week.</p><p>He was not unhappy. He said it lightly, the way you mention something you have decided not to do anything about.</p><p>What I have wondered since is whether he wanted to manage people or whether he wanted what managing people signified. Progress, recognition, some external confirmation that things were going well. None of that is shameful to want, and none of it is the same as wanting the job.</p><h3>The People Who Have to Explain Themselves</h3><p>The opposite case is more common than people assume, and it comes with an odd social penalty.</p><p>I have met plenty of people who are genuinely excellent at what they do and have no interest whatsoever in managing anybody. They like the work, and they like doing it well, and they have arranged their lives so that it occupies a particular amount of space and no more, usually finishing at a sensible hour.</p><p>What is strange is how often they end up defending that. Every few months somebody asks what is next, or whether they have thought about leading a team, or where they see themselves in five years, and the question arrives with an assumption baked into it. A perfectly deliberate choice starts to sound like inertia, purely because it does not move in the expected direction.</p><p>Nobody asks the person chasing a promotion whether they are sure. That request is treated as self-explanatory. But someone who says they are happy where they are will usually be asked to account for it, sometimes kindly, sometimes with a slight note of concern.</p><p>I have caught myself doing this. I asked someone what her plan was, and she said her plan was to keep doing this job well and go home at half past five. For a second, I waited for the rest of the sentence. There was no rest of the sentence. That was the plan.</p><h3>The Strange Arithmetic of a Number That Did Not Change</h3><p>Money is where this gets more complicated, and I have no interest in being glib about it. More money genuinely matters. It buys security, options, a smaller amount of dread about the boiler, and the ability to make decisions that are not purely financial.</p><p>But something happens when a salary meets a comparison.</p><p>Somebody can be perfectly content with what they earn on a Tuesday, then discover on Wednesday what a former colleague is being paid, and by Thursday the number has become insulting. Nothing about their circumstances has moved. The rent is the same, the work is the same, and the money buys the same things it bought two days earlier. The only thing that changed is that they now know something they did not know before.</p><p>Salary transparency is, on balance, a good thing, and I would not argue for going back. Still, it is worth noticing how often dissatisfaction arrives through the side door of comparison rather than through anything to do with the actual conditions of someone’s life. Job listings do this. LinkedIn does it constantly. Even a friend’s good news can do it, which is an uncomfortable thing to admit about oneself.</p><h3>Career Success Is Unusually Easy to Measure From the Outside</h3><p>Part of what drives all of this is simply that some things are visible and some are not.</p><p>Anybody can see a job title. A salary band, a company logo, a promotion announcement, the number of people reporting to somebody, an award, a jump from a small firm to a famous one. These are all legible at a glance, and, more importantly, they are comparable. You can line two careers up next to each other and convince yourself you have an answer.</p><p>What nobody can see is whether a person likes Tuesday mornings or whether Sunday evening has a weight to it. There is no way of knowing from the outside whether they still have energy at seven o’clock for the people they live with, or whether the job leaves room for friendships, travel, and the occasional evening spent doing nothing in particular. Whether they actually enjoy the thing they became successful at, or got good at it and then found it hard to stop, is invisible to everyone but them.</p><p>None of that shows up anywhere. It cannot be posted, and it cannot be ranked. So there is a quiet pull towards the measurable version of a good career, because the measurable version is the one other people can confirm.</p><blockquote>If somebody could see your Tuesday mornings but never your job title, what would they conclude about how your career is going?</blockquote><h3>Everything We Say About Careers Points in One Direction</h3><p>The language gives it away once you start listening for it.</p><p>Moving up. Getting ahead. The next level. Progression. Climbing. Nearly every phrase assumes one direction of travel, and staying still is treated as a neutral outcome at best.</p><p>Now try saying the alternatives out loud. I earn enough. I do not want to manage anybody. I found work I like and would happily keep doing it. Each of those can be a considered decision made by a competent adult, and each of them still tends to come out sounding faintly apologetic.</p><h3>What Would Be Left If Nobody Could See It</h3><p>I do not have a tidy position on any of this. Someone who wants to run a department because they would genuinely enjoy running a department should go and do it, and several of the most contented people I have worked with are extremely senior.</p><p>What stays with me is that careers are one of the few areas of life where we rarely stop to check whether the goal was ours to begin with. The sequence gets handed over early and repeated often enough that questioning it seriously starts to feel eccentric, and I am not certain I have entirely done it myself.</p><p>The question I keep turning over is whether the wanting would survive being invisible.</p><p>If nobody could see the title, the salary, the company name, or the announcement, and the only thing left was the actual experience of the days, how much of the current plan would still be the plan?</p><p>Some people, I suspect, would answer that immediately and cheerfully and would carry on exactly as they are. That seems like a good sign. Others might find the answer takes longer to arrive than they expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xvwwmogCBjjWMR7hXl2uGw.jpeg" /><figcaption><a href="https://www.magnific.com/free-photo/chessman-is-changed-shadow-crown_6172050.htm#fromView=search&amp;page=1&amp;position=20&amp;uuid=cbc9f9f2-ab5c-4e0c-963b-07c670d35116&amp;track=ais_hybrid&amp;query=success">Image by jcomp on Magnific</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5610732ee32" width="1" height="1" alt=""><hr><p><a href="https://medium.com/illumination/whose-definition-of-success-are-we-chasing-b5610732ee32">Whose Definition of Success Are We Chasing?</a> was originally published in <a href="https://medium.com/illumination">ILLUMINATION</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does Micromanagement Create the Employees It Complains About?]]></title>
            <link>https://medium.com/activated-thinker/does-micromanagement-create-the-employees-it-complains-about-a08424a4e089?source=rss-da406b55a6bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/a08424a4e089</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[this-happened-to-me]]></category>
            <category><![CDATA[mindset]]></category>
            <dc:creator><![CDATA[Harper Reid]]></dc:creator>
            <pubDate>Mon, 10 Aug 2026 05:56:55 GMT</pubDate>
            <atom:updated>2026-08-10T05:56:55.302Z</atom:updated>
            <content:encoded><![CDATA[<p>I have lost count of the number of calls that have opened with some version of the same sentence. “My team doesn’t take enough ownership.” It usually arrives about ten minutes in, after the pleasantries, and it is nearly always said by someone who sounds exhausted.</p><p>Then comes the rest of it. They ask me about everything. Nobody makes a decision unless I am in the room. I cannot go on holiday without the whole thing stalling.</p><p>For a long time I took that at face value because it sounds like a hiring problem, and hiring problems are the ones I get called about. Sometimes it genuinely is. But after enough of these conversations, it became hard to ignore how often the person describing the problem had helped create the conditions for it.</p><h3>The Employee Who Learned to Ask Permission</h3><p>The clearest case I have seen involved a woman who had been in the job about eight months when I met her.</p><p>I had heard about her before I met her, and not in a flattering way. Her manager described her as someone who needed a lot of hand-holding and mentioned twice that she checked in more than anyone else on the team. I went in expecting somebody nervous and out of her depth.</p><p>She was neither. Talking to her, she was quick, opinionated, and had a much better read on what was broken in that department than her manager did. She told me about her first few weeks, when she had been suggesting improvements and handling client questions on her own because nobody had told her not to.</p><p>Her manager was attentive and enormously involved. He reviewed emails before they went out, asked to be copied into things, and liked a couple of updates through the day. None of it was hostile. Most of it looked, honestly, like support, and I think he would have been genuinely wounded to hear it described any other way.</p><p>What she remembered most were the small reversals. A decision she had already made and communicated would come back slightly altered, which meant going to the client and quietly unmaking it. Nothing dramatic ever happened. She was never once told to stop thinking for herself.</p><p>By the time I arrived, her questions had become: Is this okay? Should I send this? Do you want to look before I share it?</p><p>And her manager, sincerely and with no idea what he was telling me, said she needed a lot of reassurance.</p><h3>Why Micromanaged Employees Start Asking Permission</h3><p>Her behavior made perfect sense once you looked at what had been reinforced for eight months. Making a decision on her own could mean explaining it, revising it, or undoing it later. Asking first avoided all three.</p><p>Over time, questions go up, experiments go down, and people start waiting for approval on things they once handled without thinking. To the manager, that can look like a confidence problem. To the employee, it is arithmetic.</p><h3>Why Good Managers Become Micromanagers</h3><p>I want to be fair here, because almost nobody I have met is doing this on purpose.</p><p>There was one manager who, when I asked why he reviewed everything, told me about an error a previous team member had made that had gone to a client and cost him a fairly humiliating conversation with his own boss. He had been checking everything ever since. He said it the way you would describe a sensible safety measure, which from where he was standing is exactly what it was.</p><p>Pressure from above, one costly mistake, inexperience with delegation, or simply not being able to see what the team is doing can all lead to the same behavior. That last one comes up more than people expect. If asking is your only way of knowing where something stands, you will ask repeatedly.</p><p>To the manager, checking feels responsible. To the employee, being checked feels like evidence that their judgment is not trusted on its own. Both experiences are happening inside the same conversation, which is why nobody catches it before the pattern sets.</p><h3>Micromanagement Kills Initiative Before It Hurts Performance</h3><p>This is the part that lets these situations run for years unnoticed.</p><p>Micromanagement rarely produces bad work. Deadlines are met. The work may even look better than fine because two people have checked it.</p><p>What goes first is quieter. People stop suggesting the faster way, stop mentioning the process that everyone knows is broken, and stop fixing the small thing themselves because fixing it means having a decision reviewed. Someone in that state can look completely productive right up until the moment their manager takes a week off, which is usually when it surfaces.</p><h3>How Employees Rebuild Initiative When Trust Returns</h3><p>The more encouraging thing I have seen is that this reverses.</p><p>One manager I worked with changed a single habit. Instead of “do this, then send it to me, then wait,” he started saying, “Here is what we need to end up with; use your judgment and come to me if you hit something genuinely unclear.”</p><p>For the first few weeks nothing changed at all, and he found that quite discouraging. People kept sending him things to check, even though he had told them explicitly that approval was no longer needed. He mentioned to me, slightly baffled, that he had just replied, “You don’t need to ask me,” to the same person three times in one week.</p><p>Then it started thinning out. Within a couple of months his team was making decisions again, including several he would have made differently, which he mostly let stand. He told me that was the hardest part by a distance, and I believe him. Trust is not free at the moment you extend it.</p><h3>When Lack of Visibility Turns Into Micromanagement</h3><p>One thing that has come up repeatedly in these conversations is that sometimes the checking starts because the manager genuinely cannot see what is happening.</p><p>A shared board, clear ownership, or a simple way to flag blockers can remove a surprising amount of that uncertainty. The manager can check the system instead of repeatedly checking the person. Visibility can replace surveillance.</p><h3>When Close Oversight Is Actually Appropriate</h3><p>Not every request for an update is micromanagement, and I would be useless to any manager if I pretended otherwise.</p><p>New hires need review. High-risk decisions deserve approval. Someone who has recently made a serious mistake probably does warrant closer supervision for a while.</p><p>The question is not whether oversight exists. It is whether it shrinks. What worries me is when someone has been doing a job well for a year and still needs permission for the same decisions they needed permission for in week one.</p><h3>The Question Managers Should Ask Before Blaming the Team</h3><p>So when a manager tells me the team asks too many questions, I have stopped treating that as a description of the team. I ask something else instead.</p><blockquote>What happens when they don’t?</blockquote><p>When somebody makes a reasonable call without approval, does it get backed? And when it was done differently from how you would have done it, does it still get to stand?</p><p>People work out very quickly which behaviors create friction and which ones make the day easier. If independent decisions are routinely second-guessed, asking permission becomes the sensible choice.</p><p>That is how micromanagement can create the dependency managers later complain about. The team may not have lost its ability to take ownership. It may simply have learned that taking ownership comes with consequences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PMlG1TslK43Zgow_OxendA.jpeg" /><figcaption><a href="https://www.magnific.com/free-photo/businessman-writes-with-white-chalk-that-is-controlled-by-his-hand-draw-concept_6170408.htm#fromView=search&amp;page=1&amp;position=1&amp;uuid=0f7bfc10-fdae-4278-b88c-b457ea9dd5e8&amp;track=ais_hybrid&amp;query=micromanagement">Image by jcomp on Magnific</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a08424a4e089" width="1" height="1" alt=""><hr><p><a href="https://medium.com/activated-thinker/does-micromanagement-create-the-employees-it-complains-about-a08424a4e089">Does Micromanagement Create the Employees It Complains About?</a> was originally published in <a href="https://medium.com/activated-thinker">Activated Thinker</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Tried the Pomodoro Technique for a Week]]></title>
            <link>https://medium.com/@harperr89/i-tried-the-pomodoro-technique-for-a-week-03d5685d8275?source=rss-da406b55a6bb------2</link>
            <guid isPermaLink="false">https://medium.com/p/03d5685d8275</guid>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[pomodoro-technique]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Harper Reid]]></dc:creator>
            <pubDate>Fri, 07 Aug 2026 06:44:23 GMT</pubDate>
            <atom:updated>2026-08-07T06:44:23.957Z</atom:updated>
            <content:encoded><![CDATA[<p>I am naturally suspicious of productivity trends, mostly because I have been beaten by so many of them.</p><p>When I started writing on Medium a few months ago, I had no idea I would somehow become the person testing productivity methods and reporting back on which ones survive a real workweek. Yet here we are, apparently saving each other the trouble of trying every system personally.</p><p>Over the years I have downloaded a genuinely embarrassing number of apps, read the articles, built the systems, and quietly abandoned nearly all of it within a fortnight. So when people kept recommending the Pomodoro Technique, my reaction was always the same polite skepticism. You work for twenty-five minutes, stop for five, and then repeat. The method has survived for decades, and that is essentially the entire idea.</p><p>My bigger objection was more personal. As a freelancer, I spend a good part of every day trying to get properly focused, and when it finally happens I do not want to be interrupted, least of all by myself. Deliberately stopping mid-thought sounded like sabotage with a timer attached.</p><p>Besides, I was already perfectly capable of spending an hour answering small emails while avoiding the one task that actually mattered. I was not convinced a kitchen timer was going to fix that.</p><p>Still, dismissing something for years without trying it is not a position, it is a habit. So I gave it one honest week.</p><h3>Day one: what the first 25-minute session felt like</h3><p>I started with a client’s employee handbook, which needed a fairly serious revision to two sections and had been sitting on my list for longer than I want to admit.</p><p>The first session was strange. I watched the timer far too much, in the way you watch a kettle, and became aware of every single minute passing. Around the twelve-minute mark, I forgot it existed, which I only noticed afterwards.</p><p>Then it rang in the middle of a paragraph. My instinct was to wave it off and keep going, because the sentence was right there and half-finished. I made myself stop anyway, mostly to see what would happen, and walked away to get a glass of water, convinced I would return to find the thread completely gone.</p><p>The thread was not gone. It took about ten seconds to pick the sentence back up, and I sat there mildly annoyed that my main argument against the technique had fallen apart on the first morning.</p><h3>The first benefit wasn’t focus. It was starting</h3><p>What surprised me over the following days was how much less resistance I felt before beginning a task.</p><p>A handbook revision, interview scorecards for three roles, or a pile of untouched candidate notes can all feel larger than they really are when you picture the finished job at once. Twenty-five minutes felt much easier to agree to.</p><p>I do not have to finish the handbook. I only have to work on it until a timer goes off, which is a promise I can actually keep to myself. The task stops being a mountain and becomes a slot in the morning.</p><p>By Tuesday I had used that trick on two things I had been avoiding for over a week, which is a better hit rate than most of my previous systems managed in their entire lifespans.</p><h3>The task I had avoided all week</h3><p>The clearest example came on Wednesday, and it involved the job I had been postponing most enthusiastically.</p><p>I had run a remote workshop the previous week and come away with a genuinely chaotic set of notes. Half-sentences, three different threads about the same issue, several things typed while somebody was still talking. Turning that into a usable summary for the client was going to take hours, and every time I opened the file I closed it again with the sincere intention of doing it later.</p><p>That morning I told myself I would give it one session. Twenty-five minutes, no expectation of finishing, just enough to stop avoiding it.</p><p>When the timer went, the work was nowhere near done. But the shape of it had appeared. The three threads were separated, the nonsense was deleted, and I could see it was roughly ninety minutes of work rather than the vague, endless afternoon I had been imagining. One session became two, then three, with breaks in between. By then I was simply doing the work rather than negotiating with myself about when to begin it.</p><p>The timer did not make the job easier. It made the job easier to begin, which in my case is nearly always the actual problem.</p><h3>Where Pomodoro didn’t fit: meetings and calls</h3><p>I should be clear that this does not work for everything, and the week made that obvious quickly.</p><p>It was useless during meetings. I had four client calls that week, including one where a manager needed to talk through a difficult situation with an employee, and there is no version of me that interrupts that conversation because a timer has gone off in another window. Interviews, workshops, and anything collaborative sat outside the framework completely.</p><p>What I settled on was building sessions around the meetings rather than through them. I used one session to prepare, left the timer off during the meeting, and used another immediately afterwards to organize my notes while the conversation was still fresh. That last habit was probably the single most useful thing I took from the week, and it is barely even Pomodoro.</p><p>Thursday afternoon had three calls in it, and I abandoned the technique entirely. That felt like the right decision rather than a failure.</p><h3>The breaks mattered more than I expected</h3><p>At the start I treated the five minutes as an interruption to be tolerated. By Friday they had become the part I looked forward to.</p><p>The rule I gave myself was that a break could not involve another screen, since swapping a document for social media is not a break, it is just a different tab. So I got water, stretched, opened a window, made coffee I did not strictly need, and walked around the flat for no reason.</p><p>My cat interpreted all of this as a scheduling improvement on my part. She appeared beside me within about ninety seconds of every break, having worked out the pattern faster than I did, and several of those five-minute pauses were spent with her firmly installed on my lap.</p><p>Coming back after genuinely stepping away from the work feels different from simply clicking between tabs. I had spent years treating tiredness in the middle of the afternoon as a sign to push harder, and it turns out five minutes away from the desk does more than another forty minutes of grinding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ffgt7hYHqdtaOkrmX9l0LA.jpeg" /><figcaption>My Pomodoro accountability partner is mostly here for the cuddles.</figcaption></figure><h3>How I adapted the rules to real freelance work</h3><p>Nothing about my week looked like the technique as it is usually described.</p><p>I forgot to start the timer several times and only noticed when I wondered why it had not gone off. I worked past it more than once because I was two lines from finishing a thought, and stopping would have been silly. My five-minute breaks were routinely seven. On Tuesday, I let one policy-writing session run for about forty-five minutes because it was going well and interrupting it seemed genuinely counterproductive.</p><p>By the end of the week, I had stopped treating the numbers as strict rules. Twenty-five minutes became a default rather than a requirement, which is probably why I still use the method.</p><h3>Did the Pomodoro Technique actually work?</h3><p>On Friday afternoon, my inbox was not empty. Several things on my list were exactly where they had been on Monday, and I had not transformed into anybody impressive.</p><p>The difference was smaller and more useful than that. I spent far less of the week drifting, which is my real problem and always has been. Before the experiment, an hour could disappear into email, a Slack message, half a document, an invoice, and then back to email. At the end of it, I often could not say what I had actually finished. That week I started one thing, worked on that one thing, stopped before I was worn out, and came back with a clear head.</p><p>The technique did not make me faster. It made my attention less scattered, which is a different and better outcome.</p><p>I expected the timer to run my day. Instead, it gave me permission to stop pretending I could do several things at once. The productivity problem I had been trying to solve for years was not a lack of hours. It was how rarely I gave one task my full attention before allowing something else to interrupt it.</p><p>Twenty-five minutes is not a magic number. It is simply manageable enough to begin and long enough to make meaningful progress. The timer did not change the amount of work waiting for me. It changed how much of my attention I gave to one thing at a time, and that turned out to matter more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QgBS686URUsZRZi0uCRajQ.jpeg" /><figcaption><a href="https://www.magnific.com/free-photo/hands-holding-wall-clock-still-life_47696608.htm#fromView=search&amp;page=2&amp;position=1&amp;uuid=3bdfcc55-f008-410d-9cd5-5cf53efda346&amp;track=ais_hybrid&amp;query=pomodoro+timer">Image by magnific</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=03d5685d8275" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>