Usability professionals seldom get a chance to actually do their job. Instead, they have to argue that usability is something important that should be attended to. This was the initial problem that motivated this thesis. In spite decenniums of evolution within HCI this problem is still highly relevant, and existing approaches to solve it yet have to prove their effectiveness. When approaches to integrate HCI into systems development have been discussed, there has seldom been a discussion about how a given approach may be more or less useful in different development contexts. Nor has there been much discussion about how HCI activities relates to the overall procurement-development process. One reason for this may be that existing approaches to HCI integration are suited primarily for product development and, to some extent, to in-house development. At least these contexts are most common in existing case studies.

In this thesis, I focus on the problem of HCI integration in contract development. This context poses particular challenges, mainly because two parties with different goals are involved – the procurer and the supplier. They regulate business relations and responsibilities via the contract. In both existing practice and in research the user-centred design (UCD) process has, at least implicitly, been assumed to belong to the supplier side. It is the suppliers, i.e. consultancy firms, that have employed usability professionals and that have tried to integrate HCI into their development processes. By taking a procurement perspective instead, I question this assumption.

I present three case studies that start with a survey of common problems in current procurement practice and end with trying out an approach to work with UCD in systems acquisition. While my interest initially concerned successful HCI integration, I also discuss how the suggested approach deals with several existing problems that procurers face. In particular, the approach links abstract business goals that any systems acquisition starts of with, to detailed systems requirements that it aims at defining. This facilitates for procurers to focus on the goals that the future system should help enable and linking these goals to the requirement specification that the contract is based on.