UX/ui & GRAPHICS
INFORMATION DENSE CONTENT
This is an experiment in Design, Digital Delivery, and Information Rich Content. The focus is to use Agile and Cloud based UX/UI tools to build a digital publication for consumption online, on demand, and on multiple devices. Tools for visual prototyping and brand cohesion include:
We gathered a decade worth of content from multiple sources that included Word documents, PowerPoint presentations, online data repositories, SCORM compliant online courses, and current online publications.
The team consisted of a security officer, a designer, and a web developer.
Use established and mature platform. We chose Chrome, Safari, and Apple/Android mobile devices.
Our phased approach was to get clusters of information, curate visualizations for data representation, for legibility, and for visual impact. The team proceeded to build on two-week sprints to a fully completed product.
MOSCOW: Design - User
PACT: Design - Developer
All end users and their managers who are curious or required to understand digital security.
Any organization that has requires critical annual and ad hoc delivery oversight for sensitive and personally identfiable information.
We define a persona so the whole team understands the why and the what. The design and management team get to understand the intentions of the application and the necessary features and functions. But it all starts with a user and a persona helps the team understand the user's mission, mental state, environment, and expected experiences.
An Aware Colleague
This user has been working with sensitive data, in a security scrutinized workplace, on specialized computer and software. They are reminded with every conversation and click about security. They are not the average person because they work as trusted advisors and their customers want them to be flawless. Paper and email reports do not visually impress them and they want to interact digitally.
By highlighting visually what is new and what has changed.
Focus on Content
As a supplementary source of information that is searchable and readily available in a centralized location.
Access on Demand
Deliver content across devices and get notifications on updates instead of a scheduled annual event.
An Aware Colleague
We met weekly in person and online to brainstorm, explore, discover, and finally decide on the range of epics we wanted to build on. During these meetings, the team reviewed the stories, graphics, sample data from their Apple Watch use, and discussed their data and the visuals on their Apple iPhones. We built the sprint plan, sprint backlog, estimates and the commitment to complete the beta version of the prototype. Task lists were determined and updated at each meeting to identify the sets of work effort that needs to be completed by a specific member of the project and for interdependencies.
Sprint durations were two weeks. During these two weeks, we limited changes to the duration and deliverables of the sprint. During the sprint we have the following Agile artifacts:
- User Stories that capture features, options, functionality, and requirements of other types from interviews with end-users and system owners. These stories also integrate into test cases and map to specific iterations;
- Task Lists identify the sets of work effort by person and interdependencies.
- Bug Lists that clearly define logical and system errors identified by error logs, compiler output, and testers;
- Workbooks that assign bugs, issues, and tasks to specific personnel during specific iterations;
- Task-boards, Storyboards, and Dashboards that track and display all the artifacts, progress, and status; and,
- Reports that offer a static view of any particular moment in the project.
We used Jira and Github for our Continuous Integration/Continuous Deployment (CI/CD) pipeline to match our expertise in automated CI/CD in AWS. The backlog comprises user stories with features, options, functionality, and requirements and test cases.
- Sprint Review:
During our reviews we were able to demo their completed UI/UX and coding tasks for continuous improvement.
- Sprint Retrospective:
We discuss what went well, what could be improved and selected action items for further improvement of the process.
Before and After
The material changes based on the security posture of the enterprise but the lessons need to be delivered to users as they perform at their work sites and during telework times. The online publication is far more accessible and allows for update delivery mechanisms that are not in productivity software and content.
Integrating into an online course, with online surveys, and history tracking are beneficial to security leaders and management.