InfoQ Homepage Collaboration Content on InfoQ
-
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.
-
How Empathy-Driven Platform Teams Can Support Software Development
Building empathy and understanding for product developers help platform teams figure out where to draw the boundaries of their scope to provide better support, Erin Doyle mentioned in her talk about empathy-driven platforms at InfoQ Dev Summit Boston.
-
How Inclusive Leadership Can Drive Lasting Success in Tech Organizations
Inclusion isn’t something you do once; it should be woven into everything, from how you make decisions to how you structure teams and run meetings.. When people feel seen and heard, they contribute more fully and meaningfully, which sustains long-term success. Matthew Card gave a presentation about leading with an inclusive-first mindset at Qcon London.
-
How to Develop Your Skills to Become a Principal Engineer
Becoming a principal engineer requires more than technical skill, it’s about influence, communication, and strategy. Success means enabling teams by shaping culture, Sophie Weston said. She suggested developing deep skills in multiple domains, with collaborative skills. Skills from life outside work, like sports, volunteering, or gaming, can add valuable perspective and build leadership potential.
-
How a Sociotechnical Approach Can Help to Deal with Complexity
Today’s software professionals navigate a maze of technical, business, and social complexity. According to Xin Yao, thriving in this environment requires more than just technical and business expertise. We need fluency in decoupling systems for maintainability, reconnecting them for business value, and working with the messiness of organizational dynamics.
-
Using Social Drivers to Improve Software Engineering Team Performance
According to Lizzie Matusov, technical drivers like velocity offer an incomplete view of team performance. Social drivers—trust, autonomy, purpose, and psychological safety—provide a fuller picture and reveal important areas of opportunity for improvement. She spoke about the social drivers behind high-performing engineering teams at QCon San Francisco.
-
Cultivating a Culture of Resilience in Software Organizations
Resilience helps individuals and organizations respond to challenges. Personal resilience is built through adapting, technical resilience by mastering a variety of tools, and organizational resilience through flexibility and strong networks. In fast-changing software industries, recognizing tech shifts and fostering learning, flexibility, and collaboration, enhances resilience.
-
Learnings from Working with Programming Rules and Guidelines
Programming rules and guidelines improve code consistency, but misapplication can lead to poor results. Arne Mertz suggests that software developers selectively adopt rules and guidelines, and document deviations with clear explanations. They can discuss their experiences in communities or during their daily work, to foster collaboration and improve code quality without unnecessary bureaucracy.
-
How Data Contracts Support Collaboration between Data Teams
Data contracts define the interface between data providers and consumers, specifying things like data models, quality guarantees, and ownership. They are essential for distributed data ownership in data mesh, ensuring data is discoverable, interoperable, and governed. Data contracts improve communication between teams and enhance the reliability and quality of data products.
-
How to Do National Language Adaptation in C++
As customers take on a more active role in national language adaptation, the process should be simple, using tools they are familiar with, Daniela Engert stated in her talk at NDC TechTown. They decided to use GetText in C++ where they provide tools and procedures for their customers to provide translations.
-
Enabling Fast Flow in Software Organizations
Resolving impediments to flow and removing unnecessary sources of cognitive load can make culture issues disappear in organisations, Nigel Kersten argued. Start with a clear strategy that is easy to communicate, then follow the path to creating stream-aligned teams and platform teams, he suggested.