Lab · Method
Measured with instruments, not memory: the method behind my systems
Designing systems, rather than selling tools, takes a method. Mine rests on frameworks companies already know —PMI's guide, Scrum and agile— with the quality discipline of ISO and Lean Six Sigma. This is how it works and what it guarantees to anyone who works with me.
November 20268 min
A natural evolution
Every project has taught me something, and one lesson came back more than any other: good work is not enough, you also have to be able to prove it. Users served, hours saved, decisions made; if that evidence isn't captured as it happens, it fades over time.
That lesson shaped the method's thesis:
Documentation is written during execution; results are measured with instruments, not memory.
A hybrid approach: PMI structure, Scrum delivery
The Project Management Institute's PMBOK® Guide recognises that most real projects are neither purely predictive nor purely agile, but hybrid. Órbita works that way: a phased structure that brings order and control, and an iterative build that delivers value from the first weeks.
Every project goes through five phases: framing, discovery, design, build and adoption. The first two match PMI's initiating and planning: a charter that sets the problem, the goal and what stays out, and a prioritised backlog built from the real process. The build happens in Scrum sprints. Adoption is the close: transition to operations and measured benefits.
Between phases sit three gates —kick-off, design validation and close— where we decide together whether the project moves ahead, moves ahead with adjustments or is rethought. A gate is not just another meeting: it is a review against the evidence, with the decision and its conditions in writing.
Agile where it adds value
Inside the build, the system grows in short sprints. Each one starts with planning, where we agree what goes in, taken from the backlog you prioritise as Product Owner, and ends with a review where you test an increment that already works. The retrospective closes the cycle: we look at how we work and improve it.
The benefit is concrete: if the course needs to change, we find out in weeks, not at the end of the project. It is the core idea of the Agile Manifesto —collaborate with the client and respond to change— applied to operations projects.
Quality and improvement with ISO and Lean Six Sigma
Managing the project is only half the job. The other half is making sure the process we digitise ends up better than it was, and for that Órbita relies on current quality frameworks:
- ISO 21502: life-cycle gates, transition to operations and benefits measured after closure.
- ISO 9001: process approach, evidence-based decisions and continuous improvement with the PDCA cycle.
- Lean Six Sigma (DMAIC): define and measure before improving, remove waste and control the improved process.
As complements I use Kanban to make the workflow visible, the BPM life cycle to map processes and the ADKAR model to support adoption. From each framework I take what adds value to real projects and leave the bureaucracy out: the result is not an invented methodology, but a reasoned application of recognised practices.
A method that adapts to your project
Digitising a form is not the same as building a system from scratch. As PMI recommends, the approach is tailored to the context: before we start, we identify the kind of challenge —digitising a process, building a tailored system, organising data and KPIs, managing knowledge or validating an idea— and apply only the rigour that adds value.
The level of documentation is also scaled to the project: light, standard or full. You pay for the rigour your project needs, not for bureaucracy.
Four principles
Process first, software second. Digitising a process you don't understand only automates the problem. In the Leaders App that meant mapping the Standard Work and updating procedures before writing the first screen: an AI agent on top of outdated documentation spreads the error instead of fixing it.
Working progress, not promises. Every sprint ends in something you can test, not in a progress report.
Built is not adopted. The project ends when your team uses it with ease, not when the system works.
Measured results, not assumed ones. We measure the starting point so the change can be proven; if something can't be measured, we say so clearly, never an estimate disguised as a result.
What this guarantees you
Shared decisions at every gate, progress you see working every sprint, a clear scope from day one and results you can verify. It's the same discipline behind the cases on this site: I only publish what is verified.