Proof of Concept - Small teams
My childhood was filled with playing Sega Genesis games in the living room with my brother. A standout game was General Chaos, a satirical action-strategy game. It offered a simplified take on real-time strategy, set in the classic Red vs. Blue era. Players chose squads of five soldiers, each with unique roles: Gunner, Launcher, Chucker, Scorcher, and Blaster. There was also a fifth option, the Commando squad, which had only two soldiers but combined various skills. As a kid, I couldn’t fathom why anyone would choose two soldiers over five. Then, one day, I accidentally picked the Commandos team while playing solo—and was amazed by the results. I performed far better with the two-man team. With fewer soldiers to manage, I could switch seamlessly between them, outmaneuvering the larger squad with ease. This lesson in General Chaos carried through in my craft as a designer; taking pride in the ability to do more with less. Though the word “small” might be relative to where you work, let’s discuss why having smaller teams is often more effective. Requirements for small teamsYou can’t simply shrink a team and expect the same outcomes as before. Smaller teams aren’t defined by having less work or diminished impact; in reality, they often shoulder more responsibility and operate in higher-stakes environments. Their success hinges on different dynamics, emphasizing talent, trust, adaptability, and experience in ways that large teams cannot replicate. High talent density However, high talent density doesn’t just mean hiring the most senior or experienced professionals—it’s about identifying individuals who excel in their craft and can operate autonomously while collaborating effectively. For example, companies like Replit have shown that even their interns can outperform senior designers at other organizations, showcasing how talent is not strictly tied to tenure. Smaller teams prioritize excellence at all levels, ensuring that each person adds unique value, whether they’re a generalist or specialist. Depth and range in skills For instance, a designer on a small team might also contribute to product strategy or marketing efforts, while a developer might dabble in customer support or user research. This blending of roles isn’t just a necessity—it becomes a strength. By having a range of skills within a team, smaller groups can respond more dynamically to changing priorities, ensuring that no task gets siloed or overlooked. In contrast, larger teams often suffer from fragmentation, where work is compartmentalized, and collaboration can become clunky or slow. Craft experience Similarly, in a professional setting, individuals with deep experience in their craft bring invaluable judgment to a small team. They can anticipate challenges, draw from past lessons, and make quick decisions that steer the team in the right direction. While age doesn’t necessarily equate to expertise, it’s the depth and breadth of experience that matters. This type of insight allows smaller teams to be agile and resilient, even when operating under tight constraints or with limited resources. High trust High trust allows smaller teams to move faster and make decisions with confidence. Instead of second-guessing each other or engaging in bureaucratic processes, they rely on open communication and shared goals. This contrasts with larger teams, where misalignment, unclear expectations, or lack of accountability can lead to inefficiencies and conflict. In smaller teams, trust fosters collaboration, streamlines workflows, and ensures that everyone feels empowered to take ownership of their work. CapabilitiesIf you have the requirements for successful small teams, it unlocks a lot of impactful work. Whether you’re leading one or part of a small team, there is much to be gained from the capabilities they bring. Reduced dependencies Increased quality and velocity Increased ownership and accountability Leveraging small teamsDepending on the company, the concept of small teams might take different forms. For example, an early-stage startup is (hopefully) a small team by default. However, larger companies also deploy smaller teams. There are a few use cases where small teams excel:
From blitzscaling to fitscalingBlitzscaling was a business strategy coined by Reid Hoffman, co-founder of LinkedIn and partner at Greylock. The 2010s were about growth at all costs while raising heavy capital to do so. This era ended in 2021-2022 with the mass layoffs in the industry and rise of AI. The blitzscale era messed up a lot of things, but now that tech has hit the factory reset button, we can take a fresh lens. It might been what was needed at the time, but not anymore. I believe the rest of the 2020s will be focused on Fitscaling. Now more than ever, we're able to do more with less. At Replit, we'd describe our customers as the Fortune 5,000,000 over the traditional 500. This doesn't mean larger teams will go away. Claire Vo, CPO at Launch Darkly, talks about how her role is to help larger companies work more like a startup. This is the philosophy I've taken to the AI Design team at my new company. Instead of the reaction of, "We need more resources and people," we ask, "Are there any missing capabilities on our team? If so, how can we invest in our own team before adding additional overhead?" The allure is not longer, “look how large my team is,” it is, “look how effective this team is.” Hyperlinks + notes
You're currently a free subscriber to Proof of Concept. For the full experience, upgrade your subscription. |
Older messages
Agile is not the enemy
Tuesday, December 10, 2024
Issue 223: Misconceptions designers have about the methodology ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
DH's gifts for thought 2024
Sunday, December 1, 2024
Issue 222: Holiday gift ideas for your loved ones (or yourself) ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Enrique Allen
Sunday, November 24, 2024
In memory of our friend in the design community ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Into the Fediverse
Sunday, November 17, 2024
Issue 221: We need decentralized social networks ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Slow Productivity
Sunday, November 10, 2024
Issue 220: Reflections on the new Cal Newport book ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
You Might Also Like
180 / Make your everyday browsing ridiculously beautiful
Monday, March 3, 2025
Product Disrupt Logo Product Disrupt Half-Monthly Feb 2025 • Part 2 View in browser Welcome to Issue 180 Last year I teamed up with two of my close friends on a side project we're all obsessed with
Accessibility Weekly #438: When to Use Lists
Monday, March 3, 2025
March 3, 2025 • Issue #438 View this issue online or browse the full issue archive. Featured: When to use lists for better accessibility "When creating HTML content, using lists appropriately is
High touch recruiting
Sunday, March 2, 2025
Issue 235: Long-lasting candidate experiences ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
All Compute Must Flow
Sunday, March 2, 2025
“If I don't have that kind of compute on Day 1, I can't breathe." ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
🐺 Is a trade show is your right next step?
Friday, February 28, 2025
Q&A with Shoppe Objects' founders ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
AD100 Designers on Battling Burnout
Thursday, February 27, 2025
View in your browser | Update your preferences ADPro Get Your Groove Back Most days, working in the design field is creatively fulfilling. But occasionally, in the throes of tight project timelines,
Accessibility Weekly #436: Evaluating Overlay-adjacent Accessibility Products
Thursday, February 27, 2025
February 17, 2025 • Issue #436 View this issue online or browse the full issue archive. Featured: Evaluating overlay-adjacent accessibility products "There's a category of third party products
#495: Accessibility and Inclusive UX
Thursday, February 27, 2025
Accessible fonts, inclusive design patterns, accessibility annotations and how to design for people with ADHD. Issue #495 • Feb 18, 2025 • View in the browser 💨 Smashing Newsletter Bok Smashing Friends
AD Editors Share Their Favorite March Issue Moments
Thursday, February 27, 2025
View in your browser | Update your preferences ADPro Behind the Scenes of Creatives at Home The March issue of AD, dedicated to creatives at home, is here. In her editor's letter, global editorial
🐺 Did you know about this?
Thursday, February 27, 2025
͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏