Case studies: projects, results, and lessons learned.

Q: How long does a project of this kind take?

That depends, of course, on the scope, the complexity of the environment and the level of transformation expected. Our aim nonetheless remains to produce visible value quickly, then develop the setup from real usage.

Our case studies present real situations, with their context, the setup put in place and the results observed.

We prefer facts to general formulas: when a figure exists, we publish it with its scope. When a limit or a trade-off is part of the project, we say so too.

Atlassian Platinum Solution Partner since 2008 · ITSM Specialized · Cloud Specialized · Paris and Lyon

Talk to an expert

Proof through results.

A case study is not a sales brochure.

Every case follows the same logic: the context, the need, the setup, then the results.

We take care to be as precise as possible.

Every figure comes from an engagement document

Scoping plan, acceptance report, activity record. No market average, no reconstructed estimate.

Every figure carries its unit and its scope

“500 tickets taken over with no service interruption”, not “hundreds of tickets”.

We are honest about the difficulties

A scope reassessed, a feature not carried over, a deadline overrun. A case with no friction at all is not a case, it is an advert.

“Our clients do not just entrust us with a project. Many call us back when their business has to take a new step.” Over the past three years, 83% of our target clients have stayed with us.

The three published cases.

An insurance client: from GLPI to Jira Service Management, with no service interruption

ITSM redesign

A client in the insurance sector replaced GLPI with Jira Service Management and Assets. BleuLemon ran the ITSM redesign from end to end.

Duration: 7 weeks to the first release, under 4 months for the whole project.
Carry-over: 500 tickets taken over with no service interruption.
Envelope: 117 days scoped, with lower invoicing in the end.
What came next?: The relationship continued with an application maintenance contract after the release.

Read this case study

A healthcare client: an anonymisation POC before any migration commitment

Cloud trajectory

A client in the healthcare sector, active in third-party payment, was preparing its Atlassian Cloud trajectory. BleuLemon carried out the audit of the existing environment, then a POC for anonymising sensitive data.

Audit: A full audit of the existing Atlassian environment.
POC: A POC for anonymising sensitive data, validated.
Trajectory: A Cloud trajectory documented before any commitment decision.

Read this case study

A defence client: a Manufacturing & Defence reference

Manufacturing & Defence

An international client in the defence sector is among BleuLemon's references. We publish only the information we have been authorised to release.

Read this case study

What about the other clients?

A large part of our engagements stays confidential: a sensitive sector, a project still running, or simply the client's choice. For others, we have not been given permission to publish.

We can present other references in a meeting, with the agreement of the companies concerned, choosing those closest to your situation: same sector, same platform size, same type of transformation or same regulatory constraints.

BleuLemon, a French consultancy (Paris, Lyon) and Atlassian Platinum Solution Partner since 2008, also holds the ITSM Specialized and Cloud Specialized specialisations.

Let's talk about your context

Frequently asked questions

A question that finds no answer here is dealt with in a 30-minute conversation, about your actual context rather than a general case.

Talk to an expert

Why do you publish only a few case studies?

Because not every engagement can be made public.

Some are covered by confidentiality commitments, others are still running or are simply not meant to be published.

We would rather publish few cases, but with a useful level of detail, than a long list of logos with no context.

How do you verify the figures you publish?

We rely on the engagement documents: scoping, activity records, acceptance reports, project reviews or production data.

We do not use a reconstructed estimate when a figure does not exist in the file.

Are the results shown representative of all your engagements?

Every engagement answers its own context, objectives and constraints.

The results shown illustrate what was achieved in a given environment, and are not meant to be transposed as they stand to another project.

How long does a project of this kind take?

It depends, of course, on the scope, the complexity of the environment and the level of transformation expected.

Our aim, nonetheless, remains to produce visible value quickly, then to develop the setup on the basis of real usage.

Going further: IT service management (ITSM / ESM)·Atlassian Cloud migration·Manufacturing & Defence·Banking, Finance & Insurance·The Assessment