Our methodology

Before analyzing the problem, we need to understand the context.

Every project begins with what the organization observes.

It may be a clearly defined need, a problem affecting operations, an opportunity it wants to develop, or even a solution it already has in mind.

Our first task is to listen.

We understand what the organization wants to achieve, who is involved, how it currently operates, what conditions are in place and what expectations surround the project.

We also identify constraints, relevant background and what has already been attempted.

We do not assume the initial explanation is wrong.

But we do not assume it is necessarily complete either.

Understanding allows us to build a sufficiently clear view of the context before we begin diagnosing.

Identify what is truly influencing the situation before deciding what to do.

Once we understand the context, we analyze the conditions that may be affecting the outcome or determining the success of the project.

Depending on the need, we examine processes, operations, people, information, technology, infrastructure, internal knowledge, available capabilities, risks and other relevant variables.

We seek to distinguish between what is being observed and what is actually causing it.

We separate symptoms, causes, opportunities and constraints.

We also review what resources already exist, what can be leveraged and what conditions need to be strengthened before moving forward.

A good diagnosis may confirm the initial idea.

It may also change it.

Changing the scope when the evidence supports it does not mean moving away from the project. It means understanding more clearly what actually needs to be solved.

Turn the diagnosis into a project with clear direction.

Once we understand what needs to be solved, we design the right intervention.

We define what we want to achieve, the scope of the project, which capabilities need to be involved, what resources will be required and how the work will be organized.

We establish stages, responsibilities, deliverables and criteria that allow us to evaluate whether the solution is achieving the expected result.

We also determine what needs to be built, modified, integrated or leveraged from what already exists.

We do not seek to design the biggest or most sophisticated solution.

We seek the solution that makes sense for the need, the context and the organization’s actual capabilities.

Good design means turning a strong understanding of the problem into a project that can be executed with clarity.

Turn what was designed into a solution that works in the real world.

When the project requires execution, we put the strategy into practice.

We coordinate the necessary capabilities and specialists, develop solutions, configure what is required, implement changes and support the rollout.

Implementation may involve technology, processes, infrastructure, systems, training, communication, talent or other disciplines, depending on what the project requires.

We do not seek to execute more than necessary.

We seek to ensure that every component responds to the defined objective and works within the organization’s real conditions.

Throughout implementation, we validate progress, make necessary adjustments and verify that what has been developed can operate as intended.

Implementation means turning a good decision into a solution that can actually be used and create value.

Prepare people to continue with what has been built.

An implementation is not complete simply because the solution is working.

We also need to consider who will use it, manage it, maintain it or continue developing it after the project.

That is why we document what is necessary, explain decisions, share knowledge and prepare the people responsible for continuing what has been implemented.

When the project requires it, we develop training, support or transition processes to facilitate adoption and ensure that knowledge does not remain concentrated only among those involved in developing the solution.

We also leave the organization in control of the resources, access credentials, documentation and assets that belong to it.

The depth of this transfer depends on each project.

Transfer means creating the conditions necessary for what has been implemented to continue working, being used and evolving after our involvement ends.

Evaluate what was achieved, learn and decide what comes next.

Once the solution is working, we compare the results against the objectives and criteria defined during the project design.

We review what worked, what needs adjustment and what we learned from the implementation.

When appropriate, we make improvements, correct deviations or strengthen the areas needed to consolidate the result.

We may also identify new opportunities that were not previously visible or that emerge as a result of what was learned during the project.

This does not mean every intervention should continue indefinitely.

A project can achieve its objective and come to an end.

And if a new need, opportunity or challenge arises later, we can work together again, building on what we already know and have developed.

Evolving means using the results and learning from the project to make better decisions about what comes next.

Every project has its own reality.

Some require an in-depth diagnosis before the intervention can be defined.

Others begin with sufficiently clear conditions and can move more quickly toward design or implementation.

Some projects involve a single capability, while others require the integration of different disciplines and specialists.

The depth of knowledge transfer, evaluation criteria and the conditions required for continuity also vary.

Our methodology gives us a common logic for working.

The project determines how we apply it.