InfoQ Homepage Collaboration Content on InfoQ
-
How Open Source Enables Collaboration in Creating a Platform
A platform is a collaboration system: platform teams depend on application teams, and both need shared standards. Engineers trust a platform through its predictable behavior, not its features. Being an engineer is about problem-solving and being passionate about it. And being an engineer means sharing your passion for problem-solving.
-
Shifting Platform Development from Projects to Products
A company shifted from project- to product-thinking after their platform outgrew single-team use. The limitations that they felt with their platform were one-off deliveries, lack of product vision, and weak feedback loops. They have moved toward a self-service, API-driven, multi-tenant infrastructure with clearer ownership and better abstractions.
-
Building a European Cloud Orchestration Platform within an Enterprise
Modern cloud deployments involve many tools with different lifecycles, creating a heavy burden on engineers. The Kubernetes ecosystem offers a unified Control Plane approach. Sharing best practices through tech talks and inner-source collaboration can create an engaged community and drive adoption.
-
How Lightweight ADRs and Architectural Advice Forums Can Support Architectural Decisions
How we decide is at the core of architecture, and the architecture advice process is a way to decentralize architectural decisions. It needs to be supported by Architecture Decision Records because of the speed at which technology and systems move, and can be complemented by a weekly architecture advice forum.
-
Scaling Social Systems in Software Organizations
Fast-scaling teams must rebuild trust and psychological safety as their social systems expand. Intentional, redundant communication across multiple formats can keep everyone aligned. Cross-team rituals, buddy systems, and rotating facilitators can reduce silos by building bridges between teams. Leaders accelerate this by modeling the vulnerability they want to see.
-
How to Handle Trust and Psychological Safety When Scaling Organizations
As organizations scale, communication overload, loss of shared context, and trust gaps emerge, Charlotte de Jong Schouwenburg mentioned. Trust must be built team by team; it can’t be replicated. Trust is interpersonal, while psychological safety exists among people and fuels learning. Leaders must deliberately design structures, rituals, and metrics that reward transparency and cohesion at scale.
-
Lessons from Growing a Software Leadership Team
Thiago Ghisi explained how he guided managers and senior ICs to build a resilient leadership group beneath him in his talk Lessons from Growing Engineering Organizations at QCon London. Regular syncs, expectation calibration, and alignment on broader goals made leaders multipliers of culture and performance. Culture is what you do, not what you say.
-
Creating Impactful Teams through Diversity Using Session 0
Diverse and empowered teams are impactful teams, Natan Žabkar Nordberg mentioned in his talk on creating impactful software teams at QCon London. A session 0 helps set expectations and ensures that everyone is approaching the team in a compatible way.
-
Building Software Organisations Where People Can Thrive
Continuous learning, adaptability, and strong support networks are the foundations for thriving teams, Matthew Card mentioned. Trust is built through consistent, fair leadership and addressing toxic behaviour, bias, and microaggressions early. By fostering growth, psychological safety, and accountability, people-first leadership drives resilience, collaboration, and performance.
-
European Initiative for Data Sovereignty Released a Trust Framework
The Danube release of the Gaia-X trust framework provides mechanisms for the automation of compliance and supports interoperability across sectors and geographies to ensure trusted data transactions and service interactions. The Gaia-X Summit 2025 hosted facilitated discussions on AI and data sovereignty, and presented data space solutions that support innovation across Europe and beyond.
-
How to Do Sociotechnical Design Using Domain-Driven Design and Change Smuggling
Domain-Driven Design (DDD) can upskill sociotechnical design to navigate organizational dynamics and decision complexity in human systems. Change smuggling offers a practical way to launch small, safe-to-fail probes, nudging sociotechnical changes to emerge organically and conversationally.
-
How AI with Prompt Engineering Supports Software Testing
AI is becoming a key QA tool, aiding in faster scenario generation, risk detection, and test planning. Arbaz Surti showed how effective prompting using roles, context, and output format helps to get clear, relevant, and actionable test scenarios. AI can boost testers, but human judgment is needed to ensure relevance and quality.
-
DevGreenOps: How to Design Sustainable Digital Services
DevGreenOps, also known as DevSusOps, is an extension of the DevOps approach, in which environmental sustainability considerations are integrated into every step of the DevOps cycle, Jochen Joswig said in his talk at OOP Conference. Applying transparency, minimalism, efficiency, and awareness helps us to design sustainable digital services.
-
Open Practices for Architecture and AI Adoption
Andrea Magnorsky presented on Byte-Sized Architecture at Cloud Native Summit 2025, as a format for building shared understanding through small, recurrent workshops. Ahilan Ponnusamy and Andreas Spanner discussed the Technology Operating Model for AI adoption. Both approaches drew on the Open Practice Library for human-centred collaboration and driving architectural evolution.
-
How Sociotechnical Design Can Improve Architectural Decisions
Sociotechnical design in software development emphasizes creating systems where people and technology thrive by fostering collaboration, emergent coherence, and shared understanding through enabling constraints, leading not only to improved architecture but also to more effective, adaptive, and fulfilling work.