REVISON PROCESS – LEARNING LAUNCH

CHALLENGE

I lead the Operations of a start-up media company focused in making short movie contents at YouTube.  The start-up company is composed of all remote workers and uses Slack and ClickUp software applications  in communicating updates and project progress.

  The Target: Produce and publish 4 video content each week (1 for each editor).

  The Challenge:  Reduce video revisions up to 1 only to meet the target weekly outputs.

The project scope includes 1 Operations Lead to facilitate the workflow, 1 Production Lead to review and  approve content produced, and 4 Video Editors to create content based on concept direction. All of the  team members are remote workers.

The project should not exceed than 30 business days to have ample time to provide a solution and discover  inefficiencies in repeatative revisions that causes delay in the production output per week.

SELECTION

We have already developed a general guidelines for the video standards, targets, and coordinated with  the Video Editor’s through video conference the problems they are encountering with the process. These  allowed us to gather insights and see from their perspective the bottlenecks that are present with our  implemented guide and workflow.

The common problem gathered is feedbacks are not properly communicated since all the teams are  working remotely compared to face-to-face discussions. This allowed us to proceed to make a learning  launch to test the hyphotetical solution. Additionally as stated in Week 4: Learning a Launch Tool, it is  better to do lots of experiments rather than making a business plan. Simply because learning launches  tests execution and assumptions in a fast efficient way and enables you to pivot in the right direction  based on the output.

APPLICATION

For our initial learning launch, I asked the Production Lead and the Video Editor the usual revisions they  encounter to compile both sides from the approval side and creation side. This will enable both parties to  have transparency and efficiency in the workflow.

We created a table for the Video Editor to input the issues on revision and the Production Lead to put  potential solutions to the issues:

VIDEO EDITOR  PRODUCTION LEAD

REVISIONS ARE NOT DEFINED CLEARLY  INDICATE TIMESTAMPS ON PARTS TO REVISE

REVISIONS INCLUDES PAST REVISIONS ALREADY  HAVE A TRACKING ON REVISIONS ALREADY MADE

NO PROPER COMMUNICATION TOOL IN REVISION FIND A PLATFORM TO CONSOLIDATE REVISIONS

For the next phase of the learning launch, we looked for a software that meets the needs of the Video  Editor and Production Lead. The inputs they gave will be the criteria in filtering the software to use rather  than just picking any video editing or collaborative software based on popularity or ranking.

We have picked Frame.IO as it matches the criteria. It has the following features of setting status for  uploaded videos, creating review links to allow easy access, add comments specifically on timestamps of  the video for clearer feedback, have a separate review panel that consolidates all comments, and  integrates in Slack for any updates or comments placed. We then started onboarding the 4 Video Editors  on how the software functions and to upload their video in it to test improvements in the revision process.

A validation of 0 to 30 days will be applied to check the efficiency of the software and provides the solution  needed.

INSIGHT

Upon application of the learning launch and using Frame.IO, it produced the following results:

  Managed revisions up to 1 as feedback from the Production Lead are detailed and partnered with  visual descriptions supported by the software.

  Video quality of video editors were able to meet the target 4 videos per week (1 video per editor)  as all feedbacks are consolidated, supported with visual timestamps, and defined parts to revise.

In conclusion, this improved the workflow of our video editors and enabled to meet the target content to  publish by 4 in a week. Additionally, this developed the quality of output and foster teamwork and  efficient communication considering the company are all remote employees. We have also maximized the  current technology tools we are using, which is Slack, as a tool to update progress since it seamleslly  integrates with Frame.IO.

APPROACH

Given the outstanding results and improvements we have seen on the execution of te learning launch, we  will use this process and update our general guidelines to document the process for the team’s reference  and for new video editors and production lead that will onboard the team in the future.

A feedback loop will be created to monitor the progress and feedback on the production team and adapt  to new changes as the company grows.

