Free, practical, and built on the 5 Spheres. Use them on your own, with your team, or alongside the cohort. More are added here over time.
Prompt chain
From customer understanding to a brief you can build from
A guided sequence you run with Optomize, the AI coach built on this method. It takes you from a real empathy map of your customer, through their resistance, to a brief sharp enough to hand your team. Work through the steps in order.
Before you start
The quality of your brief depends entirely on the honesty of your empathy map. If you defend your assumptions in Step 1 rather than challenge them, the brief at the end will reflect that. Optomize will push back when something does not add up. Let it.
One chain, three outputs. Tweak the final step and the same sequence produces a campaign brief, a product pipeline brief, or an MVP build brief, depending on what you are making.
Paste this to start. Replace the bracketed part with your website URL, or a short paragraph about what you do if your site is not live yet.
"I want to build an empathy map for my target customer. Here is my company: [paste your website URL, or a short paragraph about what you do if your site is not live yet]. Please map what my target customer is feeling, thinking, doing and hearing. Then add what they are hoping to gain and what they hate losing. Finally, surface what they are likely not saying out loud, and what companies serving them are not saying to them either. Use the Unsaid, Unspoken Advantage and the 5 Spheres of Empathy for this chat."
Read the output, then respond with:
What surprised you
What you disagree with or think is wrong
What is missing
Let Optomize refine the map on your feedback before moving on.
Step 2 — Find your early adopter
Once the empathy map feels accurate, say:
"Based on this empathy map, help me identify my early adopter. Using the Diffusion of Innovation framework, which adopter profile does my customer most closely resemble? What makes them ready to use an imperfect solution right now?"
Push back if the profile does not feel right. Ask Optomize to adjust until the early adopter feels like a real person you have actually met, or could meet.
Step 3 — RAID analysis
Once you have your early adopter, say:
"Now run a RAID analysis on my plan to serve this early adopter. What are the Risks, Assumptions, Issues and Dependencies I need to be aware of before I build anything?"
Pay particular attention to the Assumptions. These are the beliefs that, if wrong, mean you are building the wrong thing. Mark the two or three that feel most exposed.
Step 4 — Resistance messaging and accusation audit
Once you have the RAID, say:
"Based on the RAID analysis, what resistance will my early adopter have to adopting my solution? Run an accusation audit: what are the negative things they are likely saying, thinking or feeling about a solution like mine before they have even tried it? Then help me turn those into a resistance messaging strategy. What are the messages that directly address those objections and earn trust before I ask for anything?"
This produces two things: the honest list of what your early adopter thinks about you before they know you, and the messaging that meets them there.
Step 5 — The brief
Once you have the resistance messaging, say:
"Based on everything we have discussed, what should be in my MVP or product development brief? What are the one or two features, experiences or messages most likely to overcome the resistance we identified and win with my early adopter? Please frame this as a brief I can take to my team or use to start building."
This is your output. The brief should answer who it is for specifically, what problem it solves in their words, what the first feature or experience is and why, and what success looks like for the early adopter in the first 30 days. Swap "MVP or product development brief" for "campaign brief" or "product pipeline brief" to point the same chain at a different outcome.
The point
A brief built this way is grounded in your customer's real resistance, not your hopes. That is the difference between something you build and something they actually adopt.
More tools
Added here over time
The Sphere 1 Self-Audit
A guided look at how you actually decide. Twenty minutes, or go further and trace a real decision through all five spheres.