Translating requirements to app interactions
Based on the requirements we listed in the previous section, our app will have two primary views:
- A summary view for reviewing the updates in the meeting
- A personalized view for the owners to facilitate easy updates
The summary view should allow for navigation to drill into the details and, depending on the setup, this navigation can have multiple levels. In some cases, you may even want to build an alternate view with different navigation for the same set of data.
For example, while the summary view can be created to track and review updates on organization goals or OKRs, the other view could be created for reviewing the same information in the context of different teams due to a many-to-many relation between the organizational goals and team deliverables. It is possible that a single team can deliver many goals, and many teams can deliver a single goal.
In some organizations, viewing a summary at the OKR level...
