It's the new hire's third day. They open the incident screen for the first time: four tabs, a detail grid, 50 fields, and no clue which ones matter right now. They fill in what they recognize, skip what they don't, and hit save. The record looks fine. It isn't. A required detail is missing, a business rule quietly broke, and three weeks later someone must work out why that incident never triggered an action. As a developer you didn't do anything wrong. You trained your users how to use the application, and most days that holds. But training lives in people's heads, and heads forget, leave, and improvise. So instead of teaching users where to look, bring every field they need straight to them, one step at a time. Most of us already know that pattern by another name: a wizard. This post shows two ways to build a guided, multi-step process in the Software Factory, and how to pick the one that fits. Why guide the user at all?There are lots of reasons to guide your users. We've listed a few
