User stories describe features - _how_ a system will work - and may even describe value or purpose ("in order to..."). But stories are not the starting point: there's a deeper reason and deeper context for projects, often framed as some sort of _charter_. Charters (by whatever name) define projects' vision and mission, measures of success, boundaries. How do you handle the chartering aspects of _your_ projects? Come to this peer-to-peer workshop, prepared to share what you do, and prepared to learn from others. We'll work in small groups, then share results with the larger group.