GraphQL is rapidly becoming a core technology for modern APIs, yet managing its adoption and evolution within complex organizations remains a significant challenge. In this article, I will share my experience and lessons learned from leading a GraphQL stewardship group at AlphaSense, distilled from my presentation at apidays Helsinki & North 2025. I aim to provide practical guidance on how to effectively organize and run stewardship groups that empower teams, foster collaboration, and maintain the integrity of your GraphQL graph — and equally important, what pitfalls to avoid.
Whether you are just starting to explore GraphQL stewardship or are looking to optimize an existing group, this deep dive will help you understand why stewardship matters, how to get started, and how to keep your stewardship group relevant and impactful over time.
Understanding GraphQL Stewardship: What and Why?
Stewardship groups in the GraphQL ecosystem are often described by leading vendors and community resources as cross-functional collectives of key stakeholders. Their mission is to empower teams to be “good citizens” of the graph by setting standards, facilitating evolution, supporting operations, and enforcing best practices for client usage.
Many organizations confuse stewardship groups with guilds or informal workgroups. While guilds can be excellent for knowledge sharing and learning, they often struggle to sustain meaningful impact unless there’s dedicated focus and alignment on key priorities. In contrast, stewardship groups should operate as centers of excellence — intentional, collaborative bodies that actively own and guide the growth of the GraphQL graph, ensuring its integrity rather than merely governing it.
“The stewardship group is more than just a forum. It is about active ownership and collective improvement.“
But why invest time and effort in establishing a stewardship group? After all, it requires focus, energy, and coordination from busy teams. The answer depends largely on your organizational context and technological complexity. GraphQL, while powerful, is “savage” — it’s easy to get wrong and challenging to onboard new teams effectively.
Stewardship shines when you have:
- Complexity in your tech stack that demands coordinated management.
- Multiple teams adopting GraphQL, either voluntarily or through organizational mandate.
- A large number of teams interacting with the GraphQL API, leading to potential inconsistencies and technical debt.
In organizations where the GraphQL landscape is akin to the “Wild West,” stewardship groups become critical to tame chaos and drive alignment.
When to Know if You Need a Stewardship Group
Determining whether you need a stewardship group is not always straightforward. My recommendation is to pilot the idea for a few sessions — for example, over a quarter or six months — and then pause to evaluate its impact. During this trial period, observe whether the group is missed when paused or if it simply adds noise without value.
Many believe you can predict the need for stewardship upfront, but in reality, it’s often through experimentation and iteration that the true value becomes clear.
Real-World Context: The AlphaSense Experience
When I joined AlphaSense, the need for stewardship was already evident. The organization was growing rapidly, with many teams adopting GraphQL either because it benefited their workflows or because it was mandated to unify the platform. This growth led to:
- Significant technical debt from uneven adoption and knowledge.
- An increasing number of operational incidents and issues.
- Fragmented communication, often limited to Slack channels.
In such an environment, stewardship was not a luxury but a necessity to maintain order and drive sustainable progress.
Getting Started: Building Your Stewardship Group
Assuming you’ve decided to move forward with stewardship, the first step is to lay a solid foundation. Here are two critical components to focus on:
- Identify the right people to invite.
- Select the initial topics to address.
These two lists are deeply intertwined — the people you invite should be appropriate for the topics you want to tackle, and vice versa.
Who to Include?
Stewardship groups benefit from a diversity of voices. Consider including:
- Individual contributors who have hands-on experience with GraphQL.
- Tech leads and engineering managers who can influence team practices.
- Staff or senior engineers with deep expertise.
- Product managers who understand user needs and priorities.
The key is to assess potential members based on the impact they can have on cross-team alignment and the evolution of the GraphQL schema. Not everyone needs to be involved, but those who are should bring meaningful insight and influence.
What Topics Should You Start With?
Start small and focused. Pick topics that require alignment across teams and that address pressing challenges or opportunities. Avoid low-level issues that are specific to a single team or individual contributor — those are better handled locally.
Remember, stewardship groups are most valuable when they focus on areas where collective agreement and coordination are critical.
The Role of Stewards and Organizational Structure
At AlphaSense, one factor that strongly supported stewardship success was our organizational structure. We classify engineering teams into three types:
- Feature teams: Focused on delivering product features.
- Platform teams: Provide foundational technology and infrastructure supporting feature teams.
- Enabling teams: Less common but vital, these teams support cross-organizational initiatives aimed at improving developer experience and easing the work of feature teams.
The stewardship core team aligns with one of these enabling teams, which brings three key advantages:
- Freedom to innovate: The team can explore new approaches without being overly constrained.
- Awareness: They maintain visibility into what is happening across the company.
- Power to influence: They have the mandate to shape ways of working across teams.
This alignment creates a powerful recipe for stewardship success. If your organization lacks formal enabling teams, seek individuals who can embody these three qualities to form your core stewardship team.
Setting Goals and Making Progress
One of the toughest challenges in running a stewardship group is defining clear goals and demonstrating progress. Stewardship involves taking on long-term risks with the hope of delivering good value, which requires time to digest insights and share them widely.
At the same time, organizations expect urgency and tangible results, creating a tension between thoughtful stewardship and rapid delivery.
How to Set the Right Goals?
Unfortunately, there is no one-size-fits-all answer. However, some guiding principles can help:
- Be acutely aware of the real needs across teams and the organization.
- Track what is achieved versus what is expected to inform future priorities.
- Adjust goals regularly based on feedback and measurable outcomes.
Equally important is having a compelling reason to engage the organization and the core team. Without a clear purpose, even the best processes and tracking mechanisms will fall flat.
Focus your stewardship efforts on areas where alignment is critical and avoid low-level internal issues that don’t require cross-team coordination.
The Art of Moderation: Creating a Safe and Productive Space
Trust is the foundation when asking for change, and moderation plays a pivotal role in building that trust within stewardship groups.
Effective moderation ensures that everyone has room to share their challenges and successes, no matter their seniority level. Without it, louder voices may dominate, while less experienced members feel lost, halting progress.
To moderate well, consider these techniques:
- Provide ample context and keep discussions simple and jargon-free.
- Encourage participation from all members, creating a safe space for open dialogue.
- Remember that if a complex topic cannot be explained simply, it likely needs further understanding.
Sharing achievements rather than pushing aggressively for results fosters a positive atmosphere. This approach motivates participants to do their best without feeling micromanaged.
Maintaining Relevance and Engagement Over Time
Keeping stewardship groups relevant and engaging is an ongoing challenge. Contributions—both in quantity and quality—are the lifeblood of any successful stewardship effort.
While it sounds straightforward to “just bring important stuff,” sustaining momentum requires continuous effort, especially when progress is slow or intangible.
The Secret Weapon: Core Contributors
At AlphaSense, a core team of contributors who focus on cross-functional initiatives has been invaluable. These individuals:
- Act as frontliners by mandate, knowing what is critical for the organization.
- Understand the day-to-day struggles of teams actively using GraphQL.
- Align their work with organizational necessities, consistently delivering relevant outcomes.
This core team ensures a baseline level of engagement and relevance. Additionally, teams across the organization often develop solutions for their own needs that later benefit the wider company when shared through stewardship channels.
Elevating Your Stewardship Group’s Impact
To make a substantial impact, securing leadership buy-in is paramount. Without it, stewardship efforts risk being sidelined or under-resourced.
Leadership support provides:
- Confidence in the stewardship model.
- Resources and authority to drive broader initiatives.
- Visibility and legitimacy to the stewardship group’s work.
Clear and transparent communication about stewardship activities is also crucial. Making progress, challenges, and decisions visible to the entire organization fosters trust and encourages wider participation.
Involving the Right Stakeholders: The Voice of the Consumer
GraphQL APIs, like any product, have diverse stakeholders beyond engineers, including UX/UI designers, product owners, and client developers. Their involvement helps ensure that the schema truly serves user needs.
While these stakeholders may not engage deeply in the technical discussions, they provide invaluable feedback when topics and meeting goals are appropriately curated.
Bringing the voice of the consumer into stewardship discussions elevates the value and usability of your GraphQL API.
Conclusion: Stewardship as a Journey, Not a Destination
Running a GraphQL stewardship group is a complex but rewarding endeavor. It requires intentional organization, the right people, clear goals, effective moderation, and continuous iteration. Above all, it demands a mindset of active ownership and collective improvement rather than mere governance.
By focusing on critical alignment areas, fostering trust, sharing achievements, and securing leadership support, stewardship groups can transform the chaotic landscape of GraphQL adoption into a well-tended, evolving graph that empowers teams and drives business value.
At AlphaSense, our stewardship journey continues to evolve, guided by these principles and the dedicated core team that champions cross-functional collaboration every day.
For organizations grappling with GraphQL complexity and fragmented adoption, stewardship groups offer a path to clarity, consistency, and sustainable growth.
Thank you for exploring these insights with me.
