Ownership is the flagship feature of Rust, known to be a learning challenge for any new user. A core usability challenge of ownership in practice is the gap between its definition and its implementation within Rust’s borrow checker. As a sound and incomplete static analysis, Rust users must carefully interpret type errors to distinguish genuinely unsound behavior from limitations of the analyzer. I explore the challenges at each step in this process of interpretation, and suggest a variety of educational and automated interventions that could improve the usability of ownership.