BergLabs Field Notes · Monthly

Field Notes from the operating layer.

Each issue sets one AI failure against one that worked and names the design choice between them. Every claim is sourced, and every issue is published here as readable text as well as a LinkedIn carousel.

Issue anatomyFailure · Mechanism · Fix · Proof
  1. 01Case in pointA failure in the news
  2. 02Why it happensThe mechanism
  3. 03The fixOne design choice
  4. 04Proof pointOne that worked
  5. 05Term explainedOne AI term
  6. 06Fact-checked2+ named sources
Illustrative diagram. Every issue follows the same structure across 15 slides, then gets published here as text.
  • Case in point

    One AI failure from the last three months.

  • Proof point

    One deployment that got it right.

  • Term explained

    One AI term, defined in plain words.

Issues

The latest issues.

  • Issue 02 · October 2026

    Voice at the front door.

    BergLabs Field Notes15 slides
    Case in point · Proof point · Term: shadow mode

    The phone line is the cheapest place to start enterprise AI and the most expensive place to get it wrong. One AI receptionist that locked a patient out, one police line that cleared its queue, and the routing rule that separates them.

    Read Issue 02
  • Issue 01 · September 2026

    The human in the loop.

    BergLabs Field Notes15 slides
    Case in point · Proof point · Term: human in the loop

    One AI failure that made the news for the wrong reasons, one that did not, and the single design choice that explains both: a supervision layer between the model’s output and the customer’s outcome.

    Read Issue 01 on LinkedIn

Human in the Loop

The video series behind the notes.

Short walkthroughs of how the work is made, checked and kept on the record.

  • Video 01

    From a robot take to a trainable feed

    Why robot policies stall between capture and training, and how a managed queue closes the gap.

    Plays from LinkedIn, which may set its own cookies. Watch on LinkedIn

  • Video 02

    Who made this label, and who checked it?

    One BergFlow project from setup to batch upload, the annotator queue, reviewer decisions and QC sampling.

    Plays from LinkedIn, which may set its own cookies. Watch on LinkedIn

Articles

Long-form notes between issues.

Every article from the BergLabs editorial archive, newest first. Filter by the work it describes or search by workflow.

Showing 44 of 44 articles

About the series

What Field Notes is.

A monthly issue on enterprise workflow automation and AI transformation in 2025 and 2026.

Get each issue by email: write to partnerships@berglabs.ai with “Field Notes” in the subject line.

Each issue also runs on LinkedIn as a carousel, alongside our Human in the Loop video series.

  1. 01Public cases and our own work

    Some issues analyse recent public workflows against named sources; others turn what we have seen in BergLabs delivery work into a note. Single-source figures are labelled.

  2. 02One mechanism, explained

    The failure and the success are chosen because one design choice separates them. The issue explains that choice, then shows where it runs in BergAuto and BergFlow.

  3. 03Published as text

    The carousel goes out on LinkedIn; the full issue is published here as text, with every source line, so it can be read, searched and cited.

Questions

Questions about Field Notes

What it is, how it is checked and how to get it.

Field Notes

What is BergLabs Field Notes?

A monthly issue on enterprise workflow automation and AI transformation. Each one sets an AI failure against one that worked, drawn from public cases or from BergLabs delivery work, and explains the design choice between them. Issues run on LinkedIn and as text on this page.

How are stories chosen and checked?

From two places: recent public cases, checked against two or more independent named sources where possible, and BergLabs delivery work, described without naming clients. Figures that rest on one source are labelled.

Turn the lesson into a pilot.

Every issue ends in the same place: one workflow, scored, reviewed and measured.