Why might a normalized schema that's correct for writes be actively wrong for reads?

A normalized relational schema prevents duplicate or inconsistent data, which is exactly right for writes — but a read pattern needing a denormalized, aggregated view across several joined tables on every page load fights against that same normalized structure, since the shape correct for writing often isn't the shape needed for reading.