Why Atlas Did Not Start with Development Right Away
Diese Meldung ist noch nicht übersetzt und wird deshalb auf Englisch angezeigt.
When creating a digital product, it may seem logical to move to development as quickly as possible: write the code, build the first screens, and demonstrate the result.
Atlas took a different approach.
Before starting development, the team first determined how the system should work as a whole: which functions it would include, how they would be connected, what data would be required at each stage, and what path the user would follow.
This makes it possible to identify in advance where one part of the system does not align with another, where data is missing, or where the user scenario is interrupted. Addressing such issues at the design stage is significantly easier than after they have already been implemented in code.
This is particularly important for Atlas: the future platform is intended to bring together multiple processes and work with a large amount of interconnected data. Therefore, the objective was not to start writing code as quickly as possible, but first to establish a clear logic for the future product.
Now that this stage has been completed, the project can proceed to the next stage — development.