Human Involvement Interface Design

Good interface design is a complex engineering challenge with many dimensions. This article explores the key dimensions of Ownership and whether a Human is involved. This TensorBlue analysis is based on reporting and source material from InfoQ (https://www.infoq.com/articles/human-involvement-interface-design/).

What Happened

InfoQ Homepage Articles Ownership and Human Involvement in Interface Design

Ownership and Human Involvement in Interface Design

Before considering how to implement an interface, map out the parts of the interface and assign owners.

Understand if the interface involves a human or has to be completely automated. Human involvement is usually the only reason for using a synchronous interface.

Ownership and the presence of a human (or not) are the key drivers of any interface's nonfunctional requirements. In turn, this drives the technology choices/trade-offs interface designers and developers need to consider.

This thought process should be followed separately for each interface. You cannot put two interfaces in the same bucket without scrutinizing them.

Good interface design is a complex engineering challenge with many dimensions. In this article, I explore the key dimensions of Ownership and whether a Human is involved.

When I joined Temenos in August 2017, I came across a paper written by our Chief Enterprise Architect, John Schlesinger. The paper, written more than ten years earlier, discussed application integration. Having only a bit of experience in integration at the time, I struggled to completely understand the points made. The most striking point in that paper that I was struggling with was the "forbidden scenario," accompanied by the simple diagram shown in Figur

Implications for Product and Engineering Teams

For TensorBlue readers, the useful question is not just what happened, but how this changes product architecture, engineering priorities, AI delivery, observability, team workflows, or executive decision-making.

• Review whether this changes your AI roadmap, platform architecture, or engineering operating model.
• Identify the specific workflow, reliability, governance, or developer-productivity lesson that applies to your organization.
• Convert the lesson into a small production experiment with measurable quality, latency, cost, adoption, or risk metrics.
• Document source assumptions clearly so teams do not overgeneralize from incomplete public information.

TensorBlue Takeaway

The practical opportunity is to turn this signal into a concrete implementation decision: better AI systems, stronger product instrumentation, more reliable automation, and clearer technical governance. Teams that connect public technology shifts to their own delivery systems will move faster without adding unnecessary complexity.