Before architecting information for a better user experience, there was a very big problem with the words we were using.
For example:
These three words where often used interchangeably because of their similarity, however, they describe distinctly different things. In order to piece together what meaning was being used, you had to read into the context or voice intonation.
However, when it came time to organize the endpoints for the engineers to develop GraphQL schemas, and communicate with stakeholders and designers. It was becoming an issue.
Another issue that appeared was the fact that there was little to no documentation on the API's and how the App was built.
It all existed in one engineer's mind. This created a design challenge as to how can we design the experience and hand it off to development in a way that makes sense to both of us.
