<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Leadership Adaptation Radar</title>
    <link>https://tech-leadership.space/en/radar</link>
    <description>Evidence-backed signals for technical leaders, with confidence, role impact, and explicit review dates.</description>
    <language>en</language>
    <lastBuildDate>Wed, 12 Aug 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://tech-leadership.space/feeds/radar-en.rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Agentic SDLC is becoming an operating model</title>
      <link>https://tech-leadership.space/en/radar/agentic-sdlc-becomes-operating-model</link>
      <guid isPermaLink="true">https://tech-leadership.space/en/radar/agentic-sdlc-becomes-operating-model</guid>
      <description>The meaningful shift is not faster code completion. Teams are redesigning decomposition, review, quality gates and platform interfaces around parallel AI agents.

Why now: Coding agents now handle longer tasks and produce reviewable changes. The limiting factor moves from generation to context, verification and organizational adoption.

Status: Trial; Confidence: high; Review due: 2026-09-11.

Sources: OpenAI — Introducing Codex: https://openai.com/index/introducing-codex/; Stack Overflow 2025 Developer Survey — AI: https://survey.stackoverflow.co/2025/ai/</description>
      <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
      <category domain="status">Trial</category>
      <category domain="confidence">high</category>
      <category domain="capability">ai-enabled-engineering</category>
      <category domain="capability">delivery-reliability</category>
    </item>
    <item>
      <title>Cognitive load is an architecture input</title>
      <link>https://tech-leadership.space/en/radar/cognitive-load-is-an-architecture-input</link>
      <guid isPermaLink="true">https://tech-leadership.space/en/radar/cognitive-load-is-an-architecture-input</guid>
      <description>System boundaries and team boundaries should be evaluated together. Excess coordination and ownership ambiguity are architectural signals, not merely process problems.

Why now: Reorganizations and platform initiatives often optimize the org chart while leaving interaction load and unclear boundaries untouched.

Status: Trial; Confidence: medium; Review due: 2026-11-10.

Sources: Team Topologies — Key Concepts: https://teamtopologies.com/key-concepts; Martin Fowler — Conway&apos;s Law: https://martinfowler.com/bliki/ConwaysLaw.html</description>
      <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
      <category domain="status">Trial</category>
      <category domain="confidence">medium</category>
      <category domain="capability">architecture-org-design</category>
      <category domain="capability">adaptive-leadership</category>
    </item>
    <item>
      <title>Engineering productivity needs a measurement system</title>
      <link>https://tech-leadership.space/en/radar/engineering-productivity-needs-a-measurement-system</link>
      <guid isPermaLink="true">https://tech-leadership.space/en/radar/engineering-productivity-needs-a-measurement-system</guid>
      <description>No single metric represents engineering performance. Useful measurement combines delivery outcomes, developer experience and qualitative interpretation.

Why now: AI adoption has renewed pressure to prove productivity gains, making metric misuse and local optimization more likely.

Status: Adopt; Confidence: high; Review due: 2026-11-10.

Sources: ACM Queue — The SPACE of Developer Productivity: https://queue.acm.org/detail.cfm?id=3454124; DORA Research: https://dora.dev/research/</description>
      <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
      <category domain="status">Adopt</category>
      <category domain="confidence">high</category>
      <category domain="capability">delivery-reliability</category>
      <category domain="capability">decision-quality</category>
    </item>
    <item>
      <title>Platform engineering is moving from portal to product</title>
      <link>https://tech-leadership.space/en/radar/platform-engineering-from-portal-to-product</link>
      <guid isPermaLink="true">https://tech-leadership.space/en/radar/platform-engineering-from-portal-to-product</guid>
      <description>A developer portal is not the outcome. Strong platforms reduce cognitive load through paved paths, explicit service levels and continuous discovery with internal users.

Why now: Platform programs are maturing, while AI increases demand for governed self-service context, environments and delivery controls.

Status: Adopt; Confidence: high; Review due: 2026-11-10.

Sources: CNCF Platforms White Paper: https://tag-app-delivery.cncf.io/whitepapers/platforms/; Google Cloud DORA — Platform engineering: https://cloud.google.com/architecture/devops/devops-tech-platform-engineering</description>
      <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
      <category domain="status">Adopt</category>
      <category domain="confidence">high</category>
      <category domain="capability">architecture-org-design</category>
      <category domain="capability">technical-strategy</category>
    </item>
  </channel>
</rss>
