πŸ₯³Tech Fleet Operations Workbook

Change Process

  1. Understand the problem space you're trying to solve

  2. Ideate on the solution with the community

  3. Design the proposal

  4. Vote and implement

  5. Iterate iterate iterate

Creating New Guilds

Tech Fleet is made up of distributed teams called Guilds with different missions. Learn more about how it all works, and how to create a new Guild, in the Guild Handbook

βš’οΈpageGuild Handbook

How to Propose Changes

Let’s all take a UX approach to improving the Tech Fleet experience:

Start by understanding the problem space.

  1. First, do secondary research. Gather information from Notion, GitBook, the Tech Fleet website, and search our Slack workspace for relevant conversations.

  2. Next, do primary research. For example:

    1. Do a comparative analysis. Figure out how other organizations are handling this issue.

    2. Reach out to individuals in Tech Fleet who might have historical knowledge about this issue, being mindful that they may have limited capacity to respond.

    3. Conduct surveys or interviews with community members. Be careful to avoid bias in your sampling!

  3. Then, clearly define the problem. Synthesize your research and share your findings with the community. Ask for feedback and insights about anything you may have missed in your research.

  4. At this point, you may find that others are interested in joining you in this project. Consider forming a task force before moving onto the next step.

Ideate on the Solution

  1. Start by inviting the community to respectfully share their ideas for potential solutions. You can do this in Slack and/or a live community meeting.

  2. You can also share your own ideas, but consider holding back until others have had a chance to share.

    1. Include a reminder that all ideas will require labor to be realized, and that Tech Fleet is volunteer-run.

    2. Consider what you learned from your research, and be clear about how you might address known obstacles.

    3. Be open to hearing critical feedback, and do your best to model a kind and respectful tone.

  3. Collect and synthesize all of the research and community ideas into an organized document.

Design and Implement

  1. Create a proposal to bring the design to life.

    1. Start with a clear problem statement.

    2. Summarize your research.

    3. Describe your proposed solution(s) in detail: What, when, how, where, who, and why?

  2. Share your proposal with the community for feedback.

  3. Finalize your proposal document.

  4. Connect with a member of the Infrastructure team to discuss your proposal

    1. Infrastructure may suggest additional steps for you to complete before the project is able to be implemented

    2. If you are able to commit to doing the implementation work yourself (or with the help of a committed crew you’ve organized), it is much easier for Infrastructure to help you get it done

    3. If the plan is complete, but Infrastructure is not able to take on the project at this time, it will be backlogged for a later date

Test and Iterate

This is just the beginning! After your solution has been implemented, continue to monitor and evaluate how it is going. We’ll iterate as needed. See the Agile Handbook for more thoughts and guides on how teams should iterate through the Agile philosophy.

Last updated