End User’s Input

“Everybody who’s been successful has gotten lots of help and input from many, many people.”

– Carol S. Dweck, Author of “Mindset: The New Psychology of Success”

The Project Team was excited that the project was almost completed. Then, they were surprised when they presented it to the End Users and there were major concerns. Those who would be using the completed product had not been consulted throughout the Life Cycle of the project and were not happy with what would be delivered.

This is, unfortunately, a common scenario when executing a project or initiative. Executing a deliverable without End Users’ input can create unnecessary issues in the success of the completed project.

Involving the End Users throughout the project’s Life Cycle increases the probability of a successful execution. Why?

  • The results of the execution effort align with the business needs being addressed
  • Reduces wasted time, energy, and resources on rework created due to a deliverable that does not meet the End Users’ needs
  • Addresses the “they versus us” mentally that is caused whenever the Project Team and End Users are able to work together to achieve a unified goal
  • Encourages a more successful and timely execution of the project/initiative  
  • Creates ongoing collaboration between the Project Team and the End Users

When should the End Users be involved?

  • During the Requirements Phase of the project’s design
  • At critical milestones of the project
  • As Testers of the desired outcome

The success of any execution requires involvement by those who will benefit from its implementation. Aldridge Kerr can help your organization more clearly define the End Users’ requirements and needs. We use a proven facilitated methodology to define the requirements needed for a successful execution.

Leave a Reply

Your email address will not be published.