Conception of digital solutions – Part 1

Our Conceptual Model for Designing Digital Solutions

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

Conceptual Model

First, we look at three different levels, based on business engineering methods. The conception of a digital solution, which mainly takes place on the “processes” and “systems” levels, must be based on a strategic basis and pay into the corresponding target systems. A good solution should also offer new strategic options for business development.

Next, we always take three perspectives into account in our work and discussions in order to ensure a holistic and interdisciplinary solution:

  • Customer Perspective
  • Business Perspective
  • Technology Perspective

Insufficient consideration of this holistic approach carries the risk that the solution will ultimately fail due to user acceptance, internal resistance and obstacles, or simply technical feasibility.

By consistently combining and coordinating both models in our work, we develop digital solutions together with our customers that create sustainable added value.

Definition of the specific procedure

In most cases, the solution cannot be designed completely freely and from scratch within the framework of an order or project. In practice, we usually start the conceptual work with our customers with an already existing, rough idea of the solution or a product vision. This means that we are confronted with various preliminary considerations, existing artefacts and more or less fixed framework conditions.

In order to define the procedure, it is therefore essential to make a rough assessment of the current situation within our thinking model in advance. In doing so, we deal with the following questions:

  • What are the maturity levels in terms of the strategic basis, existing processes and organization, and the system landscape?
  • How strongly should the solution be based on the existing system, or how great are the degrees of freedom , e.g. for changing processes, responsibilities or new systems?
  • What preliminary work and artifacts exist on which levels?
  • What perspectives were taken into account for this preliminary work and in what level of detail?
Definition of Actual Status

The answers to the above questions serve to determine the introductory level of content as well as the topics and artefacts still to be worked on from the three perspectives mentioned. If the strategic basis is completely missing or has an insufficient degree of maturity, it is advisable to focus on these strategic issues before designing a solution. We would be 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.

Contact