Skip to main content
INNOV DS

Co-founder · CEO

Mohamed Yahiaoui

Programme Director — Business solutions architect

25 years of information-system projects run end to end. The industrial ERP he led in 2010 is still running — and the same client relationship has lasted sixteen years.

25
years directing information-system projects
16
years of unbroken client relationship on the same system
7
client engagements directed since INNOV DS was founded
4.5
years heading an outsourced technical support centre

The business-side pilot

Correct software is not enough. It has to be adopted.

Three disciplines — and they are the ones that decide whether a project reaches its destination.

The business before the software

Scoping, processes, functional organisation. A system that does not fit the real process is never adopted, however good its code. It is the client's process that decides the software — never the other way round.

Steering that holds the milestones

A project is not steered by guesswork: contractual documents, steering committees, indicators defined at kick-off, acceptance testing run by the business. What is not measured is not steered.

Change management

A tool deployed but not adopted is a failure on a delay fuse. Support — training, materials, presence after go-live — is part of the project, not of the aftermath.

The guardrails

What keeps a project from drifting

Four rules, applied on every engagement. None is optional.

  1. 01

    No project starts without written scoping

    Scope, deliverables, responsibilities and acceptance criteria are contracted before the first line of code. Vague scoping is never recovered along the way: it is paid for at acceptance.

  2. 02

    What is not measured is not steered

    Indicators are defined when the project opens, not invented at review time. They are examined in committee, with the client, at a fixed cadence.

  3. 03

    Acceptance testing is done by the business

    Not by the team that produced the code. The person who will use the system every day is the only one who can say whether it does what it must.

  4. 04

    A deployment without support is a deferred failure

    Training, materials and presence after go-live are in the project, not an option. A system nobody uses has not been delivered.

Two stories

What 25 years leave behind

At INNOV DS

A 2012 industrial ERP, being rebuilt today

He led the project in 2010 for a construction-industry manufacturer — while at a previous employer: business design, process modelling, digitalisation of the ISO 9001 quality system. Live since 2012, the system is still at the heart of the client's operations. The relationship, sixteen years old, is now carried by INNOV DS — and the rebuild into microservices is under way.

Before INNOV DS

A technical support centre industrialised from Morocco

For more than four years he ran the level-2 support centre of a French telecom operator, outsourced to Morocco: segmentation into silos, handling and escalation processes rebuilt, a shift from a fixed-price to a work-unit contract, productivity gains capitalised. Industrialising a service is not a theory here: it was carried out.

The track record

Twenty-five years, in six milestones

The milestones before 2020 predate the founding of INNOV DS: they were carried out at successive employers.

  1. 2002

    Before INNOV DS

    Head of information systems for a higher-education institution.

  2. 2009

    Before INNOV DS

    Project manager at ALTEN / G-FIT — banking and consumer credit, in France.

  3. 2012

    Before INNOV DS

    Go-live of the industrial ERP (integrated management system, ISO 9001) whose project he led.

  4. 2014

    Before INNOV DS

    Head of the level-2 technical support centre of a French telecom operator, outsourced to Morocco.

  5. 2020

    At INNOV DS

    Founding of INNOV DS, which he runs as chief executive.

  6. 2025

    At INNOV DS

    The portfolio of client engagements, run in parallel on the firm's technical foundation.

Today

What he answers for

  • The client relationship and the contractual commitment — he signs what we promise.
  • Business scoping and functional design of engagements, ahead of the first line of code.
  • Holding the portfolio's milestones: committees, indicators, trade-offs.
  • Adoption at the client — training, support, presence after go-live.

Methods and tools

  • SCRUM
  • Kanban
  • BPMN 2.0
  • UML
  • ISO 9001
  • ITIL
  • PMO
  • Indicateurs de performance
  • Conduite du changement
  • Jira
  • Azure DevOps
  • GitLab

A process to digitalise?

Describe your organisation and your constraints: you will get a straight answer on what is feasible, at what cost and in what time.

Talk about your project