Operating Notes

Operating Notes · by the Chief Executive Officer of Flobotics

How we build a company that executes.

On leadership, teams, ownership and the operating systems that turn good technology into outcomes. Published monthly, revised in public when we learn something.

The CEO

Builds the teams and systems behind every Flobotics deployment · 38 people · 7 client pods

Featured essay 14 Sep 2026 12 min read Culture · Company design

Culture is an operating system, not a list of values

Values describe what we hope people will do. An operating system decides what actually happens on a busy Tuesday.

Every company I have worked with had values on a wall. Most of them were good values. None of them decided anything. When a client system failed at 6:40 in the morning, nobody looked at the wall. They looked at who owned the system, what the runbook said and whether anyone was allowed to pause it.

That is culture: not what we say, but the defaults that run when nobody is deciding. At Flobotics we treat it like software. It has layers. It has owners. It gets versioned, and when a layer is broken, we fix the layer instead of giving a speech.

"If you want to know a company's culture, do not read its values. Watch what happens when something breaks."

Valueswhat we say
← most companies stop here
Principleshow we decide
6, numbered, revised yearly
Ritualswhen we meet
4 per week, each with an owner
Metricswhat we look at
11 numbers, one page, weekly
Defaultswhat happens when nobody decides
← this is the culture

Figure: the culture stack. Wider means more of daily life is decided at that layer.

Continue reading →
Leadership notesShort, weekly, numbered

Things I wrote down this month.

Short notes from running the company. Some become principles. Most stay notes.

Note 034 · 18 Sep

If two people think they own it, nobody does.

Ownership
Note 033 · 11 Sep

A meeting without a written pre-read is a meeting where the loudest idea wins.

Meetings
Note 032 · 04 Sep

The best feedback I got this quarter came in a pull request, not a review.

Feedback
Note 031 · 28 Aug

Speed is a property of the system. Heroics are a sign it is broken.

Execution
Note 030 · 21 Aug

We now end every client review with one question: what would you stop paying us for?

Clients
Culture principlesVersion 3 · revised 2026-06-30

Six principles, each with a way to check it.

A principle without a check is a value. Each of ours says how we would know we are breaking it. The numbers matter: the team refers to them by number.

01

One process, one owner, one number.

Every client process has exactly one named owner and one metric that says whether it is healthy.

CheckOwnership map has no system with two solid lines
02

Write it down before we meet.

Decisions start as a one-page pre-read. The meeting is for disagreement, not for reading.

CheckShare of decision meetings with a pre-read: 94%
03

Disagree in the room, commit outside it.

Challenge is expected from everyone, including the newest engineer. Once decided, we execute as one team.

CheckDissent recorded in decision log, quarterly review
04

Show the work, including the failed version.

The Lab publishes failures. So do we: postmortems are shared with clients, blameless and specific.

CheckPostmortem shared within 5 working days
05

Clients see our operations, not our slides.

Monthly reviews use live dashboards and real exceptions. No deck is allowed to disagree with the data.

CheckClient reviews run from the live scorecard
06

Hire for judgment, train for tools.

Tools change every quarter. The ability to decide well with incomplete information does not.

CheckEvery interview loop includes a live judgment case
FrameworksSame diagram grammar as the rest of Flobotics

The organization, drawn like a system.

Circles are people, squares are systems, a solid line is ownership. We draw the company the same way we draw a client's workflow, because it is one.

The ownership map

One client pod · Q3 2026
PEOPLE · FLOBOTICS PODSYSTEMSPEOPLE · CLIENT Pod ownerANNA W. EngineerTOMASZ K. EngineerPIOTR Z. Intake agent LIS integration Exception queue Client scorecard CoordinatorsCLIENT TEAM SOLID LINE = OWNS IT DASHED = CONTRIBUTES EVERY SYSTEM: EXACTLY ONE SOLID LINE
From the essay Why good organizations make ownership obvious

The weekly operating rhythm

4 rituals · 2 h 15 min total
Mon
Planning09:00 · 45 min · pre-read
Tue
Deep work
no meetings
Wed
Client demo14:00 · 30 min · live
Thu
Lab hour16:00 · 60 min · all
Fri
Scorecard + retro15:00 · 30 min
Yellow is the one ritual shared with the Lab. Everyone joins, including sales.
DecisionDecidesAdvisesInformed
Which model goes to productionPod tech leadLab · client ITCEO · CTO
Pausing an automationAnyone on the podNo one, act firstClient within 1 hour
Hiring an engineerHiring managerTwo future peersTeam
Starting a Lab experimentAny engineerCTOLab log
Changing a principleCEOWhole company, in writingEveryone, versioned

Decision rights, version 2. "Pausing an automation" is the most important row: anyone can stop a system that is hurting a client.

PeoplePhoto direction: documentary, available light, warm grade

A week at Flobotics, without the posing.

We photograph the work as it happens: planning, pairing, reviews, the Lab hour. Real rooms, real screens with data redacted, no one looking at the camera unless it is a portrait.

The ownership map lives on the wall and changes every quarter. This is the Q3 version, drawn in the same grammar as a client diagram.
New engineer, week two. Pairing on a live exception queue.
Friday scorecard. Eleven numbers, one page, no slides.
Lab hour. Everyone, including sales, runs one experiment a month.
Essays on execution and company buildingMonthly · 5 of 23
30 Aug 2026

Why good organizations make ownership obvious

Ambiguous ownership is the most expensive thing a company can afford. How we draw it, check it and fix it.

Ownership8 min 11 Aug 2026

What we changed when our team stopped scaling cleanly

At 25 people, the way we worked at 12 broke quietly. The three signals we missed and the pod structure that replaced it.

Company design14 min 22 Jul 2026

Building a company where people challenge each other

Challenge does not happen because you ask for it. It happens when it is safe, expected and written down.

Culture10 min 02 Jul 2026

The weekly scorecard: 11 numbers, one page, no slides

What we measure every Friday, why there are exactly eleven numbers and what we removed.

Execution7 min 12 Jun 2026

Hiring for judgment when tools change every quarter

Our interview loop has one live case with incomplete information. It predicts more than any other step.

People9 min
What we changedOrganization changelog · 2026

The company, versioned.

The CTO scores predictions in public. This is the organizational equivalent: every structural change, when we made it and why.

Q1 2026

Client pods of 4 to 6 people

Replaced functional teams. Each pod owns its clients end to end.

Why: handovers were where quality got lost.
Q2 2026

A written pre-read for every decision meeting

One page, shared 24 hours before. No pre-read, no meeting.

Why: the loudest idea stopped winning.
Q2 2026

Two deployment approvals removed

Replaced by automated checks that run on every change.

Why: approvals had become a ritual. Checks are evidence.
Q3 2026

Lab hour for everyone, every Thursday

Sales, delivery and operations each run one experiment a month.

Why: everyone should know what the Lab knows.

Operating Notes, once a month.

One essay, five short notes, and anything we changed. Written for people who run teams.