You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main focus for this cycle is improving operational efficiency and reducing operational risk for our host organisations.
We're taking a practical approach to improve the core experiences that hosts engage with most frequently (paying expenses) and a flexible approach to policy creation and enforcement, which will enable hosts to operate services like virtual card issuing, cash assistance, and grantmaking in a way that lets them set the boundaries and processes.
Alongside this, we will continue to explore new ways of working on Open Collective, completing work on our workspace concept and further developing our onboarding process with the workspace as a starting point. If there's time we will begin testing our new profile pages with users and continue to improve our platform support, guiding users to the right information and support teams when contacting us.
Improvements to Expense Payment Processing
Expense payments UI
We will improve the expenses payments dashboard, ensuring that the right information is presented to admins, enabling them to process expenses more quickly.
We will expand our anti-fraud warnings for hosts into a broader validator concept that builds confidence in admins while clearly labelling expenses that need a little more interrogation.
We will make re-requesting approval an explicit action and introduce a new 'hold' status for admins to indicate to others that an expense is being interrogated.
We will enable host admins to attach notes to Collectives and Individuals that can be used to indicate policies, link to agreements and otherwise support other admins when making a decision about paying an expense.
We will improve the ability for hosts to audit their virtual card usage, enabling them to filter issued cards by state, volume, and whether receipts are missing.
We will provide direct access to virtual card settings with their provider, enabling hosts to edit restrictions as required through their provider directly.
We will enable hosts to automatically pause cards that are no longer being used.
We will warn host admins when assigning or issuing a new card if a Collective already has a card assigned or has missing receipts.
We will enable both hosts and users to view and filter transactions for a card that they have assigned (or been assigned) so that they can track spending and comply with policies more easily.
We will complete the workspace concept developed last cycle, adding the necessary core elements so that it can be beta tested with a wider selection of users on the platform.
If there's time we will implement the designs for collective profile pages, to be able to better test them with users ahead of us, beginning to update the experience for users engaging with Collectives on the platform.
We'll continue to address platform support by better serving users' most common queries with documentation and routing support requests direct to the correct team, with the information that's relevant to the request.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
2023 Cycle 3
The main focus for this cycle is improving operational efficiency and reducing operational risk for our host organisations.
We're taking a practical approach to improve the core experiences that hosts engage with most frequently (paying expenses) and a flexible approach to policy creation and enforcement, which will enable hosts to operate services like virtual card issuing, cash assistance, and grantmaking in a way that lets them set the boundaries and processes.
Alongside this, we will continue to explore new ways of working on Open Collective, completing work on our workspace concept and further developing our onboarding process with the workspace as a starting point. If there's time we will begin testing our new profile pages with users and continue to improve our platform support, guiding users to the right information and support teams when contacting us.
Improvements to Expense Payment Processing
Expense payments UI
We will improve the expenses payments dashboard, ensuring that the right information is presented to admins, enabling them to process expenses more quickly.
Improved expense validators
We will expand our anti-fraud warnings for hosts into a broader validator concept that builds confidence in admins while clearly labelling expenses that need a little more interrogation.
Refining expense status and approval flows
We will make re-requesting approval an explicit action and introduce a new 'hold' status for admins to indicate to others that an expense is being interrogated.
Notes, links and agreements
We will enable host admins to attach notes to Collectives and Individuals that can be used to indicate policies, link to agreements and otherwise support other admins when making a decision about paying an expense.
Building a more robust Virtual Cards product
We will improve the ability for hosts to audit their virtual card usage, enabling them to filter issued cards by state, volume, and whether receipts are missing.
We will provide direct access to virtual card settings with their provider, enabling hosts to edit restrictions as required through their provider directly.
We will enable hosts to automatically pause cards that are no longer being used.
We will warn host admins when assigning or issuing a new card if a Collective already has a card assigned or has missing receipts.
We will enable both hosts and users to view and filter transactions for a card that they have assigned (or been assigned) so that they can track spending and comply with policies more easily.
Exploring new ways of working on Open Collective
Completing our workspace concept
We will complete the workspace concept developed last cycle, adding the necessary core elements so that it can be beta tested with a wider selection of users on the platform.
Expanding our vision for onboarding to include the workspace
This is a purely product design effort at this point, to be able to follow on from the workspace project that we will have completed this cycle.
Testing our new Collective profile pages
If there's time we will implement the designs for collective profile pages, to be able to better test them with users ahead of us, beginning to update the experience for users engaging with Collectives on the platform.
Addressing the 'top-of-funnel' for user support
We'll continue to address platform support by better serving users' most common queries with documentation and routing support requests direct to the correct team, with the information that's relevant to the request.
Beta Was this translation helpful? Give feedback.
All reactions