[draven]

We use Kanban in my organisation and tickets go through a Analysis phase where the dev spells out the technical details of what they're going to do and then an Analysis review where two other devs will validate the analysis. Then the ticket can move to the implementation phase itself.

It may seem a lot of overhead at first but the team is small and tickets go through these two phases fast.

The analysis can be considered sort of an ad-hoc ADR.

We started this quite recently but it's already useful and did not slow us down.

[dllthomas]

It's related, but I think it's not quite the same thing. It sounds like you are describing the intended design of the feature you're implementing. As I understand it, an ADR may also set policy regarding future features, where they touch an architectural concern.