AI Usage Style Test: What the 7 Factors Actually Measure

Most people hear "AI test" and picture a score. Seventy-two out of a hundred, intermediate, a little behind the colleague who won't stop talking about prompts. A score like that assumes everyone is on the same road at different mile markers, and that the only question is how far you still have to drive.

Spend a week watching how the people around you actually work with AI. The single scale falls apart. One colleague invents uses nobody asked for and documents none of them. Another never opens a chatbot but catches every fabricated citation that crosses her desk. A third has quietly wired three tools together and told no one. Those three are not at different points on the same skill. They lean in different directions. Slack's Workforce Lab sketched five AI personas along similar lines.

RELACTIS measures seven factors instead of one number: Creation, Crossover, Autonomy, Advocacy, Systemization, Verification, and Engagement. None of them is a grade. Each one is a dial, and a team needs people at both ends.

Creation: invent or refine?

Creation measures your itch to try unproven uses. If you score high, you ask "could it be used like this?" before anyone asks you to. You point features at problems the manual never mentions, and you treat failed experiments as tuition. Creation is the raw material of every genuinely new workflow and the signature of The Pioneer.

Low Creation is a different appetite. You would rather run proven plays well than gamble on speculative ones, and someone has to. High-Creation people produce prototypes. Low-Creation people are the reason anything ever reaches a dependable version. Every team that ships runs both ends of this dial, whether or not anyone planned it that way.

Crossover: connect or go deep?

Crossover measures breadth: pulling an idea from one domain into another, chaining tools nobody thought to combine, finding value in the gaps between products. High scorers collect parts, and their favorite question is "what if we connect these?" The Remixer runs on that restless energy.

The low end of Crossover is depth. Depth is what sets a team's quality ceiling, and it is the pattern behind The Artisan, who pushes one tool and one purpose further than anyone around. Wide-and-shallow discovers what's possible; narrow-and-deep makes it excellent. Neither can do the other's job.

Autonomy: self-serve or guided?

Autonomy measures how you prefer to get from "never touched it" to "using it daily." High scorers read the docs, poke at settings, and figure things out alone. That quiet self-drive belongs to The Self-Learner, who has usually adopted a new feature before the training session about it gets scheduled.

Scoring low means you learn best through people. You want to be shown once, and after that you will run it correctly forever. Better still, you would rather find the person who already knows. Faithful reproduction is badly underrated. It is why training works at all, and knowing who to ask is a real way to get results. The self-taught often can't explain how they learned anything, which is its own limitation.

Advocacy: broadcast or keep it quiet?

Advocacy measures whether your discoveries leave your desk. High scorers translate: "for your work, here's how you'd use it." They recommend the right tool for someone else's problem, and they treat a private win as unfinished until at least one other person has it too.

Low Advocacy is private practice. Deep skill is mostly built in silence, and not every experiment needs an audience. The two ends cover each other's blind spots: loud without practice is noise, and skilled without sharing is invisible. You may already know the best AI user on your team as the person nobody ever hears from. Low Advocacy looks exactly like that.

Systemization: improvise or templatize?

Systemization measures the urge to turn a one-off win into something repeatable: a template, a checklist, a workflow that produces the same result no matter who runs it. High scorers say "already made it a template" and mean it. The Systemizer runs on that converter instinct, which is one of the rarest behaviors in any organization. That rarity is why unshared inventions keep evaporating when their inventors change jobs.

Low scorers improvise. Every task gets a fresh approach, tuned to today's specifics. Every system eventually meets the case it wasn't designed for, and the person who never needed the template is the one who isn't stuck.

Verification: check or trust?

Verification measures your reflex to ask "what's the source for this?" High scorers read AI output the way an editor reads a first draft: useful, promising, and not yet true. Generating plausible text keeps getting cheaper, so this checking instinct keeps gaining value. It is the core of The Verifier.

Low Verification is momentum. Low scorers work with drafts, keep the speed up, and accept that a fast 80% often beats a slow 100%. If everyone verified everything, nothing would ship on time. If nobody verified anything, errors would ship instead. A team needs the tension between the two ends of this dial, not a winner.

Engagement: how close do you actually stand?

Engagement is the plainest of the seven: how much of your working life does AI touch? High scorers have it wired into daily routines and notice within hours when a model starts behaving differently. Low scorers keep their distance. Engagement is where "a low score is fine too" surprises people most.

Distance carries information. Sometimes low Engagement is a first step that hasn't happened yet. The Quiet Abstainer says "looks useful" and leaves it there. That group is often the largest silent one in a workplace. Sometimes low Engagement is deliberate skepticism that spots what enthusiasts have stopped seeing. Watching before moving is a position. A test that treats non-users as zeros learns nothing from the people it most needs to understand.

Seven dials, fifteen shapes

There is no way to max out all seven, because there is no total. The seven values come out of separate questions, and adding them together produces a number that means nothing. What you get instead is a shape.

The assessment reads your strongest signals across the seven factors, and their combination maps to one of the 15 AI usage types. High Creation with low Systemization points toward The Pioneer, whose inventions outrun his documentation. High Systemization points toward The Systemizer, who turns other people's inventions into assets. High Verification with low Engagement lands near The Critic, whose eye for flaws is real. You also get the full seven-factor radar alongside your type, because the type is a headline and not the whole story.

A usage style test names the direction you already lean. Once the direction has a name, you can stop treating it as a gap to apologize for and start using it on purpose.