Visio in Four Hours: Networks, Flows and Site Plans

Drawing by doing

Open Visio and go to File > New. Type network in the search box, choose Basic Network Diagram, then Create.

Almost every Visio tutorial opens on a flowchart. This one does not, because the network template is where the rest of the morning lives and because a network is a better first drawing: the shapes mean something, so you notice immediately when you have used the wrong one.

You are now looking at three regions. Stencils on the left, holding the shapes available to this template. The canvas in the middle. The ribbon along the top. Most of what you need is on the Home tab.

Getting shapes onto the page

1. Drag a shape from the stencil onto the canvas. As it approaches other shapes, faint guide lines appear; that is the Dynamic Grid, and it is doing your alignment for you. If you cannot see it, turn it on under View > Dynamic Grid.
2. Hold Ctrl and drag an existing shape to copy it. Faster than copy and paste, and it keeps the formatting.
3. Click any shape and start typing to label it. There is no separate text mode to enter.
4. Select several shapes, then Home > Align and Home > Position to tidy a row properly. Nudging shapes by hand is the slowest way to a messy drawing.
5. For exact placement, open View > Task Panes > Size & Position. Type coordinates rather than dragging when something has to sit precisely.

Connecting them

The Connector tool is on the Home tab, or press Ctrl+3. Press Ctrl+1 to go back to the Pointer tool afterwards; forgetting to do this is the single most common source of "why is Visio drawing lines everywhere".

There is also AutoConnect: hover over a shape and blue arrows appear on its four sides. Click an arrow and Visio adds a connected shape in that direction. It is the fastest way to build a chain, and you can turn it on or off under View > AutoConnect.

Formatting without repeating yourself

Format one shape the way you want it, then use Home > Format Painter to copy that formatting to another. Double-click the Format Painter to lock it on for several shapes; click it again to release.

Once a cluster of shapes belongs together, select them and use Home > Group so they move as one. Grouping a rack of servers or a branch office saves a great deal of grief later.

Topology and conventions

You have a drawing. Whether it is a diagram depends entirely on what happens next.

A network diagram has one job: to let somebody who was not in the room understand the network. Almost every failure to do that comes from the same handful of omissions, and they are all cheap to fix.

Use the shape that means the thing

Open More Shapes > Network and you will find several stencils: Network and Peripherals, Computers and Monitors, Detailed Network Diagram shapes, and Rack-mounted equipment. The icons are conventional, which is the point. A router icon means a router. If you use a router icon for a layer 3 switch because it looked about right, you have told the reader something false.

Pick your icons once, at the start, and stay consistent across the whole drawing. Two different icons for the same class of device is the most common thing that makes a diagram read as amateur.

Label the links, not just the boxes

Most beginner diagrams name every device and say nothing at all about what runs between them. The connections are usually where the reader's actual question lives.

To label a connector, click it and type, exactly as with a shape.

The legend and the title block

Two boxes that take five minutes and do more for readability than any amount of formatting.

The legend sits in a corner and lists every icon type you have used, with one line of plain English each. It exists because your reader does not necessarily share your icon vocabulary.

The title block carries the diagram name, who drew it, the date, the version, and one line on scope. That last line is the one people leave out and then regret: say what the diagram does not show. "Physical connections only; no VPN or cloud services" prevents an entire category of misunderstanding.

Two views of one network: layers

A physical diagram and a logical diagram usually describe the same equipment and are usually kept as two separate files that drift apart. Visio's layers let them be one file.

1. Open Home > Layers > Layer Properties and create two layers, for example Physical and Logical.
2. Select the shapes belonging to one view, then Home > Layers > Assign to Layer.
3. In Layer Properties, untick Visible on one layer to show the other view on its own.

Layers also carry a Lock setting, which is separate from visibility; hiding a layer does not protect it from editing. Lock the background layer when you are working on top of it.

Shape Data: the part that makes it an asset register

Every Visio shape can carry structured data behind it. Right-click a shape, then Data > Shape Data to see what is already there; Data > Define Shape Data to add your own fields.

On a network device the useful fields are obvious: management IP, model, serial number, firmware version, physical location, owner, warranty expiry. Fill those in and the drawing stops being a picture and starts being a small asset register that happens to be shaped like the network.

You do not have to type them one at a time. Data > Quick Import reads a spreadsheet and shows its rows in a pane on the right; drag a row onto a shape and the fields attach. Visio can also read from Access and SQL Server.

Diagrams from a table

Nobody follows along in this section. Watch it, understand the shape of it, and come back to it another day when you have a real process to draw. It is a feature that rewards a quiet afternoon and punishes an attempt to learn it at the same time as everything else.

Visio's Data Visualizer generates a flowchart from a table. You do not draw the diagram; you describe the process in rows and columns, and Visio draws it. Change the table, refresh, and the drawing updates.

The payoff, first

The demonstration worth watching is not the wizard. It is this: a finished flowchart on screen, a spreadsheet open beside it, one cell edited, then Data > Refresh All, and the diagram redraws itself. That is the whole argument for the feature. A process that changes every few months stops being a drawing you maintain and becomes a table you edit.

The schema

Everything the diagram knows comes from these columns. This is the transferable part; if you remember nothing else from this section, remember that the table is the diagram.

A worked example

Six rows, one decision, one loop back. Small enough to read whole.

Read row three across and the idea lands whole: this step is a diamond, it branches two ways, the branches go to rows four and five, and the arrows carry the labels Yes and No in that order. Row five points back at row two, which is how you write a loop.

Running the wizard

1. File > New, search Data Visualizer, and choose Data Visualizer Basic Flowchart. The cross-functional version is the same wizard with one extra step for swimlanes.
2. Visio opens a blank canvas and launches the Create Diagram From Data wizard. If it does not, use Data > Create from Data > Excel Workbook.
3. Point it at the workbook and tick "My data has headers".
4. Map the columns. Visio matches them by name and usually gets it right on its own.
5. Map the shape types. Your Shape Type values are matched to Visio shapes; fix anything showing as Unmapped.
6. Finish, and give it a few seconds on anything larger than the example above.

Wireframes and site maps

People building their first website usually start by choosing a theme, then discover three weeks later that they do not know what pages the site has. Both of the drawings in this section exist to prevent that, and they answer different questions.

A site map answers "what pages exist and how do they relate". It is the whole site at once, and nothing on it describes what any page looks like.

A wireframe answers "what is on this one page and roughly where". It is one page at a time, deliberately grey and unstyled, because the moment you add colour people start discussing colour instead of structure.

The site map

File > New, search web, and choose the Conceptual Web Site template. It opens three stencils: Conceptual Web Site Shapes for pages and page groups, Web Site Map Shapes for the more specific elements such as forms, controls and multimedia, and Callouts for annotation.

1. Drop a home page shape at the top and name it.
2. Add a page shape for each top-level section and connect them to home.
3. Add second-level pages under their sections. Stop at the point where the pages become repetitive; a site map showing forty near-identical product pages tells nobody anything, so use one shape and label it "product pages, one per item".
4. Mark the pages that do something rather than just showing text: forms, logins, downloads, embedded video. The Web Site Map stencil has shapes for these, and they are what turn a site map into a build estimate.
5. Use a Callout on anything that needs a note, for example which pages need to exist before launch and which can follow.

The wireframe

Wireframes are built from plain rectangles, lines and text, plus the control shapes from the Web Site Map stencil. Keep everything greyscale. Use a box with a cross through it for an image, a horizontal rule for a line of text, and a labelled rectangle for anything interactive.

Do one page in detail, and choose the hardest one; usually the home page or whichever page has the most going on. If the difficult page works as a wireframe, the simple ones follow the same grid.

The same diagram in text

Visio is not the only way to produce a diagram, and for a large class of diagrams it is not the best one. Mermaid is a small text language that renders as a diagram. You write a description, and something else draws it.

Here is the entire flowchart from the table section, written as text.

flowchart TD
  A([Request received]) --> B[Check request details]
  B --> C{Details complete?}
  C -->|Yes| D[Assign to team]
  C -->|No| E[Return to requester]
  E --> B
  D --> F([Request closed])

Enough syntax to be useful

Once a node has been named you can refer to it by its short name alone, which is why E --> B is enough to draw the loop back.

Where it renders

Mermaid is not a program you install. It is text that other tools know how to draw.

• The Mermaid live editor, which draws as you type and exports an image. The quickest way to try any of this.
• GitHub renders Mermaid inside a fenced code block in any Markdown file; see GitHub's own documentation.
• Obsidian, Notion and several other note applications render it in a code block, so a diagram can live inside your notes rather than beside them.
• Visual Studio Code renders it in the Markdown preview with an extension installed.

Asking an assistant for it

Mermaid is text, which means an AI assistant can write it. Ask Copilot, or any other assistant, for "a Mermaid flowchart of this process" and paste in the steps; you will get back something close, which you then edit. This is the practical reason to learn the syntax even if you never write one from scratch: you need to be able to read what comes back and correct it.

Two cautions. Assistants sometimes produce syntax from a different version and it will simply fail to render; the live editor will tell you which line. And they are prone to inventing steps that sound plausible, so check the diagram against the process rather than against how tidy it looks.