Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft a separate partner specific plan based on nature of observation (in-person/remote), number of participants at the organization and share with the organization. #286

Open
1 task done
Tracked by #253
tarunima opened this issue Jul 3, 2023 · 3 comments
Assignees
Labels
level:feature An issue that describes a feature (initiative>feature>ticket) size:2pt stale track: P1 Product track: user-facing tool for ogbv response

Comments

@tarunima
Copy link
Collaborator

tarunima commented Jul 3, 2023

Customize the general user-research plan (#285) for specific organizations. This plan will include:

  • Days, weeks when Tattle would like to interview/speak with partner organization. This will be specific in the short-term, and fuzzier for future months.
  • The number of partner organization members we would like to/can involve.

Share the plan with the organization a week before we plan to start the first exercise with them. The goal is to have the user plan sent to all three organizations, by target date.

As and when more organizations are onboarded, you can add a new issue below for the user plan for specific organizations:

@tarunima tarunima added the track: P1 Product track: user-facing tool for ogbv response label Jul 3, 2023
@tarunima tarunima self-assigned this Jul 17, 2023
@tarunima
Copy link
Collaborator Author

tarunima commented Jul 17, 2023

Tasks for July 17 - 22:

Post July 22 (convert it to another different issue in next sprint)

  • Based on feedback set up meetings.

@dennyabrain dennyabrain added the level:feature An issue that describes a feature (initiative>feature>ticket) label Jul 21, 2023
Copy link

github-actions bot commented Dec 4, 2023

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Dec 4, 2023
@github-actions github-actions bot removed the stale label Apr 8, 2024
Copy link

github-actions bot commented May 9, 2024

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level:feature An issue that describes a feature (initiative>feature>ticket) size:2pt stale track: P1 Product track: user-facing tool for ogbv response
Projects
No open projects
Status: In Progress
Status: In Progress
Development

No branches or pull requests

2 participants