I've done a few Architecture sessions with teams. It's always valuable. If anything, you'll learn that people in the team have very different ideas about the cu

I've done a few Architecture sessions with teams. It's always valuable. If anything, you'll learn that people in the team have very different ideas about the current and the ideal architecture. Making that explicit, alone, is worth a document. And also: "documentation become unmaintained" is a very poor argument to not make documentation. Because any documentation, even outdated or subtly wrong one, is better than "no documentation".