01 · Think visually
Mind Mapping
A mind map is a diagram that radiates outward from a single central idea. Instead of a linear list, you branch related thoughts into nodes and sub-nodes, building a visual structure that mirrors how ideas actually connect. The technique was popularised by Tony Buzan in the 1970s, but the underlying principle — spatial association aids memory and creativity — is far older.
For architects and designers, mind mapping shines at the fuzzy front end of a project: capturing a client brief, exploring concept directions, breaking down a design problem, or planning a presentation. Because the structure is loose, you can capture ideas at the speed of conversation and organise them later.
In practice
- Place your core subject at the centre — the project name, the design problem, the brief.
- Branch out main themes: site, program, budget, materials, precedents, stakeholders.
- Add sub-branches with details, questions, and constraints as they come up. Don't filter yet.
- Review the map: cluster related nodes, prune dead ends, and let the structure reveal priorities and gaps.
Kanban (Japanese for "signboard") is a visual workflow method developed at Toyota in the 1940s and later adopted across software and knowledge work. Work items are written on cards and moved across columns that represent stages — typically To Do → In Progress → Done. At a glance, the board shows what's being worked on, who's doing it, and where work is piling up.
Two rules give Kanban its power: visualise everything (if it's not on the board, it doesn't exist) and limit work in progress (finish things before starting new ones). For a design studio, this maps naturally onto deliverables — drawings, submissions, RFIs, revisions — and keeps a team honest about capacity during deadline crunches.
In practice
- Create columns matching your real workflow — e.g. Backlog, Drafting, Internal Review, Client Review, Issued.
- Write one card per deliverable or task. Keep cards small enough to finish within days, not weeks.
- Set a work-in-progress limit per column. If "In Progress" is full, finish something before pulling new work.
- Review the board daily. Cards stuck in one column are your bottleneck — fix that stage, not the symptoms.
03 · Plan time
Gantt Charts
A Gantt chart plots tasks against time: each task is a horizontal bar whose position and length show when it starts and how long it runs. Named after Henry Gantt, who formalised it around 1910, it remains the standard way to communicate a project schedule — from design phases and permit milestones to construction sequencing.
Where Kanban shows flow (what's moving right now), a Gantt chart shows structure (how the whole timeline fits together). Its key concepts are dependencies — task B can't start until task A finishes — and the critical path, the chain of dependent tasks that determines the earliest possible completion date. Any delay on the critical path delays the whole project.
In practice
- List your phases and tasks — concept, design development, documentation, tender, construction stages.
- Estimate durations honestly and add dependencies between tasks that must happen in sequence.
- Mark fixed milestones: submission deadlines, permit decisions, contract dates.
- Track progress against the plan weekly, and watch the critical path — that's where slippage hurts.
04 · Define the brief
Architectural Space Programming
Space programming (also called architectural programming or briefing) is the process of translating a client's needs into a structured list of spaces — each with an area, a function, occupancy, and adjacency requirements — before any design work begins. The program is the quantitative backbone of the brief: it tells you the building needs, say, 12 classrooms of 60 m², a 300 m² library, and admin offices adjacent to the entry.
A good program does more than list rooms. It captures adjacencies (which spaces must connect, which must be separated), net-to-gross ratios (circulation, walls, and services typically add 25–40% to net area), and priorities when the budget forces trade-offs. Skipping this step is how projects end up redesigned at documentation stage.
In practice
- Interview stakeholders and list every required function — don't jump to room names yet.
- Assign each space a net area, occupancy, and any technical requirements (daylight, acoustics, services).
- Map adjacencies: which spaces need direct connection, proximity, or deliberate separation.
- Sum net areas, apply a grossing factor, and check the total against the site capacity and budget.
05 · Measure the work
What is Quantity Takeoff?
Quantity takeoff (QTO) is the systematic measurement of everything a project needs to be built: cubic metres of concrete, square metres of wall and floor finishes, linear metres of pipe, counts of doors and fixtures. The name comes from "taking off" quantities from drawings. Those quantities, multiplied by unit rates, become the cost estimate — and later, the bill of quantities (BOQ) used for tendering and payment.
Accuracy matters because every downstream number depends on it: budgets, bids, procurement, and progress claims all trace back to the takeoff. Traditionally done with scale rulers and highlighters on printed drawings, QTO today ranges from digital on-screen measurement to fully automatic extraction from BIM models, where every wall already knows its own volume.
In practice
- Work systematically through the drawings by trade or element — substructure, frame, envelope, finishes, services.
- Measure in the unit the work is priced in: m³ for concrete, m² for finishes, linear m for skirtings, counts for fittings.
- Record dimensions with a clear audit trail so anyone can check where a quantity came from.
- Apply waste factors and cross-check totals against benchmarks (e.g. formwork-to-concrete ratios) to catch errors.
06 · Share models openly
openBIM
Building Information Modelling (BIM) replaces flat drawings with intelligent 3D models: a wall in a BIM model isn't just lines — it knows its material, fire rating, cost code, and which rooms it bounds. openBIM is the practice of exchanging that information through open, vendor-neutral standards rather than locking it inside one software vendor's format.
The cornerstone is IFC (Industry Foundation Classes), an ISO-standardised format (ISO 16739) maintained by buildingSMART that lets a model authored in Revit, ArchiCAD, or Tekla be opened, checked, and coordinated in any compliant tool. Alongside it sit BCF (BIM Collaboration Format) for exchanging issues and comments, and IDS for specifying what information a model must contain. For project teams, openBIM means the model outlives any single software subscription — and clients aren't held hostage to a vendor to read their own building data.
In practice
- Export IFC from your authoring tool using the appropriate Model View Definition for the exchange purpose.
- Check the export: verify georeferencing, spot floating or duplicate elements, and confirm property sets came through.
- Coordinate across disciplines by federating IFC models from each consultant into one viewer.
- Log clashes and questions as BCF issues tied to specific elements, so nothing gets lost in email.
07 · Understand the site
GIS Mapping
A Geographic Information System (GIS) links data to location. Where a CAD drawing shows geometry, a GIS map shows geometry plus attributes: this parcel has this zoning, this owner, this flood risk; this road carries this traffic volume. Data is organised in layers — cadastre, topography, utilities, land use, hazards — that you can stack, filter, and query for any point on Earth.
For site analysis and feasibility work, GIS is the fastest route from "an address" to "an informed decision." Before sketching a single line, you can establish a site's true boundaries, slope, orientation, zoning envelope, overlays, and context. Most planning authorities now publish this data through open portals, and coordinate reference systems (like WGS 84 or your local projected grid) ensure everyone's layers line up. GIS is also the bridge between BIM and the city: a properly georeferenced model drops into its real-world context.
In practice
- Locate the site and confirm cadastral boundaries against the legal title — not just the aerial photo.
- Stack the layers that constrain design: zoning, height limits, setbacks, easements, flood and hazard overlays.
- Analyse the terrain: slope, aspect, and drainage direction shape everything from access to cut-and-fill.
- Feed the findings into a feasibility check — buildable envelope, yield, and parking before concept design begins.
Ready to put these into practice?
Every DSYNTEC tool runs entirely in your browser — free, private, no sign-up.
Browse all tools