Iñigo Alonso Fernández
@inigoalonso.com
Systems Engineer - PhD in Product Development
Not great news for Venezuela.
November 12, 2025 at 4:04 PM
Not great news for Venezuela.
Loose definition + weak oversight = built-in abuse
September 19, 2025 at 2:54 PM
Loose definition + weak oversight = built-in abuse
The key takeaway: Tracking how engineers use risk tools over time reveals how to use which design supports to build robust systems.
Full paper here 👉 doi.org/10.1017/dsj....
Full paper here 👉 doi.org/10.1017/dsj....
Managing technical risks caused by indirect interactions: insights from tracking the use of risk assessment tools | Design Science | Cambridge Core
Managing technical risks caused by indirect interactions: insights from tracking the use of risk assessment tools - Volume 11
doi.org
July 17, 2025 at 2:57 PM
The key takeaway: Tracking how engineers use risk tools over time reveals how to use which design supports to build robust systems.
Full paper here 👉 doi.org/10.1017/dsj....
Full paper here 👉 doi.org/10.1017/dsj....
Big thanks to Massimo & Ola for their guidance, and to the great participants from Volvo Cars & Volvo Trucks, your discussions and good spirits made this research possible!
#VolvoCars #VolvoTrucks
#VolvoCars #VolvoTrucks
July 17, 2025 at 2:57 PM
Big thanks to Massimo & Ola for their guidance, and to the great participants from Volvo Cars & Volvo Trucks, your discussions and good spirits made this research possible!
#VolvoCars #VolvoTrucks
#VolvoCars #VolvoTrucks
✅ Use risk assessment tools early: catching indirect interactions early reduces nasty surprises later.
⚠️ But don’t overdo it: we found that low-intensity, long-term use is more effective than short bursts of intense analysis.
#ResearchInsights
⚠️ But don’t overdo it: we found that low-intensity, long-term use is more effective than short bursts of intense analysis.
#ResearchInsights
July 17, 2025 at 2:57 PM
✅ Use risk assessment tools early: catching indirect interactions early reduces nasty surprises later.
⚠️ But don’t overdo it: we found that low-intensity, long-term use is more effective than short bursts of intense analysis.
#ResearchInsights
⚠️ But don’t overdo it: we found that low-intensity, long-term use is more effective than short bursts of intense analysis.
#ResearchInsights
In complex, high-stakes systems, this is how we contain the entropy.
This is how we move forward without delusion.
This is what Systems Engineering is for.
This is how we move forward without delusion.
This is what Systems Engineering is for.
May 26, 2025 at 4:46 PM
In complex, high-stakes systems, this is how we contain the entropy.
This is how we move forward without delusion.
This is what Systems Engineering is for.
This is how we move forward without delusion.
This is what Systems Engineering is for.
It’s a form of humility:
We admit we don’t know everything at the start.
But we commit to making good decisions anyway; by design, not by accident.
We admit we don’t know everything at the start.
But we commit to making good decisions anyway; by design, not by accident.
May 26, 2025 at 4:46 PM
It’s a form of humility:
We admit we don’t know everything at the start.
But we commit to making good decisions anyway; by design, not by accident.
We admit we don’t know everything at the start.
But we commit to making good decisions anyway; by design, not by accident.
A mature SE process treats requirements as living constructs.
Not contracts to lock down, but frameworks to evolve as reality unfolds.
Not contracts to lock down, but frameworks to evolve as reality unfolds.
May 26, 2025 at 4:46 PM
A mature SE process treats requirements as living constructs.
Not contracts to lock down, but frameworks to evolve as reality unfolds.
Not contracts to lock down, but frameworks to evolve as reality unfolds.
At ESS, requirements for neutron flux, shielding, or control latency shouldn’t be fixed specs.
They should be negotiations, between physics, engineering, safety, and cost.
SE helps keep that negotiation disciplined and productive.
They should be negotiations, between physics, engineering, safety, and cost.
SE helps keep that negotiation disciplined and productive.
May 26, 2025 at 4:46 PM
At ESS, requirements for neutron flux, shielding, or control latency shouldn’t be fixed specs.
They should be negotiations, between physics, engineering, safety, and cost.
SE helps keep that negotiation disciplined and productive.
They should be negotiations, between physics, engineering, safety, and cost.
SE helps keep that negotiation disciplined and productive.
This process includes:
Translating vague goals into testable behaviors
Resolving requirement conflicts across domains
Establishing traceability to anchor decisions
Managing inevitable change with rigor
Translating vague goals into testable behaviors
Resolving requirement conflicts across domains
Establishing traceability to anchor decisions
Managing inevitable change with rigor
May 26, 2025 at 4:46 PM
This process includes:
Translating vague goals into testable behaviors
Resolving requirement conflicts across domains
Establishing traceability to anchor decisions
Managing inevitable change with rigor
Translating vague goals into testable behaviors
Resolving requirement conflicts across domains
Establishing traceability to anchor decisions
Managing inevitable change with rigor
Systems Engineering doesn’t solve this with a perfect list of specs.
Instead, it gives us a process for converging on clarity over time.
Instead, it gives us a process for converging on clarity over time.
May 26, 2025 at 4:46 PM
Systems Engineering doesn’t solve this with a perfect list of specs.
Instead, it gives us a process for converging on clarity over time.
Instead, it gives us a process for converging on clarity over time.
Stakeholders don’t always know what they want.
Engineers don’t yet know what’s possible.
And projects are boxed in by budget, compliance, and deadlines from day one.
Engineers don’t yet know what’s possible.
And projects are boxed in by budget, compliance, and deadlines from day one.
May 26, 2025 at 4:46 PM
Stakeholders don’t always know what they want.
Engineers don’t yet know what’s possible.
And projects are boxed in by budget, compliance, and deadlines from day one.
Engineers don’t yet know what’s possible.
And projects are boxed in by budget, compliance, and deadlines from day one.
In complex systems (think particle accelerators, automotive platforms, control systems) early requirements are rarely complete or stable.
They’re often ambiguous, conflicting, or just… aspirational.
They’re often ambiguous, conflicting, or just… aspirational.
May 26, 2025 at 4:46 PM
In complex systems (think particle accelerators, automotive platforms, control systems) early requirements are rarely complete or stable.
They’re often ambiguous, conflicting, or just… aspirational.
They’re often ambiguous, conflicting, or just… aspirational.
So no, Systems Engineering doesn’t find “the best solution.”
It finds the right compromise.
And in complex systems, that’s not settling; that’s mastery.
#SystemsEngineering #EngineeringLeadership #ProjectManagement #ProductDevelopment
It finds the right compromise.
And in complex systems, that’s not settling; that’s mastery.
#SystemsEngineering #EngineeringLeadership #ProjectManagement #ProductDevelopment
May 24, 2025 at 6:47 PM
So no, Systems Engineering doesn’t find “the best solution.”
It finds the right compromise.
And in complex systems, that’s not settling; that’s mastery.
#SystemsEngineering #EngineeringLeadership #ProjectManagement #ProductDevelopment
It finds the right compromise.
And in complex systems, that’s not settling; that’s mastery.
#SystemsEngineering #EngineeringLeadership #ProjectManagement #ProductDevelopment
In the end, SE is about informed decision-making.
Not making everyone perfectly happy, but ensuring rational, transparent, and defensible trade-offs.
It keeps systems viable, valuable, and verifiable.
Not making everyone perfectly happy, but ensuring rational, transparent, and defensible trade-offs.
It keeps systems viable, valuable, and verifiable.
May 24, 2025 at 6:47 PM
In the end, SE is about informed decision-making.
Not making everyone perfectly happy, but ensuring rational, transparent, and defensible trade-offs.
It keeps systems viable, valuable, and verifiable.
Not making everyone perfectly happy, but ensuring rational, transparent, and defensible trade-offs.
It keeps systems viable, valuable, and verifiable.
Metaphor time:
SE is like conducting an orchestra where:
The score changes mid-performance
The musicians interpret it differently
And the sponsor keeps revising what “success” sounds like
You can’t control every note; but you shape the harmony.
SE is like conducting an orchestra where:
The score changes mid-performance
The musicians interpret it differently
And the sponsor keeps revising what “success” sounds like
You can’t control every note; but you shape the harmony.
May 24, 2025 at 6:47 PM
Metaphor time:
SE is like conducting an orchestra where:
The score changes mid-performance
The musicians interpret it differently
And the sponsor keeps revising what “success” sounds like
You can’t control every note; but you shape the harmony.
SE is like conducting an orchestra where:
The score changes mid-performance
The musicians interpret it differently
And the sponsor keeps revising what “success” sounds like
You can’t control every note; but you shape the harmony.
This isn’t easy. Stakeholder needs shift. Engineers discover new constraints. Projects run into surprises.
SE is often more like playing 3D chess than solving a triangle.
It’s dynamic. It’s messy. It’s real-world problem solving.
SE is often more like playing 3D chess than solving a triangle.
It’s dynamic. It’s messy. It’s real-world problem solving.
May 24, 2025 at 6:47 PM
This isn’t easy. Stakeholder needs shift. Engineers discover new constraints. Projects run into surprises.
SE is often more like playing 3D chess than solving a triangle.
It’s dynamic. It’s messy. It’s real-world problem solving.
SE is often more like playing 3D chess than solving a triangle.
It’s dynamic. It’s messy. It’s real-world problem solving.
Alternatively, you can think about SE not just as balancing trade-offs, but as an alignment mechanism.
It aligns intent, design, and outcomes across time and teams.
It ensures that what’s built actually delivers what was needed; even when that need evolves.
It aligns intent, design, and outcomes across time and teams.
It ensures that what’s built actually delivers what was needed; even when that need evolves.
May 24, 2025 at 6:47 PM
Alternatively, you can think about SE not just as balancing trade-offs, but as an alignment mechanism.
It aligns intent, design, and outcomes across time and teams.
It ensures that what’s built actually delivers what was needed; even when that need evolves.
It aligns intent, design, and outcomes across time and teams.
It ensures that what’s built actually delivers what was needed; even when that need evolves.
Think of SE as solving a constrained multi-variable equation.
You can’t maximize all variables, some must yield.
But the solution must still be:
Technically sound
Feasible to deliver
Valuable to the end-user
You can’t maximize all variables, some must yield.
But the solution must still be:
Technically sound
Feasible to deliver
Valuable to the end-user
May 24, 2025 at 6:47 PM
Think of SE as solving a constrained multi-variable equation.
You can’t maximize all variables, some must yield.
But the solution must still be:
Technically sound
Feasible to deliver
Valuable to the end-user
You can’t maximize all variables, some must yield.
But the solution must still be:
Technically sound
Feasible to deliver
Valuable to the end-user
A solution might be technically perfect; but unaffordable.
Another might be cheap and fast; but useless to the customer.
Another might thrill the stakeholder; but defy physics.
SE’s job? Not perfection. Balance.
Another might be cheap and fast; but useless to the customer.
Another might thrill the stakeholder; but defy physics.
SE’s job? Not perfection. Balance.
May 24, 2025 at 6:47 PM
A solution might be technically perfect; but unaffordable.
Another might be cheap and fast; but useless to the customer.
Another might thrill the stakeholder; but defy physics.
SE’s job? Not perfection. Balance.
Another might be cheap and fast; but useless to the customer.
Another might thrill the stakeholder; but defy physics.
SE’s job? Not perfection. Balance.
Bottom line: A weak FR leads to strong regrets. Build the right system before you build the system right.
#SystemsEngineering #EngineeringManagement #BigScience #ESS #FunctionalReview #VModel
#SystemsEngineering #EngineeringManagement #BigScience #ESS #FunctionalReview #VModel
May 21, 2025 at 10:39 PM
Bottom line: A weak FR leads to strong regrets. Build the right system before you build the system right.
#SystemsEngineering #EngineeringManagement #BigScience #ESS #FunctionalReview #VModel
#SystemsEngineering #EngineeringManagement #BigScience #ESS #FunctionalReview #VModel