AIYING in Practice — Team Task Mapper

AIYING in Practice — Team Task Mapper

1-Page Printable Worksheet (PM · Design · Engineering)

Purpose:

Turn a messy team project into focused momentum by assigning thinking ownership before task ownership.

---

SECTION 1 — Outcome (Single Owner)

(Fill this first. Don’t proceed if this is fuzzy.)

Outcome we are trying to achieve:

---

Decision this work must enable:

---

Outcome owner (one person):
☐ PM ☐ Other: ____________________

🔒 Rule: One outcome = one owner.

---

SECTION 2 — Human Questions (Core of Task Mapper)

(Tasks come later. Questions come first.)

PM — owns these questions

• What problem are we solving?

• For whom?

• Why now?

• What is explicitly out of scope?

✍️ Key PM clarifications:

---

---

Design — owns these questions

• How should this work for the user?

• What behaviours are we optimising for?

• What trade-offs affect usability or adoption?

✍️ Key Design clarifications:

---

---

Engineering — owns these questions

• What is feasible now?

• What risks or constraints matter?

• What assumptions are unsafe?

✍️ Key Engineering clarifications:

---

🔑 Rule: Questions don’t bounce. Ownership is explicit.

---

SECTION 3 — Task Mapping (Only After Questions)

(Each task must answer a question.)

Task	Which question does it answer?	Owner (Human / AI)

❌ If a task doesn’t clearly answer a question → remove it.

---

SECTION 4 — AI Assist (Inside Roles)

PM uses AI for:
☐ Framing options ☐ Summaries ☐ Comparisons

Design uses AI for:
☐ Flow variants ☐ Copy drafts ☐ Explorations

Engineering uses AI for:
☐ Edge cases ☐ Approach analysis ☐ Risk surfacing

🔁 Rule: AI assists within roles, not across roles.

---

SECTION 5 — Explicit “Not Doing” List

(This prevents scope creep.)

We are not doing:

---

---

---

AIYING Insight 

Clarity sets direction.

Task mapping restores momentum.

First decide who answers which questions.

Then let tasks follow.