UX Designer
Posted on :
17-12-2023
Employer Active
1 Vacancy
The job posting is outdated and position may be filled
Job Alert
You will be updated with latest job alerts via emailValid email field required
Send jobs
Job Alert
You will be updated with latest job alerts via emailValid email field required
Send jobs
Job Description
- Working Location: Hybrid (Onsite: Brussels Belgium and offsite)
- Security Clearance: N/A
- Language: High proficiency level in English language
DESCRIPTION:
WCM is the technical system currently used to support the public NATO website ( ). It includes a hardware component (network infrastructure servers databases IT security devices) a software component (the content management application) and the content of the NATO website (text photos audio design).
The Digital Asset Management system (DAMS) is the media management system that manages processes and stores public NATO multimedia content. It also includes the publication of a selection of the assets to be shared through the NATO multimedia portal ( ) for viewing by any visitor and for download by professional media.
EXPERIENCE AND EDUCATION:
Essential Qualifications/Experience:
Possess a university degree from an institution of recognized standing
Knowledge of and previous experience in the NATO environment is an added benefit
Design of lowfidelity prototypes (wireframes) detailed architecture and adaptation of existing material
Demonstrable experience in UX/UI design projects. (by presenting portfolio of previous related achievements)
Responsible for prototyping and interaction design
Collaborates in defining information architecture
Knowledge of internet protocols and technologies (HTML HTML5 CSS HTTP SOAP).
Desirable Qualifications/Experience:
Knowledge of French language
DUTIES/ROLE:
User Experience (UX)/User Interface (UI) Design
The web design proposed as part of theContent Strategy and Web Design study represented a considerable improvement over the current state of the website but it is somewhat outdated. NATO wants to ensure a long lasting design that is modern serious and provides elegance to the organization. The deliverable therefore is a fresh more uptodate and complete design optionally inspired on the proposed design and based on the concept of mobilefirst.
Scope:
o Analysis of initial information (discovery).
o Sessions to identify UX and design requirements with the PDD team
o Definition of new visual line through new UI Kit
o Definition of new information architecture (to be defined in conversations about the new IA)
o Definition of navigation flows for 5 use cases
o Design of lowfi wireframes in desktop tablet and mobile format of 30 additional screens to those already contemplated in the Figma document
o Highfi visual design in desktop tablet and mobile format of 30 additional screens to those already contemplated in the Figma document.
o Creation of a basic navigable prototype in Figma.
Deliverables:
o Information architecture
o Navigation flows
o Templates/Components design
o Interactive navigation design
o Wireframes (prototypes)
o UI design
o UI Kit
Content strategy and governance model:
Scope:
o Based on existing documentation and after consultation with relevant key stakeholders the Contractor is expected to produce a content strategy enabling NATO to define and to plan the content to be published on the website to identify the target audience to determine when content will be published to strategize how to promote the content to achieve NATO s objectives to define the content lifecycle itself. The content strategy must be a detailed plan establishing how content will be created managed and delivered to meet the goals of NATO s website.
o In addition to the content strategy we expect the Contractor to produce a governance model in order to make the content lifecycle process as efficient as possible and to ensure that the content follows minimum quality standards.
Deliverables:
o Identifying content types and hierarchy of content based on current content and new ideas from staff
o Defining the approach to language versions
o Groups roles and responsibilities: Clearly defining the roles and responsibilities of each member of the WCMDAM team as well as endusers
o Operational process and workflows: Establishing clear processes and workflows for content creation editing approval publishing and removal within WCMDAM system
o Policies and guidelines: Establishing clear policies and guidelines about the type of content that can be published in WCMDAM system as well as about copyright and privacy. Best practice analysis
o Security and access control: Setting up security policies to protect content and ensure that only authorized users have access to the WCMDAM or to specific content
o The following point could be defined as part of the governance model: Training and support: Providing adequate training and support so that users can effectively use WCMDAM
WCMDAM Functional analysis
Scope:
o High level functional and nonfunctional requirements for the new WCMDAM have already been formulated and are the basis for the Invitation for Bid that has been launched. For the Functional Analysis the Contractor is expected to describe how content and assets will be managed in the new WCDAM based on existing documentation and consultation with relevant stakeholders.
Deliverables:
o Templates: define the necessary page types based on the page structure.
o Structure: define the hierarchy of pages and content within the site.
o Integrations: define integration elements and how they will be addressed such as Campaign Monitor FormStack or Social Media.
o Content Type Definition: define the structure and attributes of a specific type of content like Events Articles and Links .
o Components: define the catalog of components to be created based on the delivered design.
o Informational: content is created directly within the component.
o Dynamic: content is retrieved from another source.
o Dialogues: for each component the editing fields and its data type.
o Variations: for each component the possible variations offered.
o Language versions: define how the solution generates language versions of the content to have a multilanguage site
o Common elements: define the elements that can be reused within all or most of the pages on the Website such as the Header or the Footer
o Travel info: define the information that needs to be passed between different pages in a user journey
o Personalization: define the different target audiences and how the experiences are going to be displayed for each of them
o Services: define the modules that are used to extend the CMS functionality for example List of events filtered by date
o Search: define the search capabilities and its filters or facets including how the search can help users in their journey within the website
o Metadata schema: define information about the asset that is stored alongside the asset itself. Metadata provides additional context and information about the content making it easier to manage and organize
o Structure: define the hierarchy of assets within the DAM
o Renditions: define different versions or variations of the assets to make it suitable for specific use cases or devices
o Search and filters: define the search capabilities and its filters or facets
o Technical workflows: define the sequence of tasks or steps that content and assets goes through from creation to publication.
o Integrations: define integration elements and how they will be addressed
Reporting Analysis
Scope:
o Reporting is essential to allow website owners and administrators to gain insights into the performance of the content of the website and the DAM. By analyzing data and generating reports a CMS DAM can help users understand how their content is being used what is working well and what can be improved.
Deliverables: The deliverable must include an overview of the requirements such as:
o Type of report: know what comes "out of the box" or what requires a "custom development" in order to be able to evaluate the effort
o Scheduling: define whether it needs to be generated automatically or manually by the user
o Periodicity: define whether it is required to be generated once or periodic
o Format: define whether needs to be downloaded as a CSV file or displayed on screen
o Governance: define which users will be able to generate these reports
Content migration strategy
Scope:
o The current content migration plan for the website proposes to save time and costs by turning the current dynamic website into a static website so it can still function as an archive for everyone who needs to find some specific content that might not be available immediately on the new website.
o The plan proposes to review the content of the current website and to identify essential key content that must be present in the new website and could be manually (or automatically) migrated as part of training.
Deliverables:
o The goal of this deliverable is to review the plan and to recommend best way forward. In particular:
o To identify a phased migration approach that includes automatic and manual processes depending on content type
o To define key WCM and DAM content/assets for initial migration.
o To establish a quality assurance protocol
o To recommend archiving approach that considers previous static versions already in existence user experience search functionality and new site integration
Analytics
Scope:
o NATO has an important need to be able to measure the usage of the website to understand how users interact with the website but also to identify possible issues.
o Whereas the functional requirements include highlevel requirements such as the implementation of a visitor tracking tool (e.g. Google Analytics & Google Tag Manager) a description of what needs to be measured based on Key Performance Indicators (KPIs) is missing.
Deliverables:
o A report is expected to describe what exactly NATO would like to see reported to determine which information exactly needs to be tracked collected and measured and must include technical documentation such as a data layer concept and a tagging guide
Knowledge of and previous experience in the NATO environment is an added benefit
Design of lowfidelity prototypes (wireframes) detailed architecture and adaptation of existing material
Demonstrable experience in UX/UI design projects. (by presenting portfolio of previous related achievements)
Responsible for prototyping and interaction design
Collaborates in defining information architecture
Knowledge of internet protocols and technologies (HTML HTML5 CSS HTTP SOAP).
Desirable Qualifications/Experience:
Knowledge of French language
DUTIES/ROLE:
User Experience (UX)/User Interface (UI) Design
The web design proposed as part of theContent Strategy and Web Design study represented a considerable improvement over the current state of the website but it is somewhat outdated. NATO wants to ensure a long lasting design that is modern serious and provides elegance to the organization. The deliverable therefore is a fresh more uptodate and complete design optionally inspired on the proposed design and based on the concept of mobilefirst.
Scope:
o Analysis of initial information (discovery).
o Sessions to identify UX and design requirements with the PDD team
o Definition of new visual line through new UI Kit
o Definition of new information architecture (to be defined in conversations about the new IA)
o Definition of navigation flows for 5 use cases
o Design of lowfi wireframes in desktop tablet and mobile format of 30 additional screens to those already contemplated in the Figma document
o Highfi visual design in desktop tablet and mobile format of 30 additional screens to those already contemplated in the Figma document.
o Creation of a basic navigable prototype in Figma.
Deliverables:
o Information architecture
o Navigation flows
o Templates/Components design
o Interactive navigation design
o Wireframes (prototypes)
o UI design
o UI Kit
Content strategy and governance model:
Scope:
o Based on existing documentation and after consultation with relevant key stakeholders the Contractor is expected to produce a content strategy enabling NATO to define and to plan the content to be published on the website to identify the target audience to determine when content will be published to strategize how to promote the content to achieve NATO s objectives to define the content lifecycle itself. The content strategy must be a detailed plan establishing how content will be created managed and delivered to meet the goals of NATO s website.
o In addition to the content strategy we expect the Contractor to produce a governance model in order to make the content lifecycle process as efficient as possible and to ensure that the content follows minimum quality standards.
Deliverables:
o Identifying content types and hierarchy of content based on current content and new ideas from staff
o Defining the approach to language versions
o Groups roles and responsibilities: Clearly defining the roles and responsibilities of each member of the WCMDAM team as well as endusers
o Operational process and workflows: Establishing clear processes and workflows for content creation editing approval publishing and removal within WCMDAM system
o Policies and guidelines: Establishing clear policies and guidelines about the type of content that can be published in WCMDAM system as well as about copyright and privacy. Best practice analysis
o Security and access control: Setting up security policies to protect content and ensure that only authorized users have access to the WCMDAM or to specific content
o The following point could be defined as part of the governance model: Training and support: Providing adequate training and support so that users can effectively use WCMDAM
WCMDAM Functional analysis
Scope:
o High level functional and nonfunctional requirements for the new WCMDAM have already been formulated and are the basis for the Invitation for Bid that has been launched. For the Functional Analysis the Contractor is expected to describe how content and assets will be managed in the new WCDAM based on existing documentation and consultation with relevant stakeholders.
Deliverables:
o Templates: define the necessary page types based on the page structure.
o Structure: define the hierarchy of pages and content within the site.
o Integrations: define integration elements and how they will be addressed such as Campaign Monitor FormStack or Social Media.
o Content Type Definition: define the structure and attributes of a specific type of content like Events Articles and Links .
o Components: define the catalog of components to be created based on the delivered design.
o Informational: content is created directly within the component.
o Dynamic: content is retrieved from another source.
o Dialogues: for each component the editing fields and its data type.
o Variations: for each component the possible variations offered.
o Language versions: define how the solution generates language versions of the content to have a multilanguage site
o Common elements: define the elements that can be reused within all or most of the pages on the Website such as the Header or the Footer
o Travel info: define the information that needs to be passed between different pages in a user journey
o Personalization: define the different target audiences and how the experiences are going to be displayed for each of them
o Services: define the modules that are used to extend the CMS functionality for example List of events filtered by date
o Search: define the search capabilities and its filters or facets including how the search can help users in their journey within the website
o Metadata schema: define information about the asset that is stored alongside the asset itself. Metadata provides additional context and information about the content making it easier to manage and organize
o Structure: define the hierarchy of assets within the DAM
o Renditions: define different versions or variations of the assets to make it suitable for specific use cases or devices
o Search and filters: define the search capabilities and its filters or facets
o Technical workflows: define the sequence of tasks or steps that content and assets goes through from creation to publication.
o Integrations: define integration elements and how they will be addressed
Reporting Analysis
Scope:
o Reporting is essential to allow website owners and administrators to gain insights into the performance of the content of the website and the DAM. By analyzing data and generating reports a CMS DAM can help users understand how their content is being used what is working well and what can be improved.
Deliverables: The deliverable must include an overview of the requirements such as:
o Type of report: know what comes "out of the box" or what requires a "custom development" in order to be able to evaluate the effort
o Scheduling: define whether it needs to be generated automatically or manually by the user
o Periodicity: define whether it is required to be generated once or periodic
o Format: define whether needs to be downloaded as a CSV file or displayed on screen
o Governance: define which users will be able to generate these reports
Content migration strategy
Scope:
o The current content migration plan for the website proposes to save time and costs by turning the current dynamic website into a static website so it can still function as an archive for everyone who needs to find some specific content that might not be available immediately on the new website.
o The plan proposes to review the content of the current website and to identify essential key content that must be present in the new website and could be manually (or automatically) migrated as part of training.
Deliverables:
o The goal of this deliverable is to review the plan and to recommend best way forward. In particular:
o To identify a phased migration approach that includes automatic and manual processes depending on content type
o To define key WCM and DAM content/assets for initial migration.
o To establish a quality assurance protocol
o To recommend archiving approach that considers previous static versions already in existence user experience search functionality and new site integration
Analytics
Scope:
o NATO has an important need to be able to measure the usage of the website to understand how users interact with the website but also to identify possible issues.
o Whereas the functional requirements include highlevel requirements such as the implementation of a visitor tracking tool (e.g. Google Analytics & Google Tag Manager) a description of what needs to be measured based on Key Performance Indicators (KPIs) is missing.
Deliverables:
o A report is expected to describe what exactly NATO would like to see reported to determine which information exactly needs to be tracked collected and measured and must include technical documentation such as a data layer concept and a tagging guide
Employment Type
Full Time
Key Skills
Report This Job
Disclaimer: Drjobpro.com is only a platform that connects job seekers and employers. Applicants are advised to conduct their own independent research into the credentials of the prospective employer.We always make certain that our clients do not endorse any request for money payments, thus we advise against sharing any personal or bank-related information with any third party. If you suspect fraud or malpractice, please contact us via contact us page.
