This post is part of the Drift 101 series—simple, real-world introductions to the building blocks of The Drift Method.
Last time, we explored Beacons—the guide stars that help you set direction without getting trapped in rigid goals. But what happens when your work gets layered—when a single Flow starts branching into multiple streams, and clarity starts to slip?
That’s where Subflows come in.
In this post, I’ll share how Subflows help me break down complexity, keep my work organized, and avoid the trap of over-managing every detail. If you’ve ever felt your projects or routines getting tangled as they grow, Subflows might be the gentle structure you need.
1. When Flow gets tangled
Every Flow starts out simple. There’s a clear direction, a set of Steps, maybe a Kit or two. But as the work grows—especially in long-lived Flows—things can start to branch out. Suddenly, what was once a single stream now has subprojects, subprocesses, or even whole areas of work that want their own space.
I’ve seen this happen in everything from product launches (where design, content, and outreach all need their own attention) to coaching practices (where client management, marketing, and curriculum each become their own world).
Even small teams run into this: three or four people, each juggling multiple roles, quickly find themselves needing to keep separate efforts organized, but still connected.
The signs are familiar:
- A Flow starts to blur, with too many strands running together
- Notes pile up, steps get mixed
- It’s harder to see what matters most
That’s when I know it’s time to consider a Subflow.
2. What a Subflow is (and what it isn’t)
So, what is a Subflow in Drift?
A Subflow is simply a Flow nested inside a larger Flow.
Structurally, it’s no different from a regular Flow—it has its own notes, steps, kits, and views—but it only really makes sense in the context of the parent Flow. Subflows are focused containers for specific strands of attention, not separate projects or isolated folders.
They’re optional and temporary tools to reduce cognitive load, not to create more bureaucracy. Subflows clarify, not complicate.
Where do Subflows shine?
Any time you have a body of work that’s best kept together, but benefits from being partitioned off for clarity. Think of business teams: marketing, product, operations. Or creative projects: writing, editing, publishing. Each could be a Subflow, all working in harmony within the main Flow.
Personal example:
In my day-to-day work, I use Subflows for different areas and discrete roles—like business administration, or marketing. As Drift evolves, I expect to add more Subflows for things like content production or community engagement. The key is that each Subflow only exists because it serves the larger Flow.
3. How Subflows bring clarity without fragmentation
Subflows scratch an itch that a lot of traditional systems miss. They let me honor the human tendency to want some boundaries (some rooms within the workshop) without losing the big picture.
Mentally, it’s a relief. I don’t have to keep everything in one place and risk overwhelm, but I also don’t have to spin off a dozen separate projects that lose context.
Subflows let me zoom in when I need to, then zoom back out and see the whole landscape from above.
The difference between a well-used Subflow and an unnecessary layer is simple: a Subflow exists because it’s useful. If it’s helping me or my collaborators keep things clear, it stays. If not, it’s just another box to check, and I let it go.
A Flow is like a workshop, filled with Notes, Kits, Steps, and Views that help it produce things.
A Subflow is like building a room within that workshop for a specific purpose—welding, painting, or repairs. The room’s utility is defined by the larger workshop it exists within.
4. How I use Subflows in practice
When do I create a Subflow?
Usually, it’s when one part of a Flow gets “thick”—when there are enough Steps, Notes, or other resources that keeping them together would muddy the main Flow. I don’t overthink it: if it feels like a natural boundary, I make the Subflow.
In Drift, a Subflow looks just like a regular Flow, but it’s nested inside another. Notes, Steps, Kits, Views—all the basics.
And if you ever need to go deeper, you can nest again (though two or three layers is usually plenty, and often more than enough).
The beauty of Subflows is that you don’t have to check them constantly. I use them when I need to, and let them rest when I don’t. They’re there to help filter and focus, not to add another layer of “stuff” to manage.
5. When Subflows multiply or fragment
It’s easy to think that breaking work down will just create more to manage. But in Drift, Subflows are only there if they’re helpful. If you find yourself with too many, or if a Subflow is no longer useful, it’s time to merge, archive, or let it go.
The core question is always: “Is this helping me?” If yes, keep it. If not, don’t.
You can always zoom out to the parent Flow and see everything from above. If you’re keeping the basics—notes, steps, kits, views—tidy, your Subflows will stay organized too.
If you’re new to Drift, don’t worry about Subflows right away. Start simple. When your work naturally starts to branch, Subflows will be there for you. They’re not a requirement—they’re a relief.
Subflows are rooms within your workshop
You don’t need to micromanage your way through complexity. You just need a way to hold the different threads of your work without losing the whole.
Subflows are how I keep projects, teams, and layered efforts moving gracefully—even as things get more complex. They let me break things down without breaking my rhythm.
If you’ve got a part of your work that’s starting to feel tangled, try sketching a Subflow—even just a list or a simple page. See if clarity returns.
Try The Drift Method
The Drift Method is open and adaptable. There’s no one way to use it — just principles and a system to help you move forward.
🔹 Learn more — Take a look at the Drift Method resources on the website.
🔹 Start using The Drift Method today — Get the free Starter Guide, or set up in minutes with the Notion Kit.