NovWhen a table makes a property answer harder
Tables can clarify a comparison, but they can also hide differences, overload mobile screens and give unlike evidence the same visual weight.
This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.
A table looks organised before anyone has read it. That is exactly why editors need to be suspicious of the format.
On a laptop, six columns may feel manageable. On a phone, the same comparison can turn into horizontal scrolling, clipped notes and a reader who no longer remembers which row they are following.
I prefer to ask what the reader needs to see simultaneously. If the answer is three things, we probably do not need seven columns.
The economy and finance section is a useful internal benchmark: tables work where period, measure and interpretation genuinely need to be compared at once.
A table is strongest when the comparison has a clear axis. Two payment plans can be compared by instalment, timing and total due. Two ownership structures can be compared by what right is obtained, for how long and under what conditions. The reader benefits from seeing equivalent fields side by side. That is a real information-design advantage, not simply a more “analytical” appearance.
Problems start when the grid becomes a container for everything we know. A price, a legal note, a marketing claim, an editorial judgement and a long caveat can all end up as neighbouring cells. The visual treatment gives them equal weight even though the evidence behind them is completely different.
There is another problem. A table can flatten different kinds of evidence. A contractual term, a developer statement and our own interpretation may all appear as equally solid cells. The design has made them look more comparable than they really are.
This matters in property content because identical-looking numbers can come from very different sources. “8% yield” may refer to a contractual payment, a developer forecast, a historical rental figure or an illustrative calculation. If the table does not preserve that distinction, it turns typography into an argument the evidence never made.
Tables also encourage false completeness. Once a structure has five columns, there is pressure to fill every cell. If one project has a confirmed fee and another does not, the blank space can feel untidy. That is not a reason to insert an estimate. An honest “not confirmed” may be more useful than a neat but weak number that exists only to preserve symmetry.
Mobile use makes editorial prioritisation even more important. A desktop spreadsheet can display every possible parameter. A reader on a phone is usually trying to answer a narrower question. Which option costs more upfront? Which has the stricter owner-use rule? Which requires a larger payment before completion? If those answers are buried among ten secondary columns, the table has increased work instead of reducing it.
I often prefer a two-layer structure: a compact table for the parameters that genuinely compare well, followed by prose for the differences that need context. The table lets the eye find the contrast. The paragraphs explain why it matters, where the data comes from and which conditions do not fit comfortably into a cell.
Prose is also better for causality. A table can show that one scheme has a lower initial payment, but it may not explain that a much larger balance arrives later and changes the buyer’s cash-flow risk. If the practical consequence matters, the article still needs to state it in words. Readers should not be asked to reverse-engineer the conclusion from the layout.
I look at row labels carefully too. Internal categories such as “risk: medium” can appear efficient, but they often hide the very reasoning the reader needs. Why medium? Because the fee is unconfirmed? Because the source is old? Because owner use is restricted? A short explanation usually serves the reader better than a rating with no visible method.
Sometimes prose is better. Sometimes a short three-column table is perfect. The choice should follow the question, not our desire to make the page look analytical.
The measure I use is effort saved. If a table allows the reader to spot a real difference faster and with less interpretation, it has earned its place. If the reader has to decode the cells, scroll sideways, remember footnotes and then read paragraphs anyway, the format is probably doing too much.