Reaching out to see if anyone would be willing to share visuals of their Creative Request Queue / Workflow.
We are revamping our Creative Process Workflow so I am looking for examples of the following:
Hi there, this is a tough one to write out an answer to because it's a lot of info : )
Generally, our creative custom form is fairly basic and we take a deliverable = project approach (programs = campaigns, events, anything that requires many assets) and projects are a deliverable or set of like deliverables (a blog post or a set of banner ads, etc.).
We have 3 creative team PMs that get requests from other business units and convert them to projects, and for marketing/internal creative needs the project owner creates the project but uses the same project template and assigns to studio PMs to process/assign to a resource.
Happy to hop on a call in the near future to explain more in depth if it'll help give you ideas.
Views
Replies
Total Likes
@Madalyn_Destafney, I read your response and had follow up questions for you. Do you require a request per deliverable? Say there was a campaign that needed both Print and Digital deliverables, would your users need to submit 1 request for printed deliverables and then another for digital deliverables or can they indicate all needed deliverables in one request? If the latter, how are you then converting the single request into the individual deliverable projects? Thanks so much!
Views
Replies
Total Likes
It's easier on the requester to submit 1 request for whatever needed/multiple assets. Then the PM or whomever converting can convert 1 issue multiple times into different projects. Just know you'll only ever show 1 resolving object from the issue with the last project it was converted to. So if that becomes an issue for any reporting you'd want separate requests to convert.
Views
Likes
Replies