Issue List to Tasks Template for Beginners: List, Prioritize, and Turn Problems Into Tasks

Project & Development

Issue List to Tasks Template for Beginners: List, Prioritize, and Turn Problems Into Tasks

The issue list to task board is a beginner-friendly template for listing team problems, setting priorities, and turning top issues into tasks with an owner and a deadline. The whiteboard has four pages - page 1 sets the scope and lists problems one sticky note at a time, page 2 groups and sorts them into an issue table with facts and causes, page 3 ranks the top four by importance and urgency, and page 4 turns them into tasks with an owner and a deadline. The task board has four columns - to do, in progress, needs review, and done - with four parent tasks matching the four pages, each with three subtasks, all starting in To Do. A common stumble with issue lists is that problems just sit on the page; this board turns each one into a one-line action with a completion condition so you can act right away. You set the owner and deadline yourself on the task board (on the free plan you can only assign tasks to yourself).

0 Likes 0 Copies Author: WeProcess
issue list issue tracking task breakdown prioritization for beginners
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode Issue List to Tasks Template for Beginners: List, Prioritize, and Turn Problems Into Tasks

Whiteboard preview

① Start here (scope, period, reviewers) ③ How you work ④ How you talk to each other ⑤ Tools and systems ⑥ Outside the team (clients, vendors) ⑦ Ground rules (read before you start) ⑧ Merge duplicates (from ③-⑥) ⑨ Split anything too big ⑩ Filter out non-issues ⑪ Issue table (what's left after ⑧-⑩,... ⑫ Importance x Urgency matrix (place ... Plan it (important, not urgent) Do now (important and urgent) Skip it (not important, not urgent) Hand off (not important, urgent) ⑬ Priority table (top 4 from Do now a... ⑭ Issue-to-task table (from the top i... ⑮ 5 steps to register on the task boa... ⑯ 3 checks after registering (mark ea... Issue List to Tas... How to use (all 4... Goal state and de... Rules and process Problems and issues Causes and insights 1/4 List out your pro... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Sort facts and ca... ↙ 3/4 Target projecte.g. Launch of the new booking site Period (from when to when)e.g. The past month (__/__-__/__) Who's reviewing it with youe.g. 3 from dev, 1 from sales, 1 facilitator ② Gap Analysis (A... Now (As-Is) e.g. Replies to inquiries take 3 days on average Gap / issue e.g. Replies are 2 days too slow. That gap is the issue Where you want to be (To-Be) e.g. Inquiries get a reply within 1 day e.g. No set order for reviews, so work stalls e.g. Two people made the same document separately Write what's hard about steps, order, or handoffs One issue per note. Post them as they come to mind e.g. No one knows who should answer a question e.g. A decision never reached someone who missed the meeting Write what's hard about asking, telling, or meeting Describe the event, not a person's name e.g. No one can tell which file is the latest e.g. No access to the shared folder, so you wait Write what's hard about tools, files, or rules Add when and what happened e.g. 5 clients ask the same question every week e.g. A vendor's quote takes a week to arrive Write what's hard about clients or vendors Mark anything unclear with a "?" Write factsInstead of "it's slow," write what happened: "the reply took 3 days" Don't blame peopleMake the subject the event, not the person. e.g. "A forgot" becomes "the update never went out" A rule the team addse.g. Everyone can write up to 5 notes without askingAdd: ____ e.g. Merged 2 notes about "can't find the latest file" into 1 Stack notes about the same event into one Write the merge count on the note's edge (e.g. "x3") The more notes on one issue, the more people it affects e.g. "sharing info is bad" becomes "decisions don't reach people" and "can't find the latest file" Split any note that bundles 2+ issues together Rewrite vague "... is bad" notes with what actually happened Each split note should still be one issue e.g. Already has a next step, "request folder access" - send it straight to board ⑭ e.g. Waiting on info, "next month's staffing is unset" - hold on board ⑩ (check __/__) Anything with a clear next step goes straight into the board ⑭ table What's left is the issue you sort on board ⑪ Fact Impact (who it af... Likely cause How to check Issue 1 e.g. Replies to inquiries take 3 days on average e.g. Clients wait and ask the same question again e.g. No one owns it, so it sits until someone notices e.g. Last month's inquiry count and reply times Issue 2 e.g. No one can tell which file is the latest e.g. Working from old files causes a redo about once a week e.g. There's no file naming rule e.g. How many redos happened Issue 3 Write the event with numbers or a count Write whose work it affects and how Guesses like "it might be..." are OK too What to check to confirm the cause Issue 4 Issue 5 3/4 Set your priorities → 4/4 4/4 Turn issues into ... 縦軸: Importance (u... High priority. Grows worse if ignored, e.g. set a file naming rule. Put it on the calendar. Urgent priority. Start this week, e.g. replies are too slow. Assign an owner and deadline right away. Not a task this round. Write "skipped for now" on board ⑪ and revisit it at the next review. Medium priority. Someone else can handle it. Pick who, then add a one-line "hand off to ____" on board ⑭ (name in the description). Issue and priority Why it's ranked here Who to consult Review date 1st e.g. Replies are slow / urgent e.g. Clients are frustrated and it's getting worse daily e.g. Sales lead e.g. In 2 weeks (__/__) 2nd e.g. Can't find the latest file / high e.g. Redos happen weekly and eat up work time e.g. Dev lead e.g. In 2 weeks (__/__) 3rd Write the issue and its priority (urgent, high) Explain why it's first, not just its quadrant Who you'll check in with when deciding When to revisit the order 4th Original issue Action (verb phrase) Completion condition Owner Deadline Task 1 e.g. Replies are slow (urgent) e.g. Assign a daily inquiry owner e.g. The rotation is shared with the team e.g. Owner: ____ e.g. __/__ Task 2 e.g. Replies are slow (urgent) e.g. Draft answers for the top 5 FAQs e.g. All 5 answers are in the shared folder e.g. Owner: ____ e.g. __/__ Task 3 e.g. Can't find the latest file (high) e.g. Set and write down a file naming rule e.g. The rule sits at the top of the folder e.g. Owner: ____ e.g. __/__ Task 4 One action per line, from one issue Use a verb phrase, such as "set" or "draft" A state anyone can recognize as done One person per line Write an actual date 1. TitleUse the action from ⑭ as the task name, as ise.g. Assign a daily inquiry owner 2. DescriptionWrite the completion condition and the original issuee.g. Done when: rotation shared / Original issue: slow replies 3. Priority, deadline, ownerCarry the priority over from ⑬, then set the deadline and ownerOn the free plan you can only assign tasks to yourself 4. Split into subtasksIf it won't fit in a week, split it into subtasks and register thosee.g. 5 answers becomes one at a time 5. Mark it registeredOn the matching row on board ⑪, write "registered"Forgetting this can get an issue registered twice Does every task use a verb-phrase name with a clear completion condition?Checked: ____ Are owner and deadline filled in for every task? (on the free plan, owner is you)Checked: ____ Sorted by priority and by deadline, does the order match ⑬?Checked: ____ → 2/4 Sort facts and ca... ↙ 3/4 Set your priorities → 4/4 Turn issues into ...
100%

Drag to move, scroll to zoom

Task board contents

To Do 16 items

List your issues
Sort facts & causes
Set priorities
Turn into tasks
Set scope & period
Define an issue
Fill the 4 boxes
Merge & split notes
Filter non-issues
Log to issue table
Plot on 2x2 grid
Pick top 4
Set reviewer & date
Write action lines
Add to task board
Check 3 points

In Progress 0 items

Needs Review 0 items

Done 0 items

← Back to templates