How we design team ops inside tāep

Hi fam,

This week, let’s zoom out:
How do you scale that structure across a team without becoming rigid or slowing down innovation?

At our brands, we’ve baked energy-first execution into how our entire team operates.
From product to marketing to fulfillment everyone works differently, but we still move in sync.

Here’s exactly how we do it:

1. Everyone knows their Power Zone

The same energy-mapping exercise I shared last time?
Every full-time team member does it.

We ask:

• When do you feel most focused and creative?

• When are you best at communication and meetings?

• When do you crash?

Then, we map each person's energy curve into our team ops not against it.

2. We run async by default and sync with intention

Unless it’s a creative jam session or a decision block, we keep things async.
That means:

• Daily standups are Looms or Slack voice notes

• Weekly updates are Notion dashboards + Miro comments

• Everyone works to outcomes, not hours

When we do meet live, it’s structured. Everyone preps. No “let’s wing it” calls.

It’s not about being anti-meeting. It’s about being pro-momentum.

3. Clear lanes + deep accountability

Every team member owns a specific area:

• Product strategy

• Paid growth

• Ops + CX

• Brand + content

• Logistics

There’s no ambiguity. If it falls under your lane, you’re the bottleneck or the builder.

This creates calm. No one’s wondering who’s responsible or waiting for permission.

4. Strategic rhythm: 6-week cycles

We don’t sprint endlessly. Instead, we run in focused 6-week cycles:

• Week 1: Plan (decide big rocks, commit to outcomes)

• Week 2–5: Execute (no new inputs, just do)

• Week 6: Reflect (what worked, what broke, what’s next)

It keeps us iterative but sharp.
No one’s burning out. And no one's stuck in perfection mode either.

5. Culture of ownership, not surveillance

We hire adults. We don’t track hours or ping people with “quick updates.”

If someone disappears, we check in human-to-human. If things slip, we ask what support is needed.

But the baseline expectation is this:
Own your lane. Move the needle. Communicate clearly.

That’s it.

If you’re building a lean team or want to simplify your ops, start with energy.
Not tools. Not hours. Energy.

Next week, I’ll share how we do decision-making in tāep especially when there’s no clear answer or you’re juggling speed vs. quality.

If you're already running a team and want to map this into your own ops, hit reply I’ll share a custom framework we use.

Build calm. Build well.

Cheers,
Markus