Documentation
How to use Decize.
Every feature, in the order you meet it, with its real limit stated beside it. If you want the argument for why the mechanism is trustworthy instead, that is on How it works.
Getting started
A workspace, a roster, an address.
Three things exist before anything else works. Setting them up takes about five minutes and you only do it once.
Create the workspace
Sign in and create a workspace. Its handle becomes part of your capture address, so pick something you would be happy typing into a To: field — “northwind-labs”, not “ws-2”.
Add the people who decide
Add teammates by email address on the Team page. They do not need an account to take part: a person on the roster can capture decisions and answer outcome questions entirely from their inbox. They need an account only to browse the ledger in the app.
Every plan is unlimited people. Decize meters decisions, never seats.
Say what your team values
In Settings, list the handful of values your team actually decides against. Once they exist, Decize scores how a decision serves or strains them — and leaves that scoring labelled as an estimate until a person confirms it.
Optional. With no values set, Decize records no alignment rather than inventing one.
Choose what a capture must include
Also in Settings: whether logging a decision requires an owner, a due date, a confidence rating or an expected impact. Turn things off if capture is getting skipped — a shorter record that gets written beats a complete one that does not.
Capturing decisions
Three ways in, and none of them is a form.
You write the decision the way you would say it. Decize proposes the structured fields, and a person corrects what is wrong before it counts.
Type it in the app
Use the capture box on your workspace home. Plain language is enough: “we're moving the EU customer data to Frankfurt before the June renewal, Priya owns it”. Decize drafts the title, summary, owner, deadline and whether it is reversible.
Send or forward an email
Write to your capture address, or forward a thread to it. Same result as typing it in — see the email section below for the detail.
Import what you already decided
Paste a retrospective, an architecture decision record or a project history into Import. Decize pulls out the decisions the document already records, including outcomes it already states, and you approve them row by row.
Import is a paid feature. Nothing is written until you approve each row.
Check the duplicate warning before you save
If what you are logging closely matches something already on record, Decize shows you that earlier decision first, with its outcome. You can continue anyway — it is a prompt, not a block.
The record
What each field is actually for.
Nothing here is metadata for its own sake. Each field changes what happens later — who gets chased, what gets re-read, what you can be scored against.
Owner and deadline
Who is accountable and by when. These drive the reminders and the “needs attention” queue. A decision with no owner shows up as unowned rather than quietly sitting still.
Reversibility
A one-way door or a two-way door. This is the field that should change how much time you spend: cheap to undo means decide fast, hard to undo means slow down.
Confidence and the forecast
How sure you are, on a 0–4 scale, and optionally a specific prediction with a date it resolves. This is what makes calibration possible later — you cannot find out whether your judgement is good without recording what you expected at the time.
A confidence Decize inferred from your wording does not count toward calibration until a human confirms it.
Outcome and lesson
How it actually went, and the one line worth carrying forward. Recorded after the fact, usually from an email. This is the field that makes the ledger worth keeping.
Deleting a decision
Owners and managers can delete a decision outright from its page. It is removed, not hidden.
Owner or manager only.
Running the whole thing from a mail client.
Your workspace has an address of its own. Everything below happens without anyone opening Decize.
Find your capture address
Workspace Settings shows it. It looks like your-workspace@in.decize.app, sometimes with a secret token after a plus sign. Treat it like a shared mailbox address: paste it into threads, add it as a Cc, save it as a contact.
Who is allowed to send
People already on your roster. You can also allowlist a company domain — but a domain match never admits a stranger on its own: it queues them, and an owner approves with one tap from the daily summary email.
Mail from anyone else is refused and reported to the owner, never silently logged.
Rotate the address if it leaks
Settings has a rotate button. The old address keeps working for a short grace period and then stops, so a leaked address in an old thread does not stay a way in forever.
What Decize sends back
It confirms what it logged — the title, owner and date it read — so you can catch a bad reading immediately. If the decision closely matches one already on record, the reply names that earlier decision and links to it.
At most one reply per thread per day, twenty a day for the whole workspace, and an owner can switch replies off entirely in Settings.
Ask the ledger a question
Email the capture address something like “did we ever settle on the enterprise pricing?” and Decize answers from decisions your team has actually recorded, naming them and when they were made. A question is never logged as a decision.
Off by default. An owner enables it in Settings, and Decize will not answer a sender whose mail fails SPF, DKIM and DMARC — an unverified From is refused so the address cannot be used to read your ledger.
When nothing happens
Most messages are not decisions, and Decize stays silent rather than guessing. Discussion, scheduling, agreement in principle and thinking out loud are all left alone. If it could not read a decision it will tell you why rather than failing quietly.
Follow-through
The part that runs itself.
Recording a decision is the easy half. This is the half that makes the record mean something a year later.
Reminders as the deadline approaches
Owners get nudged on the cadence you set in Settings, and overdue decisions escalate. You control the frequency; if it is too much, turn it down rather than letting people mute it.
One-tap outcomes
About two weeks after a decision matures, the owner gets an email asking how it went. The answer buttons are in the message — went well, mixed, regret, didn't matter. One tap, no login.
The follow-up window is configurable in Settings.
The retrospective writes itself
Recording an outcome triggers a short retrospective comparing what you predicted against what happened, plus a one-line lesson that stays attached to the record and surfaces on similar future decisions.
Reports
What leadership sees, and what it cannot see.
Everything here is an aggregate over the workspace. There is no per-person score anywhere in Decize, by construction rather than by policy.
The dashboard
Open, overdue, unowned, awaiting an outcome, forecasts ready to resolve — one attention list, plus median days from capture to decided and how often the loop actually closes.
The weekly and monthly email
A Decision Health rollup goes to owners and managers each Monday, and a longer one on the first of the month. Owners can add extra recipients in Settings — a board member or an investor who should see the numbers without an account.
Included on a paid plan.
The PDF report
Each digest carries a link to the same numbers as a PDF. It needs no sign-in, which is what makes it forwardable — the link is tied to the person it was sent to, expires after 45 days, and stops working if that person leaves the workspace.
CSV export
Owners and managers can export the full ledger, the roster and the goals as CSV, plus the activity log separately. It is your data and it leaves in a format anything can read.
Export is a paid feature.
Why a number sometimes says “not enough data”
Every rate is suppressed until at least 5 decisions sit behind it, and the outcome-closure trend wants roughly ten weeks of steady capture. A percentage computed from two decisions is noise wearing a number's clothing.
Roles
Who can do what.
Three roles. The split is about blast radius, not seniority.
Member
Captures decisions, records outcomes, reads the whole ledger. Every active member can read every decision in the workspace — treat it as an internally public document.
Manager
Everything a member can do, plus the dashboard, the analytics, the roster, workspace settings, export and deleting a decision.
Owner
Everything a manager can do, plus changing roles, approving new email senders, billing, and the workspace itself.
Plans
Metered on decisions, never on people.
Adding a colleague costs nothing on any plan. The meter counts decisions logged in a calendar month.
What each plan allows
Free includes 10 decisions a month. Team is $99 for 50, Business is $249 for 200, and Unlimited removes the cap. Digests, export and import come with any paid plan; forecast calibration starts on Business.
Going over the allowance
Nothing is blocked. Capture keeps working over the limit, deliberately — the hard part of this product is getting teams to log decisions at all, and a meter that punished logging would defeat the thing it measures.
Cancelling
Manage or cancel the subscription from workspace Settings. Your data stays exportable.
Honest limits
What Decize does not do.
Worth knowing before you roll this out, rather than after.
There is no private decision
Every active member of a workspace can read the entire ledger, including the original captured message. There is no per-member visibility control. If something must not be seen by the whole team, do not log it here.
There is no Slack app yet
The capture pipeline is email. Slack capture exists in the codebase but is not something you can install today.
AI reads are labelled as reads
Anything Decize inferred — a value alignment, a confidence, a summary — is shown as a proposal until a person confirms it, and an unconfirmed confidence never counts toward your calibration score.
It is early
Decize is a young product and says so. If something is missing or wrong, the contact page reaches a person, not a queue.
Something here not matching what you see?
This page describes what ships today, and it is maintained alongside the code rather than written once. If a screen disagrees with it, that is a bug worth telling us about.