InfoQ Homepage Collaboration Content on InfoQ
-
How Open-Source Maintainers Can Deal with Toxic Behavior
Three toxic behaviors that open-source maintainers experience are entitlement, people venting their frustration, and outright attacks. Growing a thick skin and ignoring the behavior can lead to a negative spiral of angriness and sadness. Instead, we should call out the behavior and remind people that open source means collaboration and cooperation.
-
What Engineers and Companies Can Do to Increase Social Impact
Engineers in the tech industry have the means for social impact through their network, skills, and experience. Companies can create impact by making business practices socially-minded. Inclusive training considers the circumstances and backgrounds of individuals, with minimum entry barriers to ensure broad participation, including ethnicity, gender, neurodiversity, and socio-economic background.
-
Leading in Hybrid and Remote Environments: Skills to Develop and Tools That Can Help
Leading in hybrid and remote environments requires that managers develop new skills like coaching, facilitation, and being able to do difficult conversations remotely. With digital tools, we can include less dominant and more reflective people to get wider reflections from different brains and personalities. This can result in more diverse and inclusive working environments.
-
Learnings from Applying Psychological Safety across Teams
Applying ideas from psychological safety can enable people to speak up in teams about what they don't know, don't understand, or mistakes they have made. Trust and creating safe spaces are essential, but more is needed. People need to feel that they will not be punished or embarrassed if they take interpersonal risks.
-
How We Can Use Data to Improve System Quality
To understand how systems are being used, we can collect metrics and identify trends over time. The data and insights gained can be used to improve system quality by improving software design or testing patterns.
-
The Myth of Product Mindset: It's What You Do, Not How You Think
Companies nowadays are looking for ways to cultivate a product mindset. While the idea of cultivating a “product mindset” allows us to focus primarily on ourselves, actually transforming our organizations often means changing our behavior to focus on our customers and how we work together to serve them.
-
Motivating Employees and Making Work More Fun
Progressive workplaces focus on purpose and value, having networks of teams supported by leaders with distributed decision-making. Employees get freedom and trust, and access to information through radical transparency that enables them to experiment and adapt the organization. In such workplaces, people can develop their talents and work on tasks they like to do, and have more fun.
-
Establishing Autonomy and Responsibility with Networks of Teams
Working in outdated ways causes people to quit their work. Pim de Morree suggests structuring organizations into networks of autonomous teams and creating meaningful work through a clear purpose and direction. According to him, we can work better, be more successful, and have more fun at the same time.
-
Promoting Empathy and Inclusion in Technical Writing
Empathy is the first step in practicing sustainable, genuine inclusion. If persons or groups of people feel unwelcome because of the language being used in a community, its products, or documentation, then the words can be changed. Identifying divisive language can help to make changes to the words that we use.
-
Trust-Driven Development: Accelerate Delivery and Increase Creativity
By building trust you can break silos, foster collaboration, increase focus, and enable people to come up with creative solutions for products and for improving their processes. The DevOps movement was created to break the silos in the organisations; trust can be built by organising pair programming across various functions and various teams.
-
Transitioning to Modern Testing: How Testers Can Stop Being the Training Wheels for Teams
Traditional testing, where testers act as safety nets and testing is separated from implementation, can have a detrimental impact on quality. Testers can instead act as coaches, collaborate in teams, and foster change, to stop becoming the training wheels for teams. Culture is key, particularly in that the environment provides psychological safety.
-
Trust-Driven Development: Building Cognitive and Emotional Pillars
Trust-driven development uses authenticity to build a safe environment for people to operate. To build trust we need to focus on two main pillars of trust – cognitive and emotional. We need to be brave, have courage, and give people access to our authentic selves.
-
Improving Software Quality with Gamification
Bingo Bongo sessions for bug hunting and playing risk storming games can improve quality. Gamification supports learning, can make everyday work interesting, and strengthen team spirit. Playing games should be part of the daily work at the office and seen as an effective work time. In gamification, a real value is created by the creative process.
-
Using Team-Set Salaries for Company-Wide Compensation
Team-set salaries (TSS) can be scaled up by doing appraisals across teams where results are automatically calibrated. The scores indicate where conversations are needed. TSS encourages people to learn new skills and adapt.
-
Creating Tight Cohesive Tech Teams for Women to Thrive
Women in tech need a dynamic, valuing team, stimulating work, push and support, local role models, nonjudgmental flexibility, and personal power. Tight cohesive teams can provide high-quality interactions, making people feel valued.