Cited by 7Software System Performance and ReliabilitySoftware Engineering Techniques and PracticesSoftware Engineering Research

Design Principles and Guidelines for LLM Observability: Insights from Developers

Chen, Xin, Li, Yan, Wang, Xiaoming·2025·Proceedings of the Extended Abstracts of the CHI Conference on Human Factors in Computing Systems

Abstract

The growing number of large model development tools has increased the demand for transparency and accountability. We present four developer-centric design principles for large language model (LLM) observability across the entire LLMOps lifecycle. The research focuses on improving the developer experience by integrating design principles that address the unique needs of developers at various stages of LLM development. A mixed-methods methodology was implemented consisting of three focus groups (n=10 per group) with developers across different proficiency levels, complemented by a small-scale designer rating survey. The study highlights key design principles—Design for Awareness, Monitoring, Intervention, and Operability—and their impact on developer experience factors like mental models, efficiency, visualization, and understandability. The findings reveal significant correlations between these principles and developer needs, with a particular trade-off between efficiency and mental model clarity. The study provides actionable insights for designing effective observability tools and emphasizes the importance of balancing developer control, transparency, and ease of use.

Integrity signals

Registry

Crossref · 10.1145/3706599.3719914

Cites

5 of 5 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Public procurement of AI systems has relevance for several traditional human-centred domains, including community needs, transparency, AI governance, accountability, and policy.

    “Although not commonly recognised as such, the public procurement of AI systems has relevance for several traditional human-centred domains, including community needs [84, 92, 103, 135], transparency [31, 145], AI governance [100, 107, 109, 169, 175], accountability [31, 131, 169, 175], and policy [75, 100, 103].”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Chen, X., Li, Y., & Wang, X.
Affiliations
Alibaba Group (China) (CN)
Venue
Proceedings of the Extended Abstracts of the CHI Conference on Human Factors in Computing Systems
Publisher
ACM
Published
2025-04-25
Pages
1-9
OpenAlex
W4409721409
Cited by
7
References
5
Citations by year
2026: 5 · 2025: 2
FWCI
8.69
Type
conference paper
Language
en
Open access
closed
Locations
CHI Conference Extended Abstracts on Human Factors in Computing Systems (CHI EA) (publishedVersion)
Topics
  • Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
Keywords
developer experience, design principles, transparency and accountability, mental models, visualization

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review