RWD design process reference & resource guide initiatives
Role: Visual designer & information architect, RWD guinea pig, documentarian, and SME/trainer
Problem: Some processes are tedious and change over time, so I initially began creating word doc reference for myself, then shared with my team. Regardless of sharing reference, I often found myself handling urgent tasks for others, or repeating demonstrations for other teams.
Solution: As I moved through our new RWD design and implementation processes, I began documenting and maintaining explanatory process reference guides, including two videos for training new teams.
Ultimately, the combination of wikis and videos (below) allowed me to easily and concisely share and update reference without requiring further explanation.
The reference guides are hosted on searchable wiki pages that include related documents and downloads for ease of sharing and discoverability
The wikis include reference for working with environment managers, content implementors and developers, and parameters for visual quality assurance to ensure design fidelity in production. I also developed a role-based orientation guide for optimizing team dynamics (see below).
Outcomes: The reference enabled others to be independent and productive, and allowed me to concentrate on my work. On several occasions I was contacted by people who found the wikis which made me aware that they were being used, and gave me opportunities to refine the reference. I presented these guides in our Design Standards team's educational series for team training and evangelizing of our design system.
RWD design process video guides
The step-by-step videos below demonstrate image optimization using Adobe Generate and ImageOptim, and use of workflows in our content management system (Adobe Experience Manager) for creating responsive breakpoint images, retina and non-retina displays.
I also analyzed and compared results of our image optimization process using Adobe Generate and ImageOptim software against Akamai, a potential compression vendor and concluded that our process was at least comparable if not better, especially relative to cost of the service.
RWD team dynamics: Process analysis, recommendations for role-based orientation
After completing the first series of legacy page conversions to responsive components, I compiled detailed observations and concerns about working with teams who are new to AEM and the RWD process to set expectations and provide guidelines for interaction prior to the business team setting priorities.
I specifically addressed the importance of Design being in a position to lead and moderate the process, that content writers should guide business, and I outlined points of awareness for designers, business leads and producers, content writers, and content implementers.
I identified common recurring conflicts and gaps in awareness and recommended pathways for resolution. Considerations include role-based orientation sessions to prevent conflicts, flexible collaboration with writers to adapt responsive components and content as business requirements change, parallel communication with content implementors to anticipate such changes, and recognition of development bugs that producers might mistake for design production errors.