You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
People misunderstand Needs and sometimes write long descriptions for a Need, confusing them with Responsibilities.
In fact, Needs should have very short descriptions that should follow the pattern:
We need X (so that Y).
For example:
We need Noden to be stewarded and led to the benefit of its members.
We need great online tools to help us coordinate, collaborate, and communicate.
OR
We need Frihamnstorget and the house to be safe and secure with regards to locks, fire safety, and other matters so that we can work, create, and party safely.
We need a metal workshop so that we can make metal stuff.
We should implement a UX that makes sure that needs are always short and that helps you format them in this way.
The text was updated successfully, but these errors were encountered:
People misunderstand Needs and sometimes write long descriptions for a Need, confusing them with Responsibilities.
In fact, Needs should have very short descriptions that should follow the pattern:
We need X (so that Y).
For example:
OR
We should implement a UX that makes sure that needs are always short and that helps you format them in this way.
The text was updated successfully, but these errors were encountered: