Where could a change make the biggest difference?
Explore the impact, the effort and the people affected. The map starts a conversation, not a decision.
What is worth exploring?
Hover or focus to explore. Click or tap to keep a pain point open.
Bigger bubbles = more different people affected in one month. Colours describe position, not incident severity. Number = record ID.
Missing scores or effort stay off the matrix. Unknown never means zero.
Check through the risk process
Potential serious risks remain visible regardless of your filters or matrix score.
Pain points in this view
The same records power the map and this list. Select a title to see its detail.
| Pain point | Business area | Impact / 100 | People / month | Fix hours | Fix cost AUD |
|---|
How the map is scored · adjust the demo
Impact combines four 1–5 ratings. Adjust the relative weights; the total is normalised automatically. These are demonstration assumptions, not agreed priorities. Blank inputs are unknown and are never filled with zero.
Reach rating from different people/month: 1–5 = 1–5, 6–15, 16–30, 31–60, 61+. Frequency: 1 annual, 2 quarterly, 3 monthly, 4 weekly, 5 daily. Service criticality and financial consequence use a locally agreed 1–5 scale. Financial consequence is separate from the estimated cost to fix.
Impact = weighted average of the required ratings × 20. If any weighted rating is missing, impact is unknown. Effort positions are proportional within each half of the chart; higher effort is capped at 160 hours for display. Future replacement is a discussion flag, never an automatic reason to postpone a fix. Filters do not change scores.
Gathering pain points · a few useful workshop questions
Ask about one concrete task at a time. Capture what people know, label estimates in the description, and leave unknown numbers blank. A ticket, an opinion and an observed task are different kinds of evidence.
- What are you trying to do, and where does it get difficult?Give the issue a short name, describe the consequence, choose its main business area and assign a unique record number.
title · description · area · id - Where did this example come from?Was it a workshop, an existing ticket or a process walkthrough? Record the reference so someone can check it.
source · source_ref - How many different people are affected in a month?Distinguish people from tickets and repeat occurrences. What time period and evidence support the estimate? If it is not known, leave it blank.
people - How often does the problem happen?Use the annual-to-daily scale in the field guide below; do not confuse frequency with the number of people.
frequency - What happens if we do not address it?Discuss the service consequence and any financial consequence separately. Agree what the provisional 1–5 ratings mean before using them for real decisions.
criticality · financial - What possible fix are we estimating?Is there a small change to try first? Estimate total working hours and cost in AUD, including checks and testing. State assumptions in the description, or leave estimates blank.
hours · cost · description - Could a future replacement address this, and what supports that view?Choose possible, no or unknown. That flag is not a commitment and does not decide whether a fix should wait.
replacement - Does this need a separate urgent or serious-risk review?Use the organisation’s normal risk route when needed. Do not let a low count or a matrix score overrule a serious concern.
risk - What is the next useful action?Write a specific check, conversation or small test. Agree an owner and follow-up date in your workshop notes; those are not fields in this simple demo.
next
Before importing, check duplicate reports of the same underlying issue, inconsistent time periods and whether estimates have been confused with facts. The tool validates format, not evidence or truth.
Spreadsheet guide · what goes in each column?
One row is one pain point. Keep all 15 column headings exactly as downloaded. The same columns work in Excel and Google Sheets; save or download as CSV UTF-8 before importing.
Three useful files: “Download example CSV” gives you the original fictional examples to use as a template. “Export all working records” keeps every current record, regardless of filters. “Export filtered view” only saves the records in your current view, so it is not a complete backup. Import replaces the current records; it does not merge files.
- id · Record number
- A unique positive whole number, such as 1 or 101. Keep it with the issue when editing so you can recognise the record. Required.
- title · Short name
- A clear, short description of the problem, for example “Repair updates need chasing”. Required.
- area · Business area
- The main team or business area affected, such as Repairs, Income or Housing. Use consistent names; these become the business-area filter. Required.
- source · How it was raised
- Use exactly
Workshop,Existing ticketorProcess walkthrough. This describes where you heard about the issue, not whether it is proven. Required. - source_ref · Where to find it
- A workshop label, date or ticket reference. Enough to trace the source without adding personal or confidential details. Required.
- description · What happens?
- Describe the task, the problem and what it means for the people involved. Avoid assuming a solution before checking the cause. Required.
- people · Different people affected per month
- Enter an actual number or best estimate, not a 1–5 score. For example, 30 means about 30 different people affected in one month, not 30 tickets. Do not count the same person more than once in that estimate. Leave blank if unknown. The demo converts the count to a reach rating: 1–5 people = 1; 6–15 = 2; 16–30 = 3; 31–60 = 4; 61 or more = 5.
- frequency · How often it happens
- Use a whole-number rating: 1 annually, 2 quarterly, 3 monthly, 4 weekly, 5 daily. This is how often the problem occurs, separate from how many people it affects. Leave blank if unknown.
- criticality · How important is the affected service?
- Use 1–5 or leave blank. Provisional demo guide: 1 = minor inconvenience; 2 = routine work slowed; 3 = important work delayed; 4 = essential service significantly disrupted; 5 = serious consequence for service delivery or obligations. The team must agree this scale before real prioritisation. Serious risks also need the separate risk flag and normal risk process.
- financial · Financial consequence of the problem
- Use 1–5 or leave blank. Provisional demo guide: 1 = negligible; 2 = small avoidable cost; 3 = material cost to a team; 4 = substantial wider cost; 5 = major financial consequence. These are relative labels, not agreed dollar thresholds. Agree monetary bands with the team. This is the impact of leaving the issue unresolved, not the cost of fixing it.
- hours · Estimated effort to fix
- Total working hours for the proposed fix, not elapsed days or waiting time. Include the work needed to check, implement and test it. For example, 16 means about 16 hours of work. Leave blank until there is a useful estimate.
- cost · Estimated cost to fix
- A number in Australian dollars, without a dollar sign or thousands separators: for example
1800. Use the same costing basis across records. Leave blank if unknown; do not enter zero merely because there is no estimate. - replacement · Could a future replacement address this?
- Use exactly
possible,noorunknown. “Possible” is a hypothesis to check, not a promise or an automatic reason to wait. Required. - risk · Needs a separate risk review?
- Use
yesto flag a potential serious risk; it stays visible even when filters exclude it. Usenowhen no such flag has been identified, not as a certification that there is no risk. If unsure, review it with the relevant owner rather than relying on the score. Required. - next · Useful next step
- A short practical action: check a ticket, observe the task or test a small change. This helps turn the picture into a conversation about what to do next. Required.
How the sidebar uses your spreadsheet
Where it came from joins source and source_ref. Future replacement turns the fixed code into a plain-English label: possible → “May be addressed by a future replacement”; no → “Not expected to be addressed”; unknown → “Future replacement impact unknown”. What drives the impact? shows the four input ratings; reach is calculated from people, and the other three come directly from the spreadsheet. The weighted impact number is calculated by the formula above.
A useful next step shows exactly what you put in next. It is not AI-generated. Titles, descriptions, sources and estimates also come from the records. The headings, explanatory labels and cautionary notes are fixed interface text. Import validation rejects missing required values or invalid ratings; the tool does not invent missing information or assess whether a statement is true.
Unknown is not zero
Leave unknown numerical values blank. A blank weighted impact input or blank fix-hours estimate keeps an issue off the matrix. Missing cost does not prevent mapping; it is displayed as unknown. The import checks the required fields and rating ranges before replacing anything.
How the scoring controls work
The four sliders above set relative importance, not percentages you must make add to 100. Higher values give a factor more weight; zero excludes it. The app normalises the total and calculates impact out of 100. If all weights are zero, impact is unknown. The two thresholds determine which side of the matrix each record sits on. They do not change the source records.
Exports contain only the 15 record fields, not calculated scores or settings. Import recalculates the map using the weights and thresholds currently on this page. It does not restore earlier scoring settings. Refresh restores the demo and its default settings, so export any working records you want to keep and note down any chosen settings separately.