Preview. Operating Desk isn't open yet. Words and details may change before launch.

Help

How Operating Desk works.

Getting started

Setup takes five steps, one per screen. You can go back at any step until reading starts.

  1. Accept the invite. Open your invite email and tap Accept the invite.
  2. Sign in. We'll email a sign-in link to your address. No password needed. Links work for 15 minutes. If yours has expired, tap Get a new link.
  3. Boundaries and GitHub. These always wait for your yes: sending, publishing, deploying, spending, deleting and changing access. Then connect one GitHub repository.
  4. Reading your workspace. We read your repository and find the gaps.
  5. Your gap map and first plan. Pick a gap, and your first plan shows up as a decision card.

Can't find the email? Check your spam folder. Make sure you used the address your invite went to. Still nothing? Reply to your invite email and we'll help.

Your preview covers one repository. If the read finds nothing to work on, you can pick another repository before you use a decision.

Your gap map and first plan

Your gap map shows what's missing in your repository. Each gap has one line on why it matters.

Pick one gap to start. Your first plan shows up as a decision card on your Desk.

Your Desk and decision cards

Your Desk is where every decision waits for you. Tap Your Desk at the top of any screen to get back to it.

How a card works: each card asks one question. It says why, what it starts and how we'll prove it. Tap Approve to go ahead or Decline to say no.

When a decision is waiting, the work item says so: "A decision is waiting on your Desk."

Approved, Built and Verified

Every piece of work moves through three steps. You see where it is on the strip at the top of the work item.

Nothing is Verified because someone says so. It's Verified only when every check in its proof passes.

What the proof shows: open a Verified work item to see what was checked. For example: every change we made matches what you approved, nothing is on hold, and GitHub is fully checked. Each check shows only if it applies to that piece of work.

If something changes later, such as the plan or the change that was added, the work goes on hold until someone looks. It's checked again, and it returns to Verified only if the proof still holds.

Not Verified yet? See When something stops for Blocked and Proof incomplete.

When something stops

Work that stops is never shown as Verified. You'll see one of three labels, each with what happened and what's next.

Blocked (red): a check failed, so this piece of work isn't Verified. It stays at Built, and nothing else runs. The card says which check failed and what happens next. We never retry an action on our own.

If an action is stopped before it's Built, it stays at Approved.

Proof incomplete (amber): we can't fully check a tool, so the work stays at Built. The work itself is saved. Only the proof is missing. The card says why, for example "GitHub is disconnected.", and what's next.

On hold: if something changes after Verified, such as the plan or the change that was added, the work goes on hold until someone looks. It's checked again, and it returns to Verified only if the proof still holds.

Nothing restarts on its own. We check again when this piece of work moves to its next step.

The six that always wait for your yes

Six kinds of action always come to you first: sending, publishing, deploying, spending, deleting and changing access.

Your preview and what comes after

Your preview is free for 14 days. It covers one workspace, one repository and up to 3 decisions. It takes one real piece of your work to Verified.

What uses a decision: each Approve. Declining your first plan, picking one piece of a bigger request and a card on hold don't.

After the preview: move to Paid to keep going.

Want a hand? We also run a paid pilot and a fuller managed service. Talk to us.