Expert Authors or Authors who are Experts?

David Nedohin Community moderator

• November 24, 2023 18:08

Here's a question I'm curious about how people view it.  As you move out of a POC and prove value, how is your organization looking at scaling?  There are a 3 ways that I have seen the question approached, so would love to hear your thoughts.

1. Internal authors who become "experts at WorkLink".  When there is a use case that AR could be applied to, the business could leverage these authors.  One of their primary roles would be authoring AR content.
2. Some organizations want their experts at a specific task (ie. Mechanical Engineer who designs the part or system, as an example), to be the ones who author the AR content.  This means that they would likely only use WorkLink Create for a small % of their job, but in this situation, the company wants the people who know the equipment or process best, to be the ones who author the instructions.
3. Outsourcing.  Some organizations simply don't want to author their own content, so they outsource to either Scope AR Creative Services team or another external content creation company.  In some cases this is easier and more scalable for rapid content creation.

Do your organization lean more on one of these approaches, or something different altogether?  Love to hear about it and why.

0

• 

  Andrew Hale

  • November 30, 2023 00:07

  Hey David, Community-

   

  Our company is large, with each of our major products having it’s own internal business structure.

   

  I think the best way to scale would be a blend of the first two bullet points.  Our best projects have come from close collaboration between product expert and WorkLink author.  An author can’t usually do much without the product expert’s information, and the expert can’t do much 3D work without the WorkLink expert.

   

  I’d love to have a core team of dedicated xR experts who are skilled in WorkLink and 3D data preparation, acting as a hub for each product group’s xR projects.  The core team would train one or two product experts from each division how to use WorkLink.  Those product experts could take care of all basic WorkLink development needed for their products, while also continuing to support products.  The core xR team would handle bigger picture stuff like CMS, complex projects, general WorkLink projects not related to products, improving workflows, managing style guides, and adding spice to the most important projects.

   

  I hope y’all find my opinions helpful, and I look forward to hearing others!

   

  Thanks,

   

  Andy

  1

Please sign in to leave a comment.