A new video solution is being adopted more slowly than the business needs it to be. Which phase/activity most likely caused this issue?

Question

Options

• AOnly Senior management was involved in designing and testing.
• BIt requires the same password criteria as other systems.
• CIt is a standard, corporate application.
• DIt is free, so departments have no stake in its success.

• A
  56% (14)
• B
  12% (3)
• C
  8% (2)
• D
  24% (6)

Explanation

Option A points to a classic change management failure: excluding end users from the design and testing process. When only senior management shapes a solution, the tool gets built for executives' assumptions rather than the actual workflows of everyday users - leading to low buy-in, poor fit, and slow adoption.

Why the distractors are wrong:

• B (same password criteria) - a minor friction point, not a driver of slow adoption; standardized credentials are generally a feature, not a barrier.
• C (standard corporate application) - being standard/corporate has no inherent negative effect on adoption speed; familiar tools often spread faster.
• D (free cost) - while skin-in-the-game matters, free tools remove financial barriers and typically accelerate adoption rather than hinder it.

Memory tip: Think "WIIFM" (What's In It For Me?) - users adopt tools they helped shape because they see their own needs reflected. If only the top floor designed it, the ground floor won't use it. Slow adoption = missing voices during design/testing.

No community discussion yet for this question.