Apologies for my repeated connection issues and of course my obviously unorganized notes I prepared (badly) for the host-led question period…
To follow up, here are some key poiints I wanted to get across (in no particular order):
I may be beating a dead horse on this one now, but I need to reiterate that we do have set shifts for our team members, and they are posted up on a schedule that is the same week after week. Sometimes people need to make changes to this, and they coordinate this with another person who can cover that shift as well as the accountant or someone else involved with the multisig process (this will be much simpler with the transition back to some assigned management/administrative roles). The move from a set salary to an hourly wage for these duties will further bolster the personal responsibility each of us has to remain engaged and honor our commitments in this way.
I want to mention I am a bit confused by the statements about a lack of transparency on our side, as there is virtually no information we are not willing to share upon request.
I won’t pretend we are great at actively putting out a lot of information like this, but please don’t mistake that for intentional omission of any kind. A part of me thinks that it has just never really occurred to us to proactively put this information or ‘reports’ out because typically it is not something many people request, if ever, so we don’t spend the manpower on it. This should not be reason to suspect our group or its members are unaccountable or failing to deliver on our commitments.
As a corrective action to this, we are working on fully automated tracking, recording and assembly of some KPI’s (like what you can see in the graph on our prop discussion, and anything else we can grab) into an easily digestible and regularly released document.
To add to this, we began tracking these internal metrics quite a while ago, which I believe were referenced in some statements in our previous proposal.
We also considered moving to Mava, for the same reasons Luis mentioned, but decided it was simpler in the end to create our own bespoke tooling for the monitoring/reporting of support tickets and related metrics, using our existing platform.
On my end personally, I will be pushing for us to host regular “town hall” style events, maybe every 4-6 weeks, to help us stay ontop of these perceved issues or gaps in information. Even if the content of these meetings may be dry or seem like wasted time/effort, I think it may be beneficial for all parties if that platform for addressing these things were made available as a regular thing.
The inefficiency of the “pseudo-DAO” structure of the group is not something I will argue against, and for this reason implementing some style of effective and designated management structure is something we have been working on, and which will be in place for the approaching operating period.
Finally, I want to touch on the concerns about the seemingly constant “changes” from proposal to proposal. The changes over the past 3 or so funding rounds have indeed been very significant, but the reasons for those changes have always been from the angle of being more efficient and more effective in what we do, how we do it, and the amount of funding required for it.
I think we have always been forthcoming and genuine with our intentions in this way, and I believe our actions reflect this.
To summarize, I guess none of this is really concerning information, game-changing news or shocking discovery, which does not make this an “easy” decision. I could not in good conscience imply it would be a mistake placing them in this role, which is testament to our shared values, and reason for the two groups often collaborating.
At the end of the day, I feel like this is a choice of whether or not to make a sideways move that may very well neither improve nor degrade the overall quality of this community, or the support systems availble within.