In 2022 I was the UX designer and product manager of a website that was moving from…
- User
In 2022 I was the UX designer and product manager of a website that was moving from Drupal 7 to Drupal 9, which required we rebuild our entire website and in the meantime, it was hard to make any changes to the Drupal 7 site to test new features for hitting business goals because D7 had so much tech debt and broken code. I have some projects we did and I want to get your input
Assistant
It sounds like you navigated a complex migration project while balancing UX, product management, and technical constraints—a tough but rewarding challenge! To provide actionable feedback, I’d love to hear more about the specific projects you worked on. Below are examples of areas where teams often focus during such migrations, along with questions to help you share more details:
Common Migration Focus Areas & Questions
-
User Research & Strategy
- Did you conduct discovery workshops or usability testing to prioritize features for the new site?
- How did you align stakeholder goals (e.g., business KPIs) with technical feasibility in D9?
-
Managing Technical Debt
- What strategies did you use to avoid “fixing the plane while flying” in D7 (e.g., stopgap solutions vs. delaying changes)?
- Did you document D7 pain points to inform D9 improvements?
-
UX/UI Redesign
- Was the D9 redesign a full overhaul or iterative? How did you ensure consistency across old/new systems during migration?
- Did you build a design system or component library to streamline development?
-
Agile Development & Phased Launches
- Did you migrate content/functionality incrementally (e.g., sections of the site first)?
- How did you handle QA/testing when switching between D7 and D9 environments?
-
Content Migration & SEO
- How did you audit and prioritize content for migration?
- Did you implement redirects or SEO tracking to preserve rankings post-launch?
-
Stakeholder Communication
- How did you manage expectations when changes were blocked in D7?
- Did you use prototypes or beta releases to gather feedback during the transition?
General Advice for Future Migrations
- Dual CMS Setup: Some teams run D7 and D9 in parallel temporarily to test features before fully switching.
- Progressive Enhancement: Build core functionality in D9 first, then layer in advanced features as tech debt is resolved.
- Automated Testing: Use tools like Cypress or Selenium to validate critical workflows post-migration.
- Post-Launch Metrics: Track bounce rates, conversion rates, or load times in D9 to prove ROI of the migration.
Next Steps for Feedback
To dive deeper:
- Share a specific project (e.g., “We redesigned the homepage for D9 to improve conversions”).
- Describe what worked well and what challenges persist (e.g., “We struggled to align dev timelines with UX testing”).
- Mention any metrics you measured (e.g., reduced page load time, increased engagement).
This will help me tailor advice to your unique context! 🚀
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.