Managing a Design Project in a Classified Environment: Working Within Information Security Constraints Without Slowing the Pace

Managing a design project within a classified system poses challenges that don't exist in a regular tech project. Strict information security rules limit who can see the screens, where they can be worked on, and which tools are permitted. Meetings that require many stakeholders turn into an exercise in complex logistics, and at times physical meetings at the client's facilities are the only ones approved. In the projects I worked on for the Ministry of Defense, the success of on-schedule delivery hinged on the ability to plan every milestone in advance in a way that accounts for the security constraints. Instead of improvising, we built a detailed timeline that factors in the extra time required for every approval, every meeting at the facility, and every stage of clearing a portfolio of work. In addition, we developed a hybrid working methodology: intensive work in the classified environment at key points, and independent work in a regular environment on non-sensitive elements (such as a generic component library, a general design system). This separation cuts down the time wasted on waiting and bureaucracy, and lets the project team advance on both fronts in parallel. For project managers leading projects in classified or heavily regulated environments, the insight is this: invest in detailed upfront planning that accounts for all the constraints. The time "wasted" on planning at the start of the project is saved fivefold down the road. Anyone who tries to run fast and crack the security on the fly — falls down halfway through.