career bridge
Prove it
Lead with the reasoning, not the diagram, and show the revision that looks like being wrong and reads as being trusted.
You have an estate map, a costed decision, a reference architecture and a revision that survived contact with a second team. Architecture portfolios fail in one specific way: they lead with the final diagram, which is the least interesting thing you have produced.
What you do
Show the reasoning rather than the drawing. Lead with the decision record, because the line naming what would change your mind is what separates an architect from somebody who draws. Then show the before and after of the second team: here is what I designed, here is where it did not fit, here is what I changed and what I refused to change and why. That sequence is the whole job on one page, and almost nobody includes it because it looks like being wrong. It reads as being trusted. Keep the diagrams, but put them second and make each readable in thirty seconds, captioned with the decision it encodes rather than the components it contains. Cut every diagram you could not defend line by line. Then rewrite your CV against the estate map from stage one, using the language of constraints rather than a technology list, because architects are hired for judgement about constraints and every candidate lists the same technologies. Finally, have someone who does not do your work read it and tell you what you decided and what you refused.
Done when
- The decision record leads, including the line naming what would change your mind.
- A before and after of the second team is shown, including what you refused to change and why.
- Every diagram is readable in thirty seconds and captioned with the decision it encodes.
- Any diagram you could not defend line by line has been removed.
- Someone outside your field has read it and named both a decision and a refusal.
What you end up with
A portfolio read in twelve minutes: a decision record naming what would change your mind, and a before-and-after showing what a second team broke and what you refused to change.
If you get stuck
The quiet failure is a portfolio of beautiful diagrams with no decisions visible in it, which reads as drawing rather than architecting. Reasoning first, pictures second. The second failure is hiding the revision because it looks like the first design was wrong. Every architecture that has met a second team has been revised. Showing yours is how a reader knows it met one.