Does anyone not use a request queue?

We have several teams that don't use request queues. They only kick off new projects and it works fine. I would only say use a request queue if they need to keep a log of "pending" requests that aren't ready to be projects yet. 

Hello,

We bypass request queues and have project managers create projects utilizing a project template. 

A project manager will select the appropriate project template for their marketing channel. Once they select the template, we have them fill out the project brief, provide the Planned Completion date and supply any supporting documents.

Once the project manager is ready to kickoff the project, they will change the status to Current.

Once the status is Current, our traffic operations team will review the timeline and make the appropriate creative assignments and do quick review of the brief.

Once the traffic team is done with their step, the creative team will begin the work. Throughout the project, the traffic team will work with the project manager and creative team to update any timelines if there are any roadblocks or project issues.

We have been doing this for the last 4.5 years and have not run into any issues.

Please direct message me if you want to connect further.

Thanks!

We don't use queues to request projects, but thats just the tip of the iceberg.

We use queues to request Workfront support, process change requests and scope changes, request article permissions, stock art and video buys, payment for guest apearances on video and communications, spend approvals from Finance, approvals on internal and non-billable projects, request new vendors, clients and users, and a ton more. Request queues are a HUGE part of what makes Workfront a great product. Don't ignore the power of asking for something!

Our department handles a mixture of project types, and they get into WF through various methods:

• Our creative services work and other ad hoc jobs are submitted through a request queue; a portion of our Ops team then converts the requests to projects, assigns users to job roles, etc. 
• Large-scale learning initiatives/certificate programs are assigned to a dedicated PM within Ops; that person meets with the project team to determine needs/specifics and then creates the WF projects with the appropriate workflows (project creation has been largely manual thus far, but we will likely start using kickstarts for initiatives containing a high volume of similar projects).
• Learning products included in our annual plan (which traditionally get updated every year and number in the hundreds) are bulk-uploaded through a kickstart.  These projects use set workflows that are templated.  We also use reporting and Fusion to make bulk updates to these projects (e.g., add cross-project predecessors, make task assignments, etc.).

In all cases, it's the Ops team members creating the projects.  It's easier to have a dedicated group of staff who knows WF reasonably well handle this work (rather than have the individual product owners or pipeline teams worry about this).

Can I ask what you mean by "manage it"? What is it that queues allows you to manage that you think might be lost from the point of view of creating projects only?