How to 10x your SaaS product team with an internal community with Arne Kittler @Product at Heart

saas.unbound is a podcast for and about founders who are working on scaling inspiring products that people love, brought to you by https://saas.group/, a serial acquirer of B2B SaaS companies.

In episode #3 of season 6, Daniel Thulfaut, the Head of Product at saas.group talks with Arne Kittler, co-founder of Product at Heart, a conference for curious product people, and an experienced product management leader, building digital products & services for 25 years.

Product organizations that grow from one team into many quickly hit the same bottleneck: knowledge and best practices stop flowing. Public groups and conferences help with inspiration, but they rarely solve day-to-day problems in a way that teams can immediately apply. An internal product community—built as a community of practice—changes that dynamic. It creates shared context, speeds up learning, and becomes a multiplier for product work across a portfolio.

Why an internal product community matters more than you think

External communities are great for breadth: new ideas, weak ties, serendipity. Internal communities are different. They are:

• Context-rich — members use the same tools, see the same metrics, and can share real numbers without privacy concerns.
• Stable and results-oriented — they can focus on shared challenges and produce usable artifacts, not just inspiration.
• Aligned around company goals — internal groups can define standards, drive culture, and feed learnings into processes.
• Built for practical reuse — what’s developed internally can be applied across teams and brands without the translation overhead.

Core rituals that make a community of practice work

The most successful internal communities are simple but disciplined. Common patterns that work:

• Start small. A committed core of hosts and early participants gets momentum going.
• Regular cadence. Monthly meetings keep the habit alive; dedicated community days (for example, four times a year) deepen relationships and focus on bigger topics.
• Subgroups for focus. Tackle specific problems in smaller groups when topics are too diverse for everyone.
• Deliver artifacts. Turn learnings into frameworks, templates, or processes that can be reused (alignment frameworks, playbooks).
• Make values visible through actions. Recognize people who embody the community’s values with public kudos rather than posters on a wall.
• Leadership backing. Invite executives to participate—board-level visibility makes it acceptable for people to take time out of busy days.

Formats that actually move the needle

Different formats deliver different kinds of value. Rotate formats to keep engagement high:

• Show-and-tell: share learnings and postmortems from recent experiments.
• Problem clinics: bring a real challenge and get live feedback from peers.
• Work-in-progress reviews: early feedback on designs or roadmaps prevents costly rework.
• Co-creation / hackathons: build prototypes or process pilots together; these often yield the highest immediate ROI because outcomes are tangible and transferable.

A well-run co-creation session can produce working prototypes or process templates that scale across dozens of teams—far beyond what a single central team could deliver alone.

How to scale the community without losing relevance

Growth introduces two common risks: lost context and diluted relevance. Avoid them by:

• Keeping themes tight. If discussions drift into unrelated business models or tooling, split the group into focused cohorts.
• Prioritizing continuity. Regular attendees build trust and accelerate collaboration; avoid relying on one-off participation patterns.
• Creating sub-communities. Organize by topic, domain, or product type when necessary so conversations stay applicable.

The unpaid work that makes communities feel alive

Community hosts do more than choose topics. They create the experience. Tasks that matter but are easy to underestimate:

• Logistics: rooms, refreshments, travel coordination.
• Curation: selecting topics, speakers, and formats that matter to the group.
• Welcoming and onboarding new members so they feel safe to contribute.
• Blending internal expertise with occasional external voices to spark new perspectives.

Hosts set the tone. Treat the host role as part operational manager, part cultural ambassador.

Embedding central teams and fractional resources as multipliers

A central team can act as an in-house consultancy: embed designers, growth people, or product ops into several teams, help them succeed quickly, then capture what worked and scale it out. This creates an “extended workbench” that multiplies the central team’s impact.

Embedding part-time experts is especially useful for smaller companies that cannot afford full-time hires. A 25–50 percent designer or product operator can be transformational compared to having no specialist at all.

Fractional leadership: when it helps and when it doesn’t

The term “fractional” focuses on time slices. Reality matters more: when a senior product leader joins part-time, success depends on the organization’s maturity and the role’s scope.

Part-time leadership works best when:

• There are experienced product people in the organisation who can execute and own details.
• The part-time leader can focus on strategy, ways of working, and high-impact alignment rather than day-to-day delivery.
• The engagement is timeboxed and treated as a transition or interim arrangement—often most effective for up to a year.

Part-time leadership is not a good fit for founder handovers. That transition asks for deep trust, full attention, and heavy involvement that a fractional leader cannot reliably deliver.

“Us getting fired is the best way possible that we can do.”

That blunt line highlights an important truth: fractional or embedded resources should increase internal capability to the point where teams no longer need them.

Checklist: Is your company ready for a part-time product leader?

• Strong mid-level product or design leads who can own execution.
• Clear expectations for what the part-time leader should deliver within a fixed timeframe.
• Board or executive support to signal the initiative’s importance.
• Shared tooling and metrics so the leader’s time is used efficiently.
• A plan for knowledge capture and handover so improvements persist after the engagement ends.

How part-time leaders manage time—and what gets deprioritized

Part-time leaders cannot be everywhere. That forces healthy prioritization:

• They prioritize strategic alignment, cross-functional decision-making, and key rituals.
• They delegate detail work—deep dives, every sales sync, and granular QA— to trusted team leads.
• Casual, ad-hoc social gatherings or low-impact meetings are often deprioritized.

Being explicit about what will not be covered is as important as defining what will be covered. It reduces expectation gaps and protects the leader’s impact focus.