what does really useful reporting look like for Right to Know?
@benrfairless assigning this task, asking for a first iteration of this, to you. Some opening questions. Please have a go at a couple of sentences -> a short paragraph to begin, summarising a period of time that you have a strong sense of at the moment, for example, since the start of the year, the last quarter or the last month.
- what does good or great look and feel like to you?
- what do you want team members / the organisation / people generally (which might include users) to know?
- open to include any highlights, challenges or support needs
It's also the start of a conversation, meaning I welcome your responses to the broader questions as we navigate together a report that may include experiential, quantative and/or qualitative aspects.
I'm anticipating that some things that come up will relate to outstanding issues in Github
@katska Removing #584 as a sub-issue as it remains it's own separate issue.
Please have a go at a couple of sentences -> a short paragraph to begin, summarising a period of time that you have a strong sense of at the moment, for example, since the start of the year, the last quarter or the last month.
what does good or great look and feel like to you?
For RTK, being on top of things is one of the most important things to me. Ensuring we respond to priority issues (personal info requests and complaints) within a timely manner. Something we can't measure would be user satisfaction.
what do you want team members / the organisation / people generally (which might include users) to know?
How successful have we been in helping people access information? How much time has been invested in maintaining the service vs. improvements to the service.
open to include any highlights, challenges or support needs
Curious to know how much time is available from others (tech/leadership) to support RTK vs. other OA projects. Can't help but highlight how out of date Alaveteli is, and how quickly we need to improve it.
@benrfairless thanks I see why you removed https://github.com/openaustralia/righttoknow/issues/584 and am mentioning it here as something to report on, this gives the issue visibility at board level, which may be helpful, along with other reporting in our current configuration to help prioritise focus and resources.
thanks @benrfairless for a first report back. I'm going to leave this open for now for the following:
- I'll post any requests for information from directors.
- Please share any further thoughts or updates, reflections or feedback. I haven't shared your report here because it was shared privately, so please think about what you feel confortable sharing publicly. (not a requirement, rather a broad question to consider)