The Project Process


We start any project by planning. We will collaborate on any number of visual references to ensure we are all on the same page before we start development. This may include the creation of any of the following:
  • Visual references – Especially in graphic work, we may compile sources of inspiration for a project. We may collect images of a certain art style to help guide our design process.
  • A/V scripts – Here, we take a script that you have provided and place it in a 2-column format, where we match each piece of text with a written idea for a visual to match it. This is a great planning tool in narrated video or animation work
  • Storyboarding – Similar to an A/V script, we use storyboards to help plan the visuals for a video or animation project. In a Storyboard, we create a visual walkthrough of how the video will progress. Graphics put into a Storyboard are always placeholders and may not be very detailed, as this tool is a temporary reference meant to be adjusted up until production begins.
  • Brand styling guides – Depending on the project, we may also work together to develop a brand identity. This includes defining a clear color palette and font scheme for all elements within the project, be they website banners or title cards for videos.


In some projects, we may develop a prototype that we will use as a reference for future pieces of the project. For example, if we are developing a series of modules, we will first create a prototype layout to help define the visual style of the modules. As with other project elements, this prototype will be reviewed and receive your feedback before being finalized. The goal of having a prototype is to establish a consistent guide for how the rest of the project should proceed.

Once a prototype has been approved and finalized, it should not be changed. If a request to change the design defined in the prototype happens later in the process, a great deal of rework will be necessary. This may distract from other project tasks and will affect the team’s ability to meet the agreed deadlines.


It is recommended for most projects to have a weekly meeting between yourself, your technical lead, and any other important contributors. This allows for regular progress updates between all members and helps to hold a dedicated space for the project in amongst your other work.

Asynchronous communications may happen via email or over Microsoft Teams. The scope of your project will likely determine what the best method is. For example, if you are working on a large-scale projects with many stakeholders, Teams is a great option for keeping everything organized. If your project is smaller scale and does not require external consultation, email might be a better path.


When we have completed a draft piece of a project, we will share it with you for review. You will then be asked to provide feedback so we can make necessary changes. This may happen synchronously in a meeting or asynchronously using an external tool. Some tools that you may be expected to use include:
  • Miro (Storyboards)
  • Adobe Asset Review (Graphics)
  • Vimeo Review (Video or animation work)
  • Review 360 (Articulate modules)
Review periods will also come with deadlines. It is important that you strive to review content before the date provided by the ITRC to keep the media development process moving along.


As stated, the best projects have all their content ready before the ITRC begins any work. If you are developing content parallel to the ITRC’s media development work, you will be expected to meet agreed upon deadlines. If you cannot meet content deadlines, your technical lead will reassess how the changed deadlines affect the scope of what we can complete with a shortened amount of development time.