The art of knowledge sharing

Connector 

Although Lucas is indeed an important connector in our ecosystem, he also sees an important role for the members of the Conclusion Architecture Board (CAB). This is the collective of CTOs and knowledge managers from all Conclusion companies in the ecosystem. The members are also connectors. Through the CAB, connections are made between all companies in terms of content and craftsmanship.

Getting to know each other, sharing knowledge 

You often hear Luke say: "Getting to know each other lays a foundation for sharing knowledge. The fact that people get to know each other and know how to find each other at a later time is the most important. That is why initiatives such as Conclusion on Stage, an event where every colleague can take the stage, are so incredibly important. But also Conclusion Sport, Youngclusion and our monthly drink. By the way, sharing knowledge is multiplying knowledge. If you share your knowledge, there will only be more knowledge".

The importance of knowledge sharing 

Lucas: "The Conclusion ecosystem consists of more than 25 different Conclusion companies. This means that knowledge about a specific topic is often fragmented. In a lot of companies, it is often individuals or small groups who are engaged in certain activities around a specific subject. Everyone has a piece of the puzzle about how best to approach things. Everyone has a bit of experience and everyone is looking for how to do better. It is difficult to keep up with developments on your own. Specialists often have no or few other specialists within their own organization to spar with. If you bring all those specialists from all Conclusion companies together, you suddenly have a large group of colleagues who can strengthen each other enormously."

Guilds at Conclusion

In guilds, colleagues meet each other who are professionally involved in the same thing. In recent years, various guilds have emerged within Conclusion: groups of specialists. For example, we have an Architecture guild, an Azure guild, an Agile guild, an AI guild and a Design guild. Lucas explains why people join a guild: "First and foremost because they like to tell each other and learn from each other. There are people who come to guild meetings because they would like to transfer their experience and expertise to colleagues, but there are also people who mainly want to learn. The connecting factor: everyone is enthusiastic about the same substantive subject." 

Not primarily commercially driven

What drives us to bring these people and their knowledge together? Is it because we want to be ahead of the market? Lucas: "Personal development is also an important one in this. People want to get better at their profession. But also sharing their story and working together." According to Lucas, a guild is not primarily commercially driven: "If opportunities arise from the contacts that are made, that's great, but it is primarily for the people themselves." 

Lucas: "The moment you come together around content, your specific background actually disappears. The fact that you are from company A or B and that those companies are sometimes even each other's competitors no longer matters."

Coordinator of the guilds

Lucas: "I do feel like the facilitator of the guilds. Together with the Conclusion Architecture Board. And if someone wants to start a new guild on a theme, I would like to support him or her. But in the end, it's mainly about knowing each other. Making knowledge is and will remain the basis for sharing knowledge."