Study & decide
Scoping an idea, testing its feasibility, defining an architecture, writing or reviewing a specification, auditing a project or shedding light on a technical decision. The goal: having what you need before committing.
About
Experience built in the field
The path that leads to eletec began in 1980, with teaching and programming.
Development, information systems, technical management, project management, advisory work, training: the roles changed over time, but contact with the technology and with users stayed.
Today that experience is used to design, evolve or get digital projects back on track — with the same curiosity about new technology and the same concern for staying concrete.
Behind eletec
Understanding the technology, the project and the people
eletec was built on a fairly unlinear path: teaching, writing software, designing information systems, running a services company, managing projects and then helping companies make their technical and organisational choices.
Having held those different positions changes the way you look at a project.
An architecture decision does not have the same consequences for the executive funding the project, the business manager waiting for it, the project lead who has to deliver it and the developer who will actually build it. Our job is often to get those viewpoints talking to each other.
Today, eletec works mainly in three areas: engineering and information systems, running and supporting projects, and integrating artificial intelligence where it genuinely answers a need.
“I still enjoy understanding how things work and getting my hands into the technical side. It changes the way you advise: you have a better sense of what a decision means for the people who will actually have to carry it out.”
In a few points
- Professional IT career began in 1980
- Fifteen years as an independent developer specialising in information systems
- Advisory, audit and project management since 2003
- Experience of teaching and of the technical training
- Training in listening and support, including through psychosynthesis
- More than 1,000 projects and assignments along the way, across very different industries
- Assignments in France and worldwide
Situation
-
Address 9, place Sébastopol
59000 Lille, France -
Where we work France & international — on site or remotely
-
Contact Secure contact form
Three ways to work together
Depending on where you stand
Steer & unblock
Taking charge of or supporting the running of a project, coordinating the players, helping with trade-offs, or stepping in when things start to jam. An outside view is sometimes useful before difficulties become expensive.
Deliver & hand over
Supporting the rollout, preparing the teams, documenting the choices and passing on the skills needed so the solution keeps working after the assignment ends.
Background
A professional career that began in 1980
The industry has changed profoundly since the first systems this path began on. So has the path: teaching, independent development, running a services company, then advisory work and project management.
Some technologies in this timeline have disappeared. The underlying questions — understanding the data, the processes, the constraints and the people — are far more stable.
-
Since 2003
Consulting, audit & project management
Supporting companies and organisations with scoping, auditing, running and rescuing digital projects. Assignments combine, as needed, advisory work, technical expertise, project management, mediation, coaching and team support.
Some environments: Tape à l’Oeil, European institutions, Groupe ADC, Auchan…
-
2000 — 2003
Managing director — CEI Media
Running a services company working in development, information systems, the web and interactive systems.
Organisations supported included: Auchan, City of Lille, Essilor, Schering, Carrefour, Galeries Lafayette, Bayard Presse…
-
1985 — 2000
Independent developer
Fifteen years devoted to designing and building software and information systems, through the arrival of the PC, networks, graphical interfaces and then the Web.
That period built very concrete knowledge of a software’s full lifecycle: understanding the need, modelling data, developing, deploying, maintaining and evolving.
Some environments: IBM, Microsoft, Groupe Emap, 3 Suisses, Atos, Compaq, France Télécom, Promod, French Ministry of Justice…
-
1980 — 1985
Teaching & IT training
First teaching and IT training work, alongside hands-on practice.
These experiences left a conviction that still holds: you have not really mastered a technology until you can explain it simply.
Historical environment: C, BASIC (BASICA).
-
1978 — 1980
Student — small systems computing (University of Lille I)
At the University of Lille I, work on the small systems of the time and a first look at a very young industry.
Machines, languages and methods have changed enormously since. The need to understand data, processing and users precisely — much less so.
-
1976 — 1977
Student — first programming (Fortran)
As a student, a first encounter with computing: writing Fortran on a Honeywell Bull Gamma 30 to compute a statistical distance used in classification (Mahalanobis D²).
Historical environment: Fortran, Honeywell Bull Gamma 30.
Along the way, training assignments with EDHEC, Lille I, France Télécom, La Poste, Schering and other organisations, on various languages, databases and system environments.
How we work
A few principles that do not change
Say when we disagree
A project can be too ambitious for its budget, a technology badly suited to the job, or an idea simply premature. Part of our role is to say so plainly, with the reasons behind that conclusion.
Stay independent
eletec is tied to no vendor and takes no commission for recommending a solution. Choices are made on the basis of the need, what already exists, the budget and the constraints of the project.
Leave something useful behind
Key decisions, architecture, procedures, known limits: we document what will be needed to understand, operate and evolve the solution.
Involve the users
The people who will actually use a tool often see problems a specification never shows. Bringing them in early enough produces something more useful — and makes it far easier to adopt.
Raise the alarm early
Projects almost always run into surprises. When a deadline, a cost or a scope looks like drifting, the information has to arrive early enough to allow a decision — not on delivery day.
Hand over
An assignment must not create needless dependency. We document the choices, explain how things work and pass on the knowledge your teams need to carry on without us.
Your teams must be able to carry on without us.
Let’s get acquainted
A first conversation is usually enough to understand your situation and see whether our experience can help. No pre-packaged sales pitch: just start by telling us about your project, your question or what is stuck today.