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
As we move our discussions about priorities and bring the team into those discussions throughassessments into Coda I want to continue to provide an overview of the priorities we're considering for cycle 4 (June 5th - July 14th), and an opportunity to open the discussion to further feedback from our broader community.
The past cycle we have focussed our attention on operational efficiency and the reduction of operational risk for our hosts. We've also continued to work toward a new way of working on Open Collective.
Priorities for '23 Cycle 4
Some of the priorities for this cycle carry over from the previous cycle (yes, we do see that as a blotch on our record, and we'll do better to estimate)
Completing the first release for Workspace
Workspace is our new way of working on Open Collective, a project that we have been exploring since the beginning of the year. We are a landing page and a contributions page away from being able to release this experience to a broad audience #6385 .
Completing agreements
Agreements are our first attempt to help hosts reference contracts, terms, policies and agreements between hosts, collectives and users. We are a front-end away from releasing this to our own hosts #4894
Location updates to search, collective pages and discover
Two cycles ago we added location information to collectives on registration and in their settings, locations provide a way for Collectives to describe their base or area of impact, they are an essential tool for fundraisers, contributors and collectives themselves to target their support and find their peers. In order to enable this, we need to add support for these locations to the experiences that power them. #6454
Completing MFA/WebAuth Support
Two cycles ago, we enabled prototype support for YubiKey as a 2FA method. Our own hosts are finding that this method of authentication is improving efficiency, especially for those who are involve in payments. Before releasing this to the public we need to add management interfaces for users and to improve the user experience when entering a 2FA key. We could also expand our YubiKey OTP support into support for the broader WebAuth standard (which includes on-device biometric support).
In addition to these we have a few new projects to consider:
Tackling scheduled Payments for Wise accounts in the EU
A very specific project that tackles a problem that is plaguing our European hosts who are required to make batch payments and are forced to manage expenses off-platform because of lacking information about the total sum of batched payments #6787 .
Making 'platform tips' Clearer
We still receive reports that users are unclear about the recipient of platform tips in the contribution flow. We would like to make it very clear that these tips are for the operators of the platform. In parallel we would like to explore how we might make the arrangements between collective, host and platform clearer and provide more freedom for the user to support these entities instead of the collective to be supported.
Pitched in C3 this project is about creating a robust product around virtual cards which are provably successful. The project significantly improves the ability for hosts to audit and manage virtual card expenses #4312
Canned responses
A new pitch for '23 this project is about creating shared, canned responses that are accessible for hosts to use in their conversations with users, especially concerning expense payments. Our research has guided us toward a set of scenarios in which canned responses are currently users using textspanders. This project is intended to increase further the efficiency of hosts paying expenses at scale. #6788 .
Expense pipeline management
Another new pitch for this cycle is to provide a better experience for host admins paying expense as scale that provides an overview of the state of their workflows. This project allows us to explore some of the ideas presented in #5501 as we provide contextual information to users about expense state in a single experience #6790
Design System research and selection
Finally, and to encapsulate a discussion that has happened throughout the past cycle, we would like to make a decision on a component library and front end framework that we would like to use across Open Collective for new experiences and re-designs. Selecting a framework early on will enable the product-design team to begin adapting to a role that builds upon an external design system, acting as consultants as we build new experiences using it.
Contributing to this discussion
The projects selected above have been done so on the basis of strategic alignment, impact, urgency and readiness for development. As I wrote previously we are moving toward a process that allows us to build and communicate a vision to the team, and to work more purposefully toward than vision while balancing the more immediate needs of our hosts and our users.
My promise to you was to provide a space to highlight specific issues within a process that treats individual issues and feedback as an input, rather than a conclusion. This is that space.
If you feel that the above does not fit your expectations, that we've missed something vital or that we are moving in the wrong direction tell us. This is, as ever, a discussion.
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
-
As we move our discussions about priorities and bring the team into those discussions through assessments into Coda I want to continue to provide an overview of the priorities we're considering for cycle 4 (June 5th - July 14th), and an opportunity to open the discussion to further feedback from our broader community.
The past cycle we have focussed our attention on operational efficiency and the reduction of operational risk for our hosts. We've also continued to work toward a new way of working on Open Collective.
Priorities for '23 Cycle 4
Some of the priorities for this cycle carry over from the previous cycle (yes, we do see that as a blotch on our record, and we'll do better to estimate)
Completing the first release for Workspace
Workspace is our new way of working on Open Collective, a project that we have been exploring since the beginning of the year. We are a landing page and a contributions page away from being able to release this experience to a broad audience #6385 .
Completing agreements
Agreements are our first attempt to help hosts reference contracts, terms, policies and agreements between hosts, collectives and users. We are a front-end away from releasing this to our own hosts #4894
Location updates to search, collective pages and discover
Two cycles ago we added location information to collectives on registration and in their settings, locations provide a way for Collectives to describe their base or area of impact, they are an essential tool for fundraisers, contributors and collectives themselves to target their support and find their peers. In order to enable this, we need to add support for these locations to the experiences that power them. #6454
Completing MFA/WebAuth Support
Two cycles ago, we enabled prototype support for YubiKey as a 2FA method. Our own hosts are finding that this method of authentication is improving efficiency, especially for those who are involve in payments. Before releasing this to the public we need to add management interfaces for users and to improve the user experience when entering a 2FA key. We could also expand our YubiKey OTP support into support for the broader WebAuth standard (which includes on-device biometric support).
In addition to these we have a few new projects to consider:
Tackling scheduled Payments for Wise accounts in the EU
A very specific project that tackles a problem that is plaguing our European hosts who are required to make batch payments and are forced to manage expenses off-platform because of lacking information about the total sum of batched payments #6787 .
Making 'platform tips' Clearer
We still receive reports that users are unclear about the recipient of platform tips in the contribution flow. We would like to make it very clear that these tips are for the operators of the platform. In parallel we would like to explore how we might make the arrangements between collective, host and platform clearer and provide more freedom for the user to support these entities instead of the collective to be supported.
Virtual card compliance improvements
Pitched in C3 this project is about creating a robust product around virtual cards which are provably successful. The project significantly improves the ability for hosts to audit and manage virtual card expenses #4312
Canned responses
A new pitch for '23 this project is about creating shared, canned responses that are accessible for hosts to use in their conversations with users, especially concerning expense payments. Our research has guided us toward a set of scenarios in which canned responses are currently users using textspanders. This project is intended to increase further the efficiency of hosts paying expenses at scale. #6788 .
Expense pipeline management
Another new pitch for this cycle is to provide a better experience for host admins paying expense as scale that provides an overview of the state of their workflows. This project allows us to explore some of the ideas presented in #5501 as we provide contextual information to users about expense state in a single experience #6790
Design System research and selection
Finally, and to encapsulate a discussion that has happened throughout the past cycle, we would like to make a decision on a component library and front end framework that we would like to use across Open Collective for new experiences and re-designs. Selecting a framework early on will enable the product-design team to begin adapting to a role that builds upon an external design system, acting as consultants as we build new experiences using it.
Contributing to this discussion
The projects selected above have been done so on the basis of strategic alignment, impact, urgency and readiness for development. As I wrote previously we are moving toward a process that allows us to build and communicate a vision to the team, and to work more purposefully toward than vision while balancing the more immediate needs of our hosts and our users.
My promise to you was to provide a space to highlight specific issues within a process that treats individual issues and feedback as an input, rather than a conclusion. This is that space.
If you feel that the above does not fit your expectations, that we've missed something vital or that we are moving in the wrong direction tell us. This is, as ever, a discussion.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions