I often struggle to explain what it means to be part of a high-functioning software team. Sure, there are mountains of literature, and an entire genre of LinkedIn thought leadership that professes all kinds of guidelines and heuristics about what makes teams work, but in my experience, it’s hard to internalize these ideas and follow someone else’s model if you’ve never seen what good looks like.
Adopt and scale Team Topologies: platform-as-a-product, templates, more. — Team Topologies - Organizing for fast flow of value
Accelerate value with Team Topologies: measure cognitive load, define team boundaries, apply inverse Conway, readiness assessments, and more for fast delivery.
Theory and Memory: Two Forces Shaping Software Team Knowledge
How insights from cognitive science and social psychology explain why software knowledge is so hard to preserve
A Guide to Measuring Engineering Team Performance
“You can’t manage what you can’t measure.” While software development practices constantly change, there will always be a tier of truly top engineering teams who stand above…
What Google Learned From Its Quest to Build the Perfect Team (Published 2016)
New research reveals surprising truths about why some work groups thrive and others falter.
TeamTopologies/Team-Topologies-Community-Materials
A list of materials relating to Team Topologies (articles, tools, canvases, etc.) generated by the community.
The Value of Getting Closer to the Work
Scaling The core problem of scaling a team is that not everyone can know everything. Scaling is the work of systematizing that – so that things are understandable, knowable. It’s turnin…
Case Studies — Team Topologies - Organizing for fast flow of value
Examples of Team Topologies used in industry
Kanjun 🐙 on Twitter / X
I've always felt it weird to treat agents as team members. To me, computing is a creative medium where each step expands what I imagine to be possible. Something about the "team member" frame feels creativity-dampening. Not sure why, can't put my finger on it 🤔 https://t.co/CWT3QFVh3x— Kanjun 🐙 (@kanjun) October 1, 2026
How to build internal culture on a T&S team
T&S Insider’s practical, step-by-step guide to building a T&S team that takes accountability, surfaces problems early and doesn't shy away from asking leadership hard questions.
How finishing what you start makes teams more productive and predictable
Hot takes and cold truths on software, startups, and the lies we tell ourselves.
The Economics of Software Teams: Why Most Engineering Organizations Are Flying Blind
A breakdown of what software development teams actually cost, what they need to generate to be financially viable, and why most organizations have no visibility into either number.
Peopleware: productive projects and teams
Demarco and Lister demonstrate that the major issues of…
How teams build – Linear
AI usage patterns in software teams: who is adopting AI, how it reshapes where teams spend their time, and how much more they ship.
Home - Inside Atlassian
Research, expert perspectives, and product announcements from Atlassian on how teams can work smarter with AI. Subscribe for monthly insights on the future of teamwork.
Home - Inside Atlassian
Research, expert perspectives, and product announcements from Atlassian on how teams can work smarter with AI. Subscribe for monthly insights on the future of teamwork.
10 More (Leadership!) Lessons from 10 Years Working in a Fully-Distributed and Remote Company
To make a distributed team work in the long-term it takes deliberate planning and thoughtfulness about your culture, leadership, strategic planning, and team-building.
