Prototype

https://www.figma.com/embed?embed_host=notion&url=https%3A%2F%2Fwww.figma.com%2Fproto%2Fp9SN0k1ol4rZYulDGNdQNJ%2FAvo-Design-Challenge%3Fnode-id%3D27%253A14%26scaling%3Dscale-down

Starting the brief

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/1eabcd61-e4e9-4ec7-b46d-dc7725d9928f/Starting_the_brief.jpg

User Journey/Problem Breakdown

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/eb5665da-a978-4a8e-81bd-ecde3ef3c22b/Image_4.jpg

Assumptions/Constraints

  1. In my understanding, Avo is mostly first used by the Product Managers, Founders (Technical/Non-Technical), Business Analysts to create events, before it reaches the technical team for viewing/discussion. Therefore, I wanted to make it easy to use and make the technical terms identifiable so anyone using it could understand it.
  2. Data Sources (could change/increase in the future) have to map to Destination (could change/increase in the future, will be edited more often than Data Sources).