This is a classic spreadsheet friction point, and it deserves a sharper solution. A user sets conditional formatting to flag negatives in red and leave positives clean, but empty cells, which mean "no data yet", get painted red too. The spreadsheet punishes you for not having an answer. That is not a user error. It is a design limitation that forces people to add workaround steps to a process that should be intuitive.
The core issue is that legacy conditional formatting treats emptiness as zero, which is rarely the user's intent. If you track monthly sales and a cell is blank because the invoice hasn't arrived, you do not want that cell screaming for attention. You want it to wait quietly. The fix in traditional spreadsheets involves adding a second rule or an `ISBLANK` check, which works but adds cognitive overhead. Every extra rule is another thing to remember, another thing to break when someone else edits the sheet. The user in this case did what any reasonable person would do: they set up two rules and expected the empty cells to stay neutral. The tool failed to match that expectation.
This is where an AI-native spreadsheet should step in and say, "We see what you mean." Instead of requiring the user to manually exclude blanks, the system should recognize the pattern, red for negative, clear for positive, nothing for empty, and apply it automatically. The conditional formatting logic should treat blanks as a third state, not a numerical zero. That is a small change in code but a large change in user experience. It removes the mental friction of "why is this empty cell angry at me?"
The practical takeaway is that conditional formatting rules in legacy tools are too literal. They execute exactly what you type, even when what you type does not match what you mean. A smarter system would interpret the intent: "highlight values that are problematic" and leave untouched cells alone unless you explicitly tell it otherwise. For anyone managing a dashboard, a budget tracker, or a project log, this distinction saves time and reduces confusion. The fix is not complicated, but it requires the tool to respect the user's context, not just the cell's value. That is the standard we should expect.