The capability of “enabling” includes objectively evaluating use case ideas, implementing them into prototypes and following a highly iterative process of testing and adapting these solutions.
One of the most popular reasons why data-driven projects fail, is that the organization’s maturity level and therefore readiness to be guided by data do not fit the plans. It is critical to prepare the organisation and to establish a culture that is open for business insights gained from data. Obviously, this requires buy-in and a strong commitment from top management. One procedure that has shown itself to be effective is to engage management in a workshop session that translates predefined business objectives into guidelines. Whereas business objectives are strongly tied to existing strategic objectives as well as the nature of the business, guidelines represent the organization’s interpretation of these objectives and its intent on how to reach the objectives. Ultimately, solid guidelines form a code of conduct that helps everyone involved to decide how to act and react.
In order to establish a corporate culture that embraces data as a guiding instance, the design and prototype team needs to be truly interdisciplinary. Depending on the nature of the initiatives to be started, include representatives from different business functions in your ideation and scrum teams. Mix people from customer-facing functions, such as marketing, sales and product owners, with functions that indirectly influence customer interaction, such as IT and customer service. This mix of perspectives takes account the fact that trust as a complex psychosocial construct is always influenced by a broad set of factors. The perception of trust is, for example, highly influenced by the way data is collected, the nature of the data collected itself and the way data is ultimately used by an organisation (Nguyen et. al., 2013). Furthermore, the clues that build trust as described in the iceberg model differ in their effectiveness depending on the target group. Whereas a strong brand, for example, is highly effective for “digital natives” (younger, experimental digital customers born after 1980) and “naturalized digitals” (middle-aged, highly educated users), it shows less of an effect for “digital immigrants” (older, mostly passive users). The later audience, however, gives more weight to reciprocity – to a transparent exchange of information for appropriate compensation (Hoffmann et al., 2014). Please visit www.iceberg.digital for more details on how the consumer’s mind works and how trust is built.
As a result of the first capability described in this article, the understanding of trust issues and opportunities, a set of ideas has been created using design thinking techniques. These ideas need to be translated into use cases. Use cases show the aim and the subsequent objectives of a solution and the assigned actors by expressing a list of steps and interactions among them towards a common goal (Matz, Germanakos, 2016). It is recommended to keep these cases as simple as possible; they must be readable and understandable by all project stakeholders, sponsors and the end-users.
Usually, this process so far produces a colorful bouquet of interesting ideas. A major next challenge is to apply an effective and most necessarily objective evaluation logic to prioritize the cases for further implementation in prototypes. Far too often the ideas originating from politically important business stakeholders are preferred to other cases that would yield a better result. All use cases should be equally evaluated along dimensions such as complexity (or feasibility, or cost), expected benefit and strategic fit. In addition, the guidelines discussed previously, as well as the provisions from the governance model, need to be considered to build a shortlist of the most promising use cases.