CTA Matrix

UX & Product Architecture • Design Systems & Engineering

A CTA Matrix, or call-to-action matrix, is an ORCA grid that maps user roles to object types and records the actions each role needs to take on each object. It gives teams a starting point for defining permissions, conditions, and interaction requirements before placing controls on screens.

What goes in a CTA Matrix?

Put roles down the rows and object types across the columns. Write actions as verbs in the cells. A role can describe a person’s relationship to the object, such as the agent assigned to a trip, when that relationship affects what they can do.

Start with what each role needs to do. Review access and business rules before treating a proposed action as an approved requirement. A verb such as “Request cancellation” can become a button, menu item, or part of a guided workflow once the team designs the interaction.

CTA Matrix example for travel operations

Consider a tool where an assigned agent manages the trip and a support reviewer investigates issues without changing records. This example focuses on a few actions from each role.

Role Trip Booking Traveler
Assigned agent View trip, add booking View booking, request cancellation if eligible View traveler, update contact details if permitted
Support reviewer View trip View booking View permitted traveler details

Turn “Request cancellation” into a user story. An assigned agent needs to request cancellation on an eligible confirmed booking when a traveler changes plans. When the request succeeds, show Cancellation pending so the agent knows the supplier still has to respond. The supplier’s response determines the next state.

How do you turn matrix entries into requirements?

  1. Clarify who can act. Check role, assignment, and record access separately where they affect the action.
  2. Describe when the action is available. Record the booking state and eligibility rules. Mark unresolved rules for follow-up.
  3. Specify the result and feedback. Include what the user sees after success, a blocked attempt, or a delayed response. Use a state transition matrix to track the lifecycle.
  4. Choose placement in the interface. Give frequent or time-sensitive actions appropriate prominence. Test whether users can find and understand them where the object appears.

In ORCA, teams begin this work during Discovery and expand matrix entries into user stories during Requirements. Use the matrix to agree on who can act. The application enforces those rules when the action is requested.

Sources