Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Ideas are almost never lacking. What’s missing is the conditions to understand which ones deserve time, attention, and responsibility. A good insight can come during a conversation, from a problem encountered many times, or from the desire to simplify something that is currently confusing. Its value, however, doesn’t depend solely on originality. It depends on the ability to address a real need, find a sustainable form, and produce a recognizable effect.
Before transforming an idea into a project, it’s a good idea to slow down enough to ask five questions. They don’t dampen enthusiasm. They help distinguish a promising intuition from a commitment that risks growing aimlessly. The answers don’t have to be perfect. They must be clear enough to choose the first step.
1. What concrete problem does it make easier?
An idea takes shape when it manages to name a problem. Not a huge, indistinct problem, but a difficulty that someone recognises in their own experience. It could be confusion in the face of too much information, the difficulty of choosing a tool, the lack of a simple process, or the need for a clearer explanation. Without this connection, even an elegant project risks demanding attention without providing usefulness.
The question doesn’t require looking for flaws in people. It requires listening to where the process gets blocked. What questions come up often? What steps are put off? Where do people use temporary solutions because they can’t find a more reliable one? The answers gathered in real conversations are more valuable than many hypotheses formulated alone.
It’s helpful to describe the problem in everyday terms. If we can’t explain it without vague terms, perhaps we haven’t yet understood it well enough. A person should be able to say, “Yes, this happens to me too,” or “I understand why this would be useful to me.” This recognition is the starting point for any proposal that aims to create value and not just attract attention.
A good way to avoid confusing the problem with the solution is to formulate the sentence without naming what we’re trying to sell or achieve. For example: “People waste time because they don’t know what information to check before making a decision,” not “we need a new guide.” A guide might be an adequate answer, but it might not be the only one. Keeping the problem and the solution separate allows us to imagine better formats and listen with less need for confirmation.
This distinction also avoids another trap: building a proposal to demonstrate a skill rather than to be useful. Skills are important, but they must serve the person receiving the project. When we start with the problem, language tends to become clearer, the format more essential, and the evaluation less dependent on novelty.
2. Who would benefit, and at what moment?
Not everyone has the same need at the same time. Content may be useful to someone just starting out, but redundant for someone with more experience. A tool can be invaluable during a phase of change but irrelevant when everything is stable. Defining the recipient doesn’t mean rigidly excluding. It means avoiding speaking to everyone in such a generic way that no one is helped.
The question of timing is equally important. A guide to choosing a service can be useful before purchasing. A strategic comparison can be useful when a project is growing. A resource to organize can be useful after a period of confusion. When we understand the context, it becomes easier to choose format, language, and channel. We don’t need to invent urgency: we need to respect the time when the person is truly ready to use what we’re proposing.
To test the hypothesis, you don’t need large numbers. You can listen to five people from the imagined audience, observe the requests received, or look at the questions in the comments and conversations. The goal isn’t to gain approval. It’s to find words, obstacles, and expectations that make the idea more realistic.
Listening doesn’t mean copying every request. People can describe their discomfort well and still not know the most useful response. The person proposing a project has the task of connecting the gathered voices to a broader perspective. Listening provides concrete material; vision helps choose which response makes sense to build and which promise can be kept.
3. What must be true for it to work?
Every idea carries with it certain conditions. It requires skills, time, tools, collaboration, a certain continuity, or a way to be found. Ignoring these conditions doesn’t make the project more agile. It makes it more fragile. An honest question is: what resource is missing today, and how can I assess its importance without building everything first?
This is where the first experiment comes in. Instead of launching a complete proposal, you can create a limited version: a short guide, a meeting, a basic page, a prototype, a series of conversations. The test should be serious enough to generate feedback and small enough to be correctable. This way, the idea isn’t defended on principle. It’s tested with respect for the time of both the proposer and the recipient.
The fourth question is: What effect would I like to observe? It won’t always be an immediate sale or a number. It could be a more qualified request, a useful conversation, a step that people complete with less difficulty, a new question that shows genuine interest. Choosing a signal avoids changing your mind about the project every time your mood changes during the week.
The fifth question is about the limit: what don’t I want to sacrifice to make this idea work? It could be the quality of the relationship with clients, the time dedicated to research, transparency in how the project is supported, health, or the ability to keep commitments already made. Setting a limit isn’t pessimism. It’s what allows an idea to grow without becoming a hidden cost.
After the initial test, the choice isn’t simply between success and abandonment. You can continue, modify, suspend, or close. These are four different outcomes, all useful if accompanied by an honest reading. Continuing means that the hypothesis deserves more resources. Modifying means that the need exists but the response needs improvement. Suspending means that essential conditions are now missing. Closing means freeing up attention for a more suitable idea. Giving dignity to each outcome makes it easier to experiment without over-promising.
This approach allows you to discuss the project clearly, even to those who might be interested. It shouldn’t be presented as a definitive solution. It’s more credible to explain what problem you’re exploring, who it’s designed for, what limitations it currently has, and what changes you intend to observe. Transparency doesn’t diminish an idea’s appeal. It makes it more reliable, because it avoids asking for trust before sufficient evidence has been gathered.
We asked Alessandro Garau, CEO of Vision to Value: “Value is not created by making a choice look inevitable. It is created by showing the criterion behind it, the responsibility it requires and the change it can realistically produce.” This perspective keeps vision connected to decisions rather than slogans.
For more information about Alessandro Garau and the perspectives developed by Vision to Value, explore the project pages and the articles devoted to vision, coaching, leadership and strategic marketing.
Subscribe to the Vision to Value Letter to receive new articles and a considered selection of tools, ideas and books for turning direction into practical choices.
