{"id":15198,"date":"2026-09-24T06:37:47","date_gmt":"2026-09-24T06:37:47","guid":{"rendered":"https:\/\/incose.nl\/?page_id=15198"},"modified":"2026-09-24T06:40:00","modified_gmt":"2026-09-24T06:40:00","slug":"rob-sanders","status":"publish","type":"page","link":"https:\/\/incose.nl\/en\/the-dutch-systems-engineering-days-2026\/rob-sanders\/","title":{"rendered":"Rob Sanders"},"content":{"rendered":"
\"\"<\/a><\/div><\/div><\/div><\/div><\/div><\/section>
\"\"<\/a><\/div>

Rob Sanders
\n<\/h2>\n<\/div><\/div>

Trainer | Coach | Systems Architect | Bridging system architecture and human behavior in high-tech teams
\n<\/p>\n<\/div><\/div><\/div><\/div>

<\/div>

Systems Engineering the Soft Side: A Structural Approach to
\nHuman Alignment in Engineering Teams
\n<\/h4>\n<\/div><\/div>
<\/div>

Bio.
\n<\/strong>Bio: Rob Sanders spent 30 years as a systems architect in
\nhigh-tech engineering before becoming a certified NLP
\nMaster Trainer. He works with engineering teams on
\ncommunication and alignment problems that are at the heart
\nof most technical bottlenecks.<\/p>\n<\/div><\/div>

<\/div>

Abstract.<\/strong><\/p>\n

Most engineering teams have a problem they cannot find in
\nany technical document.<\/p>\n

Decisions get made in meetings but never actually stick.
\nTwo teams that build to the same spec often still end up
\nwith parts that do not fit together. The best engineer in
\nthe room stays quiet. The same discussion happens again
\nnext week.<\/p>\n

The technical work is fine. The people are capable. So
\nwhere is the problem?
\nIt is in the space between people. Who owns this decision?
\nWhat did we actually agree upon? What is everyone assuming
\nbut nobody saying out loud? These are engineering problems.
\nThey just happen to be about people rather than about
\nsystems.
\nThis workshop treats them exactly that way.<\/p>\n

Participants work through three structured steps, using
\ntools and logic that engineers already know.<\/p>\n

Step 1 starts with two short exercises that show, in less
\nthan ten minutes, why two people in the same meeting walk
\nout with a different picture of what was discussed. Not
\nbecause one of them was not paying attention. Because every
\nperson filters information differently. Once you see how
\nthat works, you can start asking better questions about
\nyour own team: where are we assuming alignment that we have
\nnever actually verified?<\/p>\n

Step 2 uses a modified FMEA approach to find the real cause
\nof a recurring team problem. Not the surface cause, the one
\nthat gets discussed in the meeting, but the cause
\nunderneath it. Participants will work on one real problem
\nfrom their own work and trace it step by step. Examples
\nfrom engineering practice show how this works before
\nparticipants try it themselves.<\/p>\n

Step 3 asks each participant to design one concrete change.
\nNot a complete plan to communicate better, but one simple
\nstep they can implement the next week. Written in the same
\nformat engineers use for any other change proposal: what
\nchanges, from what to what, why, and how will you know it
\nworked.<\/p>\n

Each participant leaves with three things: a clearer
\npicture of where they (or their team) are running on
\nunspoken agreements, a root cause analysis of one real
\nproblem, and one change they can actually implement next
\nweek.<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/section>\n","protected":false},"excerpt":{"rendered":"Rob Sanders Trainer | Coach | Systems Architect | Bridging system architecture and human behavior in high-tech teams Systems Engineering the Soft Side: A Structural Approach to Human Alignment in Engineering Teams Bio. Bio: Rob Sanders spent 30 years as a systems architect in high-tech engineering before becoming a certified NLP Master Trainer. He works...","protected":false},"author":402,"featured_media":0,"parent":13872,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-15198","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/incose.nl\/en\/wp-json\/wp\/v2\/pages\/15198","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/incose.nl\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/incose.nl\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/incose.nl\/en\/wp-json\/wp\/v2\/users\/402"}],"replies":[{"embeddable":true,"href":"https:\/\/incose.nl\/en\/wp-json\/wp\/v2\/comments?post=15198"}],"version-history":[{"count":1,"href":"https:\/\/incose.nl\/en\/wp-json\/wp\/v2\/pages\/15198\/revisions"}],"predecessor-version":[{"id":15201,"href":"https:\/\/incose.nl\/en\/wp-json\/wp\/v2\/pages\/15198\/revisions\/15201"}],"up":[{"embeddable":true,"href":"https:\/\/incose.nl\/en\/wp-json\/wp\/v2\/pages\/13872"}],"wp:attachment":[{"href":"https:\/\/incose.nl\/en\/wp-json\/wp\/v2\/media?parent=15198"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}