Using the Less Than Sign Correctly

Less Than Sign In Math: What It Actually Looks Like

The less than sign is that pointed character — < — and it means the number on the left is smaller than the number on the right. A < B. That's it. That's the definition. But getting it right when you're writing actual math or working through inequalities is where things get messy, and most people just guess and move on. You'd be surprised how often I see this flipped. People type B < A when they mean A < B. The point faces the bigger number, but honestly, that mnemonic only helps if you're not already rushing. I've graded enough student work to know the mistake is everywhere, from basic algebra all the way through to formal proofs where it silently derails the whole argument.

Writing It by Hand vs. On a Keyboard

Handwriting is where I run into trouble most. When I'm working through a problem set at the whiteboard, my < comes out looking like a V or some kind of half-drawn checkmark. A colleague once told me my inequalities were unreadable because the point was blurring into the equals sign next to it. I started deliberately closing the gap between the two strokes and making the point sharper. It took about three weeks to retrain my hand, but now my < doesn't look like a question mark anymore. On the keyboard, it's < and you hold Shift to get it on most US layouts. The problem here is that people confuse it with the left angle bracket in programming contexts. They look identical. In math, we use < for less than. In HTML or code, < starts a tag. Context handles the distinction, but it trips people up when they're copying notation between a math document and a code editor without thinking about it.

Inequalities and the Direction Problem

The core issue with the less than sign shows up when you manipulate inequalities. Multiply or divide both sides by a negative number and you have to flip the sign. This is not optional. It's not a suggestion. If you solve -3x > 6 and forget to reverse the sign, your answer lands in the wrong region entirely and the grading rubric doesn't care how close you were to remembering. I remember a specific homework problem where I had to solve (x - 2)/(x + 1) < 0. The trap here is that you can't just multiply both sides by (x + 1) because you don't know its sign yet. If x + 1 is negative, the inequality flips. I spent twenty minutes going down the wrong path before someone pointed out that you should use a sign chart instead of algebraic manipulation. The critical points are where the numerator is zero — x = 2 — and where the denominator is zero — x = -1. Those split the number line into three intervals, and you test a value in each one. The expression is negative on (-1, 2). That's the solution. Simple method, but the instinct to cross-multiply wins most of the time unless you've been burned by it before.

Common Pitfalls

  1. Flipping the sign when multiplying by negatives — This is the most common error and it compounds. One missed flip in a multi-step problem breaks everything downstream.
  2. Confusing and — The equals version matters in edge cases. If you're working with limits or bounds, missing that changes whether an endpoint is included in the solution set.
  3. Applying it to complex numbers — You can't say one complex number is less than another in any meaningful standard way. Ordering on C doesn't exist. This comes up more often in analysis courses than students expect.

When the Less Than Sign Fails You

There's no workaround for the complex number thing. You just have to accept that comparison operators like < don't apply and switch to magnitude or real/imaginary part comparisons if your problem actually requires it. In some applied settings, people invent custom orderings, but those aren't standard and they don't behave like regular < in most proofs. Another hard limit: in formal logic and proof assistants, the less than sign carries assumptions about the domain. If you're working in a system like Lean or Coq, you can't just assert a < b without establishing that both sides live in an ordered type. I ran into this when helping a grad student migrate a real analysis proof into Lean. The entire inequality chain broke because the variables hadn't been declared in the reals explicitly. Five minutes of type annotations fixed it, but it highlighted that the symbol isn't self-describing the way it appears to be in casual math writing.

A Practical Note on Typesetting

If you're writing math professionally, use LaTeX or a similar tool. Hand-typed inequalities in plain text documents look like a / and they confuse readers. In LaTeX, < renders cleanly in math mode with proper spacing. The difference is noticeable enough that peer reviewers will flag handwritten-style formatting without calling it out explicitly. It signals carelessness. One detail that rarely gets mentioned: in LaTeX, there's also the \lt command. It produces the same glyph as < inside math mode, but it reads as the word "less than" in semantic markup. Some publishers and typesetting pipelines prefer it because it makes the source code more readable and separates the mathematical intent from the visual symbol. Most people never use it. I only started using it after my coauthor complained that he couldn't tell at a glance whether a < in a long formula was meant to be a less-than sign or a stray angle bracket from copied code.