Behind every baseline, milestone gate, and SysML model lies an unwritten network of status preservation, informal trades, and tactical compromises. We are investigating the micro-sociological friction that normative standards overlook. Our goal is to give Systems Engineers a Guideline for the Human Aspect. Support our research by sharing your stories.
Status report is always green... until the sudden crash.
We can't decide as long as there is a 1% residual risk.
Engineering units quietly build unapproved tools and shadow pipelines.
Clear workshop consensus mysteriously evaporates overnight.
Three team members whisper: "We'll never pull this off anyway."
12 concurrent priority initiatives, each staffed with half an engineer.
Critical interface boundaries where nobody assumes ownership.
"We urgently need to address X" — and the topic is perpetually avoided.
"I'd better call them directly off the record instead of logging it formally."
Typical organisational challenges. Do you know specific examples? This is what we are interested in!
You choose the level of involvement and your boundary of comfort. No organizational exposure, no technical disclosure.
Describe a real sociotechnical interaction (e.g. a milestone review, an unwritten trade-off, or cross-discipline friction) in your own words using our structured prompt. No calls or scheduling required.
A confidential 1-on-1 interview exploring backstage coordination, "saving face", informal compromises, and metrics distortion. The full verbatim transcript is returned to you for redacting prior to analysis.
Passive observation of engineering synchronization rituals, architecture boards, or micro-analysis of recorded retrospective meetings. Strictly subject to bilateral non-disclosure and research agreements.
Delivered foundational presentation on cognitive resistance, neurobiology, and sociological interfaces in Linköping.
Scientific paper submission and presentation on architecting human-system interfaces across disciplinary boundaries.
Crowdsourcing encrypted voice notes and qualitative narratives. Joint data sessions grounding Goffman's dramaturgy.
Peer-reviewed symposium paper defending empirical findings against CFS-C2-03, CFS-C4-01, and CFS-C6-04 priorities.
Field testing backstage interface heuristics and watermelon risk protocols within live engineering programs at CAB member enterprises.
Not a rigid standard, but a territory map focusing on CFS-C2-03, CFS-C4-01, and CFS-C6-04: practical guidelines and heuristics for navigating informal barriers, status rituals, and cross-discipline interface friction.
Bridging enterprise systems architecture, micro-sociology, and industrial heritage.