• 0 Posts
  • 4 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • Technical requirements are often ambiguous when written as free text, the way someone would speak them, because as you have discovered the free text fails to capture where the linguistic stress would be that disambiguates in speech.

    Instead, I suggest using a format that is more suited to text.

    I would recommend a table. Email the customer back with your current interpretation of the requirements, with a column for outcome and a column for value. Ask them to check and sign off on the table, or to correct the table where it is wrong.

    Example:

    Outcome Value
    NULL x
    Complete x
    Cancelled x
    (Other) x

    There are edge-cases with if outcome can be "Complete or Cncelled