The decision log for teams of 10–150Didn’t we try this last year?
Cc Decize on the email where your team decides. It logs the decision, asks the owner how it turned out a couple of weeks after it’s due, and answers the next time someone asks, right in the thread.
Free for 10 decisions a month · unlimited people · no card
Customer support: outsourcing
TR
Tom Reyes
To: Maya Chen
Cc: vantia+k7q2m8xd@in.decize.app
Agreed. From Nov 1 we outsource customer support to Northfield. Maya owns the switch.
Decize
To: Tom Reyes · Cc: Maya Chen
Logged: Outsource customer support
Owner
Maya Chen
Due
Nov 1
Open in Decize
Illustrative workspace. Vantia is fictional.
It’s in a thread somewhere.
Decisions get made in email. The one that matters lands in message 9 of 23, nobody writes it down, and months later the team pays for the same decision twice.
Re: Customer support: outsourcing23 messages
Without Decize
8 earlier messages
TR
Tom ReyesMessage 9
OK, let’s go with Northfield from Nov 1. Maya, can you own the switch?
Decided here. Never written down.
11 more messages
PS
Priya Shah6 weeks later
Wait, who owns this?
SO
Sam Ortiz2 months later
Why did we do it this way?
DK
Dana Kim3 months later
Did that actually work?
How it works
Follow one decision, start to finish.
Between Oct 1 and Jan 12, the team Cc’d one address, marked the switch done, and answered one question.
Thu, Oct 1 · 9:42 AM
Cc one address.
Tom Cc’s it on the email where the decision is made. Decize writes the record and replies in the thread.
1Title and summary, drafted from the email.
2Owner and due date, when the thread names them. Both stay editable.
3The original message, kept verbatim.
As Nov 1 nears, Maya gets a reminder.At most two a week per person, never at night.
DecisionsVantia
PendingOne-way door
1
Outsource customer support
Move customer support to Northfield from Nov 1, with Maya Chen owning the switch.
2
Owner
Maya Chen
Due
Nov 1
Decided
Oct 1
Source
Email
3
Original message
“Agreed. From Nov 1 we outsource customer support to Northfield. Maya owns the switch.”
Tom Reyes · via Email · kept verbatim
Thu, Dec 3 · 9:00 AM
It asks how it turned out.
Two weeks after it’s due, Decize asks Maya how it turned out. She taps Regret, adds a note, then saves. No login.
Four answers: Went well, Mixed, Regret, Didn’t matter.
A one-line lesson, drafted for you to edit, stays on the record.
In her inbox
Decize
To: Maya Chen
How did “Outsource customer support” turn out?
How did it turn out?
You decided Outsource customer support a little while back. Tap how it went.
Went wellMixedRegretDidn’t matter
Then a page, no login
Outsource customer support
How did it turn out?
Regret
What happened?
Complaints doubled.
Save
On the record
LessonEdit
Try it small before going all in.
Tue, Jan 12 · 2:14 PM
It answers next time.
Yes.
Three months later, Leo asks. Decize replies to him in the same thread with what was decided, how it went, and the lesson.
Nothing on record? It says so.
Outsourcing support again?
LP
Leo Park
To: Tom Reyes · Cc: vantia+k7q2m8xd@in.decize.app
Didn’t we try this last year?
Decize
To: Leo Park
Yes — your team already decided this
You asked: did we outsource support before?
On Oct 1 the team decided to outsource customer support. It was marked Regret. The lesson recorded then: try it small before going all in.
What’s on record
Outsource customer supportDecided Oct 1 · outcome: Regret
Open your workspace
Every team has its own “didn’t we try this?”
Cc it even with a client, supplier or board member on the thread. Decize replies only to people on your roster.
Project architect · Cc: Decize
Didn’t we approve this substitute last time?
Substitutions and client changes get agreed in threads with contractors.
Decize
Re: Storefront substitution
Yes — your team already decided this
On Mar 4 the team decided to approve the window substitute. It was marked Went well. The lesson recorded then: ask for test data with every substitute.
What’s on record
Approve the window substituteDecided Mar 4 · outcome: Went well
Purchasing lead · Cc: Decize
Didn’t we drop this supplier once already?
Supplier swaps, surcharges and customer exceptions get settled with vendors and buyers.
Decize
Re: Resin supplier
Yes — your team already decided this
On Jun 9 the team decided to drop the backup resin supplier. It was marked Mixed. The lesson recorded then: line up a second source before dropping one.
What’s on record
Drop the backup resin supplierDecided Jun 9 · outcome: Mixed
Engagement partner · Cc: Decize
Didn’t we discount them last year?
Scope changes and pricing get agreed in email with client sponsors.
Decize
Re: Renewal pricing
Yes — your team already decided this
On Nov 3 the team decided to discount the client’s renewal. It was marked Regret. The lesson recorded then: tie every discount to a longer term.
What’s on record
Discount the client’s renewalDecided Nov 3 · outcome: Regret
Development director · Cc: Decize
Didn’t we try a spring gala already?
Program and funder calls run through email with the board.
Decize
Re: Spring fundraiser
Yes — your team already decided this
On Apr 18 the team decided to hold a spring donor gala. It was marked Didn’t matter. The lesson recorded then: put gala effort into direct donor asks.
What’s on record
Hold a spring donor galaDecided Apr 18 · outcome: Didn’t matter
Dispatch lead · Cc: Decize
Didn’t we ban this carrier already?
Carrier bans follow a claims thread; shipper terms get set in email.
Decize
Re: Carrier status
Yes — your team already decided this
On Aug 22 the team decided to ban the late‑pickup carrier. It was marked Went well. The lesson recorded then: log the claim number with every ban.
What’s on record
Ban the late‑pickup carrierDecided Aug 22 · outcome: Went well
Illustrative examples.
Every Monday
A read on the system, not on your people.
Workspace owners and managers get one email: what needs attention, how many loops closed, how many decisions have an owner.
A decision log is a running record of the calls a team has made: what was decided, when, by whom, why that option won, and what was expected to happen. A useful one is revisited when the result is known, so it records the outcome and the lesson, not just the choice.
What is Decize?
Decize is a decision log for teams that decide over email. Cc it on the thread where a call is made and it records what was decided and who owns it, asks the owner how it turned out a couple of weeks after it’s due, and answers the next time someone asks.
Do we need to install anything?
No. Anyone on your roster can Cc or forward an email to your workspace’s capture address.
What if an email doesn’t decide anything?
No record is made. Decize logs only decisions someone actually made; the email stays with its thread as context.
What if the thread keeps going?
If a later reply that keeps Decize on Cc changes the call, such as a new date, a reversal or “done”, Decize updates that same record.
What happens when we hit our monthly limit?
New captures are refused until the 1st, or until you move up a plan. Nothing already recorded is touched.