41st FVI Expert Breakfast

Topic: "When projects fail not due to the plan, but due to collaboration" – Why relationships, leadership, and communication are often more important than the perfect project plan.

The focus was on a technically well-prepared large-scale project that stalled due to new contacts, unanswered emails, and differing goal images. A joint workshop, concrete agreements, and a later reality check brought the project back on track: It was completed ahead of schedule, production started without errors, and success was celebrated together.

• The relationship level determines the factual level: The central thesis was: "The factual level must follow the relationship level." Conflicts rarely arise solely due to technical details. It is usually about trust, recognition, different perceptions, and the question of who gets to be right. Instead of selling one's own view as the truth, I-messages and the acknowledgment of different perspectives help.
• A shared project vision is more important than another project plan: Operators, suppliers, and construction management initially focused only on their own goals: maintaining production interruption, installing technology, securing deadlines. Only a joint workshop revealed what was truly important to the participants. The agreements fit on two flipchart sheets and were reviewed two months later – a pragmatic intervention with a significant impact.
• Project management means empowering rather than controlling: Micromanagement was described as the "death formula" of successful project work. In long-term projects, project management should provide an overview, remove obstacles, protect the team, and delegate responsibility to the lowest qualified level. In real emergency situations, however, a clear hierarchy and quick decisions are needed. It is crucial to adapt the leadership style to the situation.

• Methods are tools, not a religion: The discussion about agile and waterfall showed: Scrum, sprints, or classic milestone planning do not work automatically by following a textbook. When solutions are unclear, agile principles can promote motivation, self-organization, and quick course corrections. In clearly defined industrial projects, a classic approach may be more suitable. At the same time, every model requires real resources: Planning project staff at 120 percent capacity already anticipates delays.

Context: Operational intelligence creates the common working basis for successful projects

This episode fits perfectly with our strategy because digitalization fails not due to a lack of technology, just like the described large project – it fails due to media disruptions, lack of transparency, unclear responsibilities, and solutions that do not fit into people's daily work.

• Different levels of information and lack of a common truth: Project participants work with emails, personal notes, Excel lists, and distributed documents. This creates different pictures of the same project. With ADAM, we create a common operational information base. The digital lifecycle file bundles reports, documents, decisions, photos, and work histories in an asset-centered manner. This turns distributed knowledge into traceable operational intelligence that all participants can access in the right context.
• Micromanagement due to lack of transparency: Leaders constantly inquire because status, decisions, and completed tasks are not reliably documented. At the same time, employees perceive additional forms as control and administrative burden. We resolve this contradiction through voice-based feedback, mobile workflows, and no-code processes. ADAM automatically structures information and documents it where it is created. The team gains more autonomy while project management retains the necessary overview – without having to manually control every intermediate step.
• Method dogmatism and risky big-bang projects: Companies often try to fully define processes first, clean up master data, and then introduce a perfect overall solution. This makes projects slow, expensive, and difficult to convey. We work ADAM-First and Brownfield-Native. As a SaaS solution, ADAM builds on existing systems and data. Hybrid search and vector search find information even with inconsistent designations and incomplete master data. Instead of years of preparatory projects, we start with a specific bottleneck, quickly generate measurable benefits, and further develop the solution together with the professionals.

Conclusion: Successful projects do not always need more planning, but a common information base, clear responsibility, and tools that facilitate collaboration – ADAM makes these prerequisites digitally usable in everyday operations.