I'd welcome more info (task desc). I can't judge yet if I could provide any helpful input or not. "actionable tasks" for CL/CEP (kind of "internal")? Or for some eng teams? Any public examples for "non-technical feedback"? TIA
Egads, I never responded to this.
Turning feedback on Talk pages into Phab tickets, but also into reports for meetings. It's more about the non-phab feedback and more about the information that's provided by users and trying to parse it.
There is a Design Research worksgop for staff next week, and I am hoping my team can come to it. I think that team has a good method of taking feedback and turning it into concise, actionable tasks that teams can work with, and I think it could help to frame our thinking about the writen feedback that the team so often sees.
This is poorly defined. "Find a best way" of doing something is actionable, but on a more philosophical level. Will continue working on this overall problem, but I don't think this task embodies the problem we're actually trying to solve.