Keep the why behind the decision, on your Mac

The decision usually makes it into a ticket. The alternatives and the constraint that killed them usually do not. Weeve keeps all three, on the Mac that heard the review.

Record technical reviews hero

01

Press record

The session runs the way it always did. Nothing joins the call and nothing appears in the room.

02

Listen

No notebook between you. Watch the participant instead of your keyboard.

03

Read it back

A verbatim transcript, attributed by speaker, ready by the time you have shown the participant out.

Record technical reviews story beat 1

Six months later, someone asks why

The decision survived in a ticket. The alternatives considered and the constraint that killed them did not.

Record technical reviews story beat 1

Six months later, someone asks why

The decision survived in a ticket. The alternatives considered and the constraint that killed them did not.

Keep the why, not just the what

Keep the why, not just the what

Keep the why, not just the what

Record technical reviews story beat 2

The review stays on this Mac

A design review is a detailed description of your own systems. That is not a recording anyone should be uploading.

Record technical reviews story beat 2

The review stays on this Mac

A design review is a detailed description of your own systems. That is not a recording anyone should be uploading.

Record technical reviews story beat 3

Most of an ADR, already written

The decision, the options rejected, and the constraints that killed them, ready to paste into the record.

Record technical reviews story beat 3

Most of an ADR, already written

The decision, the options rejected, and the constraints that killed them, ready to paste into the record.

“For me, data sovereignty means controlling the location of data, not simply switching vendors.”

Teon Beijl

Founder

at

“For me, data sovereignty means controlling the location of data, not simply switching vendors.”

Teon Beijl

Founder

Can I use this to write an architecture decision record?

The summary gives you the decision, the rejected options, and the constraints, which is most of the document.

Is a recording of our internal systems safe here?

Does it handle technical vocabulary?

Does it work while someone is screen sharing?

Can I keep reviews for one system separate from another?

Can I use this to write an architecture decision record?

The summary gives you the decision, the rejected options, and the constraints, which is most of the document.

Is a recording of our internal systems safe here?

Does it handle technical vocabulary?

Does it work while someone is screen sharing?

Can I keep reviews for one system separate from another?