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

Figure out how to actually manage "Open Design" process and where to host it #6

Open
victorb opened this issue Nov 12, 2020 · 1 comment
Projects

Comments

@victorb
Copy link
Contributor

victorb commented Nov 12, 2020

Currently using the GitHub issues here, but that might not be the best way of managing this.

Secondly, we can take a look at Notion. Unsure how their pricing would work for us (think we have to pay per user, which is not gonna work for a truly open and inclusive process), but need to take a deeper look.

The tool needs to at least support (ad-hoc or natively):

  • Creating/closing tasks that should be done
  • Assigning people to tasks
  • Facilitate discussions around specific tasks
  • Ideally have a way of setting up dependencies between tasks
@victorb
Copy link
Contributor Author

victorb commented Nov 13, 2020

My thoughts around a workflow for this:

  • Create initial discussion to scope what problem needs solving, and include what it's not gonna solve (small steps, focus on iterations)
  • Once problem scope has been locked down, figure out requirements to get there
  • If the problem scope is very large, break down the scope into many pieces and repeat from step 1 with all of the pieces
  • Task now open for someone to start working on. Lock the task for that person/group
  • Once open for review, people can leave feedback
  • Iterate until we're happy with it
  • Implement the design into the production resource
  • And once done, close the task as finished

Any opinions on this? We could implement this flow in most tools I think, only difference would be in how "locked down" the flow is, which probably at this stage is not as important as that we actually get into the flow.

@victorb victorb added this to Problem Scoping in Taskboard Nov 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Taskboard
Problem Scoping
Development

No branches or pull requests

1 participant