[Event Recap] WUG Seattle | Workfront Intake - September 15, 2026

Thank you to Becky Barus, Workfront Champion, for joining WUG Seattle to share how she approaches intake. This was the first session in our year-long series on the end-to-end content supply chain, and intake is where that chain starts.

Attendance: 25

What Becky covered:

• A clean request process has five parts: one place to ask, a form that adapts to the request type, clear categories instead of free text, visible status, and a balance of speed and completeness.
• The requester should feel like they answered a few clear questions. The taxonomy, routing, and governance live in the architecture they never see.
• How a request moves: queue, topic group, queue topic, custom form, routing rule, then an issue assigned to a team for triage.
• Not every request becomes a project. If it needs a plan and multiple parties, convert it to a project. If it’s a one-shot answer, resolve it as a request.
• Intake needs owners, not just configuration: intake teams per topic, limited edit rights on the taxonomy, maintained request types, and defined SLAs.
• Intake reporting covers volume by request type, turnaround time, status, and assignments.

On AI: Workfront’s AI form fill already lets a requester paste a prompt or upload a document and review the fields it proposes. Becky also shared where she sees intake heading, including auto-complete from history, AI-assisted triage, and completeness review. Her reminder: required fields and routing still have to be completed, or the teams doing the work receive incomplete requests.

Thanks also to Olya Kollen, Workfront Champion (WorkFocus.io), who offered to help answer Planning questions from the group.

Recording: https://youtu.be/iIsH_hhzopw

Next in the series: project kickoff and triage. January 2027

Not a member yet? Join WUG Seattle on the Adobe User Groups site to get notified of new events.

Chris Lew and Scott Adams