<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gaby Charalampidi · Notes</title>
    <link>https://gabycharalampidi.com/notes</link>
    <atom:link href="https://gabycharalampidi.com/rss.xml" rel="self" type="application/rss+xml" />
    <description>Notes on leadership, operations, and AI from Gaby Charalampidi.</description>
    <language>en-us</language>
    <item>
      <title>The stories we make up when we don't have the facts</title>
      <link>https://gabycharalampidi.com/notes/the-stories-we-make-up</link>
      <guid isPermaLink="true">https://gabycharalampidi.com/notes/the-stories-we-make-up</guid>
      <pubDate>Sun, 26 Jul 2026 00:00:00 GMT</pubDate>
      <category>Leadership</category>
      <description>When the facts are missing your brain writes a story anyway. The only question is whether you check it before you act on it.</description>
      <content:encoded><![CDATA[<p><img src="https://gabycharalampidi.com/notes/the-stories-we-make-up-slide1%20(1).png" alt="" /></p><p>You flag a risk to your boss and hear nothing for two days. By the second morning you have a full idea of what happened. She thinks you are being dramatic, she is losing confidence in you and does not respect your opinion anymore. Maybe this is how getting managed out starts. Then she replies, apologetic, buried in a deadline, grateful you caught it. The whole story was fiction. You worked inside it for two days anyway, second-guessing everything you sent her.</p>
<p>That is just what the mind does with a gap. It manufactures an explanation and hands it to you with the confidence of a fact. The neurologist Robert Burton spent a whole book on the point: the feeling of knowing is a sensation the brain produces on its own, not a verdict earned by evidence [1]. Everyone fills gaps this way, and at work it is dangerous because the story almost always casts you as the victim or the failure.</p>
<h2 id="why-a-bad-story-beats-no-story">Why a bad story beats no story</h2>
<p>Uncertainty is the part we cannot sit with. In one study, people facing a coin-flip chance of an electric shock were more stressed than people who knew for certain the shock was coming [2]. A finished story, even an ugly one, ends that suspense, which is why we grab the first one available and hold on.</p>
<p>Brené Brown’s name for that first story is blunt: the sh*tty first draft, a term she borrowed from the writer Anne Lamott [3]. You cannot suppress it, it shows up on its own. What you can do is notice you are holding one, because the moment you call it a draft, you stop treating it like reality.</p>
<h2 id="putting-it-into-practice">Putting it into practice</h2>
<p>This is for the gaps that are really about another person, the moments where you have no idea what someone meant and your mind hands you an answer anyway. A silence, a short reply, a meeting you were not invited to, and a story already forming about what it means. The first story is going to arrive whether you invite it or not. Watch the shape of that story. When it casts you as the victim or the failure, that is your signal you are holding a draft, not the truth.</p>
<p>So name it to them. When you’re talking to the person involved, you just say it: “the story I’m making up is that the silence means you are unhappy with me.” It labels your interpretation as a guess instead of an accusation, and it hands the other person the easiest possible opening to correct you. If that phrasing feels too soft for your team, try the plain version: “here is what I’m assuming, correct me if I am wrong.” And sometimes the draft turns out to be right. Ask anyway. Then you’re working with something real instead of a suspicion you just keep turning over.</p>
<hr>
<p><strong>Sources</strong></p>
<ol>
<li>Robert Burton, <em>On Being Certain</em> — <a href="https://us.macmillan.com/books/9780312541521/onbeingcertain/">macmillan.com</a></li>
<li>de Berker et al., uncertainty and acute stress — <a href="https://www.nature.com/articles/ncomms10996">nature.com</a></li>
<li>Brené Brown, the story rumble and the “shitty first draft” — <a href="https://brenebrown.com/resources/the-story-rumble-process-a-guide-for-groups-and-teams/">brenebrown.com</a></li>
</ol>]]></content:encoded>
    </item>
    <item>
      <title>Schedule your priorities</title>
      <link>https://gabycharalampidi.com/notes/schedule-your-priorities</link>
      <guid isPermaLink="true">https://gabycharalampidi.com/notes/schedule-your-priorities</guid>
      <pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
      <category>Leadership</category>
      <description>Covey's four quadrants sort work by urgent and important. The work that builds anything sits in the one quadrant that never demands your attention.</description>
      <content:encoded><![CDATA[<p><img src="https://gabycharalampidi.com/notes/schedule-your-priorities-slide1.png" alt="" /></p><p>Your calendar says the strategy document has to get written this morning. Then a client email lands, a teammate is unavailable, a meeting runs over, and by six you have done twenty different things and written nothing. The day felt productive, but not in the way you were planning to.</p>
<p>Stephen Covey built Habit 3 of The 7 Habits of Highly Effective People (put first things first) around the distinction that explains a day like that: urgent is not the same as important [1]. Urgent things press on you and demand attention now, the ringing phone, the deadline, someone else’s crisis. They are loud, and reacting to them feels good because it makes you feel needed. Important things move your mission and your long-term goals, and they are usually quiet. Now sort your work along those two axes and you get four quadrants:</p>
<ol>
<li>crises (urgent and important)</li>
<li>quality work (important but not urgent)</li>
<li>distractions (urgent but not important)</li>
<li>waste (neither).</li>
</ol>
<p>Where your time goes across those four is what decides your effectiveness. And the whole framework hinges on the second quadrant.</p>
<h2 id="the-quadrant-that-never-demands-attention">The quadrant that never demands attention</h2>
<p>Quadrant II is the important work that is never due today: planning, prevention, the one-on-one you keep rescheduling, the skill you have been meaning to learn, your own health. Covey observed that highly effective people spend roughly 60 to 80 percent of their time there. Most people however spend about 90 percent of their time in crisis mode, with the remainder leaking into escape, scrolling and busywork (Q4)[2].</p>
<p>The reason why this happens is simple: Quadrant II always looks skippable today. Nothing breaks if you defer the planning session or the one-on-one, but tomorrow brings fresh urgency, so it keeps getting pushed, and the neglect quietly feeds the crises. Skip prevention and you get more fires to fight down the line. Neglect the relationship work and you get more conflict to referee in the future. Interestingly enough, working harder inside Quadrant I will not make it smaller, no matter how productive it feels. What actually shrinks this week’s crises is the time you put into Quadrant II last month.</p>
<p>Even with the grid in front of you, it is easy to sort things wrong. The most common mistake is labeling a task urgent and important when it is really just urgent, because a notification arrived or because someone else is panicking. Their Quadrant I is allowed to be your Quadrant III. Catching that distinction is most of the skill that many struggle to understand.</p>
<h2 id="big-rocks-first">Big rocks first</h2>
<p>On its own, the matrix only gives you some guidance without the necessary steps to apply towards your work. Covey’s fix is a weekly planning routine with four steps.</p>
<ol>
<li>Name your key roles, leader, teammate, parent, plus one for your own renewal.</li>
<li>Pick one or two important-but-not-urgent goals for each role for the coming week.</li>
<li>Block those into the calendar before anything else.</li>
<li>Then let the smaller, urgent tasks settle into the space that is left.</li>
</ol>
<p>The order is the point, and Covey gave it an image: the big rocks. Fill a jar with sand and gravel first and the big rocks never fit. Put the rocks in first and the small stuff settles around them. Schedule your priorities, he wrote, instead of prioritizing your schedule [1].</p>
<hr>
<p><strong>Sources</strong></p>
<ol>
<li>FranklinCovey, Habit 3: Put First Things First — <a href="https://www.franklincovey.com/the-7-habits/habit-3/">franklincovey.com</a></li>
<li>Toggl, The Covey Time Management Matrix: A Complete Guide — <a href="https://toggl.com/blog/time-management-matrix">toggl.com</a></li>
</ol>]]></content:encoded>
    </item>
    <item>
      <title>Curiosity: ask before you defend</title>
      <link>https://gabycharalampidi.com/notes/curiosity-ask-before-you-defend</link>
      <guid isPermaLink="true">https://gabycharalampidi.com/notes/curiosity-ask-before-you-defend</guid>
      <pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate>
      <category>Leadership</category>
      <description>Defending your position ends the conversation where it started. Asking a real question first is how you find out what you were missing.</description>
      <content:encoded><![CDATA[<p><img src="https://gabycharalampidi.com/notes/curiosity-ask-before-you-defend-slide1%20(1).png" alt="" /></p><p>Someone pushes back on the process you rolled out, and the reflex arrives before the thought does. Defend it. Explain the reasoning again, point to the meeting where everyone agreed, hold the line. Defending feels like competence in the moment, and it ends the conversation exactly where it started, with you knowing nothing new.</p>
<p>There is a name for what that reflex protects. When evidence threatens a position you own, you do not weigh it neutrally, you recruit arguments against it, a pattern the psychologist Ziva Kunda called motivated reasoning. The alternative is to ask a real question first, and that is harder than it sounds, because a genuine question means admitting a gap in what you know.</p>
<h2 id="the-gap-is-supposed-to-be-uncomfortable">The gap is supposed to be uncomfortable</h2>
<p>George Loewenstein’s information-gap theory describes curiosity as a feeling of deprivation [1]. It starts the moment you notice the distance between what you know and what you need to know, and the noticing itself is unpleasant. That discomfort explains the pull toward defending. A confident answer closes the gap instantly, it just closes it with whatever you already believed.</p>
<p>Brené Brown makes the same point for managers, that choosing to be curious means choosing to be exposed [2], which is why leaders skip it. And the fear that questions make you look weak runs backward. Studies of workplace conversation find that people who ask more questions, especially follow-ups, are rated more likable and more competent, not less [3].</p>
<h2 id="what-asking-first-buys-you">What asking first buys you</h2>
<p>A team member says the new process slows them down. Defend the rollout and you keep the procedure but lose the adoption. Ask “walk me through where it slows you down” and you find the one redundant step that was souring the whole thing. A number in this week’s report jumps and contradicts the story you told last month. Push back on it in the room and your team learns that only convenient numbers are safe to bring you. Ask “help me understand how this is calculated” and you find someone changed the definition, and your team learns you would rather have the real number than a flattering one.</p>
<p>The openers are cheap. “Help me understand.” “Tell me more.” “Walk me through it.” “What am I missing?” Each one trades a little status now for information you can act on, which is the better end of the deal every time.</p>
<p>Curiosity also has a clock. It comes before the decision, not instead of it. Ask your questions, then decide, and own the decision. What you give up is the comfort of being right immediately. What you get is being right where it counts, out where the work actually happens.</p>
<hr>
<p><strong>Sources</strong></p>
<ol>
<li>Loewenstein, information-gap theory of curiosity — <a href="https://www.cmu.edu/dietrich/sds/docs/golman/golman_loewenstein_curiosity.pdf">cmu.edu</a></li>
<li>Brené Brown on armored vs. daring leadership — <a href="https://brenebrown.com/podcast/brene-on-armored-versus-daring-leadership-part-1-of-2/">brenebrown.com</a></li>
<li>Brooks &#x26; John, “The Surprising Power of Questions” — <a href="https://hbr.org/2018/05/the-surprising-power-of-questions">hbr.org</a></li>
<li>Gino, “The Business Case for Curiosity” — <a href="https://hbr.org/2018/09/the-business-case-for-curiosity">hbr.org</a></li>
</ol>]]></content:encoded>
    </item>
    <item>
      <title>Vulnerability makes you a better leader</title>
      <link>https://gabycharalampidi.com/notes/vulnerability-makes-you-a-better-leader</link>
      <guid isPermaLink="true">https://gabycharalampidi.com/notes/vulnerability-makes-you-a-better-leader</guid>
      <pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate>
      <category>Leadership</category>
      <description>The hard things that make you a better leader share one feature: you cannot control how they go. That willingness to be exposed is the skill.</description>
      <content:encoded><![CDATA[<p><img src="https://gabycharalampidi.com/notes/vulnerability-makes-you-a-better-leader-slide1.png" alt="" /></p><p>The hard things that make you a better leader all share one feature: you cannot control how they go. Give someone honest feedback and it might strain the relationship. Admit you were wrong and it might cost you standing. Back the unpopular call and it might fail out loud. That exposure to an uncertain, risky outcome is the whole reason those acts take courage, and it is what makes you better at the job.</p>
<p>Brené Brown has a name for that exposure: vulnerability. In <em>Dare to Lead</em>, she argues it is the raw material every brave act is built from. Take the risk and uncertainty out of a decision, and it stops asking anything of you.</p>
<h2 id="what-that-willingness-buys-you">What that willingness buys you</h2>
<p>The willingness to be exposed is what makes each of those acts work. Sit in the discomfort and you have the hard conversation, so the problem gets solved while it is still small. Say “I don’t know, help me think about this,” and the bad news reaches you early instead of landing as a surprise. Stay curious instead of defending your position, and you keep learning after everyone else has stopped.</p>
<p>When you go first, people follow you into it. When you protect yourself, they protect themselves too. It starts with whoever is in charge.</p>
<h2 id="courage-and-vulnerability-are-the-same-thing">Courage and vulnerability are the same thing</h2>
<p>The usual objection is that being this exposed is weakness. Brown’s research points the other way. She asked people to name the bravest things they had done, and separately the most vulnerable, and the two lists were the same. Courage and vulnerability turn out to be one experience, felt from the inside. So when you say you want to be a more courageous leader, more honest, more accountable, what you are choosing is to be exposed more often, on purpose.</p>
<p>I felt this a couple of months ago. I was in a meeting talking through a process I had not figured out yet, and I was uncomfortable the whole time. I know why. I tie being smart to walking in with the steps already worked out and handed to my team, so sitting there without them felt like proof I was failing at the job. The honest move was to say I had not cracked it yet and work it out in the open. Everything in me wanted to perform certainty instead.</p>
<p>That pull to look like you have it handled shows up right where the work needs you most. When you feel it, you have probably found the thing worth doing, the conversation you keep rescheduling or the meeting where you will not have every step. The discomfort is the sign it matters. Walk in anyway.</p>]]></content:encoded>
    </item>
    <item>
      <title>Your AI keeps three kinds of memory</title>
      <link>https://gabycharalampidi.com/notes/your-ai-keeps-three-kinds-of-memory</link>
      <guid isPermaLink="true">https://gabycharalampidi.com/notes/your-ai-keeps-three-kinds-of-memory</guid>
      <pubDate>Sun, 05 Jul 2026 00:00:00 GMT</pubDate>
      <category>AI</category>
      <description>&quot;AI memory&quot; covers three things that don't work alike: an outdated encyclopedia, a scratchpad that clears when you leave, and a notepad it keeps between sessions.</description>
      <content:encoded><![CDATA[<p><img src="https://gabycharalampidi.com/notes/your-ai-keeps-three-kinds-of-memory-slide1%20(1).png" alt="" /></p><p>The question sounds like a trap. If an AI can remember your name from last week, doesn’t it have a memory? It does. It keeps three of them, and they work nothing alike. Knowing which one you are leaning on tells you how much to trust the answer.</p>
<p>The first is the encyclopedia in its head. When a model trains, what it learns gets baked into its weights, “encoded in the model’s weights during training” and read straight back when it answers (<a href="https://aiagentmemory.org/articles/llm-parametric-memory/">aiagentmemory.org</a>). This is the layer that holds grammar, facts, and how to reason. It is also frozen. That memory is “fixed after training,” so “from the moment training ends” it starts drifting out of date. The risk here is confidence, not gaps. It sounds just as sure about a price that changed last quarter as one that held.</p>
<p>The second is the clipboard in its hand: the context window, the working memory for one conversation. This is the one that feels most like memory, and it is the biggest illusion. The model does not hold your last message between turns. The service is stateless, so every time you send something the whole conversation gets resent and “the LLM processes all these messages again” (<a href="https://arxiv.org/pdf/2312.05516">arxiv.org</a>). The memory you feel is the model re-reading the thread you keep handing back. Overflow the clipboard and the oldest lines fall off.</p>
<p>The third is the sticky-note pad on the wall: the memory feature. Tell ChatGPT “remember that I am vegetarian” and that saved note becomes “part of the context ChatGPT uses to generate a response” (<a href="https://openai.com/index/memory-and-new-controls-for-chatgpt/">openai.com</a>). Claude does the same, keeping “your role, your preferences and how you like responses formatted” as a running summary (<a href="https://sider.ai/blog/ai-tools/what-is-claude-memory-anthropic-s-new-team-feature-explained">sider.ai</a>). The model did not grow a memory. A separate system holds a notepad and slips it in before the model answers, and it survives even a deleted chat.</p>
<p>So match the layer to the job. For anything time-sensitive, skip the frozen encyclopedia and paste the current fact onto the clipboard yourself. Expect one endless thread to slip, and start clean per task. And if you let the notepad remember you, open the settings and read what it wrote down. Memory is not one switch you flip. It is three tools, each with its own way of failing.</p>
<hr>
<p><strong>Sources</strong></p>
<ul>
<li><a href="https://aiagentmemory.org/articles/llm-parametric-memory/">aiagentmemory.org</a></li>
<li><a href="https://arxiv.org/pdf/2312.05516">arxiv.org</a></li>
<li><a href="https://openai.com/index/memory-and-new-controls-for-chatgpt/">openai.com</a></li>
<li><a href="https://sider.ai/blog/ai-tools/what-is-claude-memory-anthropic-s-new-team-feature-explained">sider.ai</a></li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>HEARD, and why the sequence matters</title>
      <link>https://gabycharalampidi.com/notes/heard</link>
      <guid isPermaLink="true">https://gabycharalampidi.com/notes/heard</guid>
      <pubDate>Sat, 04 Jul 2026 00:00:00 GMT</pubDate>
      <category>Leadership</category>
      <description>An upset customer wants to feel heard before they want a fix. The HEARD sequence, and why the order is doing all the work.</description>
      <content:encoded><![CDATA[<p><img src="https://gabycharalampidi.com/notes/slide1.png" alt="" /></p><p>An upset customer wants to feel heard before they want a fix.</p>
<p>Most of us reverse that. When something goes wrong, the first move is to explain: that the person we hired was new, that we were already on it, that no one meant it that way. All true, and none of it what the customer actually needs first. What they need first is to know I understood what happened, before I do anything about it.</p>
<h2 id="five-verbs-in-this-order">Five verbs, in this order</h2>
<p>The framework I use for this is HEARD, popularized by Disney.</p>
<ul>
<li><strong>Hear</strong> is the opening. <strong>“Tell me what happened.”</strong> No interrupting, no “I understand, but.” Just what happened.</li>
<li><strong>Empathize</strong> is next. <strong>“That would upset me too.”</strong> Reflect the emotion back before you address the facts. It lands differently than “I see.”</li>
<li><strong>Apologize</strong> follows. <strong>“I’m sorry that happened.”</strong> Not “I’m sorry you feel that way.” That is not the same apology.</li>
<li><strong>Resolve</strong> is the fix. <strong>“Here is what I’m going to do about it, and by when.”</strong> But only now, not before.</li>
<li><strong>Diagnose</strong> is different. <strong>You change what let it happen.</strong> This is the only step the customer never sees. It happens after they hang up, and it is the easiest one to skip.</li>
</ul>
<h2 id="the-sequence-is-doing-all-the-work">The sequence is doing all the work</h2>
<p>The intuitive order is Resolve first (fix the immediate problem), then maybe Diagnose if there is time, with empathy showing up as an afterthought. HEARD flips that. People need to feel heard before they can hear you, so you cannot skip ahead of them.</p>
<p>In practice, HEARD separates the customer conversation from the operational fix. H, E, A, R is the conversation. Everything that follows (the person, the process, the training) is D. Different problems, different clocks. Most operators try to compress them into one conversation, which usually means the customer walks away feeling like they were the diagnostic, not the customer.</p>
<h2 id="the-step-that-compounds">The step that compounds</h2>
<p>The other lesson: D is the step that compounds. Every complaint has a system underneath it. Skip D, and next month you write the same email.</p>]]></content:encoded>
    </item>
    <item>
      <title>What this site is</title>
      <link>https://gabycharalampidi.com/notes/what-this-site-is</link>
      <guid isPermaLink="true">https://gabycharalampidi.com/notes/what-this-site-is</guid>
      <pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate>
      <description>Why an operations person is posting her work in public.</description>
      <content:encoded><![CDATA[<p>I run a three-location tennis operation in Austin. About 50 staff, open 363 days a year, thousands of players coming through the courts. Most of my job is judgment under steady pressure: which problems the team should own, which I should own, which are worth solving at all, and which are quietly costing us more than the fix would.</p>
<p>Running an operation this size taught me that every operational problem is also a leadership problem. A recurring inventory drift is a clarity problem. A missed handoff is a definition-of-done problem. The work is naming both, then doing the harder thing the situation calls for.</p>
<p>This site is where I write about that work. Expect notes on the calls I make and the ones I get wrong: definition of done, clarity as a management tool, self-regulation under pressure, kindness versus directness, and the dozen other things nobody teaches you before you’re managing 50 people. Some of it is people work. Some of it is process. A recurring slice is software, because I have a CS degree and when a problem is mechanical and no one’s judgment is improving it, I build the tool that ends it.</p>
<p>Some notes will be text, some video. None of it is polished thought leadership. It is a working log.</p>
<p>If any of it is useful to you, or you are running an operation and want to compare notes on any of the above, find me on <a href="https://www.linkedin.com/in/gabycharalampidi/">LinkedIn</a> or send a note through the <a href="https://gabycharalampidi.com/#contact">contact form</a>.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
