“Our audience is 25 to 55, with medium to high incomes.” That may help with some analysis. It does not explain why someone buys now, what they compare or why they walk away.
Two people in the same demographic category may have completely different needs. One seeks an urgent solution; another documents a project for next year. A strategy that treats them identically can miss the difference that matters to the decision.
Before we choose messages and platforms, we clarify what we know about the situations in which the offer becomes relevant.
What the business tells us and what customers tell us
The team knows the product, costs, constraints and many recurring questions. Customers can explain the circumstances in which they searched, the alternatives they considered and the difficulties they ran into. Usage and sales data show other parts of the journey.
No source gives the whole picture. The team may remember difficult cases most vividly. A customer may reconstruct their reasons after the event. A report may show a page exit without explaining why.
That is why we compare information instead of picking the first explanation we like. The SBA distinguishes research from existing sources from direct research and recommends examining demand, alternatives and market conditions. The method and scope must be tailored to the business. SBA: market research and competitive analysis
Useful questions are tied to a decision
If we want to find out why a service receives few relevant inquiries, the question is not only whether people like the design. We need to check who arrives, what they understand and whether the offer meets their needs.
| Decision to prepare | Information required | Possible sources |
|---|---|---|
| Which segment to prioritize | Needs, potential and capacity to serve | Sales, interviews, commercial data |
| What to explain on the page | Questions and misunderstandings | Support, conversations, usage tests |
| Which difference to emphasize | Alternatives and choice criteria | Customers won and opportunities lost |
| What to test first | High-impact uncertainty | Comparative data, constraints and assumptions |
The table does not require every method in every project. It helps choose research that can change an important decision.
Ask what actually happened.
Imagine an office-services provider that assumes price is the main obstacle. It asks customers, “Would you buy if we were cheaper?” Positive answers appear to confirm the hypothesis.
But the question already suggests the explanation. A conversation about their most recent decision can bring a different kind of information: when the problem arose, who looked for a solution, which alternatives were evaluated and what needed internal approval.
We may find that the response time was unclear or that the offer was hard to compare. These are directions to check, not conclusions guaranteed after a single discussion. A statement about future intent is not the same as an order.
Understand the decision before interpreting it.
Example: a supplier assumes that the price explains the delay.
SITUATION
What problem arose and why at that time?
ALTERNATIVES
Which options were considered?
Decision
What needed to be checked or approved before the decision?
Fictional example, not NOT MORE. results or forecasts.
Who is missing from the conversation?
If we listen only to satisfied customers, we can miss the reasons why others have given up. If we analyze only the leads received, we miss the people who did not understand the offer well enough to contact us.
Research may include new customers, repeat customers, lost opportunities and people using an alternative, within the available access and appropriate contact conditions. A small group drawn from existing relationships should not be presented as representative of the whole market.
We also separate the buyer from the user when roles differ. In one company, one person may approve the cost, another may manage implementation and another may use the product daily. One perspective does not describe the whole process.
From observation to hypothesis
“Three people asked who prepares the assets” is an observation. “Unclear team responsibilities may delay the decision” is a hypothesis. “We will explain the roles and watch whether the question recurs and opportunities progress” is a direction for testing.
These levels are worth keeping separate in documents. Otherwise, a provisional interpretation can harden into a truth repeated in every presentation.
An observation is not yet a conclusion.
An example of moving from conversations to something to check.
OBSERVATION
Three people asked who was preparing the materials.
HYPOTHESIS
Unclear team involvement may be delaying the decision.
VERIFICATION
Clarify the roles, then track follow-up questions and progress in the sales process.
Fictional example, not NOT MORE. results or forecasts.
A conclusion that changes the budget or positioning needs stronger evidence than a small wording change. Match the depth of investigation to the cost of being wrong and how easily the decision can be reversed.
Research should help a decision, not postpone it indefinitely
A project can start with imperfect data. What matters is knowing what we are assuming and building a stage that can provide the missing information.
If the cost of serving a segment is unknown, clarify it before a major expansion. If the question concerns a clearer page explanation, a focused test may be enough. Not every editorial choice requires a comprehensive study.
Agree on what is enough to decide, who makes the decision and when the hypothesis will be reviewed. Without that boundary, research can produce interesting documents and very few choices.
What AI can and can’t do here
An AI tool can help organize observations or suggest questions, provided the information is processed under appropriate conditions. The summary should be verified against the source and confidential data treated according to the rules of the project.
An AI-generated persona does not replace research with people. It can be a clearly labeled hypothetical scenario. Attributing needs or quotes to it as though an interview took place would build the strategy on evidence that does not exist.
How we work at NOT MORE.
We start with questions that can change the direction: whom is the offer for, what alternative does it replace, what needs demonstrating and what can the business deliver? Those questions determine the sources and depth of research.
The useful output goes beyond an audience description. It connects what we learned with decisions about communication, promotion and implementation. That is where the strategic work becomes visible.
Research should help build the next stage
The questions may also concern the offer, business model, inquiry handling or delivery capacity. We speak with the people who know those activities and separate observations from assumptions. At NOT MORE., analysis should lead to choices and work that can be delivered with the available resources.
A Growth Diagnostic is a format for situations where we need to clarify where to focus. It examines the relevant components and data and includes conversations with the people closest to them. The result is a 90-Day Growth Map: findings, priorities, proposed owners and a way to evaluate progress. The map organizes a working horizon; it does not guarantee a commercial result within a fixed period.
If the need is already well defined, you can commission the service or project directly. Initial clarification is still necessary to understand requirements, but it does not automatically require a separate paid diagnostic. We can then develop the creative direction, produce materials, build the technical solution and implement the agreed components. Monitoring and reporting follow the scope of the collaboration.
What information is useful before the first strategy conversation?
The objective, the current situation, the offer, the available resources and concrete examples of the problem are useful. You can bring the existing strategy, materials, reports and the team’s observations. A missing document does not stop the conversation from starting; together, we establish what information the next decision needs.
A few real situations help frame the questions: what a potential customer asked, where an inquiry got stuck or why an offer was turned down. We remove personal data the analysis does not need and keep the relevant context.
Do we have to research everything before any execution? No. If the objective and requirements of a component are clear enough, we can define the implementation directly. Further investigation is justified by information that could change the decision, the cost or the risk of the project. At the end of the clarification, we should know what we can start and which dependencies remain.
You do not have to prepare every answer yourself
You can arrive with incomplete information and a problem you cannot yet name precisely. We organize the questions and identify documents or conversations that could change the decision. Missing data is recorded as a limitation, and assumptions remain visible. Before a separate research stage, we explain what we will investigate, what you will receive and how much involvement your team will need. Clarification should make the start of the collaboration easier to understand.
Clarification may be the contribution you need
You may want advice on one decision or a strategy that your team and existing partners will implement. We can limit the collaboration to that contribution. We agree on the questions, analysis, format of recommendations and information needed by those continuing the work.
If the direction is already defined, we can take on only the agreed execution. We use existing research and documentation and clarify what is missing for delivery. An additional question helps make the work deliverable; it does not automatically turn the assignment into another strategy stage.