Using Design Thinking to Navigate a “Lift and Shift” Enterprise WordPress Project

  • Define: Catalog the opportunities presented by a new system and the challenges extant in the legacy system. Here we want to pay special attention to areas of the user experience that are constrained by limitations in the backend CMS.
  • Ideate: The classic design thinking paradigm calls for blue-sky thinking — really crazy ideas. Here, we question parts of the frontend that are tightly coupled to the legacy CMS, and parts of the backend that could be streamlined. When preserving the frontend directly in an enterprise migration, it’s tempting to coax WordPress into behaving more like the legacy CMS.
  • Prototype: We quickly build a WordPress experience and manually add in some content so that editors can see and feel what it will be like to work in the new system.
  • Test: We frequently return to our users for feedback to ensure that our solutions are meeting the needs we isolated in the definition stage.
  • Implement: Once we’re satisfied with the direction of the CMS implementation, we finalize the data migration pathway and launch the site.

--

--

We are strategists, researchers, designers, and developers who craft digital experiences for publishers, nonprofit institutions, museums, and brands. alley.co

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Alley

Alley

We are strategists, researchers, designers, and developers who craft digital experiences for publishers, nonprofit institutions, museums, and brands. alley.co