# ODT Cohort

<figure><img src="/files/NLNbVMAytDa5HozBjHyv" alt=""><figcaption></figcaption></figure>

### Introducing: the Outcome Driven Teams Cohort

OKRs can be a hard change to roll out.

We write a lot about it, spend many hours with our users talking about it. It's time to do something about it.

We're launching a structured program to teach a pragmatic approach to OKRs with Tability. The end goal: achieve ruthless prioritisation and faster results.

**How it works:**

* Small cohorts of 5 people
* 1h/week for 4 weeks
* $200/person
* 2-month for free on Tability if you do not have an existing paid workspace (this program is centred around Tability, and how to use the platform effectively with OKRs).

**How to apply:**

We have limited seats (5 per cohort) and can only run 2 cohorts at a time.

👉 **Please fill in the** [**application form here**](https://tability.typeform.com/to/mKt4zJ4L) **to reserve your seat** 👈

We will then contact you to put you in the right cohort for your time zone.

### Program content

**Week 1: OKR for Prioritisation – introduction**\
\- Using OKRs as guardrails\
\- Roles and rollout schedule\
\- Top-down vs. bottom-up approach\
\- Culture and rituals\
\- The mistake that everyone makes

**Week 2: Setting good OKRs**\
\- Defining objectives\
\- Measurable key results vs. KRs for projects\
\- How many KRs per owner/plan\
\- Avoiding perfection\
\- Aligning vs. cascading OKRs\
\- Connecting OKRs to project roadmaps (now, next, later)

**Week 3: Tracking OKRs**\
\- Good status reporting\
\- Yellow and red rules\
\- Automation and integrations\
\- Reflection and adjusting roadmaps/goals

**Week 4: How to be ruthless with execution**\
\- Ruthless doesn't mean rude\
\- Honest reporting and hero culture\
\- Rigid outcomes, flexible outputs\
\- Objectives over KRs\
\- Conversations over reporting

👉 **Please fill in the** [**application form here**](https://tability.typeform.com/to/mKt4zJ4L) **to reserve your seat** 👈


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guides.tability.io/docs/tability-university/odt-cohort.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.