Our thinking model for designing digital solutions

As mentioned in the introduction to this blog series, our projects are characterized by a high degree of flexibility in our approach and methodology. We are always guided by the following thought model:

Firstly, we examine three distinct levels based on business engineering methodologies. The design of a digital solution, which primarily occurs at the "processes" and "systems" levels, must be developed with a strategic approach and align with the corresponding target systems. An effective solution should also present new strategic opportunities for business development.  

In order to ensure a holistic and interdisciplinary approach to finding solutions, our work and discussions always consider three perspectives:

• Customer perspective
• Business perspective
• Technology perspective

Insufficient consideration of this holistic approach harbors the risk of ultimately failing the solution due to user acceptance, internal resistance, obstacles, or technical feasibility.

By consistently combining and coordinating both models in our work, we develop digital solutions in collaboration with our clients that deliver long-term value.

Definition of the specific procedure

In most cases, the solution cannot be designed completely freely and from scratch as part of an order or project. In practice, our conceptual work with customers typically begins with an existing, preliminary concept of the solution or product vision. This means that we are faced with a number of preliminary considerations, existing materials, and framework conditions that are, to some extent, fixed. 

To define the procedure, it is essential to first determine a preliminary position within our conceptual framework. In doing so, we address the following questions: 

• What are the maturity levels in terms of the strategic basis, existing processes and organization, and the system landscape?
• To what extent should the solution be based on the existing system, or how much freedom is there for changing processes, responsibilities or new systems, for example?
• What preparatory work and artifacts exist at which levels?
• What perspectives were taken into account for this preliminary work and to what level of detail?

The responses to the above questions will help us determine the content-related entry level and identify the topics and artifacts that still need to be developed from the three perspectives mentioned. In the event that the strategic basis is either absent or lacks sufficient maturity, it would be prudent to prioritize these strategic topics before designing a solution.  We are happy to support you with our experienced consultants and architects and our strategy approach. However, this is not the focus of this blog series.  

In the next blog post, I would like to discuss how we divide the conceptual work into "rough concept" and "detailed concept" and what artifacts we develop in the process.