System Architecture Deck

About this template

Who this deck is for

An 8-slide deck for stating how a system is put together and why, aimed at approvers and other teams rather than a deep technical review. Interface specs and full data flows need a separate design document.

The file has no diagram shapes

There are no boxes and arrows here; body slides are title, one summary line and three bullets. To add a diagram, duplicate a body slide, delete the bullet shapes and draw in that space. Keep one diagram to three layers – slide 4 already says the system is split into gateway, service and storage tiers, so matching the drawing to those three keeps words and picture aligned.

Filling it in

1. Replace the cover label and title with the system name and document version, and fix the presenter placeholder and the template blurb underneath.
2. The agenda holds four items: boundaries and structure, monolith versus split architecture, key metrics, trend analysis. All four have slides – the first uses the divider on slide 3 with the body on slide 4, and the other three are carried by the comparison slide 5, the metric cards on slide 6 and the bars on slide 7.
3. So changing the running order means adding slots, not filling empty names. For subjects that need their own slide – requirements, data flow, failure handling, security, open decisions – duplicate slides 3 and 4 as a pair and add a matching agenda line. Only divider 01 exists, so 02 onward must be typed in by hand.
4. Rewrite the six lines on slide 5 for your system. The left column (web, API and batch on one server; a deploy stops everything; a fault spreads to every function) faces the right column (three services split by role; sequential zero-downtime deploys; blast radius isolated), line for line: structure, deployment, fault propagation. As-is and to-be diagrams fit the same left-right positions.

Examples

• Slide 4 bullets ship as three tiers of gateway, service and storage; six external integration points; an explicit boundary between the internal and public networks. For example: three services and one shared auth server / all traffic enters through a single gateway / batch jobs on a separate queue.
• If you add a failure-handling slide, for example: identical stacks in two zones / database promotes automatically, 90 seconds from detection to promotion / 30 seconds read-only during promotion.
• The cards on slide 6 ship as 3,200 requests per second, 86ms latency, three tiers and two availability zones. All four are figures you use while explaining the design, so keep the labels, replace the numbers with measured ones, and add a line under the cards stating the measurement window and path. The three tiers and two zones also appear in the wording on slides 4 and 5, so change them together.
• The bars on slide 7 are latency by load: 86 at normal, 104 at 2x, 138 at 5x, 190 at 10x. The 86 is the same value as the latency card. It is not a time series, so retitle it as response by load and caption the tool and scenario used.

Common mistakes

• Drawing every component; past ten boxes nobody follows.
• Omitting the alternatives you rejected, so the same question returns at every approval meeting.
• Quoting a response time with no request type or path.
• Filling the right column of slide 5 with product names only; the left three lines must be the problems you have today for the right three to read as answers.

Put the open decisions on a slide of their own

Architecture talks argue about what has not been settled. Duplicate a body slide before the closing slide 8 and list three open items with a decision date and a decision owner for each, for example message queue product by April 10 with the platform team, log retention by April 17 with security.

Before you circulate it

A diagram carrying real server names or internal addresses cannot go outside. In the external version replace names with roles, and keep the document version and date on the cover. Slide 8 carries a second presenter placeholder, so fill it in along with the cover.