Use Scenario Tables to Identify Requirements
Recently I worked on a feature that didn’t have any UI. When a customer is on a payment plan, their account has a due date, and the plan has its own payment schedule. The feature kept those two in sync. A job ran every night, looked at the plan and any payments that had come in, and updated the due date on the account.
Most of the time when I’m building a shared vision on a team, I lean on designs. We put a wireframe or a prototype in front of stakeholders. With this feature, there wasn’t anything to put in front of anyone. I could describe the rule, and everyone in the room…
The skinny
The skinny isn't ready yet — notes appear once the transcript is processed.