ع
Start Topics Teams Reference What's new Saved
Working knowledge

Your team's operating guide

How does my team actually run this day to day?

Short answer

An operating guide is the layer above individual tasks: who owns a decision, what material your team may share, and which check a piece of work must pass before it leaves the building. There is one below for each of nine teams.

This page is an index, not an explanation. Nine guides sit below — one each for Business Analysis, Data & Analytics, Engineering, Finance & Ops, Founders & PMs, Marketing, People & HR, Sales, and Customer Support. Read the one for your team. Skim a second only if you genuinely sit between two.

They’re built to the same shape on purpose, because the questions a team has to settle turn out to be the same everywhere: what the operating model is, what material is safe to hand over, who owns the decision when Claude is confidently wrong, how to work across Arabic and English, and what a staged path looks like so a team can start with one small honest use and grow into the harder ones rather than attempting everything in month one.

What differs — and it’s the part worth reading closely — is the gate each team’s work has to clear before it reaches anyone outside the team. Marketing’s is brand and legal. Finance’s is verification and sign-off. People & HR’s is fairness and confidentiality. Support’s is who holds authority over a refund or a policy statement. Data’s is whether the numbers reconcile and the definitions hold. Engineering’s is review and proof. Same structure, different thing that must not go wrong. If a rollout has stalled at “people are using it, but I’m nervous,” a missing gate is almost always what you’re feeling — start there, then come back to rolling Claude out to a team.

Read more