Building in Public: How Superthread Manages Product, Tech, and Growth

The ‘Dogfooding’ Secret: How We Run Superthread Using Superthread

At Superthread, we don’t just build a tool for other teams; we are our own most demanding customer. To maintain our ‘lightning-fast’ reputation, we rely on a specific organizational hierarchy that keeps our tasks and documentation in total sync.

Here is the exact blueprint of how we manage our internal Product, Engineering, and Design workflows without the typical ‘Alt-Tab tax’ of switching between Jira and Notion.

1. Spaces: The Organizational Foundation

We organize Superthread into Spaces based on functional teams. This creates a clear home for everything related to a specific department.

• Team Spaces: We have dedicated spaces for Core Product, Front End, Backend, and Design.
• Feature Spaces: For massive, cross-functional initiatives, we create temporary spaces to keep that specific feature’s docs and tasks isolated from the daily grind.

2. The Product Workflow: From Triage to Shipped

Within our Product Space, we maintain four critical boards that track the lifecycle of every feature:

• High-Level Roadmap: This is our ‘North Star’ view. It contains the highest-level strategic tasks we need to achieve.
• Roadmap (Epics): This is where the actual execution lives. Each task here is an ‘Epic’ that contains multiple Child Cards.
• Product Triage: The landing zone for all new ideas, feedback, and requests. Nothing goes to the Roadmap without passing through Triage first.
• Shipped: Once an Epic is finished, it moves here. It’s our permanent record of progress and a central hub for release notes.

3. Cross-Team Execution with Child Cards

One of our most powerful internal workflows involves Child Cards. An Epic on the Product Roadmap often requires work from both Front End and Backend teams.

• We create the Epic in the Roadmap board.
• We then create Child Cards inside that Epic.
• These Child Cards are moved into the specific Active Development boards for the Front End or Backend spaces. This allows me to open a high-level Epic and see exactly which developer is working on each technical sub-task, regardless of which Space it lives in.

4. Docs and Tasks: The ‘Stacks’ System

Underneath our boards, we use Stacks. This is where we keep the ‘static’ knowledge that powers our ‘dynamic’ tasks.

• Documentation: Technical specs and architecture docs live in Stacks right next to the active sprint.
• Customer Discovery: I maintain my own board for user interviews, linking notes directly to task cards so the context is never lost.

5. Speed Tools: Command+K and Private Notes

Because we value speed above all else, we use two shortcuts religiously:

• Command+K: Our global search. I can jump to any card, page, or board in less than a second.
• Quick Notes: Using the C shortcut, I can fire off a quick thought to my Private Space. This keeps my brain clear while ensuring no good idea gets lost.

Experience a workspace designed by builders, for builders.

Stop juggling separate apps for your docs and tasks. See how much faster you ship when everything is in one place. Sign up for Superthread for free

Further Reading & Resources

• The Anti-Bloat Philosophy: Why we built a faster alternative to Jira.