Grid Systems in Design - Do You Actually Use Them or Just Wing It?

Honest answer: I use a grid for about 60% of my work and ignore it for the rest. The 40% without a formal grid still has underlying structure - I’m just building it intuitively rather than locking to a system.

The cases where I always use a strict grid:

  • Multi-page documents (reports, brochures, anything with repetition)
  • Anything with a lot of text
  • Responsive web work where the grid carries into dev handoff
  • Client work where another designer might inherit it

Where I wing it:

  • Single posters or one-off compositions
  • Experimental or conceptual work
  • When the brief calls for organic, asymmetric layouts

The real grid knowledge lives in your eye after you’ve worked with enough of them. You start to understand why grids work - alignment, rhythm, visual rest - and you can replicate those outcomes without drawing the columns.

Do junior designers on your teams use grids consistently or do you find yourselves having to push it?

Juniors vary a lot. Some come out of school with strong grid discipline. Others treat it as optional. I always check the grid structure in design reviews before anything else - it tells you a lot about how someone thinks.

The “grid in your eye” concept is real. After a decade of working with 12-column systems you develop internal calibration. But I still draw the grid for anything going to print or to a dev team. Too much room for error otherwise.

@JohnWillowdusk same in my reviews. If the grid is inconsistent I know the layout logic will be inconsistent too. It’s a reliable early indicator.

Photography composition works the same way. Rule of thirds becomes internalized and then you consciously break it when the subject demands it. Same discipline, different medium.