team-collaboration

7 posts

figma

Sightlines Issue no.1: Insights from Config | Figma Blog (opens in new tab)

Figma’s first *Sightlines* issue distills lessons from Config’s Leadership Collective about leading design, product, and engineering teams in the AI era. Although organizations are still experimenting with AI, core leadership principles remain unchanged: build curious teams, preserve quality, collaborate openly, and rely on human judgment. As AI accelerates production, taste and thoughtful editing become increasingly important differentiators. ## Navigating Leadership in the AI Era - Leaders are still determining how to integrate AI into products, teams, and workflows. - The central challenge is gaining AI’s speed without sacrificing quality. - Many leaders are learning alongside their teams rather than presenting themselves as having all the answers. ## Fundamentals That Still Matter - Strong leadership continues to depend on: - Curious, critical-thinking teams - High standards for craft - Clear judgment about what makes work effective - Leaders are encouraging a beginner’s mindset by: - Starting from first principles - Experimenting with new tools and processes - Prototyping directly with their teams ## Collaboration and Human Judgment - AI tools can encourage isolated, individual workflows, so leaders are emphasizing collaboration more strongly. - Effective practices include: - Open critiques and feedback - Showing work early - Debating outcomes collectively - As AI automates more creation, human “taste”—the ability to judge, refine, and select high-quality work—becomes the key differentiator. ## Lessons from Industry Leaders - Teo Connor of Airbnb argues that an increase in mediocre AI-generated work will make strong editing and creative judgment more valuable. - Jen Dunnam emphasizes designing for people rather than chasing tools, noting that human needs remain constant. - Ian Silber of OpenAI recommends trusting capable teams and accepting that leaders cannot oversee every detail. - Jeetu Patel of Cisco describes meticulous design as a way to demonstrate care and create an emotional connection with customers. The practical recommendation is to adopt AI with experimentation and openness while preserving the human practices that sustain quality: collaboration, critical thinking, empathy, strong standards, and continual cultivation of taste.

gitlab

8 Agentic AI patterns reshaping team collaboration (opens in new tab)

A synthesis of 17 agentic AI platforms identifies eight patterns that help teams work faster, work smarter, and maintain control. The strongest platforms do more than provide capable individual agents: they reduce coordination overhead, embed agents in existing workflows, and provide governance across the software lifecycle. The post argues that integrated team collaboration and managed deployment will distinguish leading AI platforms. ## Eight Collaboration Patterns ### Proactive Status Updates - Agents generate progress summaries from live task data. - They identify blockers, risks, and slipping deadlines before escalation. - Automated updates reduce status meetings and manual check-ins. ### Intelligent Work Routing - Agents assign work based on skills, capacity, and project context. - Continuous workload balancing replaces periodic planning adjustments. - Transparent routing logic lets humans review and correct assignments. ### Team Communication Support - Agents summarize chats, threads, and meetings. - Decisions and conversation history remain available to new participants. - Async summaries reduce repeated explanations and unnecessary meetings. ### Role-Specific Agents in Chat - Specialist agents operate inside tools such as Slack. - They can handle onboarding, IT, sales, and other role-based tasks. - Simple interactions, such as an emoji reaction, can create tracked work. ### Shared Conversational Context - Agents retain awareness of participants, threads, and files. - Teams benefit from knowledge gathered through another member’s prompt. - Shared context prevents duplicated prompting and helps new members continue work immediately. ### Role-Based Access Control - Agents inherit permissions from their assigned identities and roles. - Access controls can apply at the field level, preventing unauthorized reading or actions. - Detailed action logs provide an auditable record for compliance. ### Governed Environments - Agents move through development, testing, and production using managed pipelines. - Sandboxes isolate early development and prevent conflicts. - Controlled promotion prevents untested agents or disruptive updates from reaching production. ### Collaborative Agent Development - Multiple team members can co-own, edit, debug, and maintain agents. - Tiered permissions support shared ownership without removing accountability. - Standardized protocols help agents created by different contributors work together. ## Lessons from the Competitive Landscape - Agents are increasingly embedded in existing communication and work tools rather than isolated portals. - Governance becomes essential as organizations scale agent usage. - Agent development is evolving into a collaborative discipline requiring shared ownership, versioning, and auditing. - The biggest opportunity is reducing the “coordination tax” of meetings, check-ins, and repeated explanations. - Few platforms provide an end-to-end governance experience combining environment grouping, shared catalogs, and managed promotion pipelines. ## Implications for GitLab GitLab’s integrated DevSecOps lifecycle gives it a structural advantage because software delivery workflows, context, and controls already exist in one platform. GitLab Duo Agent Platform is positioned to embed agents directly into those workflows, allowing teams to orchestrate work while agents execute across the software development lifecycle. Teams evaluating agentic AI should prioritize not only agent capability, but also shared context, transparent automation, permissions, deployment governance, and collaborative maintenance.

line

List of Articles for ‘Orchestration Development Workshop,’ an Internal Workshop to Enhance AI Utilization Skills (opens in new tab)

LY Corporation runs the “Orchestration Development Workshop” to help engineers apply AI more effectively in real development work. The workshop focuses on connecting multiple AI tools and agents to amplify creativity through collaborative learning and creation. A related blog series will share workshop topics, beginning with an example of using AI to reduce PR review delays and improve review culture. ## Orchestration Development Workshop - Targets engineers involved in development at LY Corporation. - Emphasizes practical, workplace-oriented AI skills rather than purely theoretical knowledge. - Uses “orchestrating multiple AIs to maximize creativity” as its central theme. - Builds on the idea that organizational learning is essential for successfully adopting AI. ## Blog Series - The series will publish workshop content incrementally. - The article list will be updated as new posts are released. - The listed update date is April 10, 2026. ## AI-Assisted PR Reviews - The first installment addresses bottlenecks and delays in pull-request reviews. - It explains how AI-assisted PR review support can help resolve review stagnation. - It also describes an internal workshop designed to change team review practices and culture. The series presents AI adoption as an organizational and collaborative practice, with PR review automation serving as an initial example of measurable workflow improvement.

datadog

Effective habits of remote workers (opens in new tab)

Remote workers at predominantly office-based companies must be intentional about staying connected, visible, and effective. The author argues that remote success depends less on physical presence and more on deliberate communication, visible engagement, and strong virtual relationships. Clear updates, responsive availability, and active participation help ensure remote employees remain part of the team. ## Overcommunicate to Compensate for Distance - Share frequent updates about progress, milestones, and blockers instead of waiting for formal meetings. - Ask questions openly, including questions that might feel “dumb”; online messages replace the casual help available in an office. - Respond promptly during working hours and clearly communicate your schedule, especially across time zones. - Keep your calendar accurate by blocking off lunch, appointments, errands, and focused work while leaving room for ad hoc conversations. - Prioritize face-to-face communication during video calls over simultaneous messaging. - Treat writing as your remote “voice”: frequent, clear communication makes your personality and engagement more visible. ## Create a Strong Sense of Presence - Keep your camera on for virtual meetings when appropriate, using reliable audio and video equipment. - Use an intentional background—either an uncluttered workspace or a virtual background that reflects some personality. - Maintain eye contact by positioning your camera properly and staying visually engaged, particularly in one-on-one meetings. - Speak up during meetings, ask questions, and volunteer to summarize notes. - In meetings dominated by office-based participants, be willing to interrupt or talk over others when necessary to contribute meaningfully. - Treat your workspace as part of your professional identity. Show personality intentionally, but avoid relying on artificial blur when a clean wall or thoughtfully arranged background works better. ## Stay Connected Despite Working Remotely - Physical distance does not have to mean disconnection. - Remote employees need to deliberately maintain visibility and presence in virtual spaces. - The excerpt introduces the importance of proactively building relationships, though the discussion ends before that section is completed. Remote workers should compensate for the lack of casual office interaction with consistent communication, visible participation, and intentional relationship-building.

datadog

Effective habits of remote workers | Datadog (opens in new tab)

Cody Lee argues that remote workers in office-centric companies must intentionally project visibility and over-communicate to remain effective. By treating digital interactions with the same gravity as physical ones, remote employees can bridge the gap with their office-based colleagues and maintain strong professional relationships. The guide concludes that long-term success depends on the intentionality of one's "digital voice" and the strategic use of periodic in-person visits. ## Prioritizing Communication to Overcome Distance * Over-communicate progress and blockers frequently to ensure teammates are aware of your status without needing to ask. * Ask "dumb" questions openly in collaboration tools to stay engaged and leverage the collective knowledge of the team. * Maintain high availability by keeping an updated calendar with visible blocks for lunch and focus time, mimicking the accessibility of an office setting. * Prioritize face-to-face video communication over asynchronous messaging when active discussions are taking place. ## Embodying Digital Presence * Always keep the camera on during virtual meetings to convey body language and build a higher level of trust. * Maintain "eye contact" by looking at the camera rather than secondary screens and speak up during meetings to remain an active participant. * Be prepared to interrupt politely in hybrid meetings where office-based participants may dominate the conversation. * Avoid the "blur" effect on backgrounds in favor of a clean, unblurred workspace or a virtual background that reflects your personality. ## Proactive Relationship Building * Schedule recurring virtual coffee chats with colleagues across the organization to build rapport beyond immediate work tasks. * Participate in non-work-related messaging threads and volunteer for team-building initiatives to become more than just a name on a screen. * When visiting the office—ideally once per quarter—prioritize casual interactions, such as morning coffees and team dinners, over routine administrative tasks. * Clear your schedule of non-critical remote meetings during in-person visits to leave room for spontaneous "hallway track" conversations. ## Balancing Visibility and Communication Fatigue * Establish a consistent communication rhythm that provides meaningful updates without becoming overwhelming or irritating to colleagues. * Tailor your outreach methods by consulting teammates’ "How to work with me" documents to respect their individual communication preferences. * Focus on clarity and brevity in written text, as your writing effectively becomes your "voice" in a remote environment. Succeeding as a remote worker requires a shift from passive participation to active, intentional engagement. By treating digital communication as a primary tool for presence and prioritizing periodic in-person connection, you can ensure your contributions remain visible and your professional relationships remain strong.

figma

Shishir Mehrotra’s 10 rules for leading great team meetings | Figma Blog (opens in new tab)

The post argues that effective teams deliberately design two products: what they deliver to customers and the workplace experience that enables employees to do their best work. Shishir Mehrotra frames this employee experience as a system of named, known, and templated rituals—especially meetings. Great teams use different meeting types intentionally and create durable rhythms that keep ambitious work moving. ## Rituals as the “Employee Product” - Company culture becomes tangible through recurring behaviors and rituals. - Strong rituals share three traits: - They are explicitly named. - Employees learn them early. - They follow a repeatable template. - Teams do not need to invent every practice themselves; they can borrow proven rituals from other organizations. ## Three Types of Team Meetings Mehrotra and meeting expert Elise Keith categorize meetings into three groups: - **Cadence meetings** - Examples include staff meetings, stand-ups, and project syncs. - They recur with the same participants and maintain forward momentum. - Their core question is: **Are we on track toward our goals?** - **Catalyst meetings** - Examples include decision forums, product reviews, and design critiques. - They are intended to change direction or resolve important questions. - Their core question is: **Did we reach an answer?** - Too many catalyst meetings can exhaust teams. - **Context meetings** - Examples include all-hands meetings, off-sites, orientations, and one-on-ones. - They establish shared information, insight, and relationships. - Their core question is: **Are we better enabled to do our jobs?** ## Sustaining Long-Term Goals - Mehrotra uses John F. Kennedy’s moonshot as an example of the power of cadence. - Kennedy reinforced the decade-long objective with a weekly meeting involving NASA’s leadership. - Regular meetings can maintain progress on ambitious goals, but they often feel repetitive or obligatory. - Teams should therefore design engaging rituals that make recurring meetings feel purposeful rather than like a chore. - The article points readers to meeting templates and a ritual toolkit for practical examples. ## Practical Takeaway Treat meetings as designed team products, not unavoidable calendar events. Choose the right meeting type, define its purpose and success question, and establish a clear, repeatable ritual that supports the team’s long-term goals.

figma

The Dropbox guide to building creative culture | Figma Blog (opens in new tab)

Culture shapes team happiness, belonging, productivity, innovation, and business outcomes. The Dropbox design team argues that creative culture should be built intentionally rather than left to develop by accident. Its Team Values Toolkit turns abstract beliefs into shared values, observable behaviors, reinforcing habits, and an iterative process. ## Culture as Intentional Practice - Culture is how teams act on their beliefs. - It exists at company, organizational, team, and working-group levels. - Although culture forms inevitably, intentional design helps creative teams innovate and deliver stronger work. - Dropbox developed Culture Kits to help teams make culture concrete and actionable. ## Defining Beliefs and Shared Values - Team members share stories about meaningful work experiences to uncover their individual values. - Including everyone’s perspective helps prevent culture from reflecting only dominant viewpoints or top-down directives. - The team then identifies recurring themes and combines related ideas into shared values, such as grouping “teamwork,” “partnership,” and “clear goals” under “collaboration.” - Shared values should support the team’s goals and connect with broader company values where appropriate. ## Turning Values into Behaviors - Values become useful when translated into specific actions. - Teams should discuss how their values guide: - Decision-making - Conflict and tension - Collaboration - Feedback - Day-to-day working relationships - These behaviors make cultural principles visible in actual team practices. ## Establishing Reinforcing Habits - Teams should define communication styles, norms, and processes that encourage desired behaviors. - For collaboration, this might include cross-functional practices and regular feedback. - The relationship between values, behaviors, and reinforcement creates a shared social contract. - Consistent habits determine how culture is experienced and understood by the team. ## Evaluating and Iterating - Cultural change takes time, so teams should preserve practices that work and remove those that do not. - Teams should define ways to assess whether their culture supports both people and outcomes. - Regular events, such as quarterly offsites, provide opportunities to revisit and refine the framework. - Like a product, culture should be continuously tested and improved. A healthy creative culture requires more than choosing inspiring values; teams must practice and reinforce them consistently. The Team Values Toolkit offers a structured way to build that culture collaboratively and keep adapting it over time.