Decisions and action items

Wisper and your teams don’t guess at things only you can decide. They also don’t stop and wait on you for things they can decide themselves. The line between the two is the Decision.

Decisions

A Decision is one question that only you can answer, written so you can answer it in a few seconds:

• The question, in one line.
• Why it matters: what changes depending on your answer.
• A recommendation: what Wisper or the team would do.

They show on the Overview in the Decisions card, newest work first, and on your phone if you’ve connected it.

Answering one

Answer on the card, in your own words. “Go with the recommendation” is a perfectly good answer. Your reply goes back to whoever asked, and the work carries on.

You can also just talk to Wisper about it (“what happens if I say no to the pricing question?”); she knows which decision you mean.

Answered decisions leave the Overview and are kept on the Activity screen, with what you said, so you can always look back at what was decided and why.

What makes a good Decision

If you’re building teams or agents for WispOS, these are the rules Wisper’s own decisions follow:

• One question per card. Two questions are two cards.
• Answerable without opening anything. The card carries what you need.
• Always a recommendation. A question with no recommendation is homework.
• Never for something the request already settled. Your request is the go-ahead; a Decision is for what it didn’t cover.

Action items

Decisions are questions; action items are things that are yours to do: sign a form, reply to someone, plug in the drive. They’re a simple checklist on the Overview. Tick one when it’s done. Wisper adds them when work needs your hands, and you can ask her to add your own (“add ‘call the accountant’ to my list”).

Ticked items move to the Activity screen’s record.