Determine UX focus for coming months

[RomijnHumanoids]

Due to recent changes in OpenKAT planning, it's time to determine focus for UX in the coming months, as well as give priority and reach consensus within the team & stakeholders.

This is an 'in progress' ticket that will be complemented/adjusted until status is changed to 'for review'.

Points to work on for now:

• 1.1 (FOR REVIEW) Design flow for Design: Copy a dashboard to another organisation #4532
• 1.2 (IN PROGRESS) Collect user needs/stories for 'uploading raw file' (to improve the UX, maybe divide in other small flows) Uploading multi reports need to be assigned to what objects #4166
• 1.3 Help with Fix styling issues #4584

Ideas as direct follow up:

• 2.1 Find a solution for organisation dropdown / design a page showing all organisations.
• 2.2 (IN PROGRESS) Design: improve 'add new organisation' #4634 Improve add organisation flow; instantly set indemnification & accept user clearance level (this is now a bit of a scavenger hunt)
• 2.4 (Check accessibility QA -> if yes, pass to code QA) Help with implementing toggle feat: toggle #3822
• 2.5 (FOR REVIEW:) Design: rethink add ooi flow #4137
• 2.6 (no ticket yet) Design a way for settings in OpenKAT per object, alternative to question ooi's. (depends on technical solutions on the long term, but design can give inspiration).

Longer term / broader scope UX questions (dare to dream)

• 3.1 Review KAT as a whole, find opportunities to simplify / go back to the core.
• 3.2 What are the biggest pain points of stakeholders right now? If there would be no limitations, what would be needed for them to use OpenKAT as their main cybersecurity tool?
• 3.3 Can plugins run on a subset of objects instead of always on all objects?
• 3.4 Can we enable plugins across organisations instead of per organisation?

Not relevant for now:

• 4.3 (No new design needed yet) Is showing findings for all organisations on the findings dashboards (via reports) satisfying user needs? Or required to be live data instead of reports? (this could be possible without current backend limitations, with XTDB2 if I'm correct)
• 4.7 (New feature, Don't touch this yet) (FOR REVIEW:) Design flow for importing/exporting reports/objects. #3890 Maybe this will function differently? Or is export boefjes still on the roadmap?
• 4.8 (New feature, FOR REVIEW:) As a user I want to see what's new since last checked (e.g. 24h) #4203
• 4.9 (New feature, FOR REVIEW:) As an admin, I want to see a log of operations by members #4202

[RomijnHumanoids]

Although third category; longer term items are not yet detailed, this ticket will go for review to look if I missed something. After that, I can still narrow things down like 3.1 which can be really broad.