Home› How to Run the Framework
Step-by-Step Guide

How to run the framework
with your team

From first assessment to first action in less than one week. Works with any team of 3–15 people, any industry, any level.

⏱ ~90 min total setup 👥 3–15 people 💰 Free to run 🔁 Repeatable every 30 days
The Process

7 steps to run your first cycle

The Better Together Framework is designed to be practical, not perfect. Follow these steps in order — skip none, rush none.

1
Step 1 — Before you begin

Assemble your team

The ideal group is 3–15 people from the same team, pod, or working group. It doesn't matter if they're engineers, designers, sales, or support — the framework works across functions. One person takes the facilitator role (usually the manager, but it can be anyone the team trusts).

The facilitator's job is light: share the assessment link, schedule the review session, and lead a 60-minute conversation. No data expertise required.

Practical tip: Don't run it with your entire company in one go. Start with one team, iterate, then expand. A bad first run kills buy-in.
2
Step 2 — Day 1

Send the self-assessment

Share the link to the Quick Assessment on this site with every team member. Each person answers 5 questions — one per dimension — in about 15 minutes. It's anonymous. Their individual scores are private.

Send it via Slack, email, or your team channel. Make it clear: there are no wrong answers, no performance evaluations, and no one can see individual results. Only the aggregate will be shared.

What to say: "Hey team, I'm running a quick 15-minute assessment to understand how we're doing as a group. Everything is anonymous and no individual scores will be shared. Link: [URL]. Please complete it by [date]."
3
✓
Step 3 — Days 2–5

Wait for responses

Give your team 3–5 days to complete the assessment. Don't rush it — people forget, get busy, or need a reminder. Send one gentle nudge on day 3 if response rate is low.

Aim for at least 70% participation before drawing conclusions. Below that, the results can be skewed by a single person's outlier response. With fewer than 5 respondents, aggregate results may not be meaningful.

Minimum threshold: 70% of the team. If you have 10 people, you need at least 7 responses before reading the results as a team signal.
🎙️

Get the full Facilitation Guide

Scripts, talking points, and how to handle tough moments when discussing team results. 15 pages, free.

4
Aggregate — anonymous
Step 4 — Day 6

Review the team radar

Schedule a 60-minute session with the whole team. Share your screen — show the aggregated radar (the pentagon with all 5 dimensions). Walk through each dimension: what it measures, what score the team got, and what the research says about it.

Critical rule: never show individual scores. Only the team average. Even if you know who scored what, that information stays private. Violating this kills psychological safety fast.

Facilitation tip: Start by asking "What surprised you about these results?" before offering your own interpretation. Let the team read it first.
5
Step 5 — Same session

Choose one dimension to improve

As a team, pick one dimension to focus on for the next 30 days. It should be the lowest score, or the one the team feels is most urgent. Not both. Not three. One.

The most common mistake is trying to fix everything at once. Teams that commit to a single focus see measurable improvement in 30 days. Teams that spread their energy across 3–4 dimensions see improvement in none.

The vote method: If the team can't agree, give everyone 2 votes to allocate across dimensions. The highest total wins. No debate needed.
6
Owner ✓
Step 6 — Same session

Define 1–2 concrete actions

Once you've chosen the focus dimension, define 1–2 specific actions to take in the next 30 days. Each action needs three things: what it is, who owns it, and by when. Vague commitments don't stick.

Keep it small and doable. "No-meeting Fridays for the next 4 weeks" is better than "improve our work-life balance culture." One thing done well beats five things started and abandoned.

Check the examples below — for each of the 5 dimensions, we've listed concrete actions that teams have used successfully.
7
30 days
Step 7 — Day 30

Re-run in 30 days

One month later, repeat the process. Send the same assessment, gather responses, and compare the new radar to the one from 30 days ago. Did the dimension you focused on improve? Why or why not?

The data over time is where the real value comes from. A single assessment is a snapshot. Four consecutive cycles is a trend. After 3 months, you'll know which interventions actually worked for your team.

The goal is progress, not perfection. A 5% improvement in one dimension over 30 days, sustained over 6 months, compounds into something real. That's the point.
Concrete Examples

Actions by dimension

Need inspiration for Step 6? Here are proven actions for each dimension — specific, assignable, and completable in 30 days.

Burnout
  • Declare no-meeting Fridays for 4 weeks — protect focus time
  • Manager sends a "blocking blocker" message each Monday: "What can I remove from your plate this week?"
  • Team agrees on a daily "log off" time — no Slack after 7pm for 30 days
  • Cancel or decline any recurring meeting no one can name a clear purpose for
Psychological Safety
  • Start every retro with "one thing I got wrong this week" from the manager (models vulnerability)
  • Add an anonymous question box (Google Form) for the team — shared publicly in retro
  • Establish a "no bad ideas" brainstorm rule for 30 days — no critiquing during ideation
  • When someone raises a concern, respond with "Tell me more" before any evaluation
Goals Clarity
  • Each person writes their top 3 priorities for the week in a shared doc — reviewed in standup
  • Add a "why this matters" line to every ticket or task description
  • Run a 30-minute "expectation reset" — each person shares what they think their job is; manager corrects misalignments
  • Create a one-page team charter: mission, key metrics, and who owns what
Work Productivity
  • Block 2-hour "deep work" slots in everyone's calendar — treat as unmovable
  • Audit tools: remove any software the team hasn't used in 30 days
  • Agree on one async-first rule: every request gets a 4-hour response window before escalating to a call
  • End every standup with "What's your one most important thing today?" — say it out loud
Work-Life Balance
  • Manager explicitly says "It's fine to not respond to this until tomorrow" in after-hours messages
  • Cancel the lowest-value recurring meeting and redistribute that time as protected personal time
  • Team agrees: no Slack on weekends unless it's a production incident (define what "incident" means)
  • Pilot 4-day workweeks for one month — track output, not hours
The Automation Layer

Want this to happen automatically?

The framework works. Tribu removes the manual work — automatic daily pulses via Slack, real-time team radars, AI-powered reports, and HRIS integrations. No spreadsheets. No reminders. No friction.

⚡
Auto pulses in Slack 2 questions/day, sent automatically. Zero setup per cycle.
📊
Live team radars Your 5 dimensions update in real time. Compare week over week.
🔗
HRIS integrated Connects to BambooHR, Gusto, Jira, Asana, and 20+ tools.
See Tribu → Add to Slack
Join community in Slack