proomt

Search

Search posts, papers, and topics

All posts

HoneycombIleanell Perez5 min readintermediate

How I Support Humans in the AI Era

Summary

An engineering manager shares her approach to integrating AI tools into her team's workflow by creating dedicated spaces for connection, collaboration, and discussion, rather than imposing new policies. This strategy fostered psychological safety and autonomy, allowing the team to organically explore and define their own AI norms and practices.

  • Prioritize creating dedicated spaces for human connection and collaboration over new AI policies.
  • Repurpose existing meeting times for AI experimentation and knowledge sharing, like 'AI Innovation Time'.
  • Grant teams autonomy to define their own AI norms and experiment with tools, fostering psychological safety.
  • Good management practices, such as structured freedom and open discussion, are amplified by AI adoption.

Engineering managers can learn practical, human-centric strategies for integrating AI tools into team workflows while preserving connection and fostering autonomy.

6/10

Related reading

  1. 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
  2. Podcast: Signals and Levers: Building Thriving Engineering Organizations

    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.

    InfoQinfoq.com31 mintalk
  3. 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
  4. Use Curiosity, Craft, and Care to Decide What AI Should Write

    The post proposes a three‑principle framework—Curiosity, Craft, and Care—to decide how much AI should author each artifact in a software development workflow. It argues that AI can be used aggressively for exploratory, disposable outputs (Curiosity) but should be limited for artifacts that commit the team to decisions (Craft) and for communications that require personal ownership (Care). The auth…

    Atomic Objectatomicobject.com4 min
  5. AI Norms & Values, Part 2 of 3: AI for Honeycomb Engineering

    Honeycomb’s engineering leadership outlines why the org is “all‑in” on AI, sets a north‑star to be in the top 10 % AI‑enabled teams, and publishes concrete 2026 goals (e.g. 25 % of PRs auto‑merged by AI with <3 % failure) plus an FAQ covering support, measurement, agent usage, and coping with workflow changes.

    Honeycombhoneycomb.io8 min