AUTOMATE WITH
THE RIGHT MIX.

For MSPs and IT teams: your team doesn't need a developer to automate. It needs the right mix of people. Find out who covers what across the 8 Archetypes of Automation, and where the gaps are.

Start the assessment Explore the framework

About 10 minutes. Score yourself on 8 archetypes, then overlay your team.

Example team radar chart Two team members overlaid across the 8 archetypes. Both score 9 in Building and zero in Quality, leaving Quality as the team's gap. Process Problem Design Comms Building Quality Human Strategy
Two 9s in Building, zero in Quality.
That's a risk profile.

ARCHETYPES OF AUTOMATION

The biggest barrier to automation isn't technical skill. It's process thinking, team composition, and role awareness. Like a sports roster, no one person covers every position. Everyone scores themselves, you overlay the results, and the lowest combined score is where to invest next.

Process & Knowledge Holding
Understanding, retaining, and communicating how work actually happens.
Problem Definition
Identifying, articulating, and prioritizing what is worth automating.
Design & Logic Thinking
Translating real-world processes into explicit logic before touching any tool.
Communication & Translation
Bridging the gap between process owners and builders.
Building & Implementation
Constructing automations using tools, AI, or both.
Quality & Oversight
Verifying automations work correctly, including failure scenarios.
Human & Organizational Awareness
Managing adoption, resistance, ownership, and compliance.
Strategic & Vision Thinking
Connecting automation work to measurable business outcomes.
Example team readout
COMBINED TEAM SCORE
  • Process9/20
  • Problem9/20
  • Design13/20
  • Comms7/20
  • Building18/20
  • Quality0/20
  • Human6/20
  • Strategy8/20
Quality is the gap. The lowest combined score is your most urgent investment in hiring, training, or partnerships. Same example team as the chart above.

Research-backed: built on Theory of Constraints, Lean, Design Thinking, Kotter's Change Model, Team Topologies, and more. See every sub-archetype and source →

WHERE YOU'VE SEEN ME

BUILD, ADVISE, TEACH

Brian Simpson
Brian Simpson · The Rhino Automator

Not a dev shop. Not a vendor. A practitioner who builds automation and teaches others to take part, whatever their technical background.

AUTOMATION

Real workflows that solve real problems. Rewst, Power Automate, and whatever gets the job done, focused on MSP and IT operations.

Read the guides →

CONSULTING

Helping teams decide what to automate, who should be involved, and how to build a practice that doesn't depend on a single developer.

Email me about consulting → brian@rhinoautomator.com

COMMUNITY & EDUCATION

Conference talks, workshops, and community content on building automation muscle and making non-technical people meaningful contributors.

See talks and demos →

WHERE DOES YOUR TEAM STAND?

Same team as the top of the page, plus one person who is strong in Quality. The gap fills in.

Example team radar chart with a third person added The same two team members as the first chart, plus a third who scores 9 in Quality, which fills the gap on that axis. Process Problem Design Comms Building Quality Human Strategy
  • Person 1
  • Person 2
  • Person 3, strong in Quality
Example data. Your chart is built from your team's own scores.
Start the assessment

The self-assessment takes about 10 minutes. Have everyone take it, then overlay the results to see your team's coverage.