Lesson 3. Task Scoring#
Why This Matters#
Not all tasks are equally valuable. Scoring helps choose where to start.
Key Idea#
Scoring = evaluation on "impact / complexity / risk" axes
Start with tasks that have high impact and low complexity.
Evaluation Axes#
1. Impact (benefit)
What we evaluate:
- time savings
- cost savings
- conversion/quality improvement
Scale:
- High impact (3): save 10+ hours/week or revenue growth of 15%+
- Medium impact (2): save 5–10 hours/week or revenue growth of 5–15%
- Low impact (1): save up to 5 hours/week or revenue growth up to 5%
2. Complexity (effort)
What we evaluate:
- how long development will take
- whether integrations are needed
- whether ready data exists (knowledge base)
Scale:
- Low complexity (1): 1–2 days, no integrations, ready data available
- Medium complexity (2): 3–7 days, simple integrations
- High complexity (3): 2+ weeks, complex integrations, need to collect data
3. Risk (error impact)
What we evaluate:
- how critical errors are
- data sensitivity
- impact on customers
Scale:
- Low risk (1): errors not critical, fallback plan exists
- Medium risk (2): errors noticeable but not critical
- High risk (3): errors critical (money, reputation, data)
4. Data Availability
What we evaluate:
- whether ready data exists for the agent
- how easy it is to obtain
Scale:
- High availability (3): data exists and is ready
- Medium availability (2): data exists but needs structuring
- Low availability (1): no data, need to collect from scratch
Scoring Matrix#
| Task | Impact (1–3) | Complexity (1–3) | Risk (1–3) | Data (1–3) | Total | Priority |
|---|---|---|---|---|---|---|
| FAQ bot | 3 | 1 | 1 | 3 | 4 | High |
| Lead qualification | 3 | 2 | 2 | 2 | 1 | Medium |
| Booking agent | 2 | 1 | 2 | 3 | 2 | Medium |
| Review analysis | 2 | 2 | 1 | 1 | 0 | Low |
Formula:
Priority = Impact + Data - Complexity - Risk
Interpretation:
- 3+: high priority, start here
- 1–2: medium priority, do after the first ones
- 0 and below: low priority, leave for later
Scoring Example#
Task 1: FAQ bot for online store
- Impact: 3 (saves 15 hours/week)
- Complexity: 1 (2 days, FAQ exists)
- Risk: 1 (errors not critical)
- Data: 3 (FAQ ready)
- Total: 3 + 3 - 1 - 1 = 4 → High priority
Task 2: Proposal generation agent
- Impact: 3 (saves 10 hours/week)
- Complexity: 3 (CRM integration needed, templates)
- Risk: 2 (pricing errors noticeable)
- Data: 2 (templates exist but need structuring)
- Total: 3 + 2 - 3 - 2 = 0 → Low priority (too complex to start)
Task 3: Service booking agent
- Impact: 2 (saves 8 hours/week)
- Complexity: 1 (3 days, simple spreadsheet integration)
- Risk: 2 (booking errors noticeable)
- Data: 3 (service list ready)
- Total: 2 + 3 - 1 - 2 = 2 → Medium priority
Conclusion: start with FAQ bot, then build booking agent, leave proposal agent for later.