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
User Journey/Problem Breakdown
Assumptions/Constraints
- 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.
- 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).