Collaboration
63 bites tagged Collaboration — interview questions with model answers, and 60-second explainers.
Design System Steering Committee: Governance in Practice
A steering committee is the board of directors for a design system, ensuring its long-term stability and direction. They set technical standards, manage releases, and resolve conflicts. The footgun is becoming a bottleneck if not diverse and well-chartered.
Driving Design System Adoption
A design system's value isn't in its components, but in its use. Drive adoption by creating collaborative feedback loops with users through interactive workshops and dedicated office hours.
Figma Team Libraries: A Single Source of Truth
Think of a Figma Library as a shared box of official LEGOs for your team. It ensures everyone uses the same approved components, styles, and variables, keeping designs consistent. The biggest footgun is forgetting to publish changes to the main components.
The RFC Process: Formalizing Technical Decisions
An RFC (Request for Comments) is a formal document for proposing a major technical change, creating a public record of the decision. It's used for big shifts like adding a new design system component or changing a core API.
Design System Office Hours: Your Team's Live Support Channel
Design System Office Hours are a live support channel for your users. They're great for answering questions, unblocking teams, and gathering feedback as adoption grows. The main footgun is inconsistent promotion, which leads to empty, ineffective sessions.
Contribution Guidelines: The Rulebook for Your Design System
Contribution guidelines are the rulebook for evolving a shared design system, defining who can add what and how. They're essential when multiple teams need to contribute without chaos.
GitHub Flow: A Simple, Branch-Based Workflow
GitHub Flow is a simple workflow where `main` is always stable and new work happens on a feature branch. It's used for continuous delivery, from code to documentation.
Pull Requests: A Structured Conversation About Code
A Pull Request (PR) is a structured conversation about a proposed code change. It's used in team projects to review new features and fixes, ensuring quality and sharing knowledge. The footgun is treating PRs as a rubber-stamp approval instead of a real review.
Distributed Version Control (DVCS): Everyone Gets a Copy
A DVCS gives every developer a full, independent copy of the repository, history and all. This is Git's model, making commits and branches instant because they're local. The footgun: your local copy isn't the team's truth until you push and pull to sync.
Swarming: The Team Tackles One Thing at Once
Swarming focuses the entire team's effort on a single work item to finish it fast, rather than having everyone work on separate tasks. Use it to unblock a critical feature or push the most important story over the finish line at the end of a.
Obeya: The Project 'War Room'
Think of an Obeya as a project's 'war room,' a space for visualizing work to make fast, informed decisions. It's used in lean and agile settings to align teams on strategy and surface problems. The footgun is treating it as a status meeting room, not.
ATDD: Aligning Code with Business Needs Before You Build
Acceptance Test-Driven Development (ATDD) is a communication framework where business, developers, and testers write acceptance tests together *before* coding begins. This ensures everyone understands the requirements.
Mob Programming: The Whole Team on One Computer
Mob programming is like pair programming for the whole team: everyone works on one task, on one computer, at the same time. It's used for complex problems or onboarding. The footgun is letting it become a passive meeting instead of an active collaboration.
Pair Programming: Two Heads, One Keyboard
Think of pair programming as a continuous code review. One developer (the Driver) writes code while the other (the Navigator) reviews it in real-time. This is often used for complex tasks or onboarding. The footgun is letting one person dominate the keyboard.
T-Shaped Skills: Deep Expertise, Broad Collaboration
T-shaped skills describe a professional with deep expertise in one area (the T's vertical bar) and the ability to collaborate across others (the horizontal bar). This is vital in agile teams where cross-functional work is constant.
Get Collaboration bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.