proomt

Search

Search posts, papers, and topics

All posts

InfoQElisabeth Hendrickson, Joel Tosi31 min readtalkintermediate

Podcast: Signals and Levers: Building Thriving Engineering Organizations

Read on infoq.com

Summary

The podcast explains how systems thinking helps leaders grasp the complex, adaptive nature of software delivery, especially as AI rollouts amplify bottlenecks. It also outlines cultural "levers"—choices that shape unwritten rules—to build sustainable, fun engineering teams.

  • Treat engineers as adults; avoid micromanaging smart hires.
  • View the organization as an adaptive, non‑linear system where changes ripple throughout.
  • AI rollouts amplify existing bottlenecks, leading to far more code and bugs; prepare downstream processes.
  • Culture is the unwritten rules; any choice that affects those rules is a lever you can pull.

Leaders navigating AI‑driven change and aiming to build thriving engineering organizations should understand systems thinking and how to intentionally shape culture.

5/10
aiengineering culturesystems thinkingleadershipculture

Related reading

  1. AI Skills with Matt Pocock

    Matt Pocock explains how he uses AI agents for software development, emphasizing "strategic programming" and guiding agents with "leading words" from classic engineering texts. He argues that this approach makes engineering fundamentals more critical than ever for creating agent-optimized codebases.

    The Pragmatic Engineerpragmaticengineer.com7 min

  2. Article: Beyond Relevance: A Governance-First Architecture for Enterprise Personalization

    The article proposes a governance‑first architecture for enterprise personalization, where policy‑driven steps (memory, journey graph, AI routing, scoring, trust checks, outcome simulation) shape the recommendation before it is returned. A reference FastAPI implementation demonstrates the pattern with external YAML policies and optional LLM assistance.

    InfoQinfoq.com19 min

  3. Every tool is green. Can you ship?

    A CloudBees blog post argues that existing CI, security, and QA tools don’t give release managers a complete view of AI‑generated code risk. It claims tool consolidation rarely helps and proposes a “control plane” (CloudBees Unify) that aggregates signals from multiple tools and adds AI‑driven test prioritization. The piece is largely promotional, with no concrete implementation details, metrics,…

    Codeshipcloudbees.com4 min

  4. From Individual Experiments to a Shared AI Practice: How Avant Scaled AI-Assisted Engineering

    Avant replaced many personal AI‑assistant setups with a single, organization‑wide Claude Code configuration that embeds the company’s coding standards, project‑tracking links, and documentation. Treated as an internal product, the setup is versioned, owned by delivery engineers, and iteratively improved. The shared tool speeds routine tasks (scaffolding, tests, migrations, docs) and enforces cons…

    Moove-itqubika.com2 min

  6. Quoting voxium

    A new engineer observes that a big company's reliance on AI for all artifacts (code, specs, tickets) leads to human bottlenecks. Despite AI generating everything, engineers work long hours because nobody understands the output, making the team slow.

    Simon Willisonsimonwillison.net1 min