Typical situations
You feel the need to automate part of your business
You have a list of initiatives, but no clear priorities
A project is already under way, but the rationale behind decisions is getting lost
Technical proposals are difficult to assess from a management perspective
What we focus on
Support before development begins:
Approach
Most IT problems are not purely technical. They arise from decision-making logic, priorities and management constraints.
The work starts not with technology, but with the structure of the business and the variables within the system.
IT initiatives are rarely exclusively technical tasks. More often, they concern:
- —decision structures
- —priorities
- —management constraints
- —the logic of consequences
Mistakes at this level cost far more than technical errors. The work focuses on clarifying the rationale behind initiatives, validating decisions and aligning the business context with technology choices.
Experience
Supporting IT initiatives in a range of contexts:
The main contribution is not technical delivery, but clarifying the structure of the challenges and decisions.
About
You can launch an IT project on the assumption that automation will improve efficiency. Or you can do it knowing that metric "X" will improve by "Y", for an investment of "Z", with an expected return in "T" months. That is what I work out with you before we begin.
I step in before development, before the budget is committed and before teams are mobilised. Not to slow projects down, but to make sure they are heading in the right direction.
In three days, we clarify the hypothesis, structure the business decision and define how to test it on a small scale before investing.
Sometimes the conclusion is: go ahead. Sometimes it is: not this way. Both are valuable.
Education: École Supérieure des Affaires, Grenoble (Pierre Mendès France University)