In joint development with our partner b.i.m.m. GmbH we have developed the construction site software Sitelife. The software solution Sitelife stands for the digital planning, tracking and analysis of construction projects in an interlocking web platform. The modules Documenting and Analysing Basic are already available.
Today in the interview: Product Manager Florian Eschauer on the development process.
What was the most exciting part of the development of Sitelife for you?
I think the most exciting part of the development of Sitelife is still ahead of us, as we will of course develop a lot over the next few years. In the work we've done over the last year, working with a wide variety of construction companies and subcontractors has been incredibly valuable. Evaluating this content, identifying common problems and proposing solutions was the basis for our 3 modules. Combining these in such a way as to create a solution that is complex in itself but remains very simple in application was and continues to be the most exciting part of the development.
How did you decide in product management which functions would be implemented in the software?
Software must solve problems - that is the primary goal and therefore also sets the guard rails in which we move. In addition, at CONTAKT we often talk about "better data for better decisions". I am constantly working to make this promise a reality for our customers. At the same time, it is also the internal yardstick for all decisions made regarding the product.
In the initial software development, the first thing is always to map the basic functionality. This is necessary to be able to start using the software at all. Once this step has been completed, a broad-based feedback gathering process begins to find out where there is a need for improvement. This feedback is analysed in detail, the underlying problems are filtered out and based on this, new functions are designed and then also developed.
Of course, there are other influencing factors in addition to customer feedback, such as our vision or strategically important functionalities, but the same applies here: First create a good database and use this as a basis for prioritisation. So I don't so much decide what to implement, but rather focus on setting priorities, which more or less automatically lead to the prioritisation of functions.