I recently became a Creative Workflow Specialist here at Adobe. In this role, I spend a lot of time working with customers, helping them understand how Adobe’s diverse technologies knit together as an end-to-end content development to syndication to monetization to measurement platform. I also spend time learning about how customers have developed their own workflows using our tools, and that is the subject of this post.
In almost every meeting I attend, Bridge appears as a critical part of the workflow. This was the intent of Bridge when it was released back in the day, but it amazes me at how differently people use the same tool. Some use it simply as a file browser. Others use it for managing metadata on assets. Still more use it to interface with their Digital Asset Management (DAM) system. I have even encountered customers who built custom plugins for Bridge to allow users to interface directly with the company’s project management and product lifecycle management solutions. Wow!
I want to thank everyone who responded to the survey that I had posted here earlier in the year. We have completed our information gathering and have presented our findings in another blog post. To all of you who responded (and there were a LOT of you who responded), thanks for your insights, and keep on being creative!