-
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 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 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 Alignment Without Mandates
Building alignment within an organization or team is crucial for success, but achieving it without relying on mandates can lead to more authentic, sustainable collaboration. Mandates often come with a top-down approach that may create compliance without true engagement or understanding. In contrast, building alignment organically fosters a sense of shared purpose, promotes ownership, and
-
Building AI that respects emotional independence
Designing AI systems that respect emotional independence is a crucial aspect of creating ethical, user-centric technology. Emotional independence refers to the ability of individuals to maintain their sense of emotional autonomy and not be overly influenced or manipulated by external systems, including AI. When AI interacts with users, it must support their emotional needs without
-
Building AI that promotes user reflection and growth
Building AI that promotes user reflection and growth involves creating systems that prioritize introspection, encourage self-awareness, and facilitate personal development. Such systems can guide users in understanding themselves better, helping them make thoughtful decisions, and fostering growth in both their personal and professional lives. Here’s a breakdown of how this can be achieved: 1. Integrating
-
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
-
Building AI that adapts across emotional and cultural boundaries
Building AI systems that can adapt across emotional and cultural boundaries requires a deep understanding of human behavior, diverse cultural contexts, and the ability to respond with empathy, respect, and sensitivity. AI needs to be designed to navigate the complexities of emotion and cultural differences, ensuring that users from various backgrounds and emotional states feel
-
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
-
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