Being true to the name of this website, I've been philosophizing and pontificating about my chosen profession for several years now. Here at this blog you'll find my thoughts, and some of my friends, as we try to explore the meaning and ramifications of Systems Engineering on our culture and society. ~~Paul
Congress told NASA to build a new rocket out of old Shuttle parts. The INCOSE Handbook calls that a brownfield design problem. The cost difference between that approach and SpaceX's clean-sheet alternative is a systems engineering lesson worth $60 billion.
The electric vehicle supply chain stretches from a showroom in California to a cobalt mine in eastern Congo, and most of the people in between never appear on a requirements document. This piece starts with a classroom question about a cow and ends with a mine collapse, and the Systems Engineering lesson connecting them is the same one the INCOSE SE Handbook has been making all along: your stakeholders are everyone your system affects, not just the ones who are easy to find.
In March 2016, Go world champion Lee Sedol walked away from the board mid-match. He needed fifteen minutes alone to process a move that no human player would have considered, made by an AI system whose engineers could not fully explain why it had chosen it. That moment is still one of the most striking illustrations of what happens when a system develops an internal logic that outgrows its designers’ ability to describe it. This piece looks at what Move 37 still has to teach Systems Engineers about complexity, opacity, and the limits of understanding the systems we build.
Failure has come up on this blog before. It keeps coming up because disciplined learning from failure is one of the things that separates good systems engineering from the kind that produces dramatic footage. SpaceX's Starship test program is the current headline version of a problem systems engineers have always faced: how do you turn a visible, expensive failure into a genuine engineering asset rather than just a press release? This piece works through that question using the INCOSE SE Handbook's verification framework, and there is a free checklist at the bottom if you want a practical tool for doing it on your own program.
The Singularity debate is long on capability and short on maintenance. I know this pattern. I saw it at an air show thirty years ago when I asked a stealth fighter pilot if his aircraft was hard to maintain and he said “You have no idea.” No system escapes the life cycle. It just shifts where the cost and friction eventually show up. This piece examines what the AI acceleration narrative keeps leaving out, and what systems engineers are specifically trained to ask about it.
When Elon Musk floated the idea of putting servers in space, most people either cheered or rolled their eyes. Systems engineers should do neither. They should recognize the pattern: two radically different architectures, the same stakeholder need, and a genuinely interesting trade space worth examining. I dust off a favorite classroom example from the 2007 INCOSE SE Handbook to show why that kind of architectural imagination — disciplined, not fanciful — is exactly what the Handbook has always asked of us. There is also a free Architecture Alternatives Comparison Worksheet at the bottom, if you want a practical tool to do this in your own program before assumptions quietly harden into designs.
When I heard that Scott Adams had died, my mind went straight to a filing cabinet — and a folder of Dilbert cartoons I used to pull into SE training sessions whenever a room full of engineers needed permission to say what everyone was already thinking. Adams gave technical professionals exactly that: a way to laugh at broken systems before getting serious about fixing them. This is a tribute to the man who did it better than anyone, and a harder look at what his later career tells us about the cost of speaking uncomfortable truths.
Boeing’s recent safety issues highlight how small, accepted risks can accumulate into enterprise-level failure. This article explores what Boeing’s experience teaches systems engineers about risk aggregation, tolerance, culture, and governance—and why disciplined, integrated risk management is essential in complex systems.
The INCOSE International Symposium (IS) was held July 1-4, 2024, in Dublin, Ireland — a beautiful host city and country. We set up a booth in the IS Exhibit Hall, joining many commercial and academic organizations in providing attendees with valuable information, demonstrations, and networking opportunities.
INCOSE has just released the Fifth Edition of the SE Handbook back in July 2024. We took a year to develop a whole new course based on this new version. This new course is now available and for sale. Check out INCOSE SEP Exam Preparation Course [Self Paced Video version]
INCOSE has just released the Fifth Edition of the SE Handbook. What does that mean for the INCOSE SEP Knowledge Exam? What are the transition plans to retire the old Exam based on the Fourth Edition?
What’s happening with SE Scholar and Certification? We have INCOSE’s Professional Development Portal and the latest news from Courtney Wright, the Program Manager for INCOSE’s Certification Program,
What’s happening with SE Scholar? We had interviews, podcasts, and even a new advertisement campaign.
The INCOSE International Symposium is an annual gathering of the world's leading Systems Engineers. We gather in order to encourage each other within our profession but also to try to learn more about how to make System Engineering even better. While I was mainly there to hawk my SE Scholar business, I did get to meet some new and old friends.
I had the honor of doing a tutorial called Applying Systems Thinking to Industry 4.0 for 2019 IEEE International Conference on Systems, Man and Cybernetics (SMC) in Bari, Italy. It turned out was better than I expected. Read more - Download the slides, handout and see some pictures.
The INCOSE International Symposium is an annual gathering of the world leading Systems Engineers. We gather in order to encourage each other within our profession but also to try to learn more about how to make System Engineering even better. While I was mainly there to hawk my SE Scholar business, I did get to see some very interesting talks.
The phrase “The whole is greater than the sum of the parts” is well known and important to Systems Scientists and Systems Engineers alike. It’s like a short pithy definition of Emergence. And it is almost always automatically attributed to Aristotle. But what I want to know is this - Did he say it? Why did he say it? And in what context?
The INCOSE International Symposium is an annual gathering of the world leading Systems Engineers. We gather in order to encourage each other within our profession but also to try to learn more about how to make System Engineering even better. While I was mainly there to hawk my SE Scholar business, I did get to see some very interesting talks.
My daughter Stephanie graduated from MIT this year and I got to hear Sheryl Sandberg, Facebook COO and best-selling author, give the Commencement address. Her message was about the effects of Technology on the Society and the World, what I heard … We Need a Better ConOps!
We’ll be going to the INCOSE Annual International Symposium. This year it's practically in our back yard (so to speak) so we couldn't resist. Please drop by our table A7 in the exhibit hall. We have some exciting promotional items we are giving away. Come and meet our team.
On June 21, 2017, I had the privilege of speaking to the INCOSE Chesapeake Chapter on the topic of Systems Science, Systems Engineering and Systems Thinking — using the catchy title, "Zen and the Art of Systems Thinking." Here I include the slides and references for those who want to explore my talk in more detail.
How is Systems Science an oxymoron? It may come from the fact that studying Systems requires a holistic perspective whereas the fundamental concept of Science is looking at things in a reductionist manner. So how do you reconcile these two fundamentally different approaches into one discipline? Maybe the key is looking and seeing “systems’ everywhere.
Where is the Science for Systems Engineering? Every engineering discipline has its science — Electrical Engineering has its Ohm's law — Mechanical Engineering has all of Newtonian Physics — Civil Engineering has Material Science — Chemical Engineering has its periodic table of elements — and so on and so forth. But what about Systems Engineering? Where is our science?
Every year the INCOSE Chesapeake Chapter holds a Systems Engineering Professional (SEP) Gala to celebrate local INCOSE members who have gotten the INCOSE SEP Certification (ASEP, CSEP & ESEP). This is my report for the 2016 version. It’s fun to be in the company of friends, peers and colleagues of your chosen profession.
As a society we tend to stigmatize and ostracize failure. But why? It is an essential step to success! We are so focused on winning that we forget the process includes failures as well. It is one of the most important lessons from our “Lessons Learned.”
On July 27, 2015, I gave a Keynote Address to the Summer Simulation Multi-Conference for the Society for Modeling & Simulation International (SCS). I talked about micro-verse, the Incredible Hulk, the history everyday reality, Internet of Things, the Science of (or lack there-of) Systems Engineering, the concept of Emergence, and M&S. It ended with a big heartfelt thank-you to all the modelers present.
Here are my slides and references for those who want more detail on my lecture. Enjoy.
In 2014 I gave two talks dealing with the newly released INCOSE Vision 2025. I gesticulated about how difficult it is to predict the future. But System Engineers should be at the forefront of innovation and invention as we bring a holistic point of view to these complex and world spanning problems. So take your place in making a better world and a brighter future.
For those who want more detail, I have links to the videos of my lecture, my slides and all my references. Enjoy.
The INCOSE CAB organization puts on a Webinar every third Wednesday of the month. They asked me to talk to INCOSE’s SE Vision 2020. Here is the abstract, a pdf of the slides, My responses to the Q&A, and a record of the chat. Enjoy.
Several years ago I was interviewed for an American Society of Mechanical Engineers (ASME) article dealing with INCOSE certification, and the author misquoted me a few times. In this post I try to “set the record start.”

In 1909, E.M. Forster wrote a short story in which humans live in isolation and only communicate through a machine. Could this be the ConOp of our Future? A blueprint for what the New Normal will look like? Let’s take a closer look at the world of “the Machine Stops”