Collaboration & Suggestions

Major decisions are rarely made in a vacuum. Axiom is built for multi-threaded, asynchronous collaboration, allowing stakeholders across different time zones to debate, suggest, and align without needing another synchronous alignment meeting.

The Problem with "Edit" Access

In typical spreadsheets, if someone disagrees with a score, they just overwrite it. This leads to version control nightmares and destroyed trust.

In Axiom, direct mutation is restricted by DACI Roles. If you are a Contributor, you cannot unilaterally change a score. Instead, you use the Suggestions Workflow.

Submitting a Score Suggestion

When you disagree with how an option is evaluated (e.g., Engineering rates a vendor's API a 3, but you've tested it and believe it's a 5), you submit a suggestion.

  1. Open the specific option's hub by clicking its drill-down arrow in the project matrix.
  2. Navigate to the Suggestions tab.
  3. Click + Suggestion.
  4. Select the specific scoring criterion you want to challenge.
  5. Enter your suggested score and, crucially, write your rationale in the comment box. (e.g., "Their new v2 API released last week resolves the latency issues. Upgrading this to a 5.")
  6. Submit. This is now queued for review.

Approving a Suggestion (For Drivers & Approvers)

Suggestions remain pending until a user with administrative authority (Driver or Approver) ratifies them.

  1. As a project owner, you'll see active suggestions flagged in the option's hub.
  2. Review the peer's rationale. You can reply in the thread if further clarification is needed.
  3. If you agree, click Approve.
  4. The matrix's main score is instantly updated to the suggested value, and the weighted totals for the project recalculate automatically.

The Activity Log: Your Audit Trail

Every single action in an Axiom project is immutably recorded in the Activity Log.

This isn't just for debugging; it's a compliance and accountability feature. The Activity Log tracks:

  • State Changes: When a criterion is added, removed, or has its weight modified.
  • Score Mutations: Exactly who changed a score and when.
  • Suggestion Approvals: Who proposed a score change, and which Approver ratified it.
  • Phase Shifts: When the project moved from Draft to Evaluate to Decision.

When your executive team asks why a specific vendor was chosen six months down the line, you don't need to dig through Slack archives. You just link them to the Activity Log.

PreviousOptionsNext Consensus Engine