NASA

How to implement

Never Assume
Avoid making any assumptions about what the other person knows, understands, or intends. Don’t rely on unspoken understanding or implied meanings.

Specify Always
Clearly and explicitly state your instructions, requirements, expectations, or any information you need to convey. Be precise and leave no room for ambiguity.

Example

Assuming that somebody has in-depth knowledge of a topic and being vague with requirements is a common issue. Let’s apply NASA to this one.

Problematic Assumption: “Hey Alex, can you just make sure the user authentication module still works like it always has after you implement those new profile fields?” [Assuming Alex knows exactly how it ‘always has’ worked and all the nuances].

Applying NASA: “Hey Alex, after you implement those new profile fields, could you please verify the following for the user authentication module? [Providing specific points to check]:

• Users can still log in with their existing username and password.
• The ‘forgot password’ functionality remains operational and sends password reset links correctly to the registered email address.
• The system correctly identifies and prevents brute-force login attempts after a certain number of failed tries.
• Session cookies are being set and cleared appropriately upon login and logout.

We should Never Assume that Alex has a complete and up-to-date mental model of all the intricacies of the authentication module. By being specific, we ensure he tests the critical aspects and avoid potential issues.