twimco.Let’s talk ↗︎
Menu

The TWIMCO notebook

Field notes.

Useful observations from inside the work.
For people building a better way.

Product & engineering · 29 notes

Editorial illustration for Field Note: Write the change-communication brief before you flip the flag.
Product & engineeringField note

Write the change-communication brief before you flip the flag.

Engineering called it a small UX tweak. At 10 a.m. ops finds a status that means something different and a filter that's gone, and support starts inventing explanations. Tell the people who run the system before the flag flips.

Read the note ↗︎
Original conceptual editorial illustration; not a client interface.
Product & engineeringField note

Test the deny shapes before you trust the policy.

Your agent policy says no rm -rf. Has anyone tried TZ="$HOME" rm -rf, a command chained after &&, or a symlink to the file you blocked? Try the odd shapes before you call it enforced.

Read the note ↗︎
Bright stair: a person walks up pale steps past a book, a phone, and a laptop toward a small cabinet.
Product & engineeringField note

Widen write access only after trust is proven.

Read access and open write access are not neighbors. Widen the write only after you can show the last rung actually held.

Read the note ↗︎
Glass office: two people at facing desks, one with a notebook and one with a tablet of two blank profiles.
Product & engineeringField note

Spec “same person” before you sync writes.

Syncing the same person across systems is a write. Decide what counts as a match before that write is allowed to land.

Read the note ↗︎
Editorial illustration for Field Note: Make training a ship gate, not a slide after launch.
Product & engineeringField note

Make training a ship gate, not a slide after launch.

A TWIMCO Operator Training Path Spec: roles, scenarios, pass evidence, and cannot-go-live-until—so the UI is not the whole delivery.

Read the note ↗︎
Antique workshop with two craft stations and a marked boundary rail between them; red thread labeling allowed tools on the rail and a locked chest for forbidden writes.
Product & engineeringField note

Specify the integration boundary before the first write.

Day one, the happy payload writes fine. Then a retry doubles a side effect, one side updates and the other doesn't, and nobody can say which fields were ever meant to cross. Decide what may and must never be written before the first real write.

Read the note ↗︎
Antique workshop ledger desk with an open bound register and a discarded message slip beside it; red thread stitching five checklist marks into the ledger margin.
Product & engineeringField note

What must live in the record—not in chat.

An approval happens in a channel and a screenshot becomes the proof. Months later nobody can say who decided what, or on which evidence. If closing the tab loses the fact, it was never really recorded.

Read the note ↗︎
Antique control room with labeled state cards on a shared ledger, a red thread between record and operator, and a mechanical agent paused until the ledger updates.
Product & engineeringField note

Specify visible state, not just a shared screen.

Two people look at the same screen. One thinks the work is done, the other thinks it's waiting on a carrier, and an agent reading it will confidently pick a side. Trust comes from state kept in a record, not implied by a color.

Read the note ↗︎
A phone, field notebook and rolled service plan sit beside a worn tool bag
Product & engineeringField note

The work between the screens.

The real requirements often appear when someone shows you how they get through an ordinary day.

Read the note ↗︎
A good place to begin.

A familiar problem? Let’s look closer.

Tell us where you want to go. We’ll find the first thing worth changing.

Tell us about it ↗︎