What is the main purpose of change management during a Workfront implementation?

Question

Options

• ATo minimize user resistance and ensure smooth adoption
• BTo limit system updates and customizations
• CTo prioritize only executive-level training
• DTo reduce the number of users accessing the system

• A
  79% (33)
• B
  12% (5)
• C
  2% (1)
• D
  7% (3)

Explanation

Change management exists to guide people through transitions, and during a Workfront implementation its primary goal is minimizing resistance and driving adoption - because even the best-configured system fails if users don't embrace it. Organizations invest in training, communication, and stakeholder engagement precisely to reduce friction and help users shift their workflows confidently.

Why the distractors are wrong:

• B is backwards - change management actually enables updates and customizations by ensuring people accept them, not limiting them.
• C is too narrow - effective change management targets all user levels, not just executives, since end-users drive daily adoption.
• D contradicts the goal entirely - you want to maximize engaged, capable users, not reduce them.

Memory tip: Think of change management as the "people layer" of any implementation. Technology handles the system; change management handles the humans using it. When in doubt, the answer that centers on people + adoption is almost always right.

No community discussion yet for this question.