This Master Thesis looks into software development processes and the work activities these need to support. Hesitation against process support within Software developing organisations combined with a possibility to develop process support for such a company, made the foundation for this thesis. The reference company where the study took place is a large worldwide Telecom company where we focused on one design department with 25 people. Instead of using Participatory Design (PD) [Schuler, Namioka] as a method for Software development as traditionally, we used it for developing process support together with the people at the department. Three different supports for different project processes were created with PD and an evolutionary way of work together with the ?designers?. We came to a complex project environment which required control in several aspects such as project sponsoring, project management, line management, design maintenance etc. We saw a way of working that was following a common agreed way of work by the group that is formed by socio-emotional aspects and co-learning aspects [Hägerfors, 1995]. In contrast to this, the study showed that the available process support and also the use of the process support had a clear concentration towards a management focus ? the control function. The available process support and the use of this did not really consider the aspects of Socio-emotional or Co-learning. Existing process support was built around documents that became evidence for actual activities during the project. The process support developed during this study (by us and the designers) finally also got that concentration. A conclusion is that when the organisation puts high requirements on control of projects, this will also affect the way the organisation wants support for work. This is the missing point.