The Architect: the design decision and the debt it just took on
The Architect: Technical decisions, trade-offs, and the risks everyone waved away. Design discussions, architecture reviews, debugging huddles, and engineering deep dives — anything her first pass classifies as technical.
Architecture meetings fail quietly. The decision gets made, the alternative nobody costed disappears from the record, and the risk someone raised at minute forty becomes an incident in Q3. The Architect lens exists to keep those three things attached to each other: what was decided, what it was decided against, and what everyone agreed to stop mentioning.
The report this lens writes
What Happened
One paragraph on the problem the session existed to solve and where it landed, then the discussion in order as transcript-grounded bullets.
Donna’s Take
Is this design actually settled, or did the loudest voice win? Is the team confident or just tired?
Decisions & Trade-offs
Every technical decision with the trade-off weighed — or conspicuously not weighed — plus which choices are reversible and which the team just married.
The Approaches on the Table
Each option seriously discussed: what it was, who championed it, why the winner won, and what the losing approach would have bought.
Risks & Debt
Every risk raised — including the ones raised, laughed about and moved past. Debt acknowledged is a plan; debt waved away is dated and named.
Unresolved Threads
The questions asked and never answered, the “let’s take that offline” moments, and the edge case mentioned once that nobody picked up.
The Receipts
Who owns which task, spike, review or fix — exact words, deadline, timestamp.
Who Knew Their Stuff
Expertise read: who spoke from experience, who spoke from confidence, who asked the question that changed the discussion, and who went quiet when their area came up.
Follow-Up (Donna’s Orders)
What has to happen next, owned and dated — and any risk that got waved away gets un-waved here.
What only this lens does
- It records the alternatives, not just the winner. Six months later the useful artefact is usually “why didn’t we do the other thing”, and that is a section here.
- Risks are graded by how they were treated, not by how they were labelled: raised-and-planned reads differently from raised-and-laughed-at.
- “Let’s take that offline” is tracked as an unresolved thread rather than a resolution, because it almost never comes back online.
When Donna picks it
Design discussions, architecture reviews, debugging huddles, and engineering deep dives — anything her first pass classifies as technical. You can also pin this lens for every meeting in settings, or re-read any past meeting through it on demand — the re-read works from the stored transcript, so nobody has to meet again.
Meetings this lens is built for
Questions, answered straight
Does Donna understand technical content well enough to be useful in a design review?
She does not write code and does not pretend to. The Architect lens reports the decision structure — options, trade-offs, risks, owners, unresolved questions — anchored in exact quotes from the engineers who did the reasoning. That is the part that normally goes missing from the record.
Can I use the Architect lens on a meeting she already read as something else?
Yes. Re-analysis runs the second pass again over the stored transcript with a different lens, so a sprint review can be re-read as an architecture session — or the other way round — without recording anything twice.
Does it capture what was on screen during the review?
Donna records screen video alongside audio, so shared diagrams and whiteboards are preserved as they were shown. The report itself is written from the transcript, with timestamps you can jump to in the recording.
Put Donna in your next meeting
Access is open — sign in with your Google account and she’s in your dashboard in minutes. Rolling out to a whole team, or want a hand with the server setup? We’re glad to help.