The text discusses strategies for avoiding authentication system lock-in, which occurs when an organization becomes too deeply invested in a third-party vendor's service and finds it difficult to switch. To avoid this, developers can insulate their application by abstracting the vendor's SDK with a generic interface, making it easier to re-implement the integration if needed. Additionally, having a backup plan involves identifying alternative solutions and keeping them in mind during design and decision-making, factoring in potential future migrations into the budget. This approach allows for more deliberate and robust system design, making it easier to switch vendors or build an authentication system in-house if necessary.