Exploring the implications of tech teams functioning without ideal principles outlined by Cagan and Ries.Challenges arise when tech teams lack autonomy and are merely given pre-designed solutions to execute.In such scenarios, tech teams receive a Business Requirement Document (BRD) and are expected to adhere to it strictly.Strategies for effective operation under constraints, akin to playing ice hockey without skates, are discussed.The role of the Product Manager shifts towards ensuring engagement and adoption when design autonomy is absent.Agile practices are crucial for effective product development due to the unpredictability of tech solutions.Mitigating the damage of limited autonomy involves assessing inherent risks and adapting strategies accordingly.Including tech specialists in the design process is crucial for innovation and optimal solution design.Adhering strictly to BRD might hinder value delivery, emphasizing the importance of understanding the 'why' behind project requirements.A lack of autonomy not only limits tech teams but also reshapes their roles and priorities.