Visualization in process-oriented organizations is becoming increasingly more important for better decision making. This case study explores the design process of an IT company's dashboard software and the software requirements of its client. Based on our results and literature review we propose a control chart design module to incorporate in the dashboard that visualizes organizational variation in an interactive way. We found that user participation was considered very important by the developers but not implemented during early stages of development and that fictional clients were developed to when the project had no real clients. This was due to intermittently insufficient resources being put into the project, lack of clients and lead developers moving to other projects. We propose that developers make a preliminary study, market analysis, have an even flow of resources and not develop to fictional customers. Developers developing client specific software attributes also need to have a thorough understanding of the customer's needs before development starts in order to not create unnecessary software features.