<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[ChainTech Brief]]></title><description><![CDATA[Weekly analysis of how technology is reshaping supply chains]]></description><link>https://www.chaintechbrief.com</link><image><url>https://substackcdn.com/image/fetch/$s_!HvVi!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa8d49de3-4b92-4e87-9444-07c0ab69fcf2_256x256.png</url><title>ChainTech Brief</title><link>https://www.chaintechbrief.com</link></image><generator>Substack</generator><lastBuildDate>Wed, 28 Oct 2026 21:07:43 GMT</lastBuildDate><atom:link href="https://www.chaintechbrief.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[ChainTech Brief]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[chaintechbrief@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[chaintechbrief@substack.com]]></itunes:email><itunes:name><![CDATA[Sogo Adeleke]]></itunes:name></itunes:owner><itunes:author><![CDATA[Sogo Adeleke]]></itunes:author><googleplay:owner><![CDATA[chaintechbrief@substack.com]]></googleplay:owner><googleplay:email><![CDATA[chaintechbrief@substack.com]]></googleplay:email><googleplay:author><![CDATA[Sogo Adeleke]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Welcome to ChainTech Brief!]]></title><description><![CDATA[Weekly analysis of how technology is reshaping supply chains]]></description><link>https://www.chaintechbrief.com/p/welcome-to-chaintech-brief</link><guid isPermaLink="false">https://www.chaintechbrief.com/p/welcome-to-chaintech-brief</guid><dc:creator><![CDATA[Sogo Adeleke]]></dc:creator><pubDate>Mon, 21 Sep 2026 22:33:25 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!SS77!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!SS77!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!SS77!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png 424w, https://substackcdn.com/image/fetch/$s_!SS77!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png 848w, https://substackcdn.com/image/fetch/$s_!SS77!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png 1272w, https://substackcdn.com/image/fetch/$s_!SS77!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!SS77!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png" width="1456" height="1050" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/f8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1050,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:2317426,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.chaintechbrief.com/i/216539718?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!SS77!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png 424w, https://substackcdn.com/image/fetch/$s_!SS77!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png 848w, https://substackcdn.com/image/fetch/$s_!SS77!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png 1272w, https://substackcdn.com/image/fetch/$s_!SS77!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff8c28f1b-11ac-4376-bb85-05379946e00e_1477x1065.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button tabindex="0" type="button" class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Hi, welcome to ChainTech Brief.</p><p>I&#8217;ve worked in supply chain and operations for more than 12 years, and one thing that&#8217;s become obvious is how much the field now depends on technology.</p><p>Whether you work in procurement, manufacturing, planning, inventory, or logistics, there&#8217;s probably a system somewhere helping you track information, talk to suppliers, analyze data, or make decisions. That part isn&#8217;t new.</p><p>What&#8217;s different now is the pace. There&#8217;s always a new AI tool being announced, a startup raising money, an established company adding a capability, or one company buying another. It&#8217;s hard to keep up.</p><p>And even when you do hear about something new, you&#8217;re still left with questions. Does this actually solve a real problem? Where would it fit inside an existing supply chain? Who would actually use it, and is it worth paying attention to or mostly hype?</p><p>Those are the questions I find myself asking. ChainTech Brief is my way of working through them, forming my own opinions, and sharing what I learn.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.chaintechbrief.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption"></p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h1>Why I Started ChainTech Brief</h1><p>There&#8217;s no shortage of supply chain technology news. Most coverage does a good job telling you what happened: a company raised funding, a product launched, an acquisition closed, a regulation was introduced.</p><p><strong>But knowing what happened doesn&#8217;t tell you why it matters.</strong></p><p>Say a company announces a new platform that promises better planning or lower costs. That sounds great, but what would a company actually need in place before it could work? Would the data be reliable enough? Would employees use it? Would it fit existing workflows, or force people to change how they work? And after all that, would the benefit be worth the cost and disruption?</p><p>Those questions are usually more interesting to me than the announcement itself.</p><p>The news still matters, and you need the facts before you can form an opinion. But it&#8217;s only the starting point. What I want to understand is what a development could actually mean for the people and companies working inside supply chains, and that&#8217;s the purpose of this publication.</p><p>I&#8217;m not trying to cover every story or become another breaking-news outlet. There&#8217;s too much happening for that, and not every announcement deserves a full article. Instead, I want to pick one development a week, slow it down, and take a real look at it.</p><h1>Who ChainTech Brief Is For</h1><p>This is mainly for people who work in or around supply chains and want to understand the technology changing the field.</p><p>If you work in procurement, sourcing, manufacturing, planning, inventory, logistics, analytics, or operations, what&#8217;s being introduced today could eventually affect how you do your job, what skills companies value, what information you have access to, and how decisions get made.</p><p>It&#8217;s also for people building supply chain technology. Founders, operators, product teams, and marketers usually understand their own product, but they also need to understand the environment it&#8217;s going into.</p><p>Supply chains can be messy. Data isn&#8217;t always clean. Different teams use different systems, and a tool often has to work across several departments before it delivers the value being promised. Sometimes the problem isn&#8217;t whether the technology works. It&#8217;s whether the organization is ready to use it.</p><p>Business and operational leaders responsible for evaluating technology, improving processes, managing risk, or deciding where to invest may find this useful too. The common thread is simple: understanding what&#8217;s changing and figuring out what actually deserves a closer look.</p><h1>What You Can Expect Every Week</h1><p>Each week I&#8217;ll pick one development in supply chain technology and look beyond the headline. It could be a new product, an acquisition, a funding round, a regulatory change, or a bigger shift happening across the market.</p><p>The topic will change week to week, but I&#8217;ll generally be digging into the same four things:</p><ul><li><p><strong>What happened</strong> &#8212; what was announced, and what background you need to understand it</p></li><li><p><strong>Why it matters</strong> &#8212; whether it&#8217;s a meaningful development or just another announcement</p></li><li><p><strong>Where it could fit</strong> &#8212; how it might actually work inside a supply chain, and what would make adoption easier or harder</p></li><li><p><strong>What to watch next</strong> &#8212; what would show it&#8217;s gaining real traction</p></li></ul><p>Some weeks I&#8217;ll write about AI or automation. Other weeks it&#8217;ll be procurement technology, planning systems, manufacturing, logistics, cybersecurity, funding, or M&amp;A. I don&#8217;t want to force every story into the same conclusion, some technologies will turn out more promising than they first look, others will get plenty of attention without solving a problem companies actually care enough about.</p><p>The goal is to look at the available information, ask practical questions, and come to my own conclusion. When I come across a report, article, or podcast that adds something useful, I&#8217;ll pass that along too.</p><h1>A Little About Me</h1><p>I&#8217;m a supply chain and operations professional with more than 12 years of experience across consulting, healthcare, manufacturing, procurement, analytics, and process improvement.</p><p>My career hasn&#8217;t been limited to one corner of the supply chain but rather across the end-to-end supply chain. I&#8217;ve worked on spend analysis, sourcing, inventory, logistics, supplier relationships, cost reduction, and operational improvement.</p><p>I currently work at Vizient, supporting the supply chain operations of a large regional health system. Before that, I worked in supply chain and operations consulting at PwC and Deloitte, and in procurement and inventory management at Patton Electronics. I hold a Master of Science in Business with a supply chain focus from the University of Maryland, and I&#8217;m a Certified Supply Chain Professional (CSCP) and SCOR Professional.</p><p>Working in healthcare supply chain has given me a sharper sense of the gap between a technology sounding useful and actually being useful. A tool still has to work with the data you actually have. It has to fit the operation you actually run. The people expected to use it have to understand and trust it. That&#8217;s usually where good ideas run into trouble.</p><p><strong>I&#8217;m not writing this because I have every answer. I don&#8217;t.</strong></p><p>I&#8217;m writing it because I want to understand this part of the field better, and writing gives me a reason to slow down, research something properly, think through the implications, and explain what I actually believe. It also leaves me a record of how my thinking changes over time.</p><p>If I can get sharper on supply chain technology while helping other people make sense of it too, that&#8217;s a good use of my time.</p><h1>Subscribe to ChainTech Brief</h1><p>If this sounds useful, subscribe. Every week you&#8217;ll get one focused look at a development in supply chain technology: what happened, why it matters, where it could fit, and what to watch next.</p><p>If there&#8217;s a technology, company, or industry development you think deserves a closer look, reply or leave a comment. I may not get to every suggestion, but I&#8217;ll read them, and some will turn into future editions.</p><p>Thanks for being here. Looking forward to seeing where this goes.</p><p><em>ChainTech Brief is an independent publication. The views expressed here are my own and do not represent or imply endorsement by my current or former employers.</em></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.chaintechbrief.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading ChainTech Brief! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item></channel></rss>