[bisq-network/proposals] Add Detailed BSQ Issuance Information to Cycle Report (#150)

[Christoph Atteneder]

> As I commented at [bisq-network/compensation#417 (comment)](https://github.com/bisq-network/compensation/issues/417#issuecomment-565268347) I think we are lacking at the moment management of efforts, targets and achieved goals. To track expenses by category would be a good first start. But I think it will require more and it might be a bit challenging how to do that in a non-hierarchical DAO-compatible way. Any good ideas are very welcome!

In a centralized approach this would be the responsibility of the product owner. In our case one for each of following products: website, docs and client. As we don't want to push for such a role which would be a newly introduced centralized entity - how can we do it instead?

- Making everyone accountable for their own work

This kind of accountability is unfortunately very hard to do as we don't have lots of key metrics at hand and we can't do it in an objective way right now.

This boils down to the question of what means success for each of these contributions?

If we take a super high-level ROI approach, it would mean:
-  Every contribution is paid with newly issued BSQ so success means if it increases the amount of BSQ burnt

ROI calculations work well for continuous improvement of existing products if they would be in place, but not for highly experimental new ideas/projects.

Using total numbers, which are partly available, won't work as those are more influenced by outside factors than by changes within client, website or documentation.

Having a product that doesn't care about privacy would track the flow from external referrals to the website/docs to the client and up to the first or recurring trades within Bisq. Introducing new features would not be deployed to everyone as to keep a significant control group to make objective decisions.

We don't want/can't do something like that as one of the selling points of Bisq is privacy.

So what could we do?
- Everyone who files a compensation request adds a section explaining what a success of this contribution would mean
- For the client: start thinking about how we could measure if a new version update was a success
- For the website: here we could use regular strategies for success already (goal conversions to client download)
- For docs: we could measure if we are able to reduce support requests on Keybase/bisq.community in comparison to the monthly active accounts

Those are just a few thoughts on this and if it went a little bit off-topic - my apologies. 
 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/150#issuecomment-566033548
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191216/4be33ee0/attachment.html>