-
Building Architecture Around Business Moments
In any business, architecture serves as the foundation upon which operations, decisions, and growth are built. It is not just a technical framework but a way to strategically structure systems and processes that align with business goals. But how can businesses create an architecture that is flexible enough to evolve with changing demands while staying
-
Building Architecture Communities of Practice
In modern organizations, especially those with a focus on technical disciplines like architecture, the creation and nurturing of Communities of Practice (CoPs) can be an essential part of organizational growth and development. Communities of practice allow teams to share knowledge, improve practices, and solve problems together. For architecture, this becomes especially important as the discipline
-
Building Better Dependencies Through Team Dialogue
In software development, dependencies are a fundamental part of system architecture. They connect different parts of the system, from libraries and frameworks to APIs and third-party services. While dependencies are necessary, they can also introduce complexity and risk. The key to building better dependencies lies not just in identifying them but in fostering open, ongoing
-
Building Consensus Without Sacrificing Quality
Building consensus in a team or organization is critical for ensuring alignment and collaboration, but it can sometimes lead to compromises that undermine the quality of the final outcome. Striking the balance between consensus-building and maintaining high standards is essential, especially in technical, creative, or strategic settings. Below are strategies for building consensus without sacrificing
-
Building Design Ownership Through Repeated Dialogue
Building design ownership within a team is a key factor in creating high-quality systems that are well-aligned with both the business objectives and technical constraints. Repeated dialogue is a powerful tool to achieve this, as it fosters continuous communication, deepens understanding, and strengthens commitment to the design decisions. The following explores how repeated dialogue can
-
Building Facilitation Capacity Across Engineering Teams
Building facilitation capacity across engineering teams is an essential aspect of creating a collaborative, productive, and innovative environment. As the complexity of modern software and system design grows, the need for effective facilitation increases. By empowering engineering teams with the skills and mindset to facilitate, organizations can unlock higher levels of communication, alignment, and problem-solving.
-
Building AI that aligns with feminist technology values
Building AI that aligns with feminist technology values involves integrating principles of equality, justice, care, and inclusivity throughout the design and implementation stages. Feminist technology values aim to address power imbalances, challenge traditional hierarchies, and create systems that prioritize marginalized voices. Here’s how these values can be translated into actionable design choices: 1. Inclusive and
-
Bringing Emergent Design to Legacy Systems
Emergent design is a software design approach that emphasizes flexibility and adaptability in response to evolving requirements and feedback. This strategy, often applied in agile environments, focuses on allowing design decisions to unfold gradually as the system is developed, rather than committing to a rigid architecture upfront. When applied to legacy systems, emergent design can
-
Bringing Product and Engineering into Technical Dialogue
Effective collaboration between product teams and engineering is crucial for building successful products. Bridging the gap between these two distinct areas can be challenging, but fostering a technical dialogue between them is essential for aligning objectives and ensuring both teams work toward the same vision. Here’s how you can bring product and engineering into a
-
Bringing the Big Picture to Daily Standups
In agile environments, daily standups are often seen as quick check-ins for the team to report on progress, roadblocks, and plans for the day. While these brief meetings are effective for tracking individual progress, they sometimes miss the opportunity to align the team with the broader vision or long-term goals. Bringing the big picture into