What do we mean by a concept?
Generally speaking, a concept is the mental abstraction of an idea, a category of things or of real processes around us. Through the process of abstraction, a model of what we want to look at and understand is created. This transforms things that we cannot immediately grasp at the outset into something real or tangible. This step of concept formation is often the biggest hurdle when it comes to transforming a project idea into a working business model. That is why many initiatives do not go beyond the idea. This is exactly where we want to support you and take you further.
Why do we need a concept?
In the beginning there is an idea, a realization or a certain insight. This is usually the easy part of the story. Before we start investing money in the realization of an idea, we want to be as sure as possible that the investment is worthwhile, that it is viable. Just as you don't build a house without having a plan, you won't commission a software development or make a specific purchase without knowing exactly what you are doing it for. This is where the concept comes in. It is the blueprint on which everything is based.
Only when you have this plan you can share it, demonstrate it, test it and improve it if necessary. Once this plan is accepted, all subsequent steps of a realization are based on it. This helps to avoid bad investments.
And what do we mean by concept development?
In the context of developing a business model or redesigning a process organization, the following core aspects come into consideration during concept development:
- A clear definition of the initial situation and the goals to be achieved
- An operational model (the "target operating model") of the envisaged solution
- Boundary conditions to be fulfilled and applicable or possible constraints
- Possible design leeway that does not impair the intended operational goal in its effect, but can positively influence the design of the solution
Procedural view of concept development
From a more procedural perspective, concept development can also be summarized this way:
- Analysis and conclusions: Analysis of the current initial situation in order to obtain a well-founded inventory of the ACTUAL situation. Subsequently, the appropriate conclusions are drawn in order to describe the desired target situation.
- Design: Development of an operational model with which the formulated goals can be achieved.
- Test and evaluation of the model: Considering the applicable constraints and limitations, the new model is tested and evaluated for its practical applicability and, if necessary, adapted. Typical constraints include available time, budget, in-house personnel in terms of availability and skills, available or maximum lead time ("time to market"), available communication channels, accessibility of the target audience, legal constraints and applicable laws, etc.
- Prototype development (optional): visual design of a possible implementation based on simulated screenshots and user interactions.
Once you have gone through these steps, you also have a solid and trustworthy starting point for the actual implementation of a project idea. The concept development we support and outline here is to be seen as an extended consultation that looks at your situation from a comprehensive perspective.
