retro.tools
retro.tools copied to clipboard
Cards hidden until 'voting mode' is enabled
If you're not the author of the card, you shouldn't be able to see the cards other users write until 'voting mode' has commenced.
This helps limit groupthink. If you see others writing about a specific topic, it could steer your thought process toward their issue prematurely and limit the topic diversity of the session.
It would be great to have a setting (similar to the 'voting allowed' selection) to hide the text of cards you haven't authored.
I don't think you need to take this wildly far. Simple is better.
Good idea, I'll see if I can work on it this week.
Nice! If they cards are there, but the text is hidden, that could also accomplish this goal.
I think users should be able to see their own cards/text
I'm undecided on how to approach this, here are a few options in order of easiest to hardest:
- Always obscure cards when voting is disallowed.
- This'll mean that the current style of adding cards visible to everyone won't be possible.
- Seperate
voting allowedandobscure cardstoggles that the board owner can flip.- A downside to this is that voting could be allowed at the same time that cards are obscured, which is a bit weird.
- A 3-way switch for
voting allowed,voting disallowedandvoting disallowed + cards obscured- This way we avoid the strange state and allow retro runners to use either style.
After all the cards are revealed, there're likely to be duplicates where people added the same thing. But there's currently no ability to merge cards, which would be an annoyance.
Option 2 seems sufficient.
Agreed that it is a bit weird, but it'll be an obvious state based on the menu items selected.
Agreed on the potential for dupes—merging would be something that would make this feature shine more, but I don't think it is a gamechanger, all things considered.
What if you had a concept of 'card groups' rather than attempting to merge cards? There could be a nullable property on the cards like a group_id
I am sort of thinking of FigJam 'sections'

I think option 2 would be fine for now as well. I'll go ahead and do that :+1:
The duplicate problem can be addressed seperately and tracked here: #3