Design Tools for IT Solutions
Why Plan Before You Build?
Every successful IT product starts with a plan. Jumping straight into building a website, app or database without a design document wastes time and leads to costly mistakes. Design tools help developers, designers and clients agree on what the finished product should look like and how it should work — before a single line of code is written.
The exam requires you to know four main types of design tool: flow charts, mind maps, visualisation diagrams and wireframes. For each one you must be able to describe its components, name software that creates it, and weigh up its advantages and disadvantages.
The four design tools are flow charts, mind maps, visualisation diagrams and wireframes. Each suits a different planning purpose — process logic, brainstorming, appearance, and page layout respectively.
Flow Charts
A flow chart maps out a process step by step. It uses internationally recognised symbols: ovals (start/end), rectangles (process steps), diamonds (decisions with yes/no branches) and parallelograms (input/output). Arrows show the direction of flow.
Flow charts are ideal when you need to show logic — for example, how a login system checks a username and password before granting access. Software such as Microsoft Visio, Lucidchart and even PowerPoint can create them, or they can be hand-sketched.
Advantages: clear visual representation of logic; easy for technical and non-technical stakeholders to follow; standard symbols mean the chart is understood internationally; helps identify missing steps or infinite loops before coding begins.
Disadvantages: can become very large and complex for multi-step systems; symbols must be used correctly or the diagram is misleading; updating a hand-drawn chart is time-consuming when the design changes.
Mind Maps
A mind map is a brainstorming tool. A central idea sits in the middle, with branches radiating outwards to related topics, and sub-branches adding more detail. The spec identifies three specific types used in IT design projects.
A library mind map organises a collection of resources or assets — for example, mapping all the images, audio clips and text files needed for a website. A tunnel timeline mind map sequences tasks over time, showing what must happen before the next stage can begin. A presentation mind map structures the content and flow of a presentation or report.
Mind maps can be drawn by hand or created using software such as MindMeister, Coggle or Microsoft Word’s SmartArt feature. They are quick to produce and easy to update as ideas evolve.
A visualisation diagram (sometimes called a mock-up) shows the intended appearance of an IT product. It includes colours, images, fonts and the general layout — it looks like the real thing but is not interactive. It is useful for getting client sign-off on aesthetics before development starts.
A wireframe is a skeletal layout of a single screen or web page. It uses simple boxes, placeholder text and labels to show where navigation menus, images, headings, forms and buttons will sit — but it deliberately avoids colour or imagery so the focus stays on structure and usability. Wireframes are often the first design step because they are quick to produce and cheap to revise.
Both can be created by hand or using specialist software. Tools widely used in schools and the workplace include Balsamiq (wireframes), Figma (visualisation diagrams) and PowerPoint or Google Slides (both).
A flow chart uses four standard shapes: ovals (start/end), rectangles (process), diamonds (decision) and parallelograms (input/output). Using these symbols correctly is essential — credit goes to labelled, accurate designs.
Sketches vs Software
Design tools can be created either by hand (sketching on paper) or using software. Each approach has its place. Hand sketches are fast, require no technology, and are ideal for early-stage brainstorming when ideas are still forming. They are also exactly what the exam’s 8-mark “create” question requires — students hand-draw their design solution.
Software-created designs look more professional, are easier to share with clients and team members, and are much simpler to edit when changes are needed. The trade-off is that software takes longer to learn and requires access to the correct application. In a professional project, hand sketches are typically used first and then refined digitally.
Assessing Suitability
Choosing the right design tool for a given context is a key exam skill. Ask yourself: does the project need to show a process or logic (flow chart), explore ideas or assets (mind map), communicate intended appearance (visualisation diagram) or plan page structure (wireframe)? A scenario question might describe a developer building a new booking system — a flow chart suits the booking logic, a wireframe suits the booking form layout, and a visualisation diagram suits the client sign-off on colours and branding.