Feature idea: Card mass as a visual signal #2207
JD-Shipit
started this conversation in
Ideas and Issue Triage
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Fizzy users,
I’ve been thinking about an idea that fits what Fizzy does best:
You shouldn’t have to dig for context.
The board itself should tell you how things stand at a glance.
Right now there’s one important thing that’s hard to see without clicking into cards:
the relative weight or impact of each card.
A board often contains a mix of big rocks and small pebbles.
On a house-build board, “Build the rough structure” and “Connect the taps” are both valid cards, but they are not the same kind of work and they do not have the same impact.
I am not necessarily talking about “size” in terms of time spent, estimates, or S/M/L labels.
Those can be proxies, and I have even suggested time as one option in different topic.
What I really mean is impact or importance, the density of a card.
Example
A tricky bug fix might take the same amount of time as a small new feature.
But the bug affects only a handful of clients, while the feature helps many.
Same “size” by time, completely different impact for the product.
The problem I am trying to solve
When everything looks identical on the board, it is easy to:
The core problem
We want a lightweight visual signal that communicates card “weight” at a glance,
so the board reads like a landscape, not a list of equal-looking items.
This is not about process, reporting, or turning Fizzy into an estimation system.
It is about board-level clarity, and it has to be visual and obvious on first glance.
Two ideas on how to approach it
I ended up with two concepts that solve the same problem in different ways.
Direction 1: Mass and Gravity (a more experimental approach)
This direction is inspired by physics.
Think in terms of mass and density:
Cards do not get bigger.
Instead, the board subtly reacts to their mass.
States
Low
Normal work, no special gravitational effect.
The card looks exactly as it does today.
If all cards are Low, the board is unchanged.
High
High mass, big impact, noticeable weight.
The card itself stays flat and unchanged.
The immediate space around it subtly compresses.
A gentle, symmetrical gradient, barely noticeable unless you are scanning.
The card feels heavy, not flashy.
Singularity
A card so important that it bends the local space of the board.
The card slightly collapses inward.
Its edges are gently curved inward.
The surrounding space visually pulls toward its center.
It communicates: “This is the center of gravity right now.”
The signal is unmistakable.
Strengths
Risks
Few rough visual concepts:
Direction 2: Card Thickness (a more conservative approach)
This direction is more literal and grounded.
Think of cards as physical objects:
They all have the same footprint.
They live in the same grid.
They do not move or reorder anything.
They simply carry more visual weight.
States
Pebble (default)
Looks exactly like today’s card.
No added visual weight.
Rock
A subtle base appears under the card.
Feels like a thicker piece of material.
Clearly heavier, but still calm.
Boulder
A more pronounced base.
Feels solid and substantial.
Instantly distinguishable at a glance.
Thicker means more impactful.
In my opinion, this is the more conservative approach, but also very effective.
It communicates the information immediately and adds meaning without asking the user to look for it.
Strengths
Risks
Few rough visual concepts:


What “good” looks like (for both directions)
Who benefits
Teams
Individuals
Wrapping up
I do not have the perfect answer yet for how this should look, but I think the problem is worth solving.
Done well, either of these directions could make Fizzy feel even more unique:
a board you can truly read without clicking around.
If you would like, I am happy to explore either direction further
or help narrow this down.
Thanks for considering this.
Beta Was this translation helpful? Give feedback.
All reactions