Values and culture

Principles used in the work

Meridian's values appear in decisions, documents, responsibilities and acceptance criteria. They must be observable during the project.

Principles

Observable principles

Clarity

Fact, hypothesis, scenario and commitment are handled separately

An estimate is presented with assumptions. A market figure has a source and a date. A contractual obligation identifies the owner, deadline and condition. When the information does not yet exist, the document records the gap.

Responsibility

Each party knows what it decides, executes, accepts and warrants

The scope distributes roles among client, Meridian, suppliers, specialists and external authorities. Meridian answers for what it takes on. Exclusive activities and third-party warranties remain with those responsible for their execution.

Traceability

Decisions and evidence must be recoverable

Assumptions, sources, versions, approvals and pending items are recorded throughout the work. In PADIS, this connects project, hours, cost, evidence, credit and reporting. In industrial implementation, it connects specification, supplier, schedule, test and acceptance.

Application

The method must work within the operation

The work includes implementing controls, training, monitoring and correction. The delivery is assessed by the use the company can make of it.

Independence

The recommendation follows the evidence

The study indicates the configuration and the conditions to move forward; the PADIS diagnosis shows where classification can be strengthened and how much of the benefit is effectively capturable. The recommendation is always well-founded, never adjusted just to close the next stage.

Autonomy

Knowledge and controls are transferred according to the scope

In PADIS implementation, the client's team is prepared to operate the cycle. In the factory, procedures, criteria and routines are organized for the team that will take over production. Later monitoring is defined according to the real need.

In practice

How the principles appear in the project

In decisions
  • explicit assumptions;
  • comparable alternatives;
  • recorded risks;
  • well-founded recommendation.
In execution
  • defined owners;
  • milestones and acceptance criteria;
  • pending-items control;
  • deviation reporting;
  • version history.
In the relationship
  • understandable scope;
  • conditions close to the statements;
  • no promise of approval or return;
  • direct communication about limits and delays.
Get to know Meridian

Get to know the company and the team