Skip to content
JiraVision
Find your fit
Answers stay in your browser

Six questions. Show the maths. Reach an honest verdict.

Half the teams that ask for a demo don't need one. This quiz scores your situation against what JiraVision actually ships — including the parts we refuse to build — and every point in the score is visible next to the answer that earned it.

  • Six questions, ~90 seconds
  • Every point value published on this page
  • Two honest veto answers — including one where we refuse the sale

The quiz

Six questions, six answers deep

Pick an option to continue. Your progress saves in this browser only — nothing is submitted anywhere.

0 of 6 answered0/18 pts so far

Question 1 / 6

How big is the team you run?

One delivery team, not the whole org.

The problem

Why we ship a quiz that can say no

Vendor quizzes exist to flatter you into a demo call. Ours exists to catch the mismatch before a pilot does — a bad fit hurts both sides for a year.

01

Shelfware is the real cost

The expensive outcome isn't a lost trial — it's a team that adopts a planning layer with no pain to solve, churns in six months, and distrusts every tool that follows.

02

Our limits are public

We sit on Jira, never copy attachments, and refuse per-person rankings. If any of that is disqualifying, the quiz surfaces it in ninety seconds instead of a month of pilots.

03

A verdict you can audit

The scoring table below this quiz is the whole model: 18 possible points, two vetoes, three bands. Unit-tested, deterministic, and readable in the source.

The maths

How the verdict is computed

  1. Step 1

    Each option carries a point value

    Every answer maps to 0–3 points toward “JiraVision solves problems you actually have”. The full weight table is printed below the quiz — no hidden scoring.

  2. Step 2

    Two answers can veto the score

    Per-person rankings triggers our standing refusal regardless of points. “Nothing hurts right now” caps the verdict at “not yet”, because tooling without pain is shelfware.

  3. Step 3

    Points set the band, caveats set the conditions

    13+ of 18 is a strong fit, 9–12 is fit-with-conditions, 8 or less probably isn't a fit. Answers like team size or attachment scope never veto — they add caveats to the result instead.

  4. Step 4

    The CTA adapts, the maths doesn't

    Your “what hurts” answer selects which product page we recommend. Reload the quiz with different answers and the same rules apply — it's deterministic by contract, and unit-tested.

No hidden scoring

Every point, printed before you answer

Scores run 0–18. The verdict bands and vetoes below use exactly these numbers — nothing else is measured, weighted, or tuned by a model.

Fit quiz scoring weights: every question, option and its point value
QuestionAnswerPtsWhy
How big is the team you run?5–10 people+2Small teams get the planning signals, but seat pricing is built for 5+.
11–30 people+3The capacity model and wellbeing pulses are tuned for one-to-a-few squads.
31–75 people+3Multiple boards with cross-team overload is exactly the mess we plan for.
76+ people+2Works, but expect a security and procurement conversation first (Enterprise).
Where does your delivery work live today?Jira — we run it already+3Zero data move: Jira stays authoritative and we read from it.
Trello or Notion+2A clean import, but you'd need a Jira site underneath — that's the honest part.
Asana or Linear+2Mappable fields and statuses, with a real migration phase plan.
Something else (or nothing yet)+0If it isn't Jira-compatible, the base tenancy comes first — we won't pretend otherwise.
What does sprint planning feel like right now?Sprints regularly derail mid-flight+3Over-commitment detection is the first thing that pays for itself.
It works, but scope drifts every cycle+3Evidence-based replanning beats tribal memory about who's swamped.
Smooth, but slower than it should be+2Estimation churn is where the AI draft + approval loop helps most.
Smooth and fast+0If planning is healthy, another tool is probably not your missing piece.
What hurts most, week to week?Estimation arguments and surprise over-commitment+3AI Scrum Master drafts sprints against measured capacity; a human approves.
After-hours creep and quiet burnout+3Team Wellbeing Radar surfaces the pattern before it shows up in attrition.
Invisible work and unfair load distribution+3The Equity Explorer is built for exactly this conversation.
Good work goes unnoticed+2Gamification rewards recognised behaviours — with guardrails against scoreboards.
Honestly? Nothing right now+0We'd rather talk you out of buying than sell you a dashboard.
How much visibility into people does leadership want?Team-level aggregates, nothing personal+3That is precisely the design line we ship on.
Some individual detail, with context and consent+2Possible — opt-in recognition and self-reported pulses only, never activity surveillance.
Per-person productivity rankings+0We refuse to build this, full stop — no configuration unlocks it.
Fewer dashboards, not more+1Respectable. Our signal-dense views would still need to earn their place.
What about your data history?Starting fresh — no legacy to carry+3Simplest possible onboarding; day one, no import.
Some history we want readable, not moved+2With Jira underneath, history stays where it is and we read it as-is.
A mountain of attachments we'd need copied+1JiraVision never copies attachments. That scope needs a written agreement before you commit.

What a result means

The five verdicts, in plain words

Not a fit — by refusal
You need per-person rankings. We won't build them. This never changes with plan or pricing.
Not yet
Nothing hurts. We talk you out of it and keep the door open.
Strong fit
13+ points, no vetoes. Trial it on one real sprint before deciding anything bigger.
Fit — with conditions
9–12 points. The mismatch is a caveat (scale, base tooling, attachments), not a dealbreaker.
Probably not a fit
8 points or less. A layer here would add ceremony, not relief.

Straight talk

The quiz is just this section, pre-filled

Works well if

  • Teams running Scrum or hybrid cycles in Jira
  • Leads who want planning arguments settled with evidence
  • Teams recovering from a bad over-commitment streak
  • Orgs that want a recognition map, not a scoreboard

Not for teams that

  • Managers wanting per-person activity reports (we won't build them)
  • Teams needing attachments moved between tools
  • Non-Jira boards today without a plan for the Jira base
  • Anyone expecting auto-pilot sprint management — approval stays human

Who should bother

Three profiles that usually get a useful result

Engineering leads

You feel over-commitment first. The quiz scores whether our planning loop matches how your sprints actually derail.

  • Sprint sandbox verdict
  • Capacity caveats up front

People ops / skip-levels

You see burnout before the retro does. We check whether team-level signals are enough for your leadership's appetite.

  • Wellbeing-pulse framing
  • The rankings veto, early

Tooling owners

You're evaluating a move. The base-tenancy and attachment caveats decide your verdict more than any score.

  • Migration honesty
  • Comparison links when it's 'not us'

Your answers stay in this browser tab.

The quiz has no account, no submission, and no analytics event with your answers in it. Progress persists in localStorage only, so you can close the tab and come back; restart clears it. If you take a screenshot of a verdict and argue with it internally, that part is on you.

The never-list

Answers the quiz can't negotiate

Some verdict conditions aren't score inputs — they're standing decisions. If your requirement lives here, no answer changes the result.

  • Per-person productivity rankings or activity surveillance.
  • Copying your attachments out of any tool — Jira stays the store.
  • Auto-applying AI sprint plans without a human approving them.
  • Selling, shipping or “anonymising” individual-level data upward.
The refusal list on the public roadmap

FAQ

Questions about the quiz itself

All product questions

Take the verdict to a human.

Quiz results are a starting point, not a contract. Bring the screenshot to the contact form and we'll respond to the caveats specifically — including the ones where our answer is no.