<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Wes West</title>
    <link>https://weswest.ai/</link>
    <description>Recent content on Wes West</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 14 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://weswest.ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Contracts Are Load-Bearing Infrastructure, Not Documentation</title>
      <link>https://weswest.ai/writing/contracts-skeleton/</link>
      <pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/contracts-skeleton/</guid>
      <description>This is the fifth article in a series on running an eight-agent AI coding team. Across the first four articles, a single design philosophy keeps surfacing: define one structural path for the system to succeed, then make it difficult to deviate from that path. Everything else is fault tolerance.
Three principles have emerged so far:
Make wrong behavior structurally impossible, not just discouraged. Agents run in physically isolated worktrees so they can&amp;rsquo;t see each other&amp;rsquo;s in-progress work.</description>
    </item>
    
    <item>
      <title>One Agent&#39;s Entire Job Is Auditing the Other Seven</title>
      <link>https://weswest.ai/writing/self-auditing-system/</link>
      <pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/self-auditing-system/</guid>
      <description>The first three articles in this series described a system: seven domain-specialist agents and a manager, a three-layer enforcement model keeping them in bounds, and a sprint cycle that coordinates their work. What none of them addressed is what happens when an agent follows all the rules and still writes bad code. Not broken code — code that passes tests and respects every boundary. Just code that&amp;rsquo;s inconsistent, poorly documented, or quietly drifting from conventions nobody explicitly checks.</description>
    </item>
    
    <item>
      <title>A Complete Sprint Cycle Runs in an Afternoon. I Spend Most of It on Proposals.</title>
      <link>https://weswest.ai/writing/sprint-cycle-walkthrough/</link>
      <pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/sprint-cycle-walkthrough/</guid>
      <description>My last two articles — It&amp;rsquo;s Just Microservices and Team Management and Policy Enforcement for Agentic Workflows — documented how I set up an eight-agent AI coding team: seven domain specialists and a manager, each operating in isolated workspaces with layered enforcement keeping them in bounds. In this article, I share how these agents coordinate through a sprint cycle — and how I spend nearly all of my time on one tiny but sacred sliver.</description>
    </item>
    
    <item>
      <title>Policy Enforcement for Agentic Workflows</title>
      <link>https://weswest.ai/writing/policy-enforcement-agentic-workflows/</link>
      <pubDate>Tue, 24 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/policy-enforcement-agentic-workflows/</guid>
      <description>Agentic AI is a management problem. Most people have never managed others&amp;rsquo; work — never had to set someone else&amp;rsquo;s objectives, define best practices, verbalize exactly what &amp;ldquo;success&amp;rdquo; and &amp;ldquo;failure&amp;rdquo; look like, implement an organizational structure, and then quality-control the output. That&amp;rsquo;s the new skill, and most of the field is trying to skip it.
I wrote about this more broadly in AI Makes Everyone a Manager. This article is the specific version: how I set up guardrails for my AI coding team, and why it looks exactly like goals-oriented management.</description>
    </item>
    
    <item>
      <title>It&#39;s Just Microservices and Team Management</title>
      <link>https://weswest.ai/writing/multi-agent-microservice/</link>
      <pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/multi-agent-microservice/</guid>
      <description>I&amp;rsquo;m running an all-AI team of seven programmers and a manager. I provide guidance, strategic direction, and surgical intervention; the seven programmers handle their workloads; the manager coordinates. It works really well.
Why does it work so well? The short version: I didn&amp;rsquo;t invent anything. I just noticed that an agentic coding team is both a software architecture problem and a team management problem at the same time, and applied known best practices from both.</description>
    </item>
    
    <item>
      <title>The Complexity Tax: Why We Build Models We&#39;ll Never Deploy</title>
      <link>https://weswest.ai/writing/complexity-tax/</link>
      <pubDate>Mon, 02 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/complexity-tax/</guid>
      <description>Originally published at Nomis Solutions
A neural network achieves 0.82 AUC. The logistic regression gets 0.72. The gap between them is what we call the complexity tax — the accuracy you sacrifice when you choose interpretability over raw predictive power. This article explains why we routinely build models we know will never hit production, and how doing so leads to better conversations with the C-suite about what to actually deploy.</description>
    </item>
    
    <item>
      <title>Building a Voice-Enabled Mortgage Assistant in Four Hours: A Lesson in Compound AI Systems</title>
      <link>https://weswest.ai/writing/voice-enabled-mortgage-assistant/</link>
      <pubDate>Thu, 14 Aug 2025 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/voice-enabled-mortgage-assistant/</guid>
      <description>Originally published on Nomis Solutions
Sometimes the most valuable projects are the ones you don&amp;rsquo;t pursue. Our team built a voice-enabled mortgage application system in just four hours, then decided not to take it to production. The lessons about compound AI systems proved more valuable than the prototype.
Key Topics:
Building compound AI systems by orchestrating specialized tools Technical architecture: Whisper, GPT-3.5, voice activity detection, and text-to-speech Five critical engineering decisions for natural conversation interfaces Why we didn&amp;rsquo;t ship: customization, voice quality, error handling, and integration challenges Knowing when to prototype, learn, and move on </description>
    </item>
    
    <item>
      <title>How AI Enhances Recommendation Engines by Combining Models and Judgment</title>
      <link>https://weswest.ai/writing/ai-recommendation-engines/</link>
      <pubDate>Thu, 24 Jul 2025 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/ai-recommendation-engines/</guid>
      <description>Originally published on Nomis Solutions
Most recommendation systems provide binary responses: approve or deny, raise rates or lower them. This article demonstrates how AI can provide nuanced decision support that goes far beyond simple yes/no recommendations.
Key Topics:
Limitations of traditional rule-based recommendation systems How AI provides arguments for and against each decision Generating creative alternative solutions beyond predetermined options Contextual insights that adapt to unique circumstances Combining quantitative models with qualitative judgment The evolution from recommendation engines to AI business analysts </description>
    </item>
    
    <item>
      <title>AI Makes Everyone a Manager: The Overlooked Challenge this Presents</title>
      <link>https://weswest.ai/writing/ai-makes-everyone-a-manager/</link>
      <pubDate>Fri, 11 Jul 2025 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/ai-makes-everyone-a-manager/</guid>
      <description>Originally published on Nomis Solutions
Millions of knowledge workers just became managers overnight. They don&amp;rsquo;t know it yet, and that&amp;rsquo;s precisely why so many AI initiatives are failing. This article explores why AI tools require management skills, not technical skills.
Key Topics:
Why AI tools behave like team members, not calculators The critical management skills needed for effective AI usage Setting clear expectations and providing appropriate context Giving constructive feedback to improve AI outputs Building organizational capacity for AI adoption </description>
    </item>
    
    <item>
      <title>How AI Accelerates Data Analysis without Replacing Analysts</title>
      <link>https://weswest.ai/writing/accelerate-data-analysis/</link>
      <pubDate>Fri, 27 Jun 2025 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/accelerate-data-analysis/</guid>
      <description>Originally published on Nomis Solutions
The debate about AI in banking often frames it as a choice: humans or machines. This article demonstrates how combining AI&amp;rsquo;s data processing capabilities with analyst expertise creates superior outcomes.
Key Topics:
Moving beyond reactive chatbots to proactive AI intelligence The critical importance of domain-specific banking knowledge in AI systems How AI can scan thousands of data points to surface patterns and anomalies Practical examples of AI-augmented analysis in deposit pricing and portfolio management The irreplaceable role of human judgment in strategic decision-making Building effective human-AI collaboration workflows </description>
    </item>
    
    <item>
      <title>How We&#39;re Actually Using AI at Nomis: A Pragmatic Approach to an Overhyped Technology</title>
      <link>https://weswest.ai/writing/pragmatic-approach-to-ai/</link>
      <pubDate>Wed, 18 Jun 2025 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/pragmatic-approach-to-ai/</guid>
      <description>Originally published on Nomis Solutions
Most AI projects fail due to overpromising and unrealistic expectations. This article outlines Nomis&amp;rsquo;s pragmatic approach to AI implementation, focusing on practical applications that create measurable value.
Key Topics:
Why most AI projects fail and how to avoid common pitfalls Three core AI use cases: data analysis, recommendation engines, and decision support The reality of AI implementation: augmenting rather than replacing human judgment Measuring ROI and demonstrating tangible business value </description>
    </item>
    
    <item>
      <title>Executive Recap: Key Takeaways from FIS Emerald 2025</title>
      <link>https://weswest.ai/writing/fis-emerald-2025-recap/</link>
      <pubDate>Thu, 29 May 2025 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/fis-emerald-2025-recap/</guid>
      <description>Originally published on Nomis Solutions
FIS Emerald 2025 highlighted a critical gap in banking&amp;rsquo;s AI journey: while 85% of banks believe generative AI will transform the industry, only 10% have concrete implementation roadmaps. This recap examines how to close that gap.
Key Topics:
The AI adoption challenge: belief vs. execution Data privacy, security, and regulatory concerns in banking AI Practical AI implementation strategies for financial institutions Building trust through transparency and explainability Creating actionable AI roadmaps for banking organizations </description>
    </item>
    
    <item>
      <title>U.S. Deposits and the Critical Lessons on Deposit Betas</title>
      <link>https://weswest.ai/writing/deposit-betas-lessons/</link>
      <pubDate>Mon, 13 Jan 2025 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/deposit-betas-lessons/</guid>
      <description>Originally published on LinkedIn
The 2022-2023 rate cycle taught the banking industry an expensive lesson about deposit betas. This analysis examines why actual deposit cost sensitivity far exceeded forecasts and provides a framework for improving future predictions.
Key Topics:
Understanding deposit beta fundamentals and measurement Why banks systematically underestimated deposit betas (20-30% forecasts vs. 50-60% reality) The role of digital banking, competitive dynamics, and customer sophistication Practical approaches to improving deposit beta forecasting Implications for balance sheet planning and NIM management </description>
    </item>
    
    <item>
      <title>Adapting to Rate Cuts: Strategic Deposit Expense Management</title>
      <link>https://weswest.ai/writing/adapting-to-rate-cuts/</link>
      <pubDate>Wed, 18 Sep 2024 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/adapting-to-rate-cuts/</guid>
      <description>Originally published on LinkedIn
In the immediate aftermath of the Federal Reserve&amp;rsquo;s 50 basis point rate cut, financial institutions face unprecedented challenges in managing deposit expenses in a falling rate environment. This article examines how banks can navigate this transition strategically.
Key Topics:
Analysis of deposit beta forecasting failures during the 2022-2023 rate cycle First mover vs. fast follower strategic considerations Managing CD and promotional product maturities Identifying and differentiating rate-sensitive vs.</description>
    </item>
    
    <item>
      <title>Banks Should Pursue Efficient and Scalable &#39;Model Factory&#39; Management</title>
      <link>https://weswest.ai/writing/model-factory-management/</link>
      <pubDate>Fri, 01 Jun 2018 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/model-factory-management/</guid>
      <description>Publication: Novantas Review (Summer 2018) Co-authors: Steve Turner, Kaushik Deka
As banks struggle to manage hundreds of models requiring increasing resources, this article proposes using sophisticated technology, including machine learning, to automate the model management process.</description>
    </item>
    
    <item>
      <title>Rethinking the Modeling Ecosystem: A Modest Proposal</title>
      <link>https://weswest.ai/writing/rethinking-modeling-ecosystem/</link>
      <pubDate>Tue, 01 Aug 2017 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/rethinking-modeling-ecosystem/</guid>
      <description>Publication: Novantas Perspective (August 2017) Co-authors: Ryan Schulz, Steve Turner
For banks in many countries the current model development and validation process is broken: it takes too long, there are too many nonstandard elements, there is too much rework, and it introduces material risk when critical models fail validation.</description>
    </item>
    
    <item>
      <title>Improving Usefulness of PPNR CCAR Stress Test Models: Adding 30&#43; Years of Rate Data</title>
      <link>https://weswest.ai/writing/cd-share-deposit-models/</link>
      <pubDate>Thu, 01 Sep 2016 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/cd-share-deposit-models/</guid>
      <description>Publication: Novantas Perspective (September 2016) Co-authors: Jane Lim, Ryan Schulz
To address the data shortcoming that many banks lack sufficiently long internal monthly history covering multiple rate cycles, Novantas uses the time deposit share of total interest-bearing deposit balances (&amp;ldquo;CD-Share&amp;rdquo;) as an independent industry variable in deposit balance models.</description>
    </item>
    
    <item>
      <title>Forecasting Percentage Growth: Do Your Dependent Variable Transformations Make Sense?</title>
      <link>https://weswest.ai/writing/forecasting-percentage-growth/</link>
      <pubDate>Tue, 10 May 2016 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/forecasting-percentage-growth/</guid>
      <description>Publication: Novantas Perspective (May 2016) Co-authors: Sean Wallace, Ryan Schulz
One of the most common transformations of the dependent variable in PPNR Stress Testing is to predict growth in balances, revenue, and expenses from period to period. This article outlines why the preferred transformation is a logarithmic one (diff-log), as opposed to percentage change.</description>
    </item>
    
    <item>
      <title>2017 CCAR PPNR Planning: Eight Things to Worry About Right Now</title>
      <link>https://weswest.ai/writing/2017-ccar-planning/</link>
      <pubDate>Tue, 12 Apr 2016 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/2017-ccar-planning/</guid>
      <description>Publication: Novantas Perspective (April 2016) Co-authors: Pete Gilchrist, Ryan Schulz, Sean Wallace
With 2016 CCAR submitted and the cycle shortened from 15 to 12 months, this article highlights the eight most critical immediate steps toward a successful 2017 submission.</description>
    </item>
    
    <item>
      <title>Modeling Deposit Portfolio Rates: Combining Replicating Portfolio Concepts with Regression Analysis</title>
      <link>https://weswest.ai/writing/deposit-rate-modeling/</link>
      <pubDate>Tue, 15 Mar 2016 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/deposit-rate-modeling/</guid>
      <description>Publication: Novantas Perspective (March 2016) Co-authors: Greg Muenzen, Steve Turner, Pete Gilchrist
PPNR and ALM modeling teams know that the bar for deposit rate modeling has risen. This article explains the Novantas regression-based approach and compares its performance to beta and replicating portfolio techniques.</description>
    </item>
    
    <item>
      <title>Avoiding PPNR Model Mis-Specification from Spurious Correlation Failures</title>
      <link>https://weswest.ai/writing/spurious-correlation-failures/</link>
      <pubDate>Tue, 01 Mar 2016 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/spurious-correlation-failures/</guid>
      <description>Publication: Novantas Perspective (March 2016)
This article describes a bug in the SAS PROC AUTOREG procedure discovered during 2015 PPNR model development: models with no serial correlation fail the Godfrey serial correlation test when also performing certain stationarity tests.</description>
    </item>
    
    <item>
      <title>CCAR PPNR Modeling</title>
      <link>https://weswest.ai/writing/ccar-ppnr-modeling/</link>
      <pubDate>Sat, 01 Nov 2014 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/writing/ccar-ppnr-modeling/</guid>
      <description>Publication: Novantas Review, Vol 5, No 3 (November 2014) Co-authors: Andrew Frisbie
Improved modeling for pre-provision net revenue requires strengthening the project framework, working to overcome data sterility and testing alternative approaches. This article addresses the paradox that even as banks improve their competency in PPNR modeling, many institutions are shifting toward an increasingly similar and rigid approach to satisfy statistical tests, exposing banks to business line disconnect and systemic risk.</description>
    </item>
    
    <item>
      <title>Search Results</title>
      <link>https://weswest.ai/search/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://weswest.ai/search/</guid>
      <description>This file exists solely to respond to /search URL with the related search layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs, jquery and mark.js
Initial setup Search depends on additional output content type of JSON in config.toml
[outputs] home = [&amp;#34;HTML&amp;#34;, &amp;#34;JSON&amp;#34;] Searching additional fileds To search additional fields defined in front matter, you must add it in 2 places.</description>
    </item>
    
  </channel>
</rss>
