<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xml:base="https://www.jaysonbrush.com/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jayson Brush</title>
    <link>https://www.jaysonbrush.com/</link>
    <atom:link href="https://www.jaysonbrush.com/feed.xml" rel="self" type="application/rss+xml" />
    <description>Director of Research and Innovation · Kansas City</description>
    <language>en</language>
    <item>
      <title>Building a Low-Cost Digital Signage Display with Raspberry Pi</title>
      <link>https://www.jaysonbrush.com/2022/08/07/raspberry-pi-digital-signage/</link>
      <description>&lt;p class=&quot;lead&quot;&gt;A step-by-step guide to transforming a Raspberry Pi Zero W into a dedicated digital signage kiosk—perfect for displaying dynamic content like movie posters, dashboards, or informational displays.&lt;/p&gt;
&lt;h2&gt;The Problem&lt;/h2&gt;
&lt;p&gt;I wanted a digital display in my home theater that would showcase movie posters from my Plex media server. Commercial digital signage solutions are expensive, and repurposing an old tablet felt wasteful and unreliable for 24/7 operation.&lt;/p&gt;
&lt;h2&gt;The Solution&lt;/h2&gt;
&lt;p&gt;A Raspberry Pi Zero W ($15) configured as a dedicated kiosk. It boots directly into a fullscreen Chromium browser displaying content from any URL—no desktop environment, no distractions, just the content.&lt;/p&gt;
&lt;p&gt;For my setup, I used &lt;a href=&quot;https://www.mattsshack.com/plex-movie-poster-display-v3/&quot;&gt;Matt’s Plex Movie Poster Display&lt;/a&gt; running on a local VM, but this kiosk can display any web-based content: dashboards, calendars, weather displays, or custom signage.&lt;/p&gt;
&lt;h2&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Raspberry Pi Zero W (or any Raspberry Pi)&lt;/li&gt;
&lt;li&gt;MicroSD card (8GB minimum)&lt;/li&gt;
&lt;li&gt;Display with HDMI input&lt;/li&gt;
&lt;li&gt;Raspbian Buster installed&lt;/li&gt;
&lt;li&gt;Network connectivity (WiFi or Ethernet)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Instructions&lt;/h2&gt;
&lt;h3&gt;Step 1: Initial Configuration&lt;/h3&gt;
&lt;p&gt;Boot your Pi and log in with the default credentials (&lt;code&gt;pi&lt;/code&gt; / &lt;code&gt;raspberry&lt;/code&gt;), then run the configuration utility:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;sudo raspi-config
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Configure the following settings:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Change the default password&lt;/li&gt;
&lt;li&gt;Set your hostname&lt;/li&gt;
&lt;li&gt;Configure WiFi (SSID and password)&lt;/li&gt;
&lt;li&gt;Set your timezone&lt;/li&gt;
&lt;li&gt;Enable SSH under Interface Options&lt;/li&gt;
&lt;li&gt;Set Boot Options → Desktop / CLI → Console Autologin&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Finish and reboot. From this point forward, you can work remotely via SSH.&lt;/p&gt;
&lt;h3&gt;Step 2: Update the System&lt;/h3&gt;
&lt;pre&gt;&lt;code&gt;sudo apt-get update &amp;amp;&amp;amp; sudo apt-get upgrade -y
&lt;/code&gt;&lt;/pre&gt;
&lt;h3&gt;Step 3: Install Minimal Display Environment&lt;/h3&gt;
&lt;p&gt;Install only what’s needed for kiosk mode—no full desktop environment:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;sudo apt-get install --no-install-recommends xserver-xorg x11-xserver-utils xinit openbox chromium-browser -y
&lt;/code&gt;&lt;/pre&gt;
&lt;h3&gt;Step 4: Configure Openbox Autostart&lt;/h3&gt;
&lt;p&gt;Edit the Openbox autostart configuration:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;sudo nano /etc/xdg/openbox/autostart
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Add the following content:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;# Disable screen saver and power management
xset s off
xset s noblank
xset -dpms

# Allow quitting X server with CTRL-ALT-Backspace
setxkbmap -option terminate:ctrl_alt_bksp

# Clear Chromium crash flags and launch in kiosk mode
sed -i &#39;s/&amp;quot;exited_cleanly&amp;quot;:false/&amp;quot;exited_cleanly&amp;quot;:true/&#39; ~/.config/chromium/&#39;Local State&#39;
sed -i &#39;s/&amp;quot;exited_cleanly&amp;quot;:false/&amp;quot;exited_cleanly&amp;quot;:true/; s/&amp;quot;exit_type&amp;quot;:&amp;quot;[^&amp;quot;]&#92;+&amp;quot;/&amp;quot;exit_type&amp;quot;:&amp;quot;Normal&amp;quot;/&#39; ~/.config/chromium/Default/Preferences
chromium-browser --disable-infobars --noerrdialogs --incognito --kiosk &#39;https://YOUR-URL-HERE&#39;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Replace &lt;code&gt;https://YOUR-URL-HERE&lt;/code&gt; with the URL you want to display.&lt;/p&gt;
&lt;h3&gt;Step 5: Auto-Start on Boot&lt;/h3&gt;
&lt;p&gt;Configure X to start automatically when the Pi boots:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;nano ~/.profile
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Add this line at the end:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;[[ -z $DISPLAY &amp;amp;&amp;amp; $XDG_VTNR -eq 1 ]] &amp;amp;&amp;amp; startx -- -nocursor
&lt;/code&gt;&lt;/pre&gt;
&lt;h3&gt;Optional: Clean Boot Experience&lt;/h3&gt;
&lt;p&gt;For a cleaner boot sequence, edit &lt;code&gt;/boot/config.txt&lt;/code&gt;:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;sudo nano /boot/config.txt
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Add these lines:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;# Disable rainbow splash screen
disable_splash=1

# Rotate display (if needed for vertical orientation)
# display_rotate=3
&lt;/code&gt;&lt;/pre&gt;
&lt;h2&gt;Result&lt;/h2&gt;
&lt;p&gt;After a reboot, your Pi will boot directly into a fullscreen browser displaying your content. No login prompts, no desktop, no cursor—just clean digital signage running 24/7 on minimal hardware.&lt;/p&gt;
</description>
      <pubDate>Sun, 07 Aug 2022 11:17:45 CDT</pubDate>
      <dc:creator>Jayson Brush</dc:creator>
      <guid>https://www.jaysonbrush.com/2022/08/07/raspberry-pi-digital-signage/</guid>
    </item>
    <item>
      <title>Values That Actually Work</title>
      <link>https://www.jaysonbrush.com/2024/09/12/values-that-actually-work/</link>
      <description>&lt;p class=&quot;lead&quot;&gt;It is surprisingly difficult for an organization to keep its stated values active. Too often, they can become like wallpaper, looking good in the lobby, but disconnected from how hard decisions actually get made.&lt;/p&gt;
&lt;h2&gt;The Poster Test&lt;/h2&gt;
&lt;p&gt;Here’s a question I ask myself about any organization’s stated values: when was the last time someone made a hard decision by referencing them? Not a feel-good moment where the values happened to align with what everyone already wanted. A genuinely difficult call where the values tipped the balance.&lt;/p&gt;
&lt;p&gt;If I can’t think of an example, those values are probably decoration.&lt;/p&gt;
&lt;p&gt;I’ve seen organizations with long lists of values that sound inspiring but don’t help anyone make decisions. Words that look good on a wall but don’t tell you what to do when two good options conflict. Over the years, I’ve developed four tenets of my own that I use wherever I work. They’re specific enough that when I’m evaluating a solution or making a tradeoff, they actually give me an answer. That’s the difference between decoration and something useful. At the end of the day, what matters is getting everyone to row the boat in the same direction. If your values do that, they’re working.&lt;/p&gt;
&lt;h2&gt;Aspirational vs. Operational&lt;/h2&gt;
&lt;p&gt;I’ve noticed a common pattern in how organizations define values. Leadership gets together, brainstorms what they want the company to be, and produces a list of aspirational qualities. Words that no one would argue against.&lt;/p&gt;
&lt;p&gt;In my experience, that’s the problem. If no one would argue against it, it’s not doing any work. A value that doesn’t help you choose between two reasonable options is just a slogan.&lt;/p&gt;
&lt;p&gt;What I’d call operational values are different. They describe how an organization actually behaves when things get hard. They’re specific enough to create disagreement. Not everyone would choose them, and I think that’s the point.&lt;/p&gt;
&lt;h2&gt;Finding Your Real Values&lt;/h2&gt;
&lt;p&gt;Instead of asking “what do we want to be,” I’ve found it more useful to ask:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;When we’re at our best, what’s driving that?&lt;/li&gt;
&lt;li&gt;What behaviors do we consistently reward, even informally?&lt;/li&gt;
&lt;li&gt;What would make someone a bad fit here, even if they’re talented?&lt;/li&gt;
&lt;li&gt;When we’ve made hard tradeoffs, what did we prioritize?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The answers tend to reveal actual operating values. They might not match what’s on the website. That gap is worth understanding.&lt;/p&gt;
&lt;h2&gt;Values as Decision Filters&lt;/h2&gt;
&lt;p&gt;The way I see it, working values should function as filters. When you’re stuck on a decision, you should be able to ask “which option better reflects our values?” and get a real answer.&lt;/p&gt;
&lt;p&gt;This requires specificity. “We value speed” is too vague. “We ship fast and iterate, even if it means launching with rough edges” tells you what to do when perfection and pace conflict. It creates useful tension. Not everyone agrees that shipping fast is worth rough edges. I think that disagreement is a feature, not a bug.&lt;/p&gt;
&lt;h2&gt;The Authenticity Requirement&lt;/h2&gt;
&lt;p&gt;From what I’ve seen, values only work if leadership actually believes them. You can’t install values through a memo. If the stated values contradict how leaders behave, people will follow the behavior every time.&lt;/p&gt;
&lt;p&gt;This means the values have to come from who the leadership team actually is, not who they think they should be. A leadership team that values stability shouldn’t pretend to value disruption. A team that prioritizes analysis shouldn’t claim to value speed over deliberation.&lt;/p&gt;
&lt;p&gt;In my opinion, authentic values that don’t sound impressive will always beat impressive values that aren’t authentic.&lt;/p&gt;
&lt;h2&gt;Putting Them to Work&lt;/h2&gt;
&lt;p&gt;Once you have values worth having, my advice is simple: use them.&lt;/p&gt;
&lt;p&gt;Reference them when explaining decisions. Include values-based questions in interviews. Tie feedback to specific values so people see them in action, not just on a poster.&lt;/p&gt;
&lt;p&gt;Values aren’t a one-time exercise. They’re a tool that gets sharper with use. At least, that’s been my experience. If you’re not reaching for them regularly, they’ll fade into the wallpaper where they started.&lt;/p&gt;
</description>
      <pubDate>Thu, 12 Sep 2024 09:00:00 CDT</pubDate>
      <dc:creator>Jayson Brush</dc:creator>
      <guid>https://www.jaysonbrush.com/2024/09/12/values-that-actually-work/</guid>
    </item>
    <item>
      <title>When to Kill a Project</title>
      <link>https://www.jaysonbrush.com/2024/11/15/when-to-kill-a-project/</link>
      <description>&lt;p class=&quot;lead&quot;&gt;Every organization has at least one project that should have ended months ago. Recognizing when to pull the plug is one of the hardest skills in leadership.&lt;/p&gt;
&lt;p&gt;Leaders who have been through difficult endings in their own lives often develop a clearer eye for this. When you’ve experienced firsthand that short-term pain can lead to long-term growth, you stop treating endings as failures. You start seeing them as part of how things get better.&lt;/p&gt;
&lt;h2&gt;The Sunk Cost Trap&lt;/h2&gt;
&lt;p&gt;We’ve all been there. A project that made sense when it started has been limping along for quarters. The team is demoralized. Resources are being pulled from higher-potential work. But nobody wants to be the one who calls it.&lt;/p&gt;
&lt;p&gt;The usual justification: “We’ve invested so much already.” This is the &lt;a href=&quot;https://greatergood.berkeley.edu/article/item/how_the_sunk_cost_fallacy_can_drive_bad_decisions&quot;&gt;sunk cost fallacy&lt;/a&gt; dressed up as responsibility. The time and money you’ve spent are gone regardless of what you do next. The only question that matters is whether continuing creates more value than stopping.&lt;/p&gt;
&lt;h2&gt;The Pruning Framework&lt;/h2&gt;
&lt;p&gt;Henry Cloud’s book &lt;a href=&quot;https://www.amazon.com/Necessary-Endings-Henry-Cloud/dp/0061777129?tag=jaysonbrush-20&quot;&gt;&lt;em&gt;Necessary Endings&lt;/em&gt;&lt;/a&gt; offers a useful mental model. Think of your organization like a tree. Healthy trees get pruned. Not because the branches are dead, but because removing some allows others to thrive.&lt;/p&gt;
&lt;p&gt;Cloud identifies three types of branches:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dead branches&lt;/strong&gt;: Projects that have clearly failed. These are easy to cut.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sick branches&lt;/strong&gt;: Projects showing signs of decline but still functioning. Harder to cut because they’re “not that bad.”&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Healthy branches consuming too many resources&lt;/strong&gt;: This is the hardest category. The project works, but it’s starving something more important.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Most organizations handle the first category reasonably well. The second and third are where projects go to slowly die while draining resources.&lt;/p&gt;
&lt;h2&gt;The Values Filter&lt;/h2&gt;
&lt;p&gt;When a project is in the gray zone, data alone won’t give you the answer. You need a different question: “Does this still align with our mission?”&lt;/p&gt;
&lt;p&gt;This shifts the conversation from performance metrics to purpose. A project might be hitting its numbers but pulling the organization away from where it needs to go. Or it might be underperforming but still central to the mission.&lt;/p&gt;
&lt;p&gt;The values filter also removes some of the emotional charge. You’re not saying the project was a mistake or that the people involved failed. You’re saying the organization has evolved and this no longer fits.&lt;/p&gt;
&lt;h2&gt;Hurt vs. Harm&lt;/h2&gt;
&lt;p&gt;Ending a project hurts. People put time and identity into their work. Acknowledging that something didn’t pan out is uncomfortable.&lt;/p&gt;
&lt;p&gt;But there’s a difference between hurt and harm. Hurt is the short-term emotional cost of making a hard decision. Harm is the long-term damage of not making it.&lt;/p&gt;
&lt;p&gt;When you delay a necessary ending, you harm morale across the organization. High performers see resources going to low-potential work. They see leadership unwilling to make hard calls. Eventually, &lt;a href=&quot;https://news.cornell.edu/stories/2025/08/high-achievers-more-likely-bolt-when-top-rankings-are-restricted&quot;&gt;they leave&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;How to Do It&lt;/h2&gt;
&lt;p&gt;Once you’ve decided to end a project:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Be direct about the reasoning.&lt;/strong&gt; Don’t hide behind vague corporate language. Explain what changed and why this no longer fits.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Acknowledge the work.&lt;/strong&gt; The effort was real even if the outcome wasn’t what you hoped.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Move quickly.&lt;/strong&gt; Prolonged wind-downs are worse than clean endings.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Redeploy the people.&lt;/strong&gt; Your best people from the cancelled project should be the first ones staffed onto something new.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The goal isn’t to make ending projects feel good. It’s to make your organization capable of ending them when necessary, so resources flow to where they create the most value.&lt;/p&gt;
</description>
      <pubDate>Fri, 15 Nov 2024 13:20:00 CST</pubDate>
      <dc:creator>Jayson Brush</dc:creator>
      <guid>https://www.jaysonbrush.com/2024/11/15/when-to-kill-a-project/</guid>
    </item>
    <item>
      <title>The Long View</title>
      <link>https://www.jaysonbrush.com/2025/07/08/the-long-view/</link>
      <description>&lt;p class=&quot;lead&quot;&gt;When you zoom out to 70,000 years of human history, today’s crisis looks different. That shift in perspective can change how you lead.&lt;/p&gt;
&lt;p&gt;I read Yuval Noah Harari’s &lt;a href=&quot;https://www.amazon.com/Sapiens-Humankind-Yuval-Noah-Harari/dp/0062316095?tag=jaysonbrush-20&quot;&gt;&lt;em&gt;Sapiens&lt;/em&gt;&lt;/a&gt; a few years ago and it rewired something in how I think. Not about history, exactly. About scale. About what actually matters when you take the long view.&lt;/p&gt;
&lt;p&gt;The book traces human history from the cognitive revolution 70,000 years ago to today. It covers the agricultural revolution, the rise of empires, the scientific revolution, and the interconnected world we live in now. But what stuck with me wasn’t any single event. It was the perspective.&lt;/p&gt;
&lt;h2&gt;The Day-to-Day Fades&lt;/h2&gt;
&lt;p&gt;Most of what consumes our attention today won’t matter in a year. Almost none of it will matter in ten. At the scale Harari writes about, entire empires rise and fall in a few pages.&lt;/p&gt;
&lt;p&gt;Some might call that nihilism, but I find it freeing. At least, that’s the idea. In practice, I still react to things that don’t deserve the energy. This is something I work at constantly. But when I can step back and remember that the urgent email, the difficult conversation, the project that’s behind schedule are all temporary, I handle them differently. The anxiety drops. I can think more clearly because I’m not treating everything like a survival threat.&lt;/p&gt;
&lt;p&gt;I still care about getting things right. But I’m trying to stop pretending that most problems are as serious as they feel in the moment.&lt;/p&gt;
&lt;h2&gt;What Actually Lasts&lt;/h2&gt;
&lt;p&gt;Harari argues that what made humans dominant wasn’t strength or speed. It was our ability to cooperate flexibly in large numbers, built on shared stories and beliefs. Money, nations, corporations, religions are all fictions we agree to believe in, and those agreements help us coordinate at scale.&lt;/p&gt;
&lt;p&gt;At work, this translates directly. The culture you build, the trust you establish, the way people learn to work together: these outlast any individual project or product. &lt;a href=&quot;https://pmc.ncbi.nlm.nih.gov/articles/PMC10850337/&quot;&gt;Teams that share a clear understanding&lt;/a&gt; of what they’re doing and why will outperform teams that don’t, regardless of talent levels.&lt;/p&gt;
&lt;p&gt;The shared story matters more than the quarterly numbers.&lt;/p&gt;
&lt;h2&gt;Progress Is Real&lt;/h2&gt;
&lt;p&gt;One thing Sapiens reinforced for me: despite everything, humans have made extraordinary progress. &lt;a href=&quot;https://ourworldindata.org/a-history-of-global-living-conditions&quot;&gt;Life expectancy, literacy, poverty reduction&lt;/a&gt;, violence per capita. By almost every measure, the average human today lives better than royalty did a few centuries ago.&lt;/p&gt;
&lt;p&gt;This matters for leadership because pessimism is easy and optimism requires effort. When you understand the long arc of human improvement, you can hold both realities: yes, there are serious problems, and yes, we’ve solved serious problems before. That combination of clear-eyed realism and grounded hope is what effective leadership looks like.&lt;/p&gt;
&lt;h2&gt;Applying the Long View&lt;/h2&gt;
&lt;p&gt;I try to ask myself a question when things get stressful: will this matter in ten years? Usually the answer is no. That should help me respond proportionally instead of reacting emotionally. Sometimes it works. Often it doesn’t. Stepping back is harder than it sounds, and it’s something I have to work at every day.&lt;/p&gt;
&lt;p&gt;For the things that do matter at that scale, like relationships, reputation, the skills your team develops, the culture you build, I try to invest more attention. These compound over time. They’re the things that actually last.&lt;/p&gt;
&lt;p&gt;Sapiens is a long book and not everyone will read it. But the core shift is available to anyone: step back far enough that you can see the whole arc, and suddenly it’s easier to tell what’s urgent from what’s important.&lt;/p&gt;
</description>
      <pubDate>Tue, 08 Jul 2025 07:59:00 CDT</pubDate>
      <dc:creator>Jayson Brush</dc:creator>
      <guid>https://www.jaysonbrush.com/2025/07/08/the-long-view/</guid>
    </item>
    <item>
      <title>Building a Unified Identity Source of Truth</title>
      <link>https://www.jaysonbrush.com/2025/10/14/building-a-unified-identity-source-of-truth/</link>
      <description>&lt;p&gt;Every organization with more than a few dozen employees has the same problem. User identities are scattered across systems that do not talk to each other.&lt;/p&gt;
&lt;p&gt;The primary directory holds the canonical employee record. Google Workspace has its own user database. Microsoft 365 maintains a separate identity store. Your line-of-business applications each have their own user tables. And somewhere in the middle, a help desk technician is manually copying data between systems, hoping they do not make a typo.&lt;/p&gt;
&lt;p&gt;This is the identity fragmentation problem. I have spent years building systems to solve it.&lt;/p&gt;
&lt;h2&gt;The Real Cost of Fragmentation&lt;/h2&gt;
&lt;p&gt;When someone joins your organization, they need accounts in multiple systems. When they leave, those accounts need to be disabled everywhere. When they change their password, that change should propagate. When they move departments, their permissions should update.&lt;/p&gt;
&lt;p&gt;In a fragmented environment, each of these events requires manual intervention in multiple places. A new hire means five separate account creations. An offboarding means hunting through every system to make sure access was revoked. A password reset means walking the user through three different change dialogs.&lt;/p&gt;
&lt;p&gt;The labor cost is obvious. Less obvious is the security cost. Orphaned accounts in forgotten systems become attack vectors. Password policies cannot be enforced consistently. Access reviews require pulling reports from a dozen sources and correlating them manually.&lt;/p&gt;
&lt;p&gt;Most organizations do not realize how bad the problem is until they fail an audit or discover a former employee still had active access six months after leaving.&lt;/p&gt;
&lt;h2&gt;The Source of Truth Problem&lt;/h2&gt;
&lt;p&gt;The first instinct is usually to pick a winner. Make the primary directory the canonical source. Or make your HR system the master record. Everything else syncs from there.&lt;/p&gt;
&lt;p&gt;This works until it does not. Different systems have different data models. AD does not know about Google organizational units. Google does not understand AD nested group memberships. Your HR system has fields that neither directory cares about.&lt;/p&gt;
&lt;p&gt;One-way sync creates a different kind of fragmentation. Now you have authoritative data in one place and stale copies everywhere else. The copies drift. Edge cases accumulate. Someone makes a temporary change directly in a downstream system, and now your sync is in conflict.&lt;/p&gt;
&lt;p&gt;The solution is not picking a winner. It is building a layer that understands all the systems and manages the relationships between them.&lt;/p&gt;
&lt;h2&gt;The Orchestration Layer&lt;/h2&gt;
&lt;p&gt;The solution is an orchestration layer that sits above the individual identity stores and treats them as endpoints rather than sources. The dashboard maintains its own record of what each user state should be across all systems. Changes flow through the dashboard, which then pushes updates to each connected system.&lt;/p&gt;
&lt;p&gt;This inverts the typical model. Instead of systems syncing to each other, they all sync to a central orchestrator. The orchestrator knows the mapping between systems and handles the translation.&lt;/p&gt;
&lt;p&gt;A password change becomes a single action. The user changes their password in the dashboard. The dashboard updates the primary directory, then Google, then M365, then any other connected system. The user does not know or care that multiple systems are involved.&lt;/p&gt;
&lt;p&gt;An offboarding becomes a single click. Disable the user in the dashboard, and every connected account is suspended simultaneously. No hunting through systems. No checklist of manual steps.&lt;/p&gt;
&lt;h2&gt;Sync Flags and Conflict Resolution&lt;/h2&gt;
&lt;p&gt;The tricky part is handling systems that can be authoritative for different attributes. Maybe HR owns the employee department and title. Maybe the primary directory owns their group memberships. Maybe Google owns their email aliases.&lt;/p&gt;
&lt;p&gt;The solution is attribute-level sync flags. Each attribute on a user record has metadata indicating which system is authoritative for that value. When a sync runs, the orchestrator checks the flag before deciding whether to push or pull.&lt;/p&gt;
&lt;p&gt;This sounds complicated, but it matches how organizations actually work. The HR team manages HR data. The IT team manages technical access. The email admin manages distribution lists. Each team works in their preferred system, and the orchestrator keeps everything consistent.&lt;/p&gt;
&lt;p&gt;Conflicts still happen. Someone updates a field in two systems before sync runs. The orchestrator needs rules for resolving these: timestamp wins, specific system wins, alert a human. The right choice depends on the attribute and the organization policies.&lt;/p&gt;
&lt;h2&gt;Scale Considerations&lt;/h2&gt;
&lt;p&gt;A few hundred users, you can brute-force this. Full sync every hour, compare everything, update what changed. A few thousand users and this starts to strain. Tens of thousands and it falls over completely.&lt;/p&gt;
&lt;p&gt;A system built on these principles manages hundreds of thousands of user records. Full sync is not possible at that scale. Instead, changes are tracked incrementally. Each system reports what changed since the last sync. The orchestrator processes only the deltas.&lt;/p&gt;
&lt;p&gt;This requires buy-in from the connected systems. the primary directory has change tracking built in (USN changed). Google has a sync API with delta support. M365 has delta queries. Not every system cooperates this well. Some require polling and comparison, which gets expensive.&lt;/p&gt;
&lt;p&gt;The other scale problem is consistency. With hundreds of thousands of records, something is always in the process of syncing. A query might return stale data because the update has not propagated yet. The system needs to handle this gracefully, either by accepting eventual consistency or by implementing synchronous updates for critical operations.&lt;/p&gt;
&lt;h2&gt;The Security Model&lt;/h2&gt;
&lt;p&gt;An identity orchestrator is a high-value target. It has credentials for every connected system. A compromise means access to everything.&lt;/p&gt;
&lt;p&gt;Defense in depth matters here. The orchestrator should not store credentials in plain text. It should not have more access than it needs. It should log every action for audit. It should require its own strong authentication.&lt;/p&gt;
&lt;p&gt;The implementation uses credential storage using hardware security modules where possible, encrypted storage where not. Service accounts have minimal permissions, just enough to read and write user attributes. Every sync operation is logged with before and after states.&lt;/p&gt;
&lt;p&gt;The dashboard itself requires multi-factor authentication. Role-based access controls limit who can see what. Bulk operations require approval workflows.&lt;/p&gt;
&lt;h2&gt;What Changes&lt;/h2&gt;
&lt;p&gt;Once the orchestrator is running, the operational model shifts. The help desk stops logging into multiple systems. They work in one place, and the orchestrator handles the rest.&lt;/p&gt;
&lt;p&gt;User onboarding goes from hours to minutes. Create the user once, assign the right sync flags, and every system gets configured automatically. Offboarding is instant and complete.&lt;/p&gt;
&lt;p&gt;Password reset calls drop because users have one password that works everywhere. Audit reports pull from a single source. Access reviews show a unified view of who has access to what.&lt;/p&gt;
&lt;p&gt;The systems people used to complain about become invisible infrastructure. the primary directory, Google, M365: they are still there, still running, but nobody thinks about them individually anymore. They are just endpoints that the orchestrator manages.&lt;/p&gt;
&lt;h2&gt;The Broader Principle&lt;/h2&gt;
&lt;p&gt;Identity fragmentation is a symptom of a larger pattern. Organizations accumulate systems over time. Each system brings its own data model, its own management interface, its own operational burden. The complexity compounds until managing the systems is a full-time job for multiple people.&lt;/p&gt;
&lt;p&gt;The fix is always the same: build an abstraction layer that unifies the complexity behind a single interface. Do not try to replace the systems. Do not try to force them to talk directly. Build something that translates between them and presents a coherent view to operators.&lt;/p&gt;
&lt;p&gt;This works for identity. It works for device management. It works for configuration management. Any domain where data lives in multiple systems can benefit from an orchestration layer that makes those systems feel like one.&lt;/p&gt;
&lt;p&gt;The investment is building the layer. The payoff is years of reduced operational friction.&lt;/p&gt;
</description>
      <pubDate>Tue, 14 Oct 2025 12:00:00 CDT</pubDate>
      <dc:creator>Jayson Brush</dc:creator>
      <guid>https://www.jaysonbrush.com/2025/10/14/building-a-unified-identity-source-of-truth/</guid>
    </item>
    <item>
      <title>Improving the Plex Movie Poster Display</title>
      <link>https://www.jaysonbrush.com/2025/11/04/improving-plex-movie-poster-display/</link>
      <description>&lt;p class=&quot;lead&quot;&gt;I forked the popular Plex Movie Poster Display project to address security vulnerabilities that made it risky to expose on a home network. Here’s what I changed and why it matters.&lt;/p&gt;
&lt;h2&gt;Background&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;https://github.com/MattsShack/Plex-Movie-Poster-Display&quot;&gt;Matt’s Plex Movie Poster Display&lt;/a&gt; is a great project that shows currently playing media on a dedicated display. When nothing is playing, it cycles through random posters from your unwatched library. I use it with a &lt;a href=&quot;https://www.jaysonbrush.com/2022/08/07/raspberry-pi-digital-signage/&quot;&gt;Raspberry Pi kiosk&lt;/a&gt; in my home theater.&lt;/p&gt;
&lt;p&gt;The original project works well, but it had security issues that concerned me—even for an internal application. Credentials stored in plaintext, no session management, and no CSRF protection are habits that shouldn’t exist in any codebase.&lt;/p&gt;
&lt;h2&gt;Security Improvements&lt;/h2&gt;
&lt;h3&gt;Bcrypt Password Hashing&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Before:&lt;/strong&gt; Passwords stored in plaintext in the config file.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;After:&lt;/strong&gt; Passwords are hashed using bcrypt. Even if someone accesses your config file, they won’t see the actual password.&lt;/p&gt;
&lt;h3&gt;Session Timeout&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Before:&lt;/strong&gt; Sessions never expired.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;After:&lt;/strong&gt; Automatic logout after 30 minutes of inactivity. If you forget to log out of the settings panel, you’re not left exposed indefinitely.&lt;/p&gt;
&lt;h3&gt;CSRF Protection&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Before:&lt;/strong&gt; Forms had no protection against cross-site request forgery.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;After:&lt;/strong&gt; All forms include CSRF tokens, preventing malicious sites from submitting requests on your behalf.&lt;/p&gt;
&lt;h3&gt;Secure Session Handling&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Before:&lt;/strong&gt; Basic session management with no security considerations.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;After:&lt;/strong&gt; Proper session initialization, regeneration on login, and complete destruction on logout.&lt;/p&gt;
&lt;h3&gt;Token Validation&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Before:&lt;/strong&gt; Plex token was used without validation.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;After:&lt;/strong&gt; Token is validated before the display loads, preventing errors and potential information leakage.&lt;/p&gt;
&lt;h2&gt;Why This Matters&lt;/h2&gt;
&lt;p&gt;“It’s just an internal tool” is how security vulnerabilities become habits. Every project—regardless of where it runs—should follow security best practices:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Never store passwords in plaintext&lt;/li&gt;
&lt;li&gt;Always implement session timeouts&lt;/li&gt;
&lt;li&gt;Protect forms against CSRF&lt;/li&gt;
&lt;li&gt;Validate all inputs and tokens&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These aren’t just rules for production applications. They’re habits that should be automatic.&lt;/p&gt;
&lt;h2&gt;Get the Fork&lt;/h2&gt;
&lt;p&gt;The secured version is available on GitHub: &lt;a href=&quot;https://github.com/jaysonbrush/Plex-Movie-Poster-Display&quot;&gt;jaysonbrush/Plex-Movie-Poster-Display&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Installation is the same as the original—just clone, configure, and deploy. If you’re running this on a Raspberry Pi kiosk, check out my &lt;a href=&quot;https://www.jaysonbrush.com/2022/08/07/raspberry-pi-digital-signage/&quot;&gt;digital signage guide&lt;/a&gt; for the full setup.&lt;/p&gt;
</description>
      <pubDate>Tue, 04 Nov 2025 16:44:00 CST</pubDate>
      <dc:creator>Jayson Brush</dc:creator>
      <guid>https://www.jaysonbrush.com/2025/11/04/improving-plex-movie-poster-display/</guid>
    </item>
    <item>
      <title>The Bus Policy</title>
      <link>https://www.jaysonbrush.com/2025/12/30/the-bus-policy/</link>
      <description>&lt;p class=&quot;lead&quot;&gt;If your most critical engineer left tomorrow, how long would it take to recover? The answer tells you how resilient your organization actually is.&lt;/p&gt;
&lt;p&gt;I’ve seen this play out. A key person leaves and suddenly everyone realizes how much was only in their head. The scramble that follows is painful and expensive.&lt;/p&gt;
&lt;p&gt;One question I ask myself regularly: who’s my backup? Not one person who handles everything when I’m out. That’s overwhelming for them and fragile for the organization. Instead, I think about who can pick up different parts of what I do. The load gets distributed, and no single person becomes a bottleneck.&lt;/p&gt;
&lt;h2&gt;The Question Nobody Wants to Ask&lt;/h2&gt;
&lt;p&gt;“What happens if someone gets hit by a bus?” It’s a morbid way to frame it. In our office we joke about “what if they won the lottery?” as the friendlier version. Either way, the question matters. Every team has at least one person whose departure would cause serious disruption. They’re the only one who understands a critical system, or they hold all the client relationships, or they’re the glue that keeps everything running.&lt;/p&gt;
&lt;p&gt;The bus policy isn’t about expecting disaster. It’s about building an organization that can absorb unexpected losses without falling apart.&lt;/p&gt;
&lt;h2&gt;Identify Your Single Points of Failure&lt;/h2&gt;
&lt;p&gt;Start by mapping out who knows what. For every critical system, process, or relationship, ask:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Who is the primary owner?&lt;/li&gt;
&lt;li&gt;Who else could step in with minimal ramp-up?&lt;/li&gt;
&lt;li&gt;What documentation exists?&lt;/li&gt;
&lt;li&gt;How long would it take to train a replacement?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If the answer to “who else could step in” is “nobody,” you’ve found a single point of failure. And if the answer is only one name, you’ve just moved the single point of failure one step away. Look for ways to spread knowledge across multiple people.&lt;/p&gt;
&lt;h2&gt;Documentation That Actually Gets Used&lt;/h2&gt;
&lt;p&gt;Most organizations have documentation. Most of it is outdated, incomplete, or impossible to find when you need it.&lt;/p&gt;
&lt;p&gt;Effective documentation isn’t about writing everything down. It’s about capturing the information that would take the longest to reconstruct: why decisions were made (not just what was decided), the gotchas and edge cases that aren’t obvious, who to call when something breaks, and the stuff that’s “in someone’s head.”&lt;/p&gt;
&lt;p&gt;A good test: could someone new to the team use this documentation to solve a real problem? If not, the documentation needs work.&lt;/p&gt;
&lt;h2&gt;Cross-Training as Insurance&lt;/h2&gt;
&lt;p&gt;Documentation helps, but nothing replaces &lt;a href=&quot;https://pmc.ncbi.nlm.nih.gov/articles/PMC8569223/&quot;&gt;hands-on experience&lt;/a&gt;. Build cross-training into your normal operations.&lt;/p&gt;
&lt;p&gt;Have people shadow each other on critical tasks, even if it feels inefficient in the short term. When someone takes vacation, split their responsibilities across a few people rather than dumping everything on one backup. Each person handles a piece, nobody gets overwhelmed, and more people gain exposure.&lt;/p&gt;
&lt;p&gt;Spread on-call duties so multiple people learn how systems fail. The person who’s been paged at 2am about a database issue understands that system differently than someone who’s only read the runbook.&lt;/p&gt;
&lt;p&gt;The goal isn’t to make everyone interchangeable. It’s to ensure that no single departure creates a crisis.&lt;/p&gt;
&lt;h2&gt;Shared Ownership Over Hero Culture&lt;/h2&gt;
&lt;p&gt;Some organizations accidentally reward &lt;a href=&quot;https://pubmed.ncbi.nlm.nih.gov/24113634/&quot;&gt;single points of failure&lt;/a&gt;. The person who “owns” a critical system becomes indispensable. They’re the hero who saves the day when things break. This feels good in the moment but creates long-term fragility.&lt;/p&gt;
&lt;p&gt;Healthy organizations distribute ownership. No one person should be able to hold the company hostage, intentionally or not. If someone’s value comes entirely from being the only one who can do something, that’s a problem to solve, not a trait to celebrate.&lt;/p&gt;
&lt;p&gt;The same logic applies to backups. If your coverage plan is “Sarah handles everything when I’m out,” you’ve just made Sarah a single point of failure. Spread the load. Different people can own different pieces.&lt;/p&gt;
&lt;h2&gt;The Quarterly Review&lt;/h2&gt;
&lt;p&gt;Put this on your calendar every quarter: review your single points of failure list to see if anything has changed, check whether documentation is still accurate, confirm that everyone knows who covers what, and run a tabletop exercise where you pick a critical person and walk through what happens if they’re unavailable for a month.&lt;/p&gt;
&lt;p&gt;This takes an hour or two per quarter. The cost of not doing it is measured in weeks or months when something actually goes wrong.&lt;/p&gt;
&lt;p&gt;The bus policy isn’t pessimism. People leave, get sick, take new opportunities, or simply need a break. Building for that reality makes your organization stronger whether or not the unexpected ever happens.&lt;/p&gt;
</description>
      <pubDate>Tue, 30 Dec 2025 11:43:00 CST</pubDate>
      <dc:creator>Jayson Brush</dc:creator>
      <guid>https://www.jaysonbrush.com/2025/12/30/the-bus-policy/</guid>
    </item>
    <item>
      <title>Using MQTT as a Wake-Up Signal</title>
      <link>https://www.jaysonbrush.com/2026/01/25/beyond-polling-the-future-of-real-time-infrastructure/</link>
      <description>&lt;p&gt;When we built our device management agent, one of the first things we had to decide was how a device finds out it has work to do.&lt;/p&gt;
&lt;p&gt;The usual answer is polling, where every device asks the server on a timer whether there’s anything for it. It’s simple and it’s easy to debug, but almost all of it is wasted. Ten thousand devices checking in once a minute works out to about 170 requests a second all day long, and nearly every answer is no. You can stretch the interval to cut the load, but then a technician clicks a button and waits fifteen minutes to see if it worked. Our fleet is tens of thousands of Windows and Mac devices, so neither option was going to work.&lt;/p&gt;
&lt;p&gt;MQTT turns that around. Each device keeps a connection open to a broker and listens, and when the server has something it publishes a message and the device hears about it right away. When nothing is going on, the only traffic is a keepalive.&lt;/p&gt;
&lt;p&gt;A lot of people use MQTT to carry the actual command, and I understand why, because it works fine in a demo. It gets harder once commands get bigger, or you need to cancel one before it lands, or you need a record of exactly when a device picked it up. At that point you’re rebuilding pieces of HTTP on top of a message broker.&lt;/p&gt;
&lt;p&gt;We went the other way and made the MQTT message empty. It’s only a signal to go check. The device then fetches its pending commands over HTTPS with its own token, the same way it would if it were polling. Commands sit in the database until they’re picked up, so they can be changed or cancelled, and every fetch gets logged. Retries and error handling are ordinary HTTP.&lt;/p&gt;
&lt;p&gt;Keeping the message empty also settled how to handle broker credentials. All of our agents share the same broker login, stored encrypted on each device. Giving every device its own broker account would have meant provisioning and rotating thousands of credentials in a second system, and since the wake-up message doesn’t carry anything, the worst a forged one can do is make a device check in early.&lt;/p&gt;
&lt;p&gt;Each device listens on its own topic, a topic for its site, and one for the whole fleet, so a single publish can wake one laptop or every device we manage. The per-device topic is a SHA-256 hash of the device’s token so nobody can guess it.&lt;/p&gt;
&lt;p&gt;We still poll underneath all of this, once an hour instead of once a minute, because connections drop and some networks don’t like long-lived connections. If MQTT is down, commands still get there, only slower.&lt;/p&gt;
&lt;p&gt;The fallback caused a problem we didn’t expect. An agent that can’t log in to the broker drops to hourly polling and keeps working, so from the outside it looks healthy and you only notice because commands are slow. We added MQTT connection status per device to the dashboard so we can actually see it.&lt;/p&gt;
&lt;p&gt;For a few hundred devices I’d just poll. Push starts paying for itself somewhere in the thousands, and you need someone keeping an eye on the broker once you have it.&lt;/p&gt;
</description>
      <pubDate>Sun, 25 Jan 2026 13:20:00 CST</pubDate>
      <dc:creator>Jayson Brush</dc:creator>
      <guid>https://www.jaysonbrush.com/2026/01/25/beyond-polling-the-future-of-real-time-infrastructure/</guid>
    </item>
    <item>
      <title>Visualizing Claude Code Sessions in Real-Time</title>
      <link>https://www.jaysonbrush.com/2026/02/04/visualizing-claude-code-sessions/</link>
      <description>&lt;p class=&quot;lead&quot;&gt;I built a real-time visualization tool that displays active Claude Code sessions as characters working in a virtual office. Each session gets its own workspace, and activity updates live as Claude uses different tools.&lt;/p&gt;
&lt;figure&gt;&lt;img width=&quot;1280&quot; height=&quot;720&quot; src=&quot;https://www.jaysonbrush.com/wp-content/uploads/2026/02/ai-hq-screenshot.png&quot; alt=&quot;AI HQ - Claude Code Visualizer showing multiple sessions&quot;&gt;&lt;figcaption&gt;AI HQ displaying multiple Claude Code sessions&lt;/figcaption&gt;&lt;/figure&gt;
&lt;h2&gt;The Concept&lt;/h2&gt;
&lt;p&gt;When running multiple Claude Code sessions across different projects, it’s easy to lose track of what’s happening. I wanted a heads-up display that would show me at a glance which sessions are active and what they’re doing, all without switching between terminals.&lt;/p&gt;
&lt;p&gt;The result is AI HQ: a browser-based visualization where each Claude Code session is represented by a character at a workstation. The character’s actions reflect what Claude is actually doing in real-time.&lt;/p&gt;
&lt;h2&gt;How It Works&lt;/h2&gt;
&lt;p&gt;The system uses &lt;a href=&quot;https://docs.anthropic.com/en/docs/claude-code/hooks&quot;&gt;Claude Code hooks&lt;/a&gt; (PreToolUse and PostToolUse) to send events to a local Node.js server via WebSocket. The server maintains state for each session and broadcasts updates to any connected browser clients.&lt;/p&gt;
&lt;p&gt;When Claude starts using a tool, the hook fires and sends the tool name and session ID to the server. The visualization updates immediately:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Edit, Write, Bash&lt;/strong&gt;: Character typing&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Read, Grep, Glob&lt;/strong&gt;: Character thinking&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No activity for 15+ seconds&lt;/strong&gt;: Character idle&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Architecture&lt;/h2&gt;
&lt;p&gt;The stack is intentionally minimal:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Node.js server&lt;/strong&gt; with WebSocket support (ws package)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Vanilla JavaScript frontend&lt;/strong&gt; with HTML5 Canvas&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;PowerShell hook scripts&lt;/strong&gt; that POST events to the server&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;No frameworks, no build process. Just start the server and open the browser. The visualization is network-accessible, so you can display it on a secondary monitor or another machine entirely.&lt;/p&gt;
&lt;h2&gt;Session Management&lt;/h2&gt;
&lt;p&gt;Each Claude Code instance gets a unique session ID. The visualization tracks:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Session title (pulled from working directory)&lt;/li&gt;
&lt;li&gt;Current state (typing, thinking, idle)&lt;/li&gt;
&lt;li&gt;Active tool being used&lt;/li&gt;
&lt;li&gt;Time since last activity&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A session panel displays all connected sessions with their current status, making it easy to monitor multiple projects simultaneously.&lt;/p&gt;
&lt;h2&gt;Use Cases&lt;/h2&gt;
&lt;p&gt;Beyond the novelty, this is a fun solve for a real workflow problem. When you’re running Claude Code on multiple projects at once, this gives you ambient awareness without constantly switching contexts.&lt;/p&gt;
&lt;p&gt;It’s also useful for demonstrations. When showing Claude Code to others, having a visual representation of what’s happening makes the AI’s work more tangible than watching terminal output scroll by.&lt;/p&gt;
&lt;h2&gt;Get It&lt;/h2&gt;
&lt;p&gt;The project is open source: &lt;a href=&quot;https://github.com/jaysonbrush/ai-hq&quot;&gt;github.com/jaysonbrush/ai-hq&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Setup takes about five minutes. Install dependencies, configure the Claude Code hooks, and you’re running.&lt;/p&gt;
</description>
      <pubDate>Wed, 04 Feb 2026 17:05:43 CST</pubDate>
      <dc:creator>Jayson Brush</dc:creator>
      <guid>https://www.jaysonbrush.com/2026/02/04/visualizing-claude-code-sessions/</guid>
    </item>
    <item>
      <title>The Strategic Pause</title>
      <link>https://www.jaysonbrush.com/2026/02/05/the-strategic-pause/</link>
      <description>&lt;p class=&quot;lead&quot;&gt;Leaders are rewarded for action. But the most important decisions often come from knowing when to stop moving and think.&lt;/p&gt;
&lt;p&gt;There is a reason that this topic resonates with me. When I’ve had the chance to step back from the day-to-day, it changes how I see where my time actually goes.&lt;/p&gt;
&lt;h2&gt;The Cost of Constant Motion&lt;/h2&gt;
&lt;p&gt;Modern leadership culture treats busyness as a virtue. Your calendar is packed, you’re responding to messages within minutes, you’re always available. The implicit message is that if you’re not moving, you’re falling behind.&lt;/p&gt;
&lt;p&gt;But constant motion has a cost. You lose the ability to anticipate because you’re too busy reacting. You stop noticing patterns because there’s no time to reflect on them. Original thinking requires quiet, and there isn’t any.&lt;/p&gt;
&lt;p&gt;The result is organizations that execute efficiently on the wrong things. Fast, but not going anywhere worth going.&lt;/p&gt;
&lt;h2&gt;Where Good Ideas Actually Come From&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;https://www.frontiersin.org/journals/human-neuroscience/articles/10.3389/fnhum.2014.00215/full&quot;&gt;Research&lt;/a&gt; on creativity consistently finds that insights don’t arrive during intense focus. They show up during breaks. In the shower. On a walk. During a commute where you’re not listening to anything.&lt;/p&gt;
&lt;p&gt;The problem is that in an always-on world, those moments barely exist anymore. Netflix fills the evening. Spotify fills the commute. Phone feeds and algorithms fill every gap in between. Our brains never get the unstructured time they need to make connections.&lt;/p&gt;
&lt;p&gt;Leaders who protect time for reflection make better strategic decisions. Not because they’re smarter, but because they’ve given their thinking room to develop.&lt;/p&gt;
&lt;h2&gt;Building the Pause Into Planning&lt;/h2&gt;
&lt;p&gt;Annual planning is where most organizations could benefit from slowing down. The typical approach is to pack the leadership team into a room, review last year’s numbers, set next year’s targets, and call it strategy.&lt;/p&gt;
&lt;p&gt;Our organization uses the &lt;a href=&quot;https://www.eosworldwide.com/&quot;&gt;EOS framework&lt;/a&gt;, and the quarterly and annual planning rhythms it creates are only as good as the thinking that goes into them. A better approach starts with space. Before diving into tactics, create room for bigger questions:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What assumptions are we making that might be wrong?&lt;/li&gt;
&lt;li&gt;What would we do differently if we were starting from scratch?&lt;/li&gt;
&lt;li&gt;What are we avoiding talking about?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These questions don’t have quick answers. They require sitting with discomfort, which is exactly why most planning sessions skip them.&lt;/p&gt;
&lt;h2&gt;Practical Tactics&lt;/h2&gt;
&lt;p&gt;A few things that have helped me:&lt;/p&gt;
&lt;p&gt;Get devices out of the room during strategic discussions. Not minimized, not on silent. Physically elsewhere. The temptation to check something “quickly” fragments attention in ways that kill deeper thinking.&lt;/p&gt;
&lt;p&gt;Start meetings with silence. Five to ten minutes, no agenda, no prompts. Let people’s minds settle before jumping into discussion. It feels awkward the first time. The quality of conversation that follows makes it worth it.&lt;/p&gt;
&lt;p&gt;Block time for thinking. Not “available if needed” time. Actually defended time with no purpose other than reflection. I aim for two hours a week minimum, though I don’t always hit it.&lt;/p&gt;
&lt;p&gt;I have found that walking meetings for discussions that need creative thinking rather than decisions work well. &lt;a href=&quot;https://news.stanford.edu/stories/2014/04/walking-vs-sitting-042414&quot;&gt;Movement helps cognition&lt;/a&gt;, and getting out of the conference room changes the dynamic.&lt;/p&gt;
&lt;h2&gt;The Discipline of Not Reacting&lt;/h2&gt;
&lt;p&gt;Pausing doesn’t come naturally to most leaders. The instinct is to respond, to fix, to act. Sitting with a problem feels like wasted time.&lt;/p&gt;
&lt;p&gt;But not every problem needs an immediate response. Some need time to clarify. Some resolve themselves. Some reveal their real nature only after the initial urgency fades.&lt;/p&gt;
&lt;p&gt;The discipline is recognizing which situations need action now and which need reflection first. Most leaders err toward action. Counterbalancing that bias takes conscious effort, and I’m still working on it.&lt;/p&gt;
&lt;h2&gt;Creating Space for Your Team&lt;/h2&gt;
&lt;p&gt;Your own reflection time matters, but so does your team’s. If you’re constantly pulling people into reactive mode, their strategic thinking suffers too.&lt;/p&gt;
&lt;p&gt;Look at your organization’s calendar. How much time is spent in meetings versus doing work versus thinking? Most organizations are meeting-heavy and thinking-light. That ratio shapes what’s possible.&lt;/p&gt;
&lt;p&gt;The goal isn’t to eliminate action. It’s to create enough space that when you do act, you’re acting on something worth acting on.&lt;/p&gt;
</description>
      <pubDate>Wed, 04 Feb 2026 18:15:07 CST</pubDate>
      <dc:creator>Jayson Brush</dc:creator>
      <guid>https://www.jaysonbrush.com/2026/02/05/the-strategic-pause/</guid>
    </item>
  </channel>
</rss>