The transition faced significant "under-the-hood" complexity that threatened the project's success:

• Legacy Dependencies: Critical business tools were integrated into the old site without clear documentation, risking total system failure during migration.
• Stakeholder Alignment: Cross-departmental communication gaps led to a lack of clarity regarding how the brand refresh would impact existing user workflows.
• Resource Constraints: A lean team with varying skill levels necessitated a strategy that balanced high-level technical execution with active mentorship.
• User Retention: The "excitement of the new" risked alienating long-term users who relied on the platform’s established functionality.

‍

I implemented a "Documentation-First" approach to mitigate risk:

• Technical Audit: Conducted a comprehensive audit of all current tools, plugins, and third-party dependencies to map out a safe migration path.
• Phased Roadmap: Developed an incremental update strategy to allow for testing and refinement at each stage rather than a "big bang" launch.
• Mentorship Framework: Structured tasks for interns that provided Work Integrated Learning (WIL) value, using their exploratory work to provide "launchpads" for senior developers to execute faster.
• Gap Analysis: Identified where wireframes and user models were incomplete, stepping in to bridge these gaps to maintain project momentum.

‍

I proposed and executed a Phased Overhaul that prioritized stability:

• Architectural Rebuild: Moved away from redundant, "black-box" tools in favor of transparent, documented systems that the team could actually manage.
• Feature Realignment: Restructured the site navigation so that users were naturally funneled to the correct tools on the correct domains, reducing support tickets and confusion.
• Centralized Documentation: Created a "Source of Truth" repository for all CMS tools and integrations to prevent future technical debt.

‍

The transition resulted in a more professional, data-driven digital ecosystem:

• Operational Efficiency: Significant reduction in "unknown" technical dependencies and a streamlined WordPress back-end that the team can now scale independently.
• Team Growth: Interns successfully completed their WIL requirements with tangible contributions, while the core team benefited from the improved documentation and structure.
• Platform Viability: The site now supports incremental improvements without the fear of breaking legacy integrations.

‍

• Leadership vs. Execution: Managing a team while maintaining an operational focus was a major learning curve. I discovered that "leading" often means spending more time on clear communication than on executing designs and features on my own.
• Communication Gaps: I realized that presenting complex technical findings to non-technical stakeholders requires a higher level of conciseness and visual structure.
• Direct Inquiry: A key takeaway was the importance of "going to the source." I learned to bypass departmental silos to get information directly from the stakeholders giving direction and considering opportunities.
• Managing Scope Creep: Facing tight deadlines with incomplete assets and unclear directives taught me the value of ruthless prioritization—focusing on the "must-haves" to ensure a stable launch and ongoing communication cross-departmental communication.

‍