Programming and software development · ENGLISH
Service page for projects serving Medellin. Plan modules and roles so new features do not disrupt the experience. For Medellin, catalogue and enquiry journeys should keep their context from search to detail and contact.
01 · CONTEXT
For Medellin, catalogue and enquiry journeys should keep their context from search to detail and contact.
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 Medellin, confirm with the people involved: For Medellin, catalogue and enquiry journeys should keep their context from search to detail and contact.
A modular map of features, roles, integrations and boundaries between product areas.
Verify each module has a clear responsibility and does not duplicate another feature.
03 · METHOD
Implementation, architecture and maintenance
04 · ANSWERS
Plan modules and roles so new features do not disrupt the experience. A modular map of features, roles, integrations and boundaries between product areas.
Share expected behaviour, users, rules, existing technology and constraints. Do not send passwords; arrange access only if needed.
Verify each module has a clear responsibility and does not duplicate another feature.