There are 2 main ways people tend to think about a #system 
I'm passionate in both. And enjoy using tools from science of systems to make life better. 

Yes, a process is also sometimes called a system: the order and manner you do stuff.

And you can get it into a structured pattern, like a recipe. To solve whatever you like.

Start here

This cat understands rocket science just as well as as some MBSE specialists understand systems architecture.

This image generation took seconds. Actual rocket science takes decades of cumulative knowledge.

Why I'm banging on this? 👇 

𝗪𝗲 𝗮𝗿𝗲 𝗰𝗼𝗻𝗳𝘂𝘀𝗶𝗻𝗴 𝘁𝗼𝗼𝗹 𝗽𝗿𝗼𝗳𝗶𝗰𝗶𝗲𝗻𝗰𝘆 𝘄𝗶𝘁𝗵 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗰𝗼𝗺𝗽𝗲𝘁𝗲𝗻𝗰𝗲.

Knowing how to operate a complex MBSE tool suite does not make you a Systems Engineer. It makes you a tool operator!

If you cannot define the problem space, identify constraints, and validate architectures without the software crutch, you are not ready to build critical systems.

The tool should accelerate your thinking, not replace it.

Are you an MBSE cat?

𝗧𝗵𝗲 𝗦𝘂𝗿𝗳𝗮𝗰𝗲 𝗟𝗲𝘃𝗲𝗹 𝗧𝗿𝗮𝗽 ->
I asked Copilot to generate an Astrophysics cat so I can talk about Systems Engineering and rocket science!

The result looks convincing. The aesthetic is right. 

RIGHT?  👇 

The equations on the board probably even make sense in isolation.

𝗕𝘂𝘁 𝘁𝗵𝗲 𝗰𝗮𝘁 𝗵𝗮𝘀 𝗻𝗼 𝗶𝗱𝗲𝗮 𝘄𝗵𝗮𝘁 𝗶𝘁 𝗶𝘀 𝗱𝗼𝗶𝗻𝗴.

This is exactly what I see happening in engineering teams right now.

We have incredible modelling tools. We generate complex diagrams that look professional and authoritative. 

But the people driving the tools often lack the fundamental domain expertise to know if the output is garbage.

A pretty model based on bad assumptions is just dangerous. Stop confusing the map with the territory.

𝗥𝗲𝗺𝗲𝗺𝗯𝗲𝗿 𝘁𝗵𝗮𝘁 𝗮𝗹𝗹 𝗺𝗼𝗱𝗲𝗹𝘀 𝗮𝗿𝗲 𝘄𝗿𝗼𝗻𝗴. 𝗘𝘃𝗲𝗻 𝘄𝗵𝗲𝗻 𝘀𝗼𝗺𝗲 𝗼𝗳 𝘁𝗵𝗲𝗺 𝗮𝗿𝗲 𝘂𝘀𝗲𝗳𝘂𝗹

Astrophysics Cat & Systems Engineering

𝗥𝗲𝗰𝗶𝗽𝗲𝘀 𝗮𝗿𝗲 𝗳𝗼𝗿 𝗰𝗼𝗼𝗸𝘀. 𝗡𝗼𝘁 𝗰𝗵𝗲𝗳𝘀!
Stop asking for the "standard template." Forget the recipes.

Engineering is about solving unique problems. 👇 

I see too many practitioners treating Systems Engineering as a compliance exercise. They think the job is just turning the handle and checking boxes.

They believe if they buy the expensive license the tool will do the thinking for them.

This is dangerous.

𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗶𝗻 𝘁𝗵𝗲 𝗵𝗮𝗻𝗱𝘀 𝗼𝗳 𝗮𝗻 𝗮𝗺𝗮𝘁𝗲𝘂𝗿 𝗺𝗲𝗿𝗲𝗹𝘆 𝗮𝗺𝗽𝗹𝗶𝗳𝗶𝗲𝘀 𝘁𝗵𝗲𝗶𝗿 𝗶𝗻𝗰𝗼𝗺𝗽𝗲𝘁𝗲𝗻𝗰𝗲.

If you automate a flawed process you do not get efficiency. You get chaos at scale!

Real Systems Engineering is not administrative work. It is the rigorous application of field-tested, proven best practices.

It requires deep collaboration with the business to 𝗶𝗱𝗲𝗻𝘁𝗶𝗳𝘆 𝘁𝗵𝗲 𝙧𝙚𝙖𝙡 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 𝗮𝗻𝗱 𝗱𝗲𝗹𝗶𝘃𝗲𝗿 𝘁𝗵𝗲 𝙧𝙞𝙜𝙝𝙩 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻.

Tools support this process. They do not replace the engineer.

𝗕𝗲 𝗮 𝗰𝗵𝗲𝗳. 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝘁𝗵𝗲 𝗶𝗻𝗴𝗿𝗲𝗱𝗶𝗲𝗻𝘁𝘀.

Some Engineers are COOKED!

There's a reason why I was so quiet lately! I was wo𝗿king the future:
𝗕𝗶𝗴 𝗻𝗲𝘄𝘀 𝗶𝗻 𝘁𝗵𝗲 𝗮𝘂𝘁𝗼𝗻𝗼𝗺𝗼𝘂𝘀 𝗺𝗼𝗯𝗶𝗹𝗶𝘁𝘆 𝘀𝗽𝗮𝗰𝗲! 

Have you seen that TIER IV is teaming up with HORIBA MIRA ? Two powerhouses in autonomous driving and engineering. 

To kick off new projects right here in the UK and across Europe. What stands out? 

TIER IV isn’t just bringing their autonomous platform and Minibus 2.0 EV; they’re also leaning on HORIBA MIRA’s real-world testing ground and local expertise to make this tech genuinely work in European cities. 

The first step is launching an autonomous bus at the UK proving ground. It’s down-to-earth, safety-first, and heavily focused on meeting actual community needs. 

As someone who loves 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗮𝗹 tech with an impact, I’m excited to see how this partnership rolls out real deployments, moving beyond just PR and pilot talk.

It was a great pleasure to work together with Tier IV colleagues and lead this project.

Curious where it’ll show up next and how many local operators will get on board!

Come, let's follow the progress together.

𝗦𝗲𝗲 𝘁𝗵𝗲 𝗮𝗻𝗻𝗼𝘂𝗻𝗰𝗲𝗺𝗲𝗻𝘁 𝗵𝗲𝗿𝗲:
https://www.eurekamagazine.co.uk/content/news/new-collaboration-drives-autonomous-vehicle-deployment-in-europe

What I'm Cooking in Autonomy?

Everyone's obsessing over the “perfect tool” BUT guess what?

If you’re burning hours fighting your app or chasing certifications you’re not an engineer... you’re just your own overpriced IT support.

Systems Engineering is about THINKING NOT tool mastery!

Tell me I’m wrong!


Use your head better, not your tool.

https://use.toth.al/posts/the-perfect-tool-trap-bigger-is-not-better


Think before using your tool

So what do systems engineers bring to the table?

They bring structure. They bring clarity. They liaise and bond expertise.

They also bring a different sort of tribal knowledge, the knowledge of how to put a large complex system together in a methodical and optimal way.

"𝘵𝘩𝘪𝘴 𝘰𝘯𝘦 𝙝𝙞𝙩 𝙝𝙤𝙢𝙚 𝙛𝙤𝙧 𝙨𝙤𝙢𝙚 𝙧𝙚𝙖𝙨𝙤𝙣. 𝘛𝘩𝘢𝘯𝘬 𝘺𝘰𝘶"

Someone recently asked for advice on improving in systems engineering. My answer seems to have "this one hit home" .. 😎

My suggestion was different from the usual "get another degree" path. I recommended prioritising practical experience over more academic qualifications early in a career.

As a SE mentor and CSEP, My core points were: 👇 

• 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗼𝗻-𝘁𝗵𝗲-𝗷𝗼𝗯 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴. Hands-on work is more valuable than theory alone. A master's degree has limited value without the corresponding practical application in a company that does proper systems engineering.

• 𝗚𝗲𝘁 𝗮 𝗺𝗲𝗻𝘁𝗼𝗿. You will progress much faster with guidance from someone experienced.

• 𝗨𝘀𝗲 𝘁𝗵𝗲𝗼𝗿𝘆 𝘁𝗼 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝘆𝗼𝘂𝗿 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲. Education is not a substitute for practice. It is a tool to organise and understand what you learn by doing.

I see some pursue advanced degrees in systems engineering immediately after college. I suggest a different path: get a job and build your skills first. Focus on practice. You can get certificates or advanced degrees later to formalise your expertise.

Don't get me wrong: education is important. But not without putting it in practice.
The example I always give: you can learn all theory for driving a car for years. Until you put in months of practice, you still won't be able to drive a car!

𝗡𝗼𝘁𝗵𝗶𝗻𝗴 𝗿𝗲𝗽𝗹𝗮𝗰𝗲𝘀 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲 in professions that create something!
Or would you like being operated on by a surgeon who has a PhD and never operated before for real??

𝗦𝗮𝗺𝗲 𝗶𝗻 𝗦𝘆𝘀𝘁𝗲𝗺𝘀. In Engineering in general, and any hands-on profession.

What is your view? How much weight should be given to practical experience versus formal education in engineering?

If you have questions, feel free to reach out. 

𝘐 𝘴𝘩𝘢𝘳𝘦 𝘮𝘰𝘳𝘦 𝘰𝘯 𝘵𝘩𝘪𝘴 𝘵𝘰𝘱𝘪𝘤 𝘩𝘦𝘳𝘦 𝘢𝘯𝘥 𝘪𝘯 𝗺𝘆 𝗻𝗲𝘄𝘀𝗹𝗲𝘁𝘁𝗲𝗿 (𝗹𝗶𝗻𝗸 𝗶𝗻 𝗯𝗶𝗼). 𝘐 𝘢𝘭𝘸𝘢𝘺𝘴 𝘦𝘯𝘤𝘰𝘶𝘳𝘢𝘨𝘦 𝘱𝘦𝘰𝘱𝘭𝘦 𝘵𝘰 𝘳𝘦𝘱𝘭𝘺 𝘢𝘯𝘥 𝘢𝘴𝘬.

Prioritize Experience Over Degrees

I just came off a call with one of my mentees. This conversation got me thinking of how people do their work, learn and improve ...
So here are some of my thoughts 👇 

The quickest way to irrelevance is doing things because that's how you been told and we always did it like that. Mechanically applying recipes!

The engineering skill that's hard to teach in school:

𝗧𝗵𝗶𝗻𝗸𝗶𝗻𝗴 ...

It's not just for 'systems engineers.'

It's seeing the forest AND the trees.

Understanding how all the pieces fit together.
Spotting potential issues before they become problems.

𝗜𝘁 𝗰𝗼𝗺𝗲𝘀 𝗳𝗿𝗼𝗺 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝗻𝗼𝘁 𝘁𝗲𝘅𝘁𝗯𝗼𝗼𝗸𝘀.

And it's crucial in today's complex tech landscape.

How to build it in your team:
1. Encourage cross-functional projects
2. Promote knowledge sharing sessions
3. Rotate roles occasionally
4. Celebrate holistic problem-solving

You are an engineer just starting out and not sure how to apply the above? The same way:

1. Cultivate your curiosity and ask to get involved with various disciplines' work to learn and get experience
2. Team up with your peers to learn together. And share experience
3. Ask to do different roles in projects. Note that the role is not the same as your job title

4. Celebrate your win and publicly talk about them. When you explain to others your learning gets multiplied (see Feynman learning principle)
 [𝘩𝘪𝘯𝘵: 𝘵𝘩𝘪𝘴 𝘭𝘢𝘴𝘵 𝘰𝘯𝘦 𝘪𝘴 𝘸𝘩𝘢𝘵 𝘐'𝘮 𝘥𝘰𝘪𝘯𝘨 𝘩𝘦𝘳𝘦 𝘰𝘯 𝘓𝘪𝘯𝘬𝘦𝘥𝘐𝘯 𝘵𝘰𝘰]

In engineering 𝘁𝗵𝗲 𝘄𝗵𝗼𝗹𝗲 𝗶𝘀 𝗼𝗳𝘁𝗲𝗻 𝗴𝗿𝗲𝗮𝘁𝗲𝗿 𝘁𝗵𝗮𝗻 𝘁𝗵𝗲 𝘀𝘂𝗺 𝗼𝗳 𝗶𝘁𝘀 𝗽𝗮𝗿𝘁𝘀. And in Systems too.

Foster systems thinking and you'll see your team's problem-solving abilities improve significantly.

𝗦𝗼 𝘄𝗵𝗮𝘁'𝘀 𝘀𝘁𝗼𝗽𝗽𝗶𝗻𝗴 𝘆𝗼𝘂 𝘁𝗼 𝗴𝗲𝘁 𝟭% 𝗯𝗲𝘁𝘁𝗲𝗿 𝗲𝘃𝗲𝗿𝘆𝗱𝗮𝘆?

Engineering Beyond the Recipe

𝗜'𝗠 𝗕𝗔𝗖𝗞! 𝗜 𝗙𝗼𝘂𝗴𝗵𝘁 𝗠𝗦 𝗪𝗼𝗿𝗱 𝗧𝗼𝗱𝗮𝘆. 𝗜𝘁 𝗪𝗼𝗻!
You are supposed to be the master of your tools. So why does it feel like you spend all day fighting them just to get simple work done?

It was a simple task:  -->

Write a one-page document. A few paragraphs of text and one image. That's it.
So I opened Microsoft Word.

The writing was fine. Then I tried to add the photo.

I spent the next 20 minutes fighting the software. I just wanted the image to sit 𝘩𝘦𝘳𝘦, with the text wrapped 𝘢𝘳𝘰𝘶𝘯𝘥 it.

Word decided it should be on the next page. Or behind the text. Or in the header.

The tool, which is supposed to 𝘦𝘯𝘢𝘣𝘭𝘦 my work, became the work itself. I was wrestling with a bloated piece of software that tries to do everything, but makes simple tasks difficult.

I wasn't doing my job. I was working for the tool.


𝗔𝗻𝗱 𝘁𝗵𝗶𝘀 𝗶𝘀 𝘁𝗵𝗲 𝘁𝗿𝗮𝗽.

In our work, we often accept the default tools and processes. We use what we've "always used" because it's the company standard or just the path of least resistance.

𝗦𝘆𝘀𝘁𝗲𝗺𝘀 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝘁𝗲𝗮𝗰𝗵𝗲𝘀 𝘂𝘀 𝘁𝗼 𝗯𝗲 𝗱𝗲𝗹𝗶𝗯𝗲𝗿𝗮𝘁𝗲.
The goal is not to "use Word" or "follow the old process." The goal is to deliver value effectively.
_____________________________________________>>

Is your tool helping you do that? Or is it, like my Word document, actively getting in the way?
A tool should be transparent. It should be an extension of your work, allowing you to focus on the 𝘱𝘳𝘰𝘣𝘭𝘦𝘮 (the system, the requirements, the design) not on the 𝘵𝘰𝘰𝘭.

We spend too many hours fighting software, navigating processes that add no value, or using complex methods when a simple one would work better.

What if we deliberately chose our tools and methods based on one question: 𝗗𝗼𝗲𝘀 𝘁𝗵𝗶𝘀 𝗱𝗲𝗹𝗶𝘃𝗲𝗿 𝘁𝗵𝗲 𝗺𝗼𝘀𝘁 𝘃𝗮𝗹𝘂𝗲 𝗶𝗻 𝘁𝗵𝗲 𝘀𝗶𝗺𝗽𝗹𝗲𝘀𝘁 𝘄𝗮𝘆?

You might find that for a simple document, a basic text editor is the right system. You might find the "way it's always been done" is the biggest roadblock you have.
Stop working 𝘧𝘰𝘳 your tools. Start choosing the tools that work 𝘧𝘰𝘳 y͟o͟u͟!

What's the one tool or process you wrestle with every week? The one thing that just gets in the way of real work.

Hit reply and let me know. I'm curious.