본문으로 건너뛰기
cccskills
무료GitHub에 공개

"grad-is-success"

"Apply the DeLone and McLean Information Systems Success Model to evaluate IS effectiveness through six interdependent dimensions. Use this skill when the user needs to assess system quality, information quality, or service quality of an IS, diagnose why users are dissatisfied, measure net benefits of a system investment, or when they ask 'how do we measure IS success', 'why are users unhappy with this system', or 'is our system delivering value'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(2)

  • SKILL.md5.0 KB
  • examples/sample_scenario.md7.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

IS Success Model (DeLone & McLean)

Overview

The DeLone and McLean IS Success Model (1992, updated 2003) identifies six interdependent dimensions of IS success: System Quality, Information Quality, Service Quality, Intention to Use/Use, User Satisfaction, and Net Benefits. These dimensions form a causal chain with feedback loops — net benefits reinforce (or undermine) subsequent use and satisfaction.

When to Use

  • Evaluating overall effectiveness of an information system
  • Diagnosing user dissatisfaction or low system utilization
  • Building a measurement framework for IS project post-implementation review
  • Comparing alternative systems across multiple quality dimensions

When NOT to Use

  • Pre-development requirements gathering (use requirements engineering methods)
  • Technology acceptance prediction before deployment (use TAM/UTAUT)
  • Measuring individual task performance only (use Task-Technology Fit)

Assumptions

IRON LAW: IS success is MULTIDIMENSIONAL — measuring only one dimension
(e.g., usage) gives an incomplete and potentially misleading picture.

Key assumptions:

  1. The six dimensions are interdependent, not independent metrics
  2. System Quality, Information Quality, and Service Quality are causally prior to Use and Satisfaction
  3. Net Benefits feed back to influence future Use and User Satisfaction
  4. Context determines which dimensions matter most — there is no universal weighting

Methodology

Step 1 — Identify the IS and stakeholder groups

Specify the information system under evaluation, its purpose, and the relevant stakeholder groups (end users, managers, IT staff, customers). Define what "net benefits" means for each group.

Step 2 — Measure quality dimensions

DimensionRepresentative Measures
System QualityReliability, response time, usability, flexibility, security
Information QualityAccuracy, completeness, timeliness, relevance, consistency
Service QualityResponsiveness, assurance, empathy of IT support (SERVQUAL-adapted)

Step 3 — Assess use and satisfaction

Measure actual Use (frequency, duration, extent) or Intention to Use (for pre-deployment). Measure User Satisfaction via overall satisfaction scales and specific feature satisfaction.

Step 4 — Evaluate net benefits and feedback loops

Quantify Net Benefits at the appropriate level (individual productivity, workgroup efficiency, organizational performance). Trace feedback: positive net benefits should increase future use and satisfaction; negative benefits signal a deterioration loop.

Output Format

## IS Success Assessment: [System Name]

### Quality Dimensions
| Dimension | Rating (1-7) | Strengths | Weaknesses |
|-----------|-------------|-----------|------------|
| System Quality | | | |
| Information Quality | | | |
| Service Quality | | | |

### Use & Satisfaction
- Usage level: [high/moderate/low] — [evidence]
- User Satisfaction: [score] — [key drivers/detractors]

### Net Benefits
| Stakeholder Group | Benefit Type | Assessment |
|-------------------|-------------|------------|
| | | |

### Feedback Loop Diagnosis
- Virtuous cycle present? [yes/no] — [evidence]
- Deterioration risks: ...

### Recommendations
1. [Target dimension]: [action]
2. ...

Gotchas

  • Usage is problematic as a success measure when system use is mandatory — satisfaction becomes the better indicator
  • The model is a taxonomy, not a causal theory — it identifies what to measure, not precise causal weights
  • Service Quality was added in the 2003 update; studies using the 1992 model omit it
  • Net Benefits replace the original "Individual Impact" and "Organizational Impact" — define the level of analysis explicitly
  • Information Quality and System Quality are highly correlated in practice; use discriminant validity checks
  • Context matters enormously — an ERP assessment weights dimensions differently than a consumer app

References

  • DeLone, W. H., & McLean, E. R. (1992). Information systems success: The quest for the dependent variable. Information Systems Research, 3(1), 60-95.
  • DeLone, W. H., & McLean, E. R. (2003). The DeLone and McLean model of information systems success: A ten-year update. Journal of Management Information Systems, 19(4), 9-30.
  • Petter, S., DeLone, W., & McLean, E. (2008). Measuring information systems success: Models, dimensions, measures, and interrelationships. European Journal of Information Systems, 17(3), 236-263.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

"Implement and select ad bidding strategies from manual CPC to automated target-CPA and target-ROAS. Use this skill when the user needs to choose a bidding strategy, set up automated bidding, or optimize bid parameters — even if they say 'what bidding strategy should I use', 'target CPA setup', or 'smart bidding configuration'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

"Optimize advertising budget allocation across campaigns using marginal returns analysis. Use this skill when the user needs to distribute budget across multiple campaigns, optimize spend pacing, or maximize overall ROAS under budget constraints — even if they say 'how to split my ad budget', 'campaign budget optimization', or 'diminishing returns on ad spend'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

"Build CTR prediction models for estimating ad click-through rates from features. Use this skill when the user needs to predict click probability, build an ad ranking model, or evaluate ad creative performance — even if they say 'predict click rate', 'ad relevance scoring', or 'which ad will get more clicks'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

"Implement Generalized Second Price auction for ad slot allocation and pricing. Use this skill when the user needs to understand search ad auctions, compute ad positions and costs-per-click, or analyze bidding dynamics — even if they say 'how does Google Ads auction work', 'ad rank calculation', or 'second price auction for ads'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

"Implement VCG mechanism for incentive-compatible ad slot allocation with truthful bidding. Use this skill when the user needs to design a truthful auction mechanism, compute externality-based payments, or understand why platforms may prefer GSP over VCG — even if they say 'truthful auction design', 'VCG payments', or 'incentive-compatible mechanism'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

"Explain blockchain fundamentals including distributed ledger architecture, consensus mechanisms, and block structure. Use this skill when the user needs to understand blockchain concepts, evaluate whether blockchain fits a use case, or design a blockchain-based solution — even if they say 'how does blockchain work', 'do I need blockchain', or 'distributed ledger'.".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

charlieviettq/awesome-agent-skill262026년 7월 20일 업데이트

charlieviettq의 스킬 모두 보기

이 스킬의 문제 신고