This blog grew from a simple conviction: technology becomes truly useful when it addresses an understood need, respects the people who will use it and makes their work simpler rather than heavier.
Through my work with Moodle, IOMAD and various digital environments, I have often found that the visible problem is not always the real one. A platform may seem difficult to use when the journey has never been clearly defined. Automation may fail because responsibilities are poorly distributed between systems. A course may contain all the necessary information without actually helping someone learn.
Understand before proposing
My first responsibility is therefore to listen, observe and ask the right questions. What outcome are you trying to achieve? Who will use the solution? What already works? Where are the pain points, duplicate entries or risks of error?
This step distinguishes the real need from the solution initially imagined. It prevents adding unnecessary technology or digitally reproducing a process that should first be simplified.
What I can contribute
I help organizations, training teams and educators design and improve their learning environments. Depending on the project, my work may include:
- instructional design and structuring learning paths;
- configuring, adapting and optimizing Moodle or IOMAD;
- analyzing processes around enrolment, cohorts, attendance and tracking;
- integrating Moodle coherently with a CRM, website or support service;
- creating tools, prototypes and demonstrations to make a concept tangible;
- documenting choices and transferring knowledge to teams.
A sustainable solution depends on more than what it can do. It also depends on people’s ability to understand, use and develop it.
An approach that is both rigorous and creative
My background is in teaching, but also in creative work. Music, imagery, experimentation and finding new ways to explain things are part of how I work. This creativity does not replace rigour: it helps me make systems more understandable, learning more lively and solutions better suited to their context.
I favour standard tool features when available, Moodle and web best practices, accessibility, security proportionate to risk and documentation that preserves the reasoning behind decisions.
Trust also requires acknowledging limits
I can analyze, design, configure, document and support many types of digital work. However, I do not claim to replace every profession. When a project requires regulated expertise, ongoing operational responsibility or a specialty beyond my scope, I prefer to say so clearly and recommend involving the right person.
For me, this transparency is not a weakness. It is part of a healthy professional relationship and protects the project, the organization and its users.
What you will find in this blog
I will publish reflections drawn from practice, accessible explanations, working methods, lessons learned and ideas for making better use of Moodle, IOMAD and the tools around them. Some articles will discuss teaching and learning, others digital architecture, automation, user experience or training management.
The common thread will remain the same: understand what we want to improve, choose tools thoughtfully and build solutions that make sense for the people using them.
Welcome to this space for reflection, sharing and building.