Find Your Sweet Spot: The Fun (and Freakishly Accurate) AI Creativity Quiz
Eliott Ardisson
Founder & CEO - Basalt Studio
How your creative working style should shape your AI implementation strategy — a practical guide for founder-led SMBs who want AI that fits how they actually work.
Key Takeaways
- Your natural creative working style — how you gather information, generate ideas, make decisions, and execute — should directly shape which AI workflows you build and what you delegate to them.
- AI works best when it covers your weak spots and accelerates your strengths, not when it tries to replace the judgment that makes you effective.
- There are four broadly recognizable creative working patterns: the Inquirer, the Dreamer, the Explorer, and the Activator. Each has a different AI sweet spot.
- Archetype-matched AI implementation tends to produce faster adoption and fewer post-deployment adjustments than generic automation rollouts.
- The biggest implementation mistakes are over-automating what you’re already good at and under-automating the tasks that actually slow you down.
Why Your Working Style Matters More Than the Tools You Pick
Most AI implementation conversations start in the wrong place. People ask “which tool should I use?” before they’ve answered a more useful question: “what does my creative process actually look like, and where does it break down?”
If you’re a founder running a recruitment agency in London or an accounting practice in Lyon, the right AI workflow for you is not the same as the right AI workflow for a solo developer or a marketing team at a software company. The tools overlap. The configuration — what you automate, what you keep human, how information flows — should be specific to how you work.
This is the idea behind creative archetype mapping. It’s not a personality quiz for its own sake. It’s a practical framework for identifying where automation will give you the most leverage and where it will get in your way.
McKinsey research on AI adoption has consistently found that fit between AI deployment and existing workflows is one of the strongest predictors of long-term adoption. Organizations that take time to understand their operational patterns before implementing tend to see faster uptake and more sustained use. That tracks with what most practitioners observe on the ground.
The Four Creative Working Patterns
These four archetypes are not rigid categories. Most people show strong characteristics of one with meaningful tendencies from a second. Think of them as dominant patterns, not fixed identities.
The Inquirer
Inquirers are thorough researchers. Before they commit to a direction, they want to understand the problem deeply — the context, the precedents, the tradeoffs. They make good decisions, but the decision-making process takes time. The risk is analysis paralysis: so much time spent gathering information that momentum stalls.
Where AI helps most: Automating the front end of the research process. An Inquirer’s real value is in strategic interpretation — connecting dots, drawing conclusions, making judgment calls. If AI can handle first-pass research, competitive scanning, and data synthesis, the Inquirer gets to spend more time doing what they’re actually good at.
What to delegate: Initial market research, document review, competitive monitoring, data aggregation, and structured summarization.
What to keep human: The interpretive layer — what does this data mean, what decision does it support, what are the second-order implications.
Common mistake: Building AI that makes decisions for the Inquirer. That removes the human judgment that makes this archetype valuable in the first place.
The Dreamer
Dreamers excel at vision and concept generation. They see the end state clearly and can articulate possibilities that others miss. The challenge is the gap between vision and execution. Projects get started, ideas accumulate, but the operational detail required to bring things to completion can feel draining or simply get dropped.
Where AI helps most: Execution infrastructure. AI that captures ideas as they emerge, organizes them into actionable frameworks, manages project sequencing, and tracks progress allows the Dreamer to stay in their zone of genius — generating and directing — without losing ideas to operational entropy.
What to delegate: Project management, task sequencing, progress tracking, deadline management, and documentation.
What to keep human: The creative direction, the vision articulation, the judgment about what matters and what doesn’t.
Common mistake: Using AI to generate ideas rather than execute them. Dreamers don’t need AI to brainstorm for them. They need AI to make sure their own ideas actually land.
The Explorer
Explorers are experimenters. They learn by doing, iterate quickly, and are genuinely comfortable with uncertainty. They generate a lot of signal through rapid testing. The challenge is that this process can become hard to systematize — experiments happen, insights emerge, and then get lost because no one documented the pattern.
Where AI helps most: Capturing and systematizing what the Explorer discovers. AI that tracks experiments, identifies which approaches worked and why, and begins to build repeatable frameworks from iterative results gives the Explorer a way to compound their learning rather than start fresh each time.
What to delegate: Documentation, experiment logging, pattern recognition across iterations, and process standardization once something works.
What to keep human: The experimental design, the willingness to try unconventional approaches, the instinct for what’s worth testing next.
Common mistake: Implementing AI that imposes rigid structure on the Explorer’s process. If the system feels constraining, it will get abandoned. The AI should capture and organize discovery, not dictate how discovery happens.
The Activator
Activators are execution-focused. They move fast, make decisions with available information, and maintain momentum. They’re natural project drivers. The risk is moving so quickly that optimization opportunities get missed, quality slips, or alternative approaches never get considered.
Where AI helps most: Quality assurance and optimization analysis that runs alongside execution rather than blocking it. AI that reviews outputs, flags potential issues, and surfaces improvement opportunities without requiring the Activator to slow down their core rhythm.
What to delegate: Quality checks, revision suggestions, performance monitoring, and identification of missed optimization opportunities.
What to keep human: The pace-setting, the prioritization, the bias toward action that makes Activators effective.
Common mistake: Configuring AI that adds friction to the decision loop. If quality-checking AI slows the Activator down, they’ll bypass it. The system needs to enhance speed, not compete with it.
A Practical Self-Assessment
If you’re unsure which pattern fits you best, work through these scenarios. They’re designed to surface authentic behavior rather than aspirational self-image.
Scenario 1: New project kickoff. Do you spend the first few days researching before making any decisions (Inquirer)? Do you start by sketching the end vision (Dreamer)? Do you run a small test to validate assumptions (Explorer)? Or do you define objectives and move straight to planning (Activator)?
Scenario 2: Conflicting information. When data points contradict each other, do you dig into the methodology (Inquirer)? Look for the unifying narrative (Dreamer)? Test both assumptions empirically (Explorer)? Make a call and adjust later (Activator)?
Scenario 3: Energy drain. What exhausts you most — making decisions without enough information (Inquirer)? Managing execution details (Dreamer)? Following rigid processes with no room to experiment (Explorer)? Extended planning phases with no forward movement (Activator)?
Scenario 4: New tool adoption. Do you read documentation before committing (Inquirer)? Imagine how it could transform your workflow (Dreamer)? Run a small pilot project first (Explorer)? Implement it across standard use cases and optimize as you go (Activator)?
If your answers cluster clearly around one pattern, that’s your primary archetype. If they split across two, you’re likely a hybrid — which is common, and which requires a slightly more nuanced AI configuration.
What Archetype-Matched AI Implementation Actually Looks Like
The practical difference between generic AI automation and archetype-aware implementation is where the workflow boundaries sit — what the AI handles, what it surfaces to you, and how it hands things back.
For an Inquirer-led legal firm running a client intake process: the AI handles document triage, initial case research, and structured summaries of relevant precedents. The lawyer reviews synthesized information and makes the strategic calls. The AI never makes a filing recommendation — it accelerates the research that informs one.
For a Dreamer-led marketing agency: the AI captures brief notes from client calls and organizes them into structured project plans. It sends progress updates, flags overdue tasks, and maintains a running record of open creative concepts. The creative director stays in ideation and client relationship mode; the AI keeps the operational layer moving.
For an Explorer-led e-commerce brand running constant product and campaign tests: the AI logs every experiment with inputs, outputs, and contextual variables. It identifies patterns across A/B tests and begins flagging which variables correlate most strongly with positive outcomes. The founder keeps experimenting; the AI makes sure the learning compounds.
For an Activator-led HVAC contracting business: the AI reviews job estimates before they go out, flags pricing inconsistencies, and generates post-job performance summaries. The business owner keeps moving fast; the AI quietly improves the quality of what gets shipped.
In our work helping founder-led SMBs deploy AI agents, the most common failure mode isn’t technical — it’s misalignment between what gets automated and how the founder actually works. An Activator who gets a research-heavy AI system will ignore it. A Dreamer who gets a rigid task-management bot will find it suffocating. The configuration matters as much as the technology.
Common Pitfalls by Archetype
Understanding your archetype also means knowing which implementation mistakes you’re most likely to make.
Inquirers often request AI that accelerates decisions by making them automatically. This removes the analytical judgment that makes the Inquirer valuable. A better configuration gives the Inquirer faster access to more information, not fewer decision points.
Dreamers frequently resist operational automation because it feels mundane. But execution support is exactly where Dreamers lose leverage. The reframe that tends to work: every hour the AI spends on project management is an hour the Dreamer spends on vision and strategy.
Explorers sometimes get handed rigid automation workflows that constrain experimentation in the name of consistency. If the AI feels like a bureaucratic layer, the Explorer will route around it. Build capture and synthesis tools, not guardrails.
Activators can receive AI implementations that introduce approval steps, review cycles, or analysis phases that interrupt their execution rhythm. If quality checking feels like a bottleneck, it won’t be used. The AI needs to work at the Activator’s pace, not slower.
How to Sequence Your Implementation
Regardless of archetype, the implementation sequence matters. A few principles hold across the board.
Start with the highest-friction task. Not the most impressive use case — the one that costs you the most time or energy right now. That’s where automation delivers the fastest, most tangible relief.
Build narrow before broad. A single well-configured AI agent that handles one workflow reliably is more valuable than five agents that each work inconsistently. Get one right, measure the impact, then expand.
Measure what changes. Track decision speed, project completion rates, revision cycles, or whatever metric maps to your archetype’s primary weakness. Without measurement, it’s hard to know whether the implementation is actually working or just adding complexity.
Expect a calibration period. Most AI agent deployments require two to four weeks of adjustment before they run smoothly in a real workflow. That’s not a sign of failure — it’s the normal process of tuning to actual usage patterns rather than theoretical ones.
Putting It Together
Creative archetype mapping isn’t a personality exercise. It’s a diagnostic tool for making better decisions about where to invest your AI implementation effort.
The firms seeing meaningful productivity gains from AI aren’t necessarily using more sophisticated tools than everyone else. They’re using tools that fit how they work — automating the right things, keeping humans in the loop on the right decisions, and avoiding the common mistake of automating their strengths while leaving their weak spots untouched.
Know your archetype. Build to it. Adjust based on what actually changes.
If you want to think through what an archetype-aware AI implementation would look like for your specific business, Basalt Studio offers an AI strategy call with no commitment attached. It’s a practical conversation, not a sales pitch. Book a time here.