Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Fine-tuning your Creative Production Workflow -- Creative Operations Essentials


Published on

When you're managing high volumes of visual assets through a Work-in-Progress (WIP) flow, it's important to diagram, document & analyze your creative production workflow so you can identify bottlenecks and begin to improve.

In this presentation you will learn:
- Assessing the workflow you have
- Finding points for improvement
- Tools to help you along the way (from point solutions to B2C software and enterprise DAM software)

Guest speaker: Brian R. Stuckey, Senior Product Manager @ globaledit.

Watch the full webinar here:

This slideshow is part of a "Creative Operations Essentials" webinar series brought to you by Globaledit, the online SaaS platform that empowers creative professionals to manage visual production at scale. You can CAPTURE, REVIEW, APPROVE, MARKUP, SHARE, ARCHIVE your digital files all within Globaledit.

More information about globaledit:

Published in: Software
  • Login to see the comments

Fine-tuning your Creative Production Workflow -- Creative Operations Essentials

  1. 1. Fine-tuning your Creative Production Workflow Brian R Stuckey! Senior Product Manager! at globaledit!
  2. 2. About globaledit Globaledit is the online SaaS platform that empowers creative professionals to manage visual production at scale.! CAPTURE. REVIEW. APPROVE. MARKUP. SHARE. ARCHIVE. All within globaledit.!
  3. 3. Overview •  Mapping Your Process! •  Finding Points of Improvement! •  Implementing Change!
  4. 4. 1. Mapping Your Process
  5. 5. Why Map? •  Visualize a complex process! •  To clearly communicate it to all team members! •  It’s a way to help everyone understand the process and to check if everyone has the same mental model !
  6. 6. Mapping Benefits •  Inefficiencies and problems become obvious! •  Quickly spot patterns in usage! •  Great tool for training new employees! •  Basis for a company/team standard!
  7. 7. How to Map •  Take an asset-centric view of your process! v  Follow an image from camera to archive! •  Document each step and write down! v  What does each step do?! v  Who does it?! v  How are data passed between steps?! v  What tools get used?! v  How long does it take?! What? Who?
  8. 8. Sample Format Step Name! Who! How Are Images Transferred! Tools! Duration! Selects! The images from set go though a second round of review! David Jones! USB Hard Drive, Contact Sheets! Adobe Bridge! 15 Min! Description! Markup! Images are printed out and drawn on ! Angus Young! USB Hard Drive,! Printouts ! Pen & Paper! 30 Min! Retouching! Modifying the image per the markup instructions! Saul Hudson! USB Hard Drive! Photoshop & Capture One! 8 Hr!
  9. 9. Completed Map
  10. 10. 2. Finding Points for Improvement
  11. 11. Improving Steps in the Process •  How are steps communicated?! •  How are images hand off between steps?! •  Do people specialize in tasks? ! •  Is it possible to consolidate tools?!
  12. 12. Improving the end-to- end process •  How large are the units of work?! •  Where are people doing rework?! •  What is overall team load?! •  Where is the bottleneck?!
  13. 13. Simplified Workflow
  14. 14. Example: Bottlenecks
  15. 15. Example: Bottlenecks
  16. 16. Example: Bottlenecks
  17. 17. Example: Bottlenecks
  18. 18. Example: Bottlenecks x! x!
  19. 19. Summary: •  There will always be a bottleneck! •  Find it & reduce its impact! •  Update your map! •  Find the next bottleneck & repeat!
  20. 20. 3. Making
  21. 21. Take a holistic 
 approach •  Whole process from capture to completion! •  Focus on throughput (reducing bottleneck impact), not pain of any individual step! •  Expert Mode: A Linear Programming model can help you optimize the entire system vs. individual steps!
  22. 22. Keep it agile •  Team mindset of continuous improvement! •  Review impact of changes with your team (retrospective)! •  Take on smaller units of work (or divide up larger tasks in to smaller ones)!
  23. 23. Use the Scientific 
 Method 1.  Establish Baseline (the map)! 2.  Make one change (bottleneck)! 3.  Measure outcome (quantify)! 4.  Compare to baseline ! 5.  Accept or reject change (update map)!
  24. 24. Brian’s Rules: •  Take on bite-sized changes! •  Measure your work! •  Update the workflow map! •  Keep a list of changes your team wants to make! •  Never stop making changes!
  25. 25. Thank you!