Up to 50% of team time is spent asking or answering questions!

Ineffective knowledge sharing decreases team productivity

Each developer wastes between 6 and 13 hours a week looking for answers to their questions

Each developer spends between 5 and 11 hours per week answering questions from others

Source: Developer Survey 2022 (StackOverflow )

Using Promyze to share knowledge

Without Promyze

Best practices are repeated during code reviews due to lack of capitalization. This increases latency and lengthens delivery times
Knowledge sharing sessions are often unstructured, exchanges are informal, and there is little capitalization
Development guidelines are hardly maintained in wikis, by few people, and very few consulted. It is an individual work with too little impact on the teams
Development teams don't have access to best practices in their daily tools (IDE, code review, ...)
Exchanges around best practices are lost in discussion channels (Slack, Teams, ...)
Best practices remain static and do not come to developers when they write or review source code
Onboarding new people requires a lot of energy to familiarize them with the team's specific best practices
Teams in the same company share few practices, lack visibility, which prevents best practice sharing and reuse

With Promyze

Every code review comment can become a practice in Promyze, capitalizing on this knowledge
During Craft Workshops, the whole team or a community of practice shares knowledge efficiently
All identified practices are recorded and automatically suggested by IDEs and during code reviews to make these practices "living"
IDE and Code Review plugins make it easy to create practices. No more switching tools to update best practices
Every developer is involved in creating best practices, and decisions are made collectively
The Craft Workshops perpetuate a continuous improvement of best practices within the teams
Discovery Workshops and automatic suggestions allow newcomers to quickly discover all the practices of the team and the company
Teams can benefit from and reuse best practices from other teams, to capitalize on the knowledge in the company

Time saved for the teams

On average 70 hours are spent per month per developer asking and answering questions. Promyze makes it possible to structure this knowledge sharing in a much more efficient way. By reducing by 1/4 the time spent by the teams to share this knowledge, Promyze allows an average gain of 17 hours per month per developer.