Programming and software development · ENGLISH
Service page for projects serving Bogota. Separate journeys, permissions and states so the application explains each step. In Bogota, products with several modules need clear distinctions between frequent tasks, permissions and pending states.
01 · CONTEXT
In Bogota, products with several modules need clear distinctions between frequent tasks, permissions and pending states.
02 · PRACTICAL BRIEF
Implementation, architecture and maintenance
Describe the problem, intended users, what exists today, technology constraints and one example of the expected result. Do not share passwords; arrange temporary access only when needed. Before finalising the brief for Bogota, confirm with the people involved: In Bogota, products with several modules need clear distinctions between frequent tasks, permissions and pending states.
A map of screens, roles, permissions and loading, success, empty and error states.
Walk through key tasks for each role and check its states and permissions.
03 · METHOD
Implementation, architecture and maintenance
04 · ANSWERS
Separate journeys, permissions and states so the application explains each step. A map of screens, roles, permissions and loading, success, empty and error states.
Share expected behaviour, users, rules, existing technology and constraints. Do not send passwords; arrange access only if needed.
Walk through key tasks for each role and check its states and permissions.