Almost every week, new experts join different departments, bringing new insights to the team. These may include better ways to solve problems, or new technologies they have been exposed to or developed in previous roles. These new team members are eager to leave their mark, and startups desperately need that input. Therefore, these ideas may be implemented in a short period of time with little regard for the overall system impact. Not only that, but very few processes are deployed in the environment and change procedures are still in their infancy. In such an environment, changes are not uniform, making it extremely difficult to keep track of the latest design revisions.
In contrast, traditional OEMs have established efficient and rigorous change management processes. These processes have been optimized through years of projects and have high organizational support. Not so in startups. Change requests will continue to be generated regardless of the freeze date or the current project stage.