Financial data warehouses are an important tool for most financial services providers today since they have to deal with several business domains and different fields of knowledge. To address complexities in the context of design processes that involve multiple heterogeneous social worlds, Bergman et al. (2007) introduced the concept of design boundary objects with four essential features to improve and promote design conversation. Given the lack of methodology or guidelines that could help both researchers and practitioners understand how the four features are implemented and integrated in specific design boundary objects, we investigate the so-called Data Requirements Tool, an artefact for storing and monitoring negotiated requirements in financial data warehouse projects. We found that the implementation of four essential features into the tool was a repeating process, with shared representation as a basic feature of design boundary objects. As a result of our analysis we propose a set of guidelines for the better development of design boundary objects in complex settings such as financial data warehousing projects.