# Teamwork Published articles for Teamwork. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Podcast: Signals and Levers: Building Thriving Engineering Organizations DevFeed: [Podcast: Signals and Levers: Building Thriving Engineering Organizations]() Original publisher: [Read original article]() Author: Elisabeth Hendrickson, Joel Tosi Published: 2026-09-18T09:05:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [systems](), [Culture & Methods](), [engineering-leadership](), [engineering-culture](), [Software](), [Artificial Intelligence]() Tags: [agile](), [building-thriving-engineering-organizations](), [collaboration](), [culture](), [culture-methods](), [distributed-team](), [engineering](), [engineering-culture](), [engineering-culture-podcast](), [engineering-leadership](), [infoq](), [leadership](), [podcast](), [psychological-safety](), [software-craftsmanship](), [software-delivery](), [systems](), [team-collaboration](), [teams](), [teamwork](), [technical-debt]() ### AI overview This podcast discusses systems thinking as a way to understand software delivery and engineering organizations. Elisabeth Hendrickson and Joel Tosi explain how leadership policies, everyday cultural behavior, context, and continuous course-correction shape sustainable engineering teams, including amid AI-driven change. ### Source excerpt In this podcast Shane Hastie, Lead Editor for Culture & Methods spoke to Elisabeth Hendrickson and Joel Tosi about systems thinking as a lens for software delivery, the cultural "levers" leaders and teams can pull to shape organizations, and building thriving, sustainable teams amid AI-driven change. By Elisabeth Hendrickson, Joel Tosi ## Sol Protocol Early Access Impressions: A Co-op Action Roguelike with a Promising Foundation DevFeed: [Sol Protocol Early Access Impressions: A Co-op Action Roguelike with a Promising Foundation]() Original publisher: [Read original article]() Author: James Galizio Published: 2026-09-17T20:28:19Z Content type: article Language: en Sources: [UploadVR]() Topics: [multiplayer]() Tags: [map](), [multiplayer](), [space](), [teamwork](), [vr-gaming](), [warp]() ### AI overview Sol Protocol is a co-op action roguelike set in space. Players work together aboard a ship and during zero-gravity exploration to gather resources, upgrade systems, and fight enemies. The game has a promising co-op foundation, though its current gameplay loop is simple and limited in scope. ### Source excerpt Sol Protocol in Early Access on Quest has a good foundation of co-op teamwork and exploration, but the limited scope has a lot of room for growth. ## Beyond Autonomous Teams in Software Product Development DevFeed: [Beyond Autonomous Teams in Software Product Development]() Original publisher: [Read original article]() Author: Ben Linders Published: 2026-09-10T10:29:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Self-organizing Team](), [Software Engineering]() Tags: [agile-conferences](), [autonomous](), [autonomous-software-teams](), [business-value](), [complex-systems](), [complexity](), [conference](), [culture-methods](), [delivering-value](), [management](), [networking](), [news](), [product-development](), [scrum](), [self-organizing-team](), [teamwork]() ### AI overview A conference talk argues for moving from product-focused autonomous teams to value centers, with organizational design shaped by value and its dependencies. It frames agency and coherence as a trade-off and uses the Viable Systems Model to suggest five questions for teams. ### Source excerpt Autonomous teams are an article of faith in modern software development. The shape of our value determines what we can do; it determines our trade-offs between agency and coherence. We all have a purpose, and we all have agency to do something, hence the suggestion is moving from product focus to value center thinking. By Ben Linders ## How agentic development affects team collaboration DevFeed: [How agentic development affects team collaboration]() Original publisher: [Read original article]() Author: Irina Nazarova (inazarova@evilmartians.com) Published: 2026-09-09T00:00:00Z Content type: opinion Language: en Sources: [Evil Martians]() Topics: [Development](), [Artificial Intelligence](), [Code](), [pull-requests]() Tags: [agentic-development](), [ai](), [code](), [collaboration](), [developer-community](), [development](), [dx](), [teamwork]() ### AI overview This opinion article examines how agentic development can increase individual speed while making collaboration harder. It distinguishes learning work, such as testing hypotheses and building experiments, from other engineering work even when both produce code, and presents practical ideas for working together again. ### Source excerpt Agentic speed turned all of us into super-ICs and broke our ability to collaborate. Two types of work that both produce code, and three recipes for working together again: a safe perimeter for experiments, shared rules everybody pays for, and an intent log your agents write themselves. ## The Context Tax of Agentic Development DevFeed: [The Context Tax of Agentic Development]() Original publisher: [Read original article]() Author: A Talhan Published: 2026-08-25T11:01:02Z Content type: opinion Language: en Sources: [Expedia]() Topics: [Agentic development](), [Development](), [networking](), [data]() Tags: [agentic](), [agentic-ai](), [agentic-development](), [agents](), [context](), [context-engineering](), [development](), [engineering-management](), [networking](), [software-engineering](), [teamwork]() ### AI overview An Expedia Group engineering team describes how hidden context can cause agentic development to accelerate technically plausible work aimed at the wrong system. Using AI Workbench's multi-environment model handling as an example, the article argues that context must be explicit and structured so humans and agents share the same understanding. ### Source excerpt Expedia Group Technology -- EngineeringMissing context used to slow a team down, with agents in the loop it speeds up the wrong work insteadPhoto by Harley-Davidson on Unsplash When we started using agents more seriously inside the team, the first bottleneck was not code generation -- It was context coordination. That sounds like a documentation problem, but it did not feel like one. It felt like a delivery problem. A human engineer who is missing context usually slows down. They ask someone, search through old notes, or wait for the next sync. An agent does not always slow down. It can keep moving and produce work that is technically plausible, well formatted, and aimed at the wrong reality. That is the agentic velocity trap: unclear context does not just delay work; it can accelerate the wrong work. Rick Fast recently wrote about the broader Expedia Group™ platform shift toward agent-friendly interfaces and operating surfaces. This is the ground-level version from one team: what did we have to change in our own planning loop so humans and agents could work from the same understanding? The problem was hidden context One of the clearest examples came from multi-environment handling in AI Workbench (our web console for machine learning (ML) artifacts and workload management). From the outside, an AI Workbench URL appeared to represent one backend environment. Under the hood, it was backed by another. A team saw their model in the UI, reasonably assumed it existed in the environment implied by the URL, and then hit "model not found" when downstream jobs queried that expected backend. Internally, the concrete case was a machine learning scientist team onboarding a model. It appeared in the .prodA AI Workbench URL, but that deployment was serving model registry prodB data rather than model registry prodA data. The platform services were not simply broken. The hidden semantic mapping was because of networking and access nuances. That distinction matters. A human team lost ## AI-Generated Images Can Perform as Well as Stock Photography DevFeed: [AI-Generated Images Can Perform as Well as Stock Photography]() Original publisher: [Read original article]() Author: Rachel Banawa Published: 2026-08-21T17:00:00Z Content type: article Language: en Sources: [NN/g latest articles and announcements]() Topics: [Artificial Intelligence](), [.NET MAUI]() Tags: [ai](), [analysis](), [article](), [collaboration](), [images](), [photography](), [statistical-significance](), [teamwork]() ### AI overview AI-generated hero images did not produce a meaningful perception penalty compared with real stock photography in a study of 77 participants evaluating fictional consulting-firm webpages. Ratings were slightly higher for AI imagery, but only the small authenticity difference reached statistical significance. ### Source excerpt When users didn't know whether an image was AI-generated, the images we tested did not create any perception penalty compared to stock photos. ## Gemini Robotics 2 brings whole body intelligence to robots DevFeed: [Gemini Robotics 2 brings whole body intelligence to robots]() Original publisher: [Read original article]() Author: Carolina Parada Published: 2026-07-28T13:21:37Z Content type: article Language: en Sources: [Google DeepMind News]() Topics: [Robotics](), [AI Models](), [Artificial Intelligence](), [vlm](), [multimodal]() Tags: [agent](), [ai](), [ai-models](), [collaboration](), [gemini](), [models](), [multimodal](), [on-device](), [robotics](), [robots](), [teamwork](), [vision]() ### AI overview Gemini Robotics 2 is presented as an intelligence layer for adaptable robots, enabling whole-body control, dexterous manipulation, multi-robot teamwork, and adaptation to new robotic bodies. The article describes three models: a vision-language-action model for motor control, an embodied reasoning vision-language model for communication and multi-step planning, and an on-device model optimized for local operation. ### Source excerpt From feet to fingertips -- we are teaching robots intelligent whole-body control, fine dexterity, and teamwork to complete a broad range of complex tasks. ## MIT in the media: Innovating and educating for the next 250 years of America DevFeed: [MIT in the media: Innovating and educating for the next 250 years of America]() Original publisher: [Read original article]() Published: 2026-07-01T20:30:00Z Content type: news Language: en Sources: [MIT AI News]() Topics: [Artificial Intelligence](), [Physical AI](), [Learning](), [Machine learning]() Tags: [ai](), [artificial-intelligence](), [curiosity](), [education-teaching-academics](), [funding](), [health](), [learning](), [physical-ai](), [president-sally-kornbluth](), [research](), [students](), [teaching](), [teamwork](), [university]() ### AI overview At a Washington Post Live panel, MIT President Sally Kornbluth discussed curiosity-driven research, university preparation for an AI-enabled future, and a human-centric approach to AI education. She emphasized foundational STEM knowledge, ethical and civic education, physical AI, collaboration, and AI as an augmentation tool. ### Source excerpt During a "Washington Post Live" panel discussion with ASU President Michael Crow, President Sally Kornbluth explored how universities are preparing the next generation of scientists to lead in America's rapidly changing technological landscape. ## Why We Designed Our Engineering Hiring Process The Way We Did DevFeed: [Why We Designed Our Engineering Hiring Process The Way We Did]() Original publisher: [Read original article]() Author: info@goteleport.com (Larry Warren) Published: 2025-08-25T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [Job](), [GitHub](), [zoom]() Tags: [alignment](), [engineering](), [github](), [hiring](), [interview](), [process](), [teamwork](), [zoom]() ### AI overview Teleport explains its transparent, challenge-based engineering hiring process, including recruiter and hiring-manager calls, a technical challenge, and opportunities for candidates to assess long-term cultural and role alignment. ### Source excerpt Discover why Teleport designed a transparent, challenge-based engineering hiring process that reflects our culture, values, and real-world teamwork. ## Test-driven Development, Clean Code, Teamwork DevFeed: [Test-driven Development, Clean Code, Teamwork]() Original publisher: [Read original article]() Author: Denis Čahuk Published: 2025-02-12T10:42:59Z Content type: opinion Language: en Sources: [Crafting Tech Teams]() Topics: [Test-driven development](), [clean-code](), [Development]() Tags: [clean-code](), [development](), [tdd](), [teamwork]() ### AI overview A recorded live video discusses test-driven development, clean code, and teamwork conflicts, including practical TDD adoption, cultural shifts, incremental quality improvements, prioritization, resistance, and sustainable change. ### Source excerpt A recording from Denis Čahuk's live video ## 8 ways to craft an unforgettable Config talk DevFeed: [8 ways to craft an unforgettable Config talk]() Original publisher: [Read original article]() Author: Carly Ayres Published: 2024-11-14T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Canvas]() Tags: [2025](), [best-practices](), [design](), [figma](), [games](), [inspiration](), [product](), [software-engineer](), [speakers](), [teamwork](), [vision]() ### AI overview Figma Config speakers recommend memorable talks from 2024 as inspiration for future Config presenters. The article highlights unconventional product development, creative simplicity, spatial computing design, the Ai Pin, product taste, and teamwork across roles. ### Source excerpt Where do inspirational people find inspiration? Our Config speakers share their favorite talks from 2024, offering up a blueprint for crafting sessions that truly stand out. ## Snyk Week of Impact 2023: A week of meaningful contributions and community engagement DevFeed: [Snyk Week of Impact 2023: A week of meaningful contributions and community engagement]() Original publisher: [Read original article]() Author: Bianca Matei Published: 2023-11-08T06:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [snyk]() Tags: [awareness](), [blog](), [collaboration](), [community](), [contributions](), [executive](), [global](), [inclusive](), [recruiting](), [snyk](), [snyk-team](), [teamwork]() ### AI overview Snyk's Week of Impact, held from October 22-27, 2023, brought together employees globally for community-focused volunteer activities. More than 20% of Snykers participated, contributing through STEM kit assembly, food support, school renovation, and diaper-kit distribution. ### Source excerpt The Snyk Week of Impact, from October 22-27, was not just another event. It was a manifestation of our core belief in giving back. In a concerted effort that saw over 20% of Snykers participating globally, we aimed to create a ripple effect of meaningful connection and community engagement. ## Benefits of Collaboration DevFeed: [Benefits of Collaboration]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-11-04T04:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Software Engineering](), [meetings]() Tags: [asynchronous](), [code-reviews](), [collaboration](), [collaboration-developer-experience-developer-productivity-team-programming-engineering-excellenc](), [communication](), [meetings](), [software-design](), [teamwork]() ### AI overview The article argues that collaboration should be the standard way of working for software teams. It describes benefits including on-the-job team building, better decisions, knowledge sharing, improved communication, and more effective problem-solving. It also argues that synchronous collaboration can improve later asynchronous communication. ### Source excerpt Benefits of Collaboration In my career, I've seen many "teams" that mainly collaborate only when the work gets tough or if someone has been stuck for days. In these cases, teamwork is more of an exception than a regular practice. This approach is backward. Collaboration should be the standard way of working, and we should only choose to work independently for good reasons. ## 4 roles to have on your incident response team for efficiency and the fastest resolution times DevFeed: [4 roles to have on your incident response team for efficiency and the fastest resolution times]() Original publisher: [Read original article]() Author: incident.io Published: 2023-04-10T00:00:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident](), [Incident response]() Tags: [best-practices](), [efficiency](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [operational](), [outage](), [post-mortem](), [slack-incident](), [teamwork](), [technical]() ### AI overview This article explains how to structure an incident response team for fast resolution and operational efficiency. It emphasizes dedicated roles, clearly defined responsibilities, and coordinated teamwork for diagnosing, triaging, resolving, and monitoring incidents. ### Source excerpt Incident response teams work best when they're structured appropriately and have dedicated roles. Here are some best practices for doing just that. ## The Benefits of Remote Work for Developer Teams: Increased Productivity and Better Work-Life Balance DevFeed: [The Benefits of Remote Work for Developer Teams: Increased Productivity and Better Work-Life Balance]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-02-18T06:00:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Development](), [pair\_programming](), [Programming]() Tags: [collaboration](), [collaboration-culture-ensemble-programming-practices-remote-work-developer-productivity-organi](), [developers](), [pair-programming](), [productivity](), [remote-work](), [teamwork](), [video-conferencing]() ### AI overview The article describes claimed benefits of remote work for developer teams, including reduced commuting stress, flexible scheduling, fewer office distractions, and improved work-life balance. It also explains how digital collaboration tools can support real-time teamwork and pair programming across locations. ### Source excerpt The Benefits of Remote Work for Developer Teams: Increased Productivity and Better Work-Life Balance In today's fast-paced and constantly changing world, many organisations are rethinking traditional work arrangements and embracing the benefits of remote work. ## My First 30 days as a Product Manager at the BBC DevFeed: [My First 30 days as a Product Manager at the BBC]() Original publisher: [Read original article]() Author: Louise Ankers Published: 2022-02-15T22:31:11Z Content type: opinion Language: en Sources: [BBC]() Topics: [Product Management](), [Agile](), [Self-organizing Team](), [User experience (UX)](), [Testing]() Tags: [agile](), [apps](), [bbc](), [data](), [distributed](), [experimentation](), [exploration](), [management](), [new-starter](), [product](), [product-management](), [software-development](), [teamwork](), [testing](), [ux]() ### AI overview A Senior Product Manager describes her first 30 days at the BBC, including the organization's product-management culture, roadmap practices, agile teamwork, distributed work, and support from specialists in UX, data, experimentation, and testing. ### Source excerpt Much like Sir David Attenborough I was not successful on my first application to the BBC , however I was not dissuaded and applied again! Fortunately, I was successful last year and have joined the BBC as Senior Product Manager -- Children's Apps. CBeebies Playtime Island app icon On my first day all the team were very welcoming and friendly, and have explained (and continue to explain!) every BBC acronym very patiently. As a new Product person, it's often intimidating to join a new organisation, not to mention within a new domain. As I have joined during the COVID-19 Omicron wave, everyone is working from home. I am keen to meet the team in person as much as possible -- though we are quite geographically distributed so we will have to plan quite carefully. Product On an organisational level -- the first thing that was clear to me was that the BBC Product Culture follows the principles and values from good Product Management practice such as that advocated by product experts such as Roman Pilcher or Melissa Perri. Having read many books and blogs over the years about say -- having a roadmap that indicates what you are working on now, next and later to offer transparency to stakeholders rather than a delivery plan -- has always been something I've desired to do, and here it is being used in practice! Agile Values Another thing I noticed was the enthusiasm for teamwork and team values -- as one of the principles of the Agile Manifesto that I am passionate about "The best architectures, requirements, and designs emerge from self-organizing teams" -- again in many organisations this may start as an ambition but be waylaid by older management practices and a blindness to what is a creative process. My own reaction to this approach is that I feel there is the right focus on thinking about why we are building, and even if we should be building -- this makes me feel that people think the same way that I do, and that experimentation and exploration in the problem and discovery space ## Flickr Engineering Team Vision & Guiding Principles DevFeed: [Flickr Engineering Team Vision & Guiding Principles]() Original publisher: [Read original article]() Author: Alex Seville Published: 2021-11-23T00:00:45Z Content type: opinion Language: en Sources: [Flickr]() Topics: [Development](), [Software](), [Code](), [Amazon Web Services](), [data centers](), [Digital Public Good]() Tags: [amazon](), [aws](), [communication](), [data-centers](), [development](), [engineering](), [history](), [innovation](), [nodejs](), [open](), [photography](), [standards](), [team](), [teamwork](), [uncategorized](), [vision]() ### AI overview Flickr presents its engineering team vision and guiding principles, covering psychological safety, inclusive communication, continuous feedback, incremental technology adoption, and reliable software delivery. ### Source excerpt There's a rich history of engineering innovation and excellence at Flickr. The team has been involved in the development of specs and open standards, been an early adopter of technologies like NodeJS, and successfully migrated from Yahoo data centers to ... Continue reading -> ## Running a Hack Day DevFeed: [Running a Hack Day]() Original publisher: [Read original article]() Author: Jossi Wolf Published: 2020-12-01T20:46:31Z Content type: opinion Language: en Sources: [Stories by Jossi Wolf on Medium]() Topics: [Development](), [Learning](), [Compose]() Tags: [android](), [hack-days](), [hackday](), [jetpack-compose](), [learning](), [programming](), [stories](), [team-building](), [teamwork]() ### AI overview The article explains what a hack day is and discusses how it can help developers break from routine work, learn, collaborate across teams, and build connections. It also compares hack days with 20% time and notes that the two approaches can complement each other. ### Source excerpt Recently, some clients asked us about our opinion on a newly released framework. To get a better idea of it, we ran an internal hack day -- here's how! Stay tuned for the second part about our experiences with running Jetpack Compose hack day! What's a Hack Day? Basically, a hack day is a one-day event where you can work on whatever. This is awesome for exploring a new technology or just doing something different once in a while! There are no rules except for that what you're doing should probably be kinda related to your work, but it doesn't have to be! Why you should run a hack day There are lots of reasons to love hack days -- I'll focus on a few. The benefits will always be a different depending on your company, team and the tech you are working with. It helps people break out of day-to-day work life A hack day can enable working with different people and build connections If you do it right, people will be able to relax a bit A fun breakout First off, hack days are a great thing to break out of day-to-day dev life. Project fatigue gets everyone after a while. Maybe the work is not mundane or boring, but working on exactly the same thing every day can get tedious. The longer you work on a project, the harder the challenges become and the longer the cycles of success/no success become. On a hack day, you will be working on something entirely different, without any expectations. This makes it a lot easier to learn, takes some pressure off and can be very satisfying. Teamwork!Teamwork Since a hack day is a defined space and time for folks to work on something, this makes working together a lot easier -- you're there anyway! Working on something alone can be nice, and maybe that's exactly what somebody is looking for. For others, learning together is a lot more fun and more memorable. Interacting with folks from different teams In our case, we had people working together who normally work on different projects. This helps create connections and makes the team grow toge ## Python Hackathon at trivago DevFeed: [Python Hackathon at trivago]() Original publisher: [Read original article]() Author: Matthias Endler Published: 2017-12-20T00:00:00Z Content type: news Language: en Sources: [Trivago]() Topics: [Hackathon](), [Python](), [coding-community](), [Programming](), [Open Source]() Tags: [code](), [collaboration](), [community](), [creativity](), [developer](), [developer-community](), [engineering-culture](), [event](), [hackathon](), [hackathons](), [open-source](), [programming](), [python](), [teamwork]() ### AI overview trivago hosted a Python Hackathon with the Python Usergroup Düsseldorf. Participants worked in teams on projects including embedded tools, graphical user interfaces, games, bots, and machine learning, with several projects releasing code as open source. ### Source excerpt Hackathons! That's where you feel super excited about creating something interesting, or useful, or just entertaining. They are a great way to encourage creativity and teamwork. Recently, trivago hosted a Python Hackathon in collaboration with the Python Usergroup Düsseldorf. The event was a full success! ## Monolith to Microservice: Architecture Behind V2 Webhooks DevFeed: [Monolith to Microservice: Architecture Behind V2 Webhooks]() Original publisher: [Read original article]() Author: Paulius Jakimavičius Published: 2017-09-11T15:09:33Z Content type: article Language: en Sources: [Teamwork]() Topics: [Microservice](), [Architecture & Design](), [Go Language](), [HTTP](), [JSON](), [XML](), [JavaScript](), [callback]() Tags: [api](), [architecture](), [go](), [http](), [javascript](), [json](), [microservice-architecture](), [sha256](), [teamwork](), [teamwork-project](), [webhooks](), [xml]() ### AI overview This article explains the redesign of Teamwork Projects webhooks from a monolithic implementation to a Go microservice. The update supports multiple webhooks per event, sends complete datasets in JSON, XML, or form format, adds SHA-256 checksums, and uses more frequent retry intervals. ### Source excerpt We've recently released an update to the Teamwork Projects webhooks feature and I was asked to do a tech talk on the topic, a recording of which can be found below. This article is a rough summary of the talk with further elaboration of the thought process behind some of our decisions, but in summary: We have a microservice written in Go. We now support multiple webhooks per-event We send full datasets in chosen format (JSON, XML or Form) We offer better security and integrity with sha256 checksums We have more frequent retry intervals. https://medium.com/media/1208334bf98663ab7d55e4d2eaad4c95/hrefWhat are Webhooks? The basic idea of webhooks is simple -- it's a HTTP POST call triggered when some event occurs. You can think of it like a JavaScript callback, except it's a HTTP POST that can be sent anywhere, to anyone -- not limited to a single codebase or domain. In the case of Teamwork Projects, we have a set list of possible events you can subscribe to, denoted in OBJECT.ACTION style, so for example TASK.CREATED or MESSAGE.DELETED. Previous Approach (v1) Our original approach was no more complicated than the concept of webhooks itself -- when any of the supported actions are taken in Projects, a "fireWebhook" function is called, which checks if they're enabled and if there is a webhook set up for that event. If all is good -- we make a cfhttp call to the relevant URL with the item ID, item type and the action taken, all encoded as form data. Now there are a few limitations with this approach which showed up as the number of webhook users increased over time: Only one webhook per event -- although it made sense as a sort of anti-spam measure initially, this resulted in a few inconveniences for our customers. For example, a user sets up a TASK.CREATED webhook that notifies a custom service which adds the task ID to their internal database. This would make it impossible for them to later set up, say a Zapier zap using TASK.CREATED event as it is already "in use". Limited ## Making 20% Time Work DevFeed: [Making 20% Time Work]() Original publisher: [Read original article]() Published: 2016-01-29T00:00:00Z Content type: article Language: en Sources: [Joe Nelson]() Topics: [Open Source](), [Maintainers](), [GitHub](), [Code]() Tags: [apply](), [blog](), [blog-post](), [contribute](), [contribution](), [developers](), [experiments](), [github](), [how-to](), [maintainers](), [open-source](), [project](), [projects](), [teamwork](), [work]() ### AI overview The article explains how companies can structure employee "20% time," a weekly period for self-directed projects, so that it produces useful tools and open-source projects instead of becoming unproductive. It introduces a contribution matrix for coordinating teamwork and begins describing the BASEDEF contribution categories, including blogging about a project and applying it in another project. ### Source excerpt 2016-01-29 Following Google's lead many companies have instituted "20% time" for their employees. This is one day per week in which employees can work on projects of their own choosing. The practice keeps developers motivated and sharp, produces tools to solve company problems, and in the best case creates open source which builds prestige and helps recruitment. But there's one problem with twenty-percent time: it takes discipline to pull it off.