A pilot that misses the demanding user group
A fictional organization plans a Citrix rollout for office staff, engineers and contact-center employees. Its pilot uses ten office employees at headquarters with managed laptops. All can launch a desktop and use email. The project report declares that the design is ready for everyone. Engineers, however, use a graphics-intensive application and a specialist USB device. Contact-center employees use a supported softphone, work from two locations and have strict audio-quality expectations. Some contractors use unmanaged endpoints. The assessment has no agreed acceptance measures for these groups, no recorded peripheral compatibility test and no evidence from the second location. Management wants a practical way to close the design evidence gap without rewriting the entire project or treating one successful administrator-style launch as proof of every user experience.
1. What does the pilot establish, and what does it not establish?
Read the worked answer
It provides limited evidence for the tested office workload, endpoints and location. It does not establish graphics/peripheral compatibility, contact-center audio quality, unmanaged-endpoint capability or the second location's experience. Define the untested requirements and avoid extending the result beyond its sample.
2. Recommend a focused next pilot and a traceable decision record.
Read the worked answer
Add representative engineers, contact-center workers and contractors with their real supported devices and network paths. Agree observable acceptance criteria, test required capabilities and record results, risks and design decisions. Change only the affected design elements, with a rollback and support plan.