01 / Methodology
A visible process for technical decisions that must stand up to review.
The MIET methodology connects business, engineering and operations without imposing a solution before understanding the problem. The depth of each stage is adapted to criticality and the applicable framework.
1. Discover the context
We identify the objective, users, asset or process, available information, constraints, pending decisions and owners.
- Input
- Need, background, sources and stakeholders.
- Output
- Context map, questions and initial risks.
2. Define the scope
We translate the need into requirements, interfaces, deliverables, exclusions, assumptions, milestones and acceptance criteria.
- Control
- Every responsibility and dependency is identified.
- Decision
- The client validates priorities before development.
3. Develop and integrate
We deliver engineering, documentation, configuration, coordination or intervention with reviews and change control.
- Evidence
- Versions, comments, tests, findings and open items.
- Interface
- Visible connections between disciplines and third parties.
4. Validate and transfer
We assess the deliverable against agreed criteria, document open items and transfer information for continuity.
- Closure
- Acceptance, dossier, training and next steps.
- Continuity
- Ownership and conditions after the project.
A technical conversation starts with scope
