Agents answer conversations on phones. Managers review campaigns on laptops. Both need the same data, and a table that works for one is unusable for the other.
What does not work
Horizontal scrolling a twelve-column table on a phone. Technically it fits; practically nobody uses it. The columns you need are always the ones off-screen.
What we do instead
Below the medium breakpoint, every row becomes a card. One column is marked primary and becomes the card title; the rest render as a compact key-value grid. Columns marked as desktop-only are dropped entirely rather than shrunk.
The cost
Two layouts to maintain per table, and a decision per column about whether it earns its place on a phone. We think that decision is worth forcing.
The overflow rule
The page never scrolls sideways. Wide content scrolls inside its own container. We check this automatically at seven widths in both themes on every build — it has caught real regressions three times, including one caused by a toolbar with too many buttons.
Touch targets
44px minimum for anything a finger is expected to hit. We do keep smaller sizes for dense desktop surfaces like inline table actions, and we documented that exception in the component rather than leaving it as folklore.