01 / VARIABLE
What can change?
Structure, tools, interfaces, processes, and the route taken to the next state.
Product · Platforms · Technology transformation
Change what can change.
Preserve what must remain. I help complex products, platforms, and organisations evolve without losing their logic, identity, or purpose.
Explore the invariantIntroducing Invariando
Evolution is easy.
Continuity takes design.
Invariando is a way of working with complex systems: separating what is essential from what is accidental, then changing with precision.
The objective is not to keep everything fixed. It is to ensure each new version can explain where it came from—and why it is still itself.
02 / INVARIANT
What must remain?
The purpose, identity, constraints, and relationships that make the system recognisably itself.
Problems, not departments
Complexity rarely lives in one box.
These problems sit between disciplines. So do I.
- 01
A product has accumulated features but lost direction.
- 02
Delivery is moving, but nobody can explain where value is getting lost.
- 03
Product and engineering are optimising different systems.
- 04
A platform needs to evolve without disrupting the organisation built around it.
- 05
AI is arriving faster than ownership, validation, and governance can adapt.
Where Invariando works
Across the seams.
Three recurring contexts. One governing principle: change the system without discarding what already makes it valuable.
Product & Platform
When product, technology, and operations have stopped telling the same story. Direction, platform evolution, prioritisation, and the operating model around them.
Complex Delivery
When legacy, dependencies, and multiple actors have made progress difficult to govern. Clarity and control without turning the work into PMO theatre.
AI & Agentic Systems
When new capabilities change how work, authority, and knowledge move. Adoption designed around ownership, validation, traceability, and purpose.
Change with trace
The terrain can change.
The path must remain legible.
How it works
Three movements.
One criterion.
From complexity to a transformation that remains clear, intentional, and traceable.
- 01
Read the system
Map relationships, tensions, and patterns before moving a single piece.
- 02
Choose the invariant
Make explicit what must survive the change: purpose, identity, or governing logic.
- 03
Transform with trace
Design every transition so the path remains legible, deliberate, and governable.
Patterns of work
Different systems.
Recurring tensions.
A view of the situations in which I tend to work, without pretending complex change fits inside a catalogue of services.
01 / PLATFORMS
Long-lived platforms
- Tension
- Legacy, multiple actors, and an operation that cannot simply stop while the system changes.
- Work
- Recover product direction, clarify ownership, and make dependencies visible.
- Preserve
- The capabilities, relationships, and operational continuity the organisation already relies on.
02 / PRODUCTS
Specialist products becoming scalable
- Tension
- Complex technology needs to become a coherent product without flattening the knowledge that makes it useful.
- Work
- Connect users, product direction, technical choices, and delivery around a path that can scale.
- Preserve
- Domain fidelity, purpose, and the expertise embedded in the existing system.
03 / AI
AI entering real delivery systems
- Tension
- New capabilities arrive in workflows built around different assumptions about work and authority.
- Work
- Redesign product and delivery around what AI changes, rather than adding another tool.
- Preserve
- Responsibility, validation, traceability, and control.
The person behind the practice
I'm Mario Yáñez.
Invariando is my independent practice. I work where software, products, organisations, and complex delivery systems meet.
I started close to the code and gradually moved outward—from building software, to leading projects and platforms, to shaping products, operating models, and transformation initiatives.
That trajectory means I tend to see organisations as systems rather than collections of departments, roles, processes, or backlogs. I do my best work when the problem does not fit neatly inside a single function.
The titles have changed. The underlying work has remained remarkably invariant.
Ways to work together
Enter where the system needs it.
Sometimes the right answer is a role. Sometimes it is an intervention.
Embedded leadership
Sustained ownership inside an organisation or initiative when the problem needs proximity to the teams doing the work.
Fractional / advisory
An experienced counterpart for recurring product, technology, operating-model, transformation, or AI decisions.
Focused engagements
A bounded problem, a period of investigation, and a concrete outcome before committing to a larger change.
The governing question
What must still be true
after the transformation?
Bring me the messy version.
You do not need a polished brief. A product, platform, or organisation that needs to change is enough to start.
Start a conversation