Name each action logic’s strength before its limit

When you see a colleague’s action logic, start with what it does well, so the map informs collaboration instead of ranking people.

Why it works

A developmental sequence invites people to treat later as better and earlier as lesser. Rooke and Torbert’s own table assigns a distinct strength to each logic — the Opportunist is good in emergencies, the Diplomat is supportive glue in an office, the Expert a strong individual contributor, the Achiever well suited to managerial roles. Naming the strength first keeps attention on fit between person and task, and guards against the contempt that ranking breeds.

How to do it

  1. Think of a colleague whose way of working frustrates you.
  2. Write which description they seem closest to — as your guess, not a diagnosis — and the strength that description carries.
  3. Write one situation where that strength is exactly what the team needs.
  4. Only then name the limit, and ask what support or partnership would cover it.

Evidence

The "strengths" column of the table Starr and Torbert (2005) adapted from Rooke and Torbert’s HBR article lists a strength for every action logic. The practice of leading with strengths is an application; it has not been studied as an intervention. (anecdotal)

Guessing another person’s action logic from outside is even less reliable than guessing your own. Keep it private and provisional, and never use it in hiring, promotion, or performance decisions.

Sources

Common mistake

Using action-logic labels as put-downs ("he’s such an Expert"). The moment the map becomes a ranking, it stops helping you work with anyone.

Practice this with IX Coach

Start with IX Coach

More practices for Torbert’s Seven Action Logics of Leadership

Related concepts

Free to reuse under CC BY 4.0: cite or embed this practice · more practices graded Practitioner experience