1:1s & Roadmaps

If you meet people every week and talk about short-term and long-term things, this is where that lives instead of OneNote or slides. One engine, reached two ways:

You want	Go to	It holds
Your 1:1 with someone	Their 1:1 tab: /people/<id>/1on1, or 1:1 → on their Team page	Their goals, your weekly notes, agreed to-dos, your private notes, the HR record
A product or program's direction (Otium, AxPILOT…)	The project's ◇ Roadmap button	Goals, the weekly team check-in, and the linked projects' hours, open work and next milestone

/roadmaps (1:1s & Roadmaps in the sidebar) lists all of them, and suggests 1:1s from your calendar: people you meet one-to-one every week who don't have a 1:1 page yet, with a Start 1:1 button.

1:1s

A 1:1 belongs to you and is about one person. They see their goals, the weekly notes and the to-dos; never your private notes or the HR record. When you add a to-do for them, pick Log time under right there (their projects and tasks) so their hours land in the right place from day one; otherwise it shows No project on their board until they pick one.

Roadmaps on projects

On any project, ◇ Roadmap creates one (or opens it). A roadmap can cover several projects, e.g. AxPILOT across Peter Standalone and Peter in Wiki and Applications: pick them when creating it or later in ⚙ Settings.

• Everyone on those projects' teams sees it automatically; no member list to keep up to date.
• The Projects panel shows each project's hours this week, this month and in total (against budget), open and overdue work, the next milestone, and who logged time this month.
• To-dos you add go into the project you pick (time logs from the start); the person has to be on that project's team.

The calendar

Otium reads your synced Outlook calendar: a 1:1 shows the next and last meeting with that person, and a roadmap shows its weekly meeting (by name, or set Calendar meeting in ⚙ Settings, e.g. "OTIUM CHECK IN").

Progress: timeline, snapshots, charts

At the top of every 1:1 and roadmap, Progress shows:

• Timeline, two months back to six ahead: goals with target dates (coloured by status), each linked project's ◆ milestones from its Gantt, a line for today, and a 📸 for every meeting. Click a 📸 to see that week.
• Coming up, next 30 days: goals and milestones due soon, and anything past due.
• Charts that fill in over time: goals by status week by week, to-dos finished per week, and each linked project's hours climbing against its budget (dashed line).

Every meeting is a snapshot. When you save the check-in, Otium records where things stood: goals by status, to-dos done since last time and still open, and each project's hours, budget used and open work. If you didn't write notes, it takes the snapshot the day after the meeting shows on your calendar. Open an earlier week to see "📸 At the meeting…" with that day's numbers.

The overall Timeline on 1:1s & Roadmaps shows project milestones too.

What every page has

1. Goals: the long-term priorities (3–6 is plenty), each with a target date, an owner and a status: On track, At risk, Off track, Done, Dropped. Change the status right on the goal; it's the first thing to review at a check-in.
2. Action items: the short-term to-dos agreed for the week. Each one is a normal task: it lands on its owner's My Tasks board, has a due date (default: Friday of that week), and can be linked to a goal. Open action items carry over week to week until they're done, so nothing gets lost.
3. Meeting notes, one entry per week: Discussion, Agreed / decisions, and 🔒 Private notes that only you (the owner) ever see. On a 1:1 there's also 🗂 Add to HR record (see below).

A weekly check-in

1. Open the roadmap (it opens on this week; ← → moves between weeks).
2. Go through the goals and set their status.
3. Look at last week's action items: done ones are in Done; drag or tick the rest.
4. Add this week's action items with + Add an action item (choose who and when).
5. Write the discussion and what you agreed, and save.

History is kept forever

• Past meetings lists every week's notes, newest first, with no cut-off. Each week also shows the goals as they stood that week, colored by status.
• If you rewrite a week's notes, the earlier version is kept (the week shows "edited 2×").
• Every goal change is recorded: created, each status change, target date moves, renames, with who did it and when. Under each goal a strip of 12 squares shows its status at the end of each of the last 12 weeks, and History lists every change.
• Moving to an earlier week (←) shows each goal's status that week, including goals removed since.
• Remove on a goal hides it from the roadmap but keeps it and its history on file.

HR record (1:1s only)

On a 1:1 roadmap the owner has a fourth box, 🗂 Add to HR record, for what should be on file: performance concerns, recognition, warnings, promotion or pay conversations.

• Who sees it: you and HR (admins and people with HR access, on the person's HR profile). The person doesn't see it on their 1:1 page.
• Permanent: an entry can't be edited or deleted. To correct one, add a new entry.
• Each save adds a new dated entry; the box starts empty again.
• The person's HR profile shows their 1:1 roadmaps: the goals with full history, which weeks a 1:1 was written up, and the HR record. HR doesn't see the discussion notes or your private notes.

Check local rules with whoever handles HR: in some places (Massachusetts, for one) employees have the right to see their personnel file.

The overview

/roadmaps shows a card for every roadmap: goals at risk or off track, open and overdue action items, and whether you've checked in this week. Cards with problems have a red edge. Ones other people own and added you to are under Shared with me.

Timeline

Roadmaps → Timeline puts every goal with a target date on one month-by-month view, one row per roadmap, colored by status (green on track, amber at risk, red off track, grey done), with a line for today. Goals without a target date are listed underneath. Click any goal to open its roadmap.

Development leaderboard

A roadmap whose linked project is a software project (Otium → OtiumWork Development) shows a Development panel: for each person, features, bug fixes and upkeep (docs, tests, deploy scripts) this month and all time, a bar per person per month, and the latest commits with whether they're live yet.

• The numbers come from the code's history. Each time code is pushed from the developer's machine, the commits are sent to Otium; Otium never connects to GitLab.
• A commit counts as a feature or a fix from its label (feat:, fix:), or from its message when it has none.
• Someone's several git identities count as one person.
• It counts commits, not their size: a one-line fix counts the same as a new module.
• AI employees' commits count too, each under its own name (Developer, QA), credited to the agents of the roadmap's workspace.

Users' reports (the workspace that runs Otium)

On the roadmaps of the workspace that runs Otium, the owner (only) sees Users' reports: every open bug report and feature request from users in any workspace, with its age, where it stands (new, being worked on, fixed on staging, approved and waiting for prod) and who's on it. Bugs nobody is on yet are in bold. Two charts show, week by week, bugs reported against bugs fixed, and how many were still open at each week's end, so you can see whether the queue is shrinking. The header gives the oldest open bug and the median days from report to fix. Reporters are shown by first name and workspace, never by email.

Who does the work: people vs AI agents

Above the leaderboard, the roadmap's owner (only) sees Who does the work: for each person and each coding AI employee over the last 4 weeks, features and fixes shipped, hours, cost, and hours and cost per shipped item, with totals for people and for AI agents and two week-by-week charts (shipped, cost).

• People: hours are their tracked time on the roadmap's projects; cost is hours × their hourly cost (Admin → People). Until a rate is set, their cost shows "no rate".
• AI agents: hours are their run time; cost is what the runs would cost at API prices. Runs on your own Claude subscription are marked covered: you don't pay that amount, it shows what they would cost on the API.

Who sees what

• You (owner) see everything, including private notes, and you're the only one who can hand action items to other people, change members, rename or archive.
• Members see the goals, action items and the shared notes, can update goal status, add action items for themselves, and write in the shared notes. They never see private notes or the HR record.
• HR (on the person's HR profile) sees a 1:1's goals and their history, the 1:1 dates and the HR record, never the discussion or private notes.
• Nobody else sees it, admins included. These are management notes.

From Claude

With the OtiumWork connector you can say: "prep me for my check-in with Stan" (Claude reads his roadmap: goals, what he committed to and whether it happened), "add to Carla's check-in: agreed to move the webinar to November", "put on Stan's HR record: missed the September target twice", "create a roadmap for NMIT with goals X and Y", or "which goals are off track across my team?".