If you decide to sign up for a project with Mayk Ideas, it is crucial for the project team to discuss and finalize the project scope and deliverables BEFORE starting the project. While some changes to the project scope are inevitable in longer-term projects, sudden shifts in the scope of a three-week project do not make sense. Mayk's project sponsor (COO in our case) lacked a clear vision on how the project activities could best serve the “agreed” project charter. Riipen Project Team had to spend extra time and effort to help Mayk understand their needs. Mayk’s project sponsor insisted on using video recordings with no transcription as the sole means of communication. The videos lacked focus and they were self-contradicting in many cases. The project team's multiple requests for a live meeting and proper use of email and MS Teams chat were ignored. Mayk's Project Manager (first point of contact) attempted several times to handle the project professionally, but Mayk's project sponsor tempted to reverse or overrule his decisions or approvals. The company clearly has issues with distrust in delegation of authority, internal miscommunication, and excessive micromanagement. When we submitted our final presentation for Mayk’s approval, the project sponsor masked over 80 percent of slides with orange boxes, claiming that they include confidential information! We delivered a full data analytics project including the development of standardized input template, fit-for-purpose data model and data analysis, data visualizations and dashboards as well as data-related documentations. However, we eventually were forced to use open-source data from public domain to present our work to our peers! The Riipen Project Team handled the situation professionally in collaboration with Riipen admin team and project’s academic coach. We eventually applied our technical knowledge and business skills to provide Mayk with a prudent solution. The main surprise was that we had signed up to learn from “best practices,” but we learned a great deal from “bad examples” in the project.