How a well-executed impact project works, from idea to verification?

Start from the problem, not the solution

A serious project does not begin with «let's install solar panels»: it begins with a client's problem and a measurable objective declared before the work starts — what we call the ex-ante target. The target is not a marketing promise: it is a number with its unit and its source, which at the end of the project will be compared against reality. Declaring it upfront changes everything: it forces you to truly understand the problem, to choose a defensible approach, and to accept being measured.

Phase 1 · Ideation

Understanding the problem better than the way it was described to you: reading the data, listening to those who live the situation firsthand, exploring multiple ideas and choosing one with a rationale that would hold up in front of the client. This is the phase where judgment matters more than tools: AI can help you explore alternatives, but the choice and its defense remain yours.

Phase 2 · Design

Turning the idea into a plan: activities, timelines, responsibilities, and above all the measurement plan — which indicators, with what method, with what evidence. A project without a measurement plan is a promise; with a measurement plan it becomes a verifiable commitment. This is also where the team is defined: complementary roles, each with its own declared function.

Phase 3 · Implementation

The field: you build, you coordinate, you face the unexpected that no plan anticipates. This is the phase of concrete deliverables and decisions made under constraints, where the difference between knowing and knowing how to do becomes clear. On Simbial, every contribution to implementation is tracked: what you do becomes part of your verifiable story.

Phase 4 · Measurement

The moment of truth: the result is compared with the target declared at the outset, honestly even when the numbers fall short of expectations. Indicators are recorded with their verification level; if an independent Impact Controller validates the data, confidence increases. The project enters the register and generates Impact Score for both the team and the company.

The team: complementary roles, one goal

In Simbial projects, Makers (those who create the impact, each with their own Impact Role) and Impact Controllers (those who safeguard the truth of the data, independent from the delivering team) work together. This separation is not bureaucracy: it follows the same logic by which the person who writes a financial statement is not the one who certifies it. The trust of others comes from how the process is built, not from declarations.

Where you truly learn it

This method is not learned by reading: it is learned by doing. The learning path of every Impact Role includes a simulated project — the same 4 phases, with Gea teaching within the work itself — in a protected environment where making mistakes costs nothing and teaches a great deal. Then comes the assessment, and finally the real field.

Net Positive Impact Score →