Make a Clean Handoff Between Design and Development When Implementing Adobe Experience Manager
When an organization embarks on the redesign of their customer experience across digital touch points, it often finds that it will need to re-platform on a modern digital experience management solution. Adobe Experience Manager does this and delivers the vision for compelling customer experiences across channels.
Design teams typically spearhead the full-scale redesign of the customer experience, while IT teams oversee the re-platform. It is critical to promote a smooth transition of a project from experience design to platform implementation.
Here are some tips for promoting a smooth transition. It is crucial to ensure the design team and IT partners a clean handoff between creative and technical development processes.
Bring People Who Know About Adobe Experience Manager Into the Design Process
User experience redesigns often revolve around the needs of the users and the desires of designers. Sometimes experienced design teams will take a purist approach. In this case, only considering site design and layout in the context of users and design. Doing this intentionally removes platform considerations from the process.
With enough coercion, Adobe Experience Manager and web technology can be bent to do just about anything. But, it is not recommended if you are concerned about managing a timeline, budget, and/or complexity.
Download Blue Acorn iCi’s Complete Customer Experience Report to learn how to create an unforgettable, personalized customer experience.
For enterprises launching a new experience on Adobe Experience Manager, it is highly recommended that someone knowledgeable about Adobe Experience Manager review the emerging designs. This review should be during the wireframe stage to discuss the implications.
By reviewing wireframes, you may be able to point out small changes in the designs that could have a big impact in reducing cost and complexity for implementation. Doing this, you could prevent a negative impact on front-end user experience.
Know When to Start Development
There is one recurring question that commonly arises from both the design and IT departments. Within a complete site redesign and re-platform project on Adobe Experience Manager, when can development begin? Usually, it is safe to begin the design and development efforts when the design team finalizes user experience (UX) wireframes.
An implementation team will then be able to discern the overall site structure, navigation, and inventory of Adobe Experience Manager templates and components. The team will be able to leverage these templates and components either out of the box, extended, or developed.
With wires in hand, a worthy implementation team should be able to create an implementation and rollout plan. Even while the design team works on user interface (UI) design, back-end work can begin in parallel. This work may include: setting up environments, firming a build process, configuring Adobe Experience Manager, and building base templates, components, and integrations.
Write Requirements for User Experience and Author Experience
This is a big one. In traditional web experience projects, requirements created against UI designs focused on the user interaction and back-end integration. When writing requirements for Adobe Experience Manager, it is critical for design and implementation teams to recognize that there are two interfaces for which an experience needs to be designed.
There is of course the front-end user experience, the flashy one that gets all the glory. There is also the authoring interface accessed by business users within the enterprise. Adobe Experience Manager provides a powerful and flexible authoring interface for content authors to produce and publish web experiences, and it needs to be considered when writing requirements.
When writing those requirements in the creative and technical design portion of a project, pay attention to authoring terms. For each Adobe Experience Manager component that will need to support the front-end, consider the requirements from three perspectives: front-end user experience, back-end integration, and author experience. Doing so will ensure that Adobe Experience Manager is more than a CMS for rendering content to users. It will ensure that Adobe Experience Manager becomes a toolset that designers need to drive their design outcomes.
Blue Acorn iCi Can Help
When implementing Adobe Experience Manager, it can be difficult to have a smooth transition between design and development. Blue Acorn iCi has plenty of project experience dealing with Adobe Experience Manager and would love to help with any issues or concerns you might be experiencing.